EDIT
TO EVERYONE ASKING TO OPEN AN ISSUE ON GITHUB, IT HAS BEEN OPEN SINCE JULY 6: https://github.com/LemmyNet/lemmy/issues/3504
June 24 - https://github.com/LemmyNet/lemmy/issues/3236
TO EVERYONE SAYING THAT THIS IS NOT A CONCERN: Everybody has different laws in their countries (in other words, not everyone is American), and whether or not an admin is liable for such content residing in their servers without their knowledge, don’t you think it’s still an issue anyway? Are you not bothered by the fact that somebody could be sharing illegal images from your server without you ever knowing? Is that okay with you? OR are you only saying this because you’re NOT an admin? Different admins have already responded in the comments and have suggested ways to solve the problem because they are genuinely concerned about this problem as much as I am. Thank you to all the hard working admins. I appreciate and love you all.
ORIGINAL POST
You can upload images to a Lemmy instance without anyone knowing that the image is there if the admins are not regularly checking their pictrs database.
To do this, you create a post on any Lemmy instance, upload an image, and never click the “Create” button. The post is never created but the image is uploaded. Because the post isn’t created, nobody knows that the image is uploaded.
You can also go to any post, upload a picture in the comment, copy the URL and never post the comment. You can also upload an image as your avatar or banner and just close the tab. The image will still reside in the server.
You can (possibly) do the same with community icons and banners.
Why does this matter?
Because anyone can upload illegal images without the admin knowing and the admin will be liable for it. With everything that has been going on lately, I wanted to remind all of you about this. Don’t think that disabling cache is enough. Bad actors can secretly stash illegal images on your Lemmy instance if you aren’t checking!
These bad actors can then share these links around and you would never know! They can report it to the FBI and if you haven’t taken it down (because you did not know) for a certain period, say goodbye to your instance and see you in court.
Only your backend admins who have access to the database (or object storage or whatever) can check this, meaning non-backend admins and moderators WILL NOT BE ABLE TO MONITOR THESE, and regular users WILL NOT BE ABLE TO REPORT THESE.
Aren’t these images deleted if they aren’t used for the post/comment/banner/avatar/icon?
NOPE! The image actually stays uploaded! Lemmy doesn’t check if the images are used! Try it out yourself. Just make sure to copy the link by copying the link text or copying it by clicking the image then “copy image link”.
How come this hasn’t been addressed before?
I don’t know. I am fairly certain that this has been brought up before. Nobody paid attention but I’m bringing it up again after all the shit that happened in the past week. I can’t even find it on the GitHub issue tracker.
I’m an instance administrator, what the fuck do I do?
Check your pictrs images (good luck) or nuke it. Disable pictrs, restrict sign ups, or watch your database like a hawk. You can also delete your instance.
Good luck.
Did you opened an issue on github?
You are wording this as a clickbait news article.
You find an issue, you report it to the right channel, you notify it. Good. This is how software development work, with active community reporting issues.
But why using such tone?
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?
Creating a product of any size is about planning.
If you notify here, your information will be lost in 2 days. People forget, and move on to the next hot topic. Relevant stakeholders might very well completely miss this post, because they are not 24/7 on lemmy.
The way to make it more relevant is going in the place where the planning is done, i.e. Github for lemmy. Open an issue there, explain the problem and describe possible solution. Come back to lemmy, link the issue and ask people to react to it (i.e. show it is relevant for them).
This is the best way to obtain what you ask. Social media platforms are too broad and fuzzy for tracking real issues.
This is also why you see a lot of work is done on performances of sql of lemmy backend, because most issues in the past on github concerned that.
This is my suggestion. If you really care about this being implemented, open a ticket on github and follow the discussion there. If you see there is not enough traction ask help to fellow lemmings.
Suggestions for the github issue are:
If your solution is good, great, if not, people are more willing to think about a problem to show stranger on the internet they are wrong
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.
Signing up for GitHub and opening this issue would take about as long as making this post.
You could’ve just done it yourself if you felt so passionate about it. Badgering people into action rarely works.
I’m not badgering, I’m demystifying the process.
I haven’t experienced myself the issue. I trust your experience, but I cannot completely reproduce/describe it, as I am not selfhosting. I couldn’t answer in case of questions from developers regarding this.
Best would be for you to report this. You can create an issue here:
https://github.com/LemmyNet/lemmy/issues
There is a simple template to fill, and you can copy and paste most text from this thread.
You don’t need to selfhost to reproduce this. Anyone can do this and that’s the problem.
Not sure why you’re getting downvoted, since you gave clear instructions that anyone can follow to verify what you said.
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.
Here you go, two steps:
https://github.com/signup
https://github.com/LemmyNet/lemmy/issues/new/choose
The other best way to do this is to actually submit the issue in the appropriate location so the Lemmy devs can track and respond to it.
It’s been 7 hours, it can’t be that hard to make a github account and format this post into an actually helpful github issue.
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.
Are you aware of the consequences of your actions? You didn’t inform the people who can fix this issue of the potential impact, no. You informed the Lemmy community that they can upload whatever they want, and some of them are pedophiles. Not cool at all. Responsible disclosure ain’t a thing outside of cybersecurity I suppose, though irresponsible disclosure is prevalent everywhere. Very irresponsible.
Rogues are very keen in their profession, and know already much more than we can teach them.
How would they address your concerns? The chances that one of the devs follows you is nonexistent, I would wager. Instead of using the proper channels to inform them, you did the exact opposite and posted it someplace they are almost guaranteed not to see it.
It’s on the GitHub issue tracker already. Did you not read the post?