"... all their followers will continue to get his updates au...

d1a61498f4b1dc26...

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

e9734133468ce581263b9afe332f6df9e35a60f53293d3d2fced5c5337aa026f

nevent

nevent1qqswju6pxdrgeevpycae4l3n9aklnc66vr6n9y7n6t7w6hznx74qymcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcwf5q2f

Kind-1 (TextNote)

2026-03-10T18:54:09Z

↳ Reply to Event not found

e57ba83cb5482e7a1f30f3ff02e8b655ff3a1654eaa004549725c1990f48d327...

"... all their followers will continue to get his updates automatically ..."

Yes, but for this to work and scale in the long-term, Nostr identities (i.e. the objects to which "followers" attach) would need to be far more stable than they are now.

Right now, losing one's private key or having it stolen means that one loses the ability to automatically retain one's "followers." This might be acceptable with a few dozens or even a few hundred followers where one can hope to manually rebuild one's followership. But it won't work for, say, a few hundred thousand followers.

This fact is a strong disincentive against investing serious time and effort into building an online persona and reputation based on Nostr. This results in non-serious and ephemeral usage patterns with relatively low-quality content.

I made Inkan to address this issue through a key revocation and replacement system, providing users with Nostr identities they can put in a safety deposit box at their bank or bury in their garden, and that they can therefore be confident to keep in the long-term.

I'm conscious about promoting a product here. The excuse is that it's relevant to what's being discussed.

Raw JSON

{
  "kind": 1,
  "id": "e9734133468ce581263b9afe332f6df9e35a60f53293d3d2fced5c5337aa026f",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1773168849,
  "tags": [
    [
      "e",
      "0000c130b638313f071f3e50b72949c40f374b4c9636a347e5b8dde0d6084ea4",
      "wss://relay.primal.net/",
      "root",
      "e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
    ],
    [
      "e",
      "e57ba83cb5482e7a1f30f3ff02e8b655ff3a1654eaa004549725c1990f48d327",
      "wss://pyramid.fiatjaf.com/",
      "reply",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "p",
      "e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb"
    ],
    [
      "p",
      "06639a386c9c1014217622ccbcf40908c4f1a0c33e23f8d6d68f4abf655f8f71"
    ],
    [
      "p",
      "f4d5bf322f77a2a15dfc6e5a507e3b675d08af517ea4feb16c19a42f7fa454ce"
    ],
    [
      "p",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ]
  ],
  "content": "\"... all their followers will continue to get his updates automatically ...\"\n\nYes, but for this to work and scale in the long-term, Nostr identities (i.e. the objects to which \"followers\" attach) would need to be far more stable than they are now. \n\nRight now, losing one's private key or having it stolen means that one loses the ability to automatically retain one's \"followers.\" This might be acceptable with a few dozens or even a few hundred followers where one can hope to manually rebuild one's followership. But it won't work for, say, a few hundred thousand followers.\n\nThis fact is a strong disincentive against investing serious time and effort into building an online persona and reputation based on Nostr. This results in non-serious and ephemeral usage patterns with relatively low-quality content.\n\nI made Inkan to address this issue through a key revocation and replacement system, providing users with Nostr identities they can put in a safety deposit box at their bank or bury in their garden, and that they can therefore be confident to keep in the long-term.\n\nI'm conscious about promoting a product here. The excuse is that it's relevant to what's being discussed.",
  "sig": "8fb573f9260ea23fe3f00a1f00f1cc00b31e61a8c5f8f89a89e2af173ac55818a8d58bd5868ffcc678db35d7bf2a29a0c1bc4b4bcd53d178e8ccc2d329bd5a8b"
}