Well, the gitserver itself has a registry. I just know that git requires both a name and something containing an @, and we'd like to eventually not need to ask for an e-mail. And that adds something human-readable to the commit text. We can always use current nprofile data in the display.
Discussion
there is such things as non-network identities using the user@location format, but anyway, the thing is that there is no consensus mechanism for tying names to nostr:npubs anyway... this would actually be a sane use of op_return then you could have the "location" being some code meaning "bitcoin blockchain" i'd sure be fine with spending a transaction to anchor my npub onchain to a name, just needs a scheme for superseding identifiers
Would it be possible to include that in the registration Lightning zap? nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszxthwden5te0wpex2mtfw4kjuurjd9kkzmpwdejhgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszdthwden5te0xgekzumyveshxe3jwgengvt8de38yungdf58wem8v9jxven8v9ekvumpv3nxzumpvesju7re0ghszrnhwden5te0v9j8yefwwd6j7qpq8pudjhdhhp2v8gxnkttt00um729nv93tuepjda2jrwn3eua5tf5sz3h4k8 would probably know a clever way to do something like that.
I'm not wedded to the NIP-05 address. Just seemed like one that most npubs would have or we could give them.
yeah, it is a way to associate a DNS and a name to an npub, that is correct, the LNURL option lacks the npub association, but it has the ability to auth with it
