Ryan, What happens to users who are at 'restricted track' or 'partner track' levels for streaming API access? Also, what is the time frame for moving from twitter to Gnip and would twitter be contacting users who will no longer be able to access Twitter API and refer them thru migration process?
I am still not clear about usage of 'non-display' term. From your example - would current or future B2B tool vendors offering services similar to Radian6, ScoutLabs, have to go thru Gnip to get Twitter data? -- Thanks, Devang. On Wed, Nov 17, 2010 at 3:25 PM, Ryan Sarver <rsar...@twitter.com> wrote: > Shannon, good questions -- answers inline below... > > On Wed, Nov 17, 2010 at 12: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? > > They will be published if they aren't already and they are being > widely reported through RWW and other outlets. One of the main goal is > transparency > > > > > 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? > > Companies can definitely build and sell products based on the analysis > of the data. A major market for this move is the Social Media > Monitoring (SMM) market and we expect that to grow. > > > > > 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?) > > Gnip is offering an exact proxy of our API so that the payloads look > the same. You would just need to change the endpoint you are pointing > at and (I think) your credentials for accessing the endpoint > > > > > 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.) > > This is really about B2C vs B2B. We expect that the dashboard will > want to show tweets and we support that, but it should be for a > commercial audience that wouldn't be interested in running Twitter's > promoted products. Let me know if that doesn't make sense. > > > > > 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? > > This deal is all about elevated access. CoTweet and Hootsuite are able > to operate on the freely available, basic APIs. If however, Hootsuite > wanted to get larger volumes of data for analytics, they would want to > reach out to Gnip. > > Hope that answers your questions. > > Best, Ryan > > > > > 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 > > > > -- > 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
