Yup.

After reading a ton of discussions and inevitably trying out many interesting text editors (including niche ones like Leo and Sam), I just had to give it to Doom Emacs. Been very happy with it ever since.

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^[So, without even going into release cadence etc.] already dictates the use of NixOS with the impermanence and nix-mineral modules.

Does anyone happen to know the state of Wayland on Linux Mint?

Domain-Specific Language. In the context of NixOS, that would be the Nix language.

Let's hope places like Lemmy stay relevant, vivid and slop-proof.

The article unfortunately does a horrendous job at highlighting AerynOS' unique features by only giving vague descriptions without going into any technicality that matters.

FWIW, my two cents on AerynOS:

• It offers (yet) a(nother) novel approach to atomic distros. The gist for its ambition (or, at least, my understanding of it) would be NixOS, but with FHS intact and without a DSL.

The article unfortunately does a horrendous job at highlighting AerynOS' unique features by only giving vague descriptions without going into any technicality that matters.

FWIW, my two cents on AerynOS:

• It offers (yet) a(nother) novel approach to atomic distros. The gist for its ambition (or, at least, my understanding of it) would be NixOS, but with FHS intact and without a DSL.

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.