[Pidgin] #5077: QQ message text and sender(Pidgin)'s nick all changed to: "(NULL)"

[Pidgin]

#5077: QQ message text and sender(Pidgin)'s nick all changed to: "(NULL)"
------------------------------+---------------------------------------------
 Reporter:  Med               |        Owner:  seanegan       
     Type:  defect            |       Status:  closed         
Milestone:  2.4.1             |    Component:  winpidgin (gtk)
  Version:  2.4.0             |   Resolution:  fixed          
 Keywords:  NULL nick change  |  
------------------------------+---------------------------------------------

Comment(by Med):

 How about the devs and people working on it have the courtesy to;[[BR]]

 a) inform all users that it will render their QQ useless upon every
 install/update. They could at least try...but no, instead they act in an
 unprofessional manner and don't inform a soul. In response to your call to
 read the full ticket, I have read the full ticket but, as I have said
 already, these 'fixes' are unknown to 99% of the people who use the
 protocol[[BR]]
 b) mark this ticket as unresolved. It is not unresolved! In fact it is
 made even harder to find by those people experiencing problems since this
 ticket is incorrectly marked

 As far as I'm concerned many people have been polite and patient enough -
 including me and I am the one who reported this bug. Like I said, if it
 isn't going to be fixed in the near future either drop the protocol
 (because it is a critical bug and renders QQ completely useless) or have
 the decency not to piss off thousands of users - most of who will not even
 come to these forums to search for a solution, let alone be able to
 implement commands in Python to fix it. It's a simple matter that requires
 30 seconds of thought and action. seanegan needs to add "If you use the QQ
 protocol please either;[[BR]]
 1. see the following link (include link to this ticket) on how to keep
 your QQ running after updating Pidgin, or[[BR]]
 2. reinstall GTK+ 2.12.1 Rev B (which is available here {link}) after you
 update"[[BR]]

 ...into the changelog popup. Now how hard can it be to act professionally,
 do the right thing and inform everyone? Not hard at all. I rest my case

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