If you use the string "?OTRv" in conversation (eg; to have a conversation
about the OTR protocol, which i was just doing), the message never reaches
it's recipient and instead you get the message "Successfully refreshed
conversation with ______".

This makes some sort of sense if the conversation is not yet encrypted, but
if you are already speaking privately, then shouldn't that "?OTRv" string
already be wrapped in an encrypted packet? Is the OTR plugin actually
recursively looking for encrypted data within encrypted data?

	- Tyler

Forgot to CC the BTS on the first mail, sorry


libotr does this because not all user interfaces have an out-of-band
method to control starting/refreshing an OTR conversation.  So it looks
for in-band control messages as well.

But it's been noted on otr-dev that this should be made an option, so
those plugins which have something like the pidgin-otr OTR menu can just
use that, and inline messages will be ignored (optionally, ignored only if
you're already encrypted).

To be honest, I don't remember if we've already checked in that change
to cvs, but it's on the todo list one way or another.

Thanks for the note,

  - Ian