Replying to Avatar dluvian

I follow 224 people and rust-nostr sdk selects 219 relays (139 connected) for me, Gossip 37 relays and the old Voyage 15 relays.

nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet is the relay selection intentionally high? I'm moving both Gitplaza and Voyage to the sdk and it would be nice if my light client doesn't have to connect to over 100 relays😄

Avatar
Yuki Kishimoto 6mo ago

It currently take at max the first 5 relays from the NIP65 list (I thought I had lowered it to 3, I'll decrease it soon).

But also taking at max 3, the number of connections may be high. Should I lower it to 2?

We've added support for "sleep when idle" for relays (in master branch). I still have to finalize the support in the SDK. With this, the gossip relays (or even all relays) can connect on-demand and sleep when idle.

Another plan is to add a persistent storage for gossip data, give a rank/score to relays... but I still not found the best way to do this. Ideas are appreciated :)

Reply to this note

Please Login to reply.

Discussion

Avatar
dluvian 6mo ago

3 feels right. In Voyage I take two per pubkey but I take the ones that overlap with my own relay list and the pool of relays that are already selected. Most people use the same big relays so the pool size never grows that much.