11 comments

[ 3.3 ms ] story [ 30.8 ms ] thread
I noticed this and was pretty disappointed, the chrome extension and unread new comment number is the only sane way I've found to follow conversations. I also love using the site for finding stories.
Well sometimes good things happen from bad situations right? I've always wanted a chronological list rather then a hot list so the blocking helped me discover this today with this post, thanks! That being said hopefully this will be unblocked asap!
I've emailed pg, hopefully we can get back up and running properly.

pg, if you see this, I've updated my crawler to be fully compliant with robots.txt (my delay between requests was too low, even if the overall req/min was fewer than 2).

Can't imagine using HN any other way. I hope this is resolved soon.
Er I have had trouble accessing HN all day, is it for sure that the site has been legit blocked?
From the server:

    $ curl http://news.ycombinator.com
    curl: (52) Empty reply from server
You might have been seeing dns problems, per: http://news.ycombinator.com/item?id=3438134
(FWIW, this is what happens when you hit the rate limit autoblocking that HN has. Irritatingly enough, I have been blocked multiple times simply for opening Chrome and having it reopen my old tabs, most of which are from this site; once was for almost a week.)
The DNS servers are located at EasyDNS:

  Retrieving DNS records for news.ycombinator.com...
  DNS servers
  ns1.easydns.com [209.200.187.4]
  ns2.easydns.com [72.52.2.1]
  remote1.easydns.com [64.68.192.10]
  remote2.easydns.com [72.52.2.1]
  ns3.easydns.org [64.68.192.10]
  ns6.easydns.net [72.52.2.1]
they have been DOS'ed today (see: http://news.ycombinator.com/item?id=3438134), its a probable reason why hckernews isn't working.