* testing (in particular, send "<" and "<a message that resembles HTML>"
in both directions between Empathy and Pidgin, and check that neither is
misinterpreted)
* review from someone who understands libotr
* Empathy: make sure OTR notifications are presented in a way that
peers cannot fake. Because Empathy doesn't support HTML messages yet,
distinctive formatting would be enough.
* string-only handling of fingerprints (emit strings to D-Bus,
parse hex -> binary when asked to trust a fingerprint from D-Bus)
Nice to have, but not blockers:
* TPAW UI for the enable-otr boolean parameter (for now, early adopters
can turn it on with mc-tool - but I think real UI *is* a blocker for
switching the default to be enabled)
* enable-opportunistic-otr boolean parameter, and UI for the same
(it will end up looking very similar to enable-otr, but with different
handling in im-channel*.c)
I've made most of the changes I wanted but haven't had time to test them yet. Use at own risk:
http:// cgit.freedeskto p.org/~ smcv/telepathy- gabble/ log/?h= untested- otr
Still to do:
* testing (in particular, send "<" and "<a message that resembles HTML>"
in both directions between Empathy and Pidgin, and check that neither is
misinterpreted)
* review from someone who understands libotr
* Empathy: make sure OTR notifications are presented in a way that
peers cannot fake. Because Empathy doesn't support HTML messages yet,
distinctive formatting would be enough.
* string-only handling of fingerprints (emit strings to D-Bus,
parse hex -> binary when asked to trust a fingerprint from D-Bus)
Nice to have, but not blockers:
* TPAW UI for the enable-otr boolean parameter (for now, early adopters
can turn it on with mc-tool - but I think real UI *is* a blocker for
switching the default to be enabled)
* Chan.I. Securable. {Encrypted, Verified} integration
* enable- opportunistic- otr boolean parameter, and UI for the same
(it will end up looking very similar to enable-otr, but with different
handling in im-channel*.c)