this post was submitted on 02 Sep 2023
18 points (95.0% liked)

literature.cafe chat

448 readers
1 users here now

Local off topic chat for literature.cafe, any and all are welcome. For discussions of books and beyond! Please follow instance rules. Although focused for literature.cafe users, any and all are welcome!

To find more communities on this instance, go to: [email protected]

founded 2 years ago
MODERATORS
 

The CSAM spamming happened again, and unfortunately a local user had to witness it and report it.

I myself did not see it, but from what I gather it was basically an innocent looking tiktok video at first glance that would transition into CSAM. Utterly vile.

The content is being reported and admins across lemmy are handling it. I am hopeful this is an isolated incident but what the fuck man. What do we do from here?

top 13 comments
sorted by: hot top controversial new old
[–] [email protected] 9 points 2 years ago

I'm honestly extremely frustrated. Which sucks cause thats the intention of these trolls.

[–] [email protected] 9 points 2 years ago (1 children)

The video that I saw today was probably not actual CSAM, although it was meant to look like it. There’s no accounting for how some people get their jollies.

On the one hand, defederating from open-registration instances is prudent. TBH, as an admin, it’s probably what I’d do out of an abundance of caution.

On the other hand, it feels like letting the bastards win. And that rubs my fur backwards.

[–] [email protected] 5 points 2 years ago

Ikr! It's just.. ugh.

[–] [email protected] 5 points 2 years ago (1 children)

What common instances are open registration?

[–] [email protected] 5 points 2 years ago (1 children)

As of right now the really only instance with open registration is sh.itjust.works. All others have closed their registration to application only in response to what has happened.

[–] [email protected] 9 points 2 years ago

Then I'd be in favor for defederation. sh.itjust.works doesn't bring enough value to me to justify the risk and mental damage to mods.

[–] [email protected] 3 points 2 years ago (1 children)

This is a really hard choice :/

[–] [email protected] 5 points 2 years ago (1 children)

If it happens again I'll defed but it seems things will improve pretty rapidly since significant changes to lemmy are coming soon

[–] [email protected] 3 points 2 years ago (1 children)
[–] [email protected] 5 points 2 years ago

Remote image caching will be able to be disabled as well as work on more granular federation operations and front end mod tooling

[–] [email protected] -3 points 2 years ago (1 children)

Just wait until ~next patch and disable image uploads. Eventually, people will catch on that it's too dangerous to leave image uploads enabled

[–] [email protected] 7 points 2 years ago* (last edited 2 years ago) (1 children)

There's a lot of FUD (fear, uncertainty & doubt) being spread on lemmy about this entire thing that's not helping anyone and it's becoming extremely annoying. The way lemmy currently handles image uploads leaves a lot of room to be desired, but allowing image uploads (when safety rails are in place) isnt as dangerous as people are making it out to be.

I'm a bit more than sick of people fearmonger that the FBI is going to raid your instance over content you had no idea about. If you live in the US and host in the US there are safe harbor protections and so long as you are doing your due diligence, reporting, etc, you'll be fine. Almost all of the images being posted that are legally problematic are from external image hosts and it's just a major issue due to the fact that lemmy caches ALL images (including external images) right now.

[–] [email protected] 0 points 2 years ago

Thanks for defining fud, it also rhymes with mud. Yeah for sure, if you want to manage a team to handle takedown requests and reply to legal threats from corporations, then go ahead and keep image uploading on

Oh the devs are already making a feature to disable this? Shit well I guess they fell for the fud