[twitter-dev] Using Oauth I keep getting 500 errors when posting a status update (statuses/update.json)
I can't seem to get a successful call through. I tried 1/statuses/ update.json and just /statuses/update.json. I can make other authenticated calls but status updates fail. My HTTP body is just status=test. Any ideas what the issue could be?
[twitter-dev] Re: Slow response to twitter updates for a third party app
We see the same huge latency and timeouts as well (our timeouts are also at 30 seconds). We running out of a US data center on multiple machines, we see this issue on all if our servers. I agree with @tjaap, would like to hear twitters reaction as well. On May 7, 6:02 pm, Tjaap jdmeij...@gmail.com wrote: I'm seeing exactly the same: big latency and a lot of timeouts. When posting a tweet, Twitter sometimes does not return a response within 30 seconds. After my curl times out, the app has no way of knowing if the post made it or not. Sometimes it will appear on Twitter and sometimes it won't. This effectively breaks our app. Replicated the error on two different servers (in the Netherlands) and with different accounts. I would very much appreciate a reaction from Twitter on this. We are in the process of switching to OAuth, but I would like to know if I have to implement a workaround while we're on the old system. Thanks, @tjaap
[twitter-dev] I am a beginner with xauth
Hello Guys. Can someone here direct me to a place which i can understand how to begin implementing xauth on my PHP server? I already have a twitter application ID and authorization to use XAUTH. Thanks, Roee A.
Re: [twitter-dev] I am a beginner with xauth
On 5/8/2010 2:56 AM, RoeeA wrote: Hello Guys. Can someone here direct me to a place which i can understand how to begin implementing xauth on my PHP server? I already have a twitter application ID and authorization to use XAUTH. Thanks, Roee A. http://dev.twitter.com/pages/xauth And from what I hear, xAuth for web apps is a one-off thing to convert usernames and passwords. Once you've converted and stored the tokens you should just use oAuth minus the xAuth conversion.
Re: [twitter-dev] Slow response to twitter updates for a third party app
Thanks for the notice. That is definitely not an expected behavior or response time. We're investigating the cause and will follow up with more information as we figure out the cause. Thanks for reporting it. Best, rs On Saturday, May 8, 2010, Naveen Ayyagari nav...@getsocialscope.com wrote: We see the same huge latency and timeouts as well (our timeouts are also at 30 seconds). We running out of a US data center on multiple machines, we see this issue on all if our servers. I agree with @tjaap, would like to hear twitters reaction as well. On May 7, 6:02 pm, Tjaap jdmeij...@gmail.com wrote: I'm seeing exactly the same: big latency and a lot of timeouts. When posting a tweet, Twitter sometimes does not return a response within 30 seconds. After my curl times out, the app has no way of knowing if the post made it or not. Sometimes it will appear on Twitter and sometimes it won't. This effectively breaks our app. Replicated the error on two different servers (in the Netherlands) and with different accounts. I would very much appreciate a reaction from Twitter on this. We are in the process of switching to OAuth, but I would like to know if I have to implement a workaround while we're on the old system. Thanks, @tjaap
Re: [twitter-dev] Re: Slow response to twitter updates for a third party app
Raj, Naveen, @tjaap, Do any of you still have tcp dumps of the calls you were making that were getting long timeouts? On Sat, May 8, 2010 at 12:08 AM, Naveen Ayyagari nav...@getsocialscope.comwrote: We see the same huge latency and timeouts as well (our timeouts are also at 30 seconds). We running out of a US data center on multiple machines, we see this issue on all if our servers. I agree with @tjaap, would like to hear twitters reaction as well. On May 7, 6:02 pm, Tjaap jdmeij...@gmail.com wrote: I'm seeing exactly the same: big latency and a lot of timeouts. When posting a tweet, Twitter sometimes does not return a response within 30 seconds. After my curl times out, the app has no way of knowing if the post made it or not. Sometimes it will appear on Twitter and sometimes it won't. This effectively breaks our app. Replicated the error on two different servers (in the Netherlands) and with different accounts. I would very much appreciate a reaction from Twitter on this. We are in the process of switching to OAuth, but I would like to know if I have to implement a workaround while we're on the old system. Thanks, @tjaap
Re: [twitter-dev] Re: Slow response to twitter updates for a third party app
Any chance that the timeouts are correlated with the top of the hour? -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sat, May 8, 2010 at 12:08 AM, Naveen Ayyagari nav...@getsocialscope.com wrote: We see the same huge latency and timeouts as well (our timeouts are also at 30 seconds). We running out of a US data center on multiple machines, we see this issue on all if our servers. I agree with @tjaap, would like to hear twitters reaction as well. On May 7, 6:02 pm, Tjaap jdmeij...@gmail.com wrote: I'm seeing exactly the same: big latency and a lot of timeouts. When posting a tweet, Twitter sometimes does not return a response within 30 seconds. After my curl times out, the app has no way of knowing if the post made it or not. Sometimes it will appear on Twitter and sometimes it won't. This effectively breaks our app. Replicated the error on two different servers (in the Netherlands) and with different accounts. I would very much appreciate a reaction from Twitter on this. We are in the process of switching to OAuth, but I would like to know if I have to implement a workaround while we're on the old system. Thanks, @tjaap
[twitter-dev] Re: what's wrong with my xAuth code ???
anybody ???
[twitter-dev] Re: Slow response to twitter updates for a third party app
john - I just scanned DM's and tweets that were slow or had no response from twitter - none were at top of hour - hth
[twitter-dev] Enable xAuth for app owners
Hey guys, I had an idea for a feature that I would like to suggest. If it's not difficult, can you extend xAuth to always allow just the owner of the application itself to be able to authenticate with xAuth by default? The http://dev.twitter.com/apps/xx/my_tokenhttp://dev.twitter.com/apps/413/my_token page is fantastic but it would be just a little bit nicer for single user apps to avoid one step of hunting down that access token. It makes one less step to get up and running with twurl and my OAuth enabled fork of earlybird. Zac Bowling @zbowling
Re: [twitter-dev] I am a beginner with xauth
The problem is that i don't know how to implement such Authentication on my PHP server side. I shall not use Oauth examples due to extras inside the code and i cannot find no PHP Xauth example on the net. Thanks, On Sat, May 8, 2010 at 8:28 PM, John Meyer john.l.me...@gmail.com wrote: On 5/8/2010 2:56 AM, RoeeA wrote: Hello Guys. Can someone here direct me to a place which i can understand how to begin implementing xauth on my PHP server? I already have a twitter application ID and authorization to use XAUTH. Thanks, Roee A. http://dev.twitter.com/pages/xauth And from what I hear, xAuth for web apps is a one-off thing to convert usernames and passwords. Once you've converted and stored the tokens you should just use oAuth minus the xAuth conversion. -- Roee Aizman, CTO E: roe...@gmail.com M: +972-542345222 Amigos-Online.com Friends have never been so close
Re: [twitter-dev] I am a beginner with xauth
http://github.com/abraham/twitteroauth/blob/master/DOCUMENTATION On 5/8/2010 3:25 PM, Roee A. wrote: The problem is that i don't know how to implement such Authentication on my PHP server side. I shall not use Oauth examples due to extras inside the code and i cannot find no PHP Xauth example on the net. Thanks, On Sat, May 8, 2010 at 8:28 PM, John Meyer john.l.me...@gmail.com mailto:john.l.me...@gmail.com wrote: On 5/8/2010 2:56 AM, RoeeA wrote: Hello Guys. Can someone here direct me to a place which i can understand how to begin implementing xauth on my PHP server? I already have a twitter application ID and authorization to use XAUTH. Thanks, Roee A. http://dev.twitter.com/pages/xauth And from what I hear, xAuth for web apps is a one-off thing to convert usernames and passwords. Once you've converted and stored the tokens you should just use oAuth minus the xAuth conversion. -- Roee Aizman, CTO E: roe...@gmail.com mailto:roe...@gmail.com M: +972-542345222 Amigos-Online.com Friends have never been so close
Re: [twitter-dev] I am a beginner with xauth
Hi. Thanks a lot. It is talking about Oauth and there are a lot of extras which i don;t know. I just need to understand what am i sending to the server (PHP) to gain these tokens and work with them later on. Thanks, On Sun, May 9, 2010 at 12:42 AM, John Meyer john.l.me...@gmail.com wrote: http://github.com/abraham/twitteroauth/blob/master/DOCUMENTATION On 5/8/2010 3:25 PM, Roee A. wrote: The problem is that i don't know how to implement such Authentication on my PHP server side. I shall not use Oauth examples due to extras inside the code and i cannot find no PHP Xauth example on the net. Thanks, On Sat, May 8, 2010 at 8:28 PM, John Meyer john.l.me...@gmail.com mailto:john.l.me...@gmail.com wrote: On 5/8/2010 2:56 AM, RoeeA wrote: Hello Guys. Can someone here direct me to a place which i can understand how to begin implementing xauth on my PHP server? I already have a twitter application ID and authorization to use XAUTH. Thanks, Roee A. http://dev.twitter.com/pages/xauth And from what I hear, xAuth for web apps is a one-off thing to convert usernames and passwords. Once you've converted and stored the tokens you should just use oAuth minus the xAuth conversion. -- Roee Aizman, CTO E: roe...@gmail.com mailto:roe...@gmail.com M: +972-542345222 Amigos-Online.com Friends have never been so close -- Roee Aizman, CTO E: roe...@gmail.com M: +972-542345222 Amigos-Online.com Friends have never been so close
[twitter-dev] Re: Slow response to twitter updates for a third party app
I dont have tcp dumps available.. Ill try to get some captures later this weekend.. Ill also run through the logs to see if they have any correlation with top of the hour, but my gut instinct is they do not. Anywhere specific I should send tcp dumps, as they may contain username and passwords of our users (we are still in the process of switching over to OAuth)? Should I just XXX those out? On May 8, 1:50 pm, Ryan Sarver rsar...@twitter.com wrote: Raj, Naveen, @tjaap, Do any of you still have tcp dumps of the calls you were making that were getting long timeouts? On Sat, May 8, 2010 at 12:08 AM, Naveen Ayyagari nav...@getsocialscope.comwrote: We see the same huge latency and timeouts as well (our timeouts are also at 30 seconds). We running out of a US data center on multiple machines, we see this issue on all if our servers. I agree with @tjaap, would like to hear twitters reaction as well. On May 7, 6:02 pm, Tjaap jdmeij...@gmail.com wrote: I'm seeing exactly the same: big latency and a lot of timeouts. When posting a tweet, Twitter sometimes does not return a response within 30 seconds. After my curl times out, the app has no way of knowing if the post made it or not. Sometimes it will appear on Twitter and sometimes it won't. This effectively breaks our app. Replicated the error on two different servers (in the Netherlands) and with different accounts. I would very much appreciate a reaction from Twitter on this. We are in the process of switching to OAuth, but I would like to know if I have to implement a workaround while we're on the old system. Thanks, @tjaap
[twitter-dev] Re: Using Oauth I keep getting 500 errors when posting a status update (statuses/update.json)
Looks like the problem was me. I'm a fool. Just in case this happens to anyone else I'll post the solution. I was setting the responseType to a standard form/multipart when it just needed to be blank.
[twitter-dev] Current TwitterOAuth API won't display authorization page
I'm having a puzzling (to me) problem with the TwitterOAuth API. I wrote and debugged code to get authorization to use a Twitter account, but I wasn't able to set the callback URL. With the help of people in this forum, I learned that I had an old beta copy of the API. Installing a current copy was supposed to solve the problem. Instead, it broke my program. Now, when I call click the link returned by getAuthorizeURL, I don't get the authorization page at all. I'm just redirected to the callback URL. (Yes, getAuthorizeURL is returning a URL on Twitter that looks about the same as it did before: https://twitter.com/oauth/authenticate?oauth_token=[a long string of gibberish].) What's happening here?
