There’s another round of CSAM attacks and it’s really disturbing to see those images. It was really bothering to see those and they weren’t taken down immediately. There was even a disgusting shithead in the comments who thought it was funny?? the fuck

It’s gone now but it was up for like an hour?? This really ruined my day and now I’m figuring out how to download tetris. It’s really sickening.

  • snowe@programming.devEnglish
    174·
    10 months ago

    Set up CloudFlare’s CSAM scanning tool. It’s completely free. It’s not on lemmy devs to secure your instance. Lemmy devs could add better admin and moderating tools, but it’s better to stop it before it even makes it to your server.

    • sugar_in_your_tea@sh.itjust.worksEnglish
      12·
      10 months ago

      Imo, lemmy shouldn’t allow image uploads at all. All images should be hosted elsewhere on services that can handle scanning content. This would also drastically cut down on hosting costs for lemmy instances.

      If lemmy is to host images, it should merely be as a backup. But since lemmy content isn’t easy to search as is anyway, that’s not a short term concern. And those images should be archived via mod action imo, not user action.

      • Die4Ever@programming.devEnglish
        5·
        10 months ago

        can’t you already run Lemmy without image hosting if you just disable the pictrs service?

        there’s also a new config option to disable caching of remote images

        • sugar_in_your_tea@sh.itjust.worksEnglish
          2·
          10 months ago

          disable caching of remote images

          I’m not exactly sure how Lemmy works here, but are pictrs images considered “remote,” or are they copied between instances? AFAIK, each instance has its own pictrs service, but I’m not sure if that’s sent along with the post content when federating messages.

          But if lemmy can interact with other instances without storing any non-text data, then perhaps the problem is solved.