Do plan on supporting node 0.5.x?

the onMessage callback gets passed a channel that can be used to reply to the message, but does not provide a way to uniquely identify a user, or get their info, like their mention_name and jid. (If you're wondering how I might need these, there are a number of cases, including needing to send the jid to another app, "mentioning" a user in a response to get their attention, and replying privately to a user to send a command in a chat room.)

I suggest that the callback receive the same user object that exists in the roster array.

The current way of setting message callbacks isn't very friendly since you always need to validate the message before continuing:

bot.on('message', function(channel, from, message) {
  if (message !== '!chuck') {
    return false;
  }
  // !chuck stuff..
}));

In addition, EventEmitters don't give us the flexibility of adding RegExp and complex conditions to our binding.

New API proposal

bot.onConnect

Triggered when the bot successfully connects.

bot.onConnect(function() {

});

bot.onMessage

Triggered by channel messages.

bot.onMessage('!chuck', function(channel, from, message) {

}));

The first argument can be either a String or a RegExp.

bot.onMessage(/^\!weather ([0-9]+)$/, function(channel, from, message, matches) {

}));

The result of the .match are returned as the 4th argument.

bot.onPrivateMessage

Triggered by private messages.

bot.onPrivateMessage('!chuck', function(from, message) {

}));

The first argument can be either a String or a RegExp.

bot.onPrivateMessage(/^\!weather ([0-9]+)$/, function(from, message, matches) {

}));

The result of the .match are returned as the 4th argument.

bot.onPing

Triggered whenever the bot pings HipChat (roughly every 30 seconds).

bot.onPing(function() {

});

bot.onError

Triggered whenever a XMPP error occurs.
This will automatically trigger onDisconnect.

bot.onError(function(errMessage, stanza) {

});

bot.onDisconnect

Triggered whenever the bot disconnects.

bot.onDisconnect(function() {

});

bot.message(targetJid, message)

The bot.pm will be removed and combined into bot.message.

The function will auto-detect the target-type and take the appropriate action of sending the message to the channel or via private message to the user.

bot.reply(message)

Within a callback you can use this.reply which will send the message to either the room or the person depending on the type of event.

For instance, if the callback is triggered by onMessage, this.reply('test') will send the message to the room.

If the callback is triggered by onPrivate, this.reply('test') will send the message to the person.

Can wobot be updated to allow installation with Node >= v0.8.0? The series is pretty far along now.

https://github.com/cjoudrey/wobot/blob/master/lib/bot.js#L14

This does not change the public API. Errors will still be emitted as error to the user.

I just tried installing wobot on to my Raspberry Pi today to play around with a new bot I've been tinkering with and I can't seem to install wobot at all. I run: npm install wobot and it says Error: failed to fetch from registry: wobot.

Here is the whole command:

pi@raspberrypi ~/Code/HipChatBot $ npm install wobot
npm http GET https://registry.npmjs.org/wobot

npm ERR! Error: failed to fetch from registry: wobot
npm ERR!     at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
npm ERR!     at cb (/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
npm ERR!     at Request._callback (/usr/share/npm/lib/utils/npm-registry-client/request.js:136:18)
npm ERR!     at Request.callback (/usr/lib/nodejs/request/main.js:119:22)
npm ERR!     at Request.<anonymous> (/usr/lib/nodejs/request/main.js:212:58)
npm ERR!     at Request.emit (events.js:88:20)
npm ERR!     at ClientRequest.<anonymous> (/usr/lib/nodejs/request/main.js:412:12)
npm ERR!     at ClientRequest.g (events.js:156:14)
npm ERR!     at ClientRequest.emit (events.js:67:17)
npm ERR!     at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1256:7)
npm ERR! You may report this log at:
npm ERR!     <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR!     reportbug --attach /home/pi/Code/HipChatBot/npm-debug.log npm
npm ERR!
npm ERR! System Linux 3.18.11+
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "wobot"
npm ERR! cwd /home/pi/Code/HipChatBot
npm ERR! node -v v0.6.19
npm ERR! npm -v 1.1.4
npm ERR! message failed to fetch from registry: wobot
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/pi/Code/HipChatBot/npm-debug.log
npm not ok

Anyone else seeing this or am I just crazy?

https://github.com/cjoudrey/wobot/blob/master/lib/bot.js#L14

i.e.

this.on('error', function() {
  this.disconnect();
});

This will allow users to override the behavior.

In message events, from is the nickname while in privateMessage event's it's the jid.

Hey,

I'm attempting to use an https.method call in my code (to get Airbrake exception information), which doesn't work with v0.4.6 of node, and requires v0.5.3

However, wobot v0.3.0 explicitly states it needs < 0.5.0, is there a gigantic dragon I will need to slay in order to get the thing to work?

Thanks,
Luke

Within a callback you can use this.reply which will send the message to either the room or the person depending on the type of event.

For instance, if the callback is triggered by onMessage, this.reply('test') will send the message to the room.

If the callback is triggered by onPrivateMessage, this.reply('test') will send the message to the person.

Looks to be a result of the node-xmpp module:

/Users/dbrito/skynetwork/chat-bot/node_modules/wobot/node_modules/node-xmpp/lib/xmpp/session.js:127
  this.connection.send(stanza.root());
                              ^
TypeError: Object   has no method 'root'
    at Client.Session.send (/Users/dbrito/skynetwork/chat-bot/node_modules/wobot/node_modules/node-xmpp/lib/xmpp/session.js:127:30)
    at null.<anonymous> (/Users/dbrito/skynetwork/chat-bot/node_modules/wobot/lib/bot.js:66:19)
    at wrapper [as _onTimeout] (timers.js:252:14)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Here is my code:

bot.onConnect(() => {
    console.log('Connected');
    bot.join('[email protected]');

    repl.start('slackbot> ').context.b = new BotApi(bot);
});

bot.onMessage(/test/, (channel, from, message, matches) => {
    console.log("message:", from, matches);
});

bot.onPrivateMessage(/hello/, (from, message, matches) => {
    console.log('pm:', message);
});

A private message fires the onPrivateMessage callback, but a normal message does not. I am able to connect and authenticate just fine. what am i doing wrong?

Ugh. Wrong git. Sorry.