Handling Feature Requests

Uservoice (e.g. Safari140) looks like a great way to manage - or better to get managed - user requests. Like digg users vote requests up or down. In the end you'll know how to "please" your crowd with reasonable expenditure. OK, it depends on the difficulty of the top requests too.
Please note that you have to pay for Uservoice.

FFView 0.9.10 [update], TriTag 0.8 Intel

Time to get ready for Snow Leopard

FFView 0.9.10:

• Polish translation by Parasit Hendersson
• Mac OS X 10.5 system log bug fixed

TriTag 0.8:

• Intel fixes & build
• Copy and paste

The bad news is that I was unable to create an Intel build of SafariToHTML due to limitations of Interface Builder 3.

[update] I forgot to bundle the help when I released FFView 0.9.10 - sorry for that. I repackaged the release so feel free to re-download the file.

Versiontracker

I didn't know that CNet bought Versiontracker until I tried to update FFView's version-information.
The problem I see - and that is why I opt not to update the info - that you have to allow CNet to host your file. While this sounds convenient, this also means that things like redirecting the user to the latest version, and download counters do not work.

Google Labs & SmartGrid

Vint Cerf message is clear: The SmartGrid development process needs to be more open - like Google Labs:
Where the smart grid meets the Internet
Sounds reasonable. Especially when you consider how many (costly) work-groups already exist within the unwieldy IETF.

32bit or 64bit Kernel

Type: ioreg -l -p IODeviceTree | grep firmware-abi

"EFI64" means that you can boot a 64-bit kernel - not that you have to. After all, 64-bits apps will just work fine in Snow Leopard.