i understand that Nostr Addresses (NIP-05 IDs) are very useful. i was the very first person to sell them as an identity service provider on nostr. i founded nostrplebs.com in December 2022.
simply put, i think NIP-05 ID aliases defeats the purpose of having a displayable unique identifer as it makes them no longer unique.
what's the end game here?
i have 1 display name. if we allow users to have 100 nostr addresses, then why not have 100 display names too?
it makes zero sense to me. i'm sorry.
It is so that users of multiple services can be identified on each portal uniquely. Such as gamer tags or other name spaces they use in a nip-05 implementation. Sometimes the length of existing nip-05 is not suitable internally when using legacy software that is integrated and unique short names (before the @) are useful on the platform.
I have intentions of launching several portals and a few of them would thrive much better this way.
Also, it allows users to search for these verified aliases without it being the primary display on the profile. It is about enabling more use cases that are not easily enabled now.
it's an interesting use case, but i think it is more negative than positive. for example, it makes it easier for scammers to impersonate someone if you can have multiple nostr addresses. all someone would have to do is spin up a few domains and use a few identity providers and they could have many aliases. some may think the more the better or the more they have, they more legit and that's simply not the case.
to me it sounds like you want to display nostr badges as gamer tags. they were designed exactly for this reason. nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m created them as a method to cosmetically display somemthing on a user's profile. i feel like you should go this route.
anyways, depending on the client, you've always been able to search for non-active nostr addresses. they wouldn't show as active or / valid though.
for example, im still derekross@nostrplebs.com and before that i was @derekross.me. you can search for those addresses on some clients.
+1 for Badges, specially since this seems to be cosmetic in nature
I plan to use badges, but this is about synergy between platforms and users ability to have varied identities for purpose. Not everybody wants their gamer tag to be the same as their public posting identity, and these will already be using the nip – 05 identifiers which have an entire ecosystem of verification and code written to handle them, since the users will be registering a wouldn’t it be good to allow them to utilize that more effectively in the ecosystem. We want to enable more platforms to adopt Noster and embracing varied used cases will help enable that adoption. We want to use standard identifier that are already embraced by users on NOSTR and just extend that capability to be more adaptive for the users and the platforms that offer registration that ties directly to their NPUB.
if you don't want your gamertag to be your public identity, then nostr addresses don't solve that. the identiy is still the same. nostr addresse are just human readble formats of the same identity.
if you're a dick in a video game, i can lookup your nostr address and get your public key. an alias doesn't solve that. a different public key does though.
It is not about anonymity, but division of identity. On Xbox live or psn, you may not want to be Derek Ross, might be bigrossman or w/e. But you may want to be discoverable and verified as both, using the same npub.
My goal is to enable more use cases and adoption.
Basically it would you rather the user be able to use both your service to register and my service to register rather than have to pick one because they both offer different things to the user and with seamless integration via aliases they can pick which one is displayed as their primary identify action on most based portals
That is a fair point, but . . .
It also brings up the key issue about . . . well, keys. It is frictionless to spin up another keypair. Is is NOT frictionless (in most cases) to get a nip-05 from a respected, established, trusted domain/relay/whatever. Sure, you can just abuse the nip-05 services like the spambots do, but, if you note . . . they all come from the same core domains, which . . . would be handy to have to block domains entirely, and I don't see a good way to do that at a lower level that some clients (very poorly implemented) block/mute lists.
Badges are cool, but also useless to me since they are way easier to make and collect than domains.
This isn't an either/or. It is a both/and.
Collecting identities seems odd. Are there any examples where someone would collect different identities on another platform that you have as an example?
Some users want a different id for social, gaming, Pinterest and other utilities because they desire different personal brands, but also users may want nip-05 providers with the same name due to add on features of the registrars that extend their use cases across their interactions on nostr.
We could further limit it down to 10 to 25 aliases in the spec by 100 allows for the network to grow an additional use cases to be invented. I don’t really care if it’s 1025 or 100. I would like to see the ability for users to have the utility along with the providers to have a path to not needing them to use it as a primary identifier on their profile if they desire a specific aesthetic as a user.
Another use case is that if you own or run Multiple Companies, you may want to have a nip identifier for each of the domains related to those companies. Let’s say for your registrar and five other projects that you run, you may want to have the same short name at multiple domains to identify that you’re a good actor for each of those services
Collecting identities is odd . . . to you.
To me, this gives people or groups more options with a simple, ignorable if you don't want to support it, array.
I could say that using one identity across all your stuff is actually, as far as I'm concerned, wet dream of the snoopers charter fans. 😂
Yes. You can collect a decent amount of metadata and use that to corelate an identity, though. That's hard to defend against. But... I am still a fan of various identity for various uses.
I want a verified account that verifies my upcoming nostr portal, nostr gaming project, future podcast, personal website, and other projects I am affiliated with in one npub.
It can show more of a trust across them and unifies the account as I wish. I could do individual accounts as the root domains and brand, but my administration account can be unified.
They can do that now, anyway, and it hasn't prevented any spam at all.
But, for example, if someone has a nip-05 from The Forest and GitCitadel and Alexandria, I, personally, and very reasonably sure that this person is who they seem to be, since I am familiar with all those particular corners of the web.
If a bio displays a bunch of random nip-05s that I am not at all familiar with, it isn't hard to discover that they are junk domains being spun up.
I also think this is another avenue of discovery, which, I think, is going to be more important in the future as more and more relays are spun up for ever more niche communities.
Please forgive me as I am on mobile and mining fiat right now, so I have limited access to resources
