Just my luck. As soon as HN took a little while to load for me, I knew that someone would mention it in this thread.
I made hn-api understanding that scraping HN is frowned upon, but also hoping that programmers wouldn't do dumb things with it. As I [said][1], I minimised the number of requests hn-api makes to HN.
In the readme, I say that hn-api is unofficial and unauthorised. I also tell people to be gentle with making requests to HN. Is there some other action I should take? Ideally I'd like to keep my work up, but if pg tells me to take it down, I will.
hn-api only makes one request when it gets stories or one request when you get a user's karma -- that doesn't seem like too much. I knew there was a velocity check on IPs (and that I was making an unofficial API), so I made it as light on HN as possible.
> It's not like you need karma updates every time you do a request to the API.
Obviously.
When a request is made to get stories from HN, no HackerNewsUser objects are created (and thus, no karma gets updated). hn-api will only update karma when you, the coder, make a HackerNewsUser object or call the HackerNewsUser.refreshKarma() method.
Like I said -- one request when it gets stories or one request when you get a user's karma.
HN is also running really pretty slow today.