[Pidgin] #10762: Server doesn't support blocking

[Pidgin]

#10762: Server doesn't support blocking
----------------------+-----------------------------------------------------
 Reporter:  foxmajik  |        Owner:           
     Type:  defect    |       Status:  new      
Milestone:            |    Component:  libpurple
  Version:  2.6.3     |   Resolution:           
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by deryni):

  * status:  closed => new
  * resolution:  fixed =>


Comment:

 "pending" means we are waiting on the reporter to respond, it will close
 the ticket after two weeks of waiting, going back to normal resets the
 countdown timer.

 You picked a resolution of fixed, the comment next to the resolution
 dropdown indicated that the next status would be closed (as only closed
 tickets have resolutions).

 finch is likely not a good test, at least not with the same .purple
 directory.

 It is unfortunate that we display that message, however I don't think
 modifying it in the way you indicated is going to be as helpful as we
 might like. I think it much more likely to just confuse people. Though it
 does bring up a very good additional argument for why pidgin-default
 client-side blocking is a bad idea. It means using a client in a different
 location will be even more disjoint than what already happens.

 I agree that the current situation with XMPP needs fixing, however if I
 were to fix it I would remove all client-side blocking from pidgin (except
 for protocols like IRC which have no notion of server-side blocking at
 all). So I don't think you really want me fixing it. =)

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