Take back the data – Part 5

I have decided to stop using cloud services and move all my data back to my own computers. Part 1 listed all the cloud services that I use. Part 2 described how I plan to replace my cloud services with my own web server. Part 3 covered the process of setting up the web server hardware and software in more detail. Part 4 covered SSL, setting up my own email server, and the backup system.

This conversion has been an interesting experience: I have learned a lot of details about web servers and Linux that I only knew in abstract; I knew that there was a lot of good opensource software out there, but this project has really brought home how much is out there and how good some of it is; I have been reminded how desktop applications can be so much better than web applications, and of how polished and easy to use modern web applications are.

I love having a local website that is reachable from the internet. My DSL upload rate is pretty slow, so the difference between dropping some files on a local network drive and uploading them is huge. I am looking forward to moving my main website to my local web server. (We will have to improve our upload speeds to support chadweisshar.com and wsims.com)

I am enjoying having ownership of all of my data, but I am also feeling the burden of being responsible for keeping the data safe and the server running.

In the rest of this post, I will describe how I am using the web server and OwnCloud installation to replace all my remaining cloud services.

Continue reading “Take back the data – Part 5”

Take back the data – part 3

I have decided to stop using cloud services and move all my data back to my own computers. In Take back the data – Part 1, I listed all the services that I use. In Take back the data – Part 2, I described how I plan to replace my cloud services with my own web server. In this post I’ll describe the process of setting up the web server hardware and software in more detail.

Continue reading “Take back the data – part 3”

Take back the data – Part 2

I’ve decided to stop using cloud services and move all my data back to my own computers. In Take back the data – Part 1, I listed all the services that I use. The next step is to figure out how to replace them and move my data back. To replace the services that the cloud provides, I need to:

  1. Store my data locally
  2. Backup my data (ideally an offsite backup)
  3. Provide remote access to my data

The first part is easy. The second two are much harder because of how home internet service works.

Internet providers use dynamic IP addresses. Each customer gets a new address every few days/weeks. This is like having a phone but getting a new phone number every week. You could make phone calls to other people, but couldn’t really receive phone calls back because no one knows your number. With dynamic IP addresses, you can talk to other computers, but you have to start the conversation. The consequence of this arrangement is that you can’t really run a website from your home computer.

Broadband companies will sell you a static IP (like a permanent phone number) for a small monthly fee, but since very few people have a static IP addresses, software companies haven’t been motivated to make it easy to setup a home website. So, for most people, if you want to share photos or start a blog, you have to involve a third party like wordpress.com or facebook.

This is really too bad. The promise of the internet was that anyone could publish content that could be seen by anyone else. Now we have a few large companies that are in the business of publishing other people’s content and making money off it. Just like record companies and book publishers before them, many internet companies (Facebook, twitter, flickr, youtube, etc) make money by publishing the content created by other people.

But it didn’t need to be that way. There was really no reason that we couldn’t each have our own IP address and our own personal website. Windows could have made it easy to publish your own content to your own site. Finding and connecting to other people could have been as easy as looking up or sharing a phone number. But that isn’t how things turned out, and now it is quite a bit of hassle to setup your own website. I’ll have another post with a lot more detail about hardware and software setup, but here is the quick summary:

  1. Buy a static IP. We have DSL from CenturyLink and they charge $5 per month to have a static IP.
  2. Register your domain name and point it to that IP address. That costs about $10/year.
  3. Setup a machine as the web-server. This machine should be left on all the time. Most any computer will do for a personal website.
  4. Install apache or some other web server software on the machine.
  5. Keep the OS and web server software up to date, do regular backups, make sure the machine stays on and working.

Once you have a website, it is possible to replicate most of the services that are provided by the cloud. I am going to use software called OwnCloud. OwnCloud is a webapp (a program that runs on a web server) that provides a way to store files, contacts, pictures, music and calendars on your website and share them with just the people you want to share them with. Since OwnCloud is running on my own web server, no third party has access to my data.

Continue reading “Take back the data – Part 2”

Take back the data – Part 1

The recent closures of Google Reader and Catch have reminded me of the quote: “If you are not paying for it, you’re not the customer; you’re the product being sold.” Free services aren’t really free, we are just paying for them with our data instead of our money. If the “free” service can’t find a way to make money with our data, they turn into a pay service or disappear.

I was fortunate that both Google Reader and Catch allowed me to download my feeds and notes before they closed. I just had to spend the time to find replacements and transfer my data. Between these two closures and the revelations that world’s spy agencies are working really hard to monitor and record my data, I have decided that I would like to take back ownership of my data. Continue reading “Take back the data – Part 1”