Auto-connect request: voxis (audio-record)

store-requests privileged-interfaces
1 
name: voxis
description: Real-time voice translation for videos, games and meetings
snapcraft: PRIVATE
upstream: PRIVATE
upstream-relation: publisher is the upstream author
plugs:
  audio-record:
    request-type: auto-connection
    reasoning: Capturing audio is the core function of the snap -- without it
      there is nothing to translate, and on first run the application does
      nothing at all rather than degrading, with no in-app way to diagnose
      why. The same interface also covers the real microphone, which two-way
      meeting mode uses to translate the user's own speech for the other
      party. Microphone use is stated in the snap description.

Revision 1 is published to the edge channel for review: snap install voxis --edge. On a store install every interface auto-connects except this one:

audio-record   voxis:audio-record   -

The only other privileged interface plugged is audio-playback (already auto-connected); network, home and the GNOME desktop interfaces are auto-connected by default, and the snap is strictly confined. This matches the recent precedent of loomfy and qvac-workbench, granted audio-record auto-connection for the same core-function reason.

2

This request has been added to the queue for review by the @reviewers team.

3

Hello @voxis :slight_smile:

Given the snap functionality, the requested interface seems reasonable, and I can see that you have already included a disclaimer in the snap description, so +1 from my side for auto-connecting the audio-record interface to the voxis snap.

1 Like
4

I think this is consistent with the current policy and existent precedents. +1 from me for granting voxis auto-connection to audio-record interface

1 Like
5

+2 votes for, and 0 against, granting audio-record to the voxis snap. This is now live :slight_smile:

1 Like