4 ms·

"Cloudflare will forward abuse reports that appear to be substantially complete to the responsible website hosting provider and to the website owner. In respons

by r1ch 8y ago

"Cloudflare will forward abuse reports that appear to be substantially complete to the responsible website hosting provider and to the website owner. In response to a substantially complete abuse report, Cloudflare will provide the complainant with the contact information for the responsible website hosting provider so they can be contacted directly." So where does this abuse report end up?

yarrel 8y ago
Where do abuse reports usually end up? In my experience they end up with the DMCA officer for the site.
jstanley 8y ago
The best you can do as an IPFS gateway operator is block particular hashes. I have had to do this when a botnet was fetching its code from my public gateway and accidentally DDoS'ing my server :).
xxdesmus 8y ago
For non-IPFS -- It depends on the notification settings selected by the complainant, but generally speaking we notify the website owner based on the Cloudflare account email address, and notify the hosting provider of the website. For IPFS -- there isn't an "owner" of the content in IPFS per se, and as such we will review the specifics of the report and then determine the appropriate next steps.
- stevenicr 8y ago
  "and as such we will review the specifics of the report and then determine the appropriate next steps. " - I understand this thing is new and policies are being created as issues are discovered, I think it would be best to be more up front about the coming blocking of things, if you all will post a notice or just make it appear that the whatever-file is not found, and things like this. That statement is very broad, and I can see a future where lots of niche communities are eventually blocked for varying reasons. Which countries are going to be able to tell you all what to take down? There was a time when I had a lot of faith in Cloudflare, and the whole, it's a pipe / telephone line, not a moderated server - but the whole stormfront thing weakened your position with all the powers that be from what I can tell. So if a bunch of <insert-niche-com-here> start posting links based upon the cloudfalre-ipfs-gateway/controversial-not-mainstream-whatever1 , 2 , 3 etc.. and you all end up nuking all of them, will people know that the files still exist and can be accessed with other means aside from the cloudflare portal? I would think that cloudflare needs to split up and create US company and an EU company and Cananda one, and a Japan... I mean there are so many conflicting things around the world, when you want to censor the internet you just pick a rule from some place on the planet and file a complaint - I think you could removed just about anything. I like the things you all are trying to do, but being a central place under whatever authorities with a fickle CEO that can single handedly change everything, along with who knows how many agencies and stick a paper to your head and make you change, I think it's time your company became decentralized itself. I hope that happens, or some rule is made saying you all are just dumb pips and can't make censor decisions, but I'm not holding my breath for that.
  - stevenicr 8y ago
    "dumb pips" was supposed to be "dumb pipes" - I'm sure most or many would have gotten that typo right away, but for those who did not, I was referring to pipes not people.

by r1ch 8y ago

yarrel 8y ago

Where do abuse reports usually end up? In my experience they end up with the DMCA officer for the site.

jstanley 8y ago

The best you can do as an IPFS gateway operator is block particular hashes. I have had to do this when a botnet was fetching its code from my public gateway and accidentally DDoS'ing my server :).

xxdesmus 8y ago

For non-IPFS -- It depends on the notification settings selected by the complainant, but generally speaking we notify the website owner based on the Cloudflare account email address, and notify the hosting provider of the website. For IPFS -- there isn't an "owner" of the content in IPFS per se, and as such we will review the specifics of the report and then determine the appropriate next steps.

stevenicr 8y ago
"and as such we will review the specifics of the report and then determine the appropriate next steps. " - I understand this thing is new and policies are being created as issues are discovered, I think it would be best to be more up front about the coming blocking of things, if you all will post a notice or just make it appear that the whatever-file is not found, and things like this. That statement is very broad, and I can see a future where lots of niche communities are eventually blocked for varying reasons. Which countries are going to be able to tell you all what to take down? There was a time when I had a lot of faith in Cloudflare, and the whole, it's a pipe / telephone line, not a moderated server - but the whole stormfront thing weakened your position with all the powers that be from what I can tell. So if a bunch of <insert-niche-com-here> start posting links based upon the cloudfalre-ipfs-gateway/controversial-not-mainstream-whatever1 , 2 , 3 etc.. and you all end up nuking all of them, will people know that the files still exist and can be accessed with other means aside from the cloudflare portal? I would think that cloudflare needs to split up and create US company and an EU company and Cananda one, and a Japan... I mean there are so many conflicting things around the world, when you want to censor the internet you just pick a rule from some place on the planet and file a complaint - I think you could removed just about anything. I like the things you all are trying to do, but being a central place under whatever authorities with a fickle CEO that can single handedly change everything, along with who knows how many agencies and stick a paper to your head and make you change, I think it's time your company became decentralized itself. I hope that happens, or some rule is made saying you all are just dumb pips and can't make censor decisions, but I'm not holding my breath for that.
- stevenicr 8y ago
  "dumb pips" was supposed to be "dumb pipes" - I'm sure most or many would have gotten that typo right away, but for those who did not, I was referring to pipes not people.