AdguardTeam / AdguardTeam/FiltersCompiler

Figured I should give a headsup about an unusual aspect of `$all` in uBlock Origin

未关闭
#158 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
JavaScript
星标
64
派生
11
PR 合并指标
30 天内没有已合并 PR

描述

This is a bit of a fringe scenario, although it's been tested out with success in Dandelion Sprout's Annoyances List, but it could become useful for you guys at some point in the future:

When an entry uses `$all`, uBlock Origin counts that entry as 5 entry points in their dashboard settings, one for each of [no $ value] + `$popup` + `$document` + `$inline-script` + `$inline-font`.

However, it turns out that this can be reduced to 3 points by changing `$all` to `$all,~inline-script,~inline-font`, especially since https://github.com/AdguardTeam/FiltersRegistry/blob/master/filters/exclusions.txt implies that AdGuard Filters was never designed with `$inline-script` and `$inline-font` in mind anyway.

For example, AdGuard Base Filter's uBO list version is currently shown in uBO as having 65,694 entries ±500. Had all its 235 `$all` entries been converted to `$all,~inline-script,~inline-font`, then the number would've gone down to circa 65,224 ±500. Though this would not be a big enough difference to make that list seem any more compact, and that it'd actually take up *more* filespace, it'd become a big deal if any of your lists' amount of `$all` entries entered the 4-digits.

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。