This is about proxying external images, URL rewrite won’t work unless the image is also downloaded and hosted by the instance (which seems even worse for many reasons).
Or am I missing something here?
I’ve done exactly what I described in my comment for the last 8 months: it’s been a UI feature of Tesseract since last October.
It proxies any image or direct video from any source you haven’t blacklisted. If you have the proxy option enabled in your settings, image URLs are re-written to go through the proxy. If not, then it uses the regular URL directly.
And anywhere it renders an image (markdown, posts, avatars/icons, banners, etc), the image source is set via imageProxyURL(url). There’s extra optional params for size and format if the image source is served by pict-rs.
This is about proxying external images, URL rewrite won’t work unless the image is also downloaded and hosted by the instance (which seems even worse for many reasons).
Or am I missing something here?
You’re missing a lot.
I’ve done exactly what I described in my comment for the last 8 months: it’s been a UI feature of Tesseract since last October.
It proxies any image or direct video from any source you haven’t blacklisted. If you have the proxy option enabled in your settings, image URLs are re-written to go through the proxy. If not, then it uses the regular URL directly.
Oh interesting I will have to look how tessaract does it
And anywhere it renders an image (markdown, posts, avatars/icons, banners, etc), the image source is set via
imageProxyURL(url). There’s extra optional params for size and format if the image source is served by pict-rs.Lemmy will rewrite the image URLs when saving a post.
But instead the URL should be rewritten when loading the post. That way the original URL wouldn’t get lost and it would also work for old posts.