Make reviews replaceable events

This commit is contained in:
Jon Staab 2024-09-26 08:33:45 -07:00
parent 0b5afbb651
commit b1432b705f
4 changed files with 16 additions and 8 deletions

1
51.md
View File

@ -53,6 +53,7 @@ Aside from their main identifier, the `"d"` tag, sets can optionally have a `"ti
| Curation sets | 30005 | groups of videos picked by users as interesting and/or belonging to the same category | `"a"` (kind:34235 videos) |
| Kind mute sets | 30007 | mute pubkeys by kinds<br>`"d"` tag MUST be the kind string | `"p"` (pubkeys) |
| Interest sets | 30015 | interest topics represented by a bunch of "hashtags" | `"t"` (hashtags) |
| Rating sets | 30020 | A list of [NIP 85](./85.md) rating events | `"e"`, `"a"` ([NIP 85](./85.md) rating events) |
| Emoji sets | 30030 | categorized emoji groups | `"emoji"` (see [NIP-30](30.md)) |
| Release artifact sets | 30063 | groups of files of a software release | `"e"` (kind:1063 [file metadata](94.md) events), `"i"` (application identifier, typically reverse domain notation), `"version"` |

5
73.md
View File

@ -24,6 +24,11 @@ There are certain established global content identifiers such as [Book ISBNs](ht
| Podcast Publishers | "podcast:publisher:guid:`<guid>`" | "podcast:publisher:guid" |
| Movies | "isan:`<id, without version part>`" | "isan" |
| Papers | "doi:`<id, lowercase>`" | "doi" |
| Nostr Event ID | "e:`<event-id>`" | "e" |
| Nostr Event Address | "a:`<address>`" | "a" |
| Nostr Pubkey | "p:`<pubkey>`" | "p" |
Note that nostr-native IDs should only be used when avoiding a collision with other tags with the same type, for example with [NIP 85](./85.md) reviews that tag a pubkey in the review.
---

12
85.md
View File

@ -6,7 +6,9 @@ Reviews
This NIP describes several different types of `review` which follow a single set of conventions.
In all cases, the `content` field SHOULD include a human-readable review. A single [NIP 73](./73.md) `i` tag indicates the object of the review. This allows for reviews of events, people, topics, relays, or external guids.
In all cases, the `content` field SHOULD include a human-readable review.
Review events' `d` tag indicates the object of the review. This MUST take the form of a [NIP 73](./73.md) id. This allows for reviews of events, people, topics, relays, or external guids without ambiguity.
# Ratings
@ -17,17 +19,17 @@ and an optional `mark` specifying an attribute of the thing being reviewed.
## Relays
Kind `1987` indicates a review of a relay:
Kind `31987` indicates a review of a relay. The `d` tag MUST be the url of the relay.
```json
{
"kind": 1987,
"kind": 31987,
"content": "This relay is fast!",
"tags": [
["d", "wss://relay.example.com/"],
["rating", "0.8"],
["rating", "0.2", "content"],
["rating", "1", "speed"],
["i", "wss://relay.example.com/"]
["rating", "1", "speed"]
],
}
```

View File

@ -131,7 +131,6 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
| `1971` | Problem Tracker | [nostrocket][nostrocket] |
| `1984` | Reporting | [56](56.md) |
| `1985` | Label | [32](32.md) |
| `1986` | Relay reviews | |
| `1987` | AI Embeddings / Vector lists | [NKBIP-02] |
| `2003` | Torrent | [35](35.md) |
| `2004` | Torrent Comment | [35](35.md) |
@ -202,6 +201,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
| `31923` | Time-Based Calendar Event | [52](52.md) |
| `31924` | Calendar | [52](52.md) |
| `31925` | Calendar Event RSVP | [52](52.md) |
| `31987` | Relay Review | [85](85.md) |
| `31989` | Handler recommendation | [89](89.md) |
| `31990` | Handler information | [89](89.md) |
| `34235` | Video Event | [71](71.md) |