I noticed a bit of panic around here lately and as I have had to continuously fight against pedos for the past year, I have developed tools to help me detect and prevent this content.

As luck would have it, we recently published one of our anti-csam checker tool as a python library that anyone can use. So I thought I could use this to help lemmy admins feel a bit more safe.

The tool can either go through all your images via your object storage and delete all CSAM, or it canrun continuously and scan and delete all new images as well. Suggested option is to run it using --all once, and then run it as a daemon and leave it running.

Better options would be to be able to retrieve exact images uploaded via lemmy/pict-rs api but we’re not there quite yet.

Let me know if you have any issue or improvements.

EDIT: Just to clarify, you should run this on your desktop PC with a GPU, not on your lemmy server!

  • nickA
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I think deleting images from the pictrs storage can corrupt the pictrs sled db so I would not advise it, you should go via the purge endpoint on the pictrs API.

      • nickA
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Interesting, when I tried a while back it broke all images (not visible on the website due to service worker caching but visible if you put any pictrs url into postman or something)

          • nickA
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            True, you’re correct. I’m just not sure how you did it without corrupting the sled db. Maybe I’m just unlucky

            • db0@lemmy.dbzer0.comOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              the sled db is not touched. It’s just that when pict-rs is trying to download the file pointed by the sleddb, it’s get a 404