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.
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.
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:
If I’m not mistaken, Mastodon already does federate images to other instances, so it isn’t unheard of.
Mastodon purges them after a while though.
Depending on how the admin has pict-rs (the “subsystem” it uses for media) configured, post images can create local copies /thumbnails for image posts. Some instances opt to do that, some don’t.
Other images like ones posted a comments, user/community avatars/banners aren’t stored anywhere except their home instance.
But yeah, even the limited caching has proven problematic if questionable/illegal content gets posted.