[OTR-dev] proposed API change

[Evan Schoenberg]

Similarly, error messages shouldn't have the OTR tag prepended... a 
client should be able to display OTR messages how it wants.  This goes 
hand in hand with needing error messages submitted to the client in a 
unique way rather than as received messages (as discussed in the 
Displaying OTR Errors (was: Re: Hmmm...) thread)

Possibilities, as an example:
- Prepend an OTR message (without the ugly question mark)
- Display it in a special window
- Tag encryption-related messages within the chat window in a special 
way (color, emblem, etc.)
- Make loud noises and make the computer blow up

-Evan

On Jan 26, 2005, at 1:48 PM, Adam Fritzler wrote:

>
> Another thing I was wondering: I think it'd be cleaner if the
> detection-of-OTR-ability was outside the scope of the OTR protocol.
> Which is to say, the library shouldn't add the whitespace tag to
> messages.  Some IM systems offer better ways of advertising
> capabilities.  I realize it's helpful for standardization if the 
> library
> attaches the tag, but at the same time, I think it'd be better done in
> the client code.
>
> asf.
>
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
>