Mastodon's decentralized social network has a major CSAM problem
engadget.com
engadget.com
So the majority of the CSAM that they detected never reaches most of the fediverse. Furthermore, the methodology of the study relies on sorta Mastodon's firehose, which is instantaneous. That means the hits they catch are before moderators get a chance to handle them. In most of the remaining percentage, they likely get reported and blocked quickly.
So most of the fediverse is blocking the vast majority of this garbage already.
Sure, there's still a lot of work to do, and plenty of ideas how to improve moderation, but the fediverse doesn't have VCs. Donate to Mastodon if you want to help fund work on this stuff.
This is like the web and just like we don't say that HTTP has a X problem it doesn't make sense to say that open source software run by thousands of people across the world under different laws has any specific purpose or problem.
Improvements can be made to the software but bad admins can just rip that code out. Still I bet good instances will make changes.
This article seems to do a pretty fair job of pointing out that they investigate this issue on many platforms, but that they've seen higher rates of CSAM on Mastodon than others. They also specifically call out, accurately, that decentralized platforms have different challenges with addressing these problems when compared to a platform with a central arbiter.
That's what's happening here.
Do you think it’s OK for a convention center to host a meeting where attendees are passing around photographs of CSAM to each other? Why treat the online world differently than the offline world in this regard?
The social network side of Mastodon, connected around mastodon.social, has quite strong moderation, and they block other Mastodon instances for even lesser transgressions.
But anyone can run a Mastodon server disconnected from the trunk of the social network, and make their own fringe network. These instances are a problem, but it's Mastodon's fault as much as Apache and Nginx are responsible for serving CSAM.
Thanks for the clarification. I’ll have think more about what I consider appropriate as far as it concerns Mastodon.
The only real difference is if the tech has the necessary tools.