FQA is merging back with with us and will be the FSTDT forums again! It'll take us a few days, but we're making this happen, When everything is ironed out, I'll be adding a forums link back to the top of this page. Contacting whoever owns the Reddit now and telling them we don't want it anymore, if none of you object to that.
In other news, I've got stack trace error pages back on. Stack traces basically say what code was being executed and what was stored in relevant memory locations at the time an error happened. Useful for figuring out what happened and fixing it if necessary. So if you catch an error, do kindly select everything on the error page and copy it, then paste it in an email and shoot it my way at firstname.lastname@example.org I will very much appreciate it. For a while, I had the server and FSTDT code set up to set up to automatically email me stack traces, but that got annoying real quick and was sending me stack traces frivolously.
[aside](Yes, I double checked to make sure I didn't compile a debug build of the code. That would flood me with even more frequent and detailed errors, and the debug symbols used to provide this extra information slow down performance pretty heavily. The FSTDT code running on the server now is a Release build with stack traces in enabled, something admittedly unusual but it is useful and worth the slight hit to performance.)[/aside]