SpaceCadet

That's another option, but it's a bit more cumbersome having to cherrypick which exact backports you need for your specific hardware. Also, if you then for some reason don't upgrade to the next stable release when it comes out, backports get abandoned after 1 year instead of the customary 3 years for the rest of the oldstable release.

From my experience, running trixie/testing the past year or so on a minipc with hardware that was a bit too recent for bookworm, I can say that the cadence of security patches has been about the same between bookworm and testing.

And let's be honest, on a desktop system your main attack surface is going to be the software you go online with, i.e. the browser. So if you make sure that is kept up to date (flatpak, vendor repo, ...) that already goes a long way.

the ctrl-super-alt is completely different

It's not "completely different" ... and that's the problem. Completely different I can handle. I can manage knowing vim keybindings, readline keybindings and standard windows keybindings at the same time. What I can't handle is: having to use command + C on one Mac and control + C on Windows to copy, but then in some cases you do use "control" on both OS-es, and sometimes control and alt are switched ... It's because they are similar but different that it's such a mess trying to get proficient in both at the same time.

Eh. Windows has its share of annoyances, but once I have set it up to my liking my desktop workflow is very similar to my KDE setup, and WSL + Windows Terminal gives me a functional Linux shell environment.

And at least on Windows I don't have to deal with cmd/control/alt switcharoo messing up my muscle memory.

The correct way with a new computer with recent hardware is to install Debian Testing to get a recent kernel, firmware and mesa and stuff, but put the code name of the next release into your apt config instead of "testing". So then when the next version is released, you can just stay on that, now stable, version.

Trixie just got released today though, so for the time being you can probably get away with using that.

every service will get your ID or photo

To be fair, that's not how it will work. The site and the identity verifier will be two different things, the verifier only attests that you are not underage and the site doesn't get your identity.

Still harmful though, because you can be sure that there will be scamsites redirecting people to fake but real looking verifiers for blackmail and identity theft purposes.

I for one will never put my ID or photo into any age verifier ever.

I think there are going to be a whole lot of phishing and blackmail scams in the future, preying on the stupid computer illiterate masses putting in their personal information into fake "age verifiers" to access porn or other adult content.

Ah I see, misunderstood your point then.

I guess that's also why Google is going to use some kind of AI to determine whether or not a profile is underage. That way, existing adult users of their services are (most likely) not affected.

In my opinion, draconian government overreach in matters of civil liberties is one of the few instances where we should be on the side of big tech companies.

Actually, I don't think this is industry mandated. I don't think it's in the interest of tech and content companies to create more friction to access their services. This one seems to have more to do with the governments wanting to exert more control over online affairs, and of course, over its citizens.

I mean, fuck Spotify and all that, but this one is really the UK government's doing.

And soon, this shit will come to every country. They're all drafting laws to mandate real age verification for adult content. The UK is just the first to implement it.

FYI Belgian "site blocks" are still just simple DNS blocks at the ISP level.

You can easily get around it by using any of the well known public DNS resolvers.

Cheatsheet:

Google: 8.8.8.8
Cloudflare: 1.1.1.1
Quad9: 9.9.9.9

square centimeter is the one I heard

Except this developer has created license terms that forbids the creation of "packages", so he clearly does want to affect my ability to do just that.