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

Update 10.md("Commit Changes Description")

Browse Source 
Changes made: Updated the description for the <pubkey> variable within the context of an event with the 'e' tag. The updated comment explains that the `<pubkey>` SHOULD be the pubkey of the author of the e tagged event, and it is used in the outbox model to search for that event from the author's write relays where relay hints did not resolve the event.
This commit is contained in:
Jesus Christ 2024-11-28 09:14:06 +00:00 committed by GitHub
parent 3d1a34de91
commit 651de5b156
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
10.md
View File

@ -26,7 +26,7 @@ A direct reply to the root of a thread should have a single marked "e" tag of ty
>This scheme is preferred because it allows events to mention others without confusing them with `<reply-id>` or `<root-id>`. >This scheme is preferred because it allows events to mention others without confusing them with `<reply-id>` or `<root-id>`.
`<pubkey>` SHOULD be the pubkey of the author of the `e` tagged event, this is used in the outbox model to search for that event from the authors write relays where relay hints did not resolve the event. `<pubkey>` SHOULD be the pubkey of the author of the `e` tagged event, this is used in the outbox model to search for that event from the author's write relays where relay hints did not resolve the event.
## 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. Used in a text event contains a list of pubkeys used to record who is involved in a reply thread.