Sometimes the app can perform actions quickly enough to trigger Lobsters' in-built spam throttling feature. In that scenario the response includes the Retry-After header that we should respect. OkHttp already has support for this AFAICT but it seems to not be triggering for Lobsters, likely due to a different HTTP status code being sent.
Sometimes the app can perform actions quickly enough to trigger Lobsters' in-built spam throttling feature. In that scenario the response includes the
Retry-After
header that we should respect. OkHttp already has support for this AFAICT but it seems to not be triggering for Lobsters, likely due to a different HTTP status code being sent.