Bug 30802

Summary: Profiles: 'message' attribute of <presence/> has strange semantics
Product: Telepathy Reporter: Will Thompson <will>
Component: tp-specAssignee: Vivek Dasmohapatra <vivek>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: vivek
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Will Thompson 2010-10-12 07:15:43 UTC 
I expected that http://telepathy.freedesktop.org/wiki/service-profile-v1#presences would basically be a superset of the information in the SimplePresence.Statuses property: <http://telepathy.freedesktop.org/spec/Connection_Interface_Simple_Presence.html#org.freedesktop.Telepathy.Connection.Interface.SimplePresence.Statuses>. Specifically, a list of statuses with name, type, whether it can be set on ourself, and whether it can have a user-supplied message.

<presence/> does have a message='' attribute, but it's not a boolean: it's a string. “the default text delivered with this presence, if any”. I don't know what the use case is for this. I do have a concrete use case for overriding the Can_Have_Message field of <http://telepathy.freedesktop.org/spec/Connection_Interface_Simple_Presence.html#Simple_Status_Spec>, though: Facebook uses XMPP, which in principle supports status messages, but Facebook just ignores them. So you'd want a profile for Facebook to be able to tell the UI “hey, the CM tells you that you can add a message here, but I know better”.
Comment 1 GitLab Migration User 2019-12-03 20:22:39 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/85.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.