- cross-posted to:
- selfhosted@lemmy.world
- cross-posted to:
- 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!
They have been used on millions of websites already. It’s pretty clear that it works. It doesn’t need to be used on lemmy to prove it works. And my application is currently in review so no I haven’t used it. But that really doesn’t matter. Especially if you’re comparing it to a tool written by one person that has been out for a few days.
The situation Has dramatically changed in the the past year. I am telling you but you seem to be in denial. Likewise currently you’re unprotected. As such my previous statement applies: good luck!
What situation? You haven’t told me anything about anything changing in the last year.
Huh? What previous statement? You’re not protected. You just think you are! You literally claimed that your product has lots of false positives. It most definitely has false negatives too.
The situation is that anyone can ai generate any amount of novel csam now.
…. That’s not what CSAM is. It’s literally in the name. abuse. CSAM requires abuse of a child. Just like pictures of your kids in the bath isn’t illegal, AI generated content is going to need to be provably linked to abuse in order to meet the definition. I seriously doubt it ever will be. You seem to have a fundamental misunderstanding of the entire situation, overreacted so much so that you might have gotten people in serious legal trouble, and are now trying to justify it because you think that the current solutions aren’t going to protect against CSAM.
I literally linked a software that does what yours does, but is already used, already proven to work, and also has the benefit of being the backup to the hash based mechanism instead of being the primary mode of filtering.
Dude, I was trying to be nice how I approached you earlier, but you clearly are unwilling to accept that you have made a massive mistake here, not only by not reading up on the laws, but not even fundamentally understanding the problem space. This is not good software engineering.
Omg! If someones starts posting photorealistic generated csam to your instance, is this what you’re going to tells to your userbase when you refuse to delete it? Are you for real? In that case, good fucking luck!
removing inappropriate sexual content is completely different than CSAM… a point you seem to be trying INCREDIBLY hard to not understand. Dude, just quit. Please please stop with this nonsense. You are unable to let it go. Every one of us builds bad software at some point. For you this is it. Just let it go, go build something else.
Sheesh.
Lol, I really pity your users if that’s what you’re like talking to other admins.
Look, maybe I can make it very plain for you to finally get. You will not be able to recognise it’s not ai generated and your “proper solution” won’t catch it. Your users will freak the fuck out.
Use your brain. I’m out
it’s clear from your comments here and in matrix that you think you’re always right and you clearly can’t take criticism. Good luck in the future dude. You’re going to need it.