It can be just like you’ve said. You can also run tailscale directly on the system hosting a service and access it directly over the tailscale network.

It still bothers me 30 years later that in the DC vs Marvel, Wolverine beat Lobo… Shouldn’t have happened to someone that beat up Superman because a guy at a bar said he couldn’t…

Just use Snapraid & MergerFS. No special Hardware required and you don’t need to change what is on your disks.

From a quick search: https://perfectmediaserver.com/02-tech-stack/snapraid/

This is how I do it. No striping, normal partitions, different hard drive sizes, pretty easy. This way makes upgrades super easy too. Currently running 76TB mergerfs with 2 14TB Snapraid parity drives.

This is the best answer I’ve seen in this whole thread. You’re right that the key is not needed. Microsoft identified your system components and did the original activation based on the hardware you’ve got on your computer. All you need to do to bring back a licensed copy of Windows is to reinstall it.

On Debian, you have to be root or a sudoer. Those commands are there, just not in the path of regular users.

This honestly sounds like the best solution to this particular problem.

Just make sure it’s RFC 2324 compliant. You don’t want it throwing any HTTP 418 error messages.

If you’re having power on issues, I would make sure you are using a standalone power brick. I’ve used a Surface Pro for work and I’ve found that sometimes when connected to the docking station, it wouldn’t power on. When connected to a standalone power brick it usually would. For a standalone power brick, I’ve used both the one that came with the Surface and also a 65W USB-C adapter with a USB-C to Surface per cable.

To your point, geostationary satellites are in orbits around 22,300 miles away while Starlink is in a LEO orbit ~342 miles away. At the speed of light, that’s an additional quarter second round trip time minimum. Absolutely forever in internet speeds. My experience with GEO is a latency >550ms round trip. With the TCP/IP protocol built the way it is (aka, three-way handshake), a webpage wouldn’t even start downloading until almost 2 seconds have passed.