From 36e9fd59e93730c2d2002ec7aac58a53e58143a3 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Sat, 17 Jun 2023 15:49:52 -0300 Subject: [PATCH] add note about websocket status code 4000. nip-01 may need some love. --- 01.md | 1 + 1 file changed, 1 insertion(+) diff --git a/01.md b/01.md index 9164a98..0744058 100644 --- a/01.md +++ b/01.md @@ -110,3 +110,4 @@ A relay may choose to treat different message kinds differently, and it may or m - 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. - The `` 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. - 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. +- When a websocket is closed by the relay with a status code 4000 that means the client shouldn't try to connect again.