Closed 2Cubed closed 6 years ago
Important thing: Each service handler needs to implement this some how. Different services have different rate limits.
We should probably have a generalized ratelimit method somewhere in the WebSocket
class, which can either be used or ignored by the individual services.
It shouldn't be able to be ignored. It should be required.
Maybe make it so that if a service rate limit isn't supplied by the handler (Or whatever would handle it) it then falls back to the default one and can't be bypassed?
Issue moved to CactusDev/Aerophyl #9 via ZenHub
The bot ignores rate limits, trying to send messages whenever they are received. This especially impacts responses that are split over multiple chat messages.