@[email protected] to [email protected] • 2 years agoUseless messengerlemmy.mlimagemessage-square146fedilinkarrow-up1644cross-posted to: [email protected]
arrow-up1644imageUseless messengerlemmy.ml@[email protected] to [email protected] • 2 years agomessage-square146fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink1•2 years agoi bet you could find some little tool to replace that easily. sucks though
minus-squareFlaxlinkfedilinkEnglish1•2 years agoIt makes sense. Websites in a browser shouldn’t be able to detect keystrokes outside of the tab
minus-square@[email protected]linkfedilink2•edit-22 years agoIf you use JACK audio, then you can make it Unix-way. Or use hardware PTT. EDIT: or just mute/unmute mic system-wide
minus-square@[email protected]linkfedilink1•2 years agoThey have to do it on fucking purpose right? Only allow keybinds so you have to get the client so they can collect user data
minus-squareFlaxlinkfedilinkEnglish2•2 years agoNo, it’s probably because websites running in Chrome might lack the ability to detect keystrokes in the background. If they did, that’s a very very concerning security risk. If they wanted to force you, they’d just disable the web app lmao
Push to talk… And I think that’s literally it 😂
i bet you could find some little tool to replace that easily. sucks though
It makes sense. Websites in a browser shouldn’t be able to detect keystrokes outside of the tab
If you use JACK audio, then you can make it Unix-way. Or use hardware PTT.
EDIT: or just mute/unmute mic system-wide
They have to do it on fucking purpose right? Only allow keybinds so you have to get the client so they can collect user data
No, it’s probably because websites running in Chrome might lack the ability to detect keystrokes in the background. If they did, that’s a very very concerning security risk.
If they wanted to force you, they’d just disable the web app lmao
Fair enough