Conversation

Notices

1. Embed this notice
   sanae :vbike: :vbus: (SF) (sanae@carfree.city)'s status on Tuesday, 18-Jul-2023 00:19:53 JST sanae :vbike: :vbus: (SF)

   From a post on private -
   There's a pretty common script people set up to remove cached images from other instances that are more than a week old. This stops storage costs from just continuously increasing. However, it seems to break looking at old images, which then don't load. What I think should happen is that if you open a post that's old it re-fetches the image. Having every instance have to store a copy of everything forever seems bad. Is there an existing way around this?

   #fediAdmin

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Tuesday, 18-Jul-2023 00:19:52 JST Annika Backstrom

     in reply to

     @sanae I'm 99% sure this is how Mastodon works: you get all the images, stale ones are deleted if you run the cron, they're re-fetched if somebody happens to look at the old post. (I can bring up ancient off-server posts and they do load after a brief delay.)

     People have floated the idea of several servers sharing a CDN, I don't know if anything has come of the idea.

   • Embed this notice
     Annika Backstrom (annika@xoxo.zone)'s status on Tuesday, 18-Jul-2023 00:31:46 JST Annika Backstrom

     in reply to

     @sanae It's the worst when you view the Media tab of somebody's profile. You quickly hit 429 rate limiting and the images stop loading.

   • Embed this notice
     sanae :vbike: :vbus: (SF) (sanae@carfree.city)'s status on Tuesday, 18-Jul-2023 00:31:47 JST sanae :vbike: :vbus: (SF)

     in reply to

     • Annika Backstrom

     @annika hmm, the re-fetching part seems buggy