(Windows) Api.Rule.34.xxx constantly spitting out "Details limit reached (HTTP 429). New try."

[WonderCrown]

Bug description

When browsing rule34.xxx, even just for one to two pages maximum, grabber stops loading images. I've got an API key and everything, but it just doesn't

When browsing rule34.xxx grabber will give up on loading images part way through. My API key says I can load 60 images every 60 seconds, but even with grabber set to requesting 30 images at a time, it still locks up. The only thing in the logs is "Details limit reached (HTTP 429). New try."

Steps to reproduce

1. Go to api.rule34.xxx
2. Load any character, series, whatever
3. Browse around for awhile, until the images stop loading.

Expected behavior

Rule.34 not to stop loading images. This seems to be a new problem with grabber too, one that makes it impossible to browse rule34 while using Grabber.

[mistyrosetta]

This is happening due to the Rule 34 API limitations, which clearly works against scrapers like Grabber, therefore there's no fix for this issue.