kbct VS syngesture

I had a similar problem with the Tecurs KB510 I got at work. The only way I found to type F1-F12 keys on Linux was to set up a hack with kbct [0] and the Super key... until I tried the configuration described in the gist you linked. Thanks a lot for that !

[0] https://github.com/samvel1024/kbct

I use KBCT and encourage others to support it: https://github.com/samvel1024/kbct

kbct

>Creating a "standardized experience" like Windows usually means that configurability goes right out the window. It's how you get abominations like dconf or the GNOME music player

I don't understand how you connected these dots and I'd suggest against calling things abominations. You don't have to use dconf or the GNOME music player, those aren't standardized. If someone does like them I think they're perfectly fine, they do exactly what they're advertised to do. It's also fine if you don't like them, they're just two options from the many configuration databases and media players that you can choose from.

>But why shouldn't I be able to run xbindkeys or sxhkd or whatever hotkey dameon I want?

In some ways you actually can but it depends on the hotkey daemon and how it's implemented. The reason for that is technical, those are implemented with X grabs which have a number of usability and security issues. There are a few key rebinding daemons that use evdev directly so they work with Wayland:

https://github.com/samvel1024/kbct

https://github.com/snyball/Hawck

But these also do have similar security issues to X key grabs, in that they effectively operate as keyloggers. If you're looking for an API that works purely within Wayland and lets unprivileged clients request key rebinding, that doesn't exist yet. Somebody would need to specify what that API looks like and figure out a good way to make it secure. What would the end goal of the API be, and how could the system (and by extension, the user) tell the difference between a legitimate hotkey daemon and a malicious keylogger? And would it actually be any better than the approach of snooping evdev? I don't know the answer to these questions but you may have more experience with this than I do.

I've shared my opinion on why mouse/trackpad handling is terrible on most Linux distributions [0], thanks to an insane obsession w/ rewriting the entire stack and throwing away vendor-provided acceleration curves in order to provide gesture support, instead of just building it on top of the correct, working solution.

More importantly, there is a solution for fixing this and I've done my part by open sourcing a multi-touch gesture support that's driver-agnostic and runs on top of the vendor-provided drivers w/ their correct acceleration curves [1].

(But TBH I don't know if this applies to Apple's trackpad because I don't know if there are any first-party drivers w/ proper acceleration curves for Linux or if they've all been poorly reverse engineered.)

[0]: https://neosmart.net/blog/multi-touch-gestures-on-linux/

[1]: https://github.com/mqudsi/syngesture/

I wrote a general purpose multitouch daemon w/ gesture support for Linux that works with the existing input stack (i.e. doesn’t require switching to evinput), if anyone is interested:

https://neosmart.net/blog/2020/multi-touch-gestures-on-linux...

https://github.com/mqudsi/syngesture

Regardless of software (touchegg + touché, fusuma, libinput-gestures + libinput-gestures-qt OR gestures, gebaar-libinput, gebaar-libinput-fork, syngesture, gestures), which gestures do you actively use on your Plasma desktop?