Google largely sticks to Chrome changes that disable ad blockers
Google announces through the Google developer Simeon Vincent that the previously proposed Chrome changes around the webRequest API will largely continue. There is a lot of criticism about this, because several ad blockers can no longer operate because of this.
Simeon Vincent defends the plans by stating that Google will only abolish the blocking functionality of the webRequest api, but not the entire api. According to him, extensions such as adblockers with the correct permissions can still observe network requests by using the webRequest API. Once this change is made, ad blockers will no longer be able to intercept, redirect, or block network requests through this api; the api is then no longer an active tool and can only be used to observe things. Adblockers and other extensions that block content will then only be allowed to use the declarativeNetRequest API. The extensions then have to tell Chrome what to block, after which Chrome handles the blocking. Only business users will keep the direct blocking function, according to Vincent.
Raymond Hill, also known as Gorhill on the internet, has previously criticized Google’s plans. He concluded that the changes to the Chrome Extensions platform mean that the ad blockers he developed uBlock Origin and uMatrix can no longer exist. Hill has since responded again. He notes that the blocking function of the webRequest API is still being disabled and that “Google Chrome’s limited matching algorithm will be left as the only option, with the restrictions dictated by Google employees.”
Hill believes that with Vincent’s explanation, Google is only trying to sell the changes to the public. In addition, he states that Google had to allow content blockers to reach its user base, because these are the most popular extensions in browsers. According to him, Google has found “the optimal point between two goals, which is to grow the number of Chrome users and prevent content blockers from harming Google’s business model.” Hill argues that the webRequest API’s blocking capability gave Google the option to transfer control over content blocking to ad blockers. “Now that Chrome is the dominant browser, Google is in a better position to shift the optimal point between the two targets, benefiting Google’s primary business model,” Hill said. He points to Firefox, where extensions can insert scripts and have them run before the page finishes loading: “If performance concerns coming from the blocking feature of the webRequest api were Google’s real motive, they would have just set up Firefox’s method.”
Google says it’s not just performance improvements that underlie the changes, but also privacy and security concerns. Vincent says that dynamic rules will be introduced on the basis of the criticism and that the limit will be increased. Chris Palmer from Google says furthermore, extensions such as adblockers could potentially run even faster and more securely after the changes.