nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-19 14:35:48 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

rename NIP-13 to NIP-10

Browse Source
This commit is contained in:
Robert C. Martin 2022-05-04 15:14:49 -05:00
parent 96e4e7eb5c
commit bd4a81a604
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
13.md → 10.md
View File

@ -1,4 +1,4 @@
NIP-13
NIP-10
======
@ -7,18 +7,18 @@ On `e` and `p` tags in Text Events (kind 1).
`draft` ~`mandatory`~ `author:unclebobmartin`
### A recommendation for clients.
### A Conventional use of `e` and `p` tags within clients.
The following seems to be the conventions that are used by `Branle`, `Damus`, and `more-speech` for referencing
events and authors when building a reply. These conventions help clients build event threads, and alert authors of
replies.
## Definitions:
### Definitions:
* A reply chain is the list of events from the root event to a specific reply.
* A reply thread is the tree of events consisting of all replies beginning at the root.
* An event id is a 32 byte number in lower-case hexidecimal.
## The `e` tag
### The `e` tag
Used in a text event contains a single event id. ["e", "`hex-number`"]
* No `e` tag:
@ -34,7 +34,7 @@ The id of the event to which this event is a reply.
There may be any number of `mention-ids`. These are the ids of events which may, or may not be in the reply chain.
They are citings from this event. `root-id` and `reply-id` are as above.
## The `p` tag
### The `p` tag
Used in a text event contains a list of pubkeys used to record who is involved in a reply thread.
When replying to a text event E with `p` tags P, the replying event's `p` tags should contain P as well as the pubkey of the of the event being replied to.