According to some founder stories we've heard, uneven workload is one of the major causes of drama. Colour us pre-emptive.

Very nice, and quite a bit of fun.

My only objection is with the TOS: while I can sort of understand defamatory and libelous (even these rule out most of the fun), I have issues with "inaccurate". Does not leave much wiggle room, does it?

Very nice. Simple, clean design and does what it says on the tin.

I am now also aware that there seems to have been a transient error between Hyderabad and my Linode. It's back up now though.

We named our daughter Ada after her, hoping that this would serve as a reminder of what you can achieve through curiosity and passion.

Apparently in due observance of the ALD, she just sleepwalked for the first time.

On Tue May 22 20:03:29 EEST 2012, all I get is a page with navigation and a greyish pattern background. Could not figure out what to do with it. This is with Chrome and FF on a Mac.

Seems fairly usable atm. A few observations: there is an XSS vulnerability as you probably learned by now. Also, there was a moment when someone was submitting content and it appeared under my nick "bpfh".

Other than that, kudos for a simple well-functioning chat.

Thanks. Those two security issues are fixed now. It was nice chatting with you :)

> > Also, there was a moment when someone was submitting content and it appeared under my nick "bpfh".

> Thanks. Those two security issues are fixed now.

You fixed one way of nickname duplication, but so long as you allow arbitrary utf-8 strings, there are all sorts of non-printing characters to use. You should really get a list of everything to filter. I don't have any experience with node.js, so I don't know if anyone has written a library that does it.

This is my weekend project, scratching a personal itch and addressing some of the complexity in HR tools I'm used to seeing.

The stack consists of Rails, MongoDB and nginx, and represents my first public-facing service with that stack. Along the way I wrote a JQuery plugin for managing a dynamic number of fields in a fieldset which I might throw on GitHub if there's interest.

Whether it be due to Anonymous or load from newly released hit games, PSN has been awfully flaky lately. Usually when PSN returns with a helpful integer error message, I hit Twitter and #psn to see if it's just me.

Frustrated with this, I took a few hours and wrote http://isthepsndown.com/. Obviously it's pretty useless at the moment, PSN being down wholesale, but I am hoping in the future it would save a few clicks whenever PSN barfs again.

Why force a click to see the result? Seems like a good way to ensure you get bogus data.

Good question. That's why I threw in the Haven't Tried option, but you might be right.

He is right. I would remove the "Haven't Tried" option and reposition the elements so that the status report is prominent and the option for user input is secondary.

Just implemented this change, and I find it much improved. Thanks.

Now the next thing would be to figure out appropriate network metrics to monitor the PSN server. I suppose portscanning Sony would be considered a bad idea though.

Donated.

Donated

Curious coindidence – I was thinking about this the other day, wading through Gibson's _Neuromancer_. The novel, just like earlier Stephenson fiction, paints a not-too-distant future entirely dominated by "Nipponese" brands and cultural artefacts. _Neuromancer_ was published in 1984. A lot has changed ever since.