Home | Recent Changes | Search | Log in

Cross Networking Madness: Strategies for portability of data and identity and how to leverage them to grow your community.

Issues with data portability:

o Need format that is both meaningful and useful
o Competitive issues with providing data portability, may benefit the competition

o Not as well adopted as you would think

Multiple interfaces to integration.

Identify your integration target.

o Synchronous vs. asynchronous integration

Twine – You can post everywhere.
Hellotext – Repeat post for you.

Reasons for interest in this issue:

How to drive traffic to your site and montetize your own community.

Facebook works well as an acquisition channel, but not a great way of generating revenue.

Clay: You need to go out to your customer, can’t wait for them to get to you.

Example of good cross-networking. Ebay Storefront API. It made it very easy to integrate your own site with eBay. Their usership exploded when they published their robust storefront API.

Not a whole lot of optimism in the immediate viability of data portability and identity. Lots of talk, but no great action.

Everyone felt data portability was too immature.

Michael Staton didn’t feel that integration of his app with Facebook to be worth it in terms of ROI so far.

Data portability is perceived as risky. Organizations large orgs are particularly risk averse.

Tip: Don’t be creepy.

Trust can be an issue with shared ids. You may need to gain trust before you can swap info.

Need a leader to get OpenID going.

Key Takeaways:

1) Is the holy grail, but a chimera?
2) Different forms of profitability - low tech (rss) vs. hi-tech
3) Be a good neighbor - share data to get data
4) ROI models are uncertain

Page Last Updated: Jun 19 2:02pm by hvirga@forumone.com


Log in - Socialtext v3.1.0.0