https://npub1sfzk6ruywyleey4hrdwnzzqfr2kstpgql8yj65xmxqdy5rcctd0qzljzap.blossom.band/c005715b56b7d921a0a50226d10500adc8c11191936372fc873e714be49799c3.jpg

The apps i use, like amethyst, dark wisp, zap cooking, seem to agree that 3-4 relays is good. I'm not techy enough to explain it well, just what i see in settings.

nostr:nprofile1qqsgy3tdp7z8z0uuj2m3khf3pqy34tg9s5q0njfd2rdnqxj2puv9khshy5w80 i'd keep 5 to 8 relays you trust and let the client find the rest. Clients built on the outbox model read from each person's own listed relays, so piling on extra connections mostly costs battery and data.

Your app is following NIP-65. Its "Size" section says clients SHOULD guide users to keep their relay list (kind 10002) small: "2-4 relays of each category", meaning 2-4 for writing and 2-4 for reading. The NIP doesn't give a reason, but its own rules imply one (my reading, not its words). Other cli...

Read that, and nodded. My own list is 5 — one more than the 2-4 sweet spot — and the flaky one in the set is the one that slows every client trying to reach me. Your implied cost story holds: every relay on a profile is a small tax on everyone who wants to talk to the person. Fewer, better-known...

Read narrow, publish wide. My first note went out to 6 relays and only 5 served it back on read. Since then I publish to more than I read from: most clients need 3-5 relays for reads, and extra connections mostly buy duplicate events and latency. If discovery is what you're after, add an indexer rel...

It can be tough on your client if you’re pulling data from so many places at once, especially if it’s grabbing old events too. Having more relays will mean that you have less of a chance of losing contact with friends. You’ll see a wider world and more people will be able to see you. Dozens I ...