19 comments

[ 6.9 ms ] story [ 46.0 ms ] thread
Ditto for me, 40 minutes later.
(comment deleted)
I appreciate the difficulty there is in keeping up with large loads of bandwidth, but if you're going to compare yourself to one of the most resource-intensive websites on the internet, you could at least handle HN traffic.
Still down, no cached version either. Womp womp. :\",
The site is back up. Sorry for the interruption.
If I enter a public Github repo and click on Gitualize, its taking forever to load. Don't know what is wrong.
I'm sorry to hear that. Can I ask which repo you are requesting so I can try to reproduce the problem?
Sorry. I checked in the Network tab of the chrome developer tools. I'm behind a proxy server. So it is not loading. No problem with the website or the application :)
ERR_CONNECTION_REFUSED as of right now :<
Still getting ERR_CONNECTION_REFUSED
Still the same. Waste of time...
(comment deleted)
Still down.
this is pretty cool. Sped through some good ruby engines that I follow and learned that the first 20 commits were tests. nice way to learn programming practices.