[Pidgin] #12231: XMPP smiley size
Pidgin
trac at pidgin.im
Fri Jun 25 00:26:24 EDT 2010
#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):
I'm sorry for the way I responded. I can very much see how it would be
taken as flamebait. Really, though, I'm just expressing (a lot of)
frustration. I felt compelled to lash out with the voices of those who
have long since stopped participating.
The point about the hostile project remains true, as any number of
searches will show, but I was stereotypically including you in the
abstract category of "jerks who develop Pidgin". I see now from your
measured response that this was unfair.
I became curious to see what your position was on [/ticket/4986 the
situation that precipitated the Carrier/funpidgin fork], and I saw that
you didn't participate at all. You may not even be aware of it, and the
resulting bad blood.
I did read your post, and I simply disagree that "the standards" are a
valid catch-all excuse for degradation, and I get annoyed when open source
projects cling tenaciously to the divine edict of committee. A lot of
things in technology would never get done if they had to wait for
standardization. I think reimplementing the functionality with better
technological underpinnings is a good idea, and I'd be all for doing it
properly, but since there is no guarantee that will ever actually happen,
I'd rather settle for doing it wrong (or having the ''option'' to) in the
meantime. Google's servers clearly don't care.
I know how easy it is to make an option (a lot easier and less time
consuming than compiling someone else's codebase with a lot of
dependencies on a non-native platform). Unfortunately, as the discussion
in the linked bug report shows, this devteam will literally reject patches
that provide preferences simply because they think preferences are the
"wrong way". Worse yet, the person ''this'' bug was assigned to ''is one
of these very same people.''
Quoth [/ticket/4986#comment:138 deryni]:
> Oh, and the fact that someone actually took the time to implement the
preference for switching back to the old behaviour is a very nice surprise
and I would like to thank nodashi for doing so (assuming the patch is
yours). I have no intention of accepting such a patch because I still
believe that is the wrong way to fix this and I would think it could be
written as a plugin as well, but it at least shows a proper way of
handling this situation and for that I want to commend you.
Nice.
Upon searching for your name, darkrain42, I found I had merely forgotten
it. It appears you made the useful XMPP priority plugin, something I
believe should really be default functionality. The fact that it is not a
patch suggests to me you may be able to see where I'm coming from with
respect to patch viability.
While I'd like to see this resolved in favor of usability, I must admit
that I'm necessarily detached from the eventual outcome, because I have no
choice but to use Carrier, dead as it is. The very feature that caused
the Carrier fork (text entry sizing) is a total usability breaker for me.
Between my penchant for sending large messages, and the textboxes jumping
around, I simply can't use a modern version of Pidgin. And the devteam
couldn't care less. Thus, my frustration. All for want of an ''option.''
For the record, it was a contact that sent me a huge emoticon from Pidgin
2.6.5. I continue to use Carrier, stuck on version 2.6.1. This will
likely be my last post since, as mentioned, I can't really have anything
like a vested interest in Pidgin anymore.
--
Ticket URL: <http://developer.pidgin.im/ticket/12231#comment:4>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list