[twitter-dev] Re: Problem signing for statuses/update
I had similar weird experience on January 8: started to get incorrect signature responses from twitter. Eventually everything started to work correctly with no code change on my part. Would be great if there was more info on the subject... On Dec 21 2009, 9:35 am, jdangerslater jasoncsla...@gmail.com wrote: Well, it just started working except the asterisk. That I had to change to be escaped as %2A instead of %2a. Not sure what was up with the rest. On Dec 17, 11:20 am, jdangerslater jasoncsla...@gmail.com wrote: I'm having a problem signing status updates, but only when any of these characters is contained in the post: ! * ( ) ' For all other posts everything works fine. At first I noticed that these characters weren't being escaped, so I fixed that ( I used this:http://www.viera.info/URLEncode_Code_Chart.htmasa reference) and everything is now going out properly and the proxy debugger I'm using (Charles) decides the values properly so I think that's fine. The response I get back looks like this: hash request/statuses/update.xml/request errorIncorrect signature/error /hash Here is what my postdata looks like: oauth_consumer_key=**CONSUMER_KEY**oauth_nonce=2287oauth_signature_method =HMAC- SHA1oauth_timestamp=1261066215oauth_t oken=**OAUTH_TOKEN**oauth_version=1.0status=BAD%20CHARS%20%21%2a %28%29%27oauth_signature=LafAO6Fd1lfZ1I 6aaaGZqDKyhnA%3D Any clues as to what I'm doing wrong would help, thanks
[twitter-dev] Re: Rate Limit Whitelisting Change
Abraham, Thank you for your suggestion about curl http://jazzychad.net/iponly.php;. Submitting the IP produced by this command seem to have fixed our rate limit issue. Thank you, -Stas On Dec 13, 8:48 pm, Abraham Williams 4bra...@gmail.com wrote: Depends on on your server setup. You might have different IPs depending on weither the request is incoming or outgoing. A sure fire way to check though is to compare them. Abraham On Sun, Dec 13, 2009 at 12:48, Stas stas.ant...@gmail.com wrote: Thanks Abraham, Does this mean that the IP produced by traceroutehttp://myservername.com was an incorrect one? Thank you, -Stas On Dec 11, 12:36 pm, Abraham Williams 4bra...@gmail.com wrote: Make sure you got the correct IP whitelisted. From your server do curlhttp://jazzychad.net/iponly.php;. That will be your external IP. Abraham On Thu, Dec 3, 2009 at 22:37, Stas stas.ant...@gmail.com wrote: Hi Michael, Thanks you for your response. The error does not specify the reason (see below), but it does show when 'get status' method is being executed for an user ID that is has not been whitelisted; we cannot possibly whitelist all application users. ERROR: Rate limit exceeded. Clients may not make more than 150 requests per hour. We whitelisted our IP address; the response from Twitter stated that our IP address and twitter @user_id (that we used to submit the form) has been whitelisted (we did not ask for @user_id to be whitelisted, but Twitter whitelisted it anyway). The application is using user standard methods (get a status, update a status, get user screen name, etc.) for various users who use the application, but the initial login within the application code is done with the whitelisted user id. What's the common way of doing this task? In other words, how would somebody like HootSuite would approach this? They are getting thousands of status, screen name, etc. per minute it seems. I think we are missing something obvious. Thank you, -Stas On Nov 23, 2:56 pm, Michael Steuer mste...@gmail.com wrote: Youre seeing rate limit errors for unauthenticated calls from that ip address, or when you authenticated calls for a user that's not whitelisted? On Nov 23, 2009, at 10:30 AM, Stas stas.ant...@gmail.com wrote: We have received whitelisting approval from Twitter, but seems it is applicable to the @name and the IP. Given that we still get rate limit errors, should we just whitelist the IP? If so, what is the process of changing the whitelisting options? Thank you, -Stas -- Abraham Williams | Community Evangelist |http://web608.org Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States -- Abraham Williams | Awesome Lists |http://bit.ly/sprout608 Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: Rate Limit Whitelisting Change
Thanks Abraham, Does this mean that the IP produced by traceroute http://myservername.com; was an incorrect one? Thank you, -Stas On Dec 11, 12:36 pm, Abraham Williams 4bra...@gmail.com wrote: Make sure you got the correct IP whitelisted. From your server do curlhttp://jazzychad.net/iponly.php;. That will be your external IP. Abraham On Thu, Dec 3, 2009 at 22:37, Stas stas.ant...@gmail.com wrote: Hi Michael, Thanks you for your response. The error does not specify the reason (see below), but it does show when 'get status' method is being executed for an user ID that is has not been whitelisted; we cannot possibly whitelist all application users. ERROR: Rate limit exceeded. Clients may not make more than 150 requests per hour. We whitelisted our IP address; the response from Twitter stated that our IP address and twitter @user_id (that we used to submit the form) has been whitelisted (we did not ask for @user_id to be whitelisted, but Twitter whitelisted it anyway). The application is using user standard methods (get a status, update a status, get user screen name, etc.) for various users who use the application, but the initial login within the application code is done with the whitelisted user id. What's the common way of doing this task? In other words, how would somebody like HootSuite would approach this? They are getting thousands of status, screen name, etc. per minute it seems. I think we are missing something obvious. Thank you, -Stas On Nov 23, 2:56 pm, Michael Steuer mste...@gmail.com wrote: Youre seeing rate limit errors for unauthenticated calls from that ip address, or when you authenticated calls for a user that's not whitelisted? On Nov 23, 2009, at 10:30 AM, Stas stas.ant...@gmail.com wrote: We have received whitelisting approval from Twitter, but seems it is applicable to the @name and the IP. Given that we still get rate limit errors, should we just whitelist the IP? If so, what is the process of changing the whitelisting options? Thank you, -Stas -- Abraham Williams | Community Evangelist |http://web608.org Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: Rate Limit Whitelisting Change
Hi Michael, Thanks you for your response. The error does not specify the reason (see below), but it does show when 'get status' method is being executed for an user ID that is has not been whitelisted; we cannot possibly whitelist all application users. ERROR: Rate limit exceeded. Clients may not make more than 150 requests per hour. We whitelisted our IP address; the response from Twitter stated that our IP address and twitter @user_id (that we used to submit the form) has been whitelisted (we did not ask for @user_id to be whitelisted, but Twitter whitelisted it anyway). The application is using user standard methods (get a status, update a status, get user screen name, etc.) for various users who use the application, but the initial login within the application code is done with the whitelisted user id. What's the common way of doing this task? In other words, how would somebody like HootSuite would approach this? They are getting thousands of status, screen name, etc. per minute it seems. I think we are missing something obvious. Thank you, -Stas On Nov 23, 2:56 pm, Michael Steuer mste...@gmail.com wrote: Youre seeing rate limit errors for unauthenticated calls from that ip address, or when you authenticated calls for a user that's not whitelisted? On Nov 23, 2009, at 10:30 AM, Stas stas.ant...@gmail.com wrote: We have received whitelisting approval from Twitter, but seems it is applicable to the @name and the IP. Given that we still get rate limit errors, should we just whitelist the IP? If so, what is the process of changing the whitelisting options? Thank you, -Stas
[twitter-dev] Rate Limit Whitelisting Change
We have received whitelisting approval from Twitter, but seems it is applicable to the @name and the IP. Given that we still get rate limit errors, should we just whitelist the IP? If so, what is the process of changing the whitelisting options? Thank you, -Stas
