Rate limiting
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 37
- Forks
- 2
- Avg merge
- 1h 35m
- Merged PRs (30d)
- 5
Description
Telegram Bot API has a concept of rate limiting with several levels (overall: ~30 messages per second, per chat: ~20 messages per minute).
https://core.telegram.org/bots/faq#my-bot-is-hitting-limits-how-do-i-avoid-this
Though we won't hit these limits anytime soon, we should probably account for that at some point.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Telegram Bot API FAQ section on rate limits. Then inspect the repository for the bot message-sending entry point and existing request handling. Done should mean that the required rate limits and their scope are explicitly defined and accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100