I’m running three atm
damus
eden
mutiny
why should I switch this?
Discussion
My understanding is that by switching to the relays suggested in this note, you’d be improving the efficiency of how your client communicates with the most used relays, and therefore improving performance. In the case of connecting to wine relay you are essentially connecting to many others for reading and writing, by just connecting to one. In doing so, you are decreasing the number of individual relay connection requests your client is making. Thereby improving (decreasing) consumption of data and battery resources. Although there seems to be a centralization factor to consider as well. Maybe we don’t want to have many accounts connecting to a handful of relays that proxy the most popular relays in the network. Even if doing so improves resource consumption
Not really sure if it is an improvement in your case since you are connected to a few, but for those who are individually connecting to many of the relays wine is, like I was, then possibly it is. Curious myself to hear the OPs thoughts on your question.
summary:
With relay.nostr.band relay you read in all relays.
With relay.nostr.mutinywallet.com you write to all relays.
nostr.wine gives you permission to use filter.nostr.wine and we use it to have a spam-free global feed as it queries the notes of your contacts and the notes of your contacts' contacts.
Even though relay.nostr.band has anti-spam, a lot of spam gets through, so I prefer to exclude it from the global feed and use filter.nostr.wine.
We also use filter.nostr.wine as both a read and write backup in case the first two fail, although its scope is more limited as it only reads and writes from about 10 relays.
In short, you have write and read access to practically all nostr realys that are in the nostr.watch list with only 4 relays, so you save on battery and data and gain in visibility.
Actually, trying this setup. So far so good 🤙