ublock origin

Ad blocker uBlock Origin “can no longer exist” if a proposed change to Chrome goes through. That’s according to Raymond Hill, the developer of uBlock Origin and uMatrix, in a comment on Chromium’s bug tracker.

如果对Chrome的更改建议通过，则广告阻止程序uBlock Origin将“不再存在”。 这是uBlock Origin和uMatrix的开发人员Raymond Hill所说的，它评论了Chromium的bug跟踪器。

As spotted by The Register, Google engineers are proposing this change in the Chromium project’s bug tracker. Chromium is the open-source browser that forms the basis for Google Chrome, Opera, and soon Microsoft Edge.

正如The Register所指出的那样，Google工程师正在Chromium项目的错误跟踪器中提出这一更改。 Chromium是一种开放源代码的浏览器，是Google Chrome，Opera以及不久的Microsoft Edge的基础。

Don’t worry, though: This won’t break ad blockers entirely. Instead, Google engineers are taking permissions away from browser extensions. Right now, ad blockers and other extensions use the “webRequest” API to listen for events during web page loads and block them.

不过请放心：这不会完全破坏广告拦截器。 相反，Google工程师正在剥夺浏览器扩展的权限。 目前，广告拦截器和其他扩展程序使用“ webRequest ” API来侦听网页加载期间的事件并将其阻止。

If the proposed change goes through, extensions won’t be able to block events with this API. Extensions can only watch these events, and that should speed up page load times. Chrome won’t have to wait for extensions to weigh in while loading a page.

如果建议的更改通过，则扩展将无法使用此API阻止事件。 扩展程序只能监视这些事件，这将加快页面加载时间。 Chrome浏览器在加载页面时不必等待扩展程序扩展。

Ad blockers must use the “declarativeNetRequest” API to tell Chrome what they want to block. Chrome itself does the blocking without waiting for extensions to respond, and this should be faster. However, declarativeNetRequest uses an Adblock Plus-style filtering system.

广告拦截者必须使用“ declarativeNetRequest ” API告诉Chrome他们要拦截的内容。 Chrome本身无需等待扩展程序响应即可执行阻止操作，这应该更快。 但是，declarativeNetRequest使用Adblock Plus样式的过滤系统。

Raymond Hill notes that, if this change goes through, ad blocker uBlock Origin and content filter uMatrix can’t do anything special:

雷蒙德·希尔(Raymond Hill)指出，如果更改成功，广告拦截器uBlock Origin和内容过滤器uMatrix将无法执行任何特殊操作：

If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin (“uBO”) and uMatrix, can no longer exist.

如果这种(非常有限的)declarativeNetRequest API最终成为内容阻止程序可以完成其职责的唯一方式，则从本质上讲，这意味着我多年维护的两个内容阻止程序uBlock Origin(“ uBO”)和uMatrix，将不再存在。

Beside causing uBO and uMatrix to no longer be able to exist, it’s really concerning that the proposed declarativeNetRequest API will make it impossible to come up with new and novel filtering engine designs, as the declarativeNetRequest API is no more than the implementation of one specific filtering engine, and a rather limited one (the 30,000 limit is not sufficient to enforce the famous EasyList alone).

除了使uBO和uMatrix不再存在之外，令人担忧的是，提议的declarativeNetRequest API将不可能提出新颖的过滤引擎设计，因为declarativeNetRequest API仅是一种特定过滤的实现引擎和一个相当有限的引擎(30,000的限制不足以单独执行著名的EasyList)。

Even Hill notes that ad blockers aren’t going away if this goes through. This change may speed up Chrome by limiting what all browser extensions can do—ad blocking extensions and other extensions. Chrome will be similar to Apple’s Safari browser, which now supports “content blockers” that operate in a speedy, standard way.

连希尔都指出，广告拦截器不会消失。 此更改可能会通过限制所有浏览器扩展的功能(阻止广告扩展和其他扩展)来加快Chrome的速度。 Chrome浏览器将类似于Apple的Safari浏览器，该浏览器现在支持以快速，标准的方式运行的“ 内容阻止程序 ”。

It’s a tradeoff. Browser extensions like uBlock Origin can no longer implement their own filtering engine, but the filtering engine will be a speedy one built into Chrome itself. The whole industry has been moving toward more limited browser extensions. Despite what some people have feared, Google isn’t using this as an opportunity to kill off ad blockers.

这是一个权衡。 像uBlock Origin这样的浏览器扩展无法再实现自己的过滤引擎，但是该过滤引擎将是Chrome内置的快速引擎。 整个行业一直在朝着更有限的浏览器扩展方向发展。 尽管有人担心，但Google并未以此为契机消灭广告拦截器。

翻译自: https://www.howtogeek.com/fyi/chrome-may-get-faster-ad-blocking-while-breaking-ublock-origin/

ublock origin