Pierre Ossman (ThinLinc team)

We want our APIs to be stable and permanent, so adding more should be a last resort as they can be a hindrance in the future. And I'm not convinced...

> Xwayland doesn't have the same non-fullscreen problem that we have :( wayland has complete control of the users' input and can use other signals into the decision whether to...

I would prefer if we start a bit more restrictive and have our own message. That way we can have it enabled by default, and we can make sure it...

It seems we don't check the boolean values, so setting them to anything at all will result in them being turned on. :/

This has been a concern of mine ever since container solutions like snap started getting popular. The security issues will multiply enormously as every container needs to be constantly updated...

This is unfortunately non-trivial as we have to know which parts of the hash that the user actually cares about. We don't want to blindly overwrite settings the user has...

This is known, but I noticed we didn't already have an issue for it. Unfortunately all attempts at debugging it has failed. What's missing is a reliable way to reproduce...

I'm afraid recordings don't reproduce this reliably. So it doesn't seem to be a protocol error, but rather some kind of race in our parsing.

This is currently being discussed under #1347.

I don't think QEMU has clipboard support over VNC, no.