Well, badbits are only enforced on the centralized http gateways. LibGen CIDs would still resolve fine using the DHT as the decentralised discovery mechanism
I don't know, it looks pretty decentralised to me?
>The purpose of this list is to allow IPFS node operators (e.g. someone running a public IPFS gateway) to opt into not hosting previously flagged content.
IPFS node operators, who are supposedly interested in hosting malicious content (and i2p-hosted phishings are a real problem) can OPT INTO using this list.
In this case, I don't see how that's any problem for piracy - people can just use one of the bad/unfiltered nodes.
Well, badbits are only enforced on the centralized http gateways. LibGen CIDs would still resolve fine using the DHT as the decentralised discovery mechanism
I don't know, it looks pretty decentralised to me?
>The purpose of this list is to allow IPFS node operators (e.g. someone running a public IPFS gateway) to opt into not hosting previously flagged content.
IPFS node operators, who are supposedly interested in hosting malicious content (and i2p-hosted phishings are a real problem) can OPT INTO using this list.
In this case, I don't see how that's any problem for piracy - people can just use one of the bad/unfiltered nodes.
The fact that it's entirely binary, and they don't separate someone copying books from malware isn't helping that argument.