diff options
Diffstat (limited to '01.md')
| -rw-r--r-- | 01.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -98,7 +98,7 @@ This NIP defines no rules for how `NOTICE` messages should be sent or treated. | |||
| 98 | ## Basic Event Kinds | 98 | ## Basic Event Kinds |
| 99 | 99 | ||
| 100 | - `0`: `set_metadata`: the `content` is set to a stringified JSON object `{name: <username>, about: <string>, picture: <url, string>}` describing the user who created the event. A relay may delete past `set_metadata` events once it gets a new one for the same pubkey. | 100 | - `0`: `set_metadata`: the `content` is set to a stringified JSON object `{name: <username>, about: <string>, picture: <url, string>}` describing the user who created the event. A relay may delete past `set_metadata` events once it gets a new one for the same pubkey. |
| 101 | - `1`: `text_note`: the `content` is set to the text content of a note (anything the user wants to say). Non-plaintext notes should instead use kind 1000-10000 as described in [NIP-16](16.md). | 101 | - `1`: `text_note`: the `content` is set to the plaintext content of a note (anything the user wants to say). Markdown links (`[]()` stuff) are not plaintext. |
| 102 | - `2`: `recommend_server`: the `content` is set to the URL (e.g., `wss://somerelay.com`) of a relay the event creator wants to recommend to its followers. | 102 | - `2`: `recommend_server`: the `content` is set to the URL (e.g., `wss://somerelay.com`) of a relay the event creator wants to recommend to its followers. |
| 103 | 103 | ||
| 104 | A relay may choose to treat different message kinds differently, and it may or may not choose to have a default way to handle kinds it doesn't know about. | 104 | A relay may choose to treat different message kinds differently, and it may or may not choose to have a default way to handle kinds it doesn't know about. |