<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 8/2/2013 3:27 AM, <a class="moz-txt-link-abbreviated" href="mailto:otr-dev-request@lists.cypherpunks.ca">otr-dev-request@lists.cypherpunks.ca</a> wrote:<br>
<blockquote
cite="mid:mailman.1.1375439275.12929.otr-dev@lists.cypherpunks.ca"
type="cite">
<pre wrap="">I'm pretty sure this has been brought up before; let's see if I
remember.
So you're saying that if the OTR plugin is installed, then even if
you're *not* speaking with an OTR-enabled buddy, Message Splitter is not
being invoked? I'm not sure what would be happening there, as if you're
not speaking OTR, pidgin-otr's process_sending_im is a no-op.</pre>
</blockquote>
<br>
That's correct!<br>
<br>
<blockquote
cite="mid:mailman.1.1375439275.12929.otr-dev@lists.cypherpunks.ca"
type="cite">
<pre wrap="">(I'll also note that if you *are* speaking OTR, then OTR itself does
message splitting.)</pre>
</blockquote>
<br>
I've seen no evidence of messages being split in OTR enabled
conversations, nor was I aware that OTR natively split messages
(shouldn't that be prominently featured?). <br>
<br>
New problem: OTR seems variable on whether or not it natively
splits/sends and you have no way to tell on the sending end if it is
sucessfully splitting/sending or not. At first I thought OTR was
not splitting only when Message Splitter was enabled, but now OTR is
not splitting when Message Splitter is disabled as well. <i>On a
failure, the entire copy and paste is simply ignored on the
receiving end as if it was never sent to begin with!</i> And no
notification or indication at all to either party.<br>
<br>
<blockquote
cite="mid:mailman.1.1375439275.12929.otr-dev@lists.cypherpunks.ca"
type="cite">
<pre wrap="">Can you be more explicit about the failure you're seeing, possibly with
a call trace? (And what version of pidgin-otr are you using?)
</pre>
</blockquote>
<br>
I don't think the conflict is necessarily in the pidgin-otr (which
is 4.0.0-1), because the Message Splitter will not work with, say,
the Offline Message Emulation plugin either. MS is being subsumed.<br>
<br>
</body>
</html>