...a case for separating 'i/o' and 'network'
facebook's service is designed to syndicate content. it needs to own your data to push it out to the parties that the service is designed to serve.... this is because it is both a content host, and a network. it actively takes your information and p ushes that data out to your friends. as mark explained in a blog post --
"when a person shares something like a message with a friend, two copies of that information are created—one in the person's sent messages box and the other in their friend's inbox. even if the person deactivates their account, their friend still has a copy of that message. we think this is the right way for facebook to work, and it is consistent with how other services like email work."
that is one way to build applications, but it isn't the only way...
because we only handle the input, access, and ouput of content and have no associated 'index' or 'network' we simply don't face the same issues that facebook must wrestle with about data ownership -- the ownership parameters are totally clear in our case, we don't own any of the content being placed in our service, end of story.
so, what does it all mean....
when you want to 'share' something on drop.io you are not making and distributing copies, instead you are simply passing on links which refer back to your drop. so, if you want to share content you own and have placed on drop.io, you can simply push out a link to your facebook network via facebook connect, or via our twitter integration, or via email, rss, and a bunch of our other 'output' options.... none of these 'networks'/distribution channels end up 'owning' or needing to duplicate anything more than url pointers.
we hope that this becomes the option of choice in the future, where data i/o is divorced from distribution networks instead of being conflagrated.... in an always connected world, there is no reason for i/o and 'network/distribution' to be encapsulated in the same entity, as it clearly only causes problems...
the model of content hosting and distribution of the future allows you to keep your information somewhere you can flexibly exert total control, and push out links/pointers across the social and searchable web. that way, when you are done you can efficiently close shop, and you don't have to worry about others needing to 'own' your content to be effective.
i see this as a big part of the future of privacy and dealing with the control of massive amounts of asymmetrical data in a massively accessible environment