Handling the maximum length of a Telegram message #1616
Merged
Conversation
This file contains 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
The maximum allowed length of a Telegram message - 4096 symbols (https://core.telegram.org/bots/api#message, 'text' field). Longer messages are not delivered. Therefore, I implemented splitting too long message into several (with a 1 second delay between sending according to the documentation - https://core.telegram.org/bots/faq#my-bot-is-hitting-limits-how-do-i-avoid-this) as the default behavior. An additional option that you can enable by truncateLongMessage is to leave one message, but truncate it to the maximum length allowed.
stof
reviewed
Nov 26, 2021
stof
reviewed
Nov 26, 2021
|
Thanks |
This was referenced Mar 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The maximum allowed length of a Telegram message - 4096 symbols ('text' field).
Longer messages are not delivered.
Therefore, I implemented truncating too long message to the maximum length allowed as the default behavior.
An additional option that you can enable by
splitLongMessagesis splitting too long message into several. Also, usingdelayBetweenMessagesyou can enable a 1 second delay between sending a split message to avoid the 429 Too Many Requests error (according to the recommendations - My bot is hitting limits, how do I avoid this?)