aboutsummaryrefslogtreecommitdiffstats
path: root/docs/peers.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-05 03:40:09 +0100
committertv <tv@krebsco.de>2026-11-05 03:40:09 +0100
commit11d098477cfc76da0bc4385635e4c4b7124a9259 (patch)
tree941640ead4d8e80b291780f708a56f8be53a0fe1 /docs/peers.md
parent9f9015a35b591043ebaf6e306f967ffc62cd07f5 (diff)
announce only to those behind
Diffstat (limited to 'docs/peers.md')
-rw-r--r--docs/peers.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/peers.md b/docs/peers.md
index 9ef570b..0f7635e 100644
--- a/docs/peers.md
+++ b/docs/peers.md
@@ -299,7 +299,8 @@ has the changes already sends nothing back, even if its heads differ, as they do
writes go on and newer changes are still on their way to it; nor is a neighbour told whose latest heads, as its
own announcement or STATUS brought them, are this node's: announcements wait 200 to
400 ms, at random, so of two neighbours with the same news one is usually first, and
-the other skips it), and a neighbour that lacks those heads pulls them (it sets them as the peer's heads in its sync state, so Automerge asks
+the other skips it; nor one whose latest heads, as it said them in a STATUS or a sync
+message, have all of this node's in their history: it is as far or further), and a neighbour that lacks those heads pulls them (it sets them as the peer's heads in its sync state, so Automerge asks
for what's missing), if it still lacks them after a round trip to the announcer (at
most 1 s): while writes go on, the newest are usually on their way to it along a
writer's tree, and would otherwise come twice. It pulls from one neighbour at a time