Obviously things have happened to this site. Let me just mention the most important here — the rest you can figure out for yourselves.

First of all, there’s a new kid on the blog. Allow me to introduce Steffen (his profile will return 404 until he publishes something), whom many of you already know. I’ve been hoping to have him join this blog for a long time now, but my old blogging software wasn’t rigged for it. I’ve finally gotten over myself and installed a standard platform, which I’ll get into in a second, but first: Welcome to the blog Steffen, I hope you’ll like it here.

Now, this new standard platform I mentioned, is (as you may have guessed) WordPress. At first I was a bit hesitant to move to such a platform, but with the ability to easily write plugins, widgets, modify templates and stuff, there’s really no reason not to. Setting up WP was a breeze and the migration from my old system to the new was a matter of 2 really simple PHP scripts — one for converting the old entries and one for the comments. A million thumbs up to the WP developers for making something so accessible, simple and easy.

Apart from a new blogger and a new platform, other things have changed a bit around here. When migrating to WP, there were some decisions to be made. One of those were whether or not to move stuff like phpCF and DynDNSupdate to the new site and I ended up deciding that DynDNSupdate wasn’t worth moving, since I haven’t coded on it for years (and I don’t intend to ever again) and it didn’t appear to be all that popular anyways. So DynDNSupdate is gone. phpCF survived though, mainly because I still code on it every now and then (and I have some huge improvements planned) and because it actually has a future (where DynDNSupdate only had a past — not even a present).

Now, no migration of this sort is without problems and I’ve tried my best to make sure that no old links are broken and stuff, but should you encounter any problems, let me know.

On a side note, the site isn’t the only thing that has had an overhaul (1 and 2).

Turns out - after a little more testing - that the DynDNSupdate binary for Windows is broken. Sorry… It’s been removed from the site. It’ll be back when I’ve found a solution to the problem.

While you’re waiting for it you could listen a little to some of the music on the site. ;)

I’ve rewritten DynDNSupdate entirely in Ruby and reset the version-numbering. The old version will still be available, but won’t be developed any further. The new version of DynDNSupdate can run on a huge variety of platforms, such as Windows, Linux, BSD, Mac OS X etc., whereas the old version was limited to run in Bash environments.

Improvements:

• Runs on most OS’es now - thanks to Ruby
• Respects a selected number of HTTP redirects (default: 10)
• Doesn’t require lynx anymore
• Easy install through RPA
• Binary (.exe) for Windows

Packages:

• RPA package: dyndnsupdate_0.1.28-1.rps (No longer existing.)
• Windows Binary: dyndnsupdate-0.1.28-1_win32_exe.tar.gz (Taken offline because of breakage.)
• Source: dyndnsupdate-0.1.28.tar.gz

What is RPA?

RPA stands for Ruby Production Archive and is a brilliant package-manager written by Batsman for handling Ruby applications and libraries at production level. If you’re using Ruby and yet don’t know RPA, do yourself a favour and check it out at: http://rpa-base.rubyforge.org.

Well, I finally got to write a little on DynDNSupdate, which has resulted in version 0.8. (And it’s now in subversion as well… Mmm… Subversion…) You can see the changes in DynDNSupdate. (Thanks to my good friend HarryV for the idea for the -s option.)

Enjoy! (No! No top 3 (or 5) this time.)

I just wrote a nice little program to keep ones dyndns hosts updated (both after reboots and in general). It’s called dyndnsupdate and is a Bash-script (so it only runs on *nix or Cygwin). More info is in the README in the package.
Get it here: dyndnsupdate-0.7.tar.gz.

Enjoy!