Selfhosted

60723 readers

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

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

339

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

submitted 2 years ago* (last edited 2 years ago) by db0@lemmy.dbzer0.com to c/selfhosted@lemmy.world

42 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

[–] Earthwormjim91@lemmy.world 7 points 2 years ago (1 children)

Why are you such a weirdo where that’s where your mind goes.

Sharing positive hits isn’t saying share the images. It’s saying share the data on who what when where how the hit showed up positive.

Who shared it.

What was it (this is obviously going to be some kind of CSAM given that’s the tool).

When did they share it (time stamps).

Where did they share it (was the same image hit on other runs and what instances did it hit on with the tool).

How did they do it (local sharing, an image hosting service, etc).

[–] bamboo@lemmy.blahaj.zone 1 points 2 years ago

You list great points of information that should be shared to admins of other instances. Thanks for clarifying.