diff options
| -rw-r--r-- | 10.md | 14 |
1 files changed, 11 insertions, 3 deletions
| @@ -12,7 +12,15 @@ This NIP defines `kind:1` as a simple plaintext note. | |||
| 12 | 12 | ||
| 13 | The `.content` property contains some human-readable text. | 13 | The `.content` property contains some human-readable text. |
| 14 | 14 | ||
| 15 | `e` and `p` tags can be used to define note threads, replies and mentions. | 15 | `e` tags can be used to define note thread roots and replies. They SHOULD be sorted by the reply stack from root to the direct parent. |
| 16 | |||
| 17 | `q` tags MAY be used when citing events in the `.content` with [NIP-21](21.md). | ||
| 18 | |||
| 19 | ```json | ||
| 20 | ["q", "<event-id> or <event-address>", "<relay-url>", "<pubkey-if-a-regular-event>"] | ||
| 21 | ``` | ||
| 22 | |||
| 23 | Authors of the `e` and `q` tags SHOULD be added as `p` tags to notify of a new reply or quote. | ||
| 16 | 24 | ||
| 17 | Markup languages such as markdown and HTML SHOULD NOT be used. | 25 | Markup languages such as markdown and HTML SHOULD NOT be used. |
| 18 | 26 | ||
| @@ -26,10 +34,10 @@ Where: | |||
| 26 | 34 | ||
| 27 | * `<event-id>` is the id of the event being referenced. | 35 | * `<event-id>` is the id of the event being referenced. |
| 28 | * `<relay-url>` is the URL of a recommended relay associated with the reference. Clients SHOULD add a valid `<relay-url>` field, but may instead leave it as `""`. | 36 | * `<relay-url>` is the URL of a recommended relay associated with the reference. Clients SHOULD add a valid `<relay-url>` field, but may instead leave it as `""`. |
| 29 | * `<marker>` is optional and if present is one of `"reply"`, `"root"`, or `"mention"`. | 37 | * `<marker>` is optional and if present is one of `"reply"`, `"root"`. |
| 30 | * `<pubkey>` is optional, SHOULD be the pubkey of the author of the referenced event | 38 | * `<pubkey>` is optional, SHOULD be the pubkey of the author of the referenced event |
| 31 | 39 | ||
| 32 | Those marked with `"reply"` denote the id of the reply event being responded to. Those marked with `"root"` denote the root id of the reply thread being responded to. For top level replies (those replying directly to the root event), only the `"root"` marker should be used. Those marked with `"mention"` denote a quoted or reposted event id. | 40 | Those marked with `"reply"` denote the id of the reply event being responded to. Those marked with `"root"` denote the root id of the reply thread being responded to. For top level replies (those replying directly to the root event), only the `"root"` marker should be used. |
| 33 | 41 | ||
| 34 | A direct reply to the root of a thread should have a single marked "e" tag of type "root". | 42 | A direct reply to the root of a thread should have a single marked "e" tag of type "root". |
| 35 | 43 | ||