Re:How We Made IPFS Content Publishing 10x Faster
by RobotToaster on Wednesday July 01, 2026 @04:42PM
(#48752829)
Suddenly it looks a lot less decentralised.
[ Parent
| on HN ]
Re:How We Made IPFS Content Publishing 10x Faster
by msm_ on Wednesday July 01, 2026 @07:30PM
(#48754498)
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.
Re:How We Made IPFS Content Publishing 10x Faster
by RobotToaster on Thursday July 02, 2026 @03:17AM
(#48757685)
The fact that it's entirely binary, and they don't separate someone copying books from malware isn't helping that argument.
Re:How We Made IPFS Content Publishing 10x Faster
by throwaway8388 on Wednesday July 01, 2026 @05:03PM
(#48753082)
Well, badbits are only enforced on the centralized http gateways. LibGen CIDs would still resolve fine using the DHT as the decentralised discovery mechanism