Re: [twitter-dev] Re: Rate limits should be resetting now
Great news. I'm crossing my fingers too. isaiah http://twitter.com/isaiah On Jul 7, 2010, at 8:32 PM, Raffi Krikorian wrote: > we are currently sitting at 100% - so 350 calls/hour on oauth, and 150 > calls/hour on basic auth. fingers crossed! > > On Wed, Jul 7, 2010 at 6:42 PM, isaiah wrote: > Does this mean a return to previous rate limits as well? Or are we > still getting the squeeze? > > Isaiah > > On Jul 7, 5:54 pm, themattharris wrote: > > Hey everyone, > > > > We've been working on the rate limit issue which has been affecting > > many of you and believe we now have it fixed. As the issue affected > > people in different ways we want to be check your applications are > > working again. > > > > If your rate limit is still not resetting please email a...@twitter.com > > the following information: > > > > * The IP of the computer which is making the requests > > * A username you are making requests for > > * The time you tried to make the request > > * The request you were trying to make > > * Any response headers you received > > > > Thanks, > > Matt > > > > -- > Raffi Krikorian > Twitter Platform Team > http://twitter.com/raffi
Re: [twitter-dev] Re: Rate limits should be resetting now
Quoting Raffi Krikorian : we are currently sitting at 100% - so 350 calls/hour on oauth, and 150 calls/hour on basic auth. fingers crossed! Seems to be working fine here at the Bar Nothing Ranch - I'm getting "Bad Gateway 502" errors but between instances of those, I'm getting 150 calls per hour unauthenticated. On Wed, Jul 7, 2010 at 6:42 PM, isaiah wrote: Does this mean a return to previous rate limits as well? Or are we still getting the squeeze? Isaiah On Jul 7, 5:54 pm, themattharris wrote: > Hey everyone, > > We've been working on the rate limit issue which has been affecting > many of you and believe we now have it fixed. As the issue affected > people in different ways we want to be check your applications are > working again. > > If your rate limit is still not resetting please email a...@twitter.com > the following information: > > * The IP of the computer which is making the requests > * A username you are making requests for > * The time you tried to make the request > * The request you were trying to make > * Any response headers you received > > Thanks, > Matt -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Rate limits should be resetting now
we are currently sitting at 100% - so 350 calls/hour on oauth, and 150 calls/hour on basic auth. fingers crossed! On Wed, Jul 7, 2010 at 6:42 PM, isaiah wrote: > Does this mean a return to previous rate limits as well? Or are we > still getting the squeeze? > > Isaiah > > On Jul 7, 5:54 pm, themattharris wrote: > > Hey everyone, > > > > We've been working on the rate limit issue which has been affecting > > many of you and believe we now have it fixed. As the issue affected > > people in different ways we want to be check your applications are > > working again. > > > > If your rate limit is still not resetting please email a...@twitter.com > > the following information: > > > > * The IP of the computer which is making the requests > > * A username you are making requests for > > * The time you tried to make the request > > * The request you were trying to make > > * Any response headers you received > > > > Thanks, > > Matt > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Rate limits should be resetting now
Does this mean a return to previous rate limits as well? Or are we still getting the squeeze? Isaiah On Jul 7, 5:54 pm, themattharris wrote: > Hey everyone, > > We've been working on the rate limit issue which has been affecting > many of you and believe we now have it fixed. As the issue affected > people in different ways we want to be check your applications are > working again. > > If your rate limit is still not resetting please email a...@twitter.com > the following information: > > * The IP of the computer which is making the requests > * A username you are making requests for > * The time you tried to make the request > * The request you were trying to make > * Any response headers you received > > Thanks, > Matt
[twitter-dev] Re: Rate limits
Yes. When I get Unix time and substract it from reset-time-in-seconds, I get 3600. It might help if that's noted in the API (in addition to an example of the return structure). BTW, thanks for the quick response. For months, I have been posting questions, with no responses. On Jan 24, 5:44 pm, ryan alford wrote: > If I am not mistaken, the reset time in seconds is the number of seconds > from 1/1/1970. > > Ryan > > Sent from my DROID > > On Jan 24, 2010 8:42 PM, "EastSideDev" wrote: > > When I get the rate_limit_status.xml, this is what I get: > Array > ( > [hash] => Array > ( > [hourly-limit] => Array > ( > [content] => 2 > [attributes] => Array > ( > [type] => integer > ) > ) > [reset-time-in-seconds] => Array > ( > [content] => 1264386634 > [attributes] => Array > ( > [type] => integer > ) > ) > [reset-time] => Array > ( > [content] => 2010-01-25T02:30:34+00:00 > [attributes] => Array > ( > [type] => datetime > ) > ) > [remaining-hits] => Array > ( > [content] => 2 > [attributes] => Array > ( > [type] => integer > ) > ) > ) > ) > > The value for [reset-time-in-seconds] cannot be right. The reset time > seems right, but I would rather work with an integer value. What am I > doing wrong? Is this a Twitter API bug?
[twitter-dev] Re: Rate limits for Searching APIs (revamped)
On Jan 14, 3:49 pm, Abraham Williams <4bra...@gmail.com> wrote: > The Search API limit is not publicly available but is more then 150 calls > per hour per IP. Once you hit the rate limit there will be a header in the > response that specifies when you start making calls again. > > You can read more about the Search API rate limit here: > > http://apiwiki.twitter.com/Rate-limiting I guess I need to run this by the author of the Perl API library then. I'm seeing "x-ratelimit" headers come back on search API calls, and it does say 150 per hour. Could that be because I'm using oAuth?
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
i've been trying to post tweet from my client application, but it wont allow access. The access tokens are always returned null. Somewhere this morning, i read that Twitter no more allows registering new applications, maybe this has something to do with the DDoS. Whatever, my application is stuck, and cant proceed with my work until this is done. --Worried Lorraine ~* On Aug 10, 7:09 am, Michael Chang wrote: > On Sun, Aug 9, 2009 at 5:23 PM, Eric wrote: > > > Any idea when the limit will be increased to 20,000? I'm sure myself > > as well as other sites are suffering a bit because of the limitation > > of API calls. > > Please read the history of the mailing list. There *IS NO ETA* on anything; > it merely depends on whether the people who are "spamming" (i.e. DoSing) > twitter ever decide to go away or not. > > As has been said before, you can help by throttling your program based on > what twitter's services tell you to throttle to. Provided that your app > behaves, your app's limit may be increased when there is capacity for the > system to handle it. > > You have my sympathies, but at least it's not your site which is being > DoS-ed, so do please have consideration for the time and hard work of the > staff at twitter. > > -- > Thanks, > > Michael Chang
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
I think the twitter service is still down due to the DDOS attacks. Its not allowing to register new applications. I am trying to make my application work for the past 2 days now and without any success. Fails during authentication. Some issue with the oauth module. On Aug 10, 3:23 am, Eric wrote: > Any idea when the limit will be increased to 20,000? I'm sure myself > as well as other sites are suffering a bit because of the limitation > of API calls. > > On Aug 7, 4:54 pm, Chad Etzel wrote: > > > > > Hi Paul (and everyone), > > > Thanks for your appreciation and your comments. > > > On a personal note: I started my support role this week, which is > > supposed to be part-time. Well, as you can imagine that went out the > > window. I have all but abandoned my other work-related > > responsibilities for the past two days in order to help with the API > > communications with Twitter. > > > As you noted, when your site goes down you get a lot of email. > > Likewise, there is an amazing flood of emails coming into Twitter (not > > counting this dev-list) all asking similar questions and demanding > > answers. This has created a DDoS on the API Support team's time, in a > > manner of speaking :) > > > I think Ryan did a good job communicating what we do and don't know in > > his email this morning, and we have tried to communicate things when > > we can. > > > During the course of this DDoS, the attackers have changed tactics and > > so our Ops team have had to change their tactics in defense of the > > attack. This is happening so often that we don't want to communicate > > something out to the community that will be nullified by the next > > move. Our opinion is, that would create more thrashing and frustration > > from the community. We have been trying to communicate workarounds and > > information that has become permanent or stable as a way to deal with > > the attacks. > > > As Peter noted, we have nothing new to share at the moment, except to > > say that this thing is still ongoing, and we're having to ride it out > > with you guys. We certainly know that the 3rd party apps make Twitter > > great (I've had to tweak code on my personal apps as well), and we > > don't want to alienate you. Unfortunately we don't have an ETA on > > resolving all of the problems because we don't have an ETA on the DDoS > > :) > > > We will continue to post updates as we can. Again, we know this sucks > > for you guys, and we really do appreciate everyone being patient with > > us. > > > Thanks, > > -Chad > > > On Fri, Aug 7, 2009 at 7:16 PM, Paul Kinlan wrote: > > > > Hi Chad, > > > > I think we all appreciate the pressure you are under and the flak that you > > > are taking for events outside your control, and we all wish we could help > > > more. > > > > But for an open communications company that is postioning itself as the > > > future platform for messaging - there has been so little communication and > > > feedback to the developers in your community that it is simply shocking. > > > > Little things such as statements that we as developers can use to pass to > > > our users with regards to issues currently affecting the service would > > > help > > > immensly. I have spent my Friday night responding to over 150 emails > > > asking > > > why twollo is down - all I can say is I think it is related to current > > > events and Twitter aren't telling us anything. This doesn't inspire > > > confidence in users of my service and of twitters' > > > > The situation is reminisent to theoauthsituation the other month. Next to > > > no communication at all. > > > > We all love your service and want to build on top of it and help it grow > > > and > > > our own services too. > > > > From my own, probably selfish point of view the app engine is completly > > > blocked at the moment and as far as I can tell we have no indication if it > > > is up yet - I can't tell correctly as I am in bed writing this. > > > > Paul > > > > On 7 Aug 2009, at 21:09, Chad Etzel wrote: > > > >> Hello all, > > > >> We have been flooded with emails asking why whitelisted IPs have been > > >> reduced from the 20k rate-limit down to the normal 150 rate-limit. > > >> This is a known issue and we are working as hard as we can on > > >> resolving it. We thank you for your patience as we are dealing with > > >> everything going on with the DDoS. > > > >> Thanks, > > >> -Chad- Hide quoted text - > > - Show quoted text -
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
On Sun, Aug 9, 2009 at 5:23 PM, Eric wrote: > > Any idea when the limit will be increased to 20,000? I'm sure myself > as well as other sites are suffering a bit because of the limitation > of API calls. > Please read the history of the mailing list. There *IS NO ETA* on anything; it merely depends on whether the people who are "spamming" (i.e. DoSing) twitter ever decide to go away or not. As has been said before, you can help by throttling your program based on what twitter's services tell you to throttle to. Provided that your app behaves, your app's limit may be increased when there is capacity for the system to handle it. You have my sympathies, but at least it's not your site which is being DoS-ed, so do please have consideration for the time and hard work of the staff at twitter. -- Thanks, Michael Chang
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Any idea when the limit will be increased to 20,000? I'm sure myself as well as other sites are suffering a bit because of the limitation of API calls. On Aug 7, 4:54 pm, Chad Etzel wrote: > Hi Paul (and everyone), > > Thanks for your appreciation and your comments. > > On a personal note: I started my support role this week, which is > supposed to be part-time. Well, as you can imagine that went out the > window. I have all but abandoned my other work-related > responsibilities for the past two days in order to help with the API > communications with Twitter. > > As you noted, when your site goes down you get a lot of email. > Likewise, there is an amazing flood of emails coming into Twitter (not > counting this dev-list) all asking similar questions and demanding > answers. This has created a DDoS on the API Support team's time, in a > manner of speaking :) > > I think Ryan did a good job communicating what we do and don't know in > his email this morning, and we have tried to communicate things when > we can. > > During the course of this DDoS, the attackers have changed tactics and > so our Ops team have had to change their tactics in defense of the > attack. This is happening so often that we don't want to communicate > something out to the community that will be nullified by the next > move. Our opinion is, that would create more thrashing and frustration > from the community. We have been trying to communicate workarounds and > information that has become permanent or stable as a way to deal with > the attacks. > > As Peter noted, we have nothing new to share at the moment, except to > say that this thing is still ongoing, and we're having to ride it out > with you guys. We certainly know that the 3rd party apps make Twitter > great (I've had to tweak code on my personal apps as well), and we > don't want to alienate you. Unfortunately we don't have an ETA on > resolving all of the problems because we don't have an ETA on the DDoS > :) > > We will continue to post updates as we can. Again, we know this sucks > for you guys, and we really do appreciate everyone being patient with > us. > > Thanks, > -Chad > > On Fri, Aug 7, 2009 at 7:16 PM, Paul Kinlan wrote: > > > Hi Chad, > > > I think we all appreciate the pressure you are under and the flak that you > > are taking for events outside your control, and we all wish we could help > > more. > > > But for an open communications company that is postioning itself as the > > future platform for messaging - there has been so little communication and > > feedback to the developers in your community that it is simply shocking. > > > Little things such as statements that we as developers can use to pass to > > our users with regards to issues currently affecting the service would help > > immensly. I have spent my Friday night responding to over 150 emails asking > > why twollo is down - all I can say is I think it is related to current > > events and Twitter aren't telling us anything. This doesn't inspire > > confidence in users of my service and of twitters' > > > The situation is reminisent to the oauth situation the other month. Next to > > no communication at all. > > > We all love your service and want to build on top of it and help it grow and > > our own services too. > > > From my own, probably selfish point of view the app engine is completly > > blocked at the moment and as far as I can tell we have no indication if it > > is up yet - I can't tell correctly as I am in bed writing this. > > > Paul > > > On 7 Aug 2009, at 21:09, Chad Etzel wrote: > > >> Hello all, > > >> We have been flooded with emails asking why whitelisted IPs have been > >> reduced from the 20k rate-limit down to the normal 150 rate-limit. > >> This is a known issue and we are working as hard as we can on > >> resolving it. We thank you for your patience as we are dealing with > >> everything going on with the DDoS. > > >> Thanks, > >> -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
My curl stuff was working fine, but not it appears to have been limited again. Sorry but this is getting s frustrating. 3 days later and things still aren't working On Aug 8, 1:13 am, Chris Corriveau wrote: > Thank you Chad. Details is really what we want and just next time as > it happens is all not a day later. We all understand the stress and > unpredictability of the situation. > > - > Chris Corriveau > Sent from my iPhone > > On Aug 7, 2009, at 7:54 PM, Chad Etzel wrote: > > > > > > > Hi Paul (and everyone), > > > Thanks for your appreciation and your comments. > > > On a personal note: I started my support role this week, which is > > supposed to be part-time. Well, as you can imagine that went out the > > window. I have all but abandoned my other work-related > > responsibilities for the past two days in order to help with the API > > communications with Twitter. > > > As you noted, when your site goes down you get a lot of email. > > Likewise, there is an amazing flood of emails coming into Twitter (not > > counting this dev-list) all asking similar questions and demanding > > answers. This has created a DDoS on the API Support team's time, in a > > manner of speaking :) > > > I think Ryan did a good job communicating what we do and don't know in > > his email this morning, and we have tried to communicate things when > > we can. > > > During the course of this DDoS, the attackers have changed tactics and > > so our Ops team have had to change their tactics in defense of the > > attack. This is happening so often that we don't want to communicate > > something out to the community that will be nullified by the next > > move. Our opinion is, that would create more thrashing and frustration > > from the community. We have been trying to communicate workarounds and > > information that has become permanent or stable as a way to deal with > > the attacks. > > > As Peter noted, we have nothing new to share at the moment, except to > > say that this thing is still ongoing, and we're having to ride it out > > with you guys. We certainly know that the 3rd party apps make Twitter > > great (I've had to tweak code on my personal apps as well), and we > > don't want to alienate you. Unfortunately we don't have an ETA on > > resolving all of the problems because we don't have an ETA on the DDoS > > :) > > > We will continue to post updates as we can. Again, we know this sucks > > for you guys, and we really do appreciate everyone being patient with > > us. > > > Thanks, > > -Chad > > > On Fri, Aug 7, 2009 at 7:16 PM, Paul Kinlan > > wrote: > > >> Hi Chad, > > >> I think we all appreciate the pressure you are under and the flak > >> that you > >> are taking for events outside your control, and we all wish we > >> could help > >> more. > > >> But for an open communications company that is postioning itself as > >> the > >> future platform for messaging - there has been so little > >> communication and > >> feedback to the developers in your community that it is simply > >> shocking. > > >> Little things such as statements that we as developers can use to > >> pass to > >> our users with regards to issues currently affecting the service > >> would help > >> immensly. I have spent my Friday night responding to over 150 > >> emails asking > >> why twollo is down - all I can say is I think it is related to > >> current > >> events and Twitter aren't telling us anything. This doesn't inspire > >> confidence in users of my service and of twitters' > > >> The situation is reminisent to the oauth situation the other month. > >> Next to > >> no communication at all. > > >> We all love your service and want to build on top of it and help it > >> grow and > >> our own services too. > > >> From my own, probably selfish point of view the app engine is > >> completly > >> blocked at the moment and as far as I can tell we have no > >> indication if it > >> is up yet - I can't tell correctly as I am in bed writing this. > > >> Paul > > >> On 7 Aug 2009, at 21:09, Chad Etzel wrote: > > >>> Hello all, > > >>> We have been flooded with emails asking why whitelisted IPs have > >>> been > >>> reduced from the 20k rate-limit down to the normal 150 rate-limit. > >>> This is a known issue and we are working as hard as we can on > >>> resolving it. We thank you for your patience as we are dealing with > >>> everything going on with the DDoS. > > >>> Thanks, > >>> -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Thank you Chad. Details is really what we want and just next time as it happens is all not a day later. We all understand the stress and unpredictability of the situation. - Chris Corriveau Sent from my iPhone On Aug 7, 2009, at 7:54 PM, Chad Etzel wrote: Hi Paul (and everyone), Thanks for your appreciation and your comments. On a personal note: I started my support role this week, which is supposed to be part-time. Well, as you can imagine that went out the window. I have all but abandoned my other work-related responsibilities for the past two days in order to help with the API communications with Twitter. As you noted, when your site goes down you get a lot of email. Likewise, there is an amazing flood of emails coming into Twitter (not counting this dev-list) all asking similar questions and demanding answers. This has created a DDoS on the API Support team's time, in a manner of speaking :) I think Ryan did a good job communicating what we do and don't know in his email this morning, and we have tried to communicate things when we can. During the course of this DDoS, the attackers have changed tactics and so our Ops team have had to change their tactics in defense of the attack. This is happening so often that we don't want to communicate something out to the community that will be nullified by the next move. Our opinion is, that would create more thrashing and frustration from the community. We have been trying to communicate workarounds and information that has become permanent or stable as a way to deal with the attacks. As Peter noted, we have nothing new to share at the moment, except to say that this thing is still ongoing, and we're having to ride it out with you guys. We certainly know that the 3rd party apps make Twitter great (I've had to tweak code on my personal apps as well), and we don't want to alienate you. Unfortunately we don't have an ETA on resolving all of the problems because we don't have an ETA on the DDoS :) We will continue to post updates as we can. Again, we know this sucks for you guys, and we really do appreciate everyone being patient with us. Thanks, -Chad On Fri, Aug 7, 2009 at 7:16 PM, Paul Kinlan wrote: Hi Chad, I think we all appreciate the pressure you are under and the flak that you are taking for events outside your control, and we all wish we could help more. But for an open communications company that is postioning itself as the future platform for messaging - there has been so little communication and feedback to the developers in your community that it is simply shocking. Little things such as statements that we as developers can use to pass to our users with regards to issues currently affecting the service would help immensly. I have spent my Friday night responding to over 150 emails asking why twollo is down - all I can say is I think it is related to current events and Twitter aren't telling us anything. This doesn't inspire confidence in users of my service and of twitters' The situation is reminisent to the oauth situation the other month. Next to no communication at all. We all love your service and want to build on top of it and help it grow and our own services too. From my own, probably selfish point of view the app engine is completly blocked at the moment and as far as I can tell we have no indication if it is up yet - I can't tell correctly as I am in bed writing this. Paul On 7 Aug 2009, at 21:09, Chad Etzel wrote: Hello all, We have been flooded with emails asking why whitelisted IPs have been reduced from the 20k rate-limit down to the normal 150 rate-limit. This is a known issue and we are working as hard as we can on resolving it. We thank you for your patience as we are dealing with everything going on with the DDoS. Thanks, -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Hi Paul (and everyone), Thanks for your appreciation and your comments. On a personal note: I started my support role this week, which is supposed to be part-time. Well, as you can imagine that went out the window. I have all but abandoned my other work-related responsibilities for the past two days in order to help with the API communications with Twitter. As you noted, when your site goes down you get a lot of email. Likewise, there is an amazing flood of emails coming into Twitter (not counting this dev-list) all asking similar questions and demanding answers. This has created a DDoS on the API Support team's time, in a manner of speaking :) I think Ryan did a good job communicating what we do and don't know in his email this morning, and we have tried to communicate things when we can. During the course of this DDoS, the attackers have changed tactics and so our Ops team have had to change their tactics in defense of the attack. This is happening so often that we don't want to communicate something out to the community that will be nullified by the next move. Our opinion is, that would create more thrashing and frustration from the community. We have been trying to communicate workarounds and information that has become permanent or stable as a way to deal with the attacks. As Peter noted, we have nothing new to share at the moment, except to say that this thing is still ongoing, and we're having to ride it out with you guys. We certainly know that the 3rd party apps make Twitter great (I've had to tweak code on my personal apps as well), and we don't want to alienate you. Unfortunately we don't have an ETA on resolving all of the problems because we don't have an ETA on the DDoS :) We will continue to post updates as we can. Again, we know this sucks for you guys, and we really do appreciate everyone being patient with us. Thanks, -Chad On Fri, Aug 7, 2009 at 7:16 PM, Paul Kinlan wrote: > > Hi Chad, > > I think we all appreciate the pressure you are under and the flak that you > are taking for events outside your control, and we all wish we could help > more. > > But for an open communications company that is postioning itself as the > future platform for messaging - there has been so little communication and > feedback to the developers in your community that it is simply shocking. > > Little things such as statements that we as developers can use to pass to > our users with regards to issues currently affecting the service would help > immensly. I have spent my Friday night responding to over 150 emails asking > why twollo is down - all I can say is I think it is related to current > events and Twitter aren't telling us anything. This doesn't inspire > confidence in users of my service and of twitters' > > The situation is reminisent to the oauth situation the other month. Next to > no communication at all. > > We all love your service and want to build on top of it and help it grow and > our own services too. > > From my own, probably selfish point of view the app engine is completly > blocked at the moment and as far as I can tell we have no indication if it > is up yet - I can't tell correctly as I am in bed writing this. > > Paul > > On 7 Aug 2009, at 21:09, Chad Etzel wrote: > >> >> Hello all, >> >> We have been flooded with emails asking why whitelisted IPs have been >> reduced from the 20k rate-limit down to the normal 150 rate-limit. >> This is a known issue and we are working as hard as we can on >> resolving it. We thank you for your patience as we are dealing with >> everything going on with the DDoS. >> >> Thanks, >> -Chad >
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Agreed Twitter is not the enemy but they need to start being honest. They ate more concerned now with spin and their public image than being honest with developers and that know the truth. We all just want it fixed and back to normal but tell us when there is an issue an when you think it would be fixed. It isn't something hard to do and something I do for all my clients. - Chris Corriveau Sent from my iPhone On Aug 7, 2009, at 7:36 PM, Peter Denton wrote: Hey everyone, I just wanted to share one quick thought about this. I know everyone is really on edge here, but it might be they don't have any information or know resolution time frames. As was already expressed, people were upset Biz said "systems back to normal". Maybe they don't want to do the same thing again and further add to frustration. Again, it is a bad bad situation for everyone. Twitter is not the enemy. Regards Peter On Fri, Aug 7, 2009 at 4:25 PM, Chris Corriveau > wrote: Ahmen Paul, glad I'm not the only one that shares you sentiments. I had previously emailed Ryan something similar. What surprises me is how little they care to share with the developers who made thier service what it is. I also can't fathom how many other developers have yet to tell Twitter this and act like this is new. This DDoS has gone on for 2 days and counting and 29 hours for them to say something ro us developers is really unprofessional. Chris- On Aug 7, 2009, at 7:16 PM, Paul Kinlan wrote: Hi Chad, I think we all appreciate the pressure you are under and the flak that you are taking for events outside your control, and we all wish we could help more. But for an open communications company that is postioning itself as the future platform for messaging - there has been so little communication and feedback to the developers in your community that it is simply shocking. Little things such as statements that we as developers can use to pass to our users with regards to issues currently affecting the service would help immensly. I have spent my Friday night responding to over 150 emails asking why twollo is down - all I can say is I think it is related to current events and Twitter aren't telling us anything. This doesn't inspire confidence in users of my service and of twitters' The situation is reminisent to the oauth situation the other month. Next to no communication at all. We all love your service and want to build on top of it and help it grow and our own services too. From my own, probably selfish point of view the app engine is completly blocked at the moment and as far as I can tell we have no indication if it is up yet - I can't tell correctly as I am in bed writing this. Paul On 7 Aug 2009, at 21:09, Chad Etzel wrote: Hello all, We have been flooded with emails asking why whitelisted IPs have been reduced from the 20k rate-limit down to the normal 150 rate-limit. This is a known issue and we are working as hard as we can on resolving it. We thank you for your patience as we are dealing with everything going on with the DDoS. Thanks, -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Hey everyone, I just wanted to share one quick thought about this. I know everyone is really on edge here, but it might be they don't have any information or know resolution time frames. As was already expressed, people were upset Biz said "systems back to normal". Maybe they don't want to do the same thing again and further add to frustration. Again, it is a bad bad situation for everyone. Twitter is not the enemy. Regards Peter On Fri, Aug 7, 2009 at 4:25 PM, Chris Corriveau wrote: > > Ahmen Paul, glad I'm not the only one that shares you sentiments. I had > previously emailed Ryan something similar. What surprises me is how little > they care to share with the developers who made thier service what it is. > > I also can't fathom how many other developers have yet to tell Twitter this > and act like this is new. This DDoS has gone on for 2 days and counting and > 29 hours for them to say something ro us developers is really > unprofessional. > > Chris- > > > On Aug 7, 2009, at 7:16 PM, Paul Kinlan wrote: > > >> Hi Chad, >> >> I think we all appreciate the pressure you are under and the flak that you >> are taking for events outside your control, and we all wish we could help >> more. >> >> But for an open communications company that is postioning itself as the >> future platform for messaging - there has been so little communication and >> feedback to the developers in your community that it is simply shocking. >> >> Little things such as statements that we as developers can use to pass to >> our users with regards to issues currently affecting the service would help >> immensly. I have spent my Friday night responding to over 150 emails asking >> why twollo is down - all I can say is I think it is related to current >> events and Twitter aren't telling us anything. This doesn't inspire >> confidence in users of my service and of twitters' >> >> The situation is reminisent to the oauth situation the other month. Next >> to no communication at all. >> >> We all love your service and want to build on top of it and help it grow >> and our own services too. >> >> From my own, probably selfish point of view the app engine is completly >> blocked at the moment and as far as I can tell we have no indication if it >> is up yet - I can't tell correctly as I am in bed writing this. >> >> Paul >> >> On 7 Aug 2009, at 21:09, Chad Etzel wrote: >> >> >>> Hello all, >>> >>> We have been flooded with emails asking why whitelisted IPs have been >>> reduced from the 20k rate-limit down to the normal 150 rate-limit. >>> This is a known issue and we are working as hard as we can on >>> resolving it. We thank you for your patience as we are dealing with >>> everything going on with the DDoS. >>> >>> Thanks, >>> -Chad >>> >>
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Ahmen Paul, glad I'm not the only one that shares you sentiments. I had previously emailed Ryan something similar. What surprises me is how little they care to share with the developers who made thier service what it is. I also can't fathom how many other developers have yet to tell Twitter this and act like this is new. This DDoS has gone on for 2 days and counting and 29 hours for them to say something ro us developers is really unprofessional. Chris- On Aug 7, 2009, at 7:16 PM, Paul Kinlan wrote: Hi Chad, I think we all appreciate the pressure you are under and the flak that you are taking for events outside your control, and we all wish we could help more. But for an open communications company that is postioning itself as the future platform for messaging - there has been so little communication and feedback to the developers in your community that it is simply shocking. Little things such as statements that we as developers can use to pass to our users with regards to issues currently affecting the service would help immensly. I have spent my Friday night responding to over 150 emails asking why twollo is down - all I can say is I think it is related to current events and Twitter aren't telling us anything. This doesn't inspire confidence in users of my service and of twitters' The situation is reminisent to the oauth situation the other month. Next to no communication at all. We all love your service and want to build on top of it and help it grow and our own services too. From my own, probably selfish point of view the app engine is completly blocked at the moment and as far as I can tell we have no indication if it is up yet - I can't tell correctly as I am in bed writing this. Paul On 7 Aug 2009, at 21:09, Chad Etzel wrote: Hello all, We have been flooded with emails asking why whitelisted IPs have been reduced from the 20k rate-limit down to the normal 150 rate-limit. This is a known issue and we are working as hard as we can on resolving it. We thank you for your patience as we are dealing with everything going on with the DDoS. Thanks, -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Hi Chad, I think we all appreciate the pressure you are under and the flak that you are taking for events outside your control, and we all wish we could help more. But for an open communications company that is postioning itself as the future platform for messaging - there has been so little communication and feedback to the developers in your community that it is simply shocking. Little things such as statements that we as developers can use to pass to our users with regards to issues currently affecting the service would help immensly. I have spent my Friday night responding to over 150 emails asking why twollo is down - all I can say is I think it is related to current events and Twitter aren't telling us anything. This doesn't inspire confidence in users of my service and of twitters' The situation is reminisent to the oauth situation the other month. Next to no communication at all. We all love your service and want to build on top of it and help it grow and our own services too. From my own, probably selfish point of view the app engine is completly blocked at the moment and as far as I can tell we have no indication if it is up yet - I can't tell correctly as I am in bed writing this. Paul On 7 Aug 2009, at 21:09, Chad Etzel wrote: Hello all, We have been flooded with emails asking why whitelisted IPs have been reduced from the 20k rate-limit down to the normal 150 rate-limit. This is a known issue and we are working as hard as we can on resolving it. We thank you for your patience as we are dealing with everything going on with the DDoS. Thanks, -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
My IPs quickly go back to 20k/hour if I turn off cron jobs. When I turn on cron jobs (and thus do a large number of API calls), the IPs quickly descend into 150/hour hell.
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
alon, This is happening intermittently. Sometimes they are completly blocked other times they are allowed 150. Chris- On Fri, Aug 7, 2009 at 4:50 PM, alon wrote: > > The whitelisted ips are not just reduced. they are totally blocked. i > cant get a response from twitter using my server. totally blocked. > Only effects whitelisted. No matter authenticated or not. > > On Aug 7, 11:34 pm, Chris Corriveau wrote: > > Chad > > > > How does a DDoS change the rate limit from 20K to 150? This has been > going > > on since yesterday, so nothing new here. Is it a bandwidth issue or > > something else? > > > > Also are you still getting hit with a DDoS? > > > > Chris- > > > > On Fri, Aug 7, 2009 at 4:09 PM, Chad Etzel wrote: > > > > > Hello all, > > > > > We have been flooded with emails asking why whitelisted IPs have been > > > reduced from the 20k rate-limit down to the normal 150 rate-limit. > > > This is a known issue and we are working as hard as we can on > > > resolving it. We thank you for your patience as we are dealing with > > > everything going on with the DDoS. > > > > > Thanks, > > > -Chad >
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
The whitelisted ips are not just reduced. they are totally blocked. i cant get a response from twitter using my server. totally blocked. Only effects whitelisted. No matter authenticated or not. On Aug 7, 11:34 pm, Chris Corriveau wrote: > Chad > > How does a DDoS change the rate limit from 20K to 150? This has been going > on since yesterday, so nothing new here. Is it a bandwidth issue or > something else? > > Also are you still getting hit with a DDoS? > > Chris- > > On Fri, Aug 7, 2009 at 4:09 PM, Chad Etzel wrote: > > > Hello all, > > > We have been flooded with emails asking why whitelisted IPs have been > > reduced from the 20k rate-limit down to the normal 150 rate-limit. > > This is a known issue and we are working as hard as we can on > > resolving it. We thank you for your patience as we are dealing with > > everything going on with the DDoS. > > > Thanks, > > -Chad
[twitter-dev] Re: Rate limits: 20k -> 150 - known issue
Chad How does a DDoS change the rate limit from 20K to 150? This has been going on since yesterday, so nothing new here. Is it a bandwidth issue or something else? Also are you still getting hit with a DDoS? Chris- On Fri, Aug 7, 2009 at 4:09 PM, Chad Etzel wrote: > > Hello all, > > We have been flooded with emails asking why whitelisted IPs have been > reduced from the 20k rate-limit down to the normal 150 rate-limit. > This is a known issue and we are working as hard as we can on > resolving it. We thank you for your patience as we are dealing with > everything going on with the DDoS. > > Thanks, > -Chad >
[twitter-dev] Re: Rate Limits - Am I Blacklisted?
Ok, I'm back again. I had thought this was fixed, but indeed I still
couldn't get it to work... I just now have a clearer idea of the
problem.
Here's the problem, my GET requests won't authenticate. I'm 100%
unequivocally sure that I'm using the correct username/password
combo. It works just fine on any POST requests, but I cannot get it
to authenticate the GET request in order to stop relying on my IP rate
limiting.
Code below (ASP Classic):
Set oXMLHttp = server.Createobject("Msxml2.ServerXMLHTTP.3.0")
oXMLHttp.open "GET", "http://username:passw...@twitter.com/account/
rate_limit_status.xml", False
oXMLHttp.setRequestHeader "Content-Type", "content=text/html;
charset=iso-8859-1"
oXMLHttp.send
REsponse.ContentType = "text/xml"
REsponse.Write oXMLHttp.responseText
On Jun 16, 12:51 pm, Matt Sanford wrote:
> Hi there,
>
> Since moving servers reset things it sounds like it's using the
> unauthenticated limit. We do that if there are no credentials or if
> the credentials are incorrect. You also mention that statuses/update
> (note the plural)is giving you a 401. That would make sense if the
> username/password were incorrect as well. Is this rate limit issue
> happening for an API method that allows unauthenticated access? If so
> it sounds like it would all fit.
>
> Thanks;
> – Matt Sanford / @mzsanford
> Twitter Dev
>
> On Jun 16, 2009, at 5:14 AM, betweeted wrote:
>
>
>
> > I began noticing some strange behavior - 401 errors on status/update
> > calls saying "We were unable to authenticate you".
>
> > I racked my brain, checked and rechecked the username and password,
> > then finally I decided to create a small script to check my ratelimit
> > at account/rate_limit_status.xml and sure enough, I was at 0. I
> > waited an hour, and I was at 54. Within minutes, however, I was back
> > to 0.
>
> > So, naturally I thought some bot had hijacked my scripts and was
> > eating up my api calls. I downloaded server logs. There is no
> > excessive activity at all. In any case, all my calls are
> > authenticated, so they should be using the users api limit, not my
> > servers.
>
> > On a hunch, I uploaded the same rate limit checking script to a
> > different host that I have access to (with a different IP). Guess
> > what? 100 hits remaining.
>
> > In fact, whether I authenticate the request or not, I'm still at 0
> > hits remaining whenever I try that same script on my server. But, if
> > I try it somewhere else, I have all 100. Am I blacklisted?
>
>
[twitter-dev] Re: Rate Limits - Am I Blacklisted?
Friggin-A, man. That was it. The call I was using allows both unauthenticated AND authenticated calls. I was baffled because I thought I was authenticating, but the real issue is that I was using the wrong DOM type and couldn't authenticate. There's 16-hours of trouble-shooting down the drain. Thanks. Nick On Jun 16, 12:51 pm, Matt Sanford wrote: > Hi there, > > Since moving servers reset things it sounds like it's using the > unauthenticated limit. We do that if there are no credentials or if > the credentials are incorrect. You also mention that statuses/update > (note the plural)is giving you a 401. That would make sense if the > username/password were incorrect as well. Is this rate limit issue > happening for an API method that allows unauthenticated access? If so > it sounds like it would all fit. > > Thanks; > – Matt Sanford / @mzsanford > Twitter Dev > > On Jun 16, 2009, at 5:14 AM, betweeted wrote: > > > > > I began noticing some strange behavior - 401 errors on status/update > > calls saying "We were unable to authenticate you". > > > I racked my brain, checked and rechecked the username and password, > > then finally I decided to create a small script to check my ratelimit > > at account/rate_limit_status.xml and sure enough, I was at 0. I > > waited an hour, and I was at 54. Within minutes, however, I was back > > to 0. > > > So, naturally I thought some bot had hijacked my scripts and was > > eating up my api calls. I downloaded server logs. There is no > > excessive activity at all. In any case, all my calls are > > authenticated, so they should be using the users api limit, not my > > servers. > > > On a hunch, I uploaded the same rate limit checking script to a > > different host that I have access to (with a different IP). Guess > > what? 100 hits remaining. > > > In fact, whether I authenticate the request or not, I'm still at 0 > > hits remaining whenever I try that same script on my server. But, if > > I try it somewhere else, I have all 100. Am I blacklisted? > >
[twitter-dev] Re: Rate Limits - Am I Blacklisted?
Hi there, Since moving servers reset things it sounds like it's using the unauthenticated limit. We do that if there are no credentials or if the credentials are incorrect. You also mention that statuses/update (note the plural)is giving you a 401. That would make sense if the username/password were incorrect as well. Is this rate limit issue happening for an API method that allows unauthenticated access? If so it sounds like it would all fit. Thanks; – Matt Sanford / @mzsanford Twitter Dev On Jun 16, 2009, at 5:14 AM, betweeted wrote: I began noticing some strange behavior - 401 errors on status/update calls saying "We were unable to authenticate you". I racked my brain, checked and rechecked the username and password, then finally I decided to create a small script to check my ratelimit at account/rate_limit_status.xml and sure enough, I was at 0. I waited an hour, and I was at 54. Within minutes, however, I was back to 0. So, naturally I thought some bot had hijacked my scripts and was eating up my api calls. I downloaded server logs. There is no excessive activity at all. In any case, all my calls are authenticated, so they should be using the users api limit, not my servers. On a hunch, I uploaded the same rate limit checking script to a different host that I have access to (with a different IP). Guess what? 100 hits remaining. In fact, whether I authenticate the request or not, I'm still at 0 hits remaining whenever I try that same script on my server. But, if I try it somewhere else, I have all 100. Am I blacklisted?
[twitter-dev] Re: Rate Limits - Am I Blacklisted?
There are two rate limits. One for user account and one for IP address. Since you mentioned that when you are on a different server, your status is 100. That definitely indicates that your shared server has lot of twitter API activity going on. On Tue, Jun 16, 2009 at 8:14 AM, betweeted wrote: > > I began noticing some strange behavior - 401 errors on status/update > calls saying "We were unable to authenticate you". > > I racked my brain, checked and rechecked the username and password, > then finally I decided to create a small script to check my ratelimit > at account/rate_limit_status.xml and sure enough, I was at 0. I > waited an hour, and I was at 54. Within minutes, however, I was back > to 0. > > So, naturally I thought some bot had hijacked my scripts and was > eating up my api calls. I downloaded server logs. There is no > excessive activity at all. In any case, all my calls are > authenticated, so they should be using the users api limit, not my > servers. > > On a hunch, I uploaded the same rate limit checking script to a > different host that I have access to (with a different IP). Guess > what? 100 hits remaining. > > In fact, whether I authenticate the request or not, I'm still at 0 > hits remaining whenever I try that same script on my server. But, if > I try it somewhere else, I have all 100. Am I blacklisted? > -- Naveen K Kohli http://www.netomatix.com
