People just need to log into https://www.inkan.cc with NIP-0...

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l
hex
b9b55df2e3e1d7c9c190c361c100b52cffb61021234b34c5ee592715c9815febnevent
nevent1qqstnd2a7t37r47fcxgvxcwpqz6jelakzqsjxje5chh9jfc4exq4l6cprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gckyl4gzKind-1 (TextNote)
↳ Reply to Event not found
0a29605ce62cd806c80073bdaa0ef7199371ea809093f54ec68650d8200a1e89...
People just need to log into https://www.inkan.cc with NIP-07 if they want to see the identity and interact with it now. They can also make their own Inkan identities, and others can see them there.
In the future people can build other clients that make these identities visible. But there is no particular rush for these clients to get created. The activities of the identities are already getting recorded cryptographically, and it's just a matter of building clients that make these activities visible, which can happen retroactively.
So what I mean is, there is lots of time to get other people to participate in the system. The sooner the better, I guess, but it's not the sort of thing that dies if it's not an immediate hit right after launch.
In the meantime, holding the identity doesn't in any way interfere with my everyday use of Nostr. The thing that happens in the background is that my activities on Nostr get attributed to the identity, so I get to keep these activities as part of the identity even if my current key is leaked or lost.
Raw JSON
{
"kind": 1,
"id": "b9b55df2e3e1d7c9c190c361c100b52cffb61021234b34c5ee592715c9815feb",
"pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
"created_at": 1781136676,
"tags": [
[
"e",
"f9901260bc194e772513aa63bc4c5e4696eaaad9168d08f4d547c18e46eae264",
"wss://cyberspace.nostr1.com/",
"root",
"577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd"
],
[
"e",
"0a29605ce62cd806c80073bdaa0ef7199371ea809093f54ec68650d8200a1e89",
"wss://relay.damus.io/",
"reply",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"p",
"577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
],
[
"p",
"930ccef12372dd2f16057cfc54f0dbd94335d8b51b4e2737236b00cab718fcd9"
],
[
"p",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
]
],
"content": "People just need to log into https://www.inkan.cc with NIP-07 if they want to see the identity and interact with it now. They can also make their own Inkan identities, and others can see them there.\n\nIn the future people can build other clients that make these identities visible. But there is no particular rush for these clients to get created. The activities of the identities are already getting recorded cryptographically, and it's just a matter of building clients that make these activities visible, which can happen retroactively.\n\nSo what I mean is, there is lots of time to get other people to participate in the system. The sooner the better, I guess, but it's not the sort of thing that dies if it's not an immediate hit right after launch.\n\nIn the meantime, holding the identity doesn't in any way interfere with my everyday use of Nostr. The thing that happens in the background is that my activities on Nostr get attributed to the identity, so I get to keep these activities as part of the identity even if my current key is leaked or lost.",
"sig": "4c592a9d0e9e93d42eb1909f7457d94efaab4a3f135c78d6c1016736a6f5767be99eb48e13677f52b25b785c673cf851ccbe5727dbdefb3997a245f5f467ad5d"
}