HN user
Sorry that wasn’t particularly clear, I was taking more about the general advantageous nature of normalising encryption.
WRT to another party to track you, one of the benefits of LE is that you only need to provide proof of domain ownership (eg dns txt) so the only tie back to you is whatever information you give to the registrar that you have to provide anyway.
GP: At least on business plans this is incorrect, it defaults to (last time I checked) accepting any SSL certificate including self signed from edge to origin and it’s a low friction option to enforce either valid or provided CA/PubKey certs for the same path.
Parent: those innocuous cat photos are fine in the current political climate… “First they came for the cat pic viewers, but I did not speak up…”
For off the shelf shadow.tech has worked pretty reliably for me, even to the point of being usable for streaming vr using alvr (uk based).
For diy you can use moonlight / sunshine or steam remote play. I find latencies lower than around 30ms perfectly playable for everything except twitch shooters etc.
For true diy look into leveraging nvenc or equivalent hw encoder using a “zero latency” profile and build on top of UDP. TCP could be feasible for client input -> remote traffic, but even then building a minimal custom reliable layer on top of UDP probably makes sense to avoid nagle type issues. If you want to support arbitrary input devices (joysticks, wheels etc) that can’t be represented as an Xbox controller things will get pretty tricky. Especially if those devices require drivers, at that point your into proxying usb.
DIY in a weekend? Definitely.
True DIY in a weekend… probably not :)
You can negotiate charging with essentially a single resistor. Deciding when to stop / balancing cells etc is the harder problem.