comparison libpurple/protocols/oscar/oscar.c @ 23438:6dc33eb841aa

Remove a failsafe check that I don't believe is needed. I'm under the impression that sometimes the last modified timestamp will (at least somewhat) legitimately be set to 0 in cases where we really have received our roster. And this function doesn't seem to get called when we haven't received our roster. So, uh, this should fix the aim buddylist for a very small fraction of users who probably gave up on using Pidgin when it didn't work for them the first time they tried.
author Mark Doliner <mark@kingant.net>
date Tue, 08 Jul 2008 00:58:21 +0000
parents c6b29adc22d1
children a73d527731ff 382e7565e628
comparison
equal deleted inserted replaced
23437:1fcdc7d11f38 23438:6dc33eb841aa
4926 od->getblisttimer = 0; 4926 od->getblisttimer = 0;
4927 4927
4928 purple_debug_info("oscar", 4928 purple_debug_info("oscar",
4929 "ssi: syncing local list and server list\n"); 4929 "ssi: syncing local list and server list\n");
4930 4930
4931 if ((timestamp == 0) || (numitems == 0)) {
4932 purple_debug_info("oscar", "Got AIM SSI with a 0 timestamp or 0 numitems--not syncing. This probably means your buddy list is empty.\n");
4933 return 1;
4934 }
4935
4936 /* Clean the buddy list */ 4931 /* Clean the buddy list */
4937 aim_ssi_cleanlist(od); 4932 aim_ssi_cleanlist(od);
4938 4933
4939 { /* If not in server list then prune from local list */ 4934 { /* If not in server list then prune from local list */
4940 PurpleBlistNode *gnode, *cnode, *bnode; 4935 PurpleBlistNode *gnode, *cnode, *bnode;