ReadWriteWeb

Gnip: Grand Central Station for the Social Web

Written by Marshall Kirkpatrick / July 1, 2008 9:02 AM / 15 Comments

gniplogo.jpgPing, ping, ping! That's the sound made day and night by the new social media technologies rapidly proliferating around the web... and the machines are getting tired. Polling for updates to user data streams, wishing they spoke the same language and dreaming they knew which accounts belonged to the same people across different services.

Sounds like a great opportunity for an infrastructure provider, doesn't it? Enter the sexiest infrastructure provider we've seen in a long time: Gnip. Venture funded and built by exited MyBlogLog co-founder Eric Marcoullier, Gnip wants to serve as the grand central station and universal translation service for the new social web.

What Gnip Does Now

The primary service that Gnip offers at launch today is to capture user data updates from any web application and then serve up the very latest information to anyone else who requests it. Your application doesn't have to ping Flickr, YouTube, etc. etc. every few minutes and ask "have any of our users done anything on your individual service?" Now with Gnip, Flickr (a launch partner in fact) can report user data updates to Gnip, which can then pass that data along to consuming parties, along with data from all the other social media services of interest.

It's about scalability and decreasing latency to near zero. It sounds like a great idea.

What Gnip Says it Will Do Within 90 Days

The sexiest features are still in the works. Here are just a few plans that the company has disclosed so far.

Protocol switching You want to communicate instantly with an application using the IM protocol XMPP/Jabber but it only publishes and consumes RSS feeds? Gnip will stand in the middle and translate so each end of the transaction can send and receive data in the format it wants. Hot!

Standardized metadata Different services publish user data with different titles for the various fields sometimes. That makes it hard for the robots to know what exactly is being said. Gnip is working with visionary developer Chris Messina to create a meta data standardization process, for social bookmarking activities in particular. Gnip will consume feeds from user bookmarks on any service, then make publicly available those same feeds appended with another version of the same data but in a standardized format. That's a really big deal because it makes interoperability possible.

Identity discovery Right now it's hard for services and for users to tie multiple social media accounts together from around the web. Gnip will let users provide usernames or emails and then check to see where else those identifiers are being used. That's a solid sounding idea.

All of this will be free, none of it will be public-facing. Application developers will tie into Gnip and there may be premium services available eventually, like translation of data into a particular vendor's proprietary template.

Is This Too Centralized?

Gnip's Eric Marcoullier acknowledges that the centralization here is worth questioning. Two primary concerns come up: scalability and privacy.

As far as scalability is concerned, that's the name of the game here. If Gnip can't scale with fantastic uptime then there's no service. The company has been working with Pivotal Labs, the strike force hired to fix Twitter, since Gnip started work.

When we asked Marcoullier about privacy, he emphasized that Gnip is only working with publicly available data right now. The company might venture into user authentication and private data, but that's "a whole other can of worms," he said.

No doubt Google is already indexing most of the information that Gnip will be transmitting, but we can't help but think that Gnip will be in a uniquely powerful position to do some mining of anonymized user data and social graphs. That could lead to very big money but it could also raise some concerns on the parts of users. Gnip says they aren't worried about monetization right now, they just want to build out their service and add value to the market place.

That may be the case, but we think that Gnip has a whole lot of potential to deliver huge value to the applications leveraging it, to the backers financing it and ultimately to all the users of the emerging class of social web applications. We love this kind of stuff.



2 TrackBacks

TrackBack URL for this entry: http://www.readwriteweb.com/cgi-bin/mt/mt-tb.cgi/4334

Comments

Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts

  1. Very cool idea. Dave Winer blogged about Twitter needing something like this to "get back into the pink" just yesterday: http://tinyurl.com/4w49rg

    Posted by: Josh Bancroft Posted on FriendFeed   | July 1, 2008 9:21 AM



  2. Protocal? Surely not...

    Good concept though - just like Winer was saying this is the sort of thing that Twitter could couple with to build some scalability.

    Posted by: Matt Rutherford | July 1, 2008 9:36 AM



  3. whoa!...

    Posted by: Barbara K. Baker Posted on FriendFeed   | July 1, 2008 9:41 AM



  4. a gloried ping server. wooohooo....or not.

    Posted by: Google FanBoy | July 1, 2008 10:05 AM



  5. Gnip? Where's the complimentary Gnop? (Hey they even copied the three rings!)

    Posted by: Rich | July 1, 2008 11:05 AM



  6. Saying that you are working with the people "fixing" Twitter when asked about scalability might not be a good thing.

    Posted by: Rob Blatt | July 1, 2008 11:23 AM



  7. Saying that you are working with the people "fixing" Twitter when asked about scalability might not be a good thing.

    Posted by: Rob Blatt | July 1, 2008 11:23 AM



  8. marshall - there is no grand central station :) it's grand central terminal

    sorry had to do it buddy!

    Posted by: allen stern | July 1, 2008 11:24 AM



  9. Saw this and immediately reminded me of Foundry Group's "glue" investment thesis. And behold, it turns out to be one of their portfolio companies.

    To do the really sexy stuff, Gnip /has/ to venture into the "other can of worms": private data. The reason being that data-portability extends beyond just flipping the on switch for your APIs and calling it a day. A broker in-between APIs is a vital player in the same sense database abstraction layers are prominent in app-dev today.

    Posted by: Q dub Posted on FriendFeed   | July 1, 2008 11:31 AM



  10. @ Q dub -- we agree that private data is a must going forward, but we don't want to hold up a good solution waiting for perfection.

    There are plenty of good people working on OAuth and we're hopeful that over time it will incorporate a cascading authentication model that enables us to work with private data transparently to the user. We're not going to offer a competing standard -- that way lies madness.

    Posted by: Eric Marcoullier | July 1, 2008 11:40 AM



  11. @ Q dub - good memory re: Foundry Group and Glue! And Eric's comment on OAuth at #10 is right on the money.

    Posted by: Brad Feld | July 1, 2008 2:07 PM



  12. Doesn't OpenSocial promise something similar? How does this compare/compete?

    Posted by: Sekhar Ravinutala | July 1, 2008 7:08 PM



  13. The words "single point of failure" come to mind...

    Posted by: Rick | July 1, 2008 10:05 PM



  14. But who is paying for this, the producers? the consumers? both? There is no information about this on their site.

    Posted by: Richard Cunningham | July 2, 2008 4:49 AM



  15. 1) Is this similar to Google's OpenSocial initiative?

    2) "Flickr (a launch partner in fact) can report user data updates to Gnip, which can then pass that data along to consuming parties, along with data from all the other social media services of interest." This sounds like "push email" but for the social space. Very nice.

    3) Somehow, FriendFeed reminds me of Gnip's efforts. What's the difference?

    Posted by: Alex Luft | July 5, 2008 9:58 PM



RWW SPONSORS


FOLLOW @RWW ON TWITTER

ReadWriteWeb on Facebook



TEXT LINK ADS