Open solick opened 2 years ago
Thanks for the feedback @solick,
Personally I think it could become a per channel/call setting plus a user specific override. Essentially I'd like to avoid force unmuting a user if they don't elected to as it could be confusing or even undesired behaviour.
It's a good discussion to have though, hope to get more feedback from other people as well.
/cc @itao
We often have calls with just very few people, where we regularly have some confusion about initially being muted.
I could imagine a setting to optionally mute joining users an "ongoing conversation", i.e. a call with n users already connected where n can be adjusted.
Maybe there could be a checkbox to join the call muted (checked according to some configuration – server/channel/user) with the "Join call" plugin message.
Hello. Our team recently started using mattermost, and overall the experience has been great, compared to Slack or Discord. But this default muted behaviour is counter-intuitive to what we are used to.
Many apps nowadays have this as a solved problem, by having a threshold of auto-unmuted/muted users. By that I mean that if for example somebody joins as the 5th person in a call, when 4 other people are already in a call, said 5th person is auto muted, to avoid too much noise in big group calls.
My suggestion would be a config option to turn on/off the auto-mute, and also set the threshold number where new joinees are muted or not.
Thanks @meierw , that's good feedback. I'll bring it up with the team and see if we can make some improvements on this front. /cc @cpoile
currently all newly joining users are joining muted which means an extra step to unmute before start talking.
It would be great to have a configuration per user or per server to start unmuted into a call.