I am also running into these issues with users/lookup.json. The ids I have issues with are totally random. Sometimes the duplicates are back to back, other times they are separated by a few records.
example screen names that are all returned duplicates: yaneeduh, JDH1127, MelxWeasley, ealderson, jennypenk, shubbs1, zx48k, Krausekid211, MissKellieBelly On Mar 9, 4:49 am, nischalshetty <[email protected]> wrote: > Hi, > > I too am getting duplicate results and some of the valid ids are not > beings returned. If it helps, these ids would replicate all the issues > faced : > > 166661825, 248874232, 28296091, 251642658, 257793455, 225992183, > 85168850, 92509004, 113697273, 99673641, 99253238, 98032551, 91619850, > 47528631, 52652119, 14941300, 26403984, 33322905, 32162070, 24612782, > 25218999, 20829096, 19491208, 18549369, 15074733, 13757662, 68889828 > > -N > > On Mar 2, 2:02 pm, David JULIEN <[email protected]> wrote: > > > I have noticed this strange behaviour too (duplicated results and > > unknown users). For instance, yesterday, when I tried to lookup for > > user 44537294 (with two different accounts), I received during many > > hours information about user 243784138, before receiving expected > > result (around 17/18h UTC). > > > David -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
