155
Lemmy's Image Problem (Updated 02-06-2024)
(wedistribute.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Mar 2024
155 points (81.4% liked)
Fediverse
17016 readers
19 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 4 years ago
MODERATORS
Well, yeah...
If you upload a picture to Lemmy, it's going to get saved by a shit of federated instances.
That's how federation works, but once it happens, it's hard to get all of them to delete it.
The fix is easy:
Upload somewhere else (theres a bunch of images hosts) then make your post point to that image host. Federated instances just have to host the link, so it's good for them too.
I'd love to see something like the RES feature where Lemmy can still show an expandable thumbnail for non-hosted images. RES pulled it off fine years ago, not sure how hard it would be.
But that would fix all these issues
So, to be clear, the story the article links to is specifically a case of local content that didn't actually federate. It was an accidental upload, he cancelled the post, it sat in storage, and even his admin was stumped about how to get it out.
I agree that with federation, it's a lot more messy. But, having provisions to delete things locally, and try to push out deletes across the network, is absolutely better than nothing.
The biggest issue I have is that there's really not much an admin can do at the moment if CSAM or some other horrific shit gets into pict-rs, short of using a tool to crawl through the database and use API calls to hackily delete things. Federation aside, at least make it easy for admins and mods to handle this on their home servers.