I am not sure if it has fallen off the radar or if it is an honest oversight but we can't seem to get an explicit description of the throttling guidelines.
Core issues like this are critical, especially for library developers, and care should be taken to be as explicit as necessary to clearly define the guidelines.
Case in point:
My lazy loading library uses a gateway that is cached and throttled.
If the throttle limits are calculated globally, I will return a common gateway from the gateway factory that all requests are routed through, resulting in a max of 6 requests per second from my IP to your IP.
if the throttle limits are calculate per endpoint, I will return a distinct gateway for each endpoint, resulting in a max of N * 6 requests per second from my IP to your IP.
This is why it is important to be as explicit and detailed as necessary in order for a reasonable person to be clear on the guidelines.
casual documentation of core issues that can result in systemic failure of libraries and/or banning of IP/Keys is not responsible stewardship.
And if there are those that think I am just being contentious, let me assure you that I and several other professionals are very wary of building anything on top of this API due to the lack of professional response to mission critical issues such as this.