From 7d91c37ec1c606f70ec7a90ce9be4b0aa5c518c4 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 13:50:25 +0000 Subject: peers: what each peer said it speaks and knows, in GET /peers GET /peers shows, of each peer, what it said with its handshakes (SPEAKS): its `knows`, the wire versions it speaks, the oldest and the newest, and the newest revision of the federation it knows; null where it said nothing, a build from before SPEAKS or no handshake from it since the node started. `localKnows` is the node's own. So every swarm, federated or not, shows which builds its nodes run, as far as each heard. `swarm::speaking::shown` shapes it, for GET /events/counts too, whose `knows` is the same; docs/openapi.yaml has it once, as `Knows`. Without the federation feature, a revision reads as one this continuum doesn't know. `Speaking::of` is now used in every build, not only federated ones, which warned of it as dead code. --- docs/operations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/operations.md') diff --git a/docs/operations.md b/docs/operations.md index 97fee26..f64bc13 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -112,7 +112,8 @@ Before 1.0.0, any release may be a flag day; its tag's message says whether it i What decides which builds work together, a build says (`-V` the release alone): the wire versions it speaks, the federation and the revisions of it it knows (with the `federation` feature), and the Automerge it makes documents with. `continuum-party ---version` says the same. +--version` says the same. Of the wire versions and the revision, a node tells its peers +too: each peer's, as far as the node heard, is its `knows` in `GET /peers`. ```sh continuum --version -- cgit v1.3.1