I must be crazy to spend my precious free time on this, but I have recently become an editor to The Internet Speculative Fiction Database (ISFDB). My goal is to enter information about all my SF&F books into the database. I track my progress on this Wiki page.

So this is it - I am now officially a CAcert assurer. Starting the count from the moment I decided to involve myself with CAcert, it took me roughly 3 months, and 3 meetings, to achieve this, but I am sure I could have done it in one month if only I had been more interested in speed.

All things considered, I would say that it is really easy to get 100 trust points and to become an assurer. I could stop here and enjoy the benefits of the CAcert program so easily won - but I think I will now try to get the hard part done: Be an active assurer and raise my account to 150 points.

Although I will not benefit immediately from having 150 instead of 100 points, I think it is only fair when I try to support and strengthen the CAcert community through activities of my own. Let's see whom I can convince... :-)

Three guys from the Linux User Group Switzerland, Fabian, Marius and Christof, assured me on June 14th 2007, at the Central Starbucks in Zurich, while having a nicely iced coffee. This boosted my trust points from 45 to 100, immediately giving me CAcert assurer status! As a bonus, the LUGS guys let me start my new career by assuring them back in turn. Although they do not benefit from this (already being assurers themselves), it raises my trust point account by another 6 points (2 points per assurance).

On May 31st 2007, I met an Australian guy at his office in Zurich, where he assured and awarded me another 35 points on the spot. Thanks David! This brings my total up to 45 points, which is tantalizingly close to the 50 points required for personalized, 2-year-validity certificates. Let's see how long it takes to get the remaining 5 points :-)

After some difficulties with finding a suitable date for an appointment, I finally met Thomas, my first CAcert assurer on May 5th 2007. We met in the train while commuting to work/to a training course, and completed the CAP process in under 5 minutes. Thomas later awarded me 10 points, the maximum he had at this time. 5 days later, on May 10th 2007, the points were registered at cacert.

Have you ever created a self-signed digital certificate, or created your own pseudo Certificate Authority (CA) so that you could issue your own certificates? Have you done so because you did not want to buy these certificates from VeriSign or some other commercial CA for an exorbitant annual fee? Were you annoyed that web browsers and other client software displayed alarm messages when they encountered your own, "cheaply manufactured" certificates - thereby implying to users that those certificates are not to be trusted?

Enter CAcert, a CA that issues digital certificates for free!

While browsing through my pile of board games I recently re-discovered the old Go board that I used to play with many years ago. I felt an immediate rush of nostalgia and talked my wife into playing an 11x11 game with me. Her discouraging comment after the game went something like "@#*&%!!!", so I was forced to look for alternative playing opportunities. The result is a trial installation (link is now defunct) of the "

I have written a script that regularly updates a list with IP addresses that have committed one or another offence in regard to the network security rules on my Internet gateway osgiliath.herzbube.ch. If you are interested to have a look, follow this link (link is now defunct)

Created the Gimp script "Aqua Crystal Ball". The script can be used to create Mac OS X icons with a (surprise!) "Aqua Crystal Ball" effect.

AceXpander 1.1 is now a universal binary. To make this possible, the application has been completely re-implemented in Objective-C. As usual you can find everything on the AceXpander page.

Once again, this is not a feature release. Almost all of the new stuff has happened behind the scenes, e.g.

• a crippling bug in the intermediate release 1.0.2 has been fixed
• in the source tar ball you will find a couple of UML diagrams and you can generate source code documentation with doxygen
• the way how the unace binary is launched has changed completely