Today we are publishing some changes for our [node:110] and [node:142]. The main goal behind these changes is to better clarify our guidelines for using our API and other platform tools, based on your feedback and comments.
For example: we relaxed some display requirements around author’s name, timestamps and permalinks; we clarified that the “no commingling” term doesn’t apply to manually curated streams; and, we now require developers to disclose their privacy policies before people download, install or sign up for a service. We have also clarified some restrictions: hosting datasets of raw Tweets for download is prohibited, and automated following or bulk following is also prohibited.
We believe these changes will help provide a better experience for everyone using Twitter. Be sure to read the actual documents and use those for final reference.
- Automation rules and best practices at http://support.twitter.com/articles/76915-automation-rules-and-best-practices
You can always find previous versions of our developer rules of the road and display requirements and review the differences between versions. We go the extra mile to clearly outline every change and make sure it’s easy to understand. That said, we realize these documents can seem a bit dense –– we’re always open to feedback, please chime in with comments or questions.
July 3, 2013