Nostr Web Client

What if instead of only allow people to use a private key for login / registration, we had a Sign Up / sign in with Google and upon doing that, a key pair is generated for you and emailed to address. You would still have a nostr npub / nsec, but it would automatically back up for you. The user recognizes the social login, and it’s easier to populate information from that option. It would be like a hybrid mode where you keep the old sign up process but on the front end it’s all nostr. Perhaps then you could use that connection to integrate with other traditional services, perhaps with a database attached. So it would be like nostr, but with a benefit of a light database for some efficiency and integrations with minimal info collected.

Dumb idea? Defeats the entire purpose? Thoughts?

Sikto 2y ago

I think nostr wins by being different and there isn’t a need to integrate it with legacy systems. I feel this just waters it down and makes it too similar and why would someone switch to something that is not that different?

Reply to this note

Please Login to reply.

Discussion

mark 2y ago

i think if its limited to signup procedure, it would make onboarding for new nostriches fairly easy.

HoloKat 2y ago

Ty for this perspective

Sikto 2y ago

Ty for always looking for new ways to make the ux more palatable for new users. You’re a huge asset to the community.

I’m not a designer, but as a user, I think the key pair is a feature and helps to differentiate nostr from legacy systems. I don’t think it needs to be “hidden”. I think people just need to be taught how it works. When I first arrived I thought it was amazing that I could take my nsec to any client and my “network” would go with me.