We recently converted to HipChat at one of my jobs. Because we’re geographically distributed, we need a solid chat client to handle our internal discussions. We landed on HipChat after trying a bunch of others such as CampFire, Skype, GChat/IM. The thing is, it’s not any one feature that makes it killer for getting things done. It’s the combination of all the things, and how well they all work together.
For example, when you upload a file it’s stored at Amazon (S3), and is available forever, no matter what your client. That is rad. There are clients for any conceivable device, especially considering that there’s XMPP/Jabber integration, so you could even use your favorite chat client to connect in that way. As a bonus, the search is good, which you’d expect except that all other clients have non-existent or crappy search. That’s just a few examples, but in short there are no barriers to getting in contact with people and sharing stuff, which makes it ideal for distributed teams.
Also, there’s a API for it, which I love. I love it so much that I wrote two different interfaces to it. I wrote FMHipChat for posting from FileMaker, and I wrote a HipChat CLI (command line) client as well, mostly because I didn’t notice that there already was one.
There are some caveats to using the file, such as the fact that you have to get an API key, and import your group’s rooms before the thing works. But, you know, there are instructions on how to do that.
I imagine using it mainly as a notifier for the end of long script runs, but let me know if you’ve got some novel use..
If you’re like me (got this far? you’re probably like me.), then you probably wanna post to HipChat from some shell scripts every now and then. Say a CRON job that runs an
fmsadmin task, or something like that. So I cooked up a real nice client for that as well.
Similar caveats to FMHipChat apply - you need an API token, and you have to modify the script to use it.
Usage is pretty simple - type
hipchat -h for options.
Thanks for reading, and happy HipChatting.