Nah I didn’t say that it’s bad lol. Didn’t mean it that way, at least. The way I understand the “fuck, marry, kill” game is that:

• Fuck: down to play with it every once in a while
• Marry: always down to use it
• Kill: never want to use it

but if someone else wants to play with Rust who am I to stop them

There’s plenty of applications that aren’t critical enough to require precise memory management and where a GC is a worthy tradeoff for the simplicity that Go brings to the table, but sure, if you are interested in going super low level that’s what you are left to work with.

And it’s probably fine. If I had to pick between C++ and Rust I would choose the latter any day of the week but thankfully not every developer has to go that low.

I was under the impression that the Go compiler was written in C/C++, though don’t quote me on this one. My browser however is Firefox, so touché on that one.

Hot take:
Fuck TS, marry Go, kill Rust.

Interesting. That would be a nice extension, I think most small admins are using the filesystem (I know I am lol).

No. Unfortunately it only works with storages on object storages like S3 buckets, not with filesystem storages. Meaning it access the files remotely one at a time from the bucket, downloading them over the internet (I assume, I didn’t make this).

But the more important thing is that, as it states in the readme, no files get saved to your disk, they only stay in your RAM while they are being processed and everything is deleted right after. This is relevant because even having had CSAM on your disk at some point can put you in trouble in some countries, with this tool it never happens.

Which btw is the same reason why mounting the pict-rs folder to your local computer is probably not a good idea.

Yeah I know. It’s supposed to be ran from your computer, not the VPS.

Same, it’s the reason why I can’t stand working with python.

Thank you for doing this, btw. Once you have something working on your hands you could consider spreading the word, maybe to db0 himself. I sure would love a convenient way to run that script, and many other admins probably would too.

I see. I considered the dependency problem but only thought of using a venv to fix that, however you are right, the python version is also often the cause of compatibility issues.

Sorry I haven’t ran this myself yet nor have any experience with that kind of issues. But may I ask why you were concerned with running it inside of a container? Seems rather unnecessary to me.

That is also very true. I think better tooling for that might come with the next pict-rs version, which will move the storage to a database (right now it’s in an internal ky-value storage). Hopefully that will make it easier to identify orphaned images.

I’m an instance administrator, what the fuck do I do?

There’s one more option. The awesome @db0@lemmy.dbzer0.com has made this tool to detect and automatically remove CSAM content from a pict-rs object storage.

https://github.com/db0/lemmy-safety