aboutsummaryrefslogtreecommitdiffstats
path: root/docs/dashboard.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/dashboard.md')
-rw-r--r--docs/dashboard.md14
1 files changed, 11 insertions, 3 deletions
diff --git a/docs/dashboard.md b/docs/dashboard.md
index be57603..54aefa7 100644
--- a/docs/dashboard.md
+++ b/docs/dashboard.md
@@ -152,9 +152,17 @@ it makes them run faster or slower (0.1 to 0.9 map units per millisecond, 0.3 at
first: a link of 200 in about 0.7 s); both are kept in the browser. A picture
of the traffic, not a record of it. A subscribed node's messages with its peers run
along its links too, from its messages of each 2 s (read from it with the page's token,
-as its links are): those with this node are drawn from this node's counts, and between
-two subscribed nodes from what the sender sent, so each message once. Links between
-other members show none.
+as its links are). Each message runs once, as it left, from its sender where the page
+reads the sender (this node's counts, or a subscribed node's messages): so it runs the
+way it went, also where it never arrived. Only a message from a node the page doesn't
+read runs as it arrived, from its receiver's. Links between other members show none.
+
+Where the page reads both ends of a link, what one sent the other should count
+received: a message sent and not received within 5 s makes the link breathe red once,
+its tooltip saying how many didn't arrive. Every kind counts but the paths and
+identity layers' (PINGs, WHO), which this node counts under addresses, not nodes; a
+tick of a subscribed node's messages that came short (more than 500 in 2 s) starts the
+count afresh, so it never takes what it didn't see as lost.
`messages: dots` after the sliders switches to `messages: flash`: each message crosses
its link as fast as it did (half the link's round trip, as the map has it; 50 ms where
none is measured), a streak widening to its head, which then draws back into where it