Nah, you’re the one who has special eyes or have never driven against Teslas and such. The color temperature on modern cars LEDs already makes it feel much brighter on other’s eyes, and then the actual lumens are usually more than triple the lumens compared to halogens.

If your playbooks don’t include an autoremove, you’re doing it wrong!

Or rather, lessons learned from when the default /boot partition was only like 100 MB.

You lose the right to class action lawsuits

I love when I get a coupon in the mail and lose my right to sue the company, whereas the offending company pays basically some small fine and the lawyers go home with a huge payday.

But I agree, forced arbitration sucks, I’m glad that it’s unenforceable here (other than in B2B agreements)

Classic enshittification of the kernel is kinda impossible while the Benevolent Dictator is around. And as for userland, we’ve already gone through many different enshittification attempts… Red Hat/CentOS, Poetterware, Snaps, etc… and we still survive.

Other than burnout and such, it’s very hard to kill free software that’s actively used by a lot of different enthusiasts.

I went all to AV1 last year. Enough stuff supports it, and realtime transcoding on a (relatively cheap) Arc GPU works well enough.

AV1 is superior enough for both size and visual fidelity, that it’s worth the slightly extra encoding time. But absolutely not if you don’t have HW encoding.

Elaborate.

We don’t usually do it for fun, but I’m sure my teammate who has petitioned deploying a “chaosmonkey”-thingy to our prod clusters would love it 😁

My team made the “mistake” that all new projects need to be built and approved on our dev clusters before we allow them to be deployed to the prod clusters. We’re very explicit that dev is ephemeral, and that everything should be as code, so everything heals itself…

Despite this, whenever we reprovision the dev env, we always get emails from several different people saying that we wiped their prod databases and such. It’s crazy.

I agree, though my biggest headache has been with systemd handling mounts. You have to modify a ton of units to add After and Required to make sure the NFS shares you have in fstab get mounted before starting services that depend on them. And then if the package maintainer updates their unit files, all your changes disappear!

Such a huge headache compared to the classic init.d that mounted everything very early – with just the occasional “boot delayed a couple seconds because your share was offline” or such.

How about when they “accidentally” sent that email to all your users saying that they NEED to buy Plex Pass to continue to use remote streaming? Or when they had that “bug” in the app shortly after that, where remote streaming would give an error message saying that need to buy Plex Pass to stream your content?

Maybe they don’t solicit from you, but they use dark tactics to trick your users, and that’s not acceptable in my opinion.

Therapy of some sorts is probably going to be more effective than making self-blocks, especially if you’re technically competent. I wish you luck with stopping whatever addiction it is.

Yep. If he wasn’t a man, and/or was of a lower class, he’d probably still be stuck in psychiatry.

It uses resources on their end, so they need to bill for it to make it make sense

Doesn’t AMD sell the hardware? Isn’t it end-users (or companies or whatever) that are running the hardware? So I’m a bit confused, what do you mean by AI dipshits “using” AMD’s resources – especially when it’s still available for free on Windows?

The whole “verified facts, no FUD” title is exactly the kind of shit an LLM would write. (And it’ll still make up a ton of “facts”, of course)

Otherwise, etckeeper is nice.

How’s that good news? It sounds like they are just double-dipping…

For fun, try compiling it yourself and see what scan results you get?

Have you livepatched the kernel though?

It might work in WSLg otherwise?

Why not RHEL then? It even has “enterprise” in the name!