Improved usage scenarios for different lists

This commit is contained in:
Geoffrey Frogeye 2020-01-11 11:26:54 +01:00
parent fbc06f71bb
commit b3a3219f93
Signed by: geoffrey
GPG key ID: D8A7ECA00A8CD3DD
2 changed files with 15 additions and 7 deletions

20
dist/README.md vendored
View file

@ -30,23 +30,31 @@ This list is an inventory of every `somestring.website1.com` found to allow non
## List variants ## List variants
### First-party trackers (recommended) ### First-party trackers
**Recommended for hostfiles-based ad blockers, such as [Pi-hole](https://pi-hole.net/).**
**Recommended for Android ad blockers as applications, such ad [Blokada](https://blokada.org/).**
- Hosts file: <https://hostfiles.frogeye.fr/firstparty-trackers-hosts.txt> - Hosts file: <https://hostfiles.frogeye.fr/firstparty-trackers-hosts.txt>
- Raw list: <https://hostfiles.frogeye.fr/firstparty-trackers.txt> - Raw list: <https://hostfiles.frogeye.fr/firstparty-trackers.txt>
This list contains every hostname redirecting to [a hand-picked list of first-party trackers](https://git.frogeye.fr/geoffrey/eulaurarien/src/branch/master/rules/first-party.list). This list contains every hostname redirecting to [a hand-picked list of first-party trackers](https://git.frogeye.fr/geoffrey/eulaurarien/src/branch/master/rules/first-party.list).
It should be safe from false-positives. It should be safe from false-positives.
It also contains all tracking hostnames under company domains (e.g. `website1.trackercompany.com`),
useful for ad blockers that don't support mass regex blocking,
while still preventing fallback to third-party trackers.
Don't be afraid of the size of the list, as this is due to the nature of first-party trackers: a single tracker generates at least one hostname per client (typically two). Don't be afraid of the size of the list, as this is due to the nature of first-party trackers: a single tracker generates at least one hostname per client (typically two).
### First-party only trackers ### First-party only trackers
**Recommended for ad blockers as web browser extensions, such as [uBlock Origin](https://pi-hole.net/).**
- Hosts file: <https://hostfiles.frogeye.fr/firstparty-only-trackers-hosts.txt> - Hosts file: <https://hostfiles.frogeye.fr/firstparty-only-trackers-hosts.txt>
- Raw list: <https://hostfiles.frogeye.fr/firstparty-only-trackers.txt> - Raw list: <https://hostfiles.frogeye.fr/firstparty-only-trackers.txt>
This is the same list as above, albeit not containing the hostnames under the tracking company domains (e.g. `website1.trackercompany.com`). This is the same list as above, albeit not containing the hostnames under the tracking company domains (e.g. `website1.trackercompany.com`).
While those are technically third-party trackers, they cannot be blocked at once by some ad blockers (e.g. Pi-hole). This allows for reducing the size of the list for ad-blockers that already block those third-party trackers with their support of regex blocking.
Use only with ad blocker able to import regular expressions and in conjuction with other block lists. Use in conjunction with other block lists used in regex-mode, such as [Peter Lowe's](https://pgl.yoyo.org/adservers/)
### Multi-party trackers ### Multi-party trackers
@ -55,7 +63,7 @@ Use only with ad blocker able to import regular expressions and in conjuction wi
As first-party trackers usually evolve from third-party trackers, this list contains every hostname redirecting to trackers found in existing lists of third-party trackers (see next section). As first-party trackers usually evolve from third-party trackers, this list contains every hostname redirecting to trackers found in existing lists of third-party trackers (see next section).
Since the latter were not designed with first-party trackers in mind, they are likely to contain false-positives. Since the latter were not designed with first-party trackers in mind, they are likely to contain false-positives.
In the other hand, they might protect against first-party tracker that we're not aware of / have not yet confirmed. On the other hand, they might protect against first-party tracker that we're not aware of / have not yet confirmed.
#### Source of third-party trackers #### Source of third-party trackers
@ -69,8 +77,8 @@ In the other hand, they might protect against first-party tracker that we're not
- Raw list: <https://hostfiles.frogeye.fr/multiparty-only-trackers.txt> - Raw list: <https://hostfiles.frogeye.fr/multiparty-only-trackers.txt>
This is the same list as above, albeit not containing the hostnames under the tracking company domains (e.g. `website1.trackercompany.com`). This is the same list as above, albeit not containing the hostnames under the tracking company domains (e.g. `website1.trackercompany.com`).
While those are technically third-party trackers, they cannot be blocked at once by some ad blockers (e.g. Pi-hole). This allows for reducing the size of the list for ad-blockers that already block those third-party trackers with their support of regex blocking.
Use only with ad blocker able to import regular expressions and in conjuction with other block lists, especially the ones in the previous section. Use in conjunction with other block lists used in regex-mode, such as the ones in the previous section.
## Meta ## Meta

View file

@ -42,7 +42,7 @@ do
then then
trackerness_flags="" trackerness_flags=""
else else
trackerness_flags="--end-chain --no-dupplicates" trackerness_flags="--no-dupplicates"
fi fi
file_list="dist/${partyness}party-${trackerness}.txt" file_list="dist/${partyness}party-${trackerness}.txt"
file_host="dist/${partyness}party-${trackerness}-hosts.txt" file_host="dist/${partyness}party-${trackerness}-hosts.txt"