summaryrefslogtreecommitdiffstats
path: root/docs/USERGUIDE.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/USERGUIDE.md')
-rw-r--r--docs/USERGUIDE.md9
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md
index e92f6bc..d631804 100644
--- a/docs/USERGUIDE.md
+++ b/docs/USERGUIDE.md
@@ -394,7 +394,9 @@ resume.
**Desktop application only.** A film playing in the application can be sent to a
cast-capable TV or dongle on the same network: *Cast to device* in the player,
-pick one from the list.
+pick one from the list. Devices appear as they answer, usually within a couple
+of seconds; the search carries on for a few more, for a TV that is still
+waking up.
The application decrypts the film and relays it to the TV itself, over your LAN.
The TV is not a group member and holds no key — which is also why the relay's
@@ -435,6 +437,11 @@ list you build yourself with invitation codes. Two things follow from that:
| **The CLI**, over SSH | no browser needed, and it works while the daemon is stopped |
| **A paired browser** | the group's Settings and Members tabs, and the Node page in the desktop application |
+Sharing is decided at the node. Adding a directory, and switching it read-write
+or removable, work only on the machine running the node — the desktop
+application, or `meshbay-node root`. From any other browser the group's
+Settings tab still lists the directories and their switches, read-only.
+
On a headless server the CLI is the only path, and it covers everything you
need to run a group. One gap is known: removing **one** device of one member is
only doable from the interface (§7). Start with: