patrick.net

I'm actually a bit confused as to how nginx rate limiting works. Here are the relevant lines:

limit_req_zone $binary_remote_addr zone=ratelimit:10m rate=30r/m; # 30 requests per minute, to match robots.txt "Crawl-Delay: 2"
limit_req_status 429;
...
limit_req zone=ratelimit burst=10 nodelay; # commented out in dev, uncomment in prod!

I think I'm saying create a 10 mb memory area called "ratelimit" and limit each ip address to 30 requests per minute, but allowing up to 10 requests at once and not just delaying requests that exceed that 10 to match the rate limit.

"When the 'nodelay' parameter is set, requests that exceed the burst limit will be rejected immediately with a 503 Service Unavailable error, instead of being delayed."

@Patrick

For the link to the latest images, can you add the #footer param to it?

Because it is at the bottom of the last page of them where the actual latest image is.

@DemocratsAreTotallyFucked

Sure thing, done. Though I used #last because that's more consistent with how that image thread works. Oversight on my part not to have it there to begin with.

Patrick says

DemocratsAreTotallyFucked

Sure thing, done. Though I used #last because that's more consistent with how that image thread works. Oversight on my part not to have it there to begin with.

Cool! Just tested it. Works great.