DivestOS sounds interesting but I am wary of any “mission-critical” software project (such as the firmware for my primary phone) that relies on a single person, for multiple reasons. Burnout and potential for social engineering by malicious actors being two of them.

GP:s comment made me curious as well. Usually, if multiple hardware vendors are supported there are separate branches with different maintainers. It doesn’t necessarily mean that the main codebase is bloated as a result.

For those that are looking to install GrapheneOS and want to ensure that their banking apps work as intended, here is a curated list of supported apps per country:

https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/

CPU vulnerability mitigations would typically be distributed with the intel-microcode package for Intel processors on Debian-based distributions, for example.

And QubesOS isnt based on linux kernel. It uses Xen. Linux is used in the Qubes aka VMs.

The dom0 is very much running a Linux kernel, the same way your domU:s are typically running Linux kernels (although you could probably run any kernel in hvm mode).

As an example, here is the documentation on how to manage updates for the dom0 kernel:

https://www.qubes-os.org/doc/how-to-install-software-in-dom0/#kernel-upgrade

Hadn’t heard about deSec until now, seems to be run by some cool privacy minded folks in Germany:

https://desec.io/

I guess you already know about the options, but for others:

Find the cheapest VPS out there and have a Wireguard tunnel between it and your home network. Run ddclient or similar on the VPS in case the public IP changes.

They went crying about WPEngine having found a good business model around Wordpress support, and started sabotaging for them.

https://www.theverge.com/2024/10/2/24260158/automattic-demand-wp-engine-revenue-wordpress-battle

Looks like they lost in court a few days ago!

https://www.theverge.com/2024/12/10/24318350/automattic-restore-wp-engine-access-wordpress