AdguardTeam / AdguardTeam/FiltersCompiler

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

Aperta
#158 1 commento 1 reazione 0 assegnatari Vedi su GitHub
Lingua principale
JavaScript
Stelle
64
Fork
11
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.