Maybe it’s something in UI, but many times I watch pictures (not even videos, they are their own can of worms), and want to save them, it shows me that I’m downloading them again although they are cached in whatever app I see them from.
Like this link with a happy dog: https://i.pinimg.com/736x/71/1e/52/711e52f1d6c7ead78f4380214f68c259.jpg
I see it in high rez in my browser, I can zoom in, and I can’t tell any difference from a copy that I can download, but it’s still, well, another download if I want to save it, and not a move from cache to my download folder, another request to the server, another waste of traffic.
Is there some rule of sandboxing for everything you load that I don’t know about? In cases like our fediverse, I wouldn’t like to cause double load when I already have the picture I want. Can I cut it down with some plugin in mobile Firefox?
I feel like I’m missing something big time.
Maybe I’m not understanding the question but typically a CDN will have HTTP headers to signal to the browser to cache the asset (image). I can’t imagine Pinterest isn’t using a CDN (with said headers), so if it’s re-fetched over the network that sounds like a browser problem more than a developer one.
That’s right, I was referring to the browser/client developer. The browser cache is treated as ephemeral storage so it’s not a safe assumption that a previously downloaded file is still there.