[Bug 24909] Anonymity API (e.g. suppressing caller-ID)
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Mar 30 20:27:08 CEST 2010
http://bugs.freedesktop.org/show_bug.cgi?id=24909
--- Comment #20 from Will Thompson <will.thompson at collabora.co.uk> 2010-03-30 11:27:07 PST ---
>From a spec meeting:
Connection interface:
• SupportedAnonymityModes should be documented to only be stable once
you've connected. Should x-ref the type.
• Should SetAM just be a writeable D-Bus property? Maybe not if it
involves talking to the sky on GSM. But it needs to be a writeable
D-Bus so that it can be a connection parameter which is also a D-Bus
property using the DBus_Property Conn_Mgr_Param_Flag, allowing Mission
Control to update it on the fly when you change the corresponding
Account's parameters.
• Will wonders if this interface might be overly tinfoil hatty and
support features no-one will ever use, and maybe we should just have a
HideCallerID: b property?
· Others think that supporting these other flags is fine, but we
should order the flags by how obscure they are, so that the one you
actually care about — OriginatorInfo, aka caller-id — is first, and
then the introduction can say "If you just care about hiding your
caller ID, call Set("Flags", 1)".
• Capitalization is wrong. smcv or similar needs to do an editorial
pass-through.
Channel interface:
• Properties don't need to be Initial*, they're immutable. Should be
AnonymityModes, AnonymityMandatory
• Should say that those two are requestable.
• AnonymizedDisplayName: this isn't a display name, it's an Identifier.
Say that it's not requestable.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the telepathy-bugs
mailing list