Hello everyone,

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.

  • jarfil@lemmy.world
    52·
    1 year ago

    What happened is I came to like 20 answers to comments in “post not found” conversations. Where am I supposed to shitcomment now? 🤬

    • prettydarknwild@lemmy.world
      3·
      1 year ago

      Talking seriously, if the scenario that im thinking happened, im so happy that i wasnt around when hell broke loose. I really dont like the idea of watching cp by surprise and having my browser’s cache filled up with that shit, i also dont like the idea of my ISP noticing it

      • jarfil@lemmy.world
        21·
        1 year ago

        True. I don’t know when it started, think I checked a post this morning, and it was throwing an error for a jpeg I know was fine yesterday. Wonder whether that was part of the countermeasures, or if the attackers were trying to overload LW’s pictrs storage… or if there is some bug involved.

        I can think of a pretty catastrophic scenario if ALL images served by LW could be replaced by CSAM. 😬