[Pidgin] #15749: Pidgin is not showing Facebook Contact List

[Pidgin]

#15749: Pidgin is not showing Facebook Contact List
-------------------------------------+---------------------
 Reporter:  superichy                |       Owner:  deryni
     Type:  defect                   |      Status:  new
Milestone:  2.10.8                   |   Component:  XMPP
  Version:  2.10.7                   |  Resolution:
 Keywords:  contacts facebook issue  |
-------------------------------------+---------------------

Comment (by datallah):

 Here's what's happening:

 We request the roster:
 {{{
 <iq type='get' id='purple5a97b6c8'><query xmlns='jabber:iq:roster'/></iq>
 }}}

 The server replies with:
 {{{
 <iq from='chat.facebook.com' id='purple5a97b6c8'
 to='-12345 at chat.facebook.com/Pidgin' type='result'>
     <query xmlns='jabber:iq:roster'>
         <item jid='-67890chat.facebook.com' name='Your Buddy Name'
 subscription='both'><group>Facebook Friends</group></item>
 ...
     </query>
 </iq>
 }}}

 The appropriate value for "from" is defined in
 [http://xmpp.org/rfcs/rfc6120.html#stanzas-attributes-from-c2s Section
 8.1.2.1 of RFC 6120].

 The way I read it (and I checked with the folks in the XMPP conference
 room (jdev at conference.jabber.org)), facebook isn't sending a valid iq
 response.

 "Rule 3" is in effect because the roster response is something requested
 by the client.
 This means that the correct value for "from" should be either the current
 user's bare JID (e.g. "-12345 at chat.facebook.com") or the attribute should
 be omitted altogether (which is what most other servers seem to do).

 Pidgin is discarding the response because the "from" attribute isn't valid
 - this is done for security reasons so that your roster can't be spoofed
 by a malicious client.

-- 
Ticket URL: <https://developer.pidgin.im/ticket/15749#comment:1>
Pidgin <http://pidgin.im>
Pidgin