What is CSAM?
Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
If the source deletes the post. Won’t that remove it from all the instances ?
I'm not subscribed to that community, but I guess I'm glad Pictrs doesn't work for me, since I am using the Yunohost version of Lemmy. The creators of the Yunohost package couldn't get it to work. I haven't really missed it honestly.
Could someone please ELI5 that script. I'm all for keeping things clean, but old enough to remember the days of console based trolling.
Looks fairly sane, finds every file in the given directory that was created in the last 24 hours and deletes them. Personally if you are dealing with CSAM I'd be using shred
instead of just rm
sudo
As root
find /srv/lemmy/example.com/volumes/pictrs/files
Find files in /srv/lemmy...
that:
-type f
Are plain files (not directories, symlinks, etc; includes images)
-ctime -1
And were created within an amount of time (probably last day, haven't used this flag in a while)
-exec rm {} \\;
For each matching file found execute rm
on it (delete it).
Likely Spez’s personal jailbait collection
There was a weird JSON error I was getting in the last few minutes. I'm not sure if this is at all related.
I am using the Lemmy easy deploy would this command works?
You'll need to find where the actual container files are being stored. I'm unfortunately not familiar with Lemmy Easy Deploy, but you should have a folder that has some files/folders like docker-compose.yml
, volumes
, lemmy.hjson
.
The important one is the volumes/pictrs/files
folder, take the full path of that folder and replace it with the /srv/lemmy/example.com...
path from the original post, and then that command should work.
Couldn't this be stopped with automatic filtering of bad content? There are open source tools and libraries that do this already
That's what we're pushing the lemmy devs to do. Honestly even if they want to use proprietary tools for this instance I'm okay, I'll happily go register an Azure account and plop an API key into the UI so it can start scanning. Lemmy should have the guardrails to prevent this from ever hitting our servers.
In the meantime, services like cloudflare will handle the recognizing and blocking access to images like that, but the problem still comes down to the federation of images. Most small hosters do not want the risk of hosting images from the whole of the internet, and it sounds like there is code in the works to disable that. Larger hosters who allow open registrations can do what they please and host what they please, but for us individual hosters we really need tools to block this.