this post was submitted on 28 Aug 2023
730 points (98.7% liked)

Selfhosted

40198 readers
652 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
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
730
I just developed and published a script to clear your pict-rs object storage from potential CSAM. (github.com)
submitted 1 year ago* (last edited 1 year ago) by db0@lemmy.dbzer0.com to c/selfhosted@lemmy.world
104 comments fedilink hide all child comments
 

I noticed a bit of panic around here lately and as I have had to continuously fight against pedos for the past year, I have developed tools to help me detect and prevent this content.

As luck would have it, we recently published one of our anti-csam checker tool as a python library that anyone can use. So I thought I could use this to help lemmy admins feel a bit more safe.

The tool can either go through all your images via your object storage and delete all CSAM, or it canrun continuously and scan and delete all new images as well. Suggested option is to run it using --all once, and then run it as a daemon and leave it running.

Better options would be to be able to retrieve exact images uploaded via lemmy/pict-rs api but we're not there quite yet.

Let me know if you have any issue or improvements.

EDIT: Just to clarify, you should run this on your desktop PC with a GPU, not on your lemmy server!

you are viewing a single comment's thread
view the rest of the comments
[–] nick@campfyre.nickwebster.dev 2 points 1 year ago (1 children)

I think deleting images from the pictrs storage can corrupt the pictrs sled db so I would not advise it, you should go via the purge endpoint on the pictrs API.

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

Nah. It will just not find those images to serve

[–] nick@campfyre.nickwebster.dev 1 points 1 year ago (1 children)

Interesting, when I tried a while back it broke all images (not visible on the website due to service worker caching but visible if you put any pictrs url into postman or something)

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

Well you can clearly see images still here ;)

[–] nick@campfyre.nickwebster.dev 1 points 1 year ago* (last edited 1 year ago) (1 children)

True, you're correct. I'm just not sure how you did it without corrupting the sled db. Maybe I'm just unlucky

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

the sled db is not touched. It's just that when pict-rs is trying to download the file pointed by the sleddb, it's get a 404