Dave.

Especially after all the spam on Facebook like:

“RANDOM_FRIEND wants to get in touch with you on Threads™!”

“RANDOM_FRIEND just posted something on Threads™! Check it out!”

Etc etc

And then the interleaving of Threads™ teaser posts amongst Facebook posts with half a sentence and then “…” and any interaction with it prompts you to join threads so you can read the rest of that sentence that hooked you in…

Or the “easy and fun™” way that every Instagram account has a Threads™ account just waiting to be activated by you.

I wonder how much of a user base they would have without all the jamming it down user’s throats.

They should be able to put memtest on the boot partition and then break to an EFI shell on boot and Ioad it manually.

There will be a bit of swearing and googling required but it’s doable in a way that doesn’t mess with the current boot arrangement.

The bug is the lack of documentation and that a simple unguarded command can erase all user’s data on the system.

Also, the principle of least surprise would like a word.

If I look at the command line arguments of a program called “systemd-tmpfiles” and one of them is called “purge” I will generally assume that option will purge temporary files.

Now it turns out that someone decided that this program would be a simple way to do something with /home directories(*) so they included /home in the config file for the program, the file that the program reads by default when it is invoked.

Who decided it would be a good idea for it to deal with /home?

Wellllll…

https://github.com/systemd/systemd/blob/main/tmpfiles.d/home.conf

(*)I have no idea what this program is doing with /home in its config file. I will presume that there is a useful and mostly logical reason for it, and that this command line option was just an unfortunate footgun for those users who were not intimately familiar with systemd.

Pretty much.

Capable employees don’t raise a huge stink.

They quietly put the word out to a few people they know and play along until something interesting appears on the horizon.

Then when they’re good and ready they just “suddenly” fuck off to somewhere nicer for them.

Eh…Windows 3.1, 95, 98SE, XP, and 7 were all pretty great.

From a user interface perspective, they were okay, perhaps because by the time people got to XP they’d had a decade of a consistent interface and were just used to its quirks.

From a security context they were not ok. Not ok at all.