Earlier this summer, Twitter made a public declaration about their intentions to “deliver a consistent experience” across all connected sites and apps. They tightened up their developer rules and started cutting loose those folks that didn’t fit with the new model. Now, they’ve taken another step which could severely impact some of the more popular third-party clients.
Twitter has just announced another round of changes which includes a cap on user tokens.
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.