I've too have noticed this with location updates: updates from the web page are seen immediately in the web page and by the API; changes via the API aren't seen by either the API or the web page until after some delay.
As Lars, said this is very annoying and makes very difficult development of a client application that can be trusted by it users. API updates really have to be visible immediately from the API. Jim Renkel On Sep 17, 1:53 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > Thedelayis due to caching. We're working on reducing it. > > On Wed, Sep 17, 2008 at 12:07 AM, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > I noticed that when I start following someone via the API, and update > > the followers list, that person is not in there yet. I suppose there > > is some kind ofdelay? Thisdelayis very annoying, and disables us to > > develop a full-featured Twitter client. Are there any workarounds? Why > > is thisdelay, if there even is one? > > > Lars > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
