Thanks for the tip. Without kwindowprop I will have to wait though.

I am on Debian 13 KDE Plasma with Wayland. I tried kdotool as @Erwan suggests but as expected xprop doesn't return anything. Apparently, I will also have to use kwindowprop which will take a while to appear on Debian Stable.

There used to be a thing in KDE where you could execute actions and macros based on window titles

Now, that would be nice but unless there is another way it looks like I will have to wait.

Thanks for the help.

My understanding is that sandboxing is not mandatory for Snaps, but it is for flatpaks. Some of the Snap code not being open source, and generally the technology being centralised around Canonical apparently is off-putting for some.

I share your concerns about trust. With flatpaks we can still read the source and commits, but not many will or can do this every time they install and update software anyway. In this sense, we have little choice but to trust the verified developer and the community, who may of course be compromised too, regardless of distribution method. I suppose with flatpaks we have to check permissions and make them as restrictive as possible.

This ranking is very close to how I see this. Anything after Docker/Podman is out unless I absolutely need an application in which case keeping a record of dependencies is a good idea. But I want to know the work system will absolutely start in the morning hours from a deadline. Avoiding single points of failure is another way of course (ie multiple systems, OSes, backups, password managers etc).

I remember the time applications came on floppies, 640kb of RAM was indeed enough for anyone, and people competed in writing games in one line of BASIC (yes, that was 255 characters code max). Containers feel horribly wasteful to me, but I came to accept there aren't many realistic alternatives for the average users who need reliability with zero effort. Making a note of dependencies in case you need to backtrack is not a realistic proposition for most. But I can understand why some users will want full control and a lean setup.

True but whatever the settings there will be times you run out of space unless you teach yourself to backtrack and accelerate, or cancel the move and restart. Using multiple fingers or the Windows method deal with that scenario.

This works but I must say the Windows approach is more elegant and intuitive than moonwalking. I would think its the driver that interprets hitting the boundary in this way.

This moonwalk does work. Thanks!