I thought this bug fix warranted a blog post. So as a few of you have noticed, using some clients the webuser was getting kicked off whenever the operator used a non-ascii character. The webusers were able to use non-ASCII characters fine, but the operators were being restricted to ASCII.
This problem is at least partially fixed (in that I am unable to reproduce it), but there may still be issues. Essentially our logging system was setup in a way that didn’t support logging messages containing international characters – so whenever the system stopped to log a harmless error message, it was crashing the chat session.
I’ve implemented a good first pass of a fix, but I have a feeling there are a few race conditions that could still occur. In any case, I’d consider it completely beta worthy