diff options
| -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 | ||