Only the kernel module is open source, and it’s just a wrapper for closed source blobs.
In actuality the open source drivers just kill all support for the 10 series, and otherwise do nothing to fix Nvidia’s utterly fucked up driver problems.
Which btw also include the Fedora Flathub repository.
We no longer touch the repos as Fedora is now in agreement with using Flathub.
You start to sound like a GrapheneOS dev. It makes no sense to prevent users from reinstalling removed packages.
It’s for user security. I have no interest in debating this decision, my reasons are outlined.
Distrobox updates automatically on Bluefin and Bazzite.
In this case we disagree with Fedora, Atomic Fedora should not have Firefox in image. It does not matter to us what they do, we explicitly remove it.
If you like the way Fedora builds their Firefox RPM, that’s all the more reason for you to use a fedora distrobox.
I shutdown my laptop every day and update every day. That is fine for me.
Irrelevant. Not everybody does. Some people pin an old image due to a bug and sit on a far older image. If you had it your way, they’d be using a week or month old build of Firefox – that’s unacceptable.
Removing Firefox prevents people from reinstalling it
Good. I can promise you if that gets fixed and I have a way to continue to prevent it, I will.
Flatpak Firefox does not have the ability to create user namespaces for tab process isolation. This is due to all Flatpaks using the same badness-enumerating seccomp filter, there is no additional hardening possible and they still block userns creation.
This is an issue for Mozilla. They are happy enough with the state of the Flatpak to not only verify it, but list it on their website. Unless you’ve got a CVE for the Flatpak version of Firefox I don’t see any point in even engaging with this argument.
We remove Firefox because having it on the image is a security hazard. You want your browser to update more often than your operating system.
We prefer the flatpak, but if for some reason you need the RPM I would suggest installing it with distrobox.
We build twice a week, that’s not frequent enough for a web browser.
Ultimately it’s saving you from yourself, if this bug gets fixed and there’s a way I can unfix it, I will do so.
If you need RPM Firefox, my recommendation is that you install it with Distrobox. This also solves the security issue that we remove upstream Firefox over - update frequency.
You don’t want Firefox to only update when your operating system image does. As far as I’m concerned the bug preventing Firefox from being re-added is a feature.
They all try to share patches and ideas too, if there’s competition - it’s friendly.
For that, check out Bluefin or Aurora. They’re all under the same umbrella as Bazzite, but with a user/developer focus instead of a gaming focus.