[Pidgin] #12932: Pidgin - what's good and what's not!

[Pidgin]

#12932: Pidgin - what's good and what's not!
-------------------------+--------------------------------------------------
 Reporter:  Sebastian78  |        Owner:  rekkanoryo  
     Type:  defect       |       Status:  new         
Milestone:               |    Component:  unclassified
  Version:  2.7.5        |   Resolution:              
 Keywords:               |  
-------------------------+--------------------------------------------------

Comment(by deryni):

 Taking your suggestions out of order.

 B) The development community does not like a forum. We never have. There
 used to be one, it was ignored by the developers and populated almost
 solely by people who didn't know what they were talking about so
 absolutely *horrible* answers and information were passed around as fact.
 This continues even now without the forum as can be seen by this recent
 MSN issue and the number of people willingly following instructions to
 download random certificates and force-feed them to pidgin. The solution
 offered in comment 39 of the cert ticket is the complete solution (though
 it doesn't include the paths for Windows). The user in comment 43 (I
 think) took it upon himself to update his previously incorrect blog post
 to include the new corrected information and for that we thank him.

 There's nothing about that which a forum would have solved.

 C) Yes, we should be better at communicating this sort of thing to people.
 We aren't. But neither are most of the people in the "community" judging
 by the fact that the wrong information is still wildly circulating and
 people are still unable to find the correct answers out there.

 Seriously, watch the tweets for #pidgin and you'll still see people having
 the problem, not finding a solution immediately, being given and giving
 the wrong information, etc. This isn't to say that there aren't people out
 there giving the right information, there are. Just less of them the the
 people giving the wrong information.

 A) What specifically about the pidgin UI is not "modern" enough for you?
 What specifically would you change? People are free to make their own GTK+
 themes, pidgin status icon themes, pidgin smiley themes, etc. Notably GTK+
 themes apply to more than just pidgin so you aren't going to find a huge
 number of them searching specifically for pidgin.

 I should also point out that just about each time some large network
 failure occurs someone chimes in with a list of suggestions much like this
 and then just as quickly disappears without actually attempting to make
 (or help us make) any real changes to any things they actually have
 problems with.

 What specifically was so complicated about the theme changing? I'm
 assuming you are on Windows in which case there is a FAQ entry
 specifically about it. Was that FAQ entry not clear? What about it could
 be improved to help make it clearer?

 The FAQ also has a specific entry about the backspace beeping. What about
 that was not helpful enough? As the FAQ entry indicates it isn't something
 we are doing. The beeping is a GTK+ "feature" that is on by default in the
 "look like Windows" GTK+ theme. There isn't anything more to explain about
 it than that.

 What problem with a non-blinking taskbar button? What fix was hard to
 apply? The solution is to turn the Message Notification plugin on and tell
 it to flash the window.

 pidgin plugins are C programs, they cannot safely be distributed in
 compiled format. There is a wiki page for people who want to list their
 plugins people are welcome to up with more fancy solutions than that but
 an plugin library really just isn't going to work.

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