Apple/Safari adopted pretty much the same architecture on Ad Blockers. Maybe just maybe the conspiracy theories are all wrong, and there was actually a legitimate, technical reason for choosing a restricted API.
If there was, they could've communicated it clearly already a year ago. There is no reason to give Google the benefit of the doubt, since it's clear they're not trying to get it.
If this rolls out, I'm going to very loudly tell my friends to use Fox, and not stop.
They have, https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3Nzz..., and reading it I have always thought it makes sense, as much sense as why Safari decided to do it. However, I don't think I have ever thoughtful discussion why their intended goal (security and privacy) is wrong or could be done in other ways.
I feel sad that each time this comes up even on HN it's always "Google, ad company, bad". There's a mention elsewhere about 30k limit being limiting. Why aren't we discussing alternative enforcement metrics, and request for inclusion?
> maybe [...] there was actually a legitimate, technical reason for choosing a restricted API
Without any further explanation that sounds rather unlikely.
The change is very publicly criticized and keeping legitimate reasons that could've increased support secret is a really counter intuitive strategy.
Apart from that I think it's not far-fetched or particularly conspiratorial to assume that an ad-company might have an interest in restricting ad-blocking.
"When you hear hoofbeats, think of horses not zebras."
I use Safari because it gives me freedom. I paid Apple for their product, now I own the product. It works well except for some Chrome demo apps(which gives me the chills "For the best experience use Internet Explorer" == "Your browser is not supported, use Chrome 46 or newer")
You can bundle many rule lists inside one extension. It's how 1Blocker works, and I did it myself for my own adblocking extension.
I'm not sure if this is possible in Chrome's proposal though.
Maybe this change will finally get people to prune Easylist which had 30% outdated cosmetic-filter cruft when I last sampled it along with hobby horse websites <0.00001% people would ever visit. Right now it's basically like an append-only legacy CSS file.
And the limit is easily circumvented by having multiple extensions. I've seen Safari extensions that split themselves up to one extension per block list.
Google is an advertisement company there is nothing conspiratorial about them using their market share to force ads on people. After all whats the point of supporting chrome if it sells no adds.
1) avoid being locked out of platforms by not controlling the default search. Apple and Microsoft could either extract a high toll, or crush search engines by controlling what search engines people see by default. On iOS, Apple does extract a toll to be the default, but MS was denied this, by Chrome beating out Windows Mobile and Edge/IE. If your company is wholly a web company, and someone else controls the key onramps to the web, you're potentially in trouble.
2) If the Web becomes a toxic wasteland (which was happening prior to Chrome when IE6 ruled), users flee more towards silo'ed platforms and apps. A healthy web is as beneficial to Google as a healthy forest is to a timber company.
It's like saying "The New York times is an advertising company, not a news company, so why would they invest in journalism schools if the point is to sell classified ads?"
And then there's just plain old interest in technology. Lots of projects at Google start from 20% engineers time, and grow to large successful projects, without any business model, they're just costs. You've got more than a thousand open source projects I bet being run by Google engineers, the majority of which exist because someone wanted to scratch an itch. Go, Angular, Tensorflow, Guava, et al, don't make money and aren't intended to.
(You need a standard disclaimer for your employer in this particular thread.)
I disagree that Google is a web company proper. It might have been years ago, but nowadays Google is capable of bending the very rules of the web and internet at their liking. As a result it can now essentially define what the web (okay, the modernish web) is, and that makes your points moot. Also Google's open-source projects are irrelevant to this discussion, much like that using React doesn't void your rights to criticize Facebook.
With Google's new API, all ads can still be blocked. There will be a limit for network request blocking rules, but it's very high so that normal users don't reach it. And for those that reach it, only network requests are affected, so adblockers can still use other APIs to hide the ads.
You can use other APIs to hide ads (i.e. prevent them from being displayed), but they would still be downloaded so you lose the privacy, performance and security benefits of the ad blocker.
If this rolls out, I'm going to very loudly tell my friends to use Fox, and not stop.