Sorry to say, but there’s a lot questionable stuff found within your comment. But I will try to limit the discussion around some of the more egregious ones.

Hate to keep litigating this around here, but the shift alone is enough. Explaining to people WTF an immutable filesystem is, is a sure way to frustrate them into giving up, despite whatever comms finesse you might THINK you have.

I don’t understand what’s so hard to understand about (some) core system files being read-only, i.e. you can’t change/modify it. Can you help me understand why that would cause so much frustration?

Counterpoint: STOP SUGGESTING IMMUTABLE DISTROS TO NEW USERS

Countering the counterpoint with an anecdote: I cold turkey switched from Windows to Fedora Silverblue almost 4 years ago. Beginner-friendly derivatives like Bazzite (or other uBlue images) weren’t even around back then. And, somehow, I managed. And there are many other testimonials that point out something similar, especially with many^[1] newbies appreciating Bazzite. Are you ignoring this empirical evidence? If so, on what basis?

there is ZERO benefit

Come on, you know that’s not true. Perhaps you intended to write: “I suppose there is ZERO benefit to me (and others like me)”. Though, if you genuinely don’t know any, then please consider going over this (lengthy) blog post by Colin Walters, a key figure in the past and current development of Fedora Atomic and Fedora CoreOS. It’s not a very efficient writing for educating oneself on this topic, but it’s the best I know.

I agree with this in general. But, I’d like to add that well-supported hardware (like a ThinkPad) may do equally well on Linux and perhaps even better.

what software do people pirate in linux?

It’s a great piece of software. As such, I wouldn’t want to harm them. Hence, I won’t give you any pointers. Sorry not sorry.

I’m obviously not an expert. But, from what I can tell, the scene seems quite healthy. And I don’t see a reason why it wouldn’t thrive further. Especially as the Linux market share is in the lift. Anti-cheat shenanigans are a lot more concerning. Though, I’m optimistic that Valve is actively making progress on that front.

Btw, just as an FYI: I know people that were more interested in software piracy. But I digress…

Vague statement. Please, fam; either be more explicit from the get-go. Or, engage with the comment section.

I suppose you meant the piracy that involves games and/or software. FWIW, I’d be more than happy to elaborate if you could clarify.

Ah…, the conundrums of subjective morality.

programs

Consider being more explicit about what you want/need. Some programs work great with wine and others have never.

Thanks for the quick rely!

Maybe this is relevant for some

That is very tangible, indeed. And kudos for providing the only browser that aced the ‘test’!

Also, pull requests attempting to improve the documentation are very much welcome. Would be great to get more contributors involved and one doesn’t have to be deeply technical to write good docs.

Hehe 😜. I do admire your work, but don’t get your hopes up 😅.

Anyhow, I will add it to the list of Firefox(-based) browsers worth looking into. To be clear, I’m not a primary consumer of the product category. FWIW, I would install it on my system if I were*.

In the now up-to-date README.md we find the following line:

A couple of privacy-related patches not built elsewhere

Cool. But…, could you name those explicitly?

Mullvad Browser is also based on Firefox ESR and is the product of a joint development involving both Mullvad and the Tor Project. Could you please explain why anyone should consider Konform Browser over it?

My priorities:

• Secure. Unlike popular belief, the fact that the worlds infrastructure basically runs on Linux does not imply that your average Desktop Linux distro enjoys the same level of scrutiny when it comes to its security. Hence, the security-conscious should carefully pick a distro that can handle their threat model. Or, at least harden it to their liking.
• Stateless. Conventionally, you will be met with a (relatively) minimal system after installation. After which you’re expected to configure it to your liking and go smooth sailing afterwards. Occasionally, you might (un)install stuff and/or modify settings; but nothing out of the ordinary, really. While applying some of these changes might seem trivial, they (kinda) lead your system to accumulate cruft. This cruft might seem innocuous, but it’s exactly why your system seems so fresh after a reinstall. Foregoing this altogether is referred to as going stateless. This is done by declaring a desired state and ‘flushing’ all changes that have not been declared. Many other benefits are associated with this, but I digress…

The above^[1] already dictates the use of NixOS with the impermanence and nix-mineral modules.

I was actually seriously considering to just write “Freedom” and call it a day. Apologies for making it more wordy than it has to be.

Freedom, it’s that simple. Any other reason is a derivative of said freedom.

There are already many good answers in the comments, so I don’t feel the need to add much to it. But perhaps the following is worth mentioning:

• Fedora has got enough agency to continue efforts in what has been abandoned by Red Hat. Or, vice versa.
  • For example: it has continued to offer Btrfs as the default file system, while Red Hat has long since deprecated it.
  • Or, conversely, Red Hat has big plans for bootc. And while Fedora has done a decent job with Fedora Atomic, it certainly does not enjoy the resources and commitment it deserves; a pretty bad regression for (at least one of) the Fedora Atomic images was not considered a blocker for one of the more recent major release updates. Heck, it has become so bad that even the likes of both CentOS Stream and GNOME OS have shown to be more receptive when it comes to addressing problems and whatnot.
• It has been pointed out that Fedora would probably not survive in the event that Red Hat would cease ‘its support’.

Glad to help out 😊!

Thankfully the model forces upon the system to keep a pristine copy around. Which enabled us to fix this rather easy :P .

Did you try rpm-ostree reset ?

EDIT: The solution provided above ‘could’ perhaps work, but perhaps it’s way too radical of a solution 😅 …, so I understand if you don’t wanna go down that route. Instead, consider

sudo cp -a /usr/etc/containers/policy.json /etc/containers

as per this comment on github.