summaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 17:26:53 +0000
committertv <tv@krebsco.de>2026-11-18 18:31:11 +0100
commit598366b03679eac9d04f32d9194f3ba4ba9c3da8 (patch)
tree91620955243fa081fdd0365fb76c8aca0ba4288c /docs/guides
parentf261a80b88c1fb640f4c892934809e15a7e05a95 (diff)
store: a drop refuses whatever writes what a dropped event writes
A fold may say what an event writes that others may write alike (`Fold::writes`): of the federation, a version event's version. A node whose operator has it drop such an event drops the taken events writing the same with it, and refuses any writing it from then on, whoever wrote it anew: of a version, it takes no other version event naming it and writes none itself, though it holds the votes that passed it. The node keeps what each dropped event writes in its store file, across restarts; allowing one of them takes them all back. Row 51 of the federation's attacks has its test, and waits no more.
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/federation/refusals-and-drops.md15
1 files changed, 9 insertions, 6 deletions
diff --git a/docs/guides/federation/refusals-and-drops.md b/docs/guides/federation/refusals-and-drops.md
index c4566e3..b32a819 100644
--- a/docs/guides/federation/refusals-and-drops.md
+++ b/docs/guides/federation/refusals-and-drops.md
@@ -21,7 +21,7 @@ curl -s -u tv:secret localhost:3000/events/refused
```
* `own`: refused by what the node took before.
-* `dropped`: dropped by its operator.
+* `dropped`: dropped by its operator, and version events naming a version among them.
* `refused`: every other, with its kind and why: `none` (none of the federation's events,
or larger than it allows), `judged` (refused at its history), `builtOn` (built on
`on`, refused), `notAbove` (not above the checkpoint's heads, as a move refuses it).
@@ -49,9 +49,11 @@ curl -u tv:secret -X POST -H 'Content-Type: application/json' \
# {"dropped":["5f19…","a03c…"]}
```
-It answers what it dropped, in the order taken. From then on the node refuses those
-events from whoever brings them, writes no version naming a version among them, though it
-holds the votes passing it, and keeps so across restarts. Not what its checkpoint keeps
+It answers what it dropped, in the order taken: those named, version events naming the
+version one of them names, and what is built on them. From then on the node refuses those
+events from whoever brings them, and any version event naming a version among them,
+whoever wrote it anew; it writes none itself, though it holds the votes passing it, and
+keeps so across restarts. Not what its checkpoint keeps
or holds by ID: every event after it builds on that. A move to a checkpoint is undone
only by a checkpoint its operator pins (`--store-checkpoint`).
@@ -62,8 +64,9 @@ curl -u tv:secret -X POST -H 'Content-Type: application/json' \
--data '{"ids": ["5f19…"]}' localhost:3000/admin/events/allow
```
-takes back what the node refused of its own, or dropped, among the events named, and
-what was refused for building on them: they are taken again where the store takes them,
+takes back what the node refused of its own, or dropped, among the events named, the
+version events dropped for naming the version one of them names, and what was refused
+for building on them: they are taken again where the store takes them,
as it reads its document again. It answers `204`.
## When to