Uh oh, no blog post for 4 days ... what's happening? Is madcat gone? Is there no progress to mention? These, and other similar questions might cross reguar blog-readers minds. Nothing could be farther from the truth though - as anyone can see from the timeline page in DevCenter, development activity is normal as usual. However, I'm bit tired of writing blog posts every night (they get rather boring after a while), so I'm doing longer, but more informative posts at few-days intervals nowadays. Anyway, the updates listing, compacted and re-formatted for your viewing pleasure:

• Introducing HydraLoad, a FireFox plugin which adds "Download with Hydranode..." to right-click context menu. Naturally, this allows downloading files using Http protocol with Hydranode, right from browser. Credits: wubbla. Download here.
• Introducing Resolver, asyncronous DNS Resolver API, which provides DNS resolution support. Credits: cyberz.
• Running out of disk space no longer corrupts downloads.
• Improvements on darwin port with new build system (builds and runs, but plugins are compiled wrong still).
• Semi-automatic binary snapshots are now available at http://hydranode.bytez.org. Still generated by hand due to some technical problems; the linux ones require GLIBC 2.3-based system (all modern distros should do).
• Now you can enable/disable log messages printing to shell via "log" command.
• Console now features proper SearchList
  

Today's snapshot r1685: Windows Linux Source

So, where are we? The release is supposed to happen in 4 days, Boost 1.33 release was supposed to be 2 days ago but they seem to be behind schedule. Since Boost 1.33 is a requirement for this release, this will most likely mean our release will slip as well. However, on the bright side, looking at ticket browser, we can see that we have 4 tickets open for 0.1.2, and 3 for 0.2.0, with one ticket overlapping (CGComm library is required by #43 and #2).

#8 is basically done, #44 as well, #45 is dependant on Boost release, which basically only leaves three things to do before release: extend libcgcomm, global searching, and use WorkThread for allocating disk space in PartData; all three of them are easy to implement. So basically, we'r looking real good already - there aren't any major bugs open to my knowledge, and we only need three easy-to-implement features for release :). And from the looks of it, it won't be 0.1.2 that gets out of the door, it'll be 0.2.0 :)

Madcat, ZzZz