diff options
| author | tv <tv@krebsco.de> | 2026-11-19 13:34:24 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 14:39:54 +0100 |
| commit | 9164ebfe9a4014cbbaaaff90c5a1d722e39457fd (patch) | |
| tree | 9a45156bd4919054939d12c97a19672e92e07b98 /docs/peers.md | |
| parent | 7a5aeb02024ddff71ba60f40913555cd21a633ad (diff) | |
federation: which nodes know a revision, in counts and before a `true`
`GET /events/counts` says, of each node a party lists, what it said it
speaks and knows (`knows`, by node ID): the wire versions, the oldest and
the newest, and the newest revision of the federation it knows, by
number and ID and as people read it, its number null where this
continuum doesn't know it; null where it said nothing, a build from
before SPEAKS or one the node didn't hear from; the node's own as it is.
So the nodes still to upgrade before a revision passes show, every
party's, where before a party's operators could check only their own.
A party's client, backing a proposal that moves to another revision,
warns of every node of any party not known to know it, a line a party
naming each and what it said: once it passes, those stop at it till
upgraded. `next` warns alike, of the revision it moves to, or of the
later one it suggests. A warning, not a refusal: what a node heard is
no proof, and a node not heard from may well be upgraded.
Diffstat (limited to 'docs/peers.md')
| -rw-r--r-- | docs/peers.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/peers.md b/docs/peers.md index c63bebe..d2f822f 100644 --- a/docs/peers.md +++ b/docs/peers.md @@ -99,9 +99,10 @@ Before each HELLO and each HELLO_REPLY, a node sends SPEAKS: the wire versions i and the newest revision of the federation it knows, as its build has them. It stands outside the wire versions, laid out as no build changes, so that a peer on another build reads it too, once that peer reads the node's WHO and ME -([Node IDs and addresses](#node-ids-and-addresses)). A build from before SPEAKS takes it -for a message of another wire version, and logs that once of the peer -([`operations.md`](operations.md), [Upgrading](operations.md#upgrading)). +([Node IDs and addresses](#node-ids-and-addresses)): what each peer said shows in `knows` +of `GET /events/counts`, for the nodes a federated store's parties list. A build from +before SPEAKS takes it for a message of another wire version, and logs that once of the +peer ([`operations.md`](operations.md), [Upgrading](operations.md#upgrading)). Every HELLO carries a random id of the sender's current run, and the HELLO_REPLY echoes it. A reply with another id answers a HELLO from an earlier run (delivered late, or |
