Selfhosted

39929 readers

419 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:

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!

founded 1 year ago

MODERATORS

366

Lemmy Safety now supports cleaning local pict-rs storage from CSAM (github.com)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted

44 comments fedilink hide all child comments

I posted the other day that you can clean up your object storage from CSAM using my AI-based tool. Many people expressed the wish to use it on their local file storage-based pict-rs. So I've just extended its functionality to allow exactly that.

The new lemmy_safety_local_storage.py will go through your pict-rs volume in the filesystem and scan each image for CSAM, and delete it. The requirements are

A linux account with read-write access to the volume files
A private key authentication for that account

As my main instance is using object storage, my testing is limited to my dev instance, and there it all looks OK to me. But do run it with --dry_run if you're worried. You can delete lemmy_safety.db and rerun to enforce the delete after (method to utilize the --dry_run results coming soon)

PS: if you were using the object storage cleanup, that script has been renamed to lemmy_safety_object_storage.py

you are viewing a single comment's thread
view the rest of the comments

[–] BitOneZero 66 points 1 year ago* (last edited 1 year ago) (19 children)

I hope people share the positive hits of CSAM and see how widespread the problem is...

DRAMTIC EDIT: the records lemmy_safety_local_storage.py identifies, not the images! @[email protected] seems to think it "sounds like" I am ACTIVELY encouraging the spreading of child pornography images... NO! I mean audit files, such as timestamps, the account that uploaded, etc. Once you have the timestamp, the nginx logs from a lemmy server should help identify the IP address.

[+] [email protected] -55 points 1 year ago (10 children)

I hope people share the positive hits of CSAM and see how widespread the problem is…

It sounds like you're encouraging people to share CSAM images found, which is obviously not the intent of this tool. There's probably a better way to phrase what you were trying to say.

[–] [email protected] 36 points 1 year ago (4 children)

I expect they just want statistics

[–] BitOneZero 13 points 1 year ago* (last edited 1 year ago) (1 children)

Yes. odd how people think sharing CSAM is why people would post here, instead of actually tracking down and prosecuting those sharing CSAM. Details about the users who sharedl CSAM content, such as timestamps - would help identify the offenders for prosecution.

[–] [email protected] -2 points 1 year ago

I assumed as much after reading it several times, but just wanted let you know and point out that statement could be misconstrued. Thanks for clarifying!

load more comments (2 replies)

load more comments (7 replies)

load more comments (15 replies)