These are very valid point. Managing keypairs and setting up wallets are still big pain points.

Reply to this note

Please Login to reply.

Discussion

yeah, I'd go further to say that the actual setup of getting an npub keypair and wallet is easy, but the ongoing maintenance and security of them is more tricky.

Integration of wallet to client is finicky most of the time, and stuff like NIP-05 verification is very much seen as extra steps after sign up, rather than part of the initial sign up process.

Then there's the whole thing about setting up relay lists...

I don't see it as difficult. I just put them in my password manager (KeePassXC).

Done -- except I have my password manager file saved in a couple places for redundancy.

Ifyou're already here you've figured it out. We should ask how we can get people who don't want to figure it out here.

How do you manage yours? I really don't know what others do. I'm not sure what the standard practice is.

But maybe when clients provide people an nsec, they should make a practical suggestion rather than only saying "don't share your nsec with anyone else." Maybe they should add something like, "One popular way to save and protect your secret key is to use a trusted password manager, such as...."

But then I dont know how many normal people are familiar with password managers. I only started using them during COVID when I become privacy conscious.

I don't have easy answers. I'm still working on getting people to ditch SMS messages for FOSS encrypted messengers.

When people don't care about commonsense privacy, they don't care to make any extra effort regarding messengers, emails, crypto, or social media. They're products of the system.

Check out something like nostr:npub1am3ermkr250dywukzqnaug64cred3x5jht6f3kdhfp3h0rgtjlpqecxrv7 where you don't ever have to expose your nsec to clients to authorise usage.

nos2x extension from nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 for desktops, as another example.