[OTR-dev] Displaying OTR errors (was Re: Hmmm.)

[Evan Schoenberg]

Sorry, I was not sufficiently specific.  I didn't mean that all errors 
are sent via inject_message, just that there are some which are and 
should not be.

9:30:30 <my buddy's name>: ?OTR Error: You sent unencrypted data to <my 
buddy's name>, who was expecting encrypted messages from you.

10:23:21 <my buddy's name>: ?OTR Error: You sent encrypted data to <my 
buddy's name>, who wasn't expecting it.

10:45:21 <my buddy's name>: The encrypted message received from  <my 
buddy's name> is unreadable, as you are not currently communicating 
privately.

10:46:10 <my buddy's name>: The following message received from  <my 
buddy's name> was not encrypted: [ok, I canceled encryption

Those are four error conditions which are displayed as incoming 
messages.  The first and second are definitely errors, but they are 
presented as simple text received from the other person.  The third I 
believe should be presented as an error, not a message, as it does not 
contain message text.  The fourth does make sense presenting as a 
message, carrying its OTR descriptive prefix ("The following message 
received.... was not encrypted:")

Is that clearer?

Thanks,
Evan

On Jan 26, 2005, at 9:29 AM, Ian Goldberg wrote:

> Actually, it doesn't.  It sends error messages to *the other person*
> using inject_message.  It sends error messages to you with the notify
> callback (if a window should be popped up) or just by setting *messagep
> (if it should be displayed inline).  [It used to be that all messages
> were displayed ouot-of-band in a popup, but people got annoyed at that
> really fast.]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 2010 bytes
Desc: not available
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20050126/a1062697/attachment.bin>