267 karma · joined June 17, 2022
Step 2) some drunk invents FTL
Step 3) the Vulcans show up
You're complaining about timely security updates?
Could you share some examples of how the old systems did this?
In practice, everyone writing new projects uses it, but when you choose to interact with existing code...
I'd recommend adding OpenGenera and IBM's systems I and Z to that list: a whole bunch of us build careers out of unnecessary unix make-work too
Yeah, some DE clipboards implement kill-yank sensitive. They're great!
At least back in the POWER8 days those z/Linux systems were the fastest you could buy, and IBM was super happy to let you overclock them: their reps told me that was just more CPU sales for them.
Kill-yank semantics give you a full kill-ring, that's what your yanking from. CUA gives you a single copy-slot.
(As an aside, I've been very happy to see you are still involved with the project!)
> GrapheneOS has a built-in encrypted backup system
Do you mean seed vault? It's really not satisfactory. For one, I should be able to encrypt my backups with any key of my choosing, on a hardware token if I so choose, not be forced into its silly codeword system or nothing at all. AES, gpg, and X.509 compatible support would get you all of the way there.
Even just letting backups be exported unencrypted, so I can easily and automatically use a trusted device to encrypt it the way all my other data is would make it so much more usable.
Frankly, the current implementation just reads as one of those ridiculous things trying to force the uneducated/uninterested to be secure, with no escape hatch for people who actually know what they are doing, nor for enterprises who need secure mobile devices, but also know an end-user will /never/ successfully take a backup on their own.
I did it the other way, and going back to elisp is /hard/.