@[email protected] to TenForward: Where Every Vulcan Knows Your Name • 2 months agoWhy don't you join me in Ten Forward? There's something I'd like you to trylemmy.caimagemessage-square28fedilinkarrow-up195arrow-down11file-text
arrow-up194arrow-down1imageWhy don't you join me in Ten Forward? There's something I'd like you to trylemmy.ca@[email protected] to TenForward: Where Every Vulcan Knows Your Name • 2 months agomessage-square28fedilinkfile-text
minus-square@[email protected]linkfedilinkEnglish1•2 months agoOh, does image caching not apply to remotely hosted content? Well, then yeah, that sounds good.
minus-square@[email protected]linkfedilinkEnglish3•2 months agoThat 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.
minus-square@[email protected]linkfedilinkEnglish1•2 months agoInteresting… 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.
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.