All fair points, but still, you're only looking at the cases where users type nsecs into untrusted apps, which is IMO orthogonal to whether a legacy solution can or should try to be built out on nostr. We should teach *users* why nsec security is important, not chill *devs* trying to build out the ecosystem. I use amethyst; never gave it any of my nsecs. Why not nostr login on proton too?

Replies (3)

Also, you gave something your nsec if you're using Amethyst to sign notes. My opinion is that I should have the option to give NOTHING my nsec ever. I don't see how that's possible right now and would discourage building critical services on Nostr until we fix that. I don't think Proton should allow it for security reasons. That's my whole point.
The current security model should be entirely changed before we encourage more people to use more things on Nostr. Otherwise, almost everyone is just going to copypasta the same nsec into everything that asks for it and get rekt at some point. We need a new default.
Something needs an nsec at some point unless you're doing your cryptography with pen and paper! I use Amber as a signer (on GrapheneOS with network permissions disabled for that app) I hear ya though, you're definitely not wrong about nsec security! And I was bit off about PW/nsec equivalemce ๐Ÿ™„ Just thought as an amethyst/amber user, it was an odd reaction to @Vitor Pamplona s suggestion, because I'd love to conceivably install & open proton, click a button, sign an event in amber (or whatever), and get logged into my (maybe just newly created) proton account. ๐ŸŽ‰
โ†‘