

I’ve never liked this approach - having to enroll certs on every machine always seemed tedious and it’s why I just “dealt with” having HTTPS errors internally for years.
You only have to do it once per machine and I use NixOS a lot so its easy to just add to a module imported by every system. On other Linux systems it’s just putting the pem file somewhere in /etc/ and running a command to reload it. Android cell phones were pretty easy but I forget the exact details.
Honest question, why not set up a reverse proxy that uses Let’s Encrypt?
I have multiple of those for public services. Because I don’t want to expose every service to the internet for HTTP-01 and can’t use DNS-01 due to how my nameservers are set up, this makes sense. Other advantages are not needing to distribute DNS update keys to every single server for security reasons and having shorter domains.

epic sucks but to play devil’s advocate here: this is not DRM. This is Anti-cheat.
It has to be a whitelist system or it would be completely ineffective as you could compile a custom kernel that would lie to the eBPF filters and inject cheats into the proecss silently, or just run a fully external cheat in the kernel. There just isn’t a way around it.
You have to understand that we are a very different userbase than the average computer gamer. Most gamers are willing to sacrifice some control over their kernel to not lose to cheaters as frequently.