Forums return
I've just re-enabled the forums, now there is no webspace pressure. I managed to upgrade to the newest version of yabb and it managed to import all the old forum data. So hopefully if you registered it should just work still.

The reason I re-enabled them now is not that I think all discussion should occur here. I ususally check the Topfield forums more often than my own site so it's better to post stuff there. But I want to use the forums as a basic bug-tracker. People send me bugs and suggestions quite often but I either deal with it, add it to a list or forget about it (sorry, it happens!). So I thought that if people posted a bug in a thread (try to keep it one bug/request per thread) I could then keep track of it and also inform you when I had dealt with it.

Also, if the Topfield forums are down, like they were recently, it gives me a place to discuss problems etc like the recent grabber failures.

The forums haven't yet got a site button, but they are at: http://noates.com/cgi-bin/yabb2/YaBB.pl

Also, I think I finally worked out how to do a proper redirect from the bur.st/~cazlar domain to noates.com, but if you have a link using the old domain I'd appreciate if you changed it to noates.com

MacTF-EPG 1.2.2
I've been a bit lax in posting to the blog, but there's a new verion of MacTF-EPG up now. This fixes the problem that most (but not all) users were having with no data being downloaded by the grabber. Thanks to v8jlene who managed to find what had changed and updated the grabber.

While I was packaging up the new version I also changed the update mechanism to the Sparkle framework. This was a bit last-minute, but looks to be a really nifty way to update your app. It allows me to post a webpage for each upgrade and if you need updating you'll see what's new in a window, with the option to download it. Sparkle then seems to quit the app and restart with the new version. It also has some "always install new updates" features but these are very beta, so please don't enable them (I tried disabling them but haven't worked out how yet).

The best thing in my mind is that if there is an issue like last time where there is a data source problem, I can simply set up a fake "update" and users will be able to see a message explaining what the problem is. Then when I actally get the problem solved, I just add the download and everyone can get it. So I recommend letting the app check for updates (I'll make this a pref soon, now it just asks once).