<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Jun 9, 2007, at 10:45 AM, Rüdiger Kuhlmann wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">So can we please please make the library stop resending stuff and leave it</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">up to the application?</FONT></P></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>As an application implementor, I most certainly don't want to have to deal with resending. The current, automatic handling seems very appropriate to me.</DIV><BR><BLOCKQUOTE type="cite"> <BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">* It is impossible to signal back to the library that an injected</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>message could not be sent due to size constraints. Thus, the library</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN>does not provide for outgoing fragmentation at all!</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">As Paul said, RSN.</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Well, I'm not using cvs - I can't expect people to have dev versions</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">installed for dlopen to grab.</FONT></P></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>So in a perfect world, what would you hope to happen in response to your comment here? Ian indicated that this was in progress.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">If otrl_message_receiving</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">gets an OTR Query message, it will start key negotiation.<SPAN class="Apple-converted-space"> </SPAN>If it gets a</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">plaintext message with the whitespace tag, and your policy is set to</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">reply to whitespace tags, it'll start key negotiation.</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">I managed Kopete to display me an HTML message complaining about a</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">plain text that visibly contained an OTR offer tag.</FONT></P></BLOCKQUOTE><DIV>Could you please write the precise steps to reproduce to cause that error to occur? In about 2 years of using OTR I've never seen this.</DIV><BR><BLOCKQUOTE type="cite"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">--[Evan Schoenberg]--<<A href="mailto:evan.s@dreskin.net">evan.s@dreskin.net</A>></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">On Jun 7, 2007, at 6:39 PM, Ian Goldberg wrote:</FONT></P> <BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">I agree that the otrl_message_* routines blur the line between library</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">stuff and app stuff.<SPAN class="Apple-converted-space"> </SPAN>That's where the English HTML messages all live,</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">for example.<SPAN class="Apple-converted-space"> </SPAN>The reason we moved them from gaim-otr to libotr is that</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">we thought they may be useful to other apps.<SPAN class="Apple-converted-space"> </SPAN>But I totally agree that</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 20.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">some refactoring may be useful there.</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Optimally, these messages would be available in the library but not <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">in their current form.<SPAN class="Apple-converted-space"> </SPAN>It'd be awesome if the library passed back <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">defined error codes which could then, at the application's <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">discretion, either be used to generate its own messages or passed to <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">something like</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 10.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">const char *otr_get_error(otr_error errno)</FONT></P> </BLOCKQUOTE><P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">That would be a start.</FONT></P></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>What more would be required to fit the needs you've described?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">I think that reading all list message before answering would have saved you</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">the time to write this email... My overall complaint is that libotr is so</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">Gaim-specific that it is not really a general purpose library.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>It's not only difficult but often counterproductive to write a library which is generalized far beyond its current use. I should imagine that patches which make the library more general without breaking current functionality would be happily reviewed.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-Evan</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>