谷歌对Manifest V3中影响广告拦截器的API修改的新进展

cxf5102

原标题：谷歌撤回了(Manifest V3中)影响广告拦截器的API修改

3楼的前情提要：https://bbs.saraba1st.com/2b/thread-1807230-0-1.html
一项研究（https://whotracks.me/blog/adblockers_performance_study.html）指出，谷歌所谓的广告拦截器影响游览器性能的说法不成立，实际影响可以忽略。随后，谷歌的拓展讨论中出了一篇新声明（https://groups.google.com/a/chro ... ensions/WcZ42Iqon_M），有相关文章（https://www.zdnet.com/article/go ... ippled-ad-blockers/）。
但是经4楼提醒，阅读声明后，我觉得我的原标题（和原本转载文章的标题）是一种误导，所以改了一下。

那么声明究竟说了什么？虽然我也做过CHROME的拓展，不过对于这里涉及的API实际上并不了解，所以我下面的概述只能算简单阅读理解：
declarativeNetRequest API这个API我们还是要实现的，但是具体做成什么样还没定论。（The declarativeNetRequest API is still being expanded and is under active development, and the exact changes that will be implemented as part of Manifest V3 are not finalized.）

webRequest API不会被完全移除，webRequest观察能力不会被砍。（webRequest API is not going to be fully removed as part of Manifest V3.  In particular, there are currently no planned changes to the observational capabilities of webRequest）
[然而Manifest V3（https://docs.google.com/document ... nk4w4PX-0XMw8/edit#）里基本上本来就是这个意思，而其modify, redirect, or block的能力会被砍掉。所以这里说了似乎等于没说。]

declarativeNetRequest API预计有三个改进：
动态规则支持：允许运行时改动拦截规则。
增加规则数量上限：原先的上限预计被提高，然而还是要有上限。原因是过多规则会影响性能，而且不加限制的话EasyList这种列表只会越来越大。
额外动作和条件：预计增加条件性动作，例如根据资源大小作出决定，又如提供部分修改request的手段而不是直接屏蔽。等等……
Dynamic Rule Support: We agree that this is valuable in creating sophisticated content blocking extensions, and will be adding support for declarative rules that can be added or removed at runtime to the declarativeNetRequest API.
Increased Ruleset Size: We will raise the rule limit from the draft 30K value.  However, an upper limit is still necessary to ensure performance for users.  Block lists have tended to be “push-only”, where new rules are added but obsolete rules are rarely, if ever, removed (external research has shown that 90% of EasyList blocking rules provided no benefit in common blocking scenarios).  Having this list continue to grow unbounded is problematic.
Additional Actions and Conditions: We plan to add support for matching based on more conditions, such as resource size, and will provide actions to modify parts of a request instead of just blocking it, such as stripping cookies.  We are also investigating other conditions and actions that may make sense to add, such as matching based on top-level domain.  (One additional note: While we are investigating adding support for CSP modifications, adding a CSP header to disable JavaScript was frequently mentioned as a use-case; this is already possible through the contentSettings API.  If this is insufficient, please let us know why.)


其它没什么实质性进展的发言我就懒得说了（如果我看漏了请指出）。总的来看还请各位继续努力喷谷歌。
（编辑了好多次好累，没怎么在S1发过贴老是格式有问题。）

——————以下是原帖内容——————

新闻原文：
https://www.zdnet.com/article/go ... ippled-ad-blockers/

简单概述：一项研究（https://whotracks.me/blog/adblockers_performance_study.html）指出，谷歌所谓的广告拦截器影响游览器性能的说法不成立（实际影响可以忽略），于是谷歌决定撤回会影响到广告拦截功能的API修改。（顺面一说这个研究的跑分是Ghostery的团队做的，所以其中关于Ghostery综合最优的结果你自己判断吧）

不知另一个影响到用户脚本管理器的修改是否会被撤回呢。

pgain2004

太好了。
前情提要：https://bbs.saraba1st.com/2b/thread-1807230-0-1.html
与楼主共勉

starrin

我仔细读了下google发布的声明，他们好像并没有说要撤回对webrequest API的修改，只是强调了一遍说这个API不会被整个干掉，监听功能本来就决定要保留，别的修改现在并没有完全决定，然后新的declarativeNetRequest API里的3万条过滤规则数量限制预定会放宽。
然后又反复辩解他们很重视生态，无意要废掉广告过滤扩展，但是又抱怨“Easylist里很多规则其实并不合适，放任Easylist继续膨胀会有麻烦的”

cxf5102

starrin 发表于 2019-2-19 02:56
我仔细读了下google发布的声明，他们好像并没有说要撤回对webrequest API的修改，只是强调了一遍说这个API ...

我马上研究一下原声明，更新到主楼。看来不该太相信网上传了几次的新闻。