Maybe think about it in a different way. Right now, there is a kill-switch within googles primary product that could essentially destroy their business model.
This is not about google wanting to harm the current power users. It is probably the idea that someone could come along and destroy their business.
If such an extensions goes mainstream that could seriously harm them.
They may also want to get rid of paying Adblock Plus money for their highway robbery.
Now that I think about it, getting rid of ABP may be the primary reason for this move. They have to basically pay a third party to get access to their own users.
Either way, the battle is not over the power user minority, but over the average user.
The idea is to make the API just powerful enough for the most annoying ads to disappear. Most users would probably be content with this. They will probably make it so they won't lose all of their power users. I think what they really want is increasing the amount of works it takes to have full adblocking functionality to the point where the average user has no access to it.
> getting rid of ABP may be the primary reason for this move
This makes no sense to me.
ABP is already publishing a version using a declarativeNetRequest-like API, it's in the Mac App Store[1], so clearly it's not going to "get rid of ABP".
Google benefits from ABP and AdBlock[2] being the most used content blockers, as they do not block Google ads by default, and do not block trackers/data miners out of the box.
If Google (rightly) deems content blockers as unavoidable, it sure would want people to install the ones which are not blocking its ads and trackers by default.
You are probably right, although a low number of rules will also affect them as their acceptable ads program is based on the fact that they block everything else. I still wonder if they can continue to offer that program with 30,000 rules only. My idea that they target ABP came from their arbitrary 30,000 rules limit.
As I have written elsewhere I consider ABP and AdBlock as "infiltrated" by Google, so they definitely want to see the rigorous blockers disappear first. Should have made that clearer in the comment.
The Safari version supports "Acceptable Ads". I counted ~17,000 rules[1] which includes exception rules. Also, keep in mind cosmetic exception filters are not implemented through the declarativeNetRequest API.
It's been my assumption that with a little bit of scripting, EasyList could be pruned to land within the 30K without too much trouble. As you have more experience in this fields though, do you have any thoughts on how viable this approach would be, and if the 30K limit will be a problem in the end?
Doesn't any finite length list that is only able to be updated when the addon is updated mean ad networks can use a random string with more combinations than the size of list to defeat all ad blocking?
This is API that ABP can use. But with the new API the rules list will be limited to 30 000 rules vs. for example 42 000 EasyList is using, and an update to the rules will require a full update of the plugin.
You do link the comments, so just to point out "will not be affected" isn't true for many reasons...not just the reduced ruleset. Details are in those comments. It will be a lesser product all around.
The idea is to make the API just powerful enough for the most annoying ads to disappear.
In other words, to block ads on third party networks but leave Google ads alone. That's a bold move these days, when antitrust regulators are putting big tech under the microscope.
well, anti-trust these days is just a buzzword, in a legal sense it is defined in a very strict way, and the cost for companies to anticipate an anti-trust ruling is way higher than just pushing their own interests.
With 66% market share and countless other browsers available, the only question for antitrust when it comes to browsers is if users have equal access to browsers, not whether google supports ad blocking.
I think they will make sure that the ad blocking capability does not explicicly favor google ads.
You know that's wrong. There's Chrome, Safari, and Firefox that support most things and which most people actually use; Internet Explorer is dead and Edge is becoming Chromium; and Brave, Midori, and Vivaldi are also Chromium.
There's also Lynx, Links, w3m, Dillo, and Netsurf, but very few people use those and ad-blocking isn't much of a concern there, because they don't enable JavaScript necessary.
This is not about google wanting to harm the current power users. It is probably the idea that someone could come along and destroy their business.
If such an extensions goes mainstream that could seriously harm them.
They may also want to get rid of paying Adblock Plus money for their highway robbery.
Now that I think about it, getting rid of ABP may be the primary reason for this move. They have to basically pay a third party to get access to their own users.
Either way, the battle is not over the power user minority, but over the average user.
The idea is to make the API just powerful enough for the most annoying ads to disappear. Most users would probably be content with this. They will probably make it so they won't lose all of their power users. I think what they really want is increasing the amount of works it takes to have full adblocking functionality to the point where the average user has no access to it.