[Bug 24908] Communication policy (blocking policy) API

[bugzilla-daemon at freedesktop.org]

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

--- Comment #32 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2011-05-05 04:12:11 PDT ---
(In reply to comment #31)
> e.g. Avatar, contact-info, showing number of buddies, external presence service

I think you're conflating two different things:

* communication policy: who is allowed to initiate a conversation with me?
  (that's this interface)

* privacy/secrecy of published information ("rich presence"): when I
  publish my avatar, contact info, etc., who's allowed to see it?  

I personally think the latter is out-of-scope for this interface: access
control for Avatars should be on the Avatars interface, and access control for
ContactInfo should be on the ContactInfo interface. (Rather like the way
Location works, except with an actual implementation...) Perhaps it should be a
settable property that is also a CM parameter? Although, having it be
asynchronous to get and set might make more sense; you'd need to look at how it
behaves in real protocols.

By "external presence service", do you mean like the way you can choose whether
your ICQ presence is visible on the ICQ website or not? That could be a
settable boolean on SimplePresence (if it's common enough to justify it) or a
subsidiary interface, maybe? Or on this interface if people don't mind blurring
its purpose.

>  - Block PSTN calls vs Client-Client calls
>  - Need PSTN specific blocking
>  - Block non-channel Protocol features

Those are all in-scope for this interface, I think: they're communication
policy analogous to what's already here.

>  - Rejecting video from some users

Is this a protocol-level feature at all? CMs should only have API for this if
there's a network-protocol operation for it (manipulating a server-stored list,
maybe).

I would have thought the behaviour at the CM level should be to not auto-accept
video at all, and the UI can auto-accept if that's what the user wants?

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