summaryrefslogtreecommitdiffstats
path: root/docs/MESHBAY_NODE_PROTOCOL.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/MESHBAY_NODE_PROTOCOL.md')
-rw-r--r--docs/MESHBAY_NODE_PROTOCOL.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/MESHBAY_NODE_PROTOCOL.md b/docs/MESHBAY_NODE_PROTOCOL.md
index d03b7eb..cdcc2c0 100644
--- a/docs/MESHBAY_NODE_PROTOCOL.md
+++ b/docs/MESHBAY_NODE_PROTOCOL.md
@@ -1183,8 +1183,7 @@ drop box", which is the ordinary arrangement.
**Nothing in this table widens what the node shares**, and that is the design too.
Adding a directory to a group, hosting a new group over a directory, and switching
a root's `writable` or `removable` flag are done on the node's own machine — the
-desktop application over the loopback API, which asks in a native dialog before it
-shares a folder or opens one to writes, or the CLI — and never over MNP. Until 6.0
+desktop application over the loopback API, or the CLI — and never over MNP. Until 6.0
they were the signed ops `root_add`, `group_attach` and `root_update`. A signature
proves that the operator's key signed, not that the operator meant it: in a browser
that key is driven by code the hub serves (T3), and in the desktop application by a