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

Adds edge cases

Browse Source
This commit is contained in:
Vitor Pamplona 2024-02-12 12:17:06 -05:00
parent 1e7da2bb70
commit 3ff65d1d64
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
81.md
View File

@ -6,7 +6,7 @@ Relationship Status
`draft` `optional` `draft` `optional`
Event `kind:30382` documents a "Relationship Status" between two pubkeys and uses private and public tags to enhance the description of that relationship. Since statuses change over time, this event is defined as a _parameterized replaceable event_ with a single `d` tag that identifies each pair of keys. Event `kind:30382` documents a "Relationship Status" between two keys, the signer and a `p`-tag, and uses private and public tags to enhance the description of that relationship. Since statuses change over time, this event is defined as a _parameterized replaceable event_ with a single `d` tag whole value identifies the key pair.
Optional `n` tags add the target key to unbound lists. Optional `n` tags add the target key to unbound lists.
@ -57,6 +57,12 @@ Profile screens MAY display the summary of the relationship and allow the user t
Clients MAY filter by `kind:30382`, with or without `n` tags, to determine how to assemble feeds, group messages, and when to display content. Clients MAY filter by `kind:30382`, with or without `n` tags, to determine how to assemble feeds, group messages, and when to display content.
Web of Trust processors MAY use `kind:30382` as directional edges in the Web of Trust graph.
Multiple `p`-tags in a single `kind:30382` represent a group of individuals that SHOULD be considered as of one entity. The other tags decribe the relationship to the entity and not individual keys.
Having one `p`-tag in multiple `d`-tags represent separate statuses for the same pubkey based on their participation in a list `n`
### Private `n`-tags ### Private `n`-tags
Clients MAY hide human readable `n`-tags behind a code and list their code maps in the new "Unbound List Names" event kind (`kind:10008`), using the `map` tag from code to name. Clients MAY hide human readable `n`-tags behind a code and list their code maps in the new "Unbound List Names" event kind (`kind:10008`), using the `map` tag from code to name.