Twitter has shaken up some of the mechanics that govern how developers are able to interact with the social network. The changes come as part of what is seen as an overhaul of the firm's Application Programming Interface control program.
Reports suggest that any newly developed application that wants to be able to serve a user base of more than 100,000 individuals must now seek the company's "explicit permission" before it can operate as intended.
Twitter has justified the changes it is making on the basis of the company's aims to "deliver a consistent Twitter experience" for all users. Applications already boasting in excess of 100,000 users will now be permitted to expand their user base by a factor of 200% before having to return for approval to Twitter.
Director of consumer product Michael Sippey has explained that version 1.1 of the Twitter API will require authentication on every API endpoint, feature a new per-endpoint rate-limiting methodology, and also include changes to Twitter's "Developer Rules of the Road", especially around applications that are traditional Twitter clients.
"Currently, in v1.0 of the Twitter API we allow developers access to certain API endpoints without requiring their applications to authenticate, essentially enabling them to access public information from the Twitter API without us knowing who they are. For example, there are many applications that are pulling data from the Twitter API at very high rates (scraping, bots, etc.) where we only know the IP address of the applications," said Sippey.
"To prevent malicious use of the Twitter API and gain an understanding of what types of applications are accessing the API in order to evolve it to meet the needs of developers, it's important to have visibility into the activity on the Twitter API and the applications using the platform," he added.
Click here to see Twitter's Developer Rules of the Road.