I don't like this idea of nostr apps priming you to replace your NIP-05 during the onboarding
clicking that inconspicuous checkbox will replace your NIP-05/Nostr address
#ux #darkpattern
Discussion
Strongly agree. I’ve seen this more than a few times.
wait till clients start gatekeeping features because you are not using their nip-05
soon
I hope not! Scary thought.
Is there any reason that a Nostr profile can’t have multiple NIP-05s? Multiple domain verifications?
You can have multiple set up but the one in your kind 0 metadata event (your profile data) is the only one that clients pay attention to.
I can think of multiple reasons that I’d want to have multiple set up and working.
Do you think it would be technically possible to have that metadata be one or many instead of just one? Or was it intentionally limited to just one?
I'd actually love to hear more about the reasons for having multiple NIP-05 verifications. For the most part, I think NIP-05 is sort of a shitcoin. It's fairly meaningless and lives outside the actual protocol so it can only sort of be trusted.
It's not technically possible to list multiple, I mean, I guess you could put multiple values in the one NIP-05 field but most clients would just puke when trying to understand it.
I think of NIP-05 basically like how attestations worked in the original Iris (cc nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk ) except it can also help your account be to be more discoverable.
Maybe I get an NIP5 from my church, my gym, and my hometown.
Each of these would not only attest my profile as someone that is “known” and (at least somewhat) trustworthy, but it would also help to increase the findability of my profile.
Now it could be that this is better solved by a different method and NIP5 should just go away. Maybe this can be solved by my church, gym, and hometown each just running exclusive relays (write for members, read for all?) and NIP5 usernames aren’t needed?
But if someone can know me by multiple usernames, I think that does help with the discoverability aspect.
"Post this as my new Nostr verified Id - NIP05" is a tiny change but changes the entire meaning of the checkbox!
To be fair, localization in a startup open source app can be tricky though...
Not at all. Where is that exchange and dns happening?
What benefit does a client receive by having you use their domain for nip-05?
Perhaps advertising, getting there name out there. And possibly this, too:
What exactly is the distinction here? (Not techy)
I agree. I had the same problem.
It’s a poor attempt to streamline the onboarding process.