Quote from: QuadraQ on February 10, 2018, 10:42:37 PM

Quote from: d2bg on February 10, 2018, 05:55:12 PM

Quote from: smaram on February 09, 2018, 08:04:29 PM

Quote from: d2bg on February 09, 2018, 07:24:44 PM

Quote from: smaram on February 09, 2018, 07:08:31 PM

Quote from: smartcrypto on February 09, 2018, 07:00:02 PM

what kind of content is allowed to be uploaded to your site? what's your take on warez/music/cracking methods, or porn. I wanted to start an account but I'd like an idea first.

when you are the copyright owner or have the rights to upload, then you can upload what ever you like, there is even a adult categorie.

when you upload stuff and you have not the rights, the content will be taked down in case of a claim.

How is this decentralized at all or support freedom of speech if content is taken down in accordance with US copyright claims?

the content can't be deleted, what i mean.. we will take it down (the url on ipbc.io), the ipfs hash will still exist and can be viewed with a ipfs daemon or gateway.

Oh okay, then another UI could potentially be made to view it. I see, I understand the value, but unfortunately that brings the next question: How would one stop this project from being used for the storage of things like child porn? This question seems to come up a lot in any project that involves digital content storage.

As I understand it, the actual data is stored on the IPFS network, which does not include the ability to delete data. As long as someone has the hash, and someone has a node hosting that content on IPFS network then it exists and could be accessed by anyone with the hash. Since IPBC is built on top of the IPFS network, that is beyond the scope of this particular project. What IPBC is doing is creating a search engine for IPFS content and linking it to copyright claims and an IPBC wallet address.

So if someone uploaded illegal content like child pornography, users of IPBC can flag that, and then IPBC can remove it from it's search engine. It would be similar to someone hosting child pornography on a server, and Google showing that content via search until it is reported, in which case Google removes it from it's search engine. So the content still exists on that server but is sort of "invisible". As for truly removing the content from the IPFS network, that's not something IPBC can do, so you'd have to research what means IPFS has to remove illegal content. I'm assuming that nodes can decide not to carry content who's hash has been blacklisted, but I'm not sure of that. If there is (or is soon going to be) as system like that in place then IPBC could of course pass along what was reported to the IPFS network.

This is a kind of method, but the creator can still share it with your own content, it seems like a dead circulation, how to perfect solution I think it is important