Extremely dependent on a number of factors, mostly hardware and configuration. I had a Thinkpad T480 and on a stock fedora install it definitely died faster than W10, but after setting up TLP and Powertop I squeezed ~2 more hours of use out of it than Windows could manage. Ditto for my framework 13, I get all day battery life on NixOS but when I’ve tested windows on it I lose a few hours immediately

What’s the name of that robot ipod dog I loved that thing

I’ve been into NixOS recently, not sure if I’m gonna stick with it long term but I’m trying to make it work. I love that it’s immutable while still allowing system packages, and declaratively configuring all of your common programs with home manager is super cool. Just have issues with scripts from the internet and trying to get nix-ld to cooperate

Hopefully they rethink this. I think adding a simple donation method for applications within FDroid would be beneficial and would support developers, but creating another for profit market for apps with the shitty subscriptions, paid apps, etc goes against the goals and spirit of FOSS

Play integrity api is implemented by some app developers to check OS integrity. Google blocks all third party OSes from utilizing this verification method, including GrapheneOS. This isn’t new, what’s new are the apps that utilize this integrity API which is where the story comes from. Most apps still work without it. Graphene has full support for hardware anttestation and they’re pushing for this to be the norm rather than relying on Google as the gatekeeper. I use graphene every day, and while I mostly use FOSS apps from other repos, the stuff I personally use from the play store works perfectly

It literally doesn’t do that

I mean yeah it does include data scraped from the web but that is all three years old at this point. Hardly a search engine by any metric

It’s not doing live queries at all, it just makes a statistically likely answer up from its training data

They’re mostly in SBCs and dev systems right now. I know StarFive makes RISC V SBCs, and I think Pine64 has a RISC V tablet and SBC available. It’s all pretty low end and intended for dev work from what I can tell though

Well Rocky can contribute, but they’d have to send their patch to CentOS stream and hope it gets merged, then wait for Red Hat to implement the changes. So it’s more roundabout and ultimately is dependent on Red Hat

Isn’t Mozilla deprecating theirs soon?

It’s not nearly as supported. There are workarounds where you can create a ~/.gtk4 directory and modify CSS yourself, or you can use a program like Gradience to modify the color scheme in an accessible way. Gradience also has community color palettes so if you’re using a popular theme it could just be a matter of loading the preset