I am presently in the process of relocating to NYC.  My usual set up is not at 100 percent so development of Battle Blog is currently on hold.  The latest version is of course posted with a completely up to date setup text file.

You can read more about this ongoing personal transition at my personal blog, an exhibition of Battle Blog itself.

Battle Blog 1.30, which includes a fix for that rather glaring SQL injection vulnerability last month, has been posted. Feel free to download it.

There's an entire history of posts explaining what Battle Blog is but unfortunately they were toasted due to said vulnerability, and, my inept attention to backing up the SQL database at least ONCE in awhile.

So, the quick of it is, Battle Blog is a classic ASP blogging engine. It started as a direct attempt to build a blogging platform that people could control content listing by voting content up or down on articles. Digg went online months after I posted the first version of this thing, and the concept of voting content up and down at a website was then popularized. Even so, Battle Blog hasn't taken off in that direction even though the democratic control functions are clearly visible, but this has more to do with the adoption and penetration rate of Battle Blog, which has been sparse. Serious bloggers seeking to stick with the mainstream have a vault of more uniform blogging platforms to choose from (like WordPress for example).

In actuality, Battle Blog appeals more to die-hard classic ASP bloggers looking for a blogging engine that will "do the trick" in a scripting language they are comfortable with. Most everyone who actually implements a Battle Blog is a classic ASP developer who winds up applying their improvements and/or customizing its behavior. Ergo, the many forks of Battle Blog. However, that's cool and I totally encourage it. I just can't support it, so read the docs for my limitations on support.