From 841897b79838f97a809356471baf2f41e186cdfa Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 14:13:39 +0000 Subject: continuum-party: which places a proposal gives another writer MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Rules go by first match, and `{party}` matches only the names of the version's parties: admitting a party named as a segment of a place, or changing the rules or their order, moves who writes the places below it, and what their writer wrote there counts no more once the version passes. Nothing said so: a proposal showed only its fields' changes. `client::writers` names, of the places holding a value, those whose writer a version changes, as `place: before -> after` (`nobody` where no rule gives it one). `continuum-party proposals` prints them under each proposal's changes (`who writes …`), and a fork's check does for the fork's version (`writers` in POST /events/fork). The guides and federation.md say so; row 72 is tested (`federation_attack_72`). --- docs/guides/federation/forking-and-following.md | 7 +++++-- docs/guides/federation/proposing-and-voting.md | 8 ++++++-- 2 files changed, 11 insertions(+), 4 deletions(-) (limited to 'docs/guides') diff --git a/docs/guides/federation/forking-and-following.md b/docs/guides/federation/forking-and-following.md index dafa974..4890a61 100644 --- a/docs/guides/federation/forking-and-following.md +++ b/docs/guides/federation/forking-and-following.md @@ -57,16 +57,19 @@ continuum-party --node http://lass:secret@localhost:3000 check fork-root # its heads lack 0c7e… # its version changes: # changes: "3a90…" -> "b41f…" +# keys.euer: {"keys":["ssh-ed25519 AAAA…"],"since":0} -> - # keys.makefu: {"keys":["ssh-ed25519 AAAA…"],"since":2} -> {"keys":[…],"since":5} -# nodes.lass: {"nodes":["continuum:9c07…"],"since":0} -> {…,"since":5} +# nodes.euer: {"nodes":["continuum:3b1e…"],"since":0} -> - # number: 4 -> 5 +# who writes home/euer/hosts/x: euer -> nobody # makefu's keys: ["ssh-ed25519 AAAA…"] here, ["ssh-ed25519 AAAA…"] in the fork ``` Whether it builds that root at those heads; what it took that the heads lack (neither among them, in their history, nor above them), which the fork doesn't hold; what the fork's version changes of the one current at those heads, field by field, its rules and -their order among them, which say who writes where; and, party by party, the keys the +their order among them, which say who writes where, and the places holding a value whose +writer it changes; and, party by party, the keys the fork's version gives otherwise than the party had at those heads. A node that doesn't hold that history takes the root on its operator's word, who names the fork by its ID: compare that ID whole, as a founder trying versions can steer its first few digits. diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index 330d670..f052276 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -157,8 +157,12 @@ curl -s -u tv:secret localhost:3000/events/counts | jq .proposals # "proposals":["c41e…"],"votes":["5a77…","e019…"],"yes":["tv"]}} ``` -The client shows the same, why it backs one not, by the federation it knows, and what -each proposal's version changes of the current one, field by field and party by party: +The client shows the same, why it backs one not, by the federation it knows, what each +proposal's version changes of the current one, field by field and party by party, and +the places holding a value whose writer it changes (`who writes names/wiki/a: tv -> +wiki`): admitting a party named as a segment of a place is, or changing the rules or +their order, moves who writes there, rules unchanged in the first case, and what was +written there counts no more once it passes: ```sh continuum-party --node http://tv:secret@localhost:3000 proposals -- cgit v1.3.1