Hi Eric - I've been looking through your docs, and I can't see how you suggest one gets Twitter approval - Do we just e-mail Alex and pass on his (hopefully) positive e-mail to you?
Thanks Nigel On Thu, Oct 2, 2008 at 7:10 AM, Eric Marcoullier @ Gnip <[EMAIL PROTECTED]> wrote: > > Hey all, just wanted to let you know that Gnip 2.0 rolled out > yesterday and we're now pushing data as well as notifications. This > means that you can tell us who you care about on Twitter and we'll > push to you their tweens in real-time. You no longer have to build a > poller (and thus, no throttling concerns). Additionally, we're now > pushing the complete public timeline to Twitter-approved parties. You > can read more about it here: > > http://blog.gnipcentral.com/2008/09/30/gnip-20-is-here/ > http://www.techcrunch.com/2008/09/30/gnip-20-launches-with-a-business-model/ > > Here's some more in-depth info. Please reach out if you have > additional questions. > > New features: > > * Full Data: It's no longer "Hey, fredwilson just tweeted. Go > query the API to get the data." Now it's "fredwilson just tweeted; > here's the data." Data consumers are no longer required to build > pollers for any of the publishers pushing data into us, they just give > us an endpoint and we push the data to them in realtime. > * Complete public data streams for Twitter, Digg and Delicious, > SixApart and others: You are bound by the TOS of the publisher, of > course, but now you don't have to beat the crap out the publisher to > get all the data. Since Twitter doesn't yet have a TOS, we're > requiring that interesting consumers get approval from Twitter before > we'll send the feed to them. > * Expanded Filters: Previously, there was only one filter, called > a collection, and it was based on username (essentially, send me > notifications whenever these hundred, or thousand, or hundred > thousand, people tweet, or digg a URL or bookmark something on > Magnolia). Now, with expanded filters, you can also create a rule > based on tags/keywords, and in the future we'll be adding filters > based on URLs and GIS locations. > * Outbound XMPP: Previously, if you wanted Gnip to push > notifications to you, it was strictly REST-based. We've added XMPP; > just enter a JID and we'll push to that XMPP endpoint. In the future, > we'll continue to add support for additional incoming and outgoing > data protocols. > * Pricing Structure: We're taking a first cut at a freemium model > for data delivery. If you want to build your own pollers, then we > want to help make you more efficient and releive stress on publishers > and that will always be free. However, if you would like Gnip to take > on all the "shipping and handling" of data, then there's real value in > that and we'll charge for it. > 1. Up to 10,000 rules for each data provider (a rule is an > element in a filter; a person or tag tracked) > 2. Starting at 10,000 rules, we charge $0.01/provider/month > -- essentially, $100/month to start > 3. It caps out at $1,000/month for a specific publisher, > regardless of whether you're tracking 100,000 rules, 1,000,000 rules > or getting the complete public feed. NOTE: If you track 9,000 names > on Twitter and 9,000 tags on Delicious, you won't get charge a cent. > If you track 6,000 people on Digg and 6,000 tags on Digg, you'd get > charged $120/month. > 4. We're still figuring out at what point an all-you-can-eat > plan comes into place. Beyond a certain number of publishers tracked > ($10k? $20k? 30K?) it's time to just say "here's the data, enjoy it > all." > 5. Anyone who is non-commercial or pre-funded will get fees > waived. If someone gets funding, we'll switch them to a commercial > relationship. > 6. The goal is to enable people to have plenty of space to > try out new ideas, integrate up-and-coming publishers and generally > increase the entropy of data around the web. When someone creates a > valid business idea using Gnip's data delivery services, then > everybody wins. > 7. LASTLY: Billing is not in place and likely won't start for > at least 30 - 60 days. We're just being exceptionally clear on what > we're thinking so that developers can make informed choices about > working with us. >
