Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smart Blocking: Allow blocking of first party tracking #730

Merged
merged 1 commit into from Dec 2, 2021

Conversation

chrmod
Copy link
Member

@chrmod chrmod commented Dec 2, 2021

In order to deal with cname cloaking we have to be able to block first party trackers. That way we can block Google Beacons.

@chrmod chrmod changed the title Block first party tracking Smart Blocking: Allow blocking of first party tracking Dec 2, 2021
Copy link
Member

@philipp-classen philipp-classen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging for now, as the change makes sense. It has an unintended side-effect of disabling the later steps of the community-based adblocking (the removed code path did not set eventMutable.ghosteryWhitelisted = true).

As the former behavior is more accidental, merging and finding a proper fix for the latter (it is an independent issue) makes sense IMHO.

@philipp-classen philipp-classen merged commit 9f3a21a into master Dec 2, 2021
@philipp-classen philipp-classen deleted the block-first-party-tracking branch December 2, 2021 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants