When an instance goes down, all of the images on it go with it. there’s going to be a lot from lemm.ee, especially given its size.
You must log in or register to comment.
Not a solution, but this is a great reminder to add descriptions/alt text to your images.
I’m gonna run some scripts on my instance’s database to look for posts that have lemm.ee pict-rs URLs and local thumbnails. Then update the url value to that of the local thumbnail_url. That’ll at least fix them on my instance where I have a copy.
I won’t be doing that until after lemm.ee shuts down, otherwise the original values will federate back in if there’s any activity on the posts.
For comment images or ones where my instance didn’t create a thumbnail, they’ll just have to be broken I guess - same goes for the community icons, though I suppose I could go ahead and get local versions of those and update the communities afterward. Prob also set those to “Mods only” in the database to keep local users from trying to post there.
For user avatars, I’ll probably just clear those in the database so when looking back at old content from .ee, it won’t try to fetch them and timeout/404.
There were less posts to worry about then, but for community icons and user avatars, that’s the same thing I did when kbin shut down.
Mind empowering my laziness and sharing that query?
I was also planning on bulk locking all their communities, to avoid any isolated islands of people that don’t realize the community is gone.
Lemm.ee had and still has strict limitations to image uploads, forcing its users to use external image providers like catbox.moe or postimages. So these images should all still be there.
Granted, I’m not sure how the thumbnails for these externally hosted images work and if they’re exclusively stored on lemm.ee
Catbox, notably, is also on the verge of shutting down.
Wtf tumblr
Images dont get saved locally on other instances if they host the content? Well that seems like a big flaw in “federation”…
I assume it’s an intentional trade-off by the devs to reduce the storage burden. If each instance is a complete mirror of all federated instances then hosting becomes that much more expensive.
It’s also an avenue for attacks.
Not really, it means I can’t send every lemmy instance csam.
no, I agree with the above user that it would be better to federate images too, for at least the following reasons:
- redundancy: see the OP
- privacy reasons: images loaded from other instances inform the other instance that one is viewing those images, do you trust all of them?
- censorship reasons: some lemmy instances are blocked in my workplace and I can never look at images from them when browsing at work; others may be blocked in entire countries
If I’m not mistaken, Mastodon already does federate images to other instances, so it isn’t unheard of.
I think they would need to find a way to address the problem first. Reportedly, these images have been a huge problem here on Lemmy. Several times now.
i heard its a problem, but never saw any. (im not saying its a lie)
Same, same. I can’t verify it and I probably don’t want to. But I had people assure to me it happened.
That’s credit towards the admins who acted quickly. That’s why you’ll see instances defederate from an instance if their admin is not active and doesn’t take action against illegal content in a reasonable time, because it can quickly get out of hand. Now if content isn’t proxied and is always mirrored, not only will the admin have to defederate from the problem instance, but they will have to go and clean up whatever was copied on their instance as well.
i hope you dont think thats the only reason for defederation.
