this post was submitted on 24 Jul 2023
232 points (100.0% liked)

Technology

37739 readers
688 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
232
Stanford researchers find Mastodon has a massive child abuse material problem (www.theverge.com)
submitted 1 year ago by trashhalo@beehaw.org to c/technology@beehaw.org
125 comments fedilink hide all child comments
 

Mastodon, an alternative social network to Twitter, has a serious problem with child sexual abuse material according to researchers from Stanford University. In just two days, researchers found over 100 instances of known CSAM across over 325,000 posts on Mastodon. The researchers found hundreds of posts containing CSAM related hashtags and links pointing to CSAM trading and grooming of minors. One Mastodon server was even taken down for a period of time due to CSAM being posted. The researchers suggest that decentralized networks like Mastodon need to implement more robust moderation tools and reporting mechanisms to address the prevalence of CSAM.

you are viewing a single comment's thread
view the rest of the comments
[–] OneRedFox@beehaw.org 19 points 1 year ago (1 children)

That’d be useless though, because first, it’d probably opt-in via configuration settings and even if it wasn’t, people would just fork and modify the code base or simply switch to another ActivityPub implementation.

No it wouldn't, because it'd still be significantly easier for instances to deal with CSAM content with this functionality built into the platforms. And I highly doubt there's going to be a mass migration from any Fediverse platform that implements such a feature (though honestly I'd be down to defederate with any instance that takes serious issue with this).

[–] zephyrvs@lemmy.ml 3 points 1 year ago (1 children)

And the instances who want to engage with that material would all opt for the fork and be done with it. That's all I meant.

[–] OneRedFox@beehaw.org 19 points 1 year ago (1 children)

Right, and the rest of us would be able to more effectively filter it out from our instances.

[–] zephyrvs@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

Of course, I didn't say that though.