Subnostr

Multiple NIP-05s. Inevitable? Valuable? But not part of the standard at present?

My Nostr profile discloses that my NIP-05 is rb@rodbishop.nz.

rodbishop.nz/.well-known/nostr.json agrees with this, and says that my npub is associated with my username.

But many other domains may also make alike claims, and may give certain accesses to me if I am defined in their domain's well-known (whether or not my profile discloses it).

e.g. Ditto will give me access to the community, Teams Relay will give me access to the relay.

I may need all of these (to be me as an individual and also a community member and also a team member).

Is this a desirable use of well-known?

It seems needed for a user to be able to understand and manage where well-known associations exist, beyond just displaying a single NIP-05 field in the profile.

Reply to this note

Please Login to reply.

Discussion

Tony 1y ago

Pointing your domain to your npub is just a step in specifying your “NIP-05 ID”. The second step is “informing Nostr” about your NIP-05. That is done by adding this info to the kind 0 event (metadata).

So when you add the NIP-05 identifier into your favorite client, it modifies the kind 0 event to inform the rest of users that this is your new “Nostr address”. This is why the same address is displayed on other clients (almost) immediately.

Currently Nostr only allows one of such connections and I don’t think adding more will be possible. Pretty sure this would create confusion and issues.

Rod 1y ago

If I am a user who want to access a team or community relay (e.g. Team Relay or Ditto), that relay is going to look for my npub to be defined in the domain's well-known, but I don't think they also need to find a corroborating event on the network. And if not, then that's interesting and is slightly different from the way NIP-05 seems to be assumed to work.