[Pidgin Plugins] #471: autodetect IRC server message truncation

[Pidgin Plugins]

#471: autodetect IRC server message truncation
------------------------------+---------------------------------------------
  Reporter:  tmetro           |       Owner:            
      Type:  FeatureRequest   |      Status:  closed    
 Milestone:                   |   Component:  PluginPack
   Version:  PluginPack2.2.0  |    Severity:  major     
Resolution:  wontfix          |    Keywords:            
   Pending:  0                |  
------------------------------+---------------------------------------------
Comment (by tmetro):

 Replying to [comment:1 jbailey]:
 > The IRC specification mandates that no IRC message may be longer
 > than 512 characters.  ...

 Ah, thanks for the detailed explanation.


 > This is a well-known IRC limit and has been in place for as long as the
 IRC
 > protocol has existed (over 15 years).  I don't see a reason for us to
 hack around
 > this bug in IRCHelper...

 Agreed. That wouldn't make sense.


 > ...nor do I see a reason to hack around it in libpurple proper.
 Libpurple doesn't
 > autosplit for any protocol, and implementing it for IRC would set a bad
 precedent.

 Autosplit was only one suggested solution. The other is to limit the
 number of characters accepted into the input box. Either approach would
 work for me, though autosplit is clearly more user-friendly (why make the
 user manually do that which the computer could do for them).

 To do nothing and lead the user to believe that their messages in excess
 of the limit are being successfully sent is clearly a bug. I'll file a
 report against Pidgin.

-- 
Ticket URL: <http://plugins.guifications.org/trac/ticket/471#comment:2>
Pidgin Plugins <http://pidgin.guifications.org/>
Plugins for the Instant Messaging client Pidgin and its backend library libpurple