I am going to be disabling image uploads and image serving, moving to moderated signups, and instituting some extensive block lists on infosec.pub due to the pervasive problems with CSAM attacks on lemmy instances.

No, it’s not happened to any of our instances yet, but I don’t need that headache. And if anyone does, I promise you that I will make it my life’s mission to see that those responsible are convicted and rotting in prison where they belong. ❤️

Edit: h/t to @infosec_jcp for pointing out the problem to me.

  • bulwark@infosec.pub
    ·
    1 year ago

    disabling image uploads and image serving

    I'm assuming this means death for image-based communities here on infosec (the hardware community comes to mind).

    Will this impact images originating from (served by) other instances?

  • Sysosmaster@infosec.pub
    ·
    1 year ago

    now if only there was a universal definition and cut off point for CSAM world wide... but sadly the only valid option is indeed to disable images...

    Lets hope https://github.com/LemmyNet/lemmy/issues/3920 gets a proper implementation or other fix so we can atleast vet before we allow an images.

  • some_guy@lemmy.sdf.org
    ·
    1 year ago

    How common is this problem? And I’m asking at scale, as in some reporters tried to say mastadon had a huge problem for like <200 instances of csam but didn’t put it into perspective that it’s a much smaller platform than Twitter or FB.

    Please note: I’m not saying that even one is ok.

    • Sysosmaster@infosec.pub
      ·
      1 year ago

      the main issue is that 1 bad post, can poison a big pool of servers, currently. Lemmy needs a better way to deal with images, to combat this issue.

      and I hope none here actively go look for CSAM material... that doesn't mean its not in the network.

  • RobotToaster@infosec.pub
    ·
    1 year ago

    As someone who joined this instance because it didn't block many instances, I guess I'll have to leave. 😔

    Anyone know of any tools to migrate my subscriptions?