Please read the original article. This very unfairly summarizes the actual blogpost.
The limit isn't 60 hits per hour. It's 60 hits per hour per endpoint, and only for some endpoints.
The user limit is 1 million users for certain api endpoints, and 100k for others - and if you need more than that, they would like you to reach out to them.
Oh, and also, all current clients are grandfathered into the old terms.
Please examine the bandwagon carefully before jumping on it.
"If your application already has more than 100,000 individual user tokens, you'll be able to maintain and add new users to your application until you reach 200% of your current user token count (as of today) — as long as you comply with our Rules of the Road. Once you reach 200% of your current user token count, you'll be able to maintain your application to serve your users, but you will not be able to add additional users without our permission."
Translation: 'Fuck you, 3rd party Twitter clients.' They'll still cut them off at the knees when they hit at most 200,000 users.
Edit: I kept reading the blog post and it got better:
That upper-right quadrant also includes, of course, "traditional" Twitter clients like Tweetbot and Echofon. Nearly eighteen months ago, we gave developers guidance that they should not build client apps that mimic or reproduce the mainstream Twitter consumer client experience." And to reiterate what I wrote in my last post, that guidance continues to apply today.
In other words, 3rd party Twitter clients are dead. Not today, but next year they're dead as a doorknob.
Edit 2: Thanks for the clarification on the '200%' thing. I think the net result is still about the same for Twitter clients in the end. They'll be EOL'd by their developers and increasingly ignored by users.
Not 200k users. 200% of their current user count. If Product A has 150k user tokens then their limit is now 300k. If Product B has 5 billion user tokens then their limit is now 10 billion.
Although this distinction doesn't really change anything.
The limit isn't 60 hits per hour. It's 60 hits per hour per endpoint, and only for some endpoints.
The user limit is 1 million users for certain api endpoints, and 100k for others - and if you need more than that, they would like you to reach out to them.
Oh, and also, all current clients are grandfathered into the old terms.
Please examine the bandwagon carefully before jumping on it.