I hope some way will get implemented to interact with the rate limiting implementation from code. The rate limit currently pretty much killed the daily Flag-war stats visualization, and while it might be possible to fix it (not quite sure yet) by implementing rate-limit awareness in the underlying library, I will most definitely need a way to communicate about rate limiting metrics with the rate limiting implementation, that currently just starts sending HTTP 4xx responses.

A number of questions to help me get a handle on this thing:

1. Is there an API planned for querying rate limiting metrics for a node?
2. When using JSON-RPC batches, how does that affect rate limiting?
3. Where in the tool stack is rate limiting implemented?

I hope a good answer to these three questions might help me get things on track to get the @pibarabot daily flag war posts up and running once more.

Oh, just a thought: It might be a food idea to implement something like a ratelimit_api.get_current_ratelimit_window_size() API call and add it to the APPBASE API documentation. That way client libraries could easily be made rate-limit aware, and maybe the impact could be mitigated by such an API feature.