diff options
| author | tv <tv@krebsco.de> | 2026-11-18 12:48:29 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 13:59:42 +0100 |
| commit | d130c0612b4c63f2d30da65ebcc231018c1f2606 (patch) | |
| tree | 8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/guides/federation/building-on-the-api.md | |
| parent | 0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (diff) | |
docs: references to another document's section linked to it
Where a document names a section of another after linking to it
("([`store.md`](store.md), Pinned checkpoints)"), the name links to that
section too, by the id both GitHub and cgit's about filter give its
heading; paragraphs that grew past the width are wrapped anew, links and
code kept on one line each.
Diffstat (limited to 'docs/guides/federation/building-on-the-api.md')
| -rw-r--r-- | docs/guides/federation/building-on-the-api.md | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/guides/federation/building-on-the-api.md b/docs/guides/federation/building-on-the-api.md index 4f37b91..45394ed 100644 --- a/docs/guides/federation/building-on-the-api.md +++ b/docs/guides/federation/building-on-the-api.md @@ -2,14 +2,17 @@ An application on a federated swarm reads what counts at a node and writes as a party. This guide says how, through the client or with code of its own. The formats are the -design's ([`federation.md`](../../federation.md), Events, The policy, What counts). +design's ([`federation.md`](../../federation.md), [Events](../../federation.md#events), +[The policy](../../federation.md#the-policy), +[What counts](../../federation.md#what-counts)). ## Reading `GET /events/counts` is what counts, as the node reads it now: the values at places (`values`), the current version and its rules, each party's keys and nodes, the members -([`writing-and-reading.md`](writing-and-reading.md), Reading). There is no stream of what -counts: read it again when the store's heads change (`heads` in `GET /events`). +([`writing-and-reading.md`](writing-and-reading.md), +[Reading](writing-and-reading.md#reading)). There is no stream of what counts: read it +again when the store's heads change (`heads` in `GET /events`). What a node answers is its word: it may be behind, and an application that must not take it on trust reads the events themselves (`GET /events/{id}`) and checks their signatures, @@ -25,8 +28,9 @@ continuum-party --node http://tv:secret@localhost:3000 --key laptop.key \ ``` It signs on the heads the node shows, records what it signed, and puts it; `again` signs -anew what a move to a checkpoint refused ([`writing-and-reading.md`](writing-and-reading.md), -After a move). +anew what a move to a checkpoint refused +([`writing-and-reading.md`](writing-and-reading.md), +[After a move](writing-and-reading.md#after-a-move)). ## Writing with code of its own |
