I wonder if there is room here for the proxy to cache the data that is transmitted. That way, the total amount of data that is transferred between domains (when more than one person is to receive the data) could be drastically reduced. That is useful in certain scenarios.
- Guus Op zo 22 jun 2025 10:17 schreef Schimon Jehudah <[email protected]>: > On Fri, 20 Jun 2025 18:06:55 +0100 > Matthew Wild <[email protected]> wrote: > > > On Fri, 20 Jun 2025 at 16:58, Goffi <[email protected]> wrote: > > > When you get a file though, the HTTP Upload service of your > > > recipient gets your IP. > > > The other issue is when you receive a file/image from some random > > > domain, in this case the simplest option is to use a proxy which > > > will get the file for you. > > > > > > A specification to indicate to XMPP clients where to find a proxy > > > would be nice, it has already been talked about in the past. > > > > The specification already exists - > > https://xmpp.org/extensions/xep-0215.html > > > > Currently the XEP is well known for being the way to discover > > STUN/TURN services offered by your server. It's actually generic > > though, and is the perfect place to advertise a proxy service (with > > associated credentials). > > > > I plan to include such a proxy in Snikket at some point. In the > > meantime, if any client devs are interested in working on this then > > I'm happy to set up a test Prosody instance that advertises such a > > proxy. > > > > Could XEP-0215 proxify data which was sent via HTTP file upload? > > Best, > Schimon > _______________________________________________ > Standards mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
