Nope. Deletion time after a thread falls off the last page is set to 6 months.
Also I have the deletion code disabled still. The problem was never that it wasn't working, it's that whenever it auto-prunes a thread it throws up "internal server error"'s to the person loading the page.
It's not a huge deal, since it correctly deletes the thread and the user can just refresh the page, but we don't really need threads to be pruned right now so I'm not in a hurry. We're still barely at about 50% disk space usage.

But I think the errors are cause by poor database design anyway. Something about removing a table causes the server to freak out a bit.
When I started making this site it was supposed to be a testbed, so I kind of just started doing whatever worked instead of researching best practices.
I wasn't aware of how bad an idea it was to make dynamic tables, where tables are created/deleted as threads are created/deleted. Turns out it causes a lot of issues.
The best practice is to have fixed tables. I've had some people recommend that to me here too, but the fact that we have dynamic tables makes it extremely difficult to change the database structure right now (another reason to use fixed tables instead).

I haven't mentioned this yet, but I've actually been rewriting the server again. This time with a focus on handling the database correctly, and in a way that will make changing the database easy as pie.
At that point deletions should just be a matter of removing rows from tables, instead of removing entire tables.
A number of other things should also be streamlined in the new code too.

Woah, Taba-tan replied fast!

>>2
Fine by me. There's no need to delete anything.
I like that this is sort-of an archive.