-
Notifications
You must be signed in to change notification settings - Fork 3
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
False Positive Automation #3
Comments
smashah
added a commit
that referenced
this issue
May 13, 2022
smashah
added a commit
that referenced
this issue
May 13, 2022
smashah
added a commit
that referenced
this issue
May 13, 2022
Done. If you've identified that a legitimate site has been added to the blocklist, please submit a PR with a change to https://github.com/smashah/smashblock/blob/master/false-positives.txt Keep the commit formatting the same as the rest of the commits on this file: https://github.com/smashah/smashblock/commits/master/false-positives.txt |
smashah
added a commit
that referenced
this issue
May 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone,
Ever since the implementation of the Quantum Ad list there have been reports of some odd edge cases. For example, Behance, Beaverton and apparently some windows update false positives.
I was thinking of further fragmenting the block list into a set with quantum and a set without. But then what's the point of this whole project?
I started this project because I'm a lazy guy so in that theme, I was thinking of creating a false positive issue template and an automation which will automatically add a domain as false positive and remove it from the block list after a certain amount of "thumbs up"s + my own thumbs up and a quick check of the domain on urlscan.io
Think of it like a lazy PR.
I would love to hear your thoughts on the idea and/or any other (semi) automated solutions to false positive rectification.
Thanks
The text was updated successfully, but these errors were encountered: