I also agree with your perspective on the user side. I think not only that… but average people are still writing their password as “Password”… so to have them managing a public private key pair seems tricky. Maybe if we can figure out a way for that key pair to auto sync with Apple Passwords or Google Passwords or whatever for the people who don’t use password managers might help. Or maybe create some sort of way of translating a password into a public private key pair so the known UX can still happen. Just some thoughts.
there is no complete onboarding resource for devs. Nostr protocol github does not contain the lessons and context of the thousands of nostr dev hours.
cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 see python feedback package.
On the user side, lmk if you have ideas. My gut tells me no one wants to do homework beforehand about scary topics like public private keypair cryptography. Things should “just work”, and learning should happen by doing.
Discussion
Dope ideas