dack

FreeCAD definitely has a steeper learning curve and a few rough edges, but to me it was absolutely worth it to learn. I really don't like my files subject to the whims of Autodesk.

Sure, you can print minis with an FFF machine. But there's a reason the mini printing folks primarily use SLA. For that particular application, it's significantly better. I say this as someone who uses an Ender 3 and is quite happy with it. If my main goal was printing minis, I would probably want an SLA machine instead.

If your goal is to make mini figures, what you want is an SLA machine. They are much better at making small detailed objects than FFF. However, it will definitely cost more than a cheap FFF machine like an Ender 3.

The Ender 3 variants are cheap and a great platform if you are OK with tuning/tweaking things. If set up properly they work great and are pretty reliable. But of you want something that works out of the box and doesn't need any tweaking/tuning, you will probably be disappointed with it.

The TPM releases the key to the OS at boot time. Without that, there would be no way for the OS to load (assuming the root FS is encrypted).

The key is bound to PCRs in the TPM, which control under what conditions the key can be released. For example, it can be tied to secure boot, bios settings, etc.

Aside from the group suggestions, you could also use ACLs. https://wiki.archlinux.org/title/Access_Control_Lists

Arch Wiki for more general info. Official docs/man pages of whatever thing you are working with for details.

Removing orphaned dependencies every once in a while is a good idea. If these were installed as dependencies and are not dependencies anymore, this would get rid of them.

https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Removing_unused_packages_(orphans)

With rootless containers, even root in the container is basically useless anyway because it truly runs as a fake ID on the host.

I've seen this repeated a lot, but I'm not really convinced running as root inside containers is a good/safe thing to do. User namespaces can provide some protection for the host, but that does nothing for the rest of the files inside the guest. For example, consider a server software with an arbitrary file write vulnerability. If the process is running as a low privilege user, exploiting the vulnerability might not really get you anywhere. If it's running as root, it's basically a free pass to root privilege and arbitrary code execution within the container.

H264 does work fine in the paid version. The lack of AAC support is sometimes an issue though. For footage in AAC+H264, I usually just run it through ffmpeg to transcode the audio to PCM and keep the video as-is.

You need to install the CUDA package to use Nvidia GPUs in blender. This is in the arch wiki page for blender.

I think they already have. I held off on Wayland on my main machine for a long time due to Nvidia issues. For example, I was getting rendering issues where some windows/popups would be totally invisible until I moused over them. Those issues are now gone, and I've been running Wayland for the last few months with no problems at all.

Aside from the geometry nodes suggestion (which is a good one), have you looked into QGIS?