Also no one uses X11 networking by default lmao, its always X forward over SSH, that is definitely secure and still something wayland can’t do.

Sure it can, with waypipe (like, for a while now…)
Just waypipe ssh <host> [command]

You can even run X apps over this through cage even when X11 forwarding is disabled by the host (because, you know, the security issues…)

Does this mean I can stop setting MOZ_ENABLE_WAYLAND?
Or is it just enabling the compilation of Wayland sections (which I thought happened a while ago?)

Right so just installed xscreensaver - automatic blanking and locking is indeed broken BUT it does display all the pretty animations just fine! (at least on Sway)
Don’t really have time to mess around with it but maybe try figuring out which mechanism is used for screen locking in your environment (in Sway’s case it’s swayidle) and get it to start xscreensaver right before calling the real locker program?
BTW you can get xscreensaver-settings to come up by unsetting the WAYLAND_DISPLAY variable:

env --unset=WAYLAND_DISPLAY xscreensaver-settings

Philosophical BS: I don’t think it’s correct to say that Wayland doesn’t support screen savers, but rather that it doesn’t support XScreenSaver, or, more accurately, the mechanisms it uses for screen locking and idle-detection.
As others have pointed out, equivalent functionality has already been implemented and is used by various screen lockers. What appears to be missing is something to take this functionality, and display an animation instead of just locking the screen.
I noticed that all of XScreenSaver’s animations are actually separate binaries in /usr/lib/screensaver/ so we basically need a locker that speaks Wayland’s locking protocol, but also takes and runs those binaries in full screen mode.
Or maybe XScreenSaver’s dev can be convinced to add support once the protocols are stable?

Ads on a computer??
He got his monitor mixed up with a TV screen or something lol