Fixed: irregular/truncated attributes in responses from /users/show You also truncated the theme values that I was using to skin my app according to the user preferences.
It's ok to have an authenticated method that gives you everything and one unauthenticated that give you parts of it (anonymize the db). Can you please tell me what are the plans? Should I add authentication to the requests? When will this be fixed? Thanks. Nuno On Dec 9, 7:32 pm, itcn <[EMAIL PROTECTED]> wrote: > Alex; > Thanks for the prompt response and updates!! Thanks for all you guys > do, > Barry > > On Dec 9, 6:48 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: > > > Apologies once again. We introduced a regression as part of another > > bug fix. We're doing an emergency deploy right now, so the correct > > behavior should be live again shortly. > > > On Tue, Dec 9, 2008 at 14:59, 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 -
