I've seen an S3 option in Smokeless_UMAF, so maybe you can enable real suspend, but I haven't tried on my Framework 13 AMD.

Most thermal paste isn't electrically conductive, so that blob inbetween the capacitors shouldn't be an issue, but it would be good to know what thermal paste it is to be sure.

This format's from 2017 I'm pretty sure.

https://hepwori.github.io/execorder/

Yes, but it doesn't look like KPROBES_ON_FTRACE is supported on arm64. I did find this patch though which implements it: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20191218140622.57bbaca5@xhacker.debian/

If you don't know how to apply a patch, you can either paste the link into b4, or download the mbox and apply it with git am.

Could also be slimline sata.

Probably a long shot, but if you live in Australia (or maybe also New Zealand), Jaycar often sells the Ender 3 V3 SE for AU$250, which seemed like a really good price compared to other places I found.

The options that start with HAVE_ usually depend on the arch or compiler. I don't believe it's possible to enable manually without modifying the source itself.

After reading their blog, it seems like it doesn't support Python 3.12, and it looks like you're using Python 3.12.

Also if you tap on the 'kebab' menu and press View Source, you can copy the message.

On Asus motherboards you can enable 'Memory Context Restore', and it'll remember the training. Unfortunately it seems rapid changes in the weather make my system unstable with it on.

Total Commander

I've started recommending Amaze, it's free, open source, and easy to use.

Although I still use Solid Explorer for myself, but only because I've paid for it and know how it works.

Both have SMB support, since copying files to and from my server is pretty much my only need for a file manager.

You're right, unless there's some vulnerability, /var/www isn't accessible by visitors when /var/www/html is configured as the web root in nginx. However if they are files that visitors shouldn't access I probably wouldn't put them in /var/www, but I guess at least you could chmod them like the previous commenter said, so that nginx can't read them.