[Bug 28423] New: Conn.I.Blocking: replacement for the 'deny' ContactList channel

[bugzilla-daemon at freedesktop.org]

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

           Summary: Conn.I.Blocking: replacement for the 'deny'
                    ContactList channel
           Product: Telepathy
           Version: git master
          Platform: Other
               URL: http://git.collabora.co.uk/?p=user/smcv/telepathy-spec
                    -smcv.git;a=shortlog;h=refs/heads/blocking
        OS/Version: All
            Status: ASSIGNED
          Keywords: patch
          Severity: enhancement
          Priority: low
         Component: tp-spec
        AssignedTo: simon.mcvittie at collabora.co.uk
        ReportedBy: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org
            Blocks: 24908


When Chan.I.ContactList is replaced with Conn.I.ContactList and
Conn.I.ContactGroups, we need a replacement for the old 'deny' channel. This
spec branch is my proposal: it's a straightforward replacement for 'deny'.

Git:

http://git.collabora.co.uk/?p=user/smcv/telepathy-spec-smcv.git;a=shortlog;h=refs/heads/blocking

HTML:

http://people.freedesktop.org/~smcv/telepathy-spec-blocking/spec/org.freedesktop.Telepathy.Connection.Interface.ContactBlocking.DRAFT.html

This would be trivial to implement in telepathy-glib using TpBaseContactList
(Bug #28200).

Potential problems:

* Do we care about protocols where you can look at the block list but not edit
it? My assumption is "no".

* Do we support protocols/CMs where you can block people at runtime (or do
pseudo-blocking in the CM) but the changes aren't stored on the server? My
assumption is "no".

See also Bug #24908, which requests the ability to change the blocking policy
from default-allow to default-deny. That feature is currently out of scope for
this bug,  but we could easily add it to the Blocking interface later.

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