[Bug 20768] Support more ways to be invisible (XEP-0186, maybe XEP-0126, maybe whatever Google does)

[bugzilla-daemon at freedesktop.org]

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

--- Comment #21 from Will Thompson <will.thompson at collabora.co.uk> 2010-06-24 05:35:52 PDT ---
(In reply to comment #19)
> From my XEP parsing, this is not a real issue. Creating a list and editing a
> list are semantically the same (XEP-0016 2.6 & 2.7). When you edit a list that
> is active in another resource, you don't get an error (although the other
> client gets a push notification). In other words a 'invisible' list creation
> stanza is guaranteed to not return a <conflict /> error from the server.

Aha, I misread the XEP: you can't delete lists that are in use, and I assumed
you couldn't modify lists which are in use either.

> The case we need to look out for is when Gabble #2 signs in and "creates" a
> list, Gabble #1 will get a privacy list push notification, which in turn it
> needs to retrieve the list, see that it is still the standard 'invisible' list,
> and carry on.

Yep, although maybe we should relax “the standard 'invisible' list” to
something like “starts with the standard <item action='deny'
order='1'><presence-out/></item> rule” or something? Not overly fussed.

> If client #2 is a rogue client (Let's call in GAIM ;), and is doing it's own
> weird crap to the 'invisible' list, then we need to gracefully step out of it's
> way, by creating and activating a list called 'invisible-gabble'.
> 
> If client #1 is rogue, when Gabble #2 signs in, it will clobber #1's
> 'invisible' list. If #1 listens for push notifications and fights back by
> re-editing 'invisible', Gabble #2 will step out by creating 'invisible-gabble'.

Yeah, so something like “if an 'invisible' list already exists, or is created,
and doesn't look like we want, give up and make a gabble-specific one” sounds
good to me.

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