3 ms·
> Applications can choose to ignore the system resolver regardless if it's over UDP or HTTPS. They can, but up until Firefox legitimized this practice, they di
by vetinari 6y ago
> Applications can choose to ignore the system resolver regardless if it's over UDP or HTTPS.
They can, but up until Firefox legitimized this practice, they didn't, maybe except some malware.
> DoH/DoT is showing up in operating system resolvers just not as fast as apps like browsers were willing/able to add it.
The browsers were so fast, that they skipped the discussion about ramification of this change with the rest of community and just abused their position. One might even wonder, why.
Does not make for good relations in future.
> Standard DHCP options for defining DoH details are still missing though
Yup. Here, browsers are not using their position to finish their push, so maybe the situation is acceptable for them.
- zamadatix 6y agoOn one hand you say browsers are to blame because they went too far too fast bypassing the OS DNS and on the other you say browsers are to blame because they didn't go far and fast enough bypassing the OS DHCP client. Again are your arguments actually about DoH causing centralization or are you just talking about browsers causing positioning centralization irrespective of the technology?
- vetinari 6y ago> On one hand you say browsers are to blame because they went too far too fast bypassing the OS DNS Yup, they shouldn't have do this. > On one hand you say browsers are to blame because they went too far too fast bypassing the OS DNS No. I'm saying, that once they did what they did, they should have finish the job. They left it unifished. > Again are your arguments actually about DoH causing centralization or are you just talking about browsers causing positioning centralization irrespective of the technology? My point is that the way DoH was implemented is causing centralization. DoH could be implemented without causing this effect.