Maybe on setup you have two modes - default and paranoid. People can opt into paranoid to get fine grained control but otherwise auto approve within sensible limits.
Less intrusive settings are ones you don’t have to look at at all.
nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac nostr:npub1a7n2h5y3gt90y00mwrknhx74fyzzjqw25ehkscje58x9tfyhqd5snyvfnu nostr:npub1uapy44zhu5f0markfftt7m2z3gr2zwssq6h3lw8qlce0d5pjvhrs3q9pmv nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q how might we design less intrusive fine grained permissions for alby login extension?
Discussion
By auto approve I’m talking about reading notes, signing reactions (if you let it handle keys) and alll the other standard event stuff. For zaps, only prompt if zap is over some threshold otherwise approve. Paranoid mode more controls
A lot of the annoying parts of alby for me right now is having to set a limit constantly. I just want the zaps to work without asking me anything.
Are you referring to the budget feature? Would setting a high enough budget work for you (need to be done once per website, if you fully trust the app) or what is the problem with that?
Agreed. That's what I designed for www.nsec.app
Called by a different name though
They chose to call it "Basic Permissions" and "On Demand" in the final app, which I also like.