On Mon, Jul 15, 2024 at 9:52 PM Tim Henkes <[email protected]> wrote: > I've been brainstorming a mechanism for offline history transfer (i.e. > one client fetches the offline message history from another client). For > that, an encrypted direct client-to-client XML channel would be neat.
I’ve been planning to implement his for a very long time and do in fact have the funding to do so I’m just trying to find the time. I was planning on using "XEP-0247: Jingle XML Streams". I don’t think the fact that the XEP is Deferred has any significant meaning. Many of the A/V call related XEPs were deferred as well before we started using them again. Whether or not the XEP needs modification we will see while implementing it but from where I’m standing now I don’t see anything wrong with it. My plan was to first and foremost use WebRTC Datachannels as transports which neatly solves the encryption issue. (This is also the primary reason I've implemented file transfer over datachannels to get familiar with the technology). In a later iteration one could potentially implement jingle-xtls to also get Socks5 and IBB working but Datachannels should provide enough to get started (and cover 95% of use cases) cheers Daniel _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
