Skip to content
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

IPFS needs a way to combat content abuse #769

Closed
ossimantylahti opened this issue Nov 10, 2022 · 1 comment
Closed

IPFS needs a way to combat content abuse #769

ossimantylahti opened this issue Nov 10, 2022 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@ossimantylahti
Copy link

ossimantylahti commented Nov 10, 2022

Recently in my e-mail inbox there is an flow of phish sites hosted on ipfs.io addresses. For example:

image

This leads to a site hosted at ipfs.io like this:

image

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.

@ossimantylahti ossimantylahti added the need/triage Needs initial labeling and prioritization label Nov 10, 2022
@achingbrain
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

2 participants