Something wrong with this?

Yesterday we took a walk up the street to the shopping center to goto my mailbox at the UPS Store. As we walked up, we passed the local Boy Scout troop setting up their annual Christmas tree lot. Something seems quite ironic about that to me; Christmas trees require a lot of energy to harvest, transport to lots (and then homes) and then requires energy to recycle. I picture Boy Scouts doing all that they can do to help the environment; this doesn't seem like the right way. When I was a scout, my troop collected Christmas trees for recycling.

I'm not saying that the troop is doing anything wrong and know how strapped troops are for cash; I'm just saying that if you step back for a second, it just doesn't seem right.

(For the most part, I support what the Boy Scouts do as becoming an Eagle Scout is one of the things that really changed my life. There are some policies that I can't believe in, but I won't get into them now.)

Misleading/Wrong Release Notes

I was having problems installing Leopard Server on VMWare Fusion and posted to VMWare's forums a few weeks back. The response I got was that it was a VMWare bug and it would be fixed in the next update. Perfect, I'd just have to wait. So today, the update comes out with the following note:

Mac OS X Server (10.5.5 and earlier) cannot be installed in a virtual machine on the new Fall 2008 MacBook, MacBook Pro, and MacBook Air.
The Fall 2008 update to the MacBook, MacBook Pro, and MacBook Air requires a newer version of Mac OS X Server than the most recent version (10.5.5). If you encounter problems installing Mac OS X Server in a virtual machine on these systems, make sure your Mac can boot from the installation disc.

I downloaded the update and decided to try to install Leopard Server even though I had a 10.5.3 disc image and wasn't hoping for much. I went through the install process and was quite surprised to find that it worked fine on my Fall 2008 MacBook Pro.

So much for believing known issues/release notes!

The end of an idea

Ever since the iPhone SDK came out, I had planned to write ReceiptWallet for iPhone as it seemed like a logical thing to do. A few users asked for it, so I thought it was a good idea. However, today is the day that ReceiptWallet for iPhone ends. I've toyed with it for the last few months, but just don't have my heart into it as it isn't something that I see myself using. As much as I wanted to do this product to answer the needs of the public, it just isn't going to happen. I was going to finish it to get it out the door, but then I'd have a crappy product that wasn't my best work.

In addition, there are some serious issues that have to be overcome before it could become usable.

First off, the camera on the iPhone can't focus close enough to get quality images. As you can see, these pictures are awful. I'm not sure they would be acceptable for any form of documentation. (Who knows, maybe the IRS would accept something that can't be read.)

Second off, the synchronization mechanism with the desktop would not be seamless; you would have to launch ReceiptWallet on the iPhone, click on sync and run ReceiptWallet on the desktop. Apple has not provided a plugin mechanism (like Palm did with HotSync Manager) for third parties to sync data.

Third, I'm not happy with the data entry mechanism. ReceiptWallet on the desktop uses combo boxes to allow you to type a few characters and then a dropdown menu shows everything close; nothing like this exists on the iPhone.

The future may change things with ReceiptWallet for iPhone, but ending this today takes a huge weight off my chest and will let me move on.

Securing Open Directory on Leopard Server

Awhile ago I wrote about how insecure Open Directory was on Leopard Server. I was not the first person to have discovered this, but apparently no one has found a real workaround. I did find information on how to secure it, but then you can't use Directory Utility to properly setup the machine. After much head bashing, I have completely given up on securing individual components of Leopard Server. It would appear that the only way to secure it is to use a VPN, turn on the firewall to block all, but VPN traffic, and set Open Directory and iCal Server to NOT use SSL. Turns out there are bugs in the iCal (CalDAV) server that don't handle a GoDaddy SSL certificate.

It still amazes me that an experienced software engineer like myself can't secure a server designed for small business that don't have an IT person. Maybe this will work in Snow Leopard.