Correct. And in addition to this, clients should consider supporting a large pool of known relays and randomly assign them to new users. Then, allow users to go in and make changes, adding and removing relays at their leisure and using WoT indicators to help them navigate relays.
Discussion
Love this idea.
we are so past needing to randomize like this, we have nip66 rolling out. you can run a nip66 agent to advertise your favorite relays and tag them with #wot or etc so people can search by tag or geocode or type of relay.
this doesn't help brand new users that don't understand technology. a client still has to choose relays for them one way or another. suggesting relays for them to use is still aiding them in making this choice.
It does though, if clients implement support for nip-66. Then users just type the domain where relays are hosted and they have a list of the public relays. This is as hard as typing "mycelium.social" into a box and clicking the relays you wish to browse regularly. Right now anyone can do this in a web browser without instructions.
The "hard part" is for clients to adapt to offering collections of relays, which Jumble (and another new client) have started doing, but those also don't support nip-66.
Jumble already supports NIP-66 🫡
My mistake! Looking good!
You clearly don't understand brand new users or non technical people. They don't know relay names. They don't even know what relays are! This makes everything more complicated for your average non technical user. You're talking about advanced options for advanced users.
That depends entirely on client implementation. These processes can be essentially automated by the community. Clients can become very flexible to cater to non-technical users.
If the client has popular/trending relays advertised and accessible at the click of a button, it's a non-issue. The same way clients recommend relays now.
This sounds highly technical
This is actually a brilliant idea 🤔