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

Technology

37736 readers
46 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
remington
alyaza
TheRtRevKaiser
gyrfalcon
rs5th
coldredlight
Los
SemioticStandard
TheRtRevKaiser@kbin.social
232
Stanford researchers find Mastodon has a massive child abuse material problem (www.theverge.com)
submitted 1 year ago by trashhalo to c/technology
84 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
[–] faeranne@lemmy.blahaj.zone 5 points 1 year ago

Another way to look at it is: How would you solve this problem with email?

The reality is, there is no way to solve the problem of moderation across disparate servers without some unified point of contact. With any form of federation, your options are:

  1. close-source the protocol, api, and implementation and have the creator be the final arbiter, either by proxy of code, or by having a back door
  2. Have every instance agree to a singular set of rules/admins
  3. Don't and just let the instances decide where to draw lines.

The reality is, any federated system is gonna have these issues, and as long as the protocol is open, anyone can implement any instance on top of it they want. It would be wonderful to solve this issue "properly", but it's like dealing with encryption. You can't force bad people to play by the rules, and any attempt to do so breaks the fundamental purpose of these systems.