With the recent release of the new Chrome version 136 and the various postponed intentions of Google to end version 2 of the Chrome Manifest, it seems that the The long-awaited day for Google has arrived.
And it is that recently on the page of the complement uBlock Origin in the Chrome Web Store, this one is already does not offer the installation option, displaying the message “This add-on is no longer available because it does not follow Chrome’s add-on development guidelines.”
Google Chrome and the future of uBlock Origin
This change is part of the Google initiative to discontinue support of version 2 of the Chrome Manifest, compliance with which will become mandatory for all Chrome users by the middle of this year, after having been initially postponed to January 2023. This new framework defines the capabilities and resources that extensions based on the WebExtensions API can use, and the third version of the manifesto is designed to facilitate the development of more secure and high-performance add-ons, at the cost of restricting certain functionalities.
One of the The most controversial changes are the modification of the webRequest API. Previously, This API allowed extensions to intercept and modify network traffic through custom handlers, which was essential for content blocking, parental controls, and malware protection. However, The transition to read-only mode of webRequest has been replaced by the declarativeNetRequest API, which operates by means of an integrated filtering engine and limits the implementation of custom algorithms. This change has raised concerns among users, as it has affected the functioning of uBlock Origin and prompted a search for alternatives.
In response to these modifications, Raymond Hill, creator of uBlock Origin, has suggested that those who value the experience of the add-on in browsers with support for the old API choose to continue using uBlock Origin in Firefox, where Mozilla has decided to maintain such support.
uBlock Origin is still fully supported on Firefox and other Gecko-based browsers.
uBlock Origin Lite may be a suitable replacement, only you can make this determination, please see the FAQ for more details on uBlock Origin Lite.
Important: Please note that for uBO Lite to have blocking effectiveness similar to uBO, you must set the default filtering mode to Optimal or Comprehensive . The default filtering mode is Basic.
For Chrome users are advised to migrate to the new uBlock Origin Lite, a version adapted to the declarativeNetRequest API and the Manifest v3. Although uBlock Origin Lite It fulfills the essential function of blocking ads, Its functionality has been simplified; for example, does not allow the use of cosmetic filters or custom filtering algorithms Just like the classic version, unless explicitly granted extended permissions. This means that while it consumes slightly less CPU and memory, in situations where websites employ advanced techniques to evade blockers, uBlock Origin Lite's effectiveness may be reduced, resulting in slightly more data download when opening pages.
This transition process to a new extensions framework It doesn't just affect blockers of advertisements, but redefines filtering capabilities and security in Chrome, by restricting the execution of code downloaded from external servers and enforcing a more granular permissions model. Google has adjusted the declarativeNetRequest API to increase the number of allowed rules, seeking to balance the need for security with the functionality users demand. Meanwhile, Mozilla has opted to preserve the full functionality of the old API in Firefox, offering users the choice between a more traditional approach or the new scheme imposed by Google.
Ultimately, the closure of uBlock Origin from the Chrome Web Store and the subsequent migration to uBlock Origin Lite reflect a change that poses significant challenges for developers and users, who will have to adapt to a browser where filtering capabilities have been limited in the "interest" of ensuring more secure operation.