In light of the downtime on 2025-02-07T00:24:00Z, the rate limits for the Discord bot have been tightened. A particularly active server led to Rick repeatedly exceeding Discord’s rate limits, resulting in a temporary ban from the Discord API for approximately 60 minutes.
[!tg] This update, although formulated after the Discord incident, is equally relevant to the Telegram bot.
More Strict Rate Limits
So, there’s been a bit of a change in the system, and some of the rate limits have been tweaked. Don’t worry, most of you should be totally unaffected, but there might be a few exceptions. My goal is to find the perfect balance so that Rick can keep running smoothly without putting too much strain on the regular users.
If you are rate limited, just wait a few seconds before querying Rick again. If anything, DO NOT keep spamming the command or contract. As long as you’re spamming, Rick will ignore you - eventually, you will hit the maximum requests/min and have to sit it out.
[!info] One of the changes is the reduction in the number of ‘slow-down’ messages from Rick, which exacerbates the situation. As a result, you won’t always be aware if you’re being rate limited.
Going forward
I think I fixed the main problem that led to this ban, but we’ll see how it goes. If these changes don’t work, I’ll put in place server-based rate limits. Hopefully, we won’t need those.
[!warning] Running any form of automation on Rick may result in your server being banned from using Rick.