>>3919 (OP)
I should have made a separate thread at this point but if you have a look at the bug thread you'll see I'm working on actually reinstalling jschan on the appserver to unfuck whatever it is I've done to the current installation. It should not be a complicated process but I've been experimenting on a separate server while hitting the books on nginx/git/node.js etc so I can be reasonably sure that I won't just fuck things again in the future. Once I've got the process ironed out I'll announce the downtime at least a week in advance and the site will be updated for the db migration, the jschan install will be wiped while retaining the db/files, and the latest version of jschan will be installed and hooked back up to the db/files. I will have a full backup of the server at the ready so I can fully revert to the beginning of the process if needed.
Yes I know it's taking forever work has been insane up until recently.