Agreed. Not sure what the solution is, though.
The freedom to choose which relays you use is a fundamental principle that we should not abandon, though. Moreover, the outbox model is needed to allow relay selection to remain decentralized.
That means clients are going need to have sensible defaults for new users who don't yet have any relays listed in a kind 10002 or kind 3, so that there is little pain felt immediately upon joining.
We are going to need to have better options for those who want to run their own personal relays, too. Haven is great, but it requires someone technically inclined to run it. We need something like Haven that is click to download, double click to install, and has a GUI for setup and management, and no messing around with setting up a reverse proxy if we expect average users to take advantage of it.
On top of this, we need tools for users to find relays they might want to use that spell out, in plain language, why they would add them to one relay list and not to another.
There are known patterns to be followed: convention over configuration, making the simple easy and the complex possible, etc. It's not rocket science.
For most clients at least. Then there will be more extreme approaches like Primal (can't configure) and others that require you to input everything.
Amethyst relay config is too confusing as it is. We need to be able to pull these configs from somewhere (vendors, paid relays, help sites), whether that's a nostr event or not.
Thread collapsed
