Appreciate your work.
bmygsbvur
joined 1 year ago
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.
Sadly not the case
This is one way to solve it.
I'm not knowledgeable with SQL. If you know or if anyone knows how to fix it with a script or built into Lemmy, please share.
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.
They probably have the tools to deal with it. Lemmy certainly doesn't.
Very much needed.
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.