git gui is nice for this.

(or jj split).

For Rust, return Result<> , as is idomatic in Rust.

Another possible method is having an installable handler that handles the error at the place it is detected. Common Lisp does that and it is very powerful.

OK, now you are talking about something a bit different - registering own keys in the UEFI system, which is significantly more involved than updating the BIOS, and also requires firmware support, and the firmware also needs to match the motherboard. And the whole issue with ACPI support for Linux shows clearly that having reams of specufications is not enough, the implementation of the BIOS needs to match that specification which whether thsz’s the case you will only learn after you bought the hardware.

Here is a description of that process:

https://docs.bell-sw.com/alpaquita-linux/latest/how-to/use-own-keys-in-secureboot/

Moreover, for any change of the boot chain, bootloader, posdibly also kernel, this needs to be repeated.

Do you think that’s accessible to normal users? Considering most have probably not even ever done a firmware update?

That said, I’ve always just enrolled my own keys.

That does not help if the master key in the key chain is expired.

Sure you can disable Secure Boot. But a password-protected BIOS is secured by TPM again. High levels of security always carry a risk of locking oneself out.

So, Google was perhaps slightly terrified from the specter of an Internet without advertising, haha.

I honestly don’t understand how this protocol can protect anything HTTP+HTML wouldn’t. If you build a browser that supports modern web technologies using Gemini, we’ll be back at the same spot. The only thing saving the protocol is its relative obscurity. A decicated and knowledgeable Dev could abuse it any way they like, no?

No. Just as examples:

• If the protocol does not support JavaScript, the server cannot ask the client to run script code which strip-searches your computer for fingerprinting information.
• If the protocol does not support tracking pixels and inline images, a server can’t use them.
• If the protocol transmits only text, the server won’t know width and height of the screen, or names and geometry of your set of fonts.

Oh, and all that makes the “small web” uninteresting for advertising.

Of course, you could publish a blog in web pages which consist of plain ol’ HTML like in 1993. But setting up even a simple HTTP server is a lot of work. Most users won’t turn off JavaScript. And to many people, the modern WWW is a lost cause. And given Firefox’ dependency on Google, this isn’t to get better.

still not sold on gemini. the project has sort of a holier-than-thou smell to it, striving for the sort of technological purity that makes it unattractive to use. i would still choose gopher.

Does it annoy you when people try and make stuff that matches their values?

More comfortable with the killings that FB contributed to in Myanmar or in the Philippines? Or attacks on democracy like this one?

The power concentration of the “modern” Internet has consequences - and not good ones.

But me personally, even if it would not matter to me what effects power concentration, targeted advertising, disinformation and so on have, it still would annoy the hell out of me that one cannot open some web sites on a two-year old medium priced smart phone because everything is stuffed to the brim with bloat and tracking.

Well, my main reason to use Zim Wiki and Gollum is that all the information stays on my computers -no sync service is needed, I sync via git + ssh to a Raspberry Pi that runs in my home. And this is a critical requirement for me since as a result of many experiences, my trust in commercial companies that collect data to respect data privacy has reached zero.

The differences between Zim and Gollum are gradual: Zim is tailored as a Desktop Wiki, so each page is already in editing mode which is slightly quicker, while Gollum is more like a classical server-based wiki, which is normally accessed over the browser (but by default, without user authentication). The difference is a bit blurry since both just modify a git repo, and Gollum can be run in localhost, so it is good for capturing changes on a laptop while on the road, and syncing them later. A further difference is that Zim is a but better for the “quick but not (yet) organized” style of work, while Gollum is better for a designed and maintained structure.

Both can capture media files and support different kinds of markup, while always storing in plain text. Gollum can also handle well things like PDFs which are displayed in the browser, and supports syntax highlighthing in many programming langages, which makes it nice for programming projects - it is perfect for writing outlines and documentation of software, and I often work by writing documentation first.