Bug 26823 - detect Facebook Chat and suppress non-working functionality?
Summary: detect Facebook Chat and suppress non-working functionality?
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-01 13:06 UTC by Simon McVittie
Modified: 2013-09-02 16:11 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon McVittie 2010-03-01 13:06:51 UTC
After ContactInfo is merged, it would be nice to detect the Facebook XMPP server, and on connections to that server, clear the SupportedFields and the Can_Set bit.

Ideally we'd also do the same for Aliasing and Avatars, but those interfaces don't have any concept of inability to set your own. For Avatars we could fake it with an empty set of supported MIME types, perhaps?
Comment 1 Simon McVittie 2010-03-22 07:39:43 UTC
Xavier points out that this also affects ContactList channels, which are rather more important (on Facebook Chat, the roster is read-only via XMPP).

One potential problem with putting in a special case that forcibly suppresses UI for write operations (contact lists, vCards, etc.) is that if/when Facebook upgrade their server to allow write operations, Telepathy UIs will keep disallowing them (until Gabble is patched again).
Comment 2 Guillaume Desmottes 2011-03-29 04:55:43 UTC
Another one: we should claim to support room listing on Facebook connection as we can't use it anyway.
Comment 3 Xavier Claessens 2011-03-29 05:01:40 UTC
Note that profile could part of this job at least: http://telepathy.freedesktop.org/wiki/service-profile-v1. Those profiles lists unsuported channel classes for the account.
Comment 4 Guillaume Desmottes 2012-01-31 02:32:11 UTC
I think the right way to do this is to extend XMPP if needed and ask Facebook to properly advertise what they (don't) support.

So we have at least:

- Not being able to set our own vCard: bug #45403

- Not being able to set our own alias

- Not being able to set our own avatar

- Not being able to modify the roster

- Not being able to list rooms or even join a chat room.
Comment 5 Guillaume Desmottes 2012-01-31 02:38:19 UTC
- Only support available and away presence: bug #39252
Comment 6 Guillaume Desmottes 2012-03-09 03:20:14 UTC
Also, Aliasing.Connection_Alias_Flags should not have the User_Set flag as we actually can't assign an alias to our contacts.
Comment 7 Xavier Claessens 2012-04-19 02:18:28 UTC
Note that MSN-XMPP is the same as facebook regarding server caps.


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.