aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/proposing-and-voting.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:13:39 +0000
committertv <tv@krebsco.de>2026-11-19 15:18:52 +0100
commit841897b79838f97a809356471baf2f41e186cdfa (patch)
tree6fb5e0ac21b69986c87e8d87e87806ff514b451f /docs/guides/federation/proposing-and-voting.md
parent27b76d5748f23a879d9fc82c725a58b514020ef9 (diff)
continuum-party: which places a proposal gives another writer
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`).
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
-rw-r--r--docs/guides/federation/proposing-and-voting.md8
1 files changed, 6 insertions, 2 deletions
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