diff options
| author | tv <tv@krebsco.de> | 2026-11-15 16:47:46 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 16:47:46 +0000 |
| commit | f751f411e954001c124afa1e3591d10094df15d7 (patch) | |
| tree | ff680cf67f0198c8e97d645ff8dea21a55877499 /src/api/auth.rs | |
| parent | af120b87c42ca56f69bbe6f8d27c023919742430 (diff) | |
rules: nothing added to the time before a swarm turned strict
A swarm turned strict by writing the policy into it kept the time
before open: a change whose history lacks the policy's change is
judged by the policy then, none or one that isn't strict, needs no
signature there, and is taken whenever it comes, from any member. With
values read by `seq`, an envelope planted at that time with the
highest `seq` there is can never be followed: a ban, a user, a
declaration, for good.
Once a document's policy is strict, a change written under one that
isn't is refused, received or held, unless it is in the history of the
change that wrote the policy the document reads (`store::written_by`).
A node that holds one beside that change, taken before it came, is
told so by any peer that refused it (REFUSALS), judges it again, now
refuses it too, and drops it with what builds on it, as for any change
it took unjudged. A swarm strict from its genesis change has no such
time; one whose policy isn't strict judges as before.
Diffstat (limited to 'src/api/auth.rs')
0 files changed, 0 insertions, 0 deletions
