As Scott says, work on DasBlog is still happening and the project is getting ready for the very last ASP.NET 1.1 release before moving on to the ASP.NET 2.0 model and being fully compatible with the 2.0 runtime. You can run it on 2.0 today without any problems, but since the project has been committed to 1.1 compatibility so far, there were quite a bit of things that weren't possible to change.

Once the project switches over to be "native" on the CLR/BCL 2.0 (we're discussing the actual target framework version), I'll rejoin the effort and I already have several truckloads of new features or changes in the wait loop. You'll be surprised what that little engine will learn to do over the next several months.... ;)