My website uses twitter for authentication,
For the past 24 hours the OAuth sign in is continuously returning
401 , i am not able to figure out what to do?
Has some one faced similar problems?
My site has been down for 24 hours now because of this.
please help me out here.
On Tue, Dec 22, 2009 at 10:42 AM, Raffi Krikorian wrote:
> go code something interesting, and we will be here to support you. (of
> course, if we missed something, as we are arguing about in the RT case, we
> will work with you all to get it to be what the community needs).
>
>
So does this mean
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
I've reported this through several means (tweets to TwitterApi, post
on this forum, etc.). Seems to be a bug that I too would like to see
fixed!
On Dec 30, 8:51 pm, Tim Haines wrote:
> Hey guys,
>
> I'm trying:
>
> curl -u
> timhaines:123#notreallyhttp://twitter.com/statuses/retweets/563582579
The "retweeted status" is only available if the tweet is a "retweet".
Thats why I was suggesting there be a variable like "retweeted_by_me"
in the original tweet to let you know you've retweeted it so you can
Undo.
If this were to be implemented there needs to be a new method to Undo
the retweet w
i can't speak as to whether we're going to put them into the
user_timeline or not -- although, i would suspect no, as it has the
potential for breaking legacy applications, and it is something we
could revisit in a future version of the API (e.g. a hypothetical
api.twitter.com/2). again, for clari
I've noticed that you keep the filename. That was kind of annoying for
other reasons:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1f63694495c02ff/a713748c19c35895
If I just check the filename, I can't be sure that the file wasn't
changed by the user. It would be ni
