-
Notifications
You must be signed in to change notification settings - Fork 226
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
Reporting spam, phishing, abuse etc. #775
Comments
It appears this isn't news: I'd appreciate if there was simple mechanism to reporting abuse on the site, linked in the footer. Other than that - good luck, I guess 🤷♂️ |
This guy is trying to hack my email: |
@alexei currently the way to report abuse on our gateways is via [email protected]. We have this linked in a few places like here. You mentioned putting it in the footer, I like that idea. Where do you imagine it'd live? Across all of ipfs.tech and docs.ipfs.tech? |
I don't know 🤷♂️ Like I mentioned earlier I don't use ipfs so I'm not familiar with your web properties. I didn't see the header link to https://ipfs.tech/help/ when I looked, for some reason I only checked the footer... |
@alexei thank you very much for your feedback, this helps a lot. I'll look into getting something akin to "Report abuse" into the footer with a page explaining what can be done about it. |
Please be aware that by posting specific URLs here, someone or something will access them and thus confirm your mail address. This will lead to you getting even more spam than before. |
https://ipfs.io/ipfs/QmPL2BcxASGfxP1vvqpMQmE9qWm3RcbEjQVzb6qpqQ2AiT#[email protected] Not easy how to report abuse. That Information is only found in your github repo. You should add this information next to the contact information on: https://ipfs.tech/ |
What are the mechanisms to reporting spam/phishing? I just received two spam emails linking to
https://ipfs.io/ipfs/QmQwN61kY9e19CxprtQC39ZHcCLt6aGNjUPnctYvz63qhR?/kiomd.html#[MY-EMAIL] I'm not an ipfs user and I will report the two emails. I thought you should know in case you want to take action against the user who created that page.
The issue has been raised before (#769 and #773) but there doesn't seem to be any resolution.
The text was updated successfully, but these errors were encountered: