I’d like to request auto-connection of the audio-record interface for the fliks snap,
the desktop client of Fliks, an open-source self-hosted media server I maintain (a jellyfin alternative). The interface is used by the watch party voice chat; details below.
name: fliks
description: Desktop client for Fliks, a self-hosted media server. Its watch parties let
several people watch the same title together, with an optional voice chat between
participants.
snapcraft: https://github.com/fliks-app/fliks/blob/main/desktop/snap/snapcraft.yaml
upstream: https://github.com/fliks-app/fliks
upstream-relation: maintainer
plugs:
audio-record:
request-type: auto-connection
reasoning: the watch party voice chat captures the microphone through Chromium's
getUserMedia, only after the user joins the voice channel of a party. Without
auto-connection the voice chat silently has no microphone until the user runs
`snap connect` or finds the toggle in Settings, which most users won't know to do.
Other communication clients with the same need, such as discord and signal-desktop,
have this grant.
This request has been added to the queue for review by the @reviewers team.
Hello @clementdelestre,
To me, this feels like reasonable and expected access for this snap, this is a +1 from me for granting auto-connect for the audio-record interface to snap fliks. What do other reviewers think?
Hi folks,
I think there are two major differences compared to Discord and Signal:
- Both
Discord and Signal have communication as their main functionality, and audio-record auto-connection is possibly expected by users. On the other hand, Fliks , as you described it, is “a self-hosted media server. Its watch parties let several people watch the same title together, with an optional voice chat between participants.” I don’t think most users would expect a media server to auto-connect the audio-record interface.
- Both
Discord and Signal meet the criteria: “the application is mature and well-known; the snap is published by a mature, well-known entity (snapcrafters in this case).” I don’t think Fliks meets these criteria as of now.
I believe the most reasonable way to navigate this would be for fliks to use snapctl is-connected audio-record to check whether the audio-record interface is connected when the user joins a party’s voice channel, and prompt the user to manually connect it if needed.
This way:
- The application won’t fail silently (by not showing any microphone).
- Only users who actually want to use voice chat will need to grant access to
audio-record .
@clementdelestre, do you think this is something you can work with?
Thanks