[decide] Pre-join connection check (RTT/jitter probe to LiveKit shown as signal bars) #115

Closed
opened 2026-09-17 13:27:08 -04:00 by jared · 1 comment
Owner

Marked "maybe" 2026-09-17. Parked until a yes/no.

A 2-second probe from the lobby to the LiveKit SFU (WebRTC data channel or the LiveKit ConnectionQuality after a silent pre-connect), rendered as signal bars with a "your connection may be choppy" hint. Local measurement only; nothing stored. Would live in the EC fork's lobby (src/lotus/*) with a host-side setting to hide it.

Marked "maybe" 2026-09-17. Parked until a yes/no. A 2-second probe from the lobby to the LiveKit SFU (WebRTC data channel or the LiveKit `ConnectionQuality` after a silent pre-connect), rendered as signal bars with a "your connection may be choppy" hint. Local measurement only; nothing stored. Would live in the EC fork's lobby (`src/lotus/*`) with a host-side setting to hide it.
jared added this to the Features 2026-Q4 milestone 2026-09-17 13:27:08 -04:00
jared added the enhancementquestionpriority: lowarea: calls labels 2026-09-17 13:27:08 -04:00
jared self-assigned this 2026-09-17 13:27:08 -04:00
Author
Owner

Owner decision (2026-10-23): not building the pre-join connection check. The post-call Details card (#253) already shows the connection numbers (RTT, packet loss, jitter, whose side the problem was on). Closing.

Owner decision (2026-10-23): **not building** the pre-join connection check. The post-call Details card (#253) already shows the connection numbers (RTT, packet loss, jitter, whose side the problem was on). Closing.
jared closed this issue 2026-10-23 16:02:21 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#115