diff options
| -rw-r--r-- | 10.md | 5 |
1 files changed, 3 insertions, 2 deletions
| @@ -10,8 +10,6 @@ This NIP defines `kind:1` as a simple plaintext note. | |||
| 10 | 10 | ||
| 11 | ## Abstract | 11 | ## Abstract |
| 12 | 12 | ||
| 13 | This NIP describes how to use "e" and "p" tags in text events, especially those that are replies to other text events. It helps clients thread the replies into a tree rooted at the original event. | ||
| 14 | |||
| 15 | The `.content` property contains some human-readable text. | 13 | The `.content` property contains some human-readable text. |
| 16 | 14 | ||
| 17 | `e` and `p` tags can be used to define note threads, replies and mentions. | 15 | `e` and `p` tags can be used to define note threads, replies and mentions. |
| @@ -19,6 +17,9 @@ The `.content` property contains some human-readable text. | |||
| 19 | Markup languages such as markdown and HTML SHOULD NOT be used. | 17 | Markup languages such as markdown and HTML SHOULD NOT be used. |
| 20 | 18 | ||
| 21 | ## Marked "e" tags (PREFERRED) | 19 | ## Marked "e" tags (PREFERRED) |
| 20 | |||
| 21 | Kind 1 events with `e` tags are replies to other kind 1 events. Kind 1 replies MUST NOT be used to reply to other kinds, use [NIP-22](22.md) instead. | ||
| 22 | |||
| 22 | `["e", <event-id>, <relay-url>, <marker>, <pubkey>]` | 23 | `["e", <event-id>, <relay-url>, <marker>, <pubkey>]` |
| 23 | 24 | ||
| 24 | Where: | 25 | Where: |