diff options
Diffstat (limited to 'docs/dashboard.md')
| -rw-r--r-- | docs/dashboard.md | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/docs/dashboard.md b/docs/dashboard.md index 2966c79..2bd126a 100644 --- a/docs/dashboard.md +++ b/docs/dashboard.md @@ -25,9 +25,15 @@ dashboard is open; it ends with the token's lifetime, or with "Log out of this browser" on the login page, or "log out" in the user's menu on the dashboard (its name, top right), which ends this browser's session only. Where the page got in by what it can't end, the browser's password or the proxy's, "log out" is greyed, and -says how instead. The menu's "credentials…" shows the user's keys, to add one (its -`.pub` line) or remove one but the last; under a strict policy, how to sign them anew -(`continuum-signed key-add`); and where its password is: in each node's `--htpasswd`. The page and the login page run their +says how instead. The menu's "credentials…" shows the user's keys, each by its name +and as much of the key as fits the dialog, cut in the middle where it doesn't (its end +and comment always shown, the whole in its tooltip), and `edit` at the right: its name +and `.pub` line in fields, to save, or to delete with the red `Delete` (on a second +click from half a second to 3 s after the first, as in the document box; the last key +only where the user has a password on this node, which it logs in by then); or one +added below; what fails says why where it was asked, to be set right and tried again. Under a +strict policy, it says how to sign them anew (`continuum-signed key-add`); and where +the password is: in each node's `--htpasswd`. The page and the login page run their own script only (a content security policy naming it by its hash), and no other page may frame them. The API listens on localhost unless `--bind-addr` says otherwise; to look at a node on another machine, forward the port (`ssh -L 3000:localhost:3000 @@ -241,7 +247,9 @@ measured. this node knows of them. The browser must reach that dashboard: not one behind NAT, on Tor alone, or plain `http` from an `https` page; the node allows this page's origin as a member's dashboard (`--cors-origins` for others). Subscriptions are kept in the - browser, and handed over with the rest. + browser, and handed over with the rest; going to another node's dashboard, the node + left is subscribed to there (this node itself never is: its links and messages are + the page's own). * **Right-click a node**: its menu: subscribing to its links (or not), and `go to its dashboard`, greyed where the node publishes none, and on this node's own. * **Go to a node's dashboard** (its menu): in this page, where the node publishes one |