[Pidgin] #15090: freenode's new +q numeric (728) is unrecognized

Pidgin trac at pidgin.im
Tue May 1 09:53:39 EDT 2012

#15090: freenode's new +q numeric (728) is unrecognized
 Reporter:  marienz  |        Owner:  elb
     Type:  defect   |       Status:  new
Milestone:           |    Component:  IRC
  Version:  2.10.3   |   Resolution:     
 Keywords:           |  

Comment(by elb):

 The problem is that, for this, as in all the other numerics that freenode
 just ''randomly made up'', it's often hard to tell exactly where the
 message belongs.  Even irssi prints this message to the server messages
 window, and doesn't know to put it in the channel.  This is one price of
 stapling random crap onto the protocol with no documentation, rhyme, or
 reason.  We have special cased several freenode numerics over the years,
 but they change -- +q alone has been handled at least three or four
 different ways since I have been using Freenode.  (Though this might be
 its first wholly separate numeric, rather than changing mode letter or ban
 pattern, I'm not sure.)

 As you may or may not know, Pidgin does not have a server messages window,
 as it does not really fit anywhere in the Pidgin UI.  This causes a
 problem for us for trapping arbitrary messages to someplace the user can
 see them.  The debug window is an unfortunate and poor catch-all, there's
 no question about that.

 Pidgin is not, and likely will never be, a "power user" IRC client.  Part
 of this is simply because its interface is geared toward IM-style
 messaging, not IRC-style messaging.  We are comfortable with this
 limitation, although why try to mitigate its particularly wild excesses
 where possible.

 The "right" solution to this, insomuch as there is a right solution, is
 probably to add an explicit 728 handler.  We do not like to add handlers
 for made-up numerics, for two primary reasons: 1) it can be the case, and
 ''has been'' the case in the past, that different networks use the same
 numeric for different purposes, with no good way to differentiate; and 2)
 networks like to change their made-up numerics more often than their ops
 change underwear.  However, we have certainly conceded this in the past,
 when a network mistakenly chooses to make up a numeric for a particularly
 important feature.  I will consider it for +q.  (As you mention, we have
 added explicit handlers for made-up critical info status numerics for
 Freenode in the past.)

 As to whether it is in fact the client or the network that is broken, that
 is certainly a matter of perspective.

Ticket URL: <http://developer.pidgin.im/ticket/15090#comment:1>
Pidgin <http://pidgin.im>

More information about the Tracker mailing list