Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not what you asked for, but you can mute/unmute quickly with the keyboard shortcut: ⌘/Ctrl + d


Ah, yes, of course. D as in mute.


M is taken by minimise, hence the next closest thing is D (for deaf).


But ⌘D is also 'add bookmark' on Mac, at least. So depending on which UI element inside Chrome is focussed, it may not do what you want either.

I've been using this extension: https://chrome.google.com/webstore/detail/google-meet-push-t...


Nice, thanks. I have a lot of Meets hanging around in my bookmarks thanks to the focus being slightly wrong when I press command-D.


What would be the logic behind “deaf”? That “mute” is a homonym/polyseme of a word for a disability, so let’s just use the first letter of any disability?


Would it be less arbitrary to add another modifier to the shortcut, rather than use "D"?


The blessed workaround as we say in software engineering, which allows us to move the real issue waay down the backlog indefinitely. :)


And ctrl+e for video


As long as the Meet browser tab _has focus_.


Zoom at least uses Cmd+Shift-A for Audio and V for Video

But as the recent Google Icon kerfuffle, UI/UX is not their strength (probably because of opinionated technical people that think you need to A/B shades of blue)


Teams uses something equally silly, like Ctrl+Shift+M for mute/unmute, IIRC.

Which is pretty annoying, because the mute button is about the most important button in a videoconferencing tool, and I want to have it under a single keypress, so it can be used effortlessly, with my left hand (the same that operates Alt+Tab, while my right hand is on the mouse, scrolling ... well, meeting agenda, let's say).

I'd fix that for myself with AutoHotkey, but I can't, because Teams is just another Electron app, so I can't just look at which UI component has the focus to create a rule, "if focused on Teams video call and not its chat, rebind M to Ctrl+Shift+M".

One of the countless reasons I hate it when people do custom UI, instead of using OS-provided controls.


Google's problem is an incompetent product org. An A/B test would have quickly solved UI issues that lead to accidental or underuse of a feature.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: