<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.
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.