digdilem

I agree, Grub is horrendous and one of the most complex systems in linux. Grub2 is even worse, and searching the web for help is difficult as the two are named interchangeably, despite being hugely different in design.

Random files spread over the filesystem. Some you edit, some are done automatically, some are done by kernel upgrades, some you need to run yet more commands for them to work - and it all differs from distro to distro. The sooner more distros move away from this, the better.

wade through hundreds of AI generated pages of useless information

I personally find the best use of AI is to read those pages of useless information and summarise what I actually want to know.

Google: " hugo, show total number of posts not including pages " = advertising, a billion pages of partially but not entirely relevant information that takes ages to wade through.

Gemini: same question: Clear explanation and working examples in seconds.

They're both google, but one knows what I'm actually trying to say and doesn't (yet) push advertising at me.

No sign of that happening yet, especially with the results of a certain election in a certain country.

I built a little bracket for mine to stop the GPU flapping around.

Here's a pic, which explains a bit better: https://imgur.com/tCtpH8g

It's fine. The usual cpu, psu and gpu fans locally cool the hot bits, just as they would inside a case. You don't need case fans if there's no case, because the volume of free air means convection moves it away better than any case.

Just wood screws. You don't need inserts unless you're looking to make it more complicated. Pilot-hole first, then screw. You don't need to worry about earthing the board.

I've been running motherboards on plywood for over a decade. (Actually, much longer. I built a plywood case back in the 90s) Okay, more horizontal than this and less aesthetically pleasing, but that's because I put them in a noiseproofed cupboard. The only real tricky bit is supporting a heavy GPU if you have one. Otherwise it is simply a case of fixing them to a piece of wood so they can't move around.

Oh, and keep cats away.

If this was just about the X/Twitter accounts, then X could just suspend them.

Neither. Cinnamon on Debian. Has just enough bling to be pretty and still manages not to be fat, and pretty similar to both your choices.

It won't be that simple.

For starters, you're assuming t-zero response. It'll likely be a week before people worry enough that LE isn't returning before they act. Then they have to find someone else for, possibly, the hundreds or thousands of certs they are responsible for. Set up processes with them. Hope that this new provide is able to cope with the massive, MASSIVE surge in demand without falling over themselves.

And that's assuming your company knows all its certs. That they haven't changed staff and lost knowledge, or outsourced IT (in which case they provider is likely staggering under the weight of all their clients demanding instant attention) and all that goes with that. Automation is actually bad in this situation because people tend to forget how stuff was done until it breaks. It's very likely that many certs will simply expire because they were forgotten about and the first thing some companies knows is when customers start complaining.

LetsEncrypt is genuinely brilliant, but we've all added a massive single point of failure into our systems by adopting it.

(Yeah, I've written a few disaster plans in my time. Why do you ask?)

Sleeping too well lately? Consider this:

If LetsEncrypt were to suffer a few weeks outage, how much of the internet would break?

It's the Sharepoint of chat.

I think your reply would have been more useful if you'd given some pointers about how, instead of just "do it right".