NIP-39: External Identities in Profiles
Nostr protocol users may have other online identities such as usernames, profile pages, keypairs etc. they control and they may want to include this data in their profile metadata so clients can parse, validate and display this information.
This is the only true verification that we have.
IMO, more Nostr clients should support displaying NIP-39 on profile pages. At this time I believe it's only Amethyst that supports this NIP. This NIP is almost 2 months old and hasn't gained a lot of support. Why? Which other services should be added to this NIP? Keybase seems like an easy addition. Others?
Derek Ross
npub18a…tp424
2023-05-01 19:02:40
Author Public Key
npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424Published at
2023-05-01 19:02:40Event JSON
{
"id": "c86f0e3f9286c81b0fd4436b0dfc95f73ec4572c3fe481e8769a062d14ef44d5",
"pubkey": "3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"created_at": 1682967760,
"kind": 1,
"tags": [],
"content": "NIP-39: External Identities in Profiles \n\nNostr protocol users may have other online identities such as usernames, profile pages, keypairs etc. they control and they may want to include this data in their profile metadata so clients can parse, validate and display this information. \n\nThis is the only true verification that we have. \n\nIMO, more Nostr clients should support displaying NIP-39 on profile pages. At this time I believe it's only Amethyst that supports this NIP. This NIP is almost 2 months old and hasn't gained a lot of support. Why? Which other services should be added to this NIP? Keybase seems like an easy addition. Others?\n",
"sig": "751cdc7f98f1913104f0b10072083fd04d9d7c3e5a0f3f903a7a4e734d319ac2c770c877ba39516f37228c8fb43ba9c162de73dcde2dd35f055a4c3d79915852"
}