[Pidgin] #9733: 2.5.8 -> Contact Stays blocked in Pidgin, despite being unblocked in other MSN clients

[Pidgin]

#9733: 2.5.8 -> Contact Stays blocked in Pidgin, despite being unblocked in other
MSN clients
----------------------------------------------------------------+-----------
 Reporter:  tigerfishdaisy                                      |        Owner:  QuLogic
     Type:  defect                                              |       Status:  new    
Milestone:                                                      |    Component:  MSN    
  Version:  2.5.8                                               |   Resolution:         
 Keywords:  UnBlocked User does not  stay unblocked in Pidgin.  |  
----------------------------------------------------------------+-----------

Comment(by tigerfishdaisy):

 Oops, my bad, then.  I'll have a look at some more libpurple code today,
 then (for the !PassportMember and !EMailMember problem).

 I don't think, however, that is the whole underlying problem, though.  To
 me, if one did distinguish between PassportMember and EMailMember and
 XXXXMember and so-on and so-forth in libpurple, that would cause, in my
 case, duplicate contacts with different networks being present in my
 contact list, which is not the case in any of the other clients I used
 (official included).

 At any rate, the official client, from glancing over its debug log,
 apparently sends out a FQY command to try and figure out the network ID of
 the contact, and then ignores the contact when the resulting FQY response
 comes back in without a 't' field in the <c> tag.  If you want, I can send
 the official client's debug log to username AT pidgin DOT im.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9733#comment:18>
Pidgin <http://pidgin.im>
Pidgin