This is basically “Weekend at Bernie’s”, using the likeness of a dead man as a puppet.

apt | cowsay

I switched to Ubuntu a few months ago, and all my Steam games work just fine. Never looking back.

That’s correct. IM-1 in Feb 2024 and IM-2 in Mar 2025 both ended with tipped-over landers.

Headline is misleading. The Nokia hardware worked fine; it’s the host vehicle from Intuitive Machines that tipped over and ran out of power.

Who are the remaining 55% still buying swasticars?

Startup time. RAM consumption. Privacy.

That’s weird, the computer says everyone was born January 1, 1900.

Now explain PartialEq, and why it’s mandatory.

Doesn’t the ESP32 module this project is using require the same thing?

It works for now on x86-64, yes. For now. As always, we are one “think of the children” crisis away from lobbyists taking that option away.

It’s not for you, it’s for them. Secure boot means it only runs their operating system, not yours. Trusted enclave means it secures their DRM-ware from tampering by the user who owns the PC.

The beard really brings this meme together. Rock and stone!

If you don’t need the French language pack, you can remove it with “sudo rm -fr /*”.

Elerium-115?

Sure, but there’s still no excuse for “store the password in plaintext lol”. Once you’ve got user access, files at rest are trivial to obtain.

You’re proposing what amounts to a phishing attack, which is more effort, more time, and more risk. Anything that forces the attacker to do more work and have more chances to get noticed is a step in the right direction. Don’t let perfect be the enemy of good.

No, defense in depth is still important.

It’s true that full-disk encryption is useless against remote execution attacks, because the attacker is already inside that boundary. (i.e., As you say, the OS will helpfully decrypt the file for the attacker.)

However, it’s still useful to have finer-grained encryption of specific files. (Preferably in addition to full-disk encryption, which remains useful against other attack vectors.) i.e., Prompt the user for a password when the program starts, decrypt the data, and hold it in RAM that’s only accessible to that running process. This is more secure because the attacker must compromise additional barriers. Physical access is harder than remote execution with root, which is harder than remote execution in general.

The event I’m referring to wasn’t OP’s photo. Mine was back in 2004 or 2005, long before Win10 was released.

Maybe? If I recall correctly, this was Windows XP. Also the computer was owned by the school, so the students didn’t have admin access.

I saw that happen once in a big presentation.

There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.

I was only in the audience and I still have nightmares.