Replying to Avatar Mazin

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

I'm intrigued.

Why would the read and broadcast relays not be the same?

Reply to this note

Please Login to reply.

Discussion

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.