mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-09-19 14:35:48 -04:00
14 lines
998 B
Markdown
14 lines
998 B
Markdown
|
NIP-31
|
||
|
|
======
|
||
|
|
|
||
|
|
Dealing with unknown event kinds
|
||
|
|
--------------------------------
|
||
|
|
|
||
|
|
`draft` `optional` `author:pablof7z` `author:fiatjaf`
|
||
|
|
|
||
|
|
When creating a new custom event kind that is part of a custom protocol and isn't meant to be read as text (like `kind:1`), clients should use the `tags` field to store all their custom data related to their protocol, and use the `content` field to write a short human-readable plaintext summary of what that event is about.
|
||
|
|
|
||
|
|
The intent is that social clients, used to display only `kind:1` notes, can still show something in case a custom event pops up in their timelines.
|
||
|
|
|
||
|
|
These clients that only know `kind:1` are not expected to ask relays for events of different kinds, but users could still reference these weird events on their notes, and without proper context these could be nonsensical notes. Having the fallback text makes that situation much better -- even if only for making the user aware that they should try to view that custom event elsewhere.
|