frankfurt_schoolgirl

Maybe you could just try a different Transmission docker image or build your own? Sounds like some weird instability in that particular version.

What do you mean by a file being displaced? Like do you want it to be unreadable, or unmodified, or just not deleted?

It's not really possible to have a level of protection that would require more than sudo because with root access you bypass anything else.

You could put the files on an encrypted volume that uses a special password when it is mounted. Or you could use the chattr command to set special ext4 attributes that would make it unmodifiable (but could be removed with sudo). Or just record the file's hash, and that way you know it hasn't been modified later.

It seems like that port needs to be accessible from the public Internet. Your local computer probably has at least one more firewall between it and the Internet, running on your router. You need to also forward the port on your router, which is what it says in the second half of the guide.

I've been using Wayland for 5 years. There were a few bugs in the beggining, but now it works great. These threads are such a waste of time.

I have over 100 confirms X11 developments

That's great dude. Why don't you go maintain it then, apparently nobody else wants to: https://www.phoronix.com/news/RHEL10-Removing-X.Org

Wayland took too long

Look up how long btrfs has been in development, or at audio subsystem churn. These things take time, because it's mostly volunteers working on them.

Systemic complexity has doubled in the last two years

What does this even mean?

Mir was better

It turns out the Canonical dumping random stuff over the wall is not the same as creating a legitimate open source community around a project.

Unfixable amount of race conditions

As if there's never been a synchronization bug in X... But also System76 and others are writing Wayland compositors on Rust anyway.

I mean xwayland is the best supported X implementation today, and will only get better. You're not ditching everything when you maintain backwards compatibility.

I think that it's a great project, and I hope it succeeds. My sense is that there is more momentum around Nix, so for a lot of uses it just makes more sense.

Guix and Nix both have the same issue imo, which is using a loosely typed language with an odd syntax. I feel like something both strongly typed and with a more common syntax would be easier to edit and faster to evaluate.

yeah if you're using unstable than it's rolling release and you just need to update regularly. the point releases shouldn't matter too much

You need to update your inputs so that you're using the 23.11 branch of nixpkgs instead of the old one. In my experience, a couple of things will break, but there's usually warnings about it.

Very few people do, you probably don't need to worry about it

there a way to know what your systems current shortcuts are

Not really, besides just reading the manual. I think this is a problem for the Linux desktop actually. I would love a standard way (dbus API?) for the DE and various apps to declare their key shortcuts, and then I could view them in a pop up when I'm using the app.

About Ansible, it's not declarative in the same way Nix is. The way it actually works is it executes little Python programs based on your config. But if you stick to the high level modules, it has a declarative feel. Also, the Python aspect is useful because you can include bits of Python to manage things like generating complicated config files.

I haven't checked out guix home, but it looks interesting. I have been doing some Lisp recently, so maybe the time is coming.

rootless containers

Are you managing dotfiles in rootless containers? IMO you shouldn't install nix in a container. If you want to customize your container, run nix outside of the container and tell home manager to apply itself to the container's file system (home-manager build will put the result into a result directory, which you can copy). Or, you could just mount your host ~/.config on the container maybe.

Ansible

Ansible is a big project, but at the end of the day it's just a Python package. If you already have Python installed, it's not really adding that much.

Also obligatory advice for anyone new to Nix: use flakes. Flakes are good and right. It sucks that Nix is in a confusing transition process to flakes, but if you just adopt them completely from the start it makes everything easier. Your home manager config can live in a single flake somewhere that you find convenient, and you can apply it from there.