Welcome to the new blog

As of today I’m officially migrating from my old personal blog at http://hecker.org/ and publicizing the new blog at http://blog.hecker.org/. (This new blog is actually hosted at wordpress.com, but I’m using a hecker.org subdomain in case I want to move it to another service or server in future.) Most of the posts on this blog have been Mozilla-related, and I anticipate that continuing; I maintain an intermittently-updated hobby blog at a different domain, but I don’t have the spare time to publish much other non-Mozilla stuff. If you want to see only Mozilla-related posts, subscribe to the Mozilla feed at http://blog.hecker.org/category/mozilla/feed/; if you don’t mind seeing non-Mozilla stuff occasionally you can subscribe to http://blog.hecker.org/feed/ instead. Finally, my Mozilla blog posts also get syndicated through planet.mozilla.org, so if you subscribe to the p.m.o feed you don’t need to subscribe to this blog’s Mozilla feed separately.

2 thoughts on “Welcome to the new blog

  1. Steve Lee

    Hi Frank, I was interested to see you have used WordPress as I’m considering moving over to a self hosted WordPress blog as well. So I was wondering how you found the hosted solution (and how you redirect) and if you had any hints from your experience. Did you hit any problems? Did you spend much effort customising it?

  2. hecker Post author

    I moved to wordpress.com because I didn’t want the hassle of administering WordPress on my own server (including doing database backups, applying security updates, etc. (Also, the server in question is running RHEL3 and thus can’t run any later than WordPress 2.0.) The restrictions on configurability, etc., on wordpress.com are a reasonable tradeoff for the reduced sysadmin burden; also I don’t care that much about customization since most of my readers probably use the feed as opposed to visiting the web site.

    Regarding the redirection, wordpress.com has an optional ($10/year) upgrade where you can have your wordpress.com-hosted blog be at your own domain name, e.g., blog.hecker.org in my case. I just set up blog.hecker.org as a CNAME pointing to hecker.wordpress.com, and they handle the rest. If you want to do the same trick at a top-level domain (like my other blog swindleeeee.com) then you can just have the domain configured to use wordpress.com’s nameservers.

Comments are closed.