Is automatically logging in if nostr extension is found a UX antipattern? I've read that some people find it annoying, what are your thoughts? #nostrdesign
Discussion
I dont like it
There are some similar UX notes for webln https://www.webln.guide/building-lightning-apps/best-practices (Note: WebLN still needs a proper public spec)
Maybe it would be good to add some suggestions as an appendix to NIP-07?
I think only primal does it currently. I like it because I switch between accounts often (using alby). I run into issues with apps because I am logged in with a user but have a different private key selected in alby.
I prefer it when the webapp ask first.
At least the first time it gets visited.
It should probably be a user choice. I would only auto log in if they click log in but not from the moment they land on the page.
It’s one thing I like about using the nos2x extension. If I authorize something “this time only” then I know it’s going to prompt me again. If I select to always allow, then I’m not surprised when I’m logged in the next time I visit the site.
This is is an abstract condition, if the app has the proper extension permission the user is virtually always logged in. The question is, what should the app *do* with this power? Asking for resource intensive actions (ex. download a lot of data) or expose the user visibility/actions (set a status, push a config, etc) after an interrupted session would be a nice touch.
Of course we can use the login concept as a general permission switch.
A good and easy solution is to actively and prominently (ex. a modal) ask the user to enable the login status after an expired (X hours) session.