From 91d1bb60cb7a8d92e4e1966dabbcb50a2406c75e Mon Sep 17 00:00:00 2001 From: tv Date: Sat, 7 Nov 2026 22:35:22 +0100 Subject: access: refused once A refused change is remembered by its hash: offered again it is refused without decoding, judging or logging, so is one built on it, and a peer offering nothing else is answered later each time, up to a minute. Auth plan M6 (re-sending). --- docs/access.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/access.md') diff --git a/docs/access.md b/docs/access.md index cc35565..e3dec0b 100644 --- a/docs/access.md +++ b/docs/access.md @@ -232,7 +232,10 @@ longer write as another member; the user a change names is still its node's word In a swarm without a registry, whatever a user would need, any member may. A refused change stays out, and so does whatever builds on it; the node logs it (`Refused a -change`) and lists the last thousand (`GET /admin/refused`). A change whose +change`) and lists the last thousand (`GET /admin/refused`). Offered again, as its +writer's node keeps offering what is never taken, it is refused by its hash, not judged +or logged again, and a peer offering nothing else is answered later each time, up to a +minute apart. A change whose dependencies haven't come yet waits for them. What it doesn't do yet: -- cgit v1.3.1