In the past months, there’s a been a issue in various instances where accounts would start uploading blatant CSAM to popular communities. First of all this traumatizes anyone who gets to see it before the admins get to it, including the admins who have to review to take it down. Second of all, even if the content is a link to an external site, lemmy sill caches the thumbnail and stores it in the local pict-rs, causing headaches for the admins who have to somehow clear that out. Finally, both image posts and problematic thumbnails are federated to other lemmy instances, and then likewise stored in their pict-rs, causing such content to be stored in their image storage.
This has caused multiple instances to take radical measures, from defederating liberaly, to stopping image uploads to even shutting down.
Today I’m happy to announce that I’ve spend multiple days developing a tool you can plug into your instance to stop this at the source: pictrs-safety
Using a new feature from pictr-rs 0.4.3 we can now cause pictrs to call an arbitary endpoint to validate the content of an image before uploading it. pictrs-safety builds that endpoint which uses an asynchronous approach to validate such images.
I had already developed fedi-safety which could be used to regularly go through your image storage and delete all potential CSAM. I have now extended fedi-safety to plug into pict-rs safety and scan images sent by pict-rs.
The end effect is that any images uploaded or federated into your instance will be scanned in advance and if fedi-safety thinks they’re potential CSAM, they will not be uploaded to your image storage at all!
This covers three important vectors for abuse:
- Malicious users cannot upload CSAM to for trolling communities. Even novel GenerativeAI CSAM.
- Users cannot upload CSAM images and never submit a post or comment (making them invisible to admins). The images will be automatically rejected during upload
- Deferated images and thumbnails of CSAM will be rejected by your pict-rs.
Now, that said, this tool is AI-driven and thus, not perfect. There will be false positives, especially around lewd images and images which contain children or child-topics (even if not lewd). This is the bargain we have to take to prevent the bigger problem above.
By my napkin calculations, false positive rates are below 1%, but certainly someone’s innocent meme will eventually be affected. If this happen, I request to just move on as currently we don’t have a way to whitelist specific images. Don’t try to resize or modify the images to pass the filter. It won’t help you.
For lemmy admins:
- pictrs-safety contains a docker-compose sample you can add to your lemmy’s docker-compose. You will need to your put the .env in the same folder, or adjust the provided variables. (All kudos to @[email protected] for the docker support).
- You need to adjust your pict-rs ENVIRONMENT as well. Check the readme.
- fedi-safety must run on a system with GPU. The reason for this is that lemmy provides just a 10-seconds grace period for each upload before it times out the upload regardless of the results. A CPU scan will not be fast enough. However my architecture allows the fedi-safety to run on a different place than pictrs-safety. I am currently running it from my desktop. In fact, if you have a lot of images to scan, you can connect multiple scanning workers to pictrs-safety!
- For those who don’t have access to a GPU, I am working on a NSFW-scanner which will use the AI-Horde directly instead and won’t require using fedi-safety at all. Stay tuned.
For other fediverse software admins
fedi-safety can already be used to scan your image storage for CSAM, so you can also protect yourself and your users, even on mastodon or firefish or whatever.
I will try to provide real-time scanning in the future for each software as well and PRs are welcome.
Divisions by zero
This tool is already active now on divisions by zero. It’s usage should be transparent to you, but do let me know if you notice anything wrong.
Support
If you appreciate the priority work that I’ve put in this tool, please consider supporting this and future development work on liberapay:
All my work is and will always be FOSS and available for all who need it most.
Db0 the fuckin hero 🙏
Well done!
Just want to add - i’ve been using this (via my desktop!) for my instance for a little while now and its great - While the evidence shows there are false positives, i’ve yet to see it affect anything in real time.
Beware your B2 transaction costs though! 😭 I’m sure there is a cheaper way to do it but backblaze costs went up quite a bit.
B2 cloud storage update says:
effective October 3, we’re making egress free (i.e. free download of data) for all B2 Cloud Storage customers—both pay-as-you-go and B2 Reserve—up to three times the amount of data you store with us, with any additional egress priced at just $0.01/GB. Because supporting an open cloud environment is central to our mission, expanding free egress to all customers so they can move data when and where they prefer is a key next step.
Yeah, I had the email yesterday, but they don’t mention if this is specifically their download charge, or if the class b and class c transactions are included in this - I mean I’ll be honest, I haven’t had time to properly look into yet, but either way it should help.
deleted by creator
Are you a lawyer? This feels like FUD.
I strongly advise anyone against using this software in production, as you will be on the hook for anything this software doesn’t catch.
So if you don’t use this software, you’re not on the hook for the pictures that this tool doesn’t catch?
deleted by creator
I think you’re confused by the purpose of that statement. When the authors say not to use it for anything important, they’re basically trying to waive liability (informally). It’s kind of like how every open source license has a statement like:
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED …
If you use an open source project for air traffic control software, and a bug causes a bunch of people to die, that’s your fault, not the author of the software. The CLIP people are essentially saying that you shouldn’t use their software to build something that requires a lot of accuracy since it probably wasn’t designed to be as accurate as you need it to be.
But what I’m wondering is why you’re being so dramatic about this. You’re claiming that it’s highly dangerous/reckless/risky to use it, yet hand waving over the why.
deleted by creator
This can be used as an additional tool not a standalone solution.
deleted by creator
Yeah, while there are concerns, and they are many, with using automated tools from uncertified sources – especially for this purpose; OP is behaving suspiciously.
For abuse detection, you need to use a service that has been vetted by an actual lawyer.
Name one. That exists and already works on Fediverse instances.
It’s free.
But only for Cloudflare customers
deleted by creator
That’s not how this works.
So you can’t name one either.
If you’re running an instance, it’s your responsibility to find an appropriate tool.
That’s exactly what the admin here did, and what’s more, he did so because he was forced to do so by a lack of “appropriate” or even adequate tools.
Hence the straightforward question you failed to answer.
I don’t run an instance. CSAM is but one of the many reasons why. But I have been paying attention to the discussions regarding the flood of it here, and the impossibilities involved in starting from scratch with preventing/blocking this on a federated instance.
But for reasons I cannot begin to fathom, and with an intense interest in seeing this anti-CSAM tool remain unused, you are blithely sailing by all that with a demand for using a tool you personally could not even name and obviously does not exist in acceptable form, or it would already have been gladly implemented.
Glad he’s ignoring you and carrying on. I think I’ll do the same.
deleted by creator
🤡
For abuse detection, you need to use a service that has been vetted by an actual lawyer.
Lmao because every tech company out there is toooootallly doing that lmao. Come onnnnn give me a break, you’re on the programming.dev instance and you’re saying this shit? Have you ever shipped anything ever? You’re calling for something above and beyond anything that actually happens in reality.
The weirdest part of what you’re demanding is that your demand makes fediverse LESS protected. Imperfectly implemented protection is better than NO protection and yet you think people are safer legally by implementing nothing at all? You’re out of your fucking mind.
deleted by creator
Drop the ad hominem attacks and argue the point
Just say “insult” ffs. Speak like a normal human being. This isn’t a debate and you win absolutely nothing by using debatebro reddit language.
Nobody has to argue with your stupid ass making absurd demands on an account with 10 whole comments in its entire history. It’s incredibly obvious wrecker behaviour.
Lay off. This person is right.
We here at hexbear are concerned about protecting people from seeing csam. That’s good. The rest of lemmy is concerned about that and the very real consequences of csam uploads for the sites, which is getting dropped by hosting and registrar and prosecuted for distributing.
There are already cases where that kind of legal dos attack has worked, there’s even cases of anti csam organizations uploading it to reverse image search sites and then serving them papers when the reverse image search site displays the uploaded image to compare with nonexistent results.
The person you’re replying to isn’t trying to fuck shit up, they’re telling you that this tool won’t actually solve the problem it’s marketed for.
E: edited for clarity and kindness
Nah fuck off is he. Imperfect protection is an improvement over no protection, you are literally doing what the utopian socialists do, demanding perfect and rejecting anything that is an extremely obvious improvement over what existed before simply because it’s not perfect.
It’s an incredibly easy calculus to perform.
I think you’re off base here. The utopian socialists were arguing against the methods and outcomes of revolutionary socialism, this person is trying their best to explain that this particular tool has serious legal repercussions within the framework we all live under. Those are pretty different.
The reason I see the logic in their arguments is because there’s longstanding legal precedent for misuse of a tool or material because it’s better than nothing to not be a defense even if there are no other options available.
So if you built a car so big no type of shock absorber could handle it cornering at speed and you knew it, using some amazing whiz bang material for shocks isn’t a defense because even though it’s the best thing you knew it wouldn’t work.
Legally speaking, the right choice there is not to make an excessively dangerous vehicle if you don’t want to be held liable for negligence.
It’s also the argument throughout unsafe at any speed although the courts always seem to side with the automakers 🤔
Or if one were to get sued for hosting csam, using the latest whiz bang ai system for detection wouldn’t be a defense or even a point in your favor because you knew it wasn’t a reasonable use of the underlying technologies. You can’t say “judge, I was relying on the ai csam detector!” When the component parts of the ai csam detector have big “prototype, do not use in production” stickers all over them.
Ultimately while these tools might protect mods and users from having to view csam in the moderation process, that’s just one side of the struggle and on its other side they’re a paper shield at best and proof of negligence at worst.
trying their best to explain that this particular tool has serious legal repercussions within the framework we all live under.
No they’re not. They’re making up bullshit. The legal framework that social media sites where user generated content exists are expected to follow is “take reasonable measures within the resources of your organisation to prevent it” in almost every single country in the world. That’s certainly the tl;dr of how it works for the US and EU anyhow.
This is above and beyond what other major platforms are doing. If you went to imgur right now and slyly uploaded CSAM absolutely fuck all would happen until someone reports it. There is NO proactive approach to countering it at the point of upload. Not on youtube, not on imgur, not on facebook, not fucking anywhere. They all don’t do it because they all don’t have to do it, they all argue that what they’re doing is reasonable, and will cite some absurd percentage of user uploaded content to CSAM reports as their reasoning for it.
If we’re better than that on services without any source of profit-based income we’re absurdly above any level of “reasonable” that exists.
The mistake here is people acting like online social media organisations (which each of these lemmy instances absolutely is as an entity) are regulated in the same way as a random shmuck individual. They’re not. If they were then 4chan would have been shut down 20 years ago and Moot would’ve been imprisoned for life.
deleted by creator
deleted by creator
deleted by creator
Stop supporting CSAM you law pervert. It might surprise you to learn there’s a lot of jurisdictions around.
deleted by creator
On Reddit there were always so many concern Karen’s peddling FUD when you say anything critical of pedos. For the longest time on Reddit all you had to do was see if the user also posted in pedofriends.
It was so obvious.
Any attempt to do anything that might impact a pedophile and there was quickly a brigade saying why that was a wrong.
No. Any action that supports pedophiles is morally wrong and we should NOT let perfect be the enemy of good when trying to make it more difficult to be a pedophile or support pedophiles.
If you have a solution that’s better, implement it and share it as Open Source.
Otherwise crawl back in your pedo hole at reddit and leave us alone.
deleted by creator
I called concern troll and then mentioned that on Reddit the subreddit pedofriends uses concern trolling as a tactic to prevent people from doing anything about pedophiles.
I never said you were a pedophile, but way to out yourself as overly concerned with people being labeled pedos cuz you have such a big heart for protecting pedophiles.
While the OP’s concerns were largely… dubious(?), simply going through with literally whatever solution is just as big of a problem. I haven’t reviewed anything about this implementation in depth, thus can’t make any statements towards quality or truthfulness (except that 1% FP seems very optimistic), but you shouldn’t simply assume it will solve your problem without introducing another. Having said that, the author appears very well intentioned and has experience on the subject, so the veredict shouldn’t take long.
The solution is to try.
In dev it’s called “fail fast”
You try several solutions to the problem and iterate until you find the best working option then optimize.
There’s no harm in an independent open source dev trying to solve a problem. Even if they fail there might be a kernel of useful code in a novel way.
You absolutely shouldn’t just settle on one option without exploring several.
But being stuck in a loop of over planning, waiting for legal, or outsourcing the problem is why everyone hates waterfall and just has small teams try with “agile” now.
1% failure is just the start. You should never call a beta shit cuz it fails sometimes. Failure is part of learning and improving.
How does one even test this ethically?
There are I think official “training kits”? I remember reading about this, there are sets of data you can get to train CSAM detection with.
Its a general image classifier. You don’t need to train it specifically on CSAM if you are willing to accept a certain false positive rate.
I think “legally” and “without constantly wanting to vomit” is the trickier question. From a purely ethical standpoint I don’t see a problem with taking CSAM that’s apparently already flooding Lemmy and using it to test whether your filter works before nuking it. At least as long as you’re making sure you’re not exposing anyone else to it.
What’s CSAM?
Child Sexual Abuse Material. Child porn.
Eww. Good riddance.
Child sexual abuse materials. Vile shit
Child pornography
I’m curious how an AI like this is trained
interesting read, thank you
given CLIP has a high zero-shot learning success rate, was it functional for this use case out of the box? or were further modifications required?
It requires specific usage of clip. Check the horde-safety repo if you’re interested
deleted by creator
We’re not using blip
deleted by creator
it’s my understanding that the csam datasets (once already labeled by people) are hashed to the point of being unrecognizable before being passed around.
I don’t think training a model on hashes would be particularly useful - if the model were able to get any meaningful information out of it, that would mean the hash function itself is somehow leaking enough of the original contents to determine the image contents (which would essentially mean the hash function is broken beyond all repair)
you know what that makes sense so I looked into it, one method of detecting csam is hashing the image and comparing it to a database of hashes of known csam images. so I guess that method might not work for “original” csam images.
apple csam detection [download]
interestingly, Google says they use AI also but didn’t really get into the details.
AFAIK it should work as long as the hashing function has some direct transformation property which can be extrapolated by the AI.
(Not an industry veteran, I dabble in AI mostly for hobby and sometimes work, but do have some accredited education on the subject. I may well be way off mark)
deleted by creator
holy hell this is massive
thank you for your work db0
Great work, this is the biggest issue that Lemmy has a the moment, I hope the admins will be able to set this up easily and start to take back all the preventative measures.
Has this been a problem since the initial spam wave? I wasn’t aware the issue was ongoing. But the less pedos, the better.
External images aren’t federated to Hexbear, so your instance is mostly unaffected by the disgusting trolls doing this stuff.
From what I’ve been hearing, it’s sadly been still ongoing :(
hexbear dub. big salute to the admins and mods
Some major instances like .ee shut down image uploads immediately and only restored them in a truncated fashion, if at all.
Cool. After some testing Hexbear should run it. Not that the problem has ever been serious for Hex but still worthwhile and work that should absolutely be supported.
deleted by creator
I think people are going to be much more concerned about the false negative rate than the false positive rate.
https://blog.cloudflare.com/the-csam-scanning-tool/
Does this not work?
Not for all csam and not at all for novel generative ai csam. It’s also not for all countries nor is it easy for everyone to join it and not everyone wants to be on cloudflare. Same is true for other tools like photodna
Yes, and it works without all the legal issues involved with doing it yourself.
You’re a laywer?
Have you considered federating hashes of positive matches and working with the Lemmy team to not outward federate on a local positive match (and potentially have the hash go instead)?
The former can reduce overhead and electricity use, and the latter will stop more distribution and aid those sans-GPU who can’t run it.
Over time, the hash DB will grow and get better. In addition, perhaps there is metadata that can be used to track image similarity to positive matches to reduce false-positives, but I imagine that algorithm would be much more complicated.
Hashes won’t work for novel GenerativeAI images. For this kind of thing we need to be sharing tensors and comparing distances so that it catches format changes and compression artifacts. Theoretically possible. Practically, I don’t know how feasible it is.
How large is each tensor? If it can be stored as JSON or Base64 and is of sufficiently small size, integration into ActivityPub wouldn’t be all that bad. The time consuming part would likely be integration into Lemmy itself.
Another option would be a separate service, similar to how Lemmy Explorer works, where a list of the latest tensors can be downloaded. It’s centralized vs distributed, but probably easier to implement. Just an API admins can register for to send and get tensors.I would be happy to assist with this if it is a route you would like to explore. Feel free to DM me.
@fmstrat each tensor is small. The problem is when you have millions of them and you have to compare each image to each. You can’t index this. It has to be one by one. And you still need to covert the new image to tensors as well,which still needs gpu. I just don’t see anything useful here. The current system would be faster.
Good point. I wonder how the commercial hash-based systems are doing it…
False positive rate ~1 % False negative rate?
