Please god a few internal features leak into the open source.

Great going. Excellent.

Please can you explain how to install it in LibreOffice. I’m not sure that I can as I saw https://github.com/Automattic/harper/issues/1427

that’s unrelated - AES-256 for example can be executed just fine on either a 32- or 64-bit machine. in theory there’s nothing stopping you from running it on an 8-bit or 16-bit CPU (although other considerations related to the size of AES’s lookup tables make this unlikely). from some random googling, here is an implementation of Chacha20, another 256-bit encryption algorithm, for 8-bit microcontrollers.

I started out programming a 6502a in 1980, 680X0 a little later in 87, so I get that bit, but it’s easier doing operations on a larger register. I remember writing code for 8 bit multiplication of 32 bit floating points.

I enjoyed and understood the rest of your prose though. Didn’t do much/any programming/low level after say 2005, and regret it now. Trying to re-learn but things have moved on so much.

I take that there isn’t much motivation in moving to 128 because it’s big enough; it’s only 8 cycles (?) to fill a 512 (that can’t be right?).

Thank-you a lot for that. I wander around the tech blogs like lobsters etc, Reddit and here but never see anything that i remember seeing (if you follow me), but I don’t consciously look.

Encryption lengths are getting long so you’d think it was high time.

Your description sounds like the advent of 32 bits where there was a 16 bit address bus stage.

Whilst other distros move to a Weston (corrections please?) era Intel x86 2013 ish?

Bravo, I think. That’s going to be tough.

On a related track, is there any talk of 128 bit chips in general?

When you’re naming a file, you can’t use anything else.

The Google Files app will find duplicates and other things.

Thank-you for this. I have a Google Alert for rust cli but many of these have been missed.

If you’re running Linux with the French language add-on installed, you can delete it:

rm -fr /