>if you want people to really test it for you, you should make >the code available. people will find bugs for you a lot faster, >and won't have to fill up your site with test posts.

(1) This project was never started or continued with the idea of releasing the source code publicly (ever). As such, the code is highly specialized and is in no way, shape, or form viable for release to the public (currently).

Making it so would not only require an entire re-write of the code as it is now, but would also (probably) require an instruction manual to written and released alongside it (were it to be released publicly).

It is heavily rewritten to include the use of php alongside the native perl implementation, and also makes heavy use of .htaccess rules and a separate file system to handle different things (for instance, archive views vs live thread views, categories, proper link forwarding when a person enters a URL into the form submission, etc.)

It's not that I don't want to release the source; I just don't have the time (personally) to do the entire rewrite necessary to make that happen.