What do you mean? Screen savers have been possible for many, many years...

I'd recommend you to make backups either way. I've had a SSD with SMART status "good" very suddenly die before, so don't take any chances!

... or targeting Microsoft again too

That's not right. Most monitors use 8 bits per color / 24 bits per pixel, though some are still using 6 bpc / 18bpp.

HDR doesn't mean or really require more than 8bpc, it's more complicated than that. To skip all the complicated details, it means more brightness, more contrast and better colors, and it makes a big difference for OLED displays especially.

Why would they do that? They're intentionally not supporting OpenGL, so that people use their proprietary API

Some day it will make it's way to banking apps/sites being unusable on OSes other than approved "secure" ones.

That day was years ago. Many banking apps refuse to start if you even just have your bootloader unlocked, and some banking websites only support Chrome, some really crappy ones even only Chrome or Edge on Windows specifically.

Not 30%, it's 30g or 5% lighter!

All it ever was intended for was to make us feel like something was being done while doing absolutely nothing.

It certainly does help a little bit. But it's of course still not a coincidence that companies are pushing for it instead of more effective measures... It's not just cheap but it also pushes people to believe that measures to save the environment are all useless and annoying, and makes them less likely to want more to happen.

KDE did bother, this does neither happen with KScreenlocker, nor do non-screenlocker windows show in another way, because the screen locker is integrated with the compositor.

If the compositor crashes or gets disabled somehow ofc though, that integration doesn't help either and you have to rely on a mountain of bad hacks as well as the hope that the screen locker doesn't also crash for nothing to happen in that case, but it's as close to secure screen locking as you get on Xorg... in the end the solution for secure screen locking is still Wayland.

Telemetry wasn't a factor iirc. The biggest reasons for this change were that

• defaults like this (that only apply to new installations) should make life easy for newcomers, not for the existing users. Those users come from Windows, MacOS or other Linux DEs, which all use double click
• it already is the default in pretty much all popular distros. KUbuntu, Fedora, Manjaro, SteamOS and I think also OpenSuse are double click by default

The very next words are "but it was my responsibility"... what exactly is bad about that statement if you don't intentionally cherry pick a bad quote?

S3 is standby. Hibernate is S4

I was especially surprised to find that Gnome would turn the screen around correctly by itself. With KDE Plasma I had to set the correct screen orientation myself. And unfortunately Plasma also did not come with any on screen keyboard so it was effectively unusable.

You just need to use a distro that follows our upstream defaults - namely Wayland, and having the virtual keyboard Maliit installed by default - then everything will work out of the box with KDE Plasma too.

It's been possible for a long time, but yes, now you can do it intuitively in the shortcuts GUI

In the case of one project in paticular, that being the Sunshine game streaming project

That's a terrible example, because they completely ignore the many many years old standardized APIs (screen casting and remote desktop portals) that they could use, in favor of doing hacky and broken things that require root access instead.

Professionals call it a "layer 8 problem"

To maybe prevent a catastrophe: The system is not able to restore virtual desktop assignments yet, it only starts the apps you had open before.

Most displays provide settings to modify the colors of your screen; mine has like 10 different "picture modes" that strongly modify gamma curves, colors and the whitepoint. The EDID only describes colors of one of them, so if you change display settings, the data no longer applies.

More generally, the information isn't used by Windows or other popular video sources by default, so manufacturers don't have much of an incentive to put correct information in there. If it doesn't make a difference for the user, why would they care? Some displays even go so far as to intentionally report wrong physical size information, to make Windows select the default scale the manufacturer wants to have on that display (or at least that's what I think is the case with my cheap AliExpress portable monitor)...

That's not to say that the information is actually often completely wrong or unusable, but if one in tenthousand displays gets really messed up colors because we toggle this setting on by default, it's not worth it. We might add some heuristics for detecting at least usable color information and change this decision at some point though

No. Source 2 still uses some X11 specific stuff and has to be ported over to Wayland before it can work Wayland-native

Thst might change with Flathub's ambitions to become an actual app store though