Developing Upwards

This was originally posted on my new website , where you can read the full post. Please subscribe to the new feed there to follow new things I write.   The most well known, yet still problematic, area of data ownership in our web-based world is all the data we keep housed "in the cloud" in the machines of the services we use every day. The contents of your blog at Tumblr The documents your company shares on Google Drive Your to-do list at Nozbe or Remember the Milk The music you've bought and listen to at Amazon All your family photos kept safely (you hope) on Flickr All of these services hold the information that is important to you, that you depend on, in many cases defines a large part of who you are (your writings, your photos, your musical tastes). How often do you plan for these services having a major outage? Or vanishing entirely and forever? Or suffering some kind of terrible data loss? read more at www.ironfroggy.com/on/web-data-ownership/owning-y

I haven’t burnt out, yet, but I can feel it coming. I’m not sure if this is something I can avoid, something inevitable, or maybe something I can soften the blow on and make a little less painful. I think there is a burn out on the way, and I’m going to at least be observant. Read the rest of my post at Medium

This is a repost from my new website . Please follow my new blog for future updates. What does it mean to "own" my data in a web-based world? I don't know what this means, but we should. Before the growing responsibilities of "The Web" is for us, owning my data meant the files sat on my own machine. It meant the files were in a format that was either human readable, or documented well enough that alternative tools could read it or convert it. It meant no vendor could die, or change its mind, and make my data useless to me. This isn't the case in the web today. read the rest of this post