diff options
| -rw-r--r-- | 65.md | 2 |
1 files changed, 2 insertions, 0 deletions
| @@ -63,6 +63,8 @@ This NIP allows Clients to connect directly with the most up-to-date relay set f | |||
| 63 | 63 | ||
| 64 | 6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-6). | 64 | 6. Clients SHOULD deduplicate connections by normalizing relay URIs according to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986#section-6). |
| 65 | 65 | ||
| 66 | 7. When publishing to a relay, clients SHOULD ensure the user's `kind 10002` is also available on that relay. Relays SHOULD accept and serve `kind 10002` notes for any pubkey whose notes they store. Relays MAY scrape the network for missing `kind 10002` events. The goal here is that for any note served from a relay the user can also request the author's relay selections as a way of bootstrapping further context discovery. | ||
| 67 | |||
| 66 | ## Related articles | 68 | ## Related articles |
| 67 | - [Outbox model](https://mikedilger.com/gossip-model/) | 69 | - [Outbox model](https://mikedilger.com/gossip-model/) |
| 68 | - [What is the Outbox Model?](https://habla.news/u/hodlbod@coracle.social/8YjqXm4SKY-TauwjOfLXS) | 70 | - [What is the Outbox Model?](https://habla.news/u/hodlbod@coracle.social/8YjqXm4SKY-TauwjOfLXS) |