AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Features

Edit history

Earlier versions of Share keyboard, mouse and/or controller input, newest first.

Current version | Edited by Rex
Changes
There may be security concerns about letting users control other user's device, which hopefully are minimized by all the explicit checks provided to all parties involved.Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing discussions and didn't find a duplicate.Removed:
Show

Share keyboard, mouse and/or controller input

Problem

Sometimes, when sharing your screen, it is desirable to let somebody on the other side of the call take control (for customer support, for quickly helping with a task, etc).

Proposed solution

Before a call is established, an option can be toggled to allow input takeover requests, with granular permissions on what kind of inputs are allowed. If enabled, other users on the call watching can request to control the screen, selecting the input methods to provide. Server operators are free to restrict those facilities through permissions.

Notes (optional)

I don't know whether this is feasible at all, hopefully a dev or somebody familiar with the codebase can answer that question. Input latency may become a concern depending on the instance, but it's probably bearable, especially in self-hosted instances with few users and hosted relatively close to the participants. There may be security concerns about letting users control other user's device, which hopefully are minimized by all the explicit checks provided to all parties involved.
Original by Rex
Show

Share keyboard, mouse and/or controller input

Problem

Sometimes, when sharing your screen, it is desirable to let somebody on the other side of the call take control (for customer support, for quickly helping with a task, etc).

Proposed solution

Before a call is established, an option can be toggled to allow input takeover requests, with granular permissions on what kind of inputs are allowed. If enabled, other users on the call watching can request to control the screen, selecting the input methods to provide. Server operators are free to restrict those facilities through permissions.

Notes (optional)

I don't know whether this is feasible at all, hopefully a dev or somebody familiar with the codebase can answer that question. Input latency may become a concern depending on the instance, but it's probably bearable, especially in self-hosted instances with few users and hosted relatively close to the participants. There may be security concerns about letting users control other user's device, which hopefully are minimized by all the explicit checks provided to all parties involved.

Checks

  • ☑ I searched for existing discussions and didn't find a duplicate.