You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently in my e-mail inbox there is an flow of phish sites hosted on ipfs.io addresses. For example:
This leads to a site hosted at ipfs.io like this:
Due to the nature there does not seem any way of intelligently reporting and taking down these kind of blatant phishing and abusive ipfs.io sites. As the technology becomes more common, there will be more abusive uses.
IPFS.io needs a way to combat this kind of content abuse. It is better to think this before someone starts hosting kiddie porn and the community finds itself in the front page of New York Times.
Recently in my e-mail inbox there is an flow of phish sites hosted on ipfs.io addresses. For example:
This leads to a site hosted at ipfs.io like this:
Due to the nature there does not seem any way of intelligently reporting and taking down these kind of blatant phishing and abusive ipfs.io sites. As the technology becomes more common, there will be more abusive uses.
IPFS.io needs a way to combat this kind of content abuse. It is better to think this before someone starts hosting kiddie porn and the community finds itself in the front page of New York Times.
IPFS already has a Code of Conduct (https://github.com/ipfs/community/blob/master/code-of-conduct.md). But the process is apparently manual and does not really take spam in account. A way of freezing malicious content should be implemented.
The text was updated successfully, but these errors were encountered: