[otr-users] Pidgin plugin sends and parses HTML

[Jonathan Schleifer]

Rüdiger Kuhlmann <l-otr.0705+23jv-l at ruediger-kuhlmann.de> wrote:

> The question is how to proceed without hampering the broken
> interoperability of the OTR-wonnabe-protocol further. Maybe the best
> idea would be to increase the version number and in the new version
> make the protocol provide means to specify the type of data
> (plain/text, a well-defined subset of HTML, whatever) and means to
> determine the receiver's preferences. Anyone who doesn't agree?

Yes, me.
XMPP offers XHTML IM. You can just put the HTML code there and put
plain-text in the message body. This way, Pidgin can use it damned HTML
(seems it can't even work without it!) and those who don't understand
XHTML IM get the plain message, like wanted.
For ICQ, HTML should just NEVER be used as it doesn't support it, even
in ICQ6.
OTR shouldn't change anything about the data it encrypts. It should
just encrypt it, nothing more. That way, you can encrypt HTML messages
and put them in the *RIGHT* place, which is *NOT* the XMPP message body
and you can encrypt plain text and put it in the XMPP message body.

-- 
Jonathan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.cypherpunks.ca/pipermail/otr-users/attachments/20080512/60d804c6/attachment.pgp>