this post was submitted on 31 Aug 2023
363 points (99.5% liked)

Selfhosted

40018 readers
660 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
363
Lemmy Safety now supports cleaning local pict-rs storage from CSAM (github.com)
submitted 1 year ago* (last edited 1 year ago) by db0@lemmy.dbzer0.com to c/selfhosted@lemmy.world
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
[–] Earthwormjim91@lemmy.world 6 points 1 year 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 0 points 1 year ago (1 children)

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

[–] SharkEatingBreakfast@sh.itjust.works 4 points 1 year ago

In order to get the answers you're looking for, put out the question "what exactly does this statement mean?" instead of "sounds like this means ___" and waiting for a confirmation/rejection of your assumption.