| From the twitter announcement (https://dev.twitter.com/blog/changes-coming-to-twitter-api): "To ensure that Twitter users have a consistent experience wherever they see and interact with Tweets, in v1.1 of the Twitter API we will shift from providing Display Guidelines to Display Requirements, which we will also introduce for mobile applications. We will require all applications that display Tweets to adhere to these." If Marco's reading is wrong, it's still the most obvious reading of the original text. Also: "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." Apropos to the Anil Dash version of the piece, the original one is already heavily tarted up with euphemisms like "guidance" where "warning" would more clearly convey their intentions. I understand the type of petty social engineering that Anil has attempted here, by spreading "Awesome" and "Excitement" around and accentuating the good instead of the bad, but I think it does developers a great disservice to assume that the biggest problem with bad news was the tone of its delivery and not the news itself. |