this post was submitted on 31 Aug 2023
359 points (99.4% liked)

Selfhosted

40183 readers
687 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
359
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
[–] poVoq@slrpnk.net 5 points 1 year ago (1 children)

Thanks for adding this. I guess I now have my weekend planned for moving Pict-rs to a server with a fast enough GPU and try this out πŸ€”

[–] db0@lemmy.dbzer0.com 7 points 1 year ago (1 children)

You don't need to move pict-rs to a GPU server. In fact that would be prohibitedly expensive long-term. I suggest you just use your PC to run this against your current pict-rs server, or just rent a GPU server for this time.

[–] poVoq@slrpnk.net 3 points 1 year ago* (last edited 1 year ago) (1 children)

I have a server with a smaller Nvidia GPU available. I hope the 3GB vRAM it has will be sufficient.

[–] db0@lemmy.dbzer0.com 4 points 1 year ago (1 children)

OK, but just to point out that the script hasn't been setup to run locally yet. Just through ssh. Making it look for the files locally is my next to-do

[–] poVoq@slrpnk.net 4 points 1 year ago (1 children)

Ah, I was already wondering why it would need SSH keys to scan local files πŸ˜… Well, I only have time to look into this on Sunday I think, so no rush.

[–] teawrecks@sopuli.xyz 1 points 1 year ago (1 children)

You could always SSH into localhost I assume.

[–] db0@lemmy.dbzer0.com 1 points 1 year ago (1 children)

Yes that would work, but it's a bit unnecessary

[–] teawrecks@sopuli.xyz 1 points 1 year ago

Yeah, just meant it should be a valid workaround in the event they want to try it before your local scan feature is ready.