Hello,
Just wanted to make a quick update here. I have patched Tweepy to use
'twitter.com' as the host
for the OAuth setup. This should resolve the issue for now until
Twitter resolves this issue [1].
Josh
Tweepy Author
[1] http://code.google.com/p/twitter-api/issues/detail?id=1207
Hey Josh,
Good to see I reached you, albeit not through the channel I'd anticipated. :)
I really think the issue is quite simple; sorry I haven't expressed it
clearly enough. If you look at the source of the
http://(api.)?twitter.com/oauth/authorize page, you'll see that the
sign up link is a rel
Hey Shiplu,
>> I've found that this works, until the user tries to sign out or sign
>> up during the authorization; if this happens, they get a 404. If,
>> however, twitter.com is used as the host:
>
> I think this happens due to cookie. People sign in twitter.com. not in
> api.twitter.com. When a
Sorry left off the link to the issue.
[1] http://github.com/joshthecoder/tweepy/issues#issue/8
Josh
On Thu, Dec 17, 2009 at 2:15 PM, Josh Roesslein wrote:
> Hey,
>
> Thanks for bringing this issue to my attention. I have opened an issue
> for it here [1].
> I will look into this and see what I
Hey,
Thanks for bringing this issue to my attention. I have opened an issue
for it here [1].
I will look into this and see what I can do to help resolve it. Shiplu
is probably on the right track
about this being cookie related. Will post updates here and on the
issue as I make progress.
Thanks,
On Fri, Dec 18, 2009 at 2:22 AM, Josh Bleecher Snyder
wrote:
> Hi all,
>
> The tweepy twitter client uses api.twitter.com for the host for oauth calls:
>
> REQUEST_TOKEN_URL = 'http://api.twitter.com/oauth/request_token'
> AUTHORIZATION_URL = 'http://api.twitter.com/oauth/authorize'
> AUT
