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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 21 02:23:09 CEST 2010


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

Eitan Isaacson <eitan.isaacson at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://git.collabora.co.uk/
                   |                            |?p=user/eitan/telepathy-gab
                   |                            |ble.git;a=shortlog;h=refs/h
                   |                            |eads/invisibility
             Status|NEW                         |ASSIGNED

--- Comment #7 from Eitan Isaacson <eitan.isaacson at collabora.co.uk> 2010-04-20 17:23:09 PDT ---
Some mid-work notes regarding XEP-0126:

1. Privacy lists (xep-0016) are super silly:
 a. The server storage part, just makes implementing invisibility more
complicated. We want a super simple privacy list, are we supposed to simply
trust a blessed list name like "invisible"? Retrieve it each time and make sure
it is what we need before making it the active list? Answer: Simply create a
new list called "invisible" every session. This overwrites whatever was on the
server and saves us some round trips.

 b. Multiple resource cases are tricky. What if another client is using a
different list with the same name? Each client would constantly be clobbering
the other client's list, or worse, the behavior of a client could change
mid-session because it's active list has been modified. Answer: xep-0126
recommends that all clients use the name "invisible" for global invisibility.

2. connection.c is huge and messy, I really wish there was a better place for
implementing this, hate to increase the mess, but I can't find it.

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



More information about the telepathy-bugs mailing list