This. I’ve had issues at work while imaging classroom computers where some would finish in ~30 minutes and a few would need hours. All of the computers used Cat6 cables. This being a classroom, and students being absolute wankbags, they kept yanking the computers and kicking the cables, so the wires came loose from the plugs. I later used ethtool to debug the slow computers – the switch would only allow 10baseT link modes.

I just simply set up a script to export my Trilium notes

edit the notes with an external editor, and then you can just re-import the note

Those two lines right there.

I value interoperability between software. Using a container format to store plaintext files and metadata introduces an XKCD 927 situation where it’s just another reinvention of the wheel that requires additional software support or a whole other workflow for no real benefit. Why is it necessary, for example, to store plaintext data and the related hierarchical structure in a container format when the same feature is already present in the filesystem with files and directories? It adds unnecessary complexity, roadblocks, and points of failure.

I’m using QOwnNotes at the moment. If I want to edit a note, for example, using neovim through SSH, all I need to do is navigate to the markdown file and open it. No scripts, no export/import. Only text files, and that is all it ever needs to be.

They all offer more or less the same network services with different UIs.

OpenWRT is specifically designed to work as a lightweight system running on consumer-grade routers. If you want this, you’ll have to check the website’s Table Of Hardware to determine if your hardware is compatible.

OPNsense and pfSense are general-purpose FreeBSD-based operating systems that you can run on discrete computers or in VMs that act as network gateways. All three are free/gratis, but you have to make an account and go through the store page to download pfSense.

I personally use OPNsense in a VM.

Damn, I had no idea netcat had a hardware implementation