web3 censorship

So I'm late coming to the blockchain party but I've been doing a deep, comprehensive dive over the past month or so from the perspective of a developer. I find it all fascinating and definitely see the paradigm shifting nature of a decentralized web3, especially when it comes to disrupting the tech and financial giants that dominate so much of the global economy. Good on all of that.

Here's the issue I'm running into: Last night I finally got around to checking out mirrror.xyz. A decentralized blog, something great in the face of totalitarian censorship. It made me think about the Chinese woman who a few years ago posted some bombshell article or accusation onto the blockchain so it could not be censored. I forget the details but that's a fantastic use case for a decentralized publishing platform. I dug into the details of mirror.xyz to learn exactly how much of the site is decentralized versus blockchain-enabled. (See Moxie Marlinspike's blog entry.) This is where I learned how mirror.xyz uses Arweave to store its data, a truly decentralized and uncensorable data solution. (My first look into web3 data storage.)

Awesome. But I see problems with an uncensorable future because there are definitely instances of censorship that the vast majority of people support: child porn, violence/torture, blackmail. Tech companies expend a huge amount of effort in conducting this censorship. Hell, even this subreddit includes a form of censorship assuming the moderators ever take an active role in curating the community.

I appreciate the desire for freedom of expression when it comes to politics and culture so let's table that debate and agree to a completely uncensored discourse. But it doesn't take much to go down the dark road of content that makes one cringe at the ability to inject something into the public record that can never be taken down and is freely accessible by anyone looking to connect to it and broadcast it.

Again, I'm new in my exploration of web3 but I haven't read much discussion about how to address this issue. The best I've seen is that KYC will prevent people from posting things they won't want to have connected to them. But that strikes me as a form of disingenuous hand waving when privacy and anonymity is so often held up as a virtue of web3. And regardless, KYC has to be chosen and implemented by the file storage provider. Or is this even true? If it's a decentralized storage blockchain, can't one just submit a transaction with the offending content and be done with it? Even if not, how long until there's a 100% privacy ensured storage option created that allows unfettered posting of content.

Happy to learn what I'm missing.