Re: [twitter-dev] Re: Rate Limit & Whitelisting Change
If your whitelisted ip is w.w.w.w and outgoing interface is o.o.o.o For any request twitter will see o.o.o.o as your ip address. Not w.w.w.w if you have w.w.w.w interface attached to your host and its an Internet gateway but not the default gateway (o.o.o.o) you can bind all the twitter connection from w.w.w.w interface. In curl we do this by curl --interface w.w.w.w http://twitter.com/account/rate_limit_status.xml -- Shiplu Mokaddim My talks, http://talk.cmyweb.net Follow me, http://twitter.com/shiplu SUST Programmers, http://groups.google.com/group/p2psust Innovation distinguishes bet ... ... (ask Steve Jobs the rest)
[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 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 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 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 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
Re: [twitter-dev] Re: Rate Limit & Whitelisting Change
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 wrote: > 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 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 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 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 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 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 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
Re: [twitter-dev] Re: Rate Limit & Whitelisting Change
Make sure you got the correct IP whitelisted. >From your server do "curl http://jazzychad.net/iponly.php";. That will be your external IP. Abraham On Thu, Dec 3, 2009 at 22:37, Stas 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 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 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 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 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
