Replying to Avatar Shawn

I’m sorry, I didn’t mean to sound defeatist. I think this is a huge opportunity to improve UX.

I’m encouraged by the work nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft has done with nsecBunker and whatever he was hinting at today:

nostr:note1qmuakk7f6zr3h8x0ng7ryc8rw2f2vjdr2ka74ayvh4lxr4hrk3jswxuqcp

And to be clear, I love the architecture of public/private key authentication. It just needs a little abstraction to make it less threatening. For example, here’s how Apple handles it:

https://support.apple.com/en-us/102195

Apple of course has the ability for deeper integration into the device than normal apps, but maybe we can learn from this.

Look, if someone were to implement Nostr across their entire company, it would need to integrate somehow into their existing IdP. (Active Directory, Okta, SAML, OAuth, whatever.)

They would need an interface to create (or maybe import, or not) their npub and nsec. And maybe change it somehow without losing history. Generic departmental accounts would need to exist where the person using it can’t access the nsec.

And then it needs to be stored and accessed easily when people need to use it. But be able to have their access to the departmental account revoked when they leave the company or even change jobs within the company.

Maybe nsecBunker can help there, but I admittedly haven’t dug into it enough to see where it meets this.

Reply to this note

Please Login to reply.

Discussion

No replies yet.