The entire bazzite build process is well documented, the entire pipeline is implemented with standard CNCF and OpenSSF tooling, the readme has crypto verification that you can run to verify it yourself. These systems have been in place since before Universal Blue went GA (It’s about 5y old).
Fedora being a better choice than Homebrew because it’s update pipeline is too slow is not something anyone should be proud of. The Bazzite images run full syft scans before they’re even finally assembled, if it’s in there that second the build fails and users never see it. The entire industry is moving left on this, with proactive work upstream - “keep old things in the field” is an antipattern.


This is pure operator error, all of these systems are well documented and are literally linux 101. If the response is “how are normal users supposed to?” the answer is normal users don’t use command line tools.
The person saying that they’re switching to Kinoite is in for a rude surprise when they find out that the virt-manager flatpak everyone is migrating to is written and maintained by the Kinoite maintainer, we helped with the QEMU extension because moving this stuff to userspace is something everyone agrees on.
Hopefully you’ve learned that there are people that claim they need super technical things like virt-manager on the image and yet can’t manage a simple linux service. “Forced Updates”. Images like Bazzite are the antithesis for people who want to be experts without putting in the work.