Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default
by josteink on Saturday September 07, 2019 @09:41AM
(#20903710)
Most mobile-browsers don’t support ad-blocking, especially on iOS.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default
by Dylan16807 on Saturday September 07, 2019 @03:47PM
(#20906060)
They're not threatening to use DNS-over-HTTPS either.
But didn't iOS get browser adblocking capability in the last couple years?
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default
by josteink on Saturday September 07, 2019 @04:47PM
(#20906417)
Not for third-party browsers like Chrome or Firefox. In a classic Apple-move, it’s for Safari only.
Re:What’s Next in Making Encrypted DNS-over-HTTPS the Default
by Dylan16807 on Saturday September 07, 2019 @10:45PM
(#20908281)
Even though those browsers have to use a safari core anyway? How strange.
But for a browser, an ad-blocking extension works better and is less than a minute to set up. Why force it to use the same DNS blocking?