this post was submitted on 24 Jul 2023
40 points (74.4% liked)

Fediverse

17717 readers
3 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
40
Stanford researchers find Mastodon has a massive child abuse material problem (www.theverge.com)
submitted 1 year ago by trashhalo@beehaw.org to c/fediverse@lemmy.ml
20 comments fedilink hide all child comments
 

cross-posted from: https://beehaw.org/post/6795142

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
[–] 0x1C3B00DA@kbin.social 10 points 1 year ago

I have argued for a while that the Fediverse is way behind in this area; part of this lack of tooling and reliance on user reports, but part is architectural. CSAM-scanning systems work one of two ways: hosted like PhotoDNA, or privately distributed hash databases. The former is a problem because all servers hitting PhotoDNA at once for the same images doesn't scale. The latter is a problem because widely distributed hash databases allow for crafting evasions or collisions.

-- https://hachyderm.io/@det/110769474386499134

This is from the study's author (here's the full thread). It shows how pernicious centralization is in technology. The author is claiming the fediverse is "behind" instead of the tools behind behind in supporting decentralized services. They were developed with only centralized Silicon Valley silos in mind and now they can't keep up with a decentralized infrastructure and the authors solution is for decentralized services to centralize around these tools.