[Bug 45403] ContactInfo.SupportedFields looks suspicious on my Facebook account

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2012-01-30 09:05:46 PST ---
(In reply to comment #0)
> Here is the value of this property on my Facebook account:
...
> I'm pretty sure Facebook doesn't allow us to set all this.

No, it doesn't allow us to set *any* of it, AIUI - but I don't see how we can
do better without either the Facebook server setting an anticapability, or us
hard-coding some way to detect the Facebook server and disallow it.

(The latter approach has the risk that Facebook people later make it work and
Gabble still falsely claims that it doesn't.)

> Also, having a field sharing a billion of 'type=' looks weird as well. Aren't
> we supposed to have max one type?

No, in vCard it's entirely valid to say "111111 is my work mobile number for
voice calls, and in general I'd prefer you to use it; 222222 is my home number,
use it to send me faxes, or dial-in to the BBS on my modem because I'm obsessed
with obsolete technology". That looks something like this:

TEL;TYPE=WORK,CELL,VOICE,PREF:111111
TEL;TYPE=HOME,FAX,MODEM,BBS:222222

XMPP's vcard-temp is a fairly straightforward mapping of vCard into XML, so it
inherits all this. Telepathy has an equally straightforward mapping of vCard
into D-Bus, where we'd use:

[("tel", ["type=work", "type=cell", "type=voice", "type=pref"], ["111111"]),
 ("tel", ["type=home", "type=fax", "type=modem", "type=bbs"], ["222222"])]

Admittedly, that example is clearly silly, but if you dropped the MODEM and BBS
bits it'd be entirely sane. It's certainly reasonable to want to be able to
distinguish between a home fixed line, personal ("home") mobile phone, work
fixed line (i.e. desk) and work-issued mobile phone, each of which has two
types.

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