mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-12-13 02:46:24 +00:00
Quick adjustments
This commit is contained in:
parent
a3292f4ae7
commit
b7aa64dab4
16
81.md
16
81.md
@ -8,7 +8,9 @@ Relationship Status
|
||||
|
||||
## Abstract
|
||||
|
||||
Creates a replaceable event to assert the level of trust from the author to any other pubkey. The wise-spread use of these statuses between pubkeys is not ideal for Kind 3 or NIP-51 list structures.
|
||||
Creates a replaceable event to assert the level of trust from the author to any other pubkey.
|
||||
|
||||
The wise-spread use of these statuses between pubkeys is not ideal for Kind 3 or NIP-51 list structures.
|
||||
|
||||
# Relationship Status Event
|
||||
|
||||
@ -23,16 +25,20 @@ For example:
|
||||
["d", "612ae..e610f"],
|
||||
],
|
||||
"content": "<NIP-44 encrypted Stringified TAG-List(
|
||||
["status", "< Known Face, Contact, Following, Coworker, Friend, Partner, Family, Extended family, Trusted, Competitor, Traitor, Used to Know, Scammer, NSFW, Unkown, etc>"],
|
||||
["nickname", "< nickname to be used instead of the person's name in all interfaces >"]
|
||||
["status", "<Known Face, Contact, Following, Coworker, Friend, Partner,
|
||||
Family, Extended family, Trusted, Competitor, Traitor, Used to Know,
|
||||
Scammer, NSFW, Unkown, etc>"],
|
||||
["nickname", "<My buddy>"]
|
||||
["summary", "<Summary of the relationship>"],
|
||||
)",
|
||||
...other fields
|
||||
}
|
||||
```
|
||||
|
||||
Status MUST be a case-sensitive displayble category name with the expecation to group users by it.
|
||||
`status` MUST be a case-sensitive displayable category name with the expectation to group users by it. It is privately scoped and thus new statuses/groups are welcome.
|
||||
|
||||
`nickname` SHOULD be used instead of the person's display name in all interfaces
|
||||
|
||||
Profile screens MAY display the summary of the relationship and allow the user to change the tags of this event.
|
||||
|
||||
Clients MAY filter by `kind:30382` to determine how to assemble feeds, group messages and when to display content.
|
||||
Clients MAY filter by `kind:30382` to determine how to assemble feeds, group messages, and when to display content.
|
Loading…
Reference in New Issue
Block a user