[Bug 38706] initially connecting as invisible problematic since last week

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=38706

--- Comment #2 from Will Thompson <will.thompson at collabora.co.uk> 2011-07-14 08:59:35 PDT ---
I took a quick look over the log:


gabble/connection-DEBUG: 27/06/11 11:58:22.703319: get_shared_status_async
(conn-presence.c:1066):  
wocky-DEBUG: 27/06/11 11:58:22.703511: _write_node_tree: Serializing tree:
* iq xmlns='jabber:client' type='get' to='mehmet.giritli at googlemail.com'
id='524836703456'
    * query xmlns='google:shared-status' version='2'

* iq xmlns='jabber:client' to='mehmet.giritli at googlemail.com/4a46a42c'
from='mehmet.giritli at googlemail.com' id='524836703456' type='result'
    * query xmlns='google:shared-status' status-min-ver='3' status-max='512'
status-list-max='3' status-list-contents-max='5'

status-min-ver=3! Gabble checks for exactly version '2' to determine whether to
support invisibility. So then we set our own status, specifying
status-min-ver='2', which causes the server to echo stuff back to us with that
minimum version, at which point Gabble miraculously discovers that it can do
invisibility after all.

I took a look at
<http://code.google.com/apis/talk/jep_extensions/shared_status.html>, which
makes no reference to version 3 (all examples are version 2). It says:

> Clients can use status-min-ver information to optionally display hints in the user interface when a user tries to select invisible mode while logged in with a client that does not support invisibility.

and:

> Allowed values are:
> true: User is invisible. Google Talk will not advertise presence for clients that support shared-status version 2 or higher.

So:

 (a) we could write to Google and be all like “hey what's new in version 3”
 (b) we could make Gabble check for version ≥ 2, and just assume that they
won't have broken the protocol backwards-incompatibly…

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.