I like this solution. Basically, clients would send the users’ kind 10002 event to *all known relays*, while only sending the note itself to the relays the user is connected to.

On the flip side, the client would then be able to pull in that 10002 event data from any of the relays a user is connected to, and know what relay to get another users posts from.

“It is suggested that people spread their kind 10002 events to many relays, but write their normal feed-related events to a much smaller number of relays (between 2 to 6 relays).”

https://github.com/nostr-protocol/nips/blob/master/65.md

Reply to this note

Please Login to reply.

Discussion

#[1]​ #[2]​ #[3]​ #[4] #[5]​ thoughts?

This is very very interesting, it will solve lot of future problems. It will also encourage small communities to host their own relays.

For sure! It also prevents the need for relays to sync data with other relays, and allow clients to autopilot pick relays in a way that evenly distributes load, without losing coverage of posts.

As far as i can tell, Coracle and Gossip use NIP-65, not sure about other clients.

Coracle has got many things right

Wow, It will really make this network more efficient, reliable & much more decentralized. Major clients should definitely implement this.

Yes the client Gossip has a button which let you send that event 10002 to all relays you’re connected to. Gossip also uses these events to let you even connect to more relays automagicly. So with a large social graph you get a lot of relays you’re connecting to. I use Gossip sometimes for some debugging and the list of relays is already quite long (40-50 relays which I haven’t added on my side)

We will be implementing support for this and the rest of Gossips replication model in Nos! It's the way to go for a more scalable network.

Awesome! I'm stoked to try out nos.social, especially after seeing what a slick experience Planetary was.