Looking into this one further... On Wed, Dec 10, 2008 at 17:21, itcn <[EMAIL PROTECTED]> wrote: > > Still the same problem; the XML version of the API no longer seems to > be returning the full data. It never made sense that this would be a > cache issue; beacuse this should return new data every time we request > the XML file; what good is data that is 24 hours old? > > > On Dec 10, 12:23 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> The fix was deployed yesterday, about 17 hours ago. Any incorrect >> responses are just cached data that will be evicted over time. >> Nothing should live in the cache longer than 24 hours, so all should >> be correct within the next 7 hours. >> >> >> >> >> >> On Wed, Dec 10, 2008 at 08:22, itcn <[EMAIL PROTECTED]> wrote: >> >> > Is there any ETA on when this bug will be fixed? >> >> > On Dec 9, 5:59 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> >> This is a temporary issue. >> >> >> On Tue, Dec 9, 2008 at 14:47, itcn <[EMAIL PROTECTED]> wrote: >> >> >> > This used to work for unauthenticated users to display statuses_count >> >> > and now it doesn't: >> >> >> >http://twitter.com/users/show/(screen_name).xml >> >> >> > Any reason this was changed recently? Is there another way to access >> >> > a user's status count (preferably without requiring the user's >> >> > authentication)? >> >> >> -- >> >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x- Hide quoted >> text - >> >> - Show quoted text - >
-- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
