Ask HN: What does the Twitter/Datasift deal mean for developers?
So, I write for ReadWriteWeb and I've been paying pretty close attention lately to the situation with Twitter, API access, the API Terms of Service and the developer ecosystem. Earlier this week, Twitter announced a deal with DataSift (formerly TweetMeme) to sell access to Twitter info (including historical) at a price much lower than the full firehose access offered with Gnip. The access is based on search, comes with extra data from Klout, PeerIndex, Qwerly and Lexalytics.
(Here's our writeup of the announcement too: http://www.readwriteweb.com/archives/twitter_announces_fire_hose_marketplace_up_to_10k.php )
So, I'm looking for reactions and interpretation from developers on what this means for the Twitter developer ecosystem. Got one? Got some insight? Let's talk!
10 comments
[ 3.0 ms ] story [ 48.1 ms ] threadThanks, Doug
"This means that developers interested in building tools to monitor and analyze Twitter data can now filter Tweets from the full Twitter Firehose, using DataSift for non-display analysis."
http://www.readwriteweb.com/archives/twitter_puts_the_smack_... http://www.readwriteweb.com/archives/twitter_kills_the_api_w...
I'm Jud Valeski, CEO of Gnip (jud@gnip.com). So we're all running on factual data, apparently a problem these days,...
Twitter's value added resellers (e.g. Gnip and DataSift) must... - sell filtered data at no less than $0.10/1k Tweets consumed. Gnip makes this price explicit, whereas DS, apparently (I can't fully tell so check w/ them directly) rolls that number into their costs, making it opaque.
- sell only to firms who will not display the Tweets in "public".
- sell only to firms who will not programmatically re-syndicate the raw Tweets further downstream.
To simplify:
<total cost> = <data cost> + <processing cost>
<total cost> = <$0.10 * #tweets % 1000> + <processing cost levied by Gnip or DataSift>
Thanks, Doug