GitHub - db0/lemmy-safety: A script that goes through a lemmy pict-rs object storage and tries to prevent illegal or unethical content
github.com
A script that goes through a lemmy pict-rs object storage and tries to prevent illegal or unethical content - GitHub - db0/lemmy-safety: A script that goes through a lemmy pict-rs object storage an...

I posted the other day that you can clean up your object storage from CSAM using my AI-based tool. Many people expressed the wish to use it on their local file storage-based pict-rs. So I’ve just extended its functionality to allow exactly that.

The new lemmy_safety_local_storage.py will go through your pict-rs volume in the filesystem and scan each image for CSAM, and delete it. The requirements are

  • A linux account with read-write access to the volume files
  • A private key authentication for that account

As my main instance is using object storage, my testing is limited to my dev instance, and there it all looks OK to me. But do run it with --dry_run if you’re worried. You can delete lemmy_safety.db and rerun to enforce the delete after (method to utilize the --dry_run results coming soon)

PS: if you were using the object storage cleanup, that script has been renamed to lemmy_safety_object_storage.py

  • db0@lemmy.dbzer0.comOPEnglish
    12·
    10 months ago

    Actually the other instances don’t pull content. You push it out instead. Basically if you don’t run pict-rs and you don’t allow user registreations, you’re safe for everything except potential copyright infringement from some text someone might post. If you make your webui inaccessible to anyone but your IP, you protect against even that.

    • rentar42@kbin.social
      3·
      10 months ago

      what stops other instances from pushing bad stuff to you? even if someone I follow posts illegal stuff, it’ll end up on my server.

      • db0@lemmy.dbzer0.comOPEnglish
        3·
        10 months ago

        If you don’t run pictrs, they literally cannot push images to you as you can’t store them