If you learn anything from the problems arising from using Web 2.0 tools, you learn that you can’t rely on just one solution. As beguiling as “one ring to rule them all” concept is, you have to find various approaches.
For example, it was a no-brainer to realize I needed a backup of this blog. So, while I did have a few backups of partial content hosted here at Around the Corner, I’m now adding a few more…and updating the ones I did have. WordPress blog platform (read this nifty tutorial) is the easiest to work with, so I’ve setup a few of those.
- Self-hosted WordPress – hosted at www.edsupport.cc/mgblog – This is a WordPress install I manage and maintain. If I’d kept this up to date, I wouldn’t have complained that much when Google disconnected Around the Corner on Blogger.
- WordPress.com – hosted at gtips.wordpress.com – This is a WordPress site I setup years ago when my son expressed an interest in authoring “game tips” for games he was playing. Although he never wrote more than one blog entry, I did successfully use WordPress.com to mirror ALL blog entries on ATC here at mguhlin.blogspot.com. Unfortunately, WordPress.com has a few issues (advertisements, content embedding restrictions) that I find objectionable. However, those are easy to overlook in a backup site. I used WordPress.com to completely backup the blogger version of ATC, then exported the content from WordPress.
- Posterous.com – mguhlin.posterous.com – My final backup attempt included Posterous.com, what everyone says is an easy to use blog on the go tool. I found it easy until I tried to import my Blog into it…the import failed about 5 times before I decided it wasn’t going to go anywhere. So, I decided to export from WordPress and then import into Posterous…and with a 20 meg file, the operation timed out. So, I’m not entirely sure that this will be a worthwhile backup, it’s evident that Posterous IS trying to get the job done…you can see a few entries have successfully been imported in.
Just thought I’d share what I’m doing, especially since Richard spent some time exploring this in detail on his blog. As he points out, recent issues do get us to think about data portability.