Make nip 05 providers also email providers. I realize this adds a large burden for providers if they want to provide an email client, but they don't necessarily have to do that. I made my NIP 05 (hodlbod@coracle.social) into an email address with an MX record. NIP 05's could do that with users' existing providers.

Lots of sharp edges there, but I really think the right UX is to have the same name for both protocols.

Reply to this note

Please Login to reply.

Discussion

People don't want yet another email address they don't check; I suppose the NIP-05 could just become an email forwarder to the user's real email address though

Yeah, I think the default should be either to forward messages to the user's real email, or an auto-responder that says it's not an email address (or both).

I am wedgesocial@nostrplebs.com

That is both my Zap and email address. It's slick easy to use and how I currently get nonkyc

Embrace the dual protocol single address

Using an email adress (new or excisting) sounds very logic for me. Than the onboarding can become much more normie-proof.