Anything that’s updated with the OS can be rolled back. Now Windows is Windows so Crowdstrike handles things it’s own way. But I bet if Canonical or RedHat were to make their own versions of Crowdstrike, they would push updates through the o regular packages repo, allowing it to be rolled back.

They will upstream stuff, but sadly they are not going to mainline.

https://mastodon.social/@GranPC/112690143171368646

No. It uses Hallium (Android kernel, basically).

It’s already delivered - a Mastodon user got one.

But getting an OEM to make a phone under your brand is easy. The real question is how long will they keep the software maintained?

These people seem like passionate Linux enthusiasts, so one can hope.

According to the Librem people: this is Android kernel (& other low level stuff) with Debian userspace, not a true Debian phone. https://social.librem.one/@dos/112686932765355105

WINE Is Not an Emulator and there is no Windows on RISC-V.

We could take this further and let developers specify exactly the dependencies they need! No more bloated runtimes! App A could specify libfoo>=1.23.45 while app B specify libfoo<1.24 and Flatpak could resolve the compatible version automatically!

Serious answer: If space saving is the goal, traditional packaging is the way to go. Allowing multiple runtimes is a slippery slope away from the core idea of Flatpak (simplest dependency management possible so developers don’t have to test many configurations).

(Not that there’s anything wrong with traditional packaging with more complicated dependency management - it’s just not Flatpak’s thing).

Looks nice! Is this yours (OP)? If so, are you aware of Bavarder? It seems to have quite some features. (But it is unmaintained and broken right now so Alpaca is a welcome replacement.)