diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2023-06-17 15:49:52 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2023-06-17 15:50:16 -0300 |
| commit | 36e9fd59e93730c2d2002ec7aac58a53e58143a3 (patch) | |
| tree | 6b2a4ba7b96f8ed0a11b2fa383e5a3b5d2876a7a /01.md | |
| parent | c8c2ab60aba9b45bb1a37f412e83921f9a8470e2 (diff) | |
add note about websocket status code 4000.
nip-01 may need some love.
Diffstat (limited to '01.md')
| -rw-r--r-- | 01.md | 1 |
1 files changed, 1 insertions, 0 deletions
| @@ -110,3 +110,4 @@ A relay may choose to treat different message kinds differently, and it may or m | |||
| 110 | - The `tags` array can store a tag identifier as the first element of each subarray, plus arbitrary information afterward (always as strings). This NIP defines `"p"` — meaning "pubkey", which points to a pubkey of someone that is referred to in the event —, and `"e"` — meaning "event", which points to the id of an event this event is quoting, replying to or referring to somehow. See [NIP-10](10.md) for a detailed description of "e" and "p" tags. | 110 | - The `tags` array can store a tag identifier as the first element of each subarray, plus arbitrary information afterward (always as strings). This NIP defines `"p"` — meaning "pubkey", which points to a pubkey of someone that is referred to in the event —, and `"e"` — meaning "event", which points to the id of an event this event is quoting, replying to or referring to somehow. See [NIP-10](10.md) for a detailed description of "e" and "p" tags. |
| 111 | - The `<recommended relay URL>` item present on the `"e"` and `"p"` tags is an optional (could be set to `""`) URL of a relay the client could attempt to connect to fetch the tagged event or other events from a tagged profile. It MAY be ignored, but it exists to increase censorship resistance and make the spread of relay addresses more seamless across clients. | 111 | - The `<recommended relay URL>` item present on the `"e"` and `"p"` tags is an optional (could be set to `""`) URL of a relay the client could attempt to connect to fetch the tagged event or other events from a tagged profile. It MAY be ignored, but it exists to increase censorship resistance and make the spread of relay addresses more seamless across clients. |
| 112 | - Clients should use the created_at field to judge the age of a metadata event and completely replace older metadata events with newer metadata events regardless of the order in which they arrive. Clients should not merge any filled fields within older metadata events into empty fields of newer metadata events. | 112 | - Clients should use the created_at field to judge the age of a metadata event and completely replace older metadata events with newer metadata events regardless of the order in which they arrive. Clients should not merge any filled fields within older metadata events into empty fields of newer metadata events. |
| 113 | - When a websocket is closed by the relay with a status code 4000 that means the client shouldn't try to connect again. | ||