diff options
Diffstat (limited to 'docs/USERGUIDE.md')
| -rw-r--r-- | docs/USERGUIDE.md | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md index 7242dc2..8a55928 100644 --- a/docs/USERGUIDE.md +++ b/docs/USERGUIDE.md @@ -742,6 +742,11 @@ player consumes it a segment at a time. Segments are 256 KB and the web client keeps 24 outstanding, so roughly 6 MB is in flight whatever the film's length. A client that sends no credit count gets the old unpaced behaviour. +**Closing the viewer stops the stream.** `stream_stop` tells the node nobody is +watching, so ffmpeg is killed and its transcode slot released at once. There are +two slots; before this, leaving a video held one for the two-minute credit +timeout, which is what made the next video answer "server busy". + **The player drops what has been watched.** A SourceBuffer is not a file: browsers cap it and refuse the append that goes past, so anything more than a minute behind the playhead is evicted. A segment refused for want of room is retried rather than @@ -826,6 +831,29 @@ If the keystore password is not stored on the node (`unlock_mode = "secure"`), a --- +### Where a node is, in the administration panel + +The **Nodes** tab lists every registered node with two addresses, and the +difference between them matters: + +- **Seen from** is the address the node's announcement arrived from. That request + carries an Ed25519 signature over a fresh timestamp made with the node key, so + the address belongs to whoever holds that key. It is IPv4 or IPv6, whichever + the node connected over, and it is the one to answer a question with. +- **Announced hint** is what the node believes its own address to be, discovered + through a STUN server and sent to us. It is useful for reaching the node + directly and it is a claim, not evidence. + +Clients are recorded the same way: `webrtc_offer` in the log is written when a +browser starts a peer connection, with the address the hub saw it come from. +Whatever the two peers then discover through STUN is theirs to negotiate and does +not belong in a log. + +Deleted accounts are not counted or listed anywhere in the panel. The tombstone +row exists so the connection log stays readable (§2) and is not a user. + +--- + ## 9. Moderation and Legal ### Who is the legal host |