From 3bf93bc192bf362b58b2161ac05da0bb8323bf43 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 9 Nov 2026 17:33:24 +0000 Subject: docs: what is postponed or rejected stays in its own two files Docs and comments outside future-work.md and review-rejections.md say what the code does, and point nowhere else for what it doesn't: the architecture page's map, the transports' forwarders, keys with `/`, a strict swarm's registry, trust.md's "Not yet" (now saying what isn't protected, in a sentence), the topology bench, and the comments of the change benchmarks, capabilities' grantor, tokens, dissemination, refusals and topology. --- docs/trust.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/trust.md') diff --git a/docs/trust.md b/docs/trust.md index 3839958..72a238d 100644 --- a/docs/trust.md +++ b/docs/trust.md @@ -159,6 +159,6 @@ Not against a hostile member, but against honest ones getting in each other's wa ## Not yet -What is left of protecting the swarm against its members, and of keys in browsers, is in -[`future-work.md`](future-work.md): Write protection by checking changes, Read access -beyond sealed values, Keys in browsers. +A member is trusted with what its own node writes as itself: checking changes protects +protocol data and the paths listed as signed, not data at large; reading is protected +only for sealed values; and keys stay out of browsers. -- cgit v1.3.1