Pardon the brevity of yesterday's post, my cylinders were running on a foggy four hours of sleep so I kept it short. This one has more heft :)
The biggest examples of social data silos today are Facebook and to a lesser extent Twitter. Social media platforms create business value from large user membership, attention, social link sharing, and the healthy ecosystems of apps that improve user and network value. While Facebook and Twitter support methods for exporting data, they have limited access and closed formats (I can't hack a new twitter API, their data is closed). Social silos write their own rules for how to access and potentially move their data. It's all good, they created the infrastructure and software, so why shouldn't they control the faucet to their data stores?
Savy users have known for a while that there's a data portable way of accomplishing nearly everything with a distributed open social web (search is tricky) . The hard part is setting standards to enhance interoperability. The idea is to shape user social data so that it natively has the ability to migrate to any servers who support open standards. The standards provide a common language between (self hosted) social hubs. This natural extension of the net is becoming the defacto social web. With high likelihood Facebook, Twitter, and other portals will follow suit but not until they have to (distributed monetization takes some work). The social web has already lead to a diversity of social communities where users converse with folks on other networks without worrying about which service is most popular today (non roach motel/data silos). As technology advances, it approaches invisible. At any time users are free to walk away without losing links to friends or business contacts (speaking of which, its time I move my gmail and phone contacts into an open format I maintain and copy, and maybe my gmail data too).
If you think of Google as just another silo, you're partially right. I should be able to easily migrate my email from gmail (I haven't tried). And Orkut is an older social network popular in Brazil isn't built on open standards, but DeWitt Clinton and his colleagues are working hard to make all our Buzz social data portable (many of the standards Buzz is built on are part of something we're working on at Victus Media, which I'll cover below).
The Push/Pull of Streams & Feeds
There's a mad scientist cooking up something wonderful at Victus Media, and it's not me. Well I'm cooking up stuff too but it's not as awesome (front end, link tagging stuff). Tyler the chief Hacknical Wizard of VM, has concocted a master plan of great vision. I assisted in design, as we hashed the idea out Thursday, but the architecting is his responsibility. We decided we both want to move away from a limited service format (twitter tool) to a web service and we have a groovy way to do so.
To accomplish this while maintaining relevance is no small feat. An example of relevance lost from mixing social feeds is the @ symbol. In Twitter it maps directly to a user account, but that user may be someone else on Buzz (they use email as a unique identifier). Fortunate for us, semantic entities are service agnostic so we can link information and people among many services. Also certain services have dedicated functionality so we'll use a meta tag (bit string) to activate other functions on our side. One example is link scraping from microblogs and semantic tagging those urls. Another example is using oembed to show mini video clips from sites like YouTube. I believe Disqus has implemented something like this in their comments. I'll try to convince Tyler to writeup a guest post on the push/pull architecture he's building (woman getting angry at my ignoring her). We may even open source the feed juggling if it makes sense.