goffi at goffi.org
Tue Feb 3 11:47:51 UTC 2015
Some clients do weird stuff like encoding XHTML-IM (which is probably
not a good idea at all). Also a XEP should give some advices on what to
allow, saying that history should be disabled by default, this kind of
Also there is an OTR space-based discovery system which should be
useless in XMPP (except if you use OTR with gateway/legacy networks).
Maybe a XEP should explain what to do, if we need to announce there
somewhere with XMPP discovery, etc.
On 03/02/2015 10:37, Florian Schmaus wrote:
> Isn't "documenting the current OTR usage in XMPP" simply
> <message …>
> … put OTR stuff here …
> where "OTR stuff" is defined at
> https://otr.cypherpunks.ca/Protocol-v2-3.1.0.html (I think most
> implementations use OTR v2) and
> So OTR is IM protocol-agnostic. You can see how OTR tries to negotiate
> using whitespaces at the end of String within the </body> element at
> I'm also not sure if, not only because it's IM protocol-agnostic, OTR
> would be a good fit for IoT. Some research in this direction would sure
> be interesting.
> - Florian
More information about the Standards