But doesn’t the instance it is delicious (edit: FUCK AUTOCORRECT!) delivered to do that, and then if the image changes later, it wouldn’t update? And then I thought further that people from other instances likewise pull from the host instance, rather than the original source.
Except maybe Lemmy.world, if the image caching was added in a more recent update, which I thought was the case?
Anyway, I’m not saying that any of this happens, only that I thought it might.
Just hot link the image to a host that you have control of instead of uploading it to lemmy. Then you can change the image anytime you like and it won’t be affected by any caching on lemmy.
That is what I have noticed. When I use Catbox, the exact Catbox URL appears on every instance. But when I upload directly to my instance, federated posts use their own cached image instead of the one from my instance.
(Wouldn’t work anyway, due to Lemmy’s caching approach iirc)
It should as Lemmy will pull any image that is linked in the markdown.
But doesn’t the instance it is
delicious(edit: FUCK AUTOCORRECT!) delivered to do that, and then if the image changes later, it wouldn’t update? And then I thought further that people from other instances likewise pull from the host instance, rather than the original source.Except maybe Lemmy.world, if the image caching was added in a more recent update, which I thought was the case?
Anyway, I’m not saying that any of this happens, only that I thought it might.
Just hot link the image to a host that you have control of instead of uploading it to lemmy. Then you can change the image anytime you like and it won’t be affected by any caching on lemmy.
Oh, does image caching not apply to remotely hosted content? Well, then yeah, that sounds good.
That is what I have noticed. When I use Catbox, the exact Catbox URL appears on every instance. But when I upload directly to my instance, federated posts use their own cached image instead of the one from my instance.
Interesting… thank you for sharing!
It seems caching doesn’t do much, even while also being a big pain for instance admins - so much so that it is explicitly made voluntary.
Perhaps that is why PieFed is going so hard on integration with PixelFed and now Loops.