featured [he/him]

Professional audits happen for big projects, and hobbyists audit the programs they use frequently. In addition, some projects adhere to the reproducible builds guidelines, which ensures the packages you’re receiving are identical to the upstream repo. There’s more work to be done in formalizing and automating these processes but this isn’t a major issue by any means

Extremely dependent on a number of factors, mostly hardware and configuration. I had a Thinkpad T480 and on a stock fedora install it definitely died faster than W10, but after setting up TLP and Powertop I squeezed ~2 more hours of use out of it than Windows could manage. Ditto for my framework 13, I get all day battery life on NixOS but when I’ve tested windows on it I lose a few hours immediately

What’s the name of that robot ipod dog I loved that thing

I’d recommend checking out Distrobox, which allows you to create containers of other Linux distros then export their applications as if they were native. Install a distrobox with one of the distros that this program works with, use the terminal to install the program within it, then if it isn’t immediately in your applications menu use the distrobox export feature to place it there.

You could also layer Nix onto your bazzite image and install it that way, but if you don’t know Nix it’ll be complicated

I was using Nix but ran into some software compatibility issues so I’m back on Arch. It’s obviously not immutable and doesn’t have generations, but using btrfs + snapper + snap-pac + grub-btrfs has given me an automated system of snapshots that let me roll back to my system state before or after each package change (As well as weekly snapshots). It has been rock solid and reliable for me. On my Debian server I just use ZFS and snapshot it weekly, which isn’t as easy to roll back but it does everything I need

I use ntfy on graphene and it works just fine. I had to fully disable battery optimizations but that was it

Anybody use NixOS? I’m trying to run a regular Linux executable and I can’t figure out what packages to use in Nix-LD to make it work…

Isn’t Mozilla deprecating theirs soon?

It’s definitely a rabbit hole and it took me a few tries to stick with it, but after getting off the ground I don’t think I could ever go back.

Here are some helpful resources for using NixOS:

This video helped me understand the basic setup of flakes and home manager, as well as general NixOS syntax.

This site from Nix lets you look up every package on the repository, and if you click options at the top you can also search through every option related to your system and packages as well.

If you decide to use home manager for declaring user packages and dotfiles, I have been using this site which is similar to the official Nix search but specifically for home manager stuff.

Hope it helps :)

Helix text editor has been in my rotation recently, I like it a lot as a regular nvim user.

Just migrated from Arch to NixOS recently. Nix+Flakes+Home-manager define my entire system, including config files and pinned package versions, using three files. My system has never felt more stable and reproducible. I even found a flake which lets you declaratively manage Flatpaks (nix-flatpak).

If you use signal, the fork Molly has UP support now