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: @[email protected] 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.

  • @MrPoopyButthole
    link
    English
    1410 months ago

    IP ban + report to the ISP or VPN provider should get the ball rolling. IP blacklist for known compromised hosts. Police report in the country with jurisdiction.

    • TacoButtPlug
      cake
      link
      fedilink
      English
      110 months ago

      Yea this is what I was wondering. A) Blocking IPs / IP blocks. B) Can we get a list of IPs posting the trash so the general community can work on deconstructing potential paths of usage? C) Maybe too far fir privacy maybe not but require MAC address data to get to post on lemmy? There’s gotta be something out there to determine masking.

      • @MrPoopyButthole
        link
        English
        310 months ago

        MAC Address is not available on the IP layer after NAT and browser side JS is not allowed to detect it and pass it on. Browser fingerprinting and localstorage are ways to identify client devices that change their IP often, but those are also defeated by easy steps like an incognito browser tab. The best info we have is the IP and the timestamp. Those together along with a court order should be able to force an ISP or VPN provider to reveal the details of the user.