Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Initial Version and Version 1 of GSoC2009/PrivacyRewrite/protocol_specific


Ignore:
Timestamp:
May 25, 2009, 10:19:40 AM (15 years ago)
Author:
sulabh.dev
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC2009/PrivacyRewrite/protocol_specific

    v1 v1  
     1Protocols: AIM, ICQ, IRC, MSN, MYSPACE, XMPP, Yahoo!
     2
     3To design the privacy subsystem from ground up, following protocol specific information needs to be considered:
     4
     5== AIM ==
     6
     7Has two lists: block list and allow list, and has the following five options for the privacy settings:
     8
     9Allow all users to contact me
     10
     11Allow only users on my buddy list
     12
     13Allow only the users on the allow list
     14
     15Block all users
     16
     17Block only the users on the block list
     18
     19Blocking here refers to stopping messages as well as presence information. We also support being invisible to everyone irrespective of the above settings.
     20
     21== ICQ ==
     22
     23ICQ has three lists: visible list, invisible list and block list. Whereas visible and invisible lists deal with controlling the presence information, the block list deals with messages. An ICQ UIN can has following settings:
     24
     25Visible (same as not choosing any setting ?)– receives both messages and presence
     26Invisible – receives messages, but not presence
     27
     28Visible + Block – receives presence, but not messages
     29
     30Invisible + Block -- doesn't receive messages or presence
     31
     32ICQ also supports being invisible to everyone irrespective of above settings, accepting messages only from the contacts and sharing presence with ICQ and web users. 
     33
     34== IRC ==
     35
     36No server side features, hence cant block presence, only messages can be blocked that too dropping after being received by the client. Simple ignore list client side implementation.
     37
     38== MSN ==
     39
     40Has two lists in context of privacy: Allow list (AL) and Block List (BL). There is a meta contact “all others” that can be placed either in AL or in BL. Default action is to include all the buddies in the AL and include all others in BL. Messages as well notifications are blocked.
     41
     42Being invisible to everyone is supported irrespective of above settings.
     43
     44== MYSPACE ==
     45
     46The protocol has not been completely reverse engineered yet, the following features are probably supported:
     47
     48Show presence to anyone or people on the contact list
     49
     50Receive messages from anyone or people on the contact list
     51
     52Accept list and Block list – (both presence and messages ??)
     53
     54==  XMPP ==
     55
     56Privacy features are handled by XMPP extension XEP-0016, but it has been deemed too complex for implementation. Other extensions like Simple Communications Blocking, XEP-0191 has atleast partially been implemented recently in Pidgin.  For invisibility XEP-0186 has come to be the most favoured extension that doesn’t break the core XMPP rules, but I am not sure if Pidgin developers want to implement it just yet.
     57
     58From XEP-0191:
     59
     60The requirements for simple communications blocking are straightforward:
     61
     62A user must be able to block communications with a specific contact.
     63 
     64A user should be able to determine which contacts are blocked.
     65
     66A user should be able to unblock communications with a specific contact.
     67
     68The default privacy list will be equivalent to the blocklist. Duration of the block is unlimited and applies across the sessions. The blocked contact doesn’t receive any presence information, and is unable to send any XML stanzas to the user. So the presence and messages are stopped both ways.
     69
     70== Yahoo! ==
     71
     72Yahoo only has one Block list. Presence and messages are both blocked, and the protocol forces us to remove the contact from the buddy list before adding to the block list. Block list is always active.
     73
     74There is an option to “ignore everyone not on list”, which is implemented client side, and messages and other requests are dropped by the client.
     75
     76There is also “appear permanently offline list”, which lists the contacts to whom only the presence information is blocked.
     77
     78While in an invisible session, we can create “appear online” list by individually sending presence to specific contacts. But that is only valid for the session, or till we go un-invisible again.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!