Message from discussion consistency and ecosystem opportunities
Received: by 10.142.209.17 with SMTP id h17mr1859142wfg.17.1299877774227;
Fri, 11 Mar 2011 13:09:34 -0800 (PST)
Received: by 10.143.87.9 with SMTP id p9ls449721wfl.1.p; Fri, 11 Mar 2011
13:09:08 -0800 (PST)
Received: by 10.142.231.15 with SMTP id d15mr742912wfh.17.1299877748848; Fri,
11 Mar 2011 13:09:08 -0800 (PST)
Received: by 22g2000prx.googlegroups.com with HTTP; Fri, 11 Mar 2011 13:09:08
Date: Fri, 11 Mar 2011 13:09:08 -0800 (PST)
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US)
AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16,gzip(gfe)
Subject: Re: consistency and ecosystem opportunities
From: Mike Champion <mike.champ...@gmail.com>
To: Twitter Development Talk <firstname.lastname@example.org>
Content-Type: text/plain; charset=ISO-8859-1
Thanks for the clarification Ryan. Two questions:
1) Do you have a clear definition of what counts as a Twitter client?
Is it any app/service that posts updates to Twitter, including apps
like twitterfeed and Instapaper? Or is it only those apps that are
"primarily" clients? I'm certainly familiar with the challenge of
classifying apps ;) but wanted to know who will be covered by the ToS
Section 1.5 and how you think about "clients" given Twitter's updated
2) In section 1.5.A of the ToS it says:
"Your Client must use the Twitter API as the sole source for features
that are substantially similar to functionality offered by Twitter.
Some examples include trending topics, who to follow, and suggested
Is the "Who to follow" functionality available via API from Twitter
for clients that want to offer this? I wasn't aware that it been
released as API but may have missed it on dev.twitter.com.
On Mar 11, 3:47=A0pm, Eric Mill <kproject...@gmail.com> wrote:
> "More specifically, developers ask us if they should build client apps th=
> mimic or reproduce the mainstream Twitter consumer client experience. =A0=
> answer is no."
> "We need to ensure users can interact with Twitter the same way everywher=
> I'm not sure you can say these things and simultaneously try to say you h=
> a welcoming developer environment. All third party Twitter developers, no
> matter what they make, are now walking on eggshells, constantly at risk o=
> offending Twitter's ideas of how users should interact with Twitter.
> You may feel you "need" this consistency, but you don't. You want it, and
> are willing to make tradeoffs to get it. I just hope you realize how big
> those tradeoffs are, and how chilling it is for Twitter to decide that on=
> certain kinds of innovation on the Twitter API are welcome.