#asknostr does this make sense to you?
Discussion
No.
Not for me. Too many relays.
The first one group and the second group should be the responsibility of the client because they enhance the customer experience.
Anything that impacts publications and events is better handled by the user. Call it the algorithm. Unless they choose auto pilot and ask you to handle it.
So maybe I can add some hard coded defaults and then let the user change them if they want. really its only necessary to have one or two lookup and fallback relays to get a good experience
As someone who understands this, I would never want to mess with this screen.
If i hard code a few relays for the "lookup" and "fallback" then you wont have too. I've just been trying to get away from hard coding relays
One option to explore might be to set some sensible defaults without showing them, then have a button to ācustomizeā that opens the advance menu.
At least thatās the way Iāll probably explore it in jumblekat
You could also lessen the visual / tech fatigue by making each section expandable and not fully visible by default
this may not be directly helpful to this post, but the most confusing things about how most clients handle relays are the following:
- where did this client get these relays from? my profile somehow? my browser extension? its own hardcoding? discovered from my follows?
- if i change them here and now, will that stick? will it only be for this client or will the change follow me around?
- what is the nature of each "type" of relay category?
- and again because its both important and confusing: if i change the settings on this screen am i overwriting settings for my profile in such a way that other clients will reflect it, or is it just local to this one?!
lack of understanding of this last point is part of the reason people get frustrated about having different experiences in different clients
That's a good point. There does need to be distinction between what relays / settings follow your account and which are just settings for the local client
I'm not sure how to show this without either breaking the settings view into two sections (account settings, client settings) or adding even more description text to the settings which no-one wants
Lol I know, it sucks, right? This is not a you problem :)
Theses bootstrap and fallback relays are actually needed, but the setting can be very confusing for the average user. Since you already build it, keep the interface, but move it behind an "Advance settings", explaining that the default are usually sufficient.
In addition I would by default make this interface read-only, explaining that with this setting defaults can be automatically updated if necessary. The user have to enable the custom version to edit the lists, and should so take care of keeping them updated.
It makes sense to me, but I also don't like it and don't think it would make sense to the average user.
I would hide these settings in an advanced option where users like myself who know what they are doing can still go to change them if we want.
When it comes to their descriptions, you could have a little (i) icon next to the relay category name and then display a toast message when it is hovered over or clicked on with a bit more detailed description of what that category of relays is for and whether it is for noStrudel only, or will update relay lists that may be used by other clients as well. That would keep the interface looking pretty clean, but still allow the user to access the information they need.
On these type of relay lists I go back and forth between whether the description of what they are for should be as easy to understand as possible, or filled with jargon so that only those who actually understand what they are doing will mess with it. š
Profile Finder Relay > Lookup Relay
Catch All Relay <=(?) Fallback Relay