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 @Penguincoder@beehaw.org 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:
https://liberapay.com/db0/
All my work is and will always be FOSS and available for all who need it most.
Respectfully, this is a gross misuse of CLIP. It is an experimental research tool, and the authors were very explicit that they were not designed to be used for critical workflows like abuse detection.
I strongly advise anyone against using this software in production. For abuse detection, you need to use a service that has been vetted by an actual lawyer. Full stop.
Edit: not BLIP
Are you a lawyer? This feels like FUD.
So if you don't use this software, you're not on the hook for the pictures that this tool doesn't catch?
This software is a bandaid around the problem. If you're using it, it will just give you a false sense of security. I cannot emphasize enough, do not use experimental research tools for legally sensitive use cases.
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:
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.
That's not the statement I'm referring to. This is the statement I'm referring to:
Source: https://huggingface.co/openai/clip-vit-large-patch14
It's dangerous for the same reason you shouldn't use tin foil for load bearing struts. There's a reason that the creators of websites are required to block CSAM, and using half-baked tooling that doesn't work is blatantly skirting around the issue.
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.
Drop the ad hominem attacks and argue the point. The creators of the tool said "Do not use this for important use cases!" What do you have to respond to that?
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.
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.
I uh actually agree with you almost entirely. Except at the end I’m like “and that’s why it won’t work as protection”.
Software hasn’t been treated like other fields of engineering and all operators have needed for protection from liability was the twin shields of “nothing I could do” and “I was doing nothing” to come out of any courthouse relatively unscathed.
That type of “aww shucks technocracy” is only possible if you do the bare minimum or nothing at all. Once an operator implements some kind of protection (yes, even one with warning labels all over it), both defenses are rendered unusable.
Now that you’ve done something you’re able to be held liable for the effects of what you’ve done and for knowing there was a problem.
The picture gets even murkier when we look at how things are going! Lawsuits against Tesla for their self driving deaths are making waves not because they impugn the dignity of Americas biggest car manufacturer by market cap but because every judge who sees one raises the biggest eyebrow possible at software engineering not being held to the same standard as any other type, both in a court of law and within its own process.
There’s a good chance that software PEs will become a thing (again?) as a result.
The long and short of it is that because the only reason monsters like moot are able to exist is their sly lethargy and looking at the legal storm rolling into software engineering, having something bolted onto the backend like this would be a bad idea.
I think automated tools like this can be put to use though if they were hosted separately and provided with an api that linked up nicely with some moderation queue standard and returned something like “entries 1,5 and 9 are likely csam” back to the moderator. It would at least save the mod from dealing with the material directly.
So I guess I agree but come to the opposite conclusion.
You still haven't argued the point. You're really bad at this, aren't you?
Coming from the person making ad hominem attacks, projection much?
I'll survive. But I'm rooting for you, pal. Maybe someday you'll even get to troll in the big leagues.
Name one. That exists and already works on Fediverse instances.
That's not how this works. If you're running an instance, it's your responsibility to find an appropriate tool. This is not an appropriate tool, and the creators of it have specifically warned against using it. Don't use it.
A simple search shows that there are dozens of actual vetted services you can use, some of which are open source.
🤡
So you can't name one either.
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.
If you read my comments, you can see that I recommended another better solution elsewhere. But instead you're just choosing to argue for no reason.
deleted by creator
I'm the one arguing for stricter and better abuse detection here, so I'm not sure what your point is.
deleted by creator