That's the issue, clients shouldn't just all connect to the same handful of relays, they should be able to find the best relay for a particular query and user
The painpoints would be much more pronounced if nostr was 1000x bigger, right now everything works because we are very smol
Already run into issues on amethyst where notes aren't displayed because it's not on a relay I've pre-ser, if it was able to find the relay that note was on, it would be much better
Imho
Default settings in clients are a huge piece of this. Doesn't matter how decentralize-able nostr is if clients push users toward centralization. I for sure see the benefit of outbox enabling clients to find where a note exists, but I don't think it's a silver bullet. I'm really curious about the gaps it leaves in user experience. Not everything works well in a decentralized manner. Search and discovery is one of the first ones that comes to mind.
Ok ok, i'll be serious for a moment. So, with gossip, all you need to do to startup a new gossip client is give it ONE relay. So if there is a relay, that is curated to be a good onboarding relay, you just point a client at that relay.. From there, it will discover all the rest AND give users a good global feed to start with. No brainer.
What about redundancy of user data? One of the selling points of nostr is knowing that if a relay goes down, or if a relay operator decides to shut down their relay for good, that my data exists on other relays. I don't think you could convince me that my notes only should be on one relay.
you could give it two relays. Basically, you should be able to give your friend an onboarding link to a client, and that client will startup with the relays you gave to your friend. That way, they have a less than zero chance of sticking around. Right?
Thread collapsed
With gossip, your notes don't just exist on one relay.. But the onboarding relay can have a combination of your notes, notes you've replied to, your friends, etc.. Gossip can still publish to all relays if you want, you can even set it up with blastr. It works.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed