Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we allow users to opt out of ratelimits in RequestOptions? #401

Closed
foxbot opened this issue Dec 5, 2016 · 2 comments
Closed

Should we allow users to opt out of ratelimits in RequestOptions? #401

foxbot opened this issue Dec 5, 2016 · 2 comments

Comments

@foxbot
Copy link
Member

foxbot commented Dec 5, 2016

For some API methods, notably AddReactionAsync and RemoveReactionAsync, Discord's actual ratelimit is 1/0.25, but for "performance" this is returned in ratelimit headers as 1/1.

For bots that use reactions as buttons, (see Paginator), this 1/1 limit is very inconvienent, and it would be useful to allow us to override header ratelimits in this case, and use the full 1/0.25

@khionu
Copy link
Contributor

khionu commented Dec 5, 2016

Not a black-and-white opt-out. Or if so, maybe an opt-out of the Headers? We do still have the constants, right? Might be better to have an option to use the Headers or Constants

@foxbot
Copy link
Member Author

foxbot commented Aug 29, 2017

It was decided that the high-level library will not support ratelimit evasion - this will become available at a later date.

@foxbot foxbot closed this as completed Aug 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants