nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

separate array elements with ,

Browse Source
This commit is contained in:
Leo Wandersleb 2022-09-02 16:07:50 -04:00 committed by fiatjaf
parent 7af2540c6e
commit 3e0e6ca2d6
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
10.md
View File

@ -13,7 +13,7 @@ This NIP describes how to use "e" and "p" tags in text events, especially those
## Positional "e" tags (DEPRECATED)
>This scheme is in common use; but should be considered deprecated.
`["e", <event-id> <relay-url>]` as per NIP-01.
`["e", <event-id>, <relay-url>]` as per NIP-01.
Where:
@ -38,7 +38,7 @@ They are citings from this event. `root-id` and `reply-id` are as above.
>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.
## Marked "e" tags (PREFERRED)
`["e", <event-id> <relay-url> <marker>]`
`["e", <event-id>, <relay-url>, <marker>]`
Where:
@ -54,7 +54,7 @@ Where:
## 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 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.
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.
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`]
in no particular order.