I run Wayland but I'm not happy about it. Most autoclickers still don't work, and autotypers need sudo and group magic to get working.

Cool kids don't allow telemetry. I think that any software whose userbase isn't totally oblivious will have severe selection effects if you use data obtained by spying.

> Wayland sessions make up 82% of all sessions with telemetry enabled.

That is a significant caveat.

I'm on Wayland with NVIDIA, it took longer to get there but it does work perfectly fine.

> However, it's clearly not _mature_ yet (which is understandable - it's very new!)

I'm admittedly biased against Wayland because in my view it's been a disaster both in organization and technically, and I've had some very frustrating interactions, but even so there's no way it's accurate to describe Wayland as very new.

Wayland started development in 2008. Version 0.85 of the protocol and of Weston, which the devs called "the first real release", was in early 2012. KDE (KWin) started adding Wayland support in 2011.

Wayland development began almost exactly 17 years after Linus released the first 0.01 kernel. Next month Wayland turns 17. So Wayland has been in development now for half of Linux's entire existence, and it's still not mature. It started when iPhone 3G was a new top notch phone, the MacBook Air was just launched, 4G mobile networks were not yet commercially available, netbooks were highly popular, solid-state drives were just breaking into the market, and the term blockchain hadn't yet been invented.

You may like Wayland, but what you're saying is you're using the most common GPU vendor (yes everyone loves AMD's open approach to drivers, but there's a reason Nvidia dominates completely, and that's because AMD GPUs are not competitive) and basic functionality like copy-pasting and key repeats doesn't work for you. Yes Deskflow isn't the most standard setup but this is completely like my experience with Wayland. A 17 year old project and it only works for a certain set of typical setups with typical use cases the committee blessed.

I am also on Wayland (via CachyOS) and recently started using Deskflow for my MacBook KVM-type setup. Linux on one screen, Mac on the other.

Works great except for the copy-and-paste issues and the mod key resets - just as you describe. I've been fiddling with it the last couple of days.

Funny to see someone with such a similar setup and issue.

Esoteric issues aside, the general use of CachyOS has been very smooth.

There seems to be a lot of momentum for desktop Linux, with Microsoft and Apple dropping the ball lately. LLMs also make deep configuration of Linux more manageable. The stars seem to be aligning for it.

Do you have a Ko-fi? 'cause I would really enjoy that screensaver.

I adore this project on its own merits too because using the memory values in an emulated game is something that has fascinated me since Twitch Plays Pokémon integrated their Twitch display!

I wish you a lot of luck; I am basically just waiting on XScreenSaver to be ported to Wayland before I move on from X11.

But jwz (XScreenSaver's creator and maintainer) doesn't give me much hope: https://www.jwz.org/blog/2025/07/xscreensaver-wayland-and-lo...

OLEDs still have burn-in issues even with all the fancy mitigation systems they have.

If there's one thing I never tire of, it's someone telling me that I don't need something or how I'm doing it wrong. I would love a screensaver that scrubs my OLED pixels.

One of the great strengths of Linux, and one of the things that draws new people in, is the custizability and making the system your own to whatever degree you want. That a "modern" display manager doesn't let you have a screensaver and people try to cover up for it with "you're just trying to use your system wrong. Be normal and use your system like we say is normal" is embarassing.

> what kind of oddball display / use-case do you have,

It's fun.

OLED. KDE has kinda a workaround with lock delay.

I use steam deck with TV as a media PC and it's OLED, I don't want to lock a media PC nor want to display a static picture on it.

From my understanding, the security decisions around things like screen locking are the source of many of the pain points holding back X11 users from wayland.. Things like xtest(send input events from random sources), screen grabbing/video recording(allowing another app to see the contents of another window from a potentially different security domain), focus grabbing, input sniffing, are all difficult on wayland, specifically because they are serious security issues on X11, especially in light of a modern understanding of the risk profile.