3 ms·
Knowing who he is, my takeaway should be, "Wow! An Internet Hall of Famer weighing in against a Google product!" But my actual takeaway is, "Legends of the CS
by AdmiralAsshat 8y ago
Knowing who he is, my takeaway should be, "Wow! An Internet Hall of Famer weighing in against a Google product!"
But my actual takeaway is, "Legends of the CS world write informal, pithy rants to Google just like the rest of us mortals."
- jchw 8y agoI find the responses on the mailing list to be interesting. Nobody there seems terribly amused by this thread so far. >Are you looking for https://support.google.com/chromecast/contactflow https://support.google.com/chromecast/contactflow ? >And [wasting our time] as well. And to be fair, I would've expected a personal blog post rather than an IETF post. This is definitely quaint, though it gets the point across.
- slim 8y agoIETF should be concerned since one solution to this problem is to hijack the DNS. Namely 8.8.8.8
- justizin 8y agoRight, realistically what Vixie is saying is: This is a major vendor failing to comply with IETF standards and using their market dominance to undermine open standards and protocols.
- dragonwriter 8y ago> This is a major vendor failing to comply with IETF standards What IETF standard is violated by a device using a known DNS server rather than the one offered by DHCP?
- trumped 8y agowhy didn't you rant about it first, then, AdmiralAsshat? (if you are so good)
- jmull 8y agoPithy, drunken, one or the other.
- nashashmi 8y agoI agree with you. He had more leverage if he said: my ISP blocks 8.8.8.8. I cannot activate chrome cast.