From f44fbf5b93269bb3573e8a2701e70ab0d7613153 Mon Sep 17 00:00:00 2001 From: tv Date: Sat, 7 Nov 2026 22:35:21 +0100 Subject: access: the policy enforced _continuum/access/policy ({"version": 1}) has every node screen every change it receives, on every path changes come in. A policy a node doesn't know stops its writes through the API. GET /admin/refused. Auth plan M6. --- docs/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/api.md') diff --git a/docs/api.md b/docs/api.md index 89da7ba..c2b9cb4 100644 --- a/docs/api.md +++ b/docs/api.md @@ -238,7 +238,7 @@ are each node's own (`--htpasswd`, or its proxy's): `alice` on two nodes is one only where their operators make it so, which nothing checks. `GET /admin/changes` lists them, newest first, with the paths each touched and whether a signature by its node vouches -for it (`verified`, Signed changes); `GET /admin/changes/settings` those that +for it (`verified`, Signed changes), and `GET /admin/refused` those this node refused under the swarm's policy ([`access.md`](access.md), Changes judged on every node); `GET /admin/changes/settings` those that touched what is at `settings`. Every node holds every change, so user names are known to the whole swarm, and so is who wrote what, until a remake drops the history ([`remakes.md`](remakes.md)). -- cgit v1.3.1