[Pidgin] #11433: Support Google Talk Shared Statuses

[Pidgin]

#11433: Support Google Talk Shared Statuses
---------------------------------------------+------------------------------
 Reporter:  Ecnassianer                      |        Owner:  darkrain42 
     Type:  enhancement                      |       Status:  new        
Milestone:  Patches Needing Review           |    Component:  Google Talk
  Version:  2.6.6                            |   Resolution:             
 Keywords:  google buzz gtalk shared status  |  
---------------------------------------------+------------------------------

Comment(by deryni):

 I doubt most of the people who use Google Talk even know they can be
 logged in more than once as they just use the gmail interface, so the
 sheer number of Google Talk users is largely irrelevant.

 Without actually doing a meaningful survey I'm not at all confident that
 the people who expect shared statuses to work outnumber people who don't
 want them to work and more importantly I don't think you can confidently
 assert either case either.

 I'd love to see official documentation about shared statuses affecting
 Google Buzz, that'd be fantastic (though I'm not going to hold my breath
 for it).

 Google Talk already has "special treatment" it has an account type entry
 of its own, no other XMPP service has that at the moment (despite many of
 them having been around far longer). We are considering adding a similar
 entry for Facebook in the future as well. But special treatment only
 extends so far, the problem with the patch is that it makes the situation
 with other XMPP services not supporting invisible even worse (in that when
 only XMPP accounts are enabled it will show up in the specialized status
 selector and in the per-account status selectors).

 Let me make it clear, I am fully in support of allowing clients to
 manually sync their status messages together (and would be more than happy
 to help someone write a pidgin plugin to do that either by default (that
 is on any status change) or at specific request (either a "sync" button or
 a special "set synced status" feature)). I specifically do not like Google
 Talk's implementation because it is enforced server-side and a client
 cannot get around it and mostly I dislike that it encompasses invisibility
 (though I understand that as well, in a universe where status is always
 shared having a single invisible resource is mental-model breaking).

 As an aside, dlenski I found your blog post rather dismissive, insulting,
 and biased. Not to mention that only one of the "reasons" you listed at
 the end even remotely resembles an actual reason.

 Oh and there hasn't been an endless stream of bugs about invisibility not
 working, in fact I'd wager that the recent AIM breakage caused more
 tickets to be filed in the course of the week-plus it was a problem than
 there have been tickets filed about Google Talk invisibility ever.

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