diff options
Diffstat (limited to '10.md')
| -rw-r--r-- | 10.md | 12 |
1 files changed, 6 insertions, 6 deletions
| @@ -13,7 +13,7 @@ This NIP describes how to use "e" and "p" tags in text events, especially those | |||
| 13 | ## Positional "e" tags (DEPRECATED) | 13 | ## Positional "e" tags (DEPRECATED) |
| 14 | >This scheme is in common use; but should be considered deprecated. | 14 | >This scheme is in common use; but should be considered deprecated. |
| 15 | 15 | ||
| 16 | `["e", <event-id> <relay-url>]` as per NIP-01. | 16 | `["e", <event-id>, <relay-url>]` as per NIP-01. |
| 17 | 17 | ||
| 18 | Where: | 18 | Where: |
| 19 | 19 | ||
| @@ -26,19 +26,19 @@ Where: | |||
| 26 | This event is not a reply to, nor does it refer to, any other event. | 26 | This event is not a reply to, nor does it refer to, any other event. |
| 27 | 27 | ||
| 28 | * One "e" tag: <br> | 28 | * One "e" tag: <br> |
| 29 | `["e",<id>]`: The id of the event to which this event is a reply. | 29 | `["e", <id>]`: The id of the event to which this event is a reply. |
| 30 | 30 | ||
| 31 | * Two "e" tags: `["e",<root-id>]`, `["e",<reply-id>]` <br> | 31 | * Two "e" tags: `["e", <root-id>]`, `["e", <reply-id>]` <br> |
| 32 | `<root-id>` is the id of the event at the root of the reply chain. `<reply-id>` is the id of the article to which this event is a reply. | 32 | `<root-id>` is the id of the event at the root of the reply chain. `<reply-id>` is the id of the article to which this event is a reply. |
| 33 | 33 | ||
| 34 | * Many "e" tags: `["e",<root-id>]` `["e",<mention-id>]`, ..., `["e",<reply-id>]`<br> | 34 | * Many "e" tags: `["e", <root-id>]` `["e", <mention-id>]`, ..., `["e", <reply-id>]`<br> |
| 35 | There may be any number of `<mention-ids>`. These are the ids of events which may, or may not be in the reply chain. | 35 | There may be any number of `<mention-ids>`. These are the ids of events which may, or may not be in the reply chain. |
| 36 | They are citings from this event. `root-id` and `reply-id` are as above. | 36 | They are citings from this event. `root-id` and `reply-id` are as above. |
| 37 | 37 | ||
| 38 | >This scheme is deprecated because it creates ambiguities that are difficult, or impossible to resolve when an event references another but is not a reply. | 38 | >This scheme is deprecated because it creates ambiguities that are difficult, or impossible to resolve when an event references another but is not a reply. |
| 39 | 39 | ||
| 40 | ## Marked "e" tags (PREFERRED) | 40 | ## Marked "e" tags (PREFERRED) |
| 41 | `["e", <event-id> <relay-url> <marker>]` | 41 | `["e", <event-id>, <relay-url>, <marker>]` |
| 42 | 42 | ||
| 43 | Where: | 43 | Where: |
| 44 | 44 | ||
| @@ -54,7 +54,7 @@ Where: | |||
| 54 | ## The "p" tag | 54 | ## The "p" tag |
| 55 | Used in a text event contains a list of pubkeys used to record who is involved in a reply thread. | 55 | Used in a text event contains a list of pubkeys used to record who is involved in a reply thread. |
| 56 | 56 | ||
| 57 | When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the `"pubkey"` of the of the event being replied to. | 57 | When replying to a text event E the reply event's "p" tags should contain all of E's "p" tags as well as the `"pubkey"` of the event being replied to. |
| 58 | 58 | ||
| 59 | Example: Given a text event authored by `a1` with "p" tags [`p1`, `p2`, `p3`] then the "p" tags of the reply should be [`a1`, `p1`, `p2`, `p3`] | 59 | Example: Given a text event authored by `a1` with "p" tags [`p1`, `p2`, `p3`] then the "p" tags of the reply should be [`a1`, `p1`, `p2`, `p3`] |
| 60 | in no particular order. | 60 | in no particular order. |