Heapy / Heapy/kotbot

Rate limiting

Open
#6 1 comment 1 reaction 0 assignees View on GitHub

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.