Skip to content

Telegramium-5.53.0
Compare
Choose a tag to compare
@johnspade johnspade released this 29 Jun 08:15
· 469 commits to master since this release
5.53.0
505094b
This commit was signed with the committer’s verified signature.
johnspade John S
GPG key ID: B1FCC5630ED47F02
Learn about vigilant mode.

Telegramium-5.53.0 released.
It supports all methods and entities of Telegram Bot API v5.3.

This MAJOR release introduces significant breaking changes.

Notable changes

  • User identifiers are now stored as Longs.

Excerpt from Bot API official announcement for version 5.3

https://core.telegram.org/bots/api#june-25-2021

Personalized Commands

  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • Added the parameters scope and language_code to the method getMyCommands.
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots

Custom Placeholders

  • Added the ability to specify a custom input field placeholder in the classes ReplyKeyboardMarkup and ForceReply.

And More

  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • Renamed the method kickChatMember to banChatMember.
  • Renamed the method getChatMembersCount to getChatMemberCount.
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

Assets 2
Loading