[Pidgin] #12231: XMPP smiley size

[Pidgin]

#12231: XMPP smiley size
---------------------------------------+------------------------------------
 Reporter:  Darius                     |        Owner:  deryni 
     Type:  defect                     |       Status:  closed 
Milestone:                             |    Component:  XMPP   
  Version:  2.6.6                      |   Resolution:  wontfix
 Keywords:  Emoticon smiley size XMPP  |  
---------------------------------------+------------------------------------

Comment(by Eklei):

 Actually, as late as 2.6.5, the largest emoticon I received over Google
 Talk (not just sent, so it actually went through) was 62 KB in size.  ''62
 KB.''  That's a wee distance from 8 KB.  How could I even receive such a
 huge 96x96 file?  Well that part is actually kind of funny.  Pidgin does
 not actually enforce a dimensions limit, or scale down the file itself. 
 It only scales down the ''display'' of ''received'' files.  So this file,
 while it appeared to me as only 84x96, was in fact 220x251, both in saved
 size and on the sender's screen.  This probably qualifies as its own bug.

 So people were able to send huge files as emoticons over Gtalk, and
 somehow they didn't lag and they weren't dropped by the server (either the
 files or the connections).  I don't know if you were simply mistaken or
 lying about this, and quite frankly I don't care.  Basically your answer
 is "heavens no, we can't possibly add an option".  Why does that not
 surprise me?

 You don't like his tone?  Well guess what: ''I don't like yours.''  I
 wonder why someone might have insinuated that an added option was anathema
 to the Pidgin project.  It's not like people lurking this ego theater
 might have come to certain conclusions about its direction, right?  Hey
 would you look at that!  The defect is already closed with your project's
 favorite tag, ''"wontfix"!  ''It's not like you just proved his point or
 anything.

 But that's okay.  You just go ahead and keep breaking things, while the
 users watch helplessly.  I don't have to just live with degraded
 functionality, because I am sticking with Carrier (AKA funpidgin).  Dead
 though the fork may be, at least the application still works, because the
 forked developers actually cared about the end user experience.  Crazy, I
 know.

 I don't think I'm alone when I say I'm sick and tired of these
 shenanigans.  The chorus is only silent now because your haughty behavior
 has driven them away.  More than half my contact list refuses to use
 Pidgin simply because of this attitude, much to my own chagrin. They use
 broken clients like Meebo and Digsby, but at least they feel they can see
 light at the end of the tunnel.  I am well aware these clients all use
 libpurple, which just makes their pathological inability to work correctly
 all the more amusing.

 Pidgin has a [http://www.google.ca/search?hl=en&q=pidgin%20devs%20assholes
 reputation] for being an absurdly
 [http://www.google.ca/search?hl=en&q=pidgin%20devs%20hostile hostile]
 project.  Congratulations: you've earned it.  I see that the project
 maintainers are beginning to notice its empty ranks, and now you're
 [http://theflamingbanker.blogspot.com/2010/01/on-subject-of-bugs-or-help-
 wanted-and.html asking for help]?  Good luck with that.  What reason do we
 have to believe our submitted patches will even be accepted?  They usually
 aren't.

 I've seen this nonsense time and time again, though Pidgin truly is one of
 the worst. This is why your silly little open source ideology is not going
 to prevail.  But hey, what do I know?  I'm just some stupid luser.  I can
 just screw off, right?  ''Exactly.''

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