Kyle Brady: A Blog

I’ve been purposely avoiding writing anything about Google’s new OpenSocial project. Why? Because it had the potential to go in a few different directions and be used different ways, and I wanted the hype to die down before seeing what it’s actually worth. (If you’re totally in the dark, read this and this, and about how it was hacked.)

The Hype

If you believe all the hype, this new initiative may be the end of “walled” social networks, meaning that users would put their data in a centralized location, and then distribute it as they wish to other networks and services.

Hello, Michael Arrington.

As I’ve mentioned before, this is a good idea in principle. Places like Ning, 37Signals, and LinkedIn (despite the fact that I hate Ning) are among the first major supporters of this, and are lauding it’s praises as if it’s the best thing since sliced bread. And the blog network (aka TechCrunch, Mashable, RW/W, etc.) is falling over themselves with self-promotional joy, except for the always-straight-shooting O’Reilly.

The Problem

Here’s the central problem: the hype is about “open data”, and yet OpenSocial is being used to create “applications” that can exist on any social network platform, not de-privatizing data. Who really cares if you can SuperCrotchPunch all your friends across 131 different social networks? No-one (except preteens and frat boys).

Also, these applications have apparently been hacked. It’s unclear as to whether this was Google’s fault or the individual network’s, but it is a problem nonetheless. I know I don’t want my data screwed with by some guy who figured out how the system works… do you?

How about “I VampireStabbed Your Mom”?

The Future

If you poke around the Google Code pages for OpenSocial, you’ll find something called “Data API”, which is labeled as “not released” and only provides documentation. But it gives insight into the true intentions of Google…

It appears that sometime in the near future, this “set of APIs” will be used for what everyone thinks it will (cross-network data), or at least be available for use. The companies/services that had access to these APIs before the general public may already be integrating the next release, but nothing’s been said.

The Final Countdown

Here’s how it breaks down: as it stands, OpenSocial is pretty worthless. Most of the “applications” on these social networks are stupid, childish, and totally worthless, so there’s no need to port them to other systems. In the event that Google does what it claims to be doing, aka “tear down [these] wall[s]”, then chances are it will be successful…

Um, yes?

But the question is will this be done with the lack of enthusiasm as other Google releases, or with the fervor of a true PR engine? The fate of the Internet’s data and Google’s dominance over search may depend on their next few dance steps.

Oh, and Facebook needs to be involved for this to be 100% successful. Which remains doubtful.

posted on November 7th, 2007 at 12:07 pm by Kyle - Comments

Tags: Code, Future, Google, OpenID, Programming, Social Graph, Technology, The Internet

“Twine” is a service that apparently does what I say over here.  I didn’t know of this company, apparently in secret development since 1998, but it is still the same idea.

However, they will have more ground to cover in an effort to beat the forthcoming Google centralized personal data API…

posted on October 18th, 2007 at 10:53 pm by Kyle - Comments

Tags: Future, Google, Microformats, OpenID, Social Graph, Technology, The Internet

I read a story just now about how a telecom company in France is going to provide all of their customers with an OpenID, immediately, without any action on the part of the customer.

OpenID, an open authentication system

In principle, OpenID is a good thing. But there are definitely better ways to “open the social graph.” Here’s a repost of something I wrote on Pownce [reference no longer valid] a little bit ago:

All this talk about microformats and the “open social graph” is all well and good… but how many places are going to open up their data? How many services are going to want o implement a centralized-server setup, and be the center of that wheel?

There is only one real solution: a big-name player in the industry has to step up, and take sides. Google is rumored to be creating a centralized social network database… where all those Web 2.0 services can pull things from (like your favorite movies, foods, hobbies, friends, etc), instead of typing them in 29 million times in different places.

There are only three companies who have the power and capability to do this:
Microsoft, Google, and Facebook (Yahoo is outdated, and no longer matters)

Microsoft isn’t trusted enough to be a part of this, so that leaves the battle between Google and Facebook.

On one hand, Facebook already has the most social network data on the most people, and has already opened up portions of that data. The next logical step would be providing a system of cross-referencing and caching that data through different sites.

Conversely, Google has the power and the money to destroy any market they see fit. Not only do they hold the sway of the search community, but also have data on many many people who use their singular Google Account for many services. They already have this database in place… they just need to expand it. They already have the functionality of access in place (Google Base), it just needs to be realized and publicized.

I’m hoping these changes come soon. I’m tired of hearing about OpenID being the future. I’m tired of re-typing my data. I’m tired of how useless, but highly flaunted, microformats are in a closed environment. I’m tired of small, next-to-meaningless services wanting to be THE hub for all your data.

We need this. We need it now. And if “the Internet” is to become what everyone of Web 2.0 wants it to be, outside of the nerd fiefdom, it needs to be done right… perfectly, the first time.

posted on September 24th, 2007 at 5:20 pm by Kyle - Comments

Tags: Code, Hmm..., Microformats, OpenID, Social Graph, The Internet