810
submitted 1 year ago* (last edited 1 year ago) by db0@lemmy.dbzer0.com to c/selfhosted@lemmy.world

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!

(page 2) 50 comments
sorted by: hot top controversial new old

Can this be used with Mastodon as well?

load more comments (1 replies)
[-] ensignrick@startrek.website 5 points 1 year ago

Amazing work.

[-] dipshit@lemmy.world 5 points 1 year ago

Just going to argue on behalf of the other users who know apparently way more than you and I do about this stuff:

WhY nOt juSt UsE thE FBi daTaBaSe of CSam?!

(because one doesn’t exist)

(because if one existed it would either be hosting CSAM itself or showing just the hashes of files - hashes which won’t match if even one bit is changed due to transmission data loss / corruption, automated resizing from image hosting sites, etc)

(because this shit is hard to detect)

Some sites have tried automated detection of CSAM images. Youtube, in an effort to try to protect children, continues to falsely flag 30 year old women as children.

OP, I’m not saying you should give up, and maybe what you’re working on could be the beginning of something that truly helps in the field of CSAM detection. I’ve got only one question for you (which hopefully won’t be discouraging to you or others): what’s your false-positive (or false-negative) detection rate? Or, maybe a question you may not want to answer: how are you training this?

[-] db0@lemmy.dbzer0.com 4 points 1 year ago* (last edited 1 year ago)

I'm not training it. Im using publicly available clip models.

The false positive rate is acceptable. But my method is open source so feel free to validate on your end

[-] dipshit@lemmy.world 5 points 1 year ago

Acceptable isn’t a percentage, but I see in your opinion that it’s acceptable. Thanks for making your content open source. I do wish your project the best of luck. I don’t think I have what it takes to validate this myself but if I end up hosting an instance I’ll probably start using this tool more often myself. It’s better than nothing at at present I have zero instances but also zero mods lined up.

[-] BeAware@lemm.ee 4 points 1 year ago

Now if you can make this work with mastodon, i'd be eternally grateful.😁

[-] db0@lemmy.dbzer0.com 8 points 1 year ago

It's software agnostic. So long as you're storing you're images in object storage, it should work

[-] lemmy@lemmy.stonansh.org 3 points 1 year ago

Can this be used with the Lemmy-easy-deploy method?

[-] db0@lemmy.dbzer0.com 4 points 1 year ago

This shouldn't run on your lemmy server (unless your lemmy server has a gpu)

[-] lemmy@lemmy.stonansh.org 1 points 1 year ago
[-] db0@lemmy.dbzer0.com 1 points 1 year ago

I don't know your setup, but unless it's a very cheap GPU, it would be a bit of a waste to use it only for this purpose. But up to you

[-] nick@campfyre.nickwebster.dev 3 points 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.

[-] db0@lemmy.dbzer0.com 1 points 1 year ago

Nah. It will just not find those images to serve

[-] nick@campfyre.nickwebster.dev 1 points 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)

[-] db0@lemmy.dbzer0.com 1 points 1 year ago

Well you can clearly see images still here ;)

[-] nick@campfyre.nickwebster.dev 1 points 1 year ago* (last edited 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.com 1 points 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

load more comments
view more: ‹ prev next ›
this post was submitted on 28 Aug 2023
810 points (98.9% liked)

Selfhosted

39550 readers
354 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS