@CjkOvPDwQW China is a repressive surveillance state with a keen interest in spying on their own people who has conducted incredibly broad state sponsored industrial espionage.
Draw your own conclusions on whether such products are safe.
@CjkOvPDwQW China is a repressive surveillance state with a keen interest in spying on their own people who has conducted incredibly broad state sponsored industrial espionage.
Draw your own conclusions on whether such products are safe.
@gkpy
The short answer is that it’s not anything like a trivial transition, and the best-case scenario appears to be precisely what you already have after you invest a substantial amount of time.
For ages, I thought it was actually outright broken, but it turns out that if your GPU is Nvidia, you need to pass a special argument and agree not to report issues. This is obvious on the CLI but invisible if you try to start an environment the standard way by selecting it in your display manager. Then you WLR_NO_HARDWARE_CURSORS=1 if you actually want to see a cursor. I’m sure proponents believe its Nvidia’s problem that they haven’t provided better support for a niche of a niche of a niche, but some of us would like to do actual work and don’t care whose fault it is that something works shitty.
Then there is scaling for those of us with high/mixed DPI. Xwayland windows end up so blurry that you would be forgiven for imagining you had a head injury. I don’t want to worry about replacing any app that doesn’t support Wayland again to have no benefit of any kind. In fact since some apps are to interact with other people I can’t just change them out regardless of wayland support. There is no plan to fix this.
Beyond that flameshot doesn’t work correctly, replacing xcape with interception tools looks quite complicated, and depending on what app and version you use screen sharing may or may not break and other people give zero fucks about your niche environment.