

How are bazzite or nobara not open?


How are bazzite or nobara not open?


This. Although not enthused with the all in use of AI tools, I dont have a problem with it being used to generate code. So long as a human is responsible for the PRs that go into the project. The bigger issue is the push around sacrificing proper security posture and process. As I’ve said else where, for a company that sold me and many based on their security and privacy stance, its an odd position to take, and probably why I will be moving on closer to my subscription end


Rust builds a unicorn


I followed the compose file in the docs with podman and it was fine, configured headplane as the management gui inside the same compose. I then later converted the compose to a quadlet and it continues to be fine. I leave it alone, it leaves me alone


I think this lets you host that management connection yourself.
No, but if you wanted to do that, headscale is the answer


oci repositories support signing artifacts, container trust policies are a thing. bootc repos are both signed and are distro repos, ostree Fedora and ublue are using it
Just because quay.io or hub.docker can be accessed without signatures or trust doesn’t mean there aren’t repos out there using it.


trusting an oci repository is the same as trusting a distro repository, if its a dodgey unknown you got from god knows where and you cant verify, dont use it


They will run a Rosetta like VM to keep old apps running
Nah they’ll make you get a Windows 365 subscription to keep running incompatible apps in an Azure VM, gotta wet their beak


This is what happens when you let someone vibe code your distro’s config
yes that is the cynical take, and I mostly agree, but installed apks list their install source, so if that information is there, then its simple to give the user the ability to mark said source as trusted. But to do this under the guise of security, when there is more malware on play than fdroid is such a head scratcher
I just want to know what is going to my fdroid apps when this comes in. Will they all get binned? Disabled? Just fail to load until I jump through the new “untrusted” sources hoops?
What gets me is that upstream linux has had this solved by trusting repo keys for years, why not let the end user be the trust arbiter
Atomic distros are no less open, its just a different workflow