Skip to content

Data Hosting vs Data Portability

A friend sent me a link to a recent post by Brad Templeton, Data hosting instead of data portability:

    A data hosting approach has your personal data stored on a server chosen by you. (You might have that server right in your own house, or pay for hosting services.) If you pay, that server’s duty is not to exploit your data, but rather to protect it. That’s what you’re paying for. You can have more than one (with different personas, if you like) but for now let’s imagine having just one.Your data host’s job is to perform actions on your data. Rather than giving copies of your data out to a thousand companies (the Facebook and Data Portability approach) you host the data and perform actions on it, programmed by those companies who are developing useful social applications.

I find data hosting appealing and would like to shift towards hosting my own data as opposed to having my data hosted elsewhere. It's a matter of making it practical though.

For instance, I'm a big fan of Flickr because it makes it so easy to have my photos taken care of. But ideally, I'd like to host my own photos and directly control how people access them. I'd do that if I could build a good repository and layer services on top of them — just like Flickr. But Flickr has an economy of scale that I don't have — it can solve that problem and provide the solution to many people.

Now, it's possible that we can solve that problem too and sell and/orr share it to lots of people so that they can do more of their own data hosting. Is that a business that I would want to be in?

Post a Comment

You must be logged in to post a comment.