diff options
| author | daniele <github@dtonon.com> | 2025-01-30 22:49:06 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-30 13:49:06 -0800 |
| commit | f440eac3dccefa5c0ec9d3964e1d08357fd31e09 (patch) | |
| tree | 612855af96a7db8f1020d9a7049609eb5b4a1232 | |
| parent | 7370729472b5d8b54693e67d0f26b2dd1da84c07 (diff) | |
Remove reference to 'username' and update descriptions in metadata (#1726)
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -89,7 +89,7 @@ Kinds specify how clients should interpret the meaning of each event and the oth | |||
| 89 | 89 | ||
| 90 | This NIP defines one basic kind: | 90 | This NIP defines one basic kind: |
| 91 | 91 | ||
| 92 | - `0`: **user metadata**: the `content` is set to a stringified JSON object `{name: <username>, about: <string>, picture: <url, string>}` describing the user who created the event. [Extra metadata fields](24.md#kind-0) may be set. A relay may delete older events once it gets a new one for the same pubkey. | 92 | - `0`: **user metadata**: the `content` is set to a stringified JSON object `{name: <nickname or full name>, about: <short bio>, picture: <url of the image>}` describing the user who created the event. [Extra metadata fields](24.md#kind-0) may be set. A relay may delete older events once it gets a new one for the same pubkey. |
| 93 | 93 | ||
| 94 | And also a convention for kind ranges that allow for easier experimentation and flexibility of relay implementation: | 94 | And also a convention for kind ranges that allow for easier experimentation and flexibility of relay implementation: |
| 95 | 95 | ||