8 ms·
Can you elaborate on this? What can you do with this client, and how does it find the relays to use to get notified of new notes? I don't know very much about
by kragen 22d ago
Can you elaborate on this? What can you do with this client, and how does it find the relays to use to get notified of new notes?
I don't know very much about Nostr, so I don't know the answers to these questions, or even if they are the right questions to ask.
- hardran3 22d agoUsers set their own relays. Other users can see this list and use it to send and receive events. It's fixed the need of big common relays. https://nips.nostr.com/65 https://nips.nostr.com/65
- kragen 22d agoSo how does this hypothetical client find out what non-big relays have been set by the other users whose notes its user wants to receive, if not by receiving notes from those other users via one of the big common relays?
- chr15m 22d agoBy seeding relay lists widely. This is the "bootstrap problem" faced by all p2p networks. NIP65 suggests spreading relay lists widely and to "pay attention" to popular relays: > Clients SHOULD spread an author's kind:10002 event to as many relays as viable, paying attention to relays that, at any moment, serve naturally as well-known public indexers for these relay lists (where most other clients and users are connecting to in order to publish and fetch those). Note this is different to centralising the whole protocol on popular relays. If affects the discovery phase only, and is robust to large relays disappearing. If clients seed address lists widely they can easily find each other without major centralisation.