3 ms·

Marco's analysis doesn't make it sound all that reasonable: http://www.marco.org/2012/08/16/twitter-api-changes http://www.marco.org/2012/08/16/twitter-api-chan

by alphang 14y ago

Marco's analysis doesn't make it sound all that reasonable: http://www.marco.org/2012/08/16/twitter-api-changes http://www.marco.org/2012/08/16/twitter-api-changes I'm concerned about the rules about embedding a tweet. So now there'll be all this widget stuff on websites when all I'm trying to read is a quoted tweet? I guess this move is to let Twitter track my behavior across the web (http://dcurt.is/twitter-is-tracking-you-on-the-web http://dcurt.is/twitter-is-tracking-you-on-the-web), but I worry about its impact on other sites that use the API.

natrius 14y ago
Since when are embedded tweets API clients?
deleted 14y ago
[deleted]
notatoad 14y ago
Marco's analysis makes it sound less reasonable because Marco's analysis is wrong, and your interpretation of Marco's analysis makes even wronger assumptions based off of his wrong assumptions. They're not forcing you to use widgets, and you don't have to display tweets as proscribed by their API restrictions if you aren't doing it through a widget.
- jmoiron 14y ago
  From the twitter announcement (https://dev.twitter.com/blog/changes-coming-to-twitter-api 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.

by alphang 14y ago

natrius 14y ago

Since when are embedded tweets API clients?

deleted 14y ago

[deleted]

notatoad 14y ago

Marco's analysis makes it sound less reasonable because Marco's analysis is wrong, and your interpretation of Marco's analysis makes even wronger assumptions based off of his wrong assumptions. They're not forcing you to use widgets, and you don't have to display tweets as proscribed by their API restrictions if you aren't doing it through a widget.

jmoiron 14y ago
From the twitter announcement (https://dev.twitter.com/blog/changes-coming-to-twitter-api 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.