GitHub - db0/fedi-safety: A script that goes through a lemmy images in storage and tries to prevent illegal or unethical content
github.com
A script that goes through a lemmy images in storage and tries to prevent illegal or unethical content - GitHub - db0/fedi-safety: A script that goes through a lemmy images in storage and tries to ...

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

  • webghost0101@sopuli.xyzEnglish
    2·
    1 year ago

    We Evolve!

    There something really satisfying about witnessing a community starting to talk about serious a issue and days later see things already improved.

    Lemmy is now the internet, glory to all volunteer devs. Lets make it the best place we possibly can!

  • BitOneZero @ .world@lemmy.worldEnglish
    1·
    1 year ago

    I hope people share the positive hits of CSAM and see how widespread the problem is…

    DRAMTIC EDIT: the records lemmy_safety_local_storage.py identifies, not the images! @bamboo@lemmy.blahaj.zone seems to think it “sounds like” I am ACTIVELY encouraging the spreading of child pornography images… NO! I mean audit files, such as timestamps, the account that uploaded, etc. Once you have the timestamp, the nginx logs from a lemmy server should help identify the IP address.

  • rentar42@kbin.social
    0·
    1 year ago

    It’s great that there’s now a tool, but this kind of issue is why I’m not considering self-hosting a fediverse service: due to the nature of the beast even a single-user instance effectively becomes a publicly accessible distributor of content that others created/uploaded. I’m sure this could be restricted somewhat (by making the web UI inaccessible for the public), but the federation means that other instances need to be able to get content from the server. That’s way to much legal risk for me.

    • db0@lemmy.dbzer0.comOPEnglish
      1·
      1 year 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.