Are We GlobalShortcuts Yet?
41 points by ecksdee
41 points by ecksdee
FYI, Ghostty on Linux supports this (if its available) since almost a year ago. Implementation here: https://github.com/ghostty-org/ghostty/blob/main/src/apprt/gtk/class/global_shortcuts.zig
Note there's a lot of... complexity and frustration in making this work, which can be part of the slow uptick (see the comments in the linked file).
(note: I co-authored the page)
It's unfortunate how slow adaptation has been for this, in voice chat apps especially. Really glad to find out while working on this that KeePassXC just recently added support though.
Hopefully with distros and desktops like Ubuntu, Gnome and KDE dropping X11 it will gain more interest.
Oh, this has been lately an obsession of mine because... conference mute.
I contributed a way to add a global shortcut to Google Meet recently, and I also nagged the autokey-wayland maintainer because I could not get autokey-wayland working on my system- I should be able to now hack that to control mute in Slack Huddles.
But global shortcuts are the way to go, apparently. Hope that gains traction soon. (I also think some sort of web standard should be added, I don't think one exists yet?)
A web standard would be nice yeah, I think the current implementation in Chromium is only for extensions, so web apps can't use it without using an extension as workaround which isn't ideal.
I don't know, I was mulling about this and I think for my purposes, the problem is that audiovisual inputs/outputs seem to be poorly integrated.
Some people at work have fancy control of screensharing in their desktop environment- AFAICT, they can control screensharing in any application through customizable desktop shortcuts.
Why can't videconferencing applications (both desktop and in the browser) detect that my OS mic input is muted and show me as muted? (My main interest on controlling this in the application and not on the desktop environment is that showing proper mute status to other is a good signal!) For that matter, why Google Meet and Slack Huddles seem to implement independent input/output audiovisual selection?
I see this is not desktop portals, but rather Pipewire? Maybe I should investigate Pipewire configuration software that hides complexity from clients?
This is also how I would like it to work. Let me mute the mic how I see fit and report the status up through every layer. That would work with USB mics with a hardware mute button too.
Small nit pick: Mumble has a wrong emoji given it has a PR.
It does have a different emoji, but this is because mumbles progress has stalled despite the PR being a few years old now and some of the project contributors are deciding to possibly switch to an alternative instead of implementing GlobalShortcuts at all. There is some hope though.
The one that matters most to me (mumble) is "stalled" not a good sign. The one that actually matters most (orca) isn't even listed, unless that's just "gnome"? But what if not using gnome?
I assume things will still work under wayback but haven't migrated to that yet from regular X.