On 8/22/11 3:03 PM, Sven Moritz Hallberg wrote: > On Thu, 18 Aug 2011 22:12:36 +0200, Jonathan Schleifer <[email protected]> > wrote: >> Actually, exactly the opposite is the case, if you look at the >> commit. There was a lot of code, but libotr just wants to be that >> three-line drop in, so you lose a lot of flexibility which you need to >> properly support XMPP with all it's features. > > out of curiosity, what are examples of those XMPP features?
XMPP is used for many things other than sending human-readable IMs. One prominent example is Jingle, an extension for managing voice, video, and other multimedia sessions that is used in the Google Talk service and several open-source XMPP clients. Such extensions are not forced into the message body, instead they are XML-structured payloads that are often placed inside the XMPP <iq/> element rather than the <message/> element. You can see examples here: http://xmpp.org/extensions/xep-0167.html#example-1 http://xmpp.org/extensions/xep-0234.html#example-1 If you're exchanging things like IP addresses and file names, you really might want to encrypt that end-to-end so snoops in the middle can't learn things that are none of their business. Ideally, a future version of OTR would have a mode that enables people to send this kind of information, instead of just XML character data like the "foo" in <message><body>foo</body></message>. Peter -- Peter Saint-Andre https://stpeter.im/ _______________________________________________ OTR-dev mailing list [email protected] http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
