Google has been saying for awhile now that it supports open source and the Open Web. In many respects, they’ve acted as if they really do. Google Wave and Google Buzz are two examples that illustrate how Google is pushing for a more open Web. Now, there’s OExchange.
The concept here is real simple. Here’s a basic explanation:
“To put this into perspective, the goal of OExchange is to lower the overhead of integrating with social sharing services,” says Messina. “So, rather than having to investigate and learn about a bunch of different sharing protocols and APIs, you should only need to learn about OExchange to cover a large number of services.”
Sounds good, doesn’t it? Like OAuth, which allows website owners to provide one authorization login across multiple protocols – for instance, you can login to your site and Facebook through one password instead of needing to know both passwords – OExchange would allow website users to share content across multiple platforms. But a social service would need to support the OExchange protocol in order for it to work.
Just imagine, if Facebook, Twitter, Google Buzz, StumbleUpon and your favorite social service all supported OExchange then your website users could share your content with all of those services at one time. It’s a win-win-win situation for everyone.
Google Buzz already supports OExchange. I think other services will follow. Perhaps you should support it too. What do you think?