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.
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).
Never heard of this “Papers” PDF reader before and it’s not on Flathub either. Apparently it is a fork of Evince with lots of big changes planned. Exciting stuff! But does anyone know what’s going to happen to Evince?
You can’t do that on modern phones with locked bootloader. This is the reason why manufacturers who allow bootloader unlock still don’t ship phones with bootloader unlocked by default.
Did 75Hz work with your previous OS?
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.)
This is not “just” a basic diffusion model we usually see. It’s one of the ControlNet ones. They do wonders. Here are some more examples.
Flatpak apps cannot set their own permissions “on installation”. If flatpak tells you some weather app uses only the network permission then that is all the app is going to get.
For an app to be able to change its own permissions, it first needs permission to the flatpak overrides directory. Any app that does this gets an “Unsafe” designation in gnome-software.
Also about most apps requiring filesystem access to work: I have 41 flatpak apps on my system (Silverblue so everything is flatpak). Only 6 have access to my home or Documents directory. (11 apps requested full filesystem or homedir permission, but 5 of these work perfectly fine after I turned off their permissions in Flatseal).
Notably, “large attack surface” apps like Thunderbird or Firefox don’t have access to my Documents. File uploads and email attachments go through the file picker portals.
Hetzner storage box is 3.81€/month for 1TB.
What I meant was that I want exactly Cackle, but I don’t want to run it on my own computer. If a crate uses some suspicious API (including transitively), I want to know before I download it.
Amazing project!
Would be cool if we also have an online database of what APIs each crate uses. This would allow quickly knowing some crates are safe without compiling them (there could be malicious build.rs code) or even seeing the source code at all.
No love for GNU IceCat?