By the way, you might be able to speed up the process of cat...

inkan

npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l

hex

817a6346198c21accc2379ae404eac5e13de97bc5942bafa79236d10fa76eb9b

nevent

nevent1qqsgz7nrgcvccgdves3hntjqf6k9uy77j779js46lfujxmgslfmwhxcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsdrfs5nr6trhpxmu97e5dra85g7d2lkc2twu0gkke8058lnx5z5gcdklajr

Kind-1 (TextNote)

2026-08-19T15:47:44Z

↳ Reply to inkan (npub16xnpfx85k8wzdhctang6860g3u64lds5kac73ddjwlg0lxdg9g3su56z6l)

I think that's most likely the issue I pointed out in the note below. You have probably been posting from a client other than https://www.inkan.cc, w...

By the way, you might be able to speed up the process of catching up on the publication of the timestamps by going to

Settings >> Inkan Settings >> Delegation & Timestamping

and on that page switch off and then immediately back on the two toggles that say

"Periodially collect timestamps info from TS Server"

and

"Periodically publish timestamps info to relays".

Switching these toggles off and back on should restart these jobs immediately (otherwise they just run periodically while you are logged in).

Another thing you can try is to switch the "Apply timestamp filter" toggle off, and then go back to the profile page of your master delegator key. I'd predict that the currently missing events will be shown because the functionality that filters out events for which no valid timestamp could be found will have been turned off. Playing with the "Apply timestamp filter" toggle and observing its effect can be useful for getting a more thorough understanding of how Inkan works.

Raw JSON

{
  "kind": 1,
  "id": "817a6346198c21accc2379ae404eac5e13de97bc5942bafa79236d10fa76eb9b",
  "pubkey": "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23",
  "created_at": 1787154464,
  "tags": [
    [
      "e",
      "6bfc8a5aad1668ea8de1f565422d4cbfe800656c2065927d055d148aed2ed101",
      "wss://relay.primal.net/",
      "root",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ],
    [
      "e",
      "1e0b23875b20ba18f5d0b86e7155cfa3d1faa99c319b117cd497e3c5b1ed3803",
      "wss://relay.damus.io/",
      "reply",
      "d1a61498f4b1dc26df0becd1a3e9e88f355fb614b771e8b5b277d0ff99a82a23"
    ],
    [
      "p",
      "199f12c94fe6a2903908c46efcb91190d9993b7380886c98321b59c513dca973"
    ]
  ],
  "content": "By the way, you might be able to speed up the process of catching up on the publication of the timestamps by going to\n\nSettings \u003e\u003e Inkan Settings \u003e\u003e Delegation \u0026 Timestamping\n\nand on that page switch off and then immediately back on the two toggles that say\n\n\"Periodially collect timestamps info from TS Server\"\n\nand \n\n\"Periodically publish timestamps info to relays\".\n\nSwitching these toggles off and back on should restart these jobs immediately (otherwise they just run periodically while you are logged in).\n\nAnother thing you can try is to switch the \"Apply timestamp filter\" toggle off, and then go back to the profile page of your master delegator key. I'd predict that the currently missing events will be shown because the functionality that filters out events for which no valid timestamp could be found will have been turned off. Playing with the \"Apply timestamp filter\" toggle and observing its effect can be useful for getting a more thorough understanding of how Inkan works.",
  "sig": "9281f3ea5bd8dbead27aa8b8ea73848db9b15e491038306f440fbbfc2b34d77950394aea3247c7609441e0e44a3e270fcba4fb0c79a51b52c933bbe6b245fcf9"
}