[1] https://arstechnica.com/gadgets/2023/11/google-chrome-will-l...
Under manifest v3, extensions are not able to dynamically inspect requests, instead, they may only apply rules to net requests. Even worse, there is a limitation of only 5000 rules per extension!! [1]
Even WORSE worse, under Chrome's manifest v3 rules, the extension cannot load any external code! Meaning that blocklists must be packaged with the extension. [2] Now, one might consider the reading of that link to no affect block lists, it's not a "library" and it's not "code" so long as it's just a list of textual rules.... however, google considers the following to be a violation: "Building an interpreter to run complex commands fetched from a remote source, even if those commands are fetched as data". [3]
Sneaky sneaky. An extension update (and hence new app store submission) is required to update filter lists.
In other words, dynamic net requests are banned, and remotely-updated blocklists are banned as well.
[1] https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
[2] https://developer.chrome.com/docs/extensions/develop/migrate...
[3] https://developer.chrome.com/docs/webstore/program-policies/...
[1] https://developer.chrome.com/docs/extensions/reference/api/d...
"Based on input from the extension community, we also increased the number of rulesets for declarativeNetRequest, allowing extensions to bundle up to 330,000 static rules and dynamically add a further 30,000."
I like this. or possibly the COM API. but I'm not a Windows expert.
You could download the Chromium source and patch it to change the extensions APIs (or better, just use Firefox), but the majority of users won't do this, and extension writers aren't going to make a version for a patched Chromium browser unless it has significant market share and support.
[1] https://nordvpn.com/blog/manifest-v3-ad-blockers/
[2] https://www.eff.org/deeplinks/2021/12/chrome-users-beware-ma...
Better to just use a browser that actually respects its users.
Unless you’re running that 20%, Google controls it, and they basically write the standards anymore.
I thought this is rather obvious, at least for those worried about experience. Do you think all those who realize they're suffering from ads don't think about using non-Chromium browser?
I hope we'll not end up in a DRM-like system where ads are somehow really baked in and content stops working for lay-people if they try to circumvent ads.
I suspect they have silently stopped blocking ad blockers.
I remember there was a lot of reports about this being the case, but there is no way I am not blocking Google.
Google knows what will likely happen, and pays people lots of money to know.
1. Googler, opinion solely my own.
I am consistently blown away when I inadvertently experience the Internet without ad-blocking. It’s absolute garbage.
I am sad that people are either OK with this or don’t care. For many they don’t know any better, and asking many of those same groups to install and manage plugins is a fraught request.
Chrome's market share is about 65% [2]. If their recent manifest changes eventually break ad blocking (which seems to be the goal), it'll lose a bunch of market share (I guess they're optimizing for short-term profit).
[1] https://backlinko.com/ad-blockers-users [2] https://gs.statcounter.com/browser-market-share
The day Chrome can't sufficiently block ads anymore is the day Chrome dies.
Is it that easy? Sounds very abusable
It's easier to get a domain added than removed. and for the "corruption"/"rackeetering" part, it's a "win-win" for the adblockers and the list maintainers.
Adblockers also often pay browsers to be integrated by default (AdGuard, Adblock Plus, etc), and then they negociate with publishers to whitelist some domains (not necessarily the most obvious, can just be analytics).
"We offer your domain to be unblocked on xx millions of devices by default, this will create you a uplift of revenue of +yy%"
i had to create a ticket in a repo explaining why blocking a whole domain instead of a single subdomain was actually pretty bad. they approved it and reverted the change.
finding where exactly i had to open the ticket and what to write was a “down the rabbit hole” experience.
Sounds like perhaps your task was to ensure a company's ads got through an adblocker?
they were blocking a whole domain instead of blocking the ad-serving subdomain.
the issue was rectified, the main domain was replaced by the ad-serving subdomain.
The default lists used by uBlock for example include things like error tracking telemetry, Sentry for example.
I can see why people want to block that stuff (privacy) but it’s not exactly an “ad”
i don't really buy your argument
I think the authors want to compare apples with apples, so they only compare their algorithm to other adblockers that use algorithms, as opposed to those which use crowdsourced lists. The paper somewhat acknowledges this:
> However, manual maintenance of these filter lists requires significant human effort
Seems like one of those tasks where crowdsourcing scales so nicely (only one person has to report an ad for it to go into a crowdsourced list that blocks it for millions of others) that it makes an algorithmic approach unnecessary.