3 ms·
Yeah, you could imagine some strategy where they modify the API to make adblockers appear progressively more annoying and unreliable to end users, so that event
by xg15 7y ago
Yeah, you could imagine some strategy where they modify the API to make adblockers appear progressively more annoying and unreliable to end users, so that eventually, the public perception of them changes.
However, this seems a bit like a Xanathos Gambit to me. There are a lot of things that could make this plan fail. It starts with the current backlash of the adblocker devs themselves: They could simply choose to boycott Chrome instead of damaging their reputation.
Even if they don't, so far you still have competition to Chrome so differences can be observed: If adblockers perform significantly worse on Chrome than they do on Firefox, it's apparent even for non-technical users that the browser is somehow a factor in this.
I agree though, just making a change to web store policy (e.g. disallowing all adblockers) probably wouldn't have cut it - that would risk triggering a Streisand effect where everyone tries to smuggle adblockers back into the store using all kinds of rule-bending. So a technical restriction would probably be needed from their point of view.
To be honest (warning, tinfoil hats ahead), I wouldn't be surprised if a long-term goal for Google is to abolish browser extensions altogether. Philosophy-wise, extensions seem completely at odds with Google's vision how the web should behave and how user experiences are designed. Most of their work in the space seems to be about restricting extensions, too - while work that extends capabilities (e.g. support for inspecting WebSocket connections or bringing extensions to mobile Chrome) is postponed.