github/hubot — comment on commit fd0887f5c0d71557c307004e587b19757a330c1f
File:  line 0
By Mange:

> > I would still opt for escaping all characters in case Talker ever changed rules.
>
> Nah we won't.

A project like Hubot shouldn't have that assumption built-in. It's like a XML-parser assuming no invalid documents will be opened. It's not like it's hard to just escape all of them anyway, thereby avoiding problems.

Besides, the bot could be configured with one nickname while the Talker user had another (they aren't tied together) and the regexp will always base on Hubot's nick, not the Talker user's nick. Anyone configuring their Hubot instance to use Talker runs a risk of having this bug explode on them when they start it up.

> Even if its a quite common problem, I don't think there is any built in method for that.

I know. I used a common snippet circling around the web. It's one of those less nice parts of JS.