From 1bbb45bfe7c9c437373aefa08a6a985bc260f520 Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 16:21:09 +0000 Subject: events: the store's summary names the node's party, and whether it votes for it `GET /events` names the party the node is of (`party`, `--store-party`) and whether it votes for it by itself (`votesByItself`, `--store-vote-key`), and so casts a vote by hand (`POST /admin/events/vote`): what a page offering votes through the node asks. --- docs/guides/federation/running-a-node.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/guides/federation/running-a-node.md') diff --git a/docs/guides/federation/running-a-node.md b/docs/guides/federation/running-a-node.md index d903b2d..af16594 100644 --- a/docs/guides/federation/running-a-node.md +++ b/docs/guides/federation/running-a-node.md @@ -62,12 +62,12 @@ alone, so that a party listing many nodes can't be all of a node's neighbours. fork's root. A token is taken by the node that issued it only. Let in those who act for the node, and give a party without nodes of its own a user to put its events. * **The events** (`docs/openapi.yaml`, Events): `GET /events` (the store's ID, its - checkpoint, its heads, how many events it took), `POST /events` (an event, whoever - signed it), `GET /events/{id}`, `GET /events/counts` (what counts), - `GET /events/refused` (what the store refused, and why), `POST /events/fork` (what the - node finds of a fork's root); and its operator's: `POST /admin/events/drop`, - `/admin/events/allow`, `/admin/events/vote`, `/admin/events/fork`. Each answers - `404` while the node holds no store. + checkpoint, its heads, how many events it took, the node's party, and whether it votes + for it by itself), `POST /events` (an event, whoever signed it), `GET /events/{id}`, + `GET /events/counts` (what counts), `GET /events/refused` (what the store refused, and + why), `POST /events/fork` (what the node finds of a fork's root); and its operator's: + `POST /admin/events/drop`, `/admin/events/allow`, `/admin/events/vote`, + `/admin/events/fork`. Each answers `404` while the node holds no store. * **The store API** (`/store`) reads the document, where events are bytes at `_continuum/events/`; what counts is read at `GET /events/counts`. A write through it is refused (`403`): the document takes events and each node's own protocol data -- cgit v1.3.1