And extracting a fuck tonne of sensitive data

I get frustrated with the track pads. Sometimes they click, sometimes they drag, sometimes they right click. I know its number of fingers and pressure/speed of clicking? I’m sure it’s great if you learn it, but nobody else has adopted it.

Oh, and 2 programs side by side and you have to jump between menus of both of them for whatever reason. The whole “1 menu per desktop” is frustrating

I’ve given this a read.
https://homelabstarter.com/homelab-networking-basics/

Covers the basics, explains them well & technically, and points to “further learning”.

I’d start with learning some networking basics.
Subnets, default gateways, DNS, routes, VLANs.

Then get another computer to install proxmox on.
Learn VMs, SSH, firewalls, basically Linux. Probably VPNs as well.

Then set up a VM and play with docker & docker-compose.

And that’s most of the tooling to be able to self host anything. A VM with docker, set up the docker compose of what you want, boom: done.
Some projects are more of a “full of” kinda thing (like home assistant), which would be its own VM

Yeh, exactly.
And the “dynamic DNS” part handles your public IP address changing with 0 pain.
You either buy a domain (like example.com), or there are free domain name providers that give you a subdomain (like mycooldomain.example.com) of one of their domains.
You then run an additional service on your home server that checks what the current public IP address is. If it changes, it notifies the DNS responsible for your domain/subdomain, which then points to your new public IP.
To connect to your VPN, you only ever care about “mycooldomain.example.com” and never the underlying IP address.

…
As long as your ISP isn’t running CG-NAT of course 😵‍💫

Is it decoupling content from presentation? I bet it’s decoupling from presentation.
Which is why LaTeX is so popular for scientific papers.

Although I struggled to read the article.

Yeh, but is extremely outside of any manufacturers control for consumer level gear.
For mission-critical satellites or space crafts, then it’s either a 3-way-quorum or extremely ruggedised processors specifically designed for the radiation of space (with a massive performance penalty).

It’s not something you buy off the shelf. It is a specific requirement that is built in at all levels of hardware, firmware and software.

So, if the steam machine is designed for high radiation environments then it’s steams fault.
Seeing as it isn’t, a cosmic bit flip that is actually able to impact hardware negatively is so extremely unlikely that it isn’t Steam’s issue. At all.

Free as in “free at the point of service”.
Of course it is paid for somehow.
But as far a a someone going into a hospital to get a cast, medicine, birth… It’s free

I always think about using nixos. But considering I dockerise everything, I always end up using Debian.
Good old stable Debian