In the coming weeks we will release version 1.1 of the Twitter API. To help you plan ahead, we're announcing these changes now, before the new version of the API is available. Changes will include:
required authentication on every API endpoint
a new per-endpoint rate-limiting methodology
changes to our Developer Rules of the Road, especially around applications that are traditional Twitter clients.
When we release version 1.1 of the API we will simultaneously announce the deprecation of v1.0. From the day of the release, developers will have six months to migrate applications from v1.0 to v1.1.
One of the key things we've learned over the past few years is that when developers begin to demand an increasingly high volume of API calls, we can guide them toward areas of value for users and their businesses. To that end, and similar to some other companies, we will require you to work with us directly if you believe your application will need more than one million individual user tokens.
Additionally, if you are building a Twitter client application that is accessing the home timeline, account settings or direct messages API endpoints (typically used by traditional client applications) or are using our User Streams product, you will need our permission if your application will require more than 100,000 individual user tokens.
We will not be shutting down client applications that use those endpoints and are currently over those token limits. 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.
Power users of twitter won't care one bit since they don't read tweets, they just spam them like its a microphone. "News agencies" that have taken to reporting tweets like its news may need to pay attention but then who is paying attention to them? This is, sadly, all about money and the paid ad platform :/