powdahound

Thanks! Initially created this when getting HipChat spun up on AWS. :)

Creator here. Agreed! I don't recall how I decided this was the right domain at the time but I think the rare .info TLD made it easier for people to remember. Can't say I'll be using .info for future projects however...

Hey - ec2instances.info creator here. I only ran this for AWS and am not sure who may have run this Azure version, sorry!

I've found myself using myNoise (https://mynoise.net) more than music lately. It has a lot of very high quality natural sound recordings as well as a bunch of synthetic options.

I guess it depends how you define "walled garden", but HipChat is built on top of XMPP: http://help.hipchat.com/knowledgebase/articles/64377-xmpp-ja.... Facebook chat used to be as well, though I'm not sure if it is these days.

A bit off topic, but it'd be interesting to have a guild for the startup/HN crowd. I've been discussing returning to the game with a few tech friends and joining a like-minded group would probably make it a lot more fun.

Blizzard recently released a documentary in celebration of the anniversary: http://us.battle.net/wow/en/blog/16668523/world-of-warcraft%.... It shows some of their design and development methods as well as the impact that the game has had on many players' lives.

Reminds me of the "JSON Encodings for XMPP" specification. :) http://xmpp.org/extensions/xep-0295.html

Garret from HipChat here. The previous discussion on this topic made a lot of assumptions about this change, so I'd like to quote some additional detail from our help doc (http://help.hipchat.com/knowledgebase/articles/358098) before the same happens here;

  In order for an organization to access 1-1 chats occurring
  after May 27, 2014 or later, the organization will need to
  make a request by emailing support@hipchat.com. As stated
  in the HipChat-specific terms, the requesting entity must
  have consent from their affected users in order to obtain
  access to those users' 1-1 chat history. The typical way
  that an entity would have the right to access employee 
  communications is through the entity's employee policy.
  It is standard practice among businesses to state in their
  policies that the employer has the right to access 
  communications occurring on workplace systems. You should
  speak with your employer if you have questions about their 
  specific data access policies.

I did all this a few weeks ago but still had to wait a few weeks for my friends' iPhones to realize my number was no longer iMessage enabled. During that time they all had to "Resend as SMS" on their messages to me.

We all ended up on Google Hangouts in the end (the iOS app is nice!)

If you've signed a policy with your employer giving them access to data in the services they pay for, we will have access to provide them, just like they can with the email account they provide you (if they do). They won't be casually browsing your chats, as that is not a feature we provide.

Hey everyone - Garret from HipChat here.

I'm sorry for the way we presented this information. We definitely should have explained these changes more clearly, because they do NOT mean that admins can browse your 1-1 chats. Our blog has been updated with a better explanation: http://blog.hipchat.com/2014/04/25/hey-were-changing-our-ter...

If you still have questions or concerns, feel free to email me directly (address in profile here) and I can answer them or put you in touch with someone who can.

I've had success syncing my SublimeText config across machines using homesick (https://github.com/technicalpickles/homesick), but this looks pretty slick.

One issue with syncing configs using either method right now is that certain keyboard shortcuts don't make sense across OS types, and your font size may not work well at different monitor resolutions (especially retina vs non-retina). See http://www.sublimetext.com/forum/viewtopic.php?f=2&t=5135 for related discussion. If you could incorporate per-OS/machine config overrides into this it would be very handy.

It's definitely very bursty. On weekends and holidays things are much more quiet. During peak load we'll be in the hundreds/sec. Also keep in mind that chat messages don't actually make up the majority of the traffic we serve; it's presence information (away, idle, available), people connecting/disconnecting, etc. (I'm one of the HipChat co-founders.)

This is the island where Typhoid Mary (http://en.wikipedia.org/wiki/Typhoid_Mary), the first person in the US detected to carry typhoid without showing symptoms, was quarantined. There's a great Radiolab episode where they take a trip to the island; http://www.radiolab.org/2011/nov/14/, http://www.radiolab.org/2011/nov/14/typhoid-mary/

It's already public knowledge: http://en.wikipedia.org/wiki/Hyperloop

Hey - Garret from HipChat here. That support info is not correct, and I'll investigate. All you need to do is go to the billing admin area and select the option to cancel your paid subscription. The message there will tell you that you have 5 users and that it's OK to cancel.

Read you loud and clear. We are split across all 4 US-East availability zones currently, but its true that we are not multi-region - yet.

Fixed now - sorry about that. :)

We're working hard on it. If you'd like to get on the list early, and help us by providing some info, please check here: https://www.hipchat.com/firewall

You don't need to identify as "bot", just send a keepalive message (can be a single space, XMPP ping, whatever) every 60 seconds or so. You can also request no history when joining rooms (most bot frameworks do this). It's part of the XMPP spec as well. Our roster pushes are also as in the spec, or have you found an oddity we should correct?

Joining a room with your full name can be an unexpected requirement but it really aligns with the way we enforce names on our service.

We've been with Atlassian for almost a year now. I hope big initiatives like this Mac app show that we're still working hard on the core product. We've got some great stuff in the works, too.

It's in the works. Vote on this and you'll receive updates: http://help.hipchat.com/forums/138883-suggestions/suggestion...

The cost to setting up and maintaining your own server and emulating many of the more modern HipChat features (drag+drop file sharing, archived/searchable history, mobile push notifications) is not trivial. Most companies find it far cheaper to spend money on a service than roll their own in house (see also: GitHub, UserVoice, hosted WordPress, etc).

Also, nontechnical people are often not very comfortable using IRC/XMPP.

The gif issue was an Adobe AIR bug, so it's definitely gone now. It was incredibly frustrating having them break functionality that many of our users love, especially because it wasn't possible for us to work around the issue. Sorry about that!

Hey - Garret from HipChat here. We're still working on retina assets for some of the app icons, and haven't started on retina versions of the emoticons quite yet. Hang tight!

Similar story here, but in the late 90s. I used to print out TI-82 calculator apps/games and type them in by hand because my parents wouldn't buy the $60 connector cable. It was surprisingly fun. All my initial programming knowledge came from debugging the typos I had made.

Location: San Francisco, CA

HipChat (https://www.hipchat.com) - the chat tool used by the smart teams at Quora, Instagram, Tumblr, Wired, Uber and thousands of other companies. Also the people who put the Y U NO guy on a billboard on 101 (http://blog.hipchat.com/2011/06/23/a-tale-of-a-ridiculous-bi...).

We're a team of 5 working in Atlassian's beautiful San Francisco office after our acquisition in March. Currently seeking;

- An engineer interested in doing application development (desktop and mobile) for any combination of iOS/OSX/Android/Windows. We're moving away from AIR and our users are quite excited about it (http://help.hipchat.com/forums/138883-suggestions/filters/to...).

- An engineer knowledgeable in Python, PHP, and web stuff to work on our website and XMPP backend (Twisted Python). You'll also be working with Redis, CouchDB, and MySQL.

Since we're a small team inside of Atlassian, you'll have all the benefits and responsibility that working on a small team provides, but also the security and excitement of a larger pre-IPO company. Plus, working on a product that people absolutely love is a wonderful feeling.

Full details on our jobs page: https://www.hipchat.com/jobs

Here's the source for that one: https://github.com/mape/node-wargames

Native apps are definitely in our future. :)