Over the past year we have spoken with many companies and
entrepreneurs throughout the ecosystem who need easier access to more
data. In particular, companies building analysis and non-display
products have asked us for greater volume and coverage. Our
partnership with Gnip is built to address this need. Gnip will focus
exclusively on creating products to meet the existing and emerging
demands of companies creating non-display products. Check out Gnip’s
blog to learn more and to see details about their initial Twitter data
products: http://blog.gnip.com/gnip-twitter-partnership/.
Many of you may wonder what this means for elevated access and
whitelisting requests. Our default levels like Spritzer, Follow and
Track will not be changing, and will remain free and available
directly from Twitter. Companies and developers are encouraged to
begin development with these free APIs, available at
http://dev.twitter.com/pages/streaming_api. This does affect companies
wishing to create products which analyze Tweets and do not display
Tweets to end-users. Moving forward, we will begin to encourage these
companies needing elevated access for analysis and non-display
products to work with Gnip to find the right data products for their
commercial needs.
We’re excited about this partnership, and the support it offers the
data analysis and non-display market. You can learn more about the
details and Gnip by visiting http://gnip.com/twitter. Please let me
know if you have any questions about how this affects you and your
products.
To contact Gnip:
web: http://gnip.com
email: in...@gnip.com
twitter: http://twitter.com/gnip
Best, Ryan
Best,
--------------
Edward H. Hotchkiss
http://www.edwardhotchkiss.com/
http://www.twitter.com/edwardhotchkiss/
--------------
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
> --
> 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
>
"A mathematician is a device for turning coffee into theorems." - Paul Erdos
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.
--
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev
I have no idea what Gnip's final prices will be. If they are
exhorbitant, Twitter will either die, or they will give wholesale
status to multiple vendors and let the market figure out the wholesale
price. I think they are smart enough to choose the later. The big
thing, the REALLY BIG thing, is that I just used the word price twice
in relation to Twitter. That means people will pay for Twitter stuff.
That means developers can get paid for Twitter stuff. Hooray! I like
getting paid. I don't mind paying others if it means I can also get
paid. As long as everything is free, nobody gets paid.
Don't you want to get paid for your work?
> --
> 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
>
--
"A mathematician is a device for turning coffee into theorems." - Paul Erdos
Quoting Dewald Pretorius <dpr...@gmail.com>:
On Wed, Nov 17, 2010 at 12:27 PM, Shannon Clark <shanno...@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
As to the second part of your question we are setting the pricing as
to ensure that their sole position isn't exploited. With that being
said, you might find the products to be expensive, but we feel this is
premium data and we're mostly focused on consumer facing businesses
where the business model is promoted products and the data is free to
developers.
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.
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.
As I've already noted, I don't see the economic / business sense in
paying a monopoly middleman for downsampled Firehose when the full
Firehose is directly available via negotiation with Twitter. IMHO, if
you've got the brains and infrastructure to create social media
monitoring business value from 10% or 50% of the Firehose, it's easy
to scale that up to 100% of the Firehose. If you don't, well, you're
one of the 95 percent of businesses that fail because *you* made a
wrong decision.
While I haven't paid much attention to the "social media monitoring"
market recently, what I've seen for much of 2010 is consolidation -
big companies like IBM buying smaller ones with *solid* business
models. What I *haven't* seen in social media monitoring / analytics
is "small nimble startups" becoming successful with "minimum viable
products".
Social media monitoring is a difficult business to be in, *especially*
at the data rates Twitter delivers and the "unnatural" aspects of
Twitter linguistics. The sales cycle for social media monitoring tools
is long and arduous, and, IMHO, Facebook, Flickr and YouTube data are
immensely richer and easier for marketers to explore and exploit than
Twitter data.
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb
> Every search engine, social network, blogging platform, content aggregator,
> and to a certain extent, every used book store and used record store...
Except that digital content producers can block search engines if it's
in their economic interests to do so. I'm not sure how that's working
out in "Murdoch vs. Google", but at least it's been examined. ;-)
For that matter, some "news organizations" have imposed strict rules
on how and when they may "use" Twitter.
Tom
Sent from my iPhone
Companies have leveraged Twitter’s open API to analyze and report on
conversations and sentiment across the network since its inception.
These products have been indispensable in helping brands, marketers
and businesses engage with their customers on Twitter. This is an area
we want to support more fully, and today we are excited to announce a
partnership with Gnip to develop and market data products specifically
for these analysis and non-display companies. Gnip will sublicense
access to our public Tweets to developers interested in analyzing
large amounts of Twitter data.
Over the past year we have spoken with many companies and
entrepreneurs throughout the ecosystem who need easier access to more
data. In particular, companies building analysis and non-display
products have asked us for greater volume and coverage. Our
partnership with Gnip is built to address this need. Gnip will focus
exclusively on creating products to meet the existing and emerging
demands of companies creating non-display products. Check out Gnip’s
blog to learn more and to see details about their initial Twitter data
products: http://blog.gnip.com/gnip-twitter-partnership/.
Many of you may wonder what this means for elevated access and
whitelisting requests. Our default levels like Spritzer, Follow and
Track will not be changing, and will remain free and available
directly from Twitter. Companies and developers are encouraged to
begin development with these free APIs, available at
http://dev.twitter.com/pages/streaming_api. This does affect companies
wishing to create products which analyze Tweets and do not display
Tweets to end-users. Moving forward, we will begin to encourage these
companies needing elevated access for analysis and non-display
products to work with Gnip to find the right data products for their
commercial needs.
We’re excited about this partnership, and the support it offers the
data analysis and non-display market. You can learn more about the
details and Gnip by visiting http://gnip.com/twitter. Please let me
know if you have any questions about how this affects you and your
products.
To contact Gnip:
web: http://gnip.com
email: in...@gnip.com
twitter: http://twitter.com/gnip
Best, Ryan
--
> --
> 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
>
--
Is "Spritzer" still 1% of the Firehose? Since the status IDs are no
longer sequential, the previous "obvious" sampling algorithm - "status
ID mod 100 == 0" - no longer will work.
> Spritzer is currently at 1% of the Firehose, but as the docs say it's
> subject to change without notice
Given the Snowflake algorithm, how can a program consuming Spritzer
determine whether a Spritzer rate change has happened because
a. People are tweeting at a different rate, exclusive-or
b. Twitter has changed the proportion of Firehose being sent to Spritzer?