[ad_1]
In recent years, several Chrome extensions have collected user data irregularly or even used victims' computers to exploit crypto-rooms without warning. In response, Google has announced changes to make the extensions safer, but the company has not warned that this could also significantly affect the most popular add-ons of the public: ad blockers .
The case comes from Raymond Hill, developer of popular extensions like uBlock Origin and uMatrix. He added that Chrome's planned changes in Chrome's project pages, which form the basis of Google's browser, should cause problems in several APIs, which could have adverse consequences on adblockers extensions.
The explanation is as follows: in the version of the Chrome manifest, which since 2012 is in version 2; This feature determines what each extension can access and what it can not access through the APIs, development tools that allow integration of add-ons with the browser.
In practice, Hill's explanation is that version 3 indicates that there is an API called webRequest that would be replaced by another call. declarativeNetRequest, which is considerably more limited and can affect ad blocking extensions.
Changing Chrome would have performance benefits. These APIs control what extensions can or can not block in terms of network demand, and with the change, the browser would not have to wait for extensions to validate what can or can not be loaded, which simplifies the process. process. However, this tends to have an impact on the add-ons that depend on these changes, such as uBlock.
It is important to note, however, that version 3 of the manifesto is still in development, which means that Google can still change its mind and that things stay as before, but it's good to keep an eye on the world.
[ad_2]
Source link
