[Pidgin] #1525: Invisible mode doesn't work in Jabber

[Pidgin]

#1525: Invisible mode doesn't work in Jabber
---------------------------+------------------------------------------------
  Reporter:  cartman       |       Owner:        
      Type:  defect        |      Status:  closed
  Priority:  minor         |   Milestone:        
 Component:  pidgin (gtk)  |     Version:  2.0.1 
Resolution:  invalid       |    Keywords:        
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by deryni):

 We are not going to remove the invisible feature from pidgin entirely
 because it doesn't work on XMPP, that is a ludicrous request. When you
 only have XMPP accounts logged in you will find that you can't actually
 select invisible because the XMPP protocol plugin knows it isn't valid.
 The issue you are seeing is that invisible is valid across the board and
 XMPP just doesn't know what to do about it. If you want to work on
 implementing a powerful, reasonable, and useful status fallback mechanism
 that manages to always do the right thing when a protocol is told to
 activate a status it doesn't know about you are welcome to do so and we
 will gladly accept the patch. If you want to instead write a patch which
 presents the user with an error that some protocols don't support the
 status just chosen that would likely also be acceptable to some degree
 (though a direct dialog would likely not be so welcome as that would
 quickly get rather annoying).

 If invisible works with kopete and ejabberd than either kopete has
 implemented the new xep and so has ejabberd (which I doubt) or kopete
 continues to implement the utterly broken, entirely non-standard, and
 totally deprecated ancient method and ejabberd fails to disallow it (which
 I doubt) or ejabberd and kopete happen to agree on a hack that pretends or
 appears to work.

 A patch to implement XEP-0126 in pidgin would be more than welcome and
 quickly accepted.

 As reported this isn't a bug, it is at best a feature request, and more
 likely a "patches welcome" item. I can move this to either of those if
 that will make you happy but if either of you really want this fixed a
 patch is the fastest way to get that to happen.

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