This is true for most link aggregators that attempt to render external content. Proxying images and videos would dramatically increase costs.
If you care that much about anonymity, use a VPN/Tor and a browser with advanced fingerprinting resistance — tor browser, mullvad browser, or firefox with resist fingerprinting = true.
That makes sense. But I guess there’s these questions: at what resolution? For how long? Maybe the status quo is such because it’s simpler code. The project is still relatively young. I wonder where/how we can discuss these things?
It still adds up fast especially if you run an instance that stores to s3 with a cdn. My mastodon server racked up 1k in cdn usage one month before I switched to local storage no cdn.
This is true for most link aggregators that attempt to render external content. Proxying images and videos would dramatically increase costs.
If you care that much about anonymity, use a VPN/Tor and a browser with advanced fingerprinting resistance — tor browser, mullvad browser, or firefox with resist fingerprinting = true.
They normal don’t render then instantly, though. Caching at least a lower res version should barely be noticable compared to actual image posts.
That makes sense. But I guess there’s these questions: at what resolution? For how long? Maybe the status quo is such because it’s simpler code. The project is still relatively young. I wonder where/how we can discuss these things?
Probably the same as for other images? I mean, it’s not as if remote images are vastly different from uploaded ones ;)
It still adds up fast especially if you run an instance that stores to s3 with a cdn. My mastodon server racked up 1k in cdn usage one month before I switched to local storage no cdn.
At the very least setting referer policy headers and such would be a good addition.
That’s great except those browsers often don’t work.