2 ms·

Not quite -- this was designed to avoid developers using the "Input Monitoring" access, which covered whole-keyboard, etc. monitoring on a per-app level. The p

Not quite -- this was designed to avoid developers using the "Input Monitoring" access, which covered whole-keyboard, etc. monitoring on a per-app level. The permissions change is nothing new (introduced Fall 2019), and covers many more permissions than simply keystroke access. Given the hotkey could be changed, keyboard-wide access makes the most sense -- would you really think it more "sane" to have to have a separate call and permission requests for each individual key, across apps? Blame Discord for failing to communicate something that isn't a big deal, and hasn't been for the over 3 years this dialog has existed with it -- and worry more about what they're doing in the background, than Apple's APIs.

yjftsjthsd-h 4y ago
> would you really think it more "sane" to have to have a separate call and permission requests for each individual key, across apps? Er, yes? I'd expect it to be something like on the first run you get a prompt like "foo wants to read ctrl+a, ctrl+b, and ctrl+shift+c even when it's in the background; allow?", and reprompt on changes (so you'd tell the app to change it, and then confirm to the OS that you're okay with it). I'd also personally be happy with the OS initiating things with a single control panel that listed all apps that can listen and you tell the OS what keys should signal what apps and how, but that might be too complex to ask people to use. > Blame Discord for failing to communicate something that isn't a big deal In fairness, also very much this; every app should always explain every single permission it requests.