The most straightforward thing to do, on a private LAN, is to make all your own certs, from a custom root cert, and then manually install that cert as “trusted” on each machine. If none of the machines on this network need to accessed from outside the LAN, then you’re golden.

Wait, I’m supposed to be doing my home improvements?

“You’ll sudo shoot your eye out, kid.”

What DOES the new scanner do with its scan output, then?

I fucking love the fox’s expression here.

Second.

A little off-topic: anyone else read this as “BCA Chefs”, initially?

Welcome!

a good way to get yourself labeled by someone who thinks in memes.

What an effective way to put it.

KeePass on my phone and desktop, with the master file sync’d automatically to the server in my basement.

So, you’re a tech nerd who wants an addictive game?

Factorio.

Also Satisfactory, but I’m not sure how well it runs on Linux. Fairly sure Factorio will run on just about anything

Windows 11 has ads NOW, in the enterprise install I’m provided at work.

MLB 66

You mention Bally and baseball, mlb66 was my go-to last year.

Generally speaking, fault protection schemes need only account for one fault at a time, unless you’re a really large business, or some other entity with extra-stringent data protection requirements.

RAID protects against drive failure faults. Backups protect against drive failure faults as well, but also things like accidental deletions or overwrites of data.

In order for RAID on backups to make sense, when you already have RAID on your main storage, you’d have to consider drive failures and other data loss to be likely to occur simultaneously. I.E. RAID on your backups only protects you from drive failure occurring WHILE you’re trying to restore a backup. Or maybe more generally, WHILE that backup is in use, say, if you have a legal requirement that you must keep a history of all your data for X years or something (I would argue data like this shouldn’t be classified as backups, though).

Defederation is an administrative solution, specifically for when the user-facing tools like muting and blocking aren’t enough. It’s the solution against instance admins that aren’t capable or willing to moderate their users, or that are actively malicious.

Name checks out.

Why buy a $15 replacement when I can print one from $20 of filament?!

(I kid)

As someone with 0 investment in this whole ecosystem, I saw and perused this article like a week ago, and my immediate impression was “Why is this guy constantly saying ‘Wayland breaks XXXXX’? Wayland isn’t breaking anything, it’s new tech. Wayland has certain features, or it doesn’t or doesn’t yet. The only folks breaking anything are those swapping use of X with Wayland, within various apps or tech stacks, potentially prematurely, where Wayland doesn’t yet have the full set of features needed.”

Whoever this is seems to have a really poor understanding of long-term software development, despite being way more invested in it than I am.