Google Chrome’s plan to limit ad blocking extensions kicks off next week
Google Chrome’s plan to limit ad blocking extensions kicks off next week
Chrome's Manifest V3 transition is here. First up are warnings for any V2 extensions.
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.
You're viewing a single thread.
won't stop pihole
It's still DNS level only, right? That wouldn't stop YouTube ads, or remove annoyances.
Love my PiHole but you’re hella correct
You can block ads from being served to you.
But the flip side is that the website developer can make a website that won't function if it can't load the ads being served.
And most users are gonna want a functional website.
Somebody's going to need to write a web site with a very, very compelling function to make me give enough of a shit to not just click away if it is deliberately coded to not work with Firefox/adblockers. Like, gives me a million dollars per page load functionality.
Man for real.
And they never will.
You sweet summer child.
How long do you think Chrome will let DoH be opt-in?
You sweet summer child
How are they going to get past my firewall rules?
Nerd fight! Nerd fight! Nerd fight! Show 'em your bionicles collection!
By using the same hostnames that you need for wanted content.
By refusing to load
Personally, I'd like to see them force in-browser DoH down my throat with my computer powered off. They'll never see it coming.
It's not up to Chrome.
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.
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.
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.