Better defining kind:0

This commit is contained in:
Vitor Pamplona 2024-01-03 14:41:11 -05:00
parent c4daa69498
commit 2f8da3a5c7

4
01.md
View File

@ -83,9 +83,7 @@ Parameterized Repleaceable events MUST include a `d`-tag with an identifier val
In case of replaceable events with the same timestamp, the event with the lowest `.id` (first in lexical order) SHOULD be retained. Older versions MAY be kept but SHOULD not be returned on queries. In case of replaceable events with the same timestamp, the event with the lowest `.id` (first in lexical order) SHOULD be retained. Older versions MAY be kept but SHOULD not be returned on queries.
This NIP defines two kinds: This NIP defines the `kind:0` as **User Metadata**. The `.content` is set to a stringified JSON object `{name: <user's name, string>, about: <string>, picture: <url, string>}`. Since other attributes might exist, Clients SHOULD preseve any unsupported attribute when updating this event.
- `kind:0`: **User Metadata**: An event kind to add name and other information to the pubkey. The `content` is set to a stringified JSON object `{name: <user's name, string>, about: <string>, picture: <url, string>}`
## Tags ## Tags