>Except if that computer is in your TV, or is in an iOS-based device, or in another piece of hardware. This is a problem, yes. We should fix that problem. >It

>Except if that computer is in your TV, or is in an iOS-based device, or in another piece of hardware. This is a problem, yes. We should fix that problem. >It's just one more way in which we've lost control of our local network. When it's not our network, it's a benefit. The same reason why use we SSL. I think part of the reason why I'm in favor of things like DoH and SSL everywhere is there are very few cases nowadays where services are running entirely on a local network. The vast majority of things that people do on networks now touch the internet. >I would like to use the device and filter out any of its harmful effects ... We used to have at least this as a last line of defense. And now we won't. Except that "last line of defense" was always an illusion; as tptacek mentioned, malicious devices have always been able to perform encrypted DNS lookups if their developers really wanted to. DNS filtering was never a reliable defense. You still do have IP blocking as a last line of defense, and that _is_ reliable considering nothing's going to get routed through the internet without being in an IP packet. >I never considered the personal costs of all these good security practices until a cloud hardware device I own had the company go out of business. My recommendation: if it depends on someone running something out on the internet to function, avoid it like the plague. The service _will_ shut down, it's just a matter of time, and IMO it's a waste to buy something that could turn into an expensive paperweight at any time.