4 ms·
The problem here is you are falling in the same trap as the Google engineers here. Why would ______ want to do _______ with their ______ device? You can make
by pixl97 8y ago
The problem here is you are falling in the same trap as the Google engineers here.
Why would ______ want to do _______ with their ______ device?
You can make a locked down device that only does a very limited subset of functions, but you really should make that known to the user before hand. "This device requires access to $X servers to function".
If you have secret requirements that go far beyond user expectations, expect that your users might get pissy about it.
- hannasanarion 8y agoThe fact that we got six years into the chromecast world before anybody complained is a pretty good indicator that, no, in fact, most people who want to watch youtube on their TVs don't configure their firewalls to block 8.8.8.8.
- scbrg 8y agoPerhaps the hordes of previous complainers, unlike Paul Vixie, complained to the black hole that is Google support, so we never heard of it :)
- Sendotsh 8y agoIt has actually been a common issue for many years, including for myself, but the rest of us don't have the social clout for it to make it to HN front page. These days you have no chance of getting any form of tech support or even issue acknowledgement unless you have a large follower count online.
- acct1771 8y agoMmmm...I love manufactured consent in the morning.
- scarface74 8y agoIf you want a general purpose computer to serve as your set top box, buy a general purpose computer.
- kllrnohj 8y agoGoogle isn't exactly secret about the fact that Chromecast connects to Google's data centers. Especially if you're using it to, say, watch YouTube, as Paul Vixie was. Chromecast connecting to Google is not a "secret requirements that go far beyond user expectations." Expecting a cloud-connected product to continue to work when you've randomly blacklisted IPs that belong to that company is, however, an unreasonable expectation.
- nofunsir 8y ago"cloud-connected" Hacker News is not the best* place for nebulous cumulonimbus commentary.
- markstos 8y agoWe expect that Chromecast connects to Google's servers when you are using Google services. By forcing you to use their DNS service, they can track every non-Google DNS query you make as well, which is all tied to your IP address. It is a form of surveillance of everything that you do on your Chromecast, for which there is no explicit consent. https://security.stackexchange.com/questions/62273/can-dns-servers-log-users-requests-for-commercial-use-e-g-track-direct-access https://security.stackexchange.com/questions/62273/can-dns-s... It is similar in some ways to Facebook tracking users across the internet through Facebook "Like" and "Connect" buttons across the internet, even when the user's aren't on the Facebook site and did not opt-in to having their browsing tracked by Facebook outside of Facebook.
- kllrnohj 8y ago> By forcing you to use their DNS service, they can track every non-Google DNS query you make as well, which is all tied to your IP address. It's a Chromecast. You literally can't make non-Google queries on it at all in the first place. So what, exactly, is the privacy concern here? What specific flow of events does the Chromecast using 8.8.8.8 impact your privacy?
- markstos 8y agoChromecast allows casting any tab, with any URL, not just Google properties.