4 ms·
That argument seems to boil down to “We can’t use any new record types in the DNS ever again because 4-5% of users had problems when we silently tested it”. Fi
by teddyh 10y ago
That argument seems to boil down to “We can’t use any new record types in the DNS ever again because 4-5% of users had problems when we silently tested it”. First, this is defeatism writ large – if we can’t develop anything new, ever, we may all just as well go home and give up. Secondly, these things don’t exist in a vacuum; if a website failed because a user couldn’t access DANE or whatever, this would create pressure on all affected parties to fix the situation. This is how things progress instead of stagnates.
- hannob 10y ago> First, this is defeatism writ large – if we can’t develop anything new, ever, we may all just as well go home and give up. No, it means you need to consider the existing realities when designing a new protocol. A good example is HTTP/2: Probably countless proxies would produce crap once they see an HTTP/2 packet. So people came to the conclusion that they need to wrap HTTP/2 in TLS in order to deploy it. (I know that there's HTTP/2 without tls, but nobody is using it for precisely that reason.) HTTP/2 was built with deployability in mind. DNSSEC was not. > Secondly, these things don’t exist in a vacuum; if a website failed because a user couldn’t access DANE or whatever, this would create pressure on all affected parties to fix the situation. This is simply not what's happening. What happens in the real world is that people blame their browser for breaking things that previously worked. There are countless examples for this.
- Senji 10y ago>What happens in the real world is that people blame their browser for breaking things that previously worked. There are 3 browser vendors of any note right now. It wouldn't be that hard for them to collaborate to push this change at the same time.
- kjs3 10y agoWe aren't talking about a shiny new feature in the latest cat photo sharing app. We're talking about fundamental infrastructure services. Do you have any concept of how many people "4-5% of users" is in this context? More fundamentally, breaking 1 in 20 users while you fumble your way to "progress" isn't how adults do things.
- javajosh 10y agoNot necessarily. Consider the (admittedly dystopian) future where everything you do is hosted at Facebook.com. DNS becomes a vestigial remnant of the old Internet, and Facebook does de facto name resolution on it's private servers. New things can then develop within the proprietary Facebook ecosystem, in part because FB controls (more of) the entire experience. (Come to think of it, why doesn't FB develop a browser and an OS? And hardware while their at it. The fewer middlemen between you and your product the fewer risks you'll get cut off from them/it.)