3 ms·
If Google actually cared about this, why bother going through the faff of making and standardising a new protocol? You don't need a "DNS Standard" to be able t
by growse 5y ago
If Google actually cared about this, why bother going through the faff of making and standardising a new protocol?
You don't need a "DNS Standard" to be able to do name resolution between a client and a server you control. Just make up your own, pick a network transport (HTTPS works in most places!) and deploy it without telling anyone.
- kuschku 5y agoIsn’t that how DNS over HTTPS started? As internal research project by Google, deployed on Chromecast before ever being standardized? From what I remember, the standardization happened after they used it to circumvent ad blockers. Before this, Chromecasts already hard-coded 8.8.8.8 regardless of what DHCP assigned.
- eli 5y agoI don't follow what connection that has to Firefox. Seems like Google already comfortably solved their problem with Chromecast without needing a standard or anyone else to implement it.
- tempest_ 5y agoLike IBM patenting everything that any of their employees ever stumbled upon there is value to controlling and defining standards (both inside and outside of tech).