Martin Ek

Having RoR/Django South like generated migrations would definitely take Sequelize to a whole new level.

Thanks! I'm a bit hesitant towards recommending Heroku for slack-irc though. Don't get me wrong, Heroku is great, but the fact that dynos are restarted once a day makes it...

Sorry, I completely missed this one. Sounds like a great idea, although it would probably require a bit of code to get it working smoothly. I won't have time to...

Definitely. Could implement something similar to [parseText](https://github.com/ekmartin/slack-irc/blob/master/lib%2Fbot.js#L136-L164), but for IRC -> Slack. Would you want to try sending a pull request?

Hi David! This sounds like a reasonable addition—feel free to send a PR if you have time!

If you export NODE_ENV as development you should see a debug log for each Slack message posted (i.e. `NODE_ENV=development slack-irc --config`). Then you can see the raw message that gets...

There's a test for that here: https://github.com/ekmartin/slack-irc/blob/master/test/bot.test.js#L268 You could try adding an assertion using the input message that produces the weird output, then removing `replace` statements from `parseText` until it...

Looking at the code of node-irc it looks like this should be handled already: https://github.com/martynsmith/node-irc/blob/master/lib/irc.js#L230-L237 Maybe this is a non-protocol event though, so it's up to each IRC server how...

It's supposed to append the number to the already existing nick though, not just replace it. See https://github.com/martynsmith/node-irc/blob/master/lib/irc.js#L234

It should set `self.opt.nick` to the correct nick [here](https://github.com/martynsmith/node-irc/blob/master/lib/irc.js#L37). If you're interested in debugging further you could put a few console.logs inside node-irc' code to see what it's actually sending...