Feature/missing rate limiting 267#320
Open
sr-857 wants to merge 6 commits intoGauravKarakoti:mainfrom
Open
Conversation
Contributor
|
@sr-857 is attempting to deploy a commit to the Gaurav's projects Team on Vercel. A member of the Team first needs to authorize it. |
✅ Deploy Preview for swapsmithminiapp canceled.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR 3: Missing Rate Limiting on Bot (#267)
Technical Analysis
The Telegram bot lacked rate limiting, making it vulnerable to spam and potential API flooding. This could lead to service degradation and increased costs.
Proposed Solution
Integrate
telegraf-ratelimitmiddleware to restrict the frequency of messages from a single user.Changes
telegraf-ratelimitand added it to the bot's middleware stack inbot/src/bot.ts.Verification