Google Chrome will limit ad blockers starting June 2024
Google Chrome will limit ad blockers starting June 2024
Ars Technica – Bias and Credibility Check
Bias Rating: LEAST BIASED
Factual Reporting: HIGH
Country: USA
MBFC’s Country Freedom Rating: MOSTLY FREE
Media Type: Website
Traffic/Popularity: High Traffic
MBFC Credibility Rating: HIGH CREDIBILITY

LEAST BIASED These sources have minimal bias and use very few loaded words (wording that attempts to influence an audience by appealing to emotion or stereotypes). The reporting is factual and usually sourced. These are the most credible media sources. See all Least Biased Sources. Overall, we rate Ars Technica Least Biased based on mostly neutral reporting that sticks to their
Google’s sales pitch for Manifest V3 is that, by limiting extensions, the browser can be lighter on resources, and Google can protect your privacy from extension developers.
Emphases mine. Funny, I use extensions to protect my privacy from Google.
The second being Safari, right?
Right?
…right…
Tell me about it. Every time I implement some new thing in my app:
Firefox/Chrome: You cast HTML5 video. Critical hit!
Safari: Your spell fizzles…
It also has no timeline for wasm-gc
Apple has been removing support for garbage collection from their dev tools. Wouldn’t be surprised if they never add support for that, they’ll tell you not to waste CPU cycles (and therefore, battery power) collecting garbage.
… Safari added support for HTMl5 video in 2009.
Chrome did not even exist yet in 2009.
Ah - that’s got nothing to do with supported features.
Your video wasn’t working because the default settings (which a user can change) block most video… because safari assumes (correctly) that most video on the web is an ad.
I’m mostly joking.
Mostly.
Even without all this ad blocker bs from Google, I like Firefox a lot better than the chrome based browser I used before, opera.
It’s a lot cleaner and feels faster
You would think, but the number of people I've met who surf the web without any adblockers at all and just seem fine with it is alarming. I think Google is counting on a lot of people just not knowing any better.
Won't stop me from informing them otherwise though.
Funnily enough I think the percentage use of adblockers is going to go up a fair bit thanks to what Google is doing. My amazingly sweet "just go along with anything" MIL actually complained to me about YouTube ads the other day, then ads on websites in general. She jumped at my offer to install a different YouTube client and a good adblocker once I explained that it was a possibility for her tablet.
If they wanted to pull this off they needed to do it quietly, not draw attention to the fact that adblockers exist and are apparently so effective they need to do something very public about them.
Enterprise users with the “ExtensionManifestV2Availability” policy turned on will get an extra year of Manifest V2 compatibility.
Who are these enterprise users 🤨 🤔…
Remember, Firefox is great and has no dependency on upstream Google code.
Use Firefox.
For a while I was a bit confused, because Mozilla said they would also implement V3 Manifest …
by implementing Manifest V3 on its own terms, Mozilla saves developers who are switching to the new platform from having to support two different versions of their extensions (for Google Chrome and Firefox) at the same time. On the other hand, it allows content-blocking extensions that were originally built using the less restrictive Manifest V2 to continue working at full tilt.
Mozilla is implementing Manifest V3. They plan to implement it slightly different than Chrome: blog.mozilla.org/…/manifest-v3-in-firefox-recap-n…
They have published a guide for extension developers: extensionworkshop.com/…/manifest-v3-migration-gui…
More background on Manifest V3:
eff.org/…/googles-plans-chrome-extensions-wont-re…
eff.org/…/manifest-v3-open-web-politics-sheeps-cl…
Relevant part from the blog post:
What are we doing differently in Firefox? WebRequest
One of the most controversial changes of Chrome’s MV3 approach is the removal of blocking WebRequest, which provides a level of power and flexibility that is critical to enabling advanced privacy and content blocking features. Unfortunately, that power has also been used to harm users in a variety of ways. Chrome’s solution in MV3 was to define a more narrowly scoped API (declarativeNetRequest) as a replacement. However, this will limit the capabilities of certain types of privacy extensions without adequate replacement.
Mozilla will maintain support for blocking WebRequest in MV3. To maximize compatibility with other browsers, we will also ship support for declarativeNetRequest. We will continue to work with content blockers and other key consumers of this API to identify current and future alternatives where appropriate. Content blocking is one of the most important use cases for extensions, and we are committed to ensuring that Firefox users have access to the best privacy tools available.
Adguard and pihole rely on DNS redirects - googs has already implemented “secure DNS” for Chrome in Android, which circumvents network level/local DNS by connecting to a Google owned DNS, serving content using those listings instead.
They’ll likely bring this to all flavors of Chrome.
Yes, one should use Firefox. Yes that could also avoid the android problem, but also no, because Google forces chrome at weird times (eg, some apps will load a minimal web viewer for hyperlinks links, without leaving the app - sometimes apps don’t respect the default browser setting and instead just use chrome.
🤷