3 ms·
"It is also limiting the rate on its API per end-point, meaning that most individual clients will be limited to 60 calls per hour instead of 350 calls per hour.
by ljd 14y ago
"It is also limiting the rate on its API per end-point, meaning that most individual clients will be limited to 60 calls per hour instead of 350 calls per hour. "
If you can't raise revenue, reduce expenses. That cut is significant enough to reduce their rate of growth of monthly expenses but probably not enough to reduce their rate of user growth. Probably not a bad move for them.
With press releases like this Twitter is App.net's new best friend.
- gjulianm 14y ago<i>Most individual API endpoints will be rate limited at 60 calls per hour per-endpoint. Based on analysis of current use of our API, this rate limit will be well above the needs of most applications built against the Twitter API, while protecting our systems from abusive applications. There will be a set of high-volume endpoints related to Tweet display, profile display, user lookup and user search where applications will be able to make up to 720 calls per hour per endpoint.</i> 60 calls per hour are only for certain endpoints, probably creating lists, tweeting... It's really rare that an user uses so much of this kind of resources. The endpoints that are used the more (viewing tweets, look up an user, etc) are actually less limited than before.
- kmfrk 14y agoMaybe they just hate the crazed Bieber, Glee, and Twilight fans out there with over 20k tweets to their name like the rest of us. :) It could suck for live-tweeting events, though.