diff options
| author | tv <tv@krebsco.de> | 2026-11-12 05:58:57 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-12 15:26:45 +0100 |
| commit | df766dea6c4d8fd527af323b6ad101c682b9d104 (patch) | |
| tree | 3e5ea23da0761d70502fc71cd222aca1e31602d1 /src/remake/catchup.rs | |
| parent | a4da3a94cb51b893dc259a1741df0071c46e1ac3 (diff) | |
docs: federation: numbers without constraint, names by a decision
What the maintainer answered to the questions the design had left:
* Every quantity of the design is a number of the policy, in one
table with what the design recommends (the times, the limits, how
much a remake's base may lack, how long the root's node lets a claim
wait). The genesis policy sets each, and a decision changes any to
any value: nothing constrains them. The fractions aren't numbers.
* While a user is out, the voters free its names or give them to
another by a decision, whatever `gone` says; a policy without `gone`
has the names wait until a vouch or a decision.
* Nobody is put out by a vote, said where unvouching is, with what
there is against a user that harms within the rules.
* A node keeps the epochs it left for as long as its operator says,
`archiveRetention` at least, and says which; so a node coming back,
or one joining from the genesis root, walks every epoch where an
archive is within reach, and shows where the walk doesn't end at its
peers' epoch.
* Settled, and listed so: who votes, from where an unvouch undoes,
gone for good, first keys by a decision, what the root holds
unsigned. Two questions remain: whether the fractions are numbers
too, and whether a decision gives a user name with its namespace.
future-work.md: an archive of every epoch.
Diffstat (limited to 'src/remake/catchup.rs')
0 files changed, 0 insertions, 0 deletions
