aboutsummaryrefslogtreecommitdiffstats
path: root/src/access/bans.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-15 20:25:37 +0000
committertv <tv@krebsco.de>2026-11-15 20:25:37 +0000
commit6ae5da042629d085a2410bcca68a4d697a44854a (patch)
treee22006a230c170f289027dba6d33a3fa6bba3669 /src/access/bans.rs
parent767364b2906cacc15699fead626b552617aff111 (diff)
federation: started by its genesis change; votes kept across a remake
A federation starts with a swarm of its own, its genesis change writing the federated policy and the first version: nothing is from before it, so the time before, the federating change and values from before go, and nothing writes the policy's place after the genesis change. A running swarm doesn't become federated; that is left as a road not taken. A remake replays a party's votes before its key sets where neither saw the other, so a vote counts as cast across a remake too; a party that wrote two key sets at once is answered as one voting twice. A version is replayed in one change with the keys it sets, and a replay holds for any base. A `null` the epoch's first change holds goes only at a remake, and housekeeping deletes one only where this epoch's history holds what it covers. A node is a member while the party its own entry names lists it; another party's list does nothing. A proposal counts as written, like a vote. A fork is named by its first version and the heads it names, in its genesis change; `went/` says where to those who follow. Leftovers: the unsigned key envelope's meta; "can bring back" reaching deletions; the first link checked against the place as the deletion leaves it; "is left out"; the attack rows, renumbered.
Diffstat (limited to 'src/access/bans.rs')
0 files changed, 0 insertions, 0 deletions