[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):

 Replying to [comment:18 datallah]:
 > Crying about it doesn't improve the situation.

 First of all, there is no need to accuse someone of doing something
 they're quite obviously not. It was a blatant exaggeration. You know it
 and you're certainly not going to get away with it. Seems you were just
 looking for an excuse to attack me just because I have the guts to
 complain after 6 months and many updates only to find out every single
 time that there's no notification this critical bug still exists. If you
 do in fact think I am 'crying' then I can happily point you to forums and
 posts where there is real 'crying'...[[BR]]

 Second, you are wrong. Complaining about it will get attention and
 hopefully the attention it deserves so something will finally be done
 about it, ie: everyone notified and informed of how to get their QQ
 operational again.


 Replying to [comment:18 datallah]:
 > Your attitude makes me less inclined to want to spend my limited time to
 help you[[BR]]


 How hypocritical. I and thousands of others have patiently waited 6 months
 and multiple betas and finals to be released and still the discourtesy
 continues. Just because you are a power user, in the know and are aware of
 how to fix it doesn't mean you should ignore your userbase and not treat
 them with the respect they deserve - free/open source or not. That, my
 friend, is attitude. A lousy attitude that gets you nowhere, not to
 mention one that loses you the respect of others. I also cannot understand
 how you can happily sit there and ignore that this ticket is going to
 remain unread by the minute percentage of QQ protocol users that happen to
 stumble upon these tickets - unless of course one of you decides to do the
 right thing and reopen it. I cannot understand that nor why you seem to be
 oblivious to and unconcerned with the fact, now mentioning it for the
 third (or is it the fourth) time, that thousands of mainstream Pidgin
 users are being led astray and shown zero consideration for by the fact
 that there has been, and still is, no warning whatsoever of the existence
 of this bug in the updates/changelogs. Nor is there any solution or link
 to this thread for them. How sad. And what's even worse is you sit there
 and act like nothing is wrong. It's pathetic.[[BR]]


 I only ask on behalf of myself and the many other friends I have (also
 living in Asia and who want to continue using Pidgin as an alternative to
 that malware-infested Chinese crap that the original QQ client is), to be
 able to be given the common courtesy (again, something I have repeated for
 the third time and something that has flown way above your head) and be
 told that;[[BR]]
 1. '''the problem has not been fixed'''[[BR]]
 2. '''they will not be able to use the QQ protocol should they install any
 standard so-called 'stable' release''', which, in my and many others'
 opinion, shouldn't be finals at all since...[[BR]]
 3. '''they render one of its supported protocols useless''' - again,
 another thing I've had to repeat and that has gone in one ear and straight
 out the other. And finally,[[BR]]
 4. '''there is a solution''' lying hidden in a closed ticket on
 http://developer.pidgin.im [[BR]]

 If you think that what I'm asking is unreasonable then I'll be more than
 happy to put it into a poll on a website forum that I've been moderating
 for the last 4 1/2 years. There are currently 17,000+ (non-geek) members.
 Let's see what they say, shall we? I dare you to take me up on the offer.
 No doubt I will have called your bluff and some form of attack or flaming
 could occur as a result. Maybe...maybe not...but I've seen it all, and
 what I can tell you from my experience moderating is that every single
 minute of every day there are people who come into a help thread with the
 mindset that everyone is as good with computers as they are. They
 subconsciously think that everyone can run commandline scripts at will on
 their *nix boxes and find and fix problems in a jiffy instead of the hours
 of googling that normal users take to get the same thing done. It's almost
 as bad as the other end of the scale when Mac users pop in with their 2c
 worth and say, ''"Get a Mac. They just work"''.[[BR]]
 It's no surprise in the least to see your response - a response that is so
 naive and with a perspective totally alienated from your average computer
 user that it doesn't even begin to take into account the fact that more
 than 90% of people run Windows while the remainder - usually 5% or less -
 are running Linux/Unix or Mac. Well, matey, wake up. What you have
 conveniently left out of your poor excuse for a rebuttle is that most
 people running Pidgin are Windows users who, and it's obvious you need to
 be reminded of these points;[[BR]]

 a) have very limited computer skills and can pretty much point and click
 only[[BR]]

 b) have limited time and as a consequence are not prepared nor willing to
 spend hours googling for solutions that they shouldn't have to be googling
 for (not that they know how to properly define search terms in the first
 place)[[BR]]

 And need I remind you, '''again''' *yawn*, that all this would be
 unnecessary if a little simple courtesy was extended to the demographic
 that makes up more than 90% of your userbase, ie: notification of the bug
 and the temporary fix.[[BR]]

 It's plain to see that you are of the *nix breed that is, in all
 likelihood, proficient with running most of your apps GUI-less via
 commandline switches over SSH from a remote server...and act like everyone
 else is as skilled as you are and has the knowledge, perseverance and time
 on their hands to search the net for the answers - in this case half-
 hidden answers - to their problems. The fact that they have to do that
 when a couple of lines inserted into the changelogs could prevent it along
 with preventing the hours of wasted time and frustration for these average
 users is, again, beyond you and it's very clear that you couldn't care
 less about it. You or anyone else hasn't mentioned it and I'm the only one
 that has...and I get crap for it. It's also apparent that you don't use QQ
 on Pidgin. If you do then we can all see that you most definitely couldn't
 care less about the hassle and frustration that thousands of other, less
 skilled users than yourself, are experiencing. Hassle and frustration
 caused by the lack of info regarding this bug.[[BR]]

 As I have already mentioned, you are most likely intelligent and skilled
 (that's not a pisstake, BTW) and good for you mate, but just because you
 can do it doesn't mean that most others can! Really, sometimes you people
 need a good dose of reality. And this all stems from a simple lack of
 netiquette - netiquette that has unfortunately been completely absent in
 this case. I'm sorry to say it but it is true. One could argue that I was
 somewhat rude and lacked said etiquette and yes, I admit it...but I had
 just cause due to 6 months of being pissed around...installing,
 reinstalling '''and educating others on how to do it'''. Again, something
 you don't have to deal with with Pidgin because you are here every day and
 no doubt have the skill to implement whatever patch/script that may be
 available to you to fix whatever problems you have. Sorry to remind you
 again, but as I said before: everybody is not as fortunate as you are. And
 whether they have to do a patch or reinstall with GTK+ 2.12.1 is
 irrelevant. The vast majority don't even know that a solution exists. If
 you can't or don't fix it immediately then that's fine but at least have
 the common decency to inform your userbase that there is a temporary
 solution. '''THAT IS MY POINT'''[[BR]]

 In the last year alone I have introduced Pidgin to more than 30 others and
 since this bug has been plaguing the so-called stable releases for the
 last 6 months I have helped more than 10 of them get around this problem
 and keep their QQ running. Whose responsibility is this? Mine? And just
 because I vocalize my disappointment after 6 months of silence doesn't
 entitle you to look down upon me, spout off on tangents and miss my points
 entirely - something I've seen a million times before on help forums. The
 fact that you didn't rebut any of my main points just shows you that
 you're biased and have no leg to stand on with your arguments. Grow up,
 please. And I have been aware of the solution since bokamba posted it,
 thank you very much. You should know that I am permanently added to the cc
 list but by going OT and pretending to be helpful by posting a summary for
 me like I'm a beginner can only be considered condescending and only
 served to make yourself look...well...condescending.[[BR]]

 And, if you do decide to grow up and reply without attacking, ridiculing
 or badmouthing me in one form or another, then perhaps you could do
 something constructive to address the issues at hand (since you have
 elevated privs on this forum). You could start by addressing the reasons
 why I am complaining (see points 1-4 above)[[BR]]


 Replying to [comment:18 bokamba]:
 > Med doesn't represent me.

 I can see that. However, someone has to represent the thousands of n00bs
 that are left uninformed and their QQ rendered useless don;t you think? Or
 shall we just continue to leave them in the dark? So far I am the only one
 to suggest something useful as far as this goes and I am perfectly
 justified to suggest that the devs either drop QQ support (for the reason
 I have stated numerous times already) or inform '''everyone''' what to do
 in order to keep it running.

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