AdguardTeam / AdguardTeam/FiltersCompiler

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

Aberta
#158 1 comentário 1 reação 0 responsáveis Ver no GitHub
Linguagem predominante
JavaScript
Estrelas
64
Forks
11
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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.

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.