You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’d like to propose an enhancement to how the bot interacts with the CoinGecko API. Right now, while we’re successfully pulling data from the API, we need to ensure that we’re managing our requests effectively to avoid hitting any rate limits. This will help us maintain a smooth operation without interruptions.
Use Case
Implementing better rate limiting will make a huge difference in how the bot performs. By adding features like a request queue and exponential backoff for failed calls, we can ensure that the bot continues to operate reliably even during busy times. It will also keep our users informed about the status of their requests, making the experience much smoother.
Benefits
Adding this feature will bring several benefits:
1)Better Reliability: Users will experience fewer interruptions and delays when fetching data.
2)Enhanced User Experience: With a more responsive system, users will trust the bot more and feel confident using it.
3)Efficient API Use: We'll reduce unnecessary API calls, which can save us from hitting those annoying rate limits.
Priority
High
Record
I agree to follow this project's Code of Conduct
I'm a GSSOC WOB24 contributor
I want to work on this issue
I'm willing to provide further clarification or assistance if needed.
The text was updated successfully, but these errors were encountered:
Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.
This project is very well structured and I want to make more enhancement ,I am really excited to contribute to this project,Looking forward to contribute to this amazing project
Is there an existing issue for this?
Feature Description
I’d like to propose an enhancement to how the bot interacts with the CoinGecko API. Right now, while we’re successfully pulling data from the API, we need to ensure that we’re managing our requests effectively to avoid hitting any rate limits. This will help us maintain a smooth operation without interruptions.
Use Case
Implementing better rate limiting will make a huge difference in how the bot performs. By adding features like a request queue and exponential backoff for failed calls, we can ensure that the bot continues to operate reliably even during busy times. It will also keep our users informed about the status of their requests, making the experience much smoother.
Benefits
Adding this feature will bring several benefits:
1)Better Reliability: Users will experience fewer interruptions and delays when fetching data.
2)Enhanced User Experience: With a more responsive system, users will trust the bot more and feel confident using it.
3)Efficient API Use: We'll reduce unnecessary API calls, which can save us from hitting those annoying rate limits.
Priority
High
Record
The text was updated successfully, but these errors were encountered: