AdguardTeam / AdguardTeam/FiltersCompiler

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

Ouverte
#158 1 commentaire 1 réaction 0 personnes assignées Voir sur GitHub
Langage dominant
JavaScript
Étoiles
64
Forks
11
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.