Caleb Cartwright

I appreciate everyone's willingness to share their feedback! However, I want to gently remind everyone that this issue is simply a poll with one specific question. This is just one,...

The [upstream API is rate limited at 4k requests per _day_](https://wiki.archlinux.org/title/Aurweb_RPC_interface#Limitations) which is a rather strict amount to begin with. For reference, we've received >18k requests for AUR badges in...

> https://github.com/badges/shields/issues/7863#issuecomment-1160834238 I don't feel like there's enough specificity in your question for me to be able to answer, and I don't want to make assumptions about what you're saying...

> but we run like ~20 servers so I'd assume we'd actually be well under their rate limits, assuming load balancing.. balances smile Also our staging server is rate limited...

Quite baffling indeed. Definitely something we should ask them about if/when we hopefully chat. We've seen other cases where a rate limiting implementation diverged from documentation so perhaps there's something...

Thanks for your interest and submitting a PR However, given that this is out of the blue without an associated issue (which is perfectly fine!), it would be helpful if...

Thank you for the additional detail @valeriangalliat and yes we want to get some kind of documentation or official blessing before using any endpoint for reasons Chris has summarized well...

@valeriangalliat - we're going to be unable to move forward unless and until we get some kind of explicit acknowledgement from the service maintainers. That doesn't seem to be happening...

That works for me, thanks!

The CI failures seem to be non-spurious. Are you able to get the tests passing locally? (`npm run test:services -- --only=socket` should do the trick)