diff options
| author | tv <tv@krebsco.de> | 2026-11-14 03:16:56 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-14 03:16:56 +0000 |
| commit | 2b13313ad0ea46c0dd211a54120c294beb4501fa (patch) | |
| tree | 88b20897c68cc016cd5207453635b9226b3be6c2 /src/swarm | |
| parent | 86e5a91fd0c014cd1642f95f87e37117d40af784 (diff) | |
federation: operator actions, writers past cuts, caught up, fork bases, relays
- What an operator says, listed with each action named where it is used:
rejoin, choose (two remakes decided, or a walk through the archives
that ends elsewhere), follow (a node that waits past `remakeAge`), back
(refusing the remake), fork, refusing and bounds, dropping what the
others refuse, accepting a check of itself that differed, taking what
was put off. Tokens from the nodes `--token-nodes` names.
- Where a cut takes a thief's node's writers off a user's count, below the
limit again, every node takes what it put off for that user, nobody
acting. A writer counts for the user it was counted for until such a cut.
- Caught up: the heads each peer kept had when the node reached it, as its
first STATUS says, or `witness` passed; a peer that keeps sending keeps it
silent no longer.
- A fork's base: rule 4 takes its proposer's node's record, without votes;
it refused it unless two thirds voted for the fork.
- Relays: each node's configuration in a federated swarm; nobody may write
`_continuum/relays` plain.
- In the open: `GET /registry/users/<name>` shows which root's node keeps a
user in past an unvouch or a cut, and which roots' creations contest a
moved-in user's first keys.
- A carry record names what counts through a cut, as through an unvouch.
Two rows move to the stage of policies changing: a limit lowered and raised
again, a stamp between.
Diffstat (limited to 'src/swarm')
0 files changed, 0 insertions, 0 deletions
