3 ms·
I read that IPFS purposefully has mechanisms in it to allow banning content. While hypothetically you could still run a custom client that won't ban content, pe
by lijogdfljk 5y ago
I read that IPFS purposefully has mechanisms in it to allow banning content. While hypothetically you could still run a custom client that won't ban content, peered nodes might still ban the content leaving you with no source.
Based on what i read long, long ago - IPFS is very much not intended to be censorship resistant.
- capableweb 5y ago> I read that IPFS purposefully has mechanisms in it to allow banning content I'd be interested in reading whatever article you got that from, because last time I checked, IPFS doesn't have any such mechanism. You might be confusing it with the content blocking Protocol Labs does on the public IPFS gateway (https://ipfs.io/ipfs/hash https://ipfs.io/ipfs/hash). The gateway being a centralized gateway to distributed IPFS content, is hosted by a US party and must therefore follow US law, so sometimes they block content from being accessed via the gateway.
- TUSF 5y agoI can totally see how some nodes could block content, and refuse to propagate information on certain content addresses, but as far as I know, this would only slow down reaching the desired content, not completely block it—every node on the network would need to blacklist the banned address, which is pretty infeasible. Also, as far as I know, the official daemon doesn't really have any functionality to block certain addresses like this.