Cookie support was, as you mentioned, never actually support, and it's definitely disabled. There's a method you can use to find if the user is logged in, but not WHO the user is. That's intentional.
On Fri, Jan 9, 2009 at 10:33, Paul Kinlan <[email protected]> wrote: > Hi, > > I am seeing problems using the JSON api calls to > statuses/user_timeline.json?suppress_response_codes=1 from a webpage > (www.itsabot.com) are now comming back saying that the call requires > authentication where as in the past the auth cookie went accross with the > request from a SCRIPT tab and the data came back. > > Now I know "cookie auth" is not supported, but I find it hard to perform any > form of useful "hands off" interaction without. Can you clarify that cookie > support to JSON endpoints no longer work? > > Many Kind Regards, > Paul Kinlan. > > > 2009/1/9 Alex Payne <[email protected]> >> >> It's long since fixed. >> >> On Fri, Jan 9, 2009 at 00:51, Paul Kinlan <[email protected]> wrote: >> > >> > Hi, >> > >> > I know this is probably a cheeky questions, what is there an eta for >> > the fix? My site www.itsabot.com is getting a lot of authentication >> > problems at the moment. >> > >> > Kind Regards, >> > Paul Kinlan. >> > >> > On Jan 9, 12:33 am, "Alex Payne" <[email protected]> wrote: >> >> This is a bug, deployed as part of a related fix to our handling of >> >> web sessions vs API authentication. A fix is pending deploy while we >> >> resolve some issues with our cluster's internal network. >> >> >> >> -- >> >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >> > >> >> >> >> -- >> Alex Payne - API Lead, Twitter, Inc. >> http://twitter.com/al3x > > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
