[Pidgin] #2065: 2 long a message auto sent in multiple IMs

[Pidgin]

#2065: 2 long a message auto sent in multiple IMs
---------------------------+------------------------------------------------
  Reporter:  bradwjensen   |       Owner:       
      Type:  enhancement   |      Status:  new  
  Priority:  minor         |   Milestone:       
 Component:  pidgin (gtk)  |     Version:  2.0.2
Resolution:                |    Keywords:       
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by chemistrydioxide):

 '''1. Resuming sent messages:''' I suppose you don't know that it's
 possible to resume previously sent messages by hitting CTRL+UP or
 CTRL+DOWN. As far as I know, this feature isn't documented anywhere. It
 took me some time to discover it.

 '''2. Behavior in case of send/delievery errors:''' I think current
 send/delievery error handling breaks the
 [http://developer.pidgin.im/wiki/DesignGuidelines#Uniformity uniformity of
 different protocols]. Delievery errors are treated differently, depending
 on protocol and error. Sometimes, the undelievered message is shown in the
 conversation window (XMPP/Jabber), sometimes it's not (OSCAR). Sometimes,
 the error messsage appears in the conversation window (OSCAR, IRC),
 sometimes it's a dialog box (XMPP/Jabber). And those error messages in the
 conversation window even look different: On IRC they are black, on OSCAR
 they are red.

 I think Pidgin's behavior in case of message delievery failure should
 always be protocol-independent.

 There are several options to handle message delievery failures:

 Option 1: Handle them protocol-dependent: That's what Pidgin is doing
 now.[[BR]]
 Option 2: Throw the message away and show an error message: Doesn't make
 sense either because some users don't know the CTRL+UP/DOWN hotkeys.[[BR]]
 Option 3: Try to auto-resend the message in a modified way, e. g. as
 several messages (your idea, bradwjensen): I think this is a workaround
 that causes other problems:[[BR]]
    - It will only work if we know the character limit that we have to
 follow.[[BR]]
    - The user will be charged higher costs if he has to pay for every
 single message (that's the case with SMS).[[BR]]
    - Problems that do not result from the message itself (e. g. S2S
 connect failure on XMPP) are not resolved.[[BR]]
    - Sending several messages at once might cause trouble with server-side
 spam protection (e. g. g-lines on IRC).[[BR]]
 Option 4: Show the message in the conversation window and show an error
 message (either as an extra dialog or in the conversation window).[[BR]]
 Option 5: Write the message back to the input field (attach it to the
 beginning of the next message if the user has been typing in the
 meantime), remove it from the main part of the conversation window (if
 necessary) and show an error message (either as an extra dialog or in the
 conversation window).

 I think option 5 with errors in dialogs is the best choice (although
 option 4 with errors in the conversation window would be nice as well).
 Option 3 doesn't make much sense because of the problems I mentioned.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2065#comment:2>
Pidgin <http://pidgin.im>
Pidgin