-
Notifications
You must be signed in to change notification settings - Fork 76
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
Add exceptions for statcounter #2301
Conversation
Add exceptions for statcounter after auditing that those resources can be loaded safely and with allowing Brave users to be tracked cross-site or cross-profile (i.e., they do not try to circumvent brave's tracking protecitons)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd want to follow this up with:
- A resource/script replacement to lock down the privacy risk even more (our privacy review of their script is a point-in-time check)
- Don't add these exceptions for users in Aggressive ad & tracker mode. We don't currently have the ability to only apply a rule or a filter list in one mode but not the other.
In the meantime, users can badfilter
these rules (i.e. make sure that the exception doesn't apply) by adding the following custom rules in the Settings > Shields > Content filtering > Custom filters (might have to enable developer mode):
@@||secure.statcounter.com/counter$script,badfilter
@@||www.statcounter.com/counter$script,badfilter
@@||c.statcounter.com^$image,xhr,badfilter
Guessing can't we limit it to a specific domain? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure, what I saw from statcounter (sample, https://unsri.ac.id/ )
@@||secure.statcounter.com/counter/counter.js$script
@@||c.statcounter.com/t.php$xhr
add `xhr` requests to c.statcounter.com too, since these are made when the initial statcoutner script is `https://*.statcounter.com/counter/counter_xhtml.js
just a note @ShivanKaul that I made a small change to also exempt ajax calls to c.statcounter.com, since statcounter collects pings using XMLHTTPRequest calls from some initial scripts |
These will be too narrow. The former one will miss the It'd be great to be able to strip query parameters from these calls though. If there is a way to do that @antonok-edm @ryanbr please let me know and i can futher update the PR |
|
The proper way to override the exception rules would be by adding the custom rules, but unexcepted and with an
|
This is currently only applied in aggressive mode though right? And since we will just (at some point, even if not v1) outright block these requests in aggressive mode, that might be a pickle that said, i think this would be good to add in the meantime. I’ll update the PR tomorrow |
On re-review, the lines of code i thought were pushing query parameters along don't copy-over the original values, just that there are values, so i dont think theres a need for for example:
|
Add exceptions for statcounter after auditing that those resources can be loaded safely and without allowing Brave users to be tracked cross-site or cross-profile (i.e., they do not try to circumvent Brave's tracking protections)