Users shouldn't have to touch this until they're ready. They will have to learn to become comfortable with the existing "home profile." configuration.
This should also make it easier for people transitioning their relay configurations as they evolve along the protocol. Over time we are only exposed to more relays. This allows us to grow our horizons without committing our npub to a bunch of new relays when we discover something new.
For instance, if I meet 30 users who each have their own relays. I want to retain my relays as they are set up now. All of these friends' relays could be added to a new profile, which generates a new, local feed. I can then browse these feeds, and rely on the same profile for "relay selection" when commenting on those relays.
I have only designed this concept around client-local kind-1 participation. All other kinds would require significant reworks. But I don't see kind-1 relevance going anywhere. This allows the ecosystem to expand within our apps, which can create communities that build out their own specialized clients, with their own similar mechanics.
The graphic may be misleading in this way, because I have included all of the traditional green toggle options besides the relay names. These can instead only be "global" and "remove", which means no support for dm's etc. My intention was not to support the bulk of these features, as "core relays" should always be managed through existing configuration settings like the "home profile", or other settings within amethyst.
In my mind this formally extends the "local relays" section within our existing relay settings page.
Ooo good point. I often wanted to experiment with alternative relays.. but didn't want to mess up my main settings.
Not sure about the effort / value ratio as I can't estimate required effort.
Thread collapsed
