From f0019e366fef813b22d2d55cf7604e20f0a08707 Mon Sep 17 00:00:00 2001 From: Christophe Besson Date: Thu, 1 Oct 2026 13:24:11 +0200 Subject: fix(node): a revoked account is disconnected, not only refused next time A user revocation closed nothing: the denylist stopped the next connection and left the live ones streaming and chatting. Revocations now go through one method that closes the account's or the group's sessions (F-21). Co-Authored-By: Claude Opus 5.5 --- docs/MESHBAY_DESIGN.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/MESHBAY_DESIGN.md') diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md index c443955..8c1f446 100644 --- a/docs/MESHBAY_DESIGN.md +++ b/docs/MESHBAY_DESIGN.md @@ -2161,8 +2161,9 @@ Two verbs on a group, and they are distinct things: | Reversible from the panel | yes | no | The client shows the real state, not a blanket one. **Revocation is honoured by -nodes** and the denylist survives a restart (**H4**); signaling refuses a group that -is not active. +nodes** and the denylist survives a restart (**H4**): an account's or a group's +live sessions are closed when the revocation arrives, not left to run until they +happen to end. Signaling refuses a group that is not active. **Revocation has one door, and it broadcasts.** Only an administrator revokes, and only through `POST /v1/admin/revoke`, which signs the revocation and pushes it to every -- cgit v1.2.3