FSTDT

Blogs

FQA #announcement forums.fstdt.net blog

I am posting this from my phone, so please pardon any terseness or errors. So was my last post, and it is awful. I swear to God I was not drunk. I just couldn't see more than three lines at a time. I usually don't write things like blog posts in complete sentences until after I have an outline of what I want to say, otherwise I will inevitably forget something. You can see how I forgot being coherent in the last post. (Edit: Back on my laptop. Now you can't see it much anymore, because I edited it. I'm cool with letting funny near-incoherence stand, but there was one part where I couldn't even remember WTF I was trying to say and couldn't make any sense of it.)

But I wanted to officially go say the FQA forums are back with us again and a part of FSTDT again!! They're still an independent part of FSTDT, though. I'm not a mod there — I just can't handle the forums and main site at the same time — so plz put questions about the forums there. Also be sure to behold the spiffy new logo.

I haven't forgotten about the FSTDT Awards. I've just been busy with other things too mostly work. I've also been babysitting my parents' dog and she's the most adorable thing. She won't be fucking still long enough for me to get a decent picture though. >:( Anyway, I'll verify the votes for the last round of the FSTDT Awards and announce winners either tomorrow, or barring that, some time within the next couple days after that.

OMG #announcement forums.fstdt.net blog

image

http://forums.fstdt.net/ !!

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 admin@fstdt.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]