[Pidgin] #15706: odd username display for facebook users

[Pidgin]

#15706: odd username display for facebook users
---------------------+-------------------------
 Reporter:  XmanORE  |       Owner:  rekkanoryo
     Type:  defect   |      Status:  closed
Milestone:           |   Component:  Facebook
  Version:  2.10.7   |  Resolution:  cantfix
 Keywords:           |
---------------------+-------------------------

Comment (by Mic92):

 Replying to [comment:10 jcourtei]:
 > Replying to [comment:9 Robby]:
 > > You are in error. The error has been reported to Facebook by
 developers of different apps.
 > I've seen the bug reported on facebook, but it works fine on
 Thunderbird, how do you explain that?
 > The fact that there is a bug on facebook's side doesn't mean that there
 is no bug on Pidgin's side
 > To me it can be fixed on client's side as well (after all, why should
 facebook send the contact's name for every update since pidgin already get
 it at log in?)

 The problem is on the protocol level (XMPP). On the first roster query,
 facebook returns the name and the jabber id correctly:

 {{{
 <!-- Out (On connection startup) -->
 <iq xmlns="jabber:client" type="get" id="1233">
 <query xmlns="jabber:iq:roster" />
 </iq>

 <!-- In -->
 <iq from="jthalheim at chat.facebook.com"
 to="jthalheim at chat.facebook.com/6d7469e9_4E31A4DB5CB9B" id="1233"
 type="result">
 <query xmlns="jabber:iq:roster">
 <item jid="-112230****@chat.facebook.com" subscription="both"
 name="Andreas Schulz"> <!-- Correct name -->
 <group>Facebook</group>
 </item>
 <!-- ... -->
 </query>
 </iq>
 }}}

 Later it sends status updates with empty names:

 {{{
 <!-- In (later) -->
 <iq from="jthalheim at chat.facebook.com"
 to="jthalheim at chat.facebook.com/6d7469e9_4E31A4DB5CB9B"
 id="fbiq4E31A5AFC6433" type="set">
 <query xmlns="jabber:iq:roster">
 <item jid="-112230****@chat.facebook.com" subscription="both" name="">
 <!-- Empty name -->
 <group>Facebook</group>
 </item>
 </query>
 </iq>
 }}}

 As pidgin follow the protocol, it updates the name from this message. As
 it seams this problem currently is prioritized low at facebook's side...

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