REDACTED PENDING CONFIRMATION ABOUT SECURITY.


DO NOT TRUST LOCKS ON THIS SITE TO KEEP INFORMATION PRIVATE.

MORE
9/24 '14 5 Comments
Psst - this is a google-able public post with your real name on it, so you might want to ponder that.
Thomas Boutell 9/24 '14
The comment form doesn't say "this post is public" at the bottom, which is, I thought, a reliable tell for whether or not someone else's post is locked.
Sean M Puckett 9/24 '14
A lock is set on this post, which is the same as it was when I wrote it, so your privacy model and my trust in this site are both broken.
Dawn Keenan 9/24 '14
Removed lock after editing post.
Tom, either you fucked up in your statement above or you have to fix some shit yesterday.
Dawn Keenan 9/24 '14
I fucked up in my statement. I got completely turned around and thought the ABSENCE of a message when replying meant the post was public.

"Tom that is totally ridiculous, you built this site! You know it works exactly the way Sean said because you coded it!" Yes it is totally ridiculous and I have no adequate explanation for my behavior. My inadequate explanation, if you care to hear it, is that I was rushing around doing way too damn much this evening and didn't think through what I was doing.

Did I bother to actually try to access your post via a logged-out browser or in any other way double-check my statement before scaring the crap out of you? No, because I'm a dipshit.

I have had cause to regret it exceedingly. The time and effort that Sean and I put into making this site secure may have been ruined by my carelessness, even though the site was never actually insecure. This is maddening to me and it is my own fault.

I am profoundly sorry and will be giving twice as much attention to security matters in future.
Thomas Boutell 9/24 '14