I will look into the ordering issue.

On Dec 3, 9:26 am, Naveen <knig...@gmail.com> wrote:
> This "unorderedness" is confusing to users.. They see their number of
> followers increase, then when they open their list of followers, the
> same set of people are always shown.. They are expecting to see their
> newest followers at the top of the list like they do on the twitter
> website.
>
> Its not even possible to to order this list ourselves, as the
> "followed date" is not available in the response. Though that would be
> a very expensive operation to do on a mobile device for people with
> thousands of followers.
>
> On Dec 2, 4:00 pm, Thomas Woolway <tswool...@gmail.com> wrote:
>
>
>
> > Hi Wilhelm,
>
> > Thanks for the follow up, The Twitter web site is still showing followers in
> > the correct order - is this not something that can be extended to the API,
> > and if not, why the disconnect?
>
> > Thanks,
>
> > Tom
>
> > On Wed, Dec 2, 2009 at 7:32 PM, Wilhelm Bierbaum <wilh...@twitter.com>wrote:
>
> > > Your observations are correct. Ordering cannot be guaranteed because
> > > of the way we store the graph. I'll make sure that we update the
> > > documentation to reflect this fact.
>
> > > On Dec 2, 7:45 am, tom <tswool...@gmail.com> wrote:
> > > > Hi All,
>
> > > > We've recently seen a change in the ordering of the users that the
> > > > statuses/followers method returns - according to the docs, this method
> > > > should be returning the users in this order: "They are ordered by the
> > > > order in which they followed the user". However, they now appear
> > > > essentially unordered - doing a simple curl call shows that we're not
> > > > even getting the latest 100 users back. This is causing some problems
> > > > in our app as we depend on the ordering being as documented.
>
> > > > Has anyone else noticed this? Can anyone from Twitter confirm?
>
> > > > Thanks,
>
> > > > Tom

Reply via email to