It does have a rate limit, it's just very very high. I've hit it sometime when trying to download every single item since day 0. But it's very lenient, you have to run multiple threads downloading as fast as they can in order to hit it. The API is not hosted by HN/Ycombinator themselves. If I recall correctly, it was initially hosted by Firebase which is/was a company seed-funded by Ycombinator. It (Firebase) is now…
> It does have a rate limit, it's just very very high. I've hit it sometime when trying to download every single item since day 0. Interesting. The API README states: > There is currently no rate limit. I guess that's wrong/out of date. I wonder when that changed?
Ask HN: How does Hacker News avoid (successful) DDoS attacks?
21–25 of 25 posts
Re: Ask HN: How does Hacker News avoid (successful) DDoS attacks?
#22Re: Ask HN: How does Hacker News avoid (successful) DDoS attacks?
#23Earlier quoted context omitted.
It's one of the few places we can vent about HN without being reprimanded, rate limited and eventually banned.
does HN rate limit people?
Basically, the mods will tweak anything and everything they can to either increase the quality of your comments or decrease the damage they do, with banning outright as a last resort.
Re: Ask HN: How does Hacker News avoid (successful) DDoS attacks?
#24There are many services you can use that will filter traffic and prevent DDoS. It's relatively easy to shift traffic to them if there is a problem.
Lastly the content of HN is almost entirely text, high read, very low write. Nearly all writes are behind an account, signup can be protected by a captcha or turned off entirely. The architecture means that reads can be cached, and the caching, serving, and traffic layers (assuming they are there) can likely scale horizontally nearly unbounded.
Then hacker news is full of tech folks who would probably enjoy investigating a DDoS.
DDoSing seems high risk low reward.