diff options
| author | tv <tv@krebsco.de> | 2026-11-16 04:14:37 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 04:14:37 +0000 |
| commit | 2b03f0e2d13774a5a455ec0136afe384e7b28658 (patch) | |
| tree | 38c7dc81b3a7ff90320ff6e2fff9bc4f3e71962a /docs/federation.md | |
| parent | 3b4b0ef9ad295b358023dd659caf3f14e950a514 (diff) | |
federation: what a node's API users may have it commit
Without a user registry, every user a node lets in may do everything,
and `--protocol-writers` say who writes protocol data; what of that held
in a federated swarm the design didn't say. Whoever a node lets in may
have it commit what the rules take, envelopes and the node's own
protocol data; `--protocol-writers` names nobody.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/federation.md b/docs/federation.md index ed36660..e976067 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -224,6 +224,9 @@ node picks its own relays, and some of its neighbours by party (Nodes). Nothing policy is read of the rest. A member's change carries its node's signature, as signatures are required in a strict swarm. A party logs in to its own nodes as its operator sets up, and a node takes tokens only from the nodes of its own party (Nodes). +Whoever a node lets in through its API may have it commit what the rules take: +envelopes, whoever signed them, and the node's own protocol data; `--protocol-writers` +names nobody in a federated swarm. ### Changing the policy |
