On Thu, 26 Jun 2025, 20:33 Goffi, <goffi@goffi.org> wrote:
Hi Matthew,
Le jeudi 26 juin 2025, 19:35:55 heure d’été d’Europe centrale Matthew Wild a écrit :
[SNIP] So despite my initial enthusiasm for off-the-shelf proxy support, it seems that it might actually be worth considering other options. For example, we could do something similar to Matrix, where you make a normal HTTPS request to your own server, with the remote URL embedded in the path. Your server will then transparently fetch the remote resource and return it. Something like:
'GET https://recipient.example/fetch/share.sender.example/ d8c16ada-52b3-11f0-9de6-1b9c14dcd995/cat.jpg'
This has a number of advantages: [SNIP]
That's actually what I had in mind when thinking about a proxy for this use- case. On my wishlist, I would love it to have a way to get a preview of images/video and/or a resized media to some common resolutions. The benefit would be that :
- we could cache and share preview/resized image/video for huge files at the proxy level.
- devices with restricted resources (connection/CPU), typically mobile devices, could get a small file instead of having to request a huge one then resize on-device.
Of course, and in particular for videos, it could be resource intensive for the server. But at least for images, it would be a useful feature.
For various reasons, such as server load and E2EE, I think such previews need to be provided by the sender. Regards, Matthew