Shown as idle while talking in a voice channel #1008

Open
opened 2026-11-20 08:07:03 +00:00 by charles · 0 comments
Owner

Reported by Charles (2026-11-20): "If we're in a voice channel and we've been talking/active, we should not show as idle in the user list."

What happens: the presence goes idle after 10 minutes without input (fluxer-core/src/presence.rs, IDLE_AFTER, from CoreEvent::Idle). The idle time comes from the OS (fluxer_platform::idle::system_idle) and, where the OS gives no answer, from the last input in the client's own windows. On KDE Plasma on Wayland (Charles's desktop) the probe has no answer (see the module docs), so someone who talks in a call while playing a game or working in another window for ten minutes is shown idle although they are plainly there.

Wanted:

  1. Speaking in a voice call counts as activity: while the user is connected to voice, each time their own voice is transmitted (voice activity detected and not muted, or push-to-talk held) the idle clock restarts, for both idle and the AFK timeout. Merely sitting in a channel silent, muted or deafened does not count (the original marks those idle too, and the server's AFK move relies on it).
  2. Separately, a real system idle time on Wayland compositors that have no D-Bus idle answer (the ext-idle-notify-v1 protocol, which KWin implements), so activity in other applications counts there as it does on GNOME, X11 and Windows. Do this here if it is small and safe, otherwise leave it as its own follow-up issue.

Parity: the original (features/ui/state/Idle.ts) uses input only and has no voice rule, so (1) is a deliberate deviation; record it.

Reported by Charles (2026-11-20): "If we're in a voice channel and we've been talking/active, we should not show as idle in the user list." **What happens:** the presence goes `idle` after 10 minutes without input (`fluxer-core/src/presence.rs`, `IDLE_AFTER`, from `CoreEvent::Idle`). The idle time comes from the OS (`fluxer_platform::idle::system_idle`) and, where the OS gives no answer, from the last input in the client's own windows. On KDE Plasma on Wayland (Charles's desktop) the probe has no answer (see the module docs), so someone who talks in a call while playing a game or working in another window for ten minutes is shown idle although they are plainly there. **Wanted:** 1. Speaking in a voice call counts as activity: while the user is connected to voice, each time their own voice is transmitted (voice activity detected and not muted, or push-to-talk held) the idle clock restarts, for both `idle` and the AFK timeout. Merely sitting in a channel silent, muted or deafened does not count (the original marks those idle too, and the server's AFK move relies on it). 2. Separately, a real system idle time on Wayland compositors that have no D-Bus idle answer (the `ext-idle-notify-v1` protocol, which KWin implements), so activity in other applications counts there as it does on GNOME, X11 and Windows. Do this here if it is small and safe, otherwise leave it as its own follow-up issue. **Parity:** the original (`features/ui/state/Idle.ts`) uses input only and has no voice rule, so (1) is a deliberate deviation; record it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/fluxer-native#1008
No description provided.