Where are these OEMs that allow proper bootloader unlocking on most of their range?

Google, Sony …? Huawei stopped doing it, Oppo & Samsung doesn’t last I checked.

IIRC docker on Windows lives inside WSL, so everything is done on Linux anyway. What’s the issues you’re getting?

The typical way involves something outside your network acting as a proxy. Your home network VPNs to this proxy, then the proxy sends requests down to your homelab.

I used a VPS and a VPN, I would connect to the VPN endpoint on the VPS, and then route all traffic back down to home.

You can also run a reverse proxy on the VPS, so it does TLS for clients, and speaks to the servers direct over the VPN.

Another option is things like Cloudflare tunnels, which means cloudflare does the “VPS and VPN” part of the above, but the tradeoff is that your have to trust cloudflare, rather than yourself (may be a positive or not depending on your perspective).

Lastly you could use something like tinc (which needs something on the outside to act as a negotiator) to form a mesh between NAT’d devices.

There’s mt32-pi, a baremetal app that emulates the classic MT-32 MIDI synthesizer.

For better or worse, the Pi (2+) seems to be the only SBC with a video output that can do 240P or other funky CRT resolutions (the DPI interface on the GPIO).

(If you buy a suitable device) You don’t have to use the preloaded OS (see Graphrne, Lineage etc).

gedit in native Linux or WSL2. use it for Ansibke, python, C, bash, basically anything I need to edit. Has a git plugin, bottom terminal pane, left open files / current folder pane. Does all I need it to do, and it’s not a huge fuckoff electron app.

I’m pretty certain that the USB IF decided to use the max possible Gbps as the cable rating, rather than the mess that was

USB 3.0 USB 3.1 USB 3.1 (Gen 1) USB 3.1 (Gen 2) …

So it’s more likely apple are just being specific in the type of cable you need.

Landing gears are usually designed to drop by gravity (or manual hand cranking) alone if there’s a hydraulic failure.

One thing that people miss - either out of ignorance, or because it goes against the narrative - is that systemd is modular.

One part handles init and services (and related things like mounts and sockets, because it makes sense to do that), one handles user sessions (logind), one handles logging (journald), one handles networking (networkd) etc etc.

You don’t have to use networkd, or their efi bootloader, or their kernel install tool, or the other hostname/name resolution/userdb/tmpfiles etc etc tools.