We unfortunately have to close the !lemmyshitpost community for the time being. We have been fighting the CSAM (Child Sexual Assault Material) posts all day but there is nothing we can do because they will just post from another instance since we changed our registration policy.

We keep working on a solution, we have a few things in the works but that won't help us now.

Thank you for your understanding and apologies to our users, moderators and admins of other instances who had to deal with this.

Edit: @Striker@lemmy.world the moderator of the affected community made a post apologizing for what happened. But this could not be stopped even with 10 moderators. And if it wasn't his community it would have been another one. And it is clear this could happen on any instance.

But we will not give up. We are lucky to have a very dedicated team and we can hopefully make an announcement about what's next very soon.

Edit 2: removed that bit about the moderator tools. That came out a bit harsher than how we meant it. It's been a long day and having to deal with this kind of stuff got some of us a bit salty to say the least. Remember we also had to deal with people posting scat not too long ago so this isn't the first time we felt helpless. Anyway, I hope we can announce something more positive soon.

you are viewing a single comment's thread
view the rest of the comments

[–] snowe@programming.dev -1 points 1 year ago (1 children)

It really shouldn’t. There are plenty of existing tools already created for this, and giving anyone who runs a lemmy server access to the CSAM hashes is a terrible terrible terrible idea. Use CF or another existing solution to stop CSAM. Do not put that into the lemmy code.

[–] Ab_intra@lemmy.world 5 points 1 year ago (1 children)

Can you elaborate on why this is a terrible idea?

[–] snowe@programming.dev 2 points 1 year ago

I have detailed why in plenty of my other comments. Here is one. https://programming.dev/comment/2426720