Thank you #[4]! Let me know if you have any questions #[2]
Scroll down this guide to part about “relays”. https://bit.ly/41gaBdE
One of the most popular relays is: nostr.wine
Nostr wine, Also has monthly fee “relay filter” (filter separate fee from relay).
#[2] is owner that relay, very helpful kind fren
#[3] is really amazing & knowledgeable about relays… I’m not the best, so I’ll direct you to dear fren fishcake
Discussion
Thanks for this. As far as I understand the relays sync with each other but the paid ones have less or no spam. I‘ll try nostr.wine as soon as I understand which of the relays to keep and which ones to kick…
No explicit syncing between relays, nostr.wine has it but that’s the only one I know. Relay only relays between users of that relay! 🐶🐾🫡
Ah, so I have to know what’s in a relay. Are there relays for special interest? Like relays for developers or relays for linux enthusiasts?
I keep forgetting where the list of all relays was, but there is some sort of directory for that. Also, you could look at stats to see how active each one is. https://stats.nostr.band/
Mine are fairly well balanced and have a lot of devs on them! 🐶🐾🫡
One question #[4] : should I use both relays: nostr.wine and filter.nostr.wine or is the filter relay enough?
Both! 🐶🐾🫂🫡
And why both? Do they contain different events?
Events are deduplicated by you client. One can do rebroadcasting (filter) and removes the spam, another one is a general relay! #[3] will have to chime in to provide more details, since I am not on the team or have access to the code! 🐶🐾🫡
Think of nostr.wine as just a normal one time fee pay to write, free to read relay. It doesn’t aggregate events from anywhere, and it only lets paid members post.
Filter.nostr.wine is a completely different relay/product that requires a monthly recurring subscription. This relay reads from a 10-15 large public relays and rebroadcasts your events to them (if you use broadcast=true). You can learn more about filter here: https://docs.nostr.wine/filter/readme