Doesn’t change the fact that this is an issue. Besides, do you think American law applies everywhere?

It’s on the GitHub issue tracker already. Did you not read the post?

Very easily you say? Maybe tell us what this cron job is so we can all add it?

Doesn’t change the fact that this is an issue.

Rogues are very keen in their profession, and know already much more than we can teach them.

Whether it’s illegal content or storage-filling DoS attacks, the issue needs to be addressed.

Sadly not everyone bothered to read the post and just jumped to the comments. Again its like the Mastadon CSAM issue last month. People don’t read the paper and act so defensively about it. Now Lemmy is experiencing the same problems, people suddenly act differently?? Crazy.

Because there’s already an issue dated July 6: https://github.com/LemmyNet/lemmy/issues/3504

Like I said, people already know about this months ago.

I don’t care if you don’t like my English writing. I brought up the issue and if people don’t care about it then whatever. We’ll just have to wait until it’s abused then maybe people will be actually concerned.

Entitled attitude? I’m just bringing it up again. It was brought up some time ago but wasn’t given attention so I’m bringing it up again after the recent CSAM attacks.

I didn’t demand anything in the post. I brought up the issue, explained why it’s important, and what admins could do about it.

I don’t know how to code but that doesn’t mean I’m not allowed to bring this issue to light…

This is for public instances.

Which is why we need to act now.

You don’t need to selfhost to reproduce this. Anyone can do this and that’s the problem.

They are stored in the pctrs folder. They don’t have file extensions but are viewable with many image programs.

Feel free to open the issue on my behalf. I am not a software developer. You seem to know more about this. I’m just reminding people something that I and many others have observed months ago.

The issue is that you can share the image link to other people. People CAN get the content back out and admins or moderators WILL NOT KNOW about it.

So if someone uploads an illegal image in the comments, copies the link and does not post the comment, then they have a link of an illegal image hosted on someone’s Lemmy instance. They can share this image to other people or report it to the FBI. Admins won’t know about this UNLESS they look at their pictrs database. Nobody else can see it so nobody can report it.

I’m not on GitHub. Nor is a lot here. I’m wording it this way so the issue gets the attention it deserves. Anyway, everybody already knows about this but nobody understood the consequences. Same reason why there’s no option to disable image caching. These issues should have been addressed the moment image uploading was made available in Lemmy. It was just overlooked because of how tiny the platform was then.

It’s funny because last month Mastodon CSAM was a hot topic in the Fediverse and people were being defensive about it. Look where we are now. Has Mastodon addressed the CSAM issue? Did they follow the recommendations made by that paper? I don’t think so. There wouldn’t be an open GitHub issue about it. Will Lemmy be like Mastodon or will it addressed the concerns of its users?

Sadly not the case

That’s another issue. Also a necessary feature.

This is a nice tool but orphaned images still need to be purged. Mentioned on the other thread that bad actors can upload spam to fill up object storage space.