-
Notifications
You must be signed in to change notification settings - Fork 812
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
fishstrap.com: badware #27022
Comments
We don’t block sites which are "unofficial". There need to be a real thread like malware or phishing but the download links i see point to the official github. |
the site leads to the official github download, but thats also not a reason to continue using it because that could change at any time. |
"It could" is not enough to block a site. Also there are no flags on virustotal. |
"It could" is a good reason for the site to get blocked, in a other issue bloxstrap.app was blocked even though it has no flags on virustotal and doesn't host any malware. |
Tbh, that's what I want to not address in the list either. There are thousands of clone sites of Facebook, Instagram, Netflix... hosting on github, and we cannot block every single one of them.
What we would face in every page blocking is what arguments we can use to reply if the page owners come here to complain? Reporters will just report once, and then all of the responsibilities of later arguments fall back to us. The only valid arguments we could use is "the site is having advertisements", which is a really weak argument to justify blocking a whole site. |
If the fake site doesn't say it's an unofficial site, then I think it's fine to block it if there is a complaint by main site that we could refer to. |
The complaint for |
Prerequisites
URL address of the web page
https://fishstrap.com/
Category
badware
Description
This site is a fishstrap site that claims to be official. The only 2 official sources are https://github.com/returnrqt/fishstrap and https://fishstrap.app/
Other extensions used
none
Screenshot(s)
Screenshot(s)
Configuration
The text was updated successfully, but these errors were encountered: