#AUStriches help me grock relays. How many do I need? What is considered a good relay? How to optimise relays for best user experience?

Reply to this note

Please Login to reply.

Discussion

I wouldn't add any more than a dozen or so. After that you could experience problems on certain clients. I had 47 back in January. It was a bad time. I then tried mid 30s that was not better. Neither were 20s. I am mid-teens now and am mostly fine, but Snort is very slow. If I had 8-12 it would be best.

Hi Derek, thanks for sharing!

I don't understand, why is more relays worse?

My first attempt to improve my experience was to add more relays. I feel others will do the same by default.

How did you identify less was better? Trial and error? Cheers

it's definitely not like pokemon. you do not want to catch them all. why? because for every relay, that's a web socket connection that your client must read and write from for every single action you take across nostr. contacting them all over and over again uses TONS of data, but not only that, it slows down your entire experience having to read and write to and from so many web sockets. if one of those relays is slow or has issues, the entire experience is degraded.

i used 10GB of data in the first 6 days of january on my phone 😆

Put briefly, focus on quality over quantity, pulling the same data from 100 relays is more intensive than from a smaller group of good relays

I try to stay around 10 or less and go for popular relays that run strfry (nostr-rs is good too).

It’s also good to have a relay that does aggregation like nostr.band or nostr.wine (paid).

The nostr.wine filter relay also rebroadcasts your notes. IMO, the best client experience is using this set up with only 4-5 backup relays, but you need to pay for it.