Google is currently working with updating the API used by Chrome extensions. This is not something that would be normal for users, so that extension developers would suggest that one of the suggested changes could block many content barriers (which -doclock uBlock Origin) from working. Although Google is not completely restored from its plans, it has made solutions within public clams and legal threats.
Initially, a bit back – the current API level for Chrome extensions, known as Manifest V2 & # 39; was introduced in 2012. Since then, Chrome has been at topic time and again to an expanding expansion. Le Manifest V3, which is currently being developed, Google is hoping to reduce the potential to reduce the expansion that may be reduced, and also to # 39; Increase performance and enhance new features.
One of the suggested changes is the new Identity API, designed to replace the API webRequest that there is much expansion (including AdBlock Plus and uBlock Origin) now & # 39; used. Put straight, instead of extensions that make the network a & # 39; They spread themselves, they would send a list of filters that would depend on Chrome itself. In the Manifest V3 design document, Google says that the API can "have an important impact" of current performance:
On the surface, it seems that it is reasonable enough to expand all network applications and its; stop the browser to expand it to & # 39; respond slowly to performance. Cliqz, a company outside Ghostery's widget widget, decided to explore the impact of advanced world-wide performances, and the results did not; means Google was saying.
(Credit image: ZDNet)
The Cliqz survey showed that the average performance impact across air barriers – including Ghostery, uBlock Origin, and AdBlock Plus – was often less than 0.05 millions. Although the design document says that the existing API can only do slowly on Chrome, in practice, not something that the average user would have to do; happening.
Ghostery / Cliqz was largely done for the suggested API modifications. In a blog post, the company wrote, "They do this because of privacy and browser performance, however, users would only have left with just a few ways to stop to third parties from taking over their cargo or getting rid of a unwanted content. What does Google do to protect their advertising business or for its own rules awarded to everyone else, it would not be a lower reason for misuse in terms of its market situation. If this is true, we will consider filing a complaint against trust . "
In response to developers and users broadcast, the Chrome Devlin Cronin engineer on Google Groups has added new features to the new API:
I would like to say again that all of these changes are still in the layout and layout level, as is clearly stated in the paper and on the management terms. The declarativeNetRequest API is still being expanded and it has been developed actively, and the direct modifications that are granted as part of V3 Details are not completed. Feedback at this time is vital, and we are really keen to hear your thoughts and concerns.
Another clarification is that the API webRequest will not be removed as a whole as part of the V3 Manifest. In particular, any current changes currently have no webRequest capabilities (eg anything that does not change the application). We are also listening and listening to us. evaluate the information we receive, and we still have & # 39; Reduce changes that are suggested on the API webRequest.
The forum post also describes other changes made to the & # 39; recommendation based on developer ideas, such as advanced management support for the future and future declarativeNetRequest API; Increase the highest level of rules. In a summary, the old API will still be able to stop networking requests, but Google has restored some of the constraints for a new API.