Re: [twitter-dev] Re: Rate limit reduction to 75?
Hi John, I appreciate the offer, and I'm excited about user steams. I attended your talk about it at chirp. But I'm afraid I don't have the resources to invest in experimental development. When everything's settled and user-streams are a reality I'll join the crowd. isaiah http://twitter.com/isaiah On Jun 29, 2010, at 7:24 PM, John Kalucki wrote: > Isaiah, > > I'm assuming your client is Kiwi, a desktop client. Are you interested in > participating in the User Streams beta test for desktop clients? User Streams > are not subject to the same rate limits that the rest of the API must adhere > to. > > We're currently lining up clients to start the beta test in the next few > weeks. Basically, you'll need to implement oAuth and follow the guidelines > (http://apiwiki.twitter.com/User-Stream-Implementation-Suggestions) to get > ready for a limited private test for a few hundred users. For capacity > planning purposes, we'll also need to understand how many users to expect > during a public beta and how many installed copies you have. > > Let me know if you'd like to participate. > > -John Kalucki > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > > > > > > > > > On Tue, Jun 29, 2010 at 12:30 PM, isaiah wrote: > > Given that Raffi told us that that Rate Limits would be going to 10X > by chirp -- it almost sounds like a joke now, but he definitely seemed > serious -- we designed features that were already constrained at 350 > calls/hr. > > Now at these dramatically lower limits, even with dynamic adjustments, > many features are failing regularly and our customers are screaming. > > Clearly cutting features from our app is pretty much the only way > forward. However we were already having trouble trying to maintain > some semblance of feature parity with Twitter.com -- which is what our > users are demanding. > > With the failures and changes combined our users are going to be > marching with pitchforks very and torches looking for heads to chop > very soon. > > I'm not asking for any specific action here. Merely passing along the > anger that we see just in case you weren't aware of it. > > Isaiah > >
Re: [twitter-dev] Re: Rate limit reduction to 75?
Isaiah, I'm assuming your client is Kiwi, a desktop client. Are you interested in participating in the User Streams beta test for desktop clients? User Streams are not subject to the same rate limits that the rest of the API must adhere to. We're currently lining up clients to start the beta test in the next few weeks. Basically, you'll need to implement oAuth and follow the guidelines ( http://apiwiki.twitter.com/User-Stream-Implementation-Suggestions) to get ready for a limited private test for a few hundred users. For capacity planning purposes, we'll also need to understand how many users to expect during a public beta and how many installed copies you have. Let me know if you'd like to participate. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Jun 29, 2010 at 12:30 PM, isaiah wrote: > > Given that Raffi told us that that Rate Limits would be going to 10X > by chirp -- it almost sounds like a joke now, but he definitely seemed > serious -- we designed features that were already constrained at 350 > calls/hr. > > Now at these dramatically lower limits, even with dynamic adjustments, > many features are failing regularly and our customers are screaming. > > Clearly cutting features from our app is pretty much the only way > forward. However we were already having trouble trying to maintain > some semblance of feature parity with Twitter.com -- which is what our > users are demanding. > > With the failures and changes combined our users are going to be > marching with pitchforks very and torches looking for heads to chop > very soon. > > I'm not asking for any specific action here. Merely passing along the > anger that we see just in case you weren't aware of it. > > Isaiah > >
[twitter-dev] Re: Rate limit reduction to 75?
Given that Raffi told us that that Rate Limits would be going to 10X by chirp -- it almost sounds like a joke now, but he definitely seemed serious -- we designed features that were already constrained at 350 calls/hr. Now at these dramatically lower limits, even with dynamic adjustments, many features are failing regularly and our customers are screaming. Clearly cutting features from our app is pretty much the only way forward. However we were already having trouble trying to maintain some semblance of feature parity with Twitter.com -- which is what our users are demanding. With the failures and changes combined our users are going to be marching with pitchforks very and torches looking for heads to chop very soon. I'm not asking for any specific action here. Merely passing along the anger that we see just in case you weren't aware of it. Isaiah
[twitter-dev] Re: Rate limit reduction to 75?
Due to the high amount of traffic we are seeing at the moment we have needed to lower the rate limit to 75 to ensure Twitter remains available to as wide an audience as possible. We are posting updates as the situation develops on http://status.twitter.com. Thanks for your patience. Matt On Jun 29, 9:45 am, SM wrote: > I have an OAuth app (http://mowglii.com/itsy) and I'm getting errors > saying I'm limited to 75 requests per hour. Huh?
