Subject: [twitter-dev] Re: consistency and ecosystem
opportunities - msg#00181

Previous Message by Date:

[twitter-dev] Re: consistency and ecosystem opportunities

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 stance. 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 user lists." 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. Thanks, -mike On Mar 11, 3:47 pm, Eric Mill <kproject...@xxxxxxxxx> wrote: > "More specifically, developers ask us if they should build client apps that > mimic or reproduce the mainstream Twitter consumer client experience.  The > answer is no." > > "We need to ensure users can interact with Twitter the same way everywhere." > > I'm not sure you can say these things and simultaneously try to say you have > a welcoming developer environment. All third party Twitter developers, no > matter what they make, are now walking on eggshells, constantly at risk of > 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 only > certain kinds of innovation on the Twitter API are welcome. > > -- Eric -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk

Next Message by Date:

[twitter-dev] Looking to sell my apps

Hello Twitter Dev Community, I own/run 3 Twitter related apps that I am interested in selling to the right person. I've recently committed to a new startup and just won't have time to tend to the apps like they deserve. They are: http://tweetsaver.com http://useqwitter.com http://get.floxee.com If you know ruby/rails/sinatra or employ devs that do, these apps might be a great addition to your portfolio. They have over 170,000 users combined. If you are interested in making an offer, please contact me directly via bjoyce [at] velocis.us Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk

Previous Message by Thread:

Re: [twitter-dev] consistency and ecosystem opportunities

Translation: "Thanks for building apps that made people want to use Twitter. Thanks for putting up with us through the months and months of instability. We'll take over from here. If you want to try to build something around the fringes of Twitter, that's fine, but really, we don't need you anymore. Goodbye." Think I'm wrong? Here are the first 3 responses from people I follow on Twitter. "Just FYI, Twitter doesn't want you to make client apps anymore. http://j.mp/eTicd4" "Unfortunately the handwriting in regards to 3rd party twitter client seems to be plastered on the wall - http://t.co/SWAv1JE" "People may infer that Apple hates 3rd party devs, but Twitter has the giant brass balls to just come out and state it." I guess in hindsight, forcing the move to oAuth was just the first of many ways to eliminate developers. Oh, and this? > According to our data, 90% of active Twitter users use official Twitter apps > on a monthly basis. Gee, I wonder if that's because you add features to your own apps that you don't give others access to. How many of them are using the official Twitter apps as their primary way of reading Twitter? That's my favorite statistic since Twitter released their own iOS app with the ability to create new accounts (something you refuse to let other developers do) and then talk about the wild success of mobile account creation vs people who created an account via mobile before (which, I guess, meant sending a post via SMS since that was the only way to do it). Welcome to the beginning of the end. Maybe not for Twitter, Inc. but for developers. Nice job releasing this on a Friday afternoon too… oh, and the same day as the iPad launch? Huh. Interesting. TjL -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk

Next Message by Thread:

Re: [twitter-dev] consistency and ecosystem opportunities

On Fri, 11 Mar 2011 13:18:24 -0700, Ryan Sarver <rsarver@xxxxxxxxxxx> wrote: THE OPPORTUNITY FOR DEVELOPERS Some key areas where ecosystem developers are thriving: Â- PUBLISHER TOOLS. ÂCompanies such as SocialFlow [2] help publishers optimize how they use Twitter, leading to increased user engagement and the production of the right tweet at the right time. Â- CURATION. ÂMass Relevance [3] and Sulia [4] provide services for large media brands to select, display, and stream the most interesting and relevant tweets for a breaking news story, topic or event.  Â- REALTIME DATA SIGNALS. ÂHundreds of companies use real-time Twitter data as an input into ranking, ad targeting, or other aspects of enhancing their own core products. ÂKlout [5] is an example of a company which has taken this to the next level by using Twitter data to generate reputation scores for individuals. ÂSimilarly, Gnip [6] syndicates Twitter data for licensing by third parties who want to use our real-time corpus for numerous applications (everything from hedge funds to ranking scores).  Â- SOCIAL CRM, ENTREPRISE CLIENTS, AND BRAND INSIGHTS. ÂCompanies such as HootSuite [7], CoTweet [8], Radian6 [9], Seesmic [10], and Crimson Hexagon [11] help brands, enterprises, and media companies tap into the zeitgeist about their brands on Twitter, and manage relationships with their consumers using Twitter as a medium for interaction. Â- VALUE-ADDED CONTENT AND VERTICAL EXPERIENCES. ÂEmerging services like Formspring [12], Foursquare [13], Instagram [14], and Quora [15] have built into Twitter by allowing users to share unique and valuable content to their followers, while, in exchange, the services get broader reach, user acquisition, and traffic.  There's a common thread in most of the businesses you've listed as "thriving" above. Nearly all of them interface with *multiple* networks - Twitter, yes, but also Facebook, LinkedIn, and even MySpace. HootSuite, for example, connects to Twitter, Facebook, LinkedIn, MySpace, Ping.fm, WordPress, Foursquare and mixi. There's also Google Buzz / Latitude, Tumblr, Posterous, Gowalla, Yelp, and I'm sure many others. In short, I'd say there seem to be few businesses "thriving" that have focused only on Twitter. Last time I looked at the Alexa site rankings world-wide, Twitter was number nine. It's a long climb to the top IMHO - Twitter needs to pass Wikipedia and Baidu just to get to the point where Google, Yahoo!, Microsoft and Facebook are in sight. Twitter is still growing, for sure, but there are clearly some challenges for developers who only develop for Twitter. -- http://twitter.com/znmeb http://borasky-research.net "A mathematician is a device for turning coffee into theorems." -- Paul ErdÅs -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk