• 0 Posts
  • 65 Comments
Joined 2 years ago
cake
Cake day: February 14th, 2024

help-circle



  • Not sure if you mean hardcoded DNS IPs or hardcoded “phone home” IPs. Hardcoded DNS addresses in devices are annoying, the only way i’ve found to get around that is using destination nat rules (DNAT) which requires more than a consumer router typically. hardcoded phone home IPs would get blocked by your firewall. you’re right that most firewalls are set up by default to implicitly allow outbound traffic. you set up a rule that denies all outbound traffic from the TV, then only allow port 443 (or whatever port your streaming service uses) on the specific IP/IPs that your service uses. Here’s Netflix’s published IP info for example.

    edit also i’m fully aware it’s fucking ridiculous that we as consumers have to go through this much rigamarole. you shouldnt have to be a literal network engineer to do something as simple as have a tv that doesnt spy on you.







  • I’m throwing in my vote for CachyOS. Not because it’s the easiest to use (though it isnt difficult imo) but because it works out of the box, then they have nice wiki to guide you through simple things (like using Lutris and Proton). It’s also Arch based so there’s the arch wiki to fall back on. I ran Windows for 35 years and just switched to Linux in like October, fwiw.








  • Fun fact, the only reason North America can get away with our dinky plugs and sockets is because we only run 120V (typically). Anything here that’s 240V will have a much beefier plug and socket, more similar to the UK plugs. Heres a 240V/30A and a 240V/50A. These don’t bother with the coated pins because it would typically be plugged in once behind a big appliance and never touched again.