▲ 1065 ▼ Google Chrome’s plan to limit ad blocking extensions kicks off next week (arstechnica.com) submitted 2 years ago by AnActOfCreation@programming.dev to c/technology@lemmy.world 357 comments fedilink hide all child comments Reminder to switch browsers if you haven't already! Google Chrome is starting to phase out older, more capable ad blocking extensions in favor of the more limited Manifest V3 system. The Manifest V3 system has been criticized by groups like the Electronic Frontier Foundation for restricting the capabilities of web extensions. Google has made concessions to Manifest V3, but limitations on content filtering remain a source of skepticism and concern.
[–] Album@lemmy.ca 11 points 2 years ago (3 children) It's not up to Chrome. permalink fedilink source parent hideshow 3 child comments replies: [–] HarriPotero@lemmy.world 6 points 2 years ago (2 children) The day they do their own DoH in-browser it is definitely up to them. It's already opt-in if you want to see how well your pi-hole won't work with it enabled. Next step is to do DoH by default, and finally making it compulsory. permalink fedilink source parent hideshow 2 child comments replies: [–] Spotlight7573@lemmy.world 3 points 2 years ago Chrome already does have DoH enabled by default from what I can tell. https://support.google.com/chrome/answer/10468685 By default, Secure DNS in Chrome is turned on in automatic mode. If Chrome has issues looking up a site in this mode, it'll look up the site in the unencrypted mode. permalink fedilink source parent [–] Album@lemmy.ca 1 point 2 years ago* (last edited 2 years ago) They can do it all they want but it won't work... If I "opt in" it falls back to non doh immediately because using doh on my network is not up to Chrome. use-application-dns.net + nxdomain for any known doh provider I don't use pihole but doh blocking works great on my network. It should work on a pihole tho it's pretty basic stuff. If you can't resolve the domain you can't validate the TLS certificate. permalink fedilink source parent
[–] HarriPotero@lemmy.world 6 points 2 years ago (2 children) The day they do their own DoH in-browser it is definitely up to them. It's already opt-in if you want to see how well your pi-hole won't work with it enabled. Next step is to do DoH by default, and finally making it compulsory. permalink fedilink source parent hideshow 2 child comments replies: [–] Spotlight7573@lemmy.world 3 points 2 years ago Chrome already does have DoH enabled by default from what I can tell. https://support.google.com/chrome/answer/10468685 By default, Secure DNS in Chrome is turned on in automatic mode. If Chrome has issues looking up a site in this mode, it'll look up the site in the unencrypted mode. permalink fedilink source parent [–] Album@lemmy.ca 1 point 2 years ago* (last edited 2 years ago) They can do it all they want but it won't work... If I "opt in" it falls back to non doh immediately because using doh on my network is not up to Chrome. use-application-dns.net + nxdomain for any known doh provider I don't use pihole but doh blocking works great on my network. It should work on a pihole tho it's pretty basic stuff. If you can't resolve the domain you can't validate the TLS certificate. permalink fedilink source parent
[–] Spotlight7573@lemmy.world 3 points 2 years ago Chrome already does have DoH enabled by default from what I can tell. https://support.google.com/chrome/answer/10468685 By default, Secure DNS in Chrome is turned on in automatic mode. If Chrome has issues looking up a site in this mode, it'll look up the site in the unencrypted mode. permalink fedilink source parent
[–] Album@lemmy.ca 1 point 2 years ago* (last edited 2 years ago) They can do it all they want but it won't work... If I "opt in" it falls back to non doh immediately because using doh on my network is not up to Chrome. use-application-dns.net + nxdomain for any known doh provider I don't use pihole but doh blocking works great on my network. It should work on a pihole tho it's pretty basic stuff. If you can't resolve the domain you can't validate the TLS certificate. permalink fedilink source parent