I think one of the troubles is deliviring the therapy, because generally the brain is protected from virii reaching him.

With SD cards relatively cheap I long thought about, why delete them at all. Just put them into a box after importing the images/when full. So you still have a physical backup.

Because it's a waste of money, space, effort, and nature as well as an unreliable backup that gives you a false sense of security. As well as a good way to leak information.

But yes, keeping the cards for a while and rotating a large pool can be a good approach. When they're in actual reliable ro-at-rest, checksummed, possibly encrypted, offline backup, the cards can be reused. (Always format in device etc.)

Modwiggler changed name around the same time.

From what to what?

Original name: muffwiggler

In the beginning I had my Obsidian folder in my iCloud, but had not so happy experiences regarding the conflict resolution.

moricons.dll is also still around. https://devblogs.microsoft.com/oldnewthing/20250507-00/?p=11...

A few years ago, before the great System Settings revamp, I saw a post of system settings dialogs that had a 1:1 lineage back to NeXTStep.

I tried to copy some files once. I was unsure about the syntax of "cp" and my sleep deprived brain did neither remember to just try "man cp", nor when I searched via Bing to add "syntax" to the search term "cp". This lead to a very stern warning, that let me wonder if I'm on a list now...

> Most people will never need a Quinolone

At least in Germany eye doctors are very happy to prescribe them. It's "only" eye drops, but it is (for laymen) almost impossible to find information if they are also dangerous in this form.

Ok, but how do you call what we are doing:

We have an interpreted language in which you can call "subroutines" by name. But you can build the name in you program "on the fly", for example out of data.

I'm sure this is a naive take, but why is it not possible to enter a new key into the BIOS (dating myself, I know it's EFI) by hand?

It's possible and it's what you should be doing. "sbctl" (https://github.com/Foxboron/sbctl) AFAIK has a reasonable frontend for doing that on Linux (don't know, I did it manually). You have to put the system in "secure boot setup mode" in BIOS/UEFI options before booting, which enables changing the PK (Platform Key) which is used to chain off all the other keys. (Setup mode should be automatically exited when you install a new PK.)

You can keep the Microsoft keys in there if you want to dual boot Windows, you just need to re-sign the keys themselves with your own PK.

It should be, at least on higher-end boards, no?

You'd have control over what boots on your computer then...

you literally have though. you can self sign everything and set up uefi to only boot your signature

Only on x86 secure boot implementations. On most devices with trusted boot, you don't have this option.

uefi on non x86 is a non starter for most people anyways. not that uboot is better

That would be a disaster. Or imagine what would happen if you just disabled secure boot, your computer will be infected with viruses and your bank account emptied instantly I reckon

Secure boot doesn't stop user-space malicious activity.

I'd argue that it only helps check a tick box on corporate security manifest, as it indicates the kernel being booted, is not tampered with.

OP was being sarcastic