Alex, I think there might still be an issue with this fix. I've run through many test cases (including your profile) and all of them are still failing to return the full <user> object.
It looks like this might be just an issue with the xml format of / users/show (the json output seems to contain all the data). Thanks for all the hard work. If I can provide any more detail or testing assistance, let me know. Regards, Dharmesh 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