fambalamboni

Nice. Anyway to batch convert it all to ePub?

I use screen all the time in an SSH session. Locally, not so much.

Although if I'm running something that I know will take hours, I tend to run that in Screen because I'm likely to nuke the terminal by accident.

> Stopped because it didn’t have the “CI tested” flag: low pri.

Agree, certainly lower priority than the "caught by chance" case, but I wouldn't say "low priority". That system is the last line of defence and the fact that something is hitting it is definitely a large concern.

In the CrowdStrike's fiasco last year, their last line of defence, "Content Validator" failed.

"On July 19, 2024, two additional IPC Template Instances were deployed. Due to a bug in the Content Validator, one of the two Template Instances passed validation despite containing problematic content data."

https://www.crowdstrike.com/falcon-content-update-remediatio...

The article is spot on. It's pretty much what happened when Maersk was hacked within an inch of bankruptcy.

The flaw was identified, flagged and acknowledged before it happened:

"In 2016, one group of IT executives had pushed for a preemptive security redesign of Maersk’s entire global network. They called attention to Maersk’s less-than-perfect software patching, outdated operating systems, and above all insufficient network segmentation. That last vulnerability in particular, they warned, could allow malware with access to one part of the network to spread wildly beyond its initial foothold, exactly as NotPetya would the next year."

But:

"The security revamp was green-lit and budgeted. But its success was never made a so-called key performance indicator for Maersk’s most senior IT overseers, so implementing it wouldn’t contribute to their bonuses."

Basically, a near miss that wasn't incentivised for anyone to fix.

If you're interested in this type of story, it's an absolute thriller to read: https://archive.is/Gyu2T#selection-3563.0-3563.212