nextcloud / nextcloud/spreed

Split default camera and microphone settings into separate toggles

Open
#17,202 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: api 🛠️ feature: call 📹 feature: frontend 🖌️ feature: settings ⚙️ papercut
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using:
32.0.5, Talk v2.0.4

Is your feature request related to a problem? Please describe.
In the "Devices" setting section, there's a toggle to "turn camera and microphone off by default". It's great that we have this option, but most of our internal use is with microphone on and camera off. So right now, we have to choose one of two bads — usually both off to be safe — and then turn on the mic before every single call.

Describe the solution you'd like
It would be great if the current setting "turn camera and microphone off by default" was split into two separate switches, one for the camera and one for the microphone.

Describe alternatives you've considered
An alternative would be to simply always keep the settings from the last call you were in.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Devices settings section and locate the existing combined camera-and-microphone default toggle. Separate its camera and microphone behavior into two switches, and verify that each setting can be controlled independently.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.