Thinking about how humanity had a moon landing in 1969, and here I am in 2026 trying to bind a global shortcut to my GTK app running on KDE Wayland using shortcut portal, and sometimes shortcut binding just fails without explanation. Stale sessions? kglobalaccel failing? kglobalshortcutsrc broken? D-bus connection problems? Portal itself fails? Who knows! Meanwhile just for the shortcut binding to work whatsoever I had to wrap my app in systemd scope - because if I don't, it will attempt to bind the shortcut to my terminal instead (which is where I launch my app from).

Impressive how something so simple as pressing a hotkey was turned into a dog's dinner, some arcane voodoo magic, all under retarded pretense of "security" (security being - "no shortcuts for you bro, keyloggers or something, forget LD_PRELOAD please"), 18 years of development and it doesn't even work.

So here I am, a very basic desktop developer who is trying to build a simple hello-world app that does nothing, who must study the entirety of Wayland spec, Dbus and portal extensions, then spend hours debugging this entire mess first on KDE then on GNOME just to understand why exactly it does not work -sometimes- but also somehow works most of the time. Sounds great! Sounds even better if you try to write your own GUI toolkit instead of using GTK/Qt abstractions, because it adds even more complexity - all of which should be handled by the compositor, but instead has been laid off to you, the developer.

Then Wayland fans close the doors, close the curtains and violently masturbate to the sleek design of "Just The Protocol Bro".