Several months ago there were multiple subtle problems with consistency in following lists. We've since rolled to a new system that have numerous constraints in place to prevent duplicates and provide much stronger consistency guarantees.
There is, however, a known issue around pagination. You may see some jitter as you page through a long list -- off by one errors. We're working to fix this to make pagination completely solid. If you are seeing duplicates that aren't on a page boundary, please let us know. -John On Sep 4, 8:42 pm, Howard Siegel <hsie...@gmail.com> wrote: > There have been times when a friend or follower id has been reported > multiple times. Did you check to see if any of the friend or follower ids > that you get back were duplicates? > > - h > > On Fri, Sep 4, 2009 at 20:17, Dewald Pretorius <dpr...@gmail.com> wrote: > > > For @dewaldp I get, via the API social graph methods with paging: > > Friends: 764 , Followers: 3,977. > > > While on my web profile the numbers are: Friends: 747 , Followers: > > 3,911. > > > On Sep 4, 11:56 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > > > Not only do the social graph calls now suddenly, without any prior > > > warning of announcement, return only 5,000 ids, it is messed up even > > > when you do the paging as per the API documentation. > > > > Case in point. @socialoomph has 16,598 followers. If you page through > > > the follower ids with &page, you get only 12,017 entries. > > > > This is highly frustrating, and it has now completely screwed up my > > > follower processing. It does not help that Twitter has rolled out > > > something into production without any kind of testing, right before a > > > weekend. > > > > Dewald