12 lines
999 B
HTML
12 lines
999 B
HTML
<p>Disconnects are normal. Unhandled disconnects are how archives get holes and how hosts talk to an empty capture for twenty minutes.</p>
|
|
<h2>Detect absence, not just errors</h2>
|
|
<p>A client can sit in a “connected” UI state while events have stopped. Alert on last-event age, not only on thrown exceptions.</p>
|
|
<h2>Reconnect policy</h2>
|
|
<p>Exponential backoff with a cap. Hammering a session endpoint in a tight loop can make a platform issue worse and can look abusive.</p>
|
|
<h2>User-visible status</h2>
|
|
<p>Show “no events for 22s” in the operator UI. Hidden retries feel like a freeze. Visible retries feel like a system doing its job.</p>
|
|
<h2>Host communication</h2>
|
|
<p>If capture is down, the host may still be live on the official app. Do not tell them to end the stream unless you have confirmed the official player is also dark.</p>
|
|
<h2>Post-incident</h2>
|
|
<p>Log start, end, suspected cause (Wi-Fi, app crash, laptop sleep). Patterns across weeks beat a single angry screenshot.</p>
|