[Pidgin] #414: You dont the See Which Protocol

[Pidgin]

#414: You dont the See Which Protocol
---------------------------+------------------------------------------------
  Reporter:  dancle        |       Owner:  lschiere
      Type:  defect        |      Status:  closed  
  Priority:  minor         |   Milestone:          
 Component:  pidgin (gtk)  |     Version:  2.0     
Resolution:  wontfix       |    Keywords:          
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by lschiere):

 We are not currently considering an option because this option would make
 support and code maintenance significantly more complex.  It may be a
 "simple" thing from a user's point of view, but it is not from ours.
 There will be no chance of arguing for it to be a preference for at least
 1 full release cycle after 2.0.0 final.

 Protocol changes and server outages are not really a valid argument.  If
 the protocol changes, you will know it because your account cannot
 connect.  If its a full server outage, again because you cannot connect.
 If its a partial outage, your friend is just offline for a few hours, and
 having the protocol icons really won't help you notice that.

 Being two persons is perhaps the most tempting argument.  Sean and I have
 come to think that this is not a sufficient argument, that using different
 profiles (with the -c flag) or setting up appropriate custom states will
 solve this if users give it a few weeks to adjust.  Recall, that you need
 not have all your accounts in the same state.  If you aren't at work, why
 would you want your work account online at all?  And if it is not online,
 you won't accidentally use it.  You could also use contact priorities
 (that plugin does not compile by default, but is in our source tarball) to
 effectively force the use of a given protocol when possible.  That plugin
 currently does not have any way to automatically adjust this for status or
 time, but it could be added.

 In short, I think most of the people here are reacting most strongly to
 the fact of change, and not dispassionately evaluating whether or not this
 change actually impacts them in any way, much less whether the impact is a
 net gain or loss.  I would be interested to see how many of you still
 object two weeks from now, I know that across the population of Pidgin
 developers, the number greatly reduced after we waited awhile when this
 was introduced as a pure experiment.

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