bmygsbvur @ bmygsbvur @lemmy.ca

Posts

2

Comments

52

Joined

2 yr. ago

Doesn't change the fact that this issue needs to be addressed. Besides, do you think all countries laws are the same?

Thanks for this.

https://sh.itjust.works/pictrs/image/08ff5623-e553-4d00-a6e2-e9fb6798a972.webp

Here is another test ^ I use a different instance to better illustrate the point because it's easy to upload images in comments. Nobody in shitjustworks will see this picture in their instance so nobody can report this picture.

This picture is just Salvadaor Dali by the way.

I can see it. It's a very nice artwork.

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

I've mentioned this before to a similar reply. But I'll say it again: this was already publicly known months ago. People just forgot about it because they didn't think it was a big deal. Now that they realize CSAM is a real issue, I made this post to remind everyone about it again. Bad actors already know about this and really, it isn't hard to figure out how this work.

Thank you. I did not see this one but it's almost two months old now. This is what I was talking about when I said that it was already a known issue back then. it just isn't being addressed. I hope this post will give more attention to this problem.

This is for public instances.

Yes. This is a great alternative solution.

"Quietly delete the images periodically". If only it was made easier for admins. You can't even report these images because nobody knows it was there in the first place.

Which is why we need to act now.

Doesn't change the fact that this is an issue that needs to be resolved.

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.

Most admins aren't in the USA. But that's not really the issue here is it?

Appreciate your work.

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?

This has been known forever. Any bad actor already knows about this. There's no reason to hide this. I am reminding people so solutions can be solved sooner. I will keep reminding until the problem is solved.

I'm not on GitHub. Someone else can submit it this and I'm very sure the Lemmy devs are aware. They just have different priorities.