I love Mastodon and all but isn’t it about time your mastodon client pulled in missing images, etc., from the source server? I mean, it’s still the web, y’know? We’re what, seven years in? It’s a bit embarrassing at this point.
@aral remote media caches expire very frequently and yeah it's kind of embarrassing, but,
a better scenario is one where your home server can fetch missing media from the source server for the client. keeps traffic routed through the home server where it belongs, preserving privacy and caching it for everyone on your instance.
it's the web but also it's really not? AP and existing AP implementations have as much in common with email and Usenet as they do with conventional web scenarios. and if we're giving up the home server's role in caching and access control, we should be trading it for something *better* than the web at scaling, like torrents.
@exchgr@MonaApp Just tried it out but still seeing broken media on older posts. Also the same for profile pics etc. that have been updated but not pulled in on my server. As far as I can see, the behaviour matches the web client.
What I’d love to see is if I’m viewing something and it’s not available, it’s fetched automatically from the original server.
@aral as far as i know, @MonaApp, which is so stable and good that it’s mind-boggling that it’s still in beta, can do this. it can also load an entire profile and its latest posts from the source server