diff options
| author | tv <tv@krebsco.de> | 2026-11-19 01:48:57 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 03:19:19 +0100 |
| commit | 101080b8a62709cd2606dece086f959781bdf38f (patch) | |
| tree | 618e9acdd6e5d311ece2cf5b213432257c31bc39 /src/lib.rs | |
| parent | e0075264e9efdd4c8a32290c0d5643e7f48bfb14 (diff) | |
vote: a follower copies no false, lapses nothing others back, waits after a move
A node following a party (`--store-follow`) handed it more than the text said:
* it copied the party's `false`: one party's nay freed bound followers, and its `true`
shown to some and its `false` to the rest passed a checkpoint at one history and made it
dead at another. It copies the `true` alone now, on any version too;
* a checkpoint lapses every other proposal: the followed party ended any proposal it
disliked by passing one. A node follows a checkpoint only where no proposal that changes
more can still pass that someone but its proposer backs;
* nothing bounded how often the store moved, so fresh events could be left out of every
checkpoint; and a node just started held nothing for a while, so the voters' rule kept
nothing. A node backs, and proposes, a checkpoint only once its store held its
checkpoint, or ran, for a while (`--store-back-after`, ten minutes unless set), by itself
or by hand.
`federation.md` says what following hands over, and row 58 what a follower on any
version copies; the guides and the example say the rest.
Diffstat (limited to 'src/lib.rs')
| -rw-r--r-- | src/lib.rs | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -70,6 +70,7 @@ fn voter(args: &config::Settings) -> Result<Option<federation::held::Voter>> { propose_events: args.store_propose_events, propose_every: args.store_propose_every, held_for: args.store_held_for, + back_after: args.store_back_after, }, })) } |
