I agree with blogging platforms and social networks but not the rest. Being an owner of a website does not imply that I'm a "Google user". Nor is a musician a user of the used record store.
On Nov 17, 8:48 pm, John Kalucki <j...@twitter.com> wrote: > Every search engine, social network, blogging platform, content aggregator, > and to a certain extent, every used book store and used record store... > > -JohnOn Wed, Nov 17, 2010 at 1:04 PM, Dewald Pretorius <dpr...@gmail.com> > wrote: > > As a business model, is there another company that takes content, > > which its users create and enter into the company's service with no > > compensation, and then turns around and sells that content to third > > parties, still with no compensation to the creators of the content? > > > I've been trying to think of another company that does this, but I'm > > striking a blank. I'm sure there must be others. > > > On Nov 17, 4:55 pm, Adam Green <140...@gmail.com> wrote: > > > Ryan, I understand. I'm just happy to see you help companies put a > > > real value on Twitter data in any form. And I'm happy to see Twitter > > > find new ways to make money. You'll never hear "everything online must > > > be free" from me. I go way back to when people paid for software, in > > > a box, in stores. > > > > I'm also willing to bet that Twitter will eventually allow a paid > > > market to develop in actual tweets as well as data derived from them. > > > When Twitter IPOs, the market will demand that. Paying a third party > > > to filter and rank tweets that can be displayed on a website seems > > > perfectly legitimate. Why should every company have to pay to do their > > > own API programming to display aggregated tweets, when they can pay > > > someone for high quality tweets as a service? It seems illogical to > > > me, and from the point of view of the tweet's author, the copyright > > > issues are identical. > > > > On Wed, Nov 17, 2010 at 3:31 PM, Ryan Sarver <rsar...@twitter.com> > > wrote: > > > > Adam, it's a good question and it really comes down to what you are > > > > trying to re-sell. > > > > > Re-syndication or re-sale of the actual tweets is strictly prohibited > > > > and won't change on our end. We are however, ok with reselling of data > > > > that results from analysis of the Twitter API. > > > > > So a great example is Klout. They do a lot of work to determine a > > > > user's Klout score by analyzing the Twitter API and the content of > > > > tweets. They *are* able to resell their score, but they would not be > > > > able to resell the tweets that were used to determine that score. > > > > > It's nuanced, so let me know if that makes sense. > > > > > On Wed, Nov 17, 2010 at 12:55 PM, Adam Green <140...@gmail.com> wrote: > > > >> Ryan: > > > > >> Shannon raises a lot of great points, but I'd like to hear more about > > > >> the issue of reselling data derived from a purchased stream. Right now > > > >> the TOS says that you can't resell data from the API. I've been > > > >> telling clients that eventually Twitter will decide to make money from > > > >> the API, and when that happens there would have to be a way to resell > > > >> what has been paid for. Now that you are selling access to the API, > > > >> which I strongly agree with, will you allow a free market to evolve > > > >> around that by making it possible for Twitter data retailers to grow > > > >> businesses, as well as wholesalers like Gnip? Please, say yes. I'm > > > >> hoping an Apple-style, control the distribution channel completely > > > >> mindset doesn't develop at Twitter. I'm hoping Twitter wants to help > > > >> the developer ecosystem turn into a true third party market. Letting > > > >> developers sell data or help clients sell data is essential for that. > > > > >> On Wed, Nov 17, 2010 at 1:27 PM, Shannon Clark < > > shannon.cl...@gmail.com> wrote: > > > >>> Looking at Gnip's website they have the "contact us for pricing" > > links - > > > >>> will Twitter & Gnip be making the pricing for the various levels > > public? > > > > >>> Will companies that license the data be allowed to, in turn, sell > > services > > > >>> on top of that data - i.e. will this spark a new generation of > > products such > > > >>> as Scout Labs (now Lithium) or other analytics tools which are built > > by > > > >>> companies who have negotiated for full or partial firehose access but > > which > > > >>> are then used by clients of those companies each of whom will > > configure > > > >>> different queries and searches to monitor? > > > > >>> And on a more technical level will Gnip and Twitter work together to > > make > > > >>> the transition for developers who might start building/testing a tool > > using > > > >>> Twitter's free API's but then later migrate to Gnip's commercial > > feeds as > > > >>> seemless as possible? Will the API calls etc be similar (or identical > > but > > > >>> with different URL's?) > > > > >>> And a further query - you emphasize that this is for "non-display" > > services > > > >>> - does that mean, for example, that an analytics tool built using the > > new > > > >>> Mentions feed from Gnip cannot display the underlying Tweets that are > > > >>> returned by that feed? This would seem to severely limit the value > > and > > > >>> utility of such analytics to many businesses (who might want to reply > > to > > > >>> many of those messages, might want to follow people on Twitter > > discussing > > > >>> their company/brand/industry/competitors, and in almost all cases > > will want > > > >>> to view the full Tweet w/rich metadata not just a summarization of #s > > of > > > >>> tweets etc.) > > > > >>> And/or would a business focused Twitter client - CoTweet, Hootsuite, > > > >>> Tweetdeck etc be able to offer (perhaps as part of a professional > > version) > > > >>> such enhanced Mentions feeds and display them within that > > application? > > > > >>> thanks, > > > > >>> Shannon > > > > >>> (I'm not an active developer at the moment but I am consulting some > > business > > > >>> clients on a range of social media tools and as analytics and the > > > >>> appropriate use of them is a core part of my recommendations I'm > > following > > > >>> these developments closely and look forward to I hope new competitors > > in the > > > >>> analytics space soon) > > > > >>> --------------------- > > > >>> Real Things -http://realthings.posterous.com/ > > > >>> Slow Brand -http://slowbrand.com > > > >>> Searching for the Moon -http://shannonclark.wordpress.com > > > >>> --------------------- > > > >>> cell: 1.510.333.0295 Twitter - rycaut > > > > >>> On Wed, Nov 17, 2010 at 10:09 AM, Ryan Sarver <rsar...@twitter.com> > > wrote: > > > > >>>> Dewald, > > > > >>>> The basic levels of all of the streaming APIs -- Spritzer, Follow, > > > >>>> Track -- will remain open, free and direct from us. Elevated levels > > > >>>> for non-display use will be served through Gnip. > > > > >>>> Hope that answers the question. > > > > >>>> Best, Ryan > > > > >>>> On Wed, Nov 17, 2010 at 5:44 PM, Dewald Pretorius <dpr...@gmail.com > > > > >>>> wrote: > > > >>>> > Ryan, > > > > >>>> > The Gnip blog post states: > > > > >>>> > [QUOTE]Twitter Decahose. This volume-based product is comprised of > > 10% > > > >>>> > of the full firehose. Starting today, developers who want to > > access > > > >>>> > this sample rate will access it via Gnip instead of Twitter. > > Twitter > > > >>>> > will also begin to transition non-display developers with existing > > > >>>> > Twitter Gardenhose access over to Gnip.[/QUOTE] > > > > >>>> > How does this affect the basic statuses/sample method of the > > Streaming > > > >>>> > API? Are you discontinuing it? If so, when? > > > > >>>> > -- > > > >>>> > 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 > > > > >>>> -- > > > >>>> 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 > > > > >>> -- > > > >>> 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 > > > > >> -- > > > >> Adam Green > > > >> Twitter API Consultant and Trainer > > > >>http://140dev.com > > > >> @140dev > > > > >> -- > > > >> 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 > > > > > -- > > > > 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 > > > > -- > > > Adam Green > > > Twitter API Consultant and Trainerhttp://140dev.com > > > @140dev > > > -- > > 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 -- 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
