Recent submissions

Comment · 5 years ago
Thanks! Initially created this when getting HipChat spun up on AWS. :)
Comment · 5 years ago
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...
Comment · 5 years ago
Hey - ec2instances.info creator here. I only ran this for AWS and am not sure who may have run this Azure version, sorry!
Comment · 9 years ago
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.
Comment · 12 years ago
Comment · 12 years ago
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.
Comment · 12 years ago
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.
Comment · 12 years ago
Comment · 12 years ago
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 [email protected]. 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.
Comment · 12 years ago
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!)

Comment · 12 years ago
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.
Comment · 12 years ago
Comment · 12 years ago
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.

Comment · 13 years ago
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.)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton