HipChat releases native app for Mac

Post by billymeltdown » Thu, Feb 14, 2013, 7:01 PM UTC

dljsjr wrote: post #34

n9com wrote: post #19

I know people are happy as the infamous GIF bug is fixed, but seriously this is one of the worst 'beta' apps I have tried. This mac app has been in development for ages, then been in closed beta and now finally it's available to everyone to try. Our team just switched to the beta native app, and already found several critical bugs with the app within minutes. Sorry guys, this is really poorly put together and the num…

Philosophical question: Is it really a bad "beta", or has your preconceived notion on what a "beta" should be been radically altered by the sheer number of startups that throw the word around now? Gmail was in "beta" for about a million years, and was incredibly stable for most of that. I think it has become the allegorical metric these days. But I remember back in the late 90's and early 2000's when making the choic…

Post by lobster_johnson » Thu, Feb 14, 2013, 7:01 PM UTC

pbiggar wrote: post #50

lobster_johnson wrote: post #45

Earlier quoted context omitted.

And so you have set up Nagios and whatever to always include the appropriate recipients in the messages? Where do you centralize the information about who should be @-mentioned? Edit: Seems like a lot of noise if there are a lot of recipients (some of our apps or libs have 8+ people).

We dont do that at all, though I'm 90% sure the hipchat API supports that. What I meant was, when a team member wants to contact me personally, they put @pbiggar in front, and Hipchat will give me a notification for that, but not all the other messages.

Post by timtadh » Thu, Feb 14, 2013, 7:02 PM UTC

n9com wrote: post #43

spencerfry wrote: post #32

Earlier quoted context omitted.

What kind of bugs have you found?

There's a difference between a new beta and an app that has been in closed beta for months already and only today has been made available to the public. Just because it's 'beta' doesn't mean there should be obvious trivial bugs present. Just to run off a few issues we found within literally minutes of using the app: 1. Resizing window to a small size then making it large again causes the entire chat view to become ve…

Post by lobster_johnson » Thu, Feb 14, 2013, 7:13 PM UTC

plasma wrote: post #56

lobster_johnson wrote: post #45

Earlier quoted context omitted.

And so you have set up Nagios and whatever to always include the appropriate recipients in the messages? Where do you centralize the information about who should be @-mentioned? Edit: Seems like a lot of noise if there are a lot of recipients (some of our apps or libs have 8+ people).

HipChat has the concept of a "notify" flag for every message you send via the API. Notified messages make a ding sound in chat, flash the task bar, etc. For my HipChat setup, build logs are silent (and don't disturb anyone), but a notification that a deployment failed has the "notify" flag set to gain everyone's attention.

Post by easytiger » Thu, Feb 14, 2013, 7:18 PM UTC

potatolicious wrote: post #54

dreamdu5t wrote: post #24

Earlier quoted context omitted.

The account manager at my company takes offense to this. Sorry, but even "nontechnical" people have setup mIRC when they were 14.

HipChat is more than an IRC server - it's a fully searchable web-based chat archival system, as well as a file transmission and sharing app backed by S3. It's also fully mobile-compatible and will do proper message routing to multiple devices owned by the same user, as well as temporary message caching/retry if your device is unreachable when a message is sent. etc etc. The list goes on. None of it impossible to repl…