Just deployed additional read/broadcast relays to the https://filter.nostr.wine π· aggregator/broadcast relay.
Added read relays:
- wss://nostr.zebedee.cloud
- wss://relay.plebstr.com
- wss://offchain.pub
Added broadcast relays:
- wss://relay.snort.social
- wss://relay.plebstr.com
- wss://offchain.pub
Noice. Keep up the great work π€
Thank you π«‘
You do great work as well, thank you for helping educate so many.
I'm intrigued.
Why would the read and broadcast relays not be the same?
Good question. They mostly are with a few caveats.
- brb.io is too unstable for broadcasting. We can read from it (poorly) but writing events in mass is a pointless effort (constant timeouts+reconnects)
- snort requires origin header to open the websocket connection. By default not supported by strfry stream (for reading) but we added the header for our broadcaster.
- relay.current.fyi disconnects us every time we try to write an event. Not sure if itβs rate limiting or something else, reached out to them.
Nice! What are your selection criteria if I may ask? I see that nostr.wine exchanges relays quite often.
Nothing too strict. Big(ish) public relays with reasonable performance + uptime.
Most of the switching is due to issues experienced with one or another. Some new additions just because there are new up and coming public relays. For reading, lots of what we get is duplicates after the top 3-5 relays anyway. I doubt adding 200 public relays would get very many more unique events than 10 (at this time).
Nice workβοΈTy π·
I will take zebedee off from may corrections ππ
