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 a...@twitter.com wrote:
This is a bug, deployed as part of a related
It's long since fixed.
On Fri, Jan 9, 2009 at 00:51, Paul Kinlan paul.kin...@gmail.com 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.
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 paul.kin...@gmail.com wrote:
Hi,
I am seeing
It's unfortunate, because it did work before yesterday.
I can no longer get the user timeline without a) asking them for a
username and b) using a proxy account.
It is unfortunate again because I have created www.twollo.com which
requires a users username and password and I have been hoping
Apologies. If there's some way that we can help within the realm of
API methods that we support, let me know.
On Fri, Jan 9, 2009 at 11:39, Paul Kinlan paul.kin...@gmail.com wrote:
It's unfortunate, because it did work before yesterday.
I can no longer get the user timeline without a) asking
Hehe, I am not sure if there is anything you can do other than support
cookies again :)
From an API point of view for itsabot I need to be able to detect the
current twitter user, whilst the rest of the functionality is accessed
through a proxy using my account and auth details.
I think
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
