diff --git a/data/web/blogfork.telegram.org/bots/api-changelog.html b/data/web/blogfork.telegram.org/bots/api-changelog.html index 1c3eb8c9e8..17e6f3f996 100644 --- a/data/web/blogfork.telegram.org/bots/api-changelog.html +++ b/data/web/blogfork.telegram.org/bots/api-changelog.html @@ -54,7 +54,8 @@ To learn how to create…">
-Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk
Bot API 6.5
Bot API 6.4
Bot API 6.3
Bot API 6.2
Custom Emoji Support
Bot API 6.1
Media in Descriptions
Bot API 6.0
WARNING!
After the next update, only HTTPS links will be allowed in login_url inline keyboard buttons.
Bot API 5.7
Bot API 5.6
Bot API 5.5
Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.
Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.
Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.
-Bot API 5.4
creates_join_request
to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests (read more about this on our blog). WARNING!
User identifiers will become bigger than 2^31 - 1
before the end of this year 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.
Bot API 5.3
Personalized Commands
WARNING!
After one of the upcoming Bot API updates, 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.
Bot API 5.2
WARNING!
After one of the upcoming Bot API updates, 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.
Bot API 5.1
Added two new update types
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.
Introducing Bot API 5.0
Run Your Own Bot API Server
Bot API 4.9
Bot API 4.8
Bot API 4.7
Bot API 4.6
Bot API 4.5
Bot API 4.4
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.3
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.2
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.1
Bot API 4.0.
410 Gone
for all requests for more than 23 hours successively, it can be automatically removed.Bot API 3.6.
Bot API 3.5.
Bot API 3.4.
Bot API 3.3.
Bot API 3.2. Teach your bot to handle stickers and sticker sets.
Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:
Introducing Bot API 3.0.
NEW Payment Platform
See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.
@@ -568,14 +575,15 @@ To learn how to create…">Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.
Bot API 2.3
Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.
Introducing Bot API 2.0. Check out this page for a review of this major update.
setinlinefeedback
command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object./setinline
to @BotFather.@channelusername
) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).The bot platform was officially launched.
+The bot platform is officially launched.
diff --git a/data/web/core.telegram.org/bots/api-changelog.html b/data/web/core.telegram.org/bots/api-changelog.html index 1c3eb8c9e8..17e6f3f996 100644 --- a/data/web/core.telegram.org/bots/api-changelog.html +++ b/data/web/core.telegram.org/bots/api-changelog.html @@ -54,7 +54,8 @@ To learn how to create…">
-Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk
Bot API 6.5
Bot API 6.4
Bot API 6.3
Bot API 6.2
Custom Emoji Support
Bot API 6.1
Media in Descriptions
Bot API 6.0
WARNING!
After the next update, only HTTPS links will be allowed in login_url inline keyboard buttons.
Bot API 5.7
Bot API 5.6
Bot API 5.5
Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.
Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.
Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.
-Bot API 5.4
creates_join_request
to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests (read more about this on our blog). WARNING!
User identifiers will become bigger than 2^31 - 1
before the end of this year 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.
Bot API 5.3
Personalized Commands
WARNING!
After one of the upcoming Bot API updates, 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.
Bot API 5.2
WARNING!
After one of the upcoming Bot API updates, 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.
Bot API 5.1
Added two new update types
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.
Introducing Bot API 5.0
Run Your Own Bot API Server
Bot API 4.9
Bot API 4.8
Bot API 4.7
Bot API 4.6
Bot API 4.5
Bot API 4.4
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.3
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.2
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.1
Bot API 4.0.
410 Gone
for all requests for more than 23 hours successively, it can be automatically removed.Bot API 3.6.
Bot API 3.5.
Bot API 3.4.
Bot API 3.3.
Bot API 3.2. Teach your bot to handle stickers and sticker sets.
Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:
Introducing Bot API 3.0.
NEW Payment Platform
See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.
@@ -568,14 +575,15 @@ To learn how to create…">Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.
Bot API 2.3
Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.
Introducing Bot API 2.0. Check out this page for a review of this major update.
setinlinefeedback
command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object./setinline
to @BotFather.@channelusername
) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).The bot platform was officially launched.
+The bot platform is officially launched.
diff --git a/data/web/corefork.telegram.org/bots/api-changelog.html b/data/web/corefork.telegram.org/bots/api-changelog.html index f8f20661fe..3d4843c724 100644 --- a/data/web/corefork.telegram.org/bots/api-changelog.html +++ b/data/web/corefork.telegram.org/bots/api-changelog.html @@ -54,7 +54,8 @@ To learn how to create…">
-Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk
Bot API 6.5
Bot API 6.4
Bot API 6.3
Bot API 6.2
Custom Emoji Support
Bot API 6.1
Media in Descriptions
Bot API 6.0
WARNING!
After the next update, only HTTPS links will be allowed in login_url inline keyboard buttons.
Bot API 5.7
Bot API 5.6
Bot API 5.5
Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.
Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.
Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.
-Bot API 5.4
creates_join_request
to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests (read more about this on our blog). WARNING!
User identifiers will become bigger than 2^31 - 1
before the end of this year 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.
Bot API 5.3
Personalized Commands
WARNING!
After one of the upcoming Bot API updates, 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.
Bot API 5.2
WARNING!
After one of the upcoming Bot API updates, 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.
Bot API 5.1
Added two new update types
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.
Introducing Bot API 5.0
Run Your Own Bot API Server
Bot API 4.9
Bot API 4.8
Bot API 4.7
Bot API 4.6
Bot API 4.5
Bot API 4.4
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.3
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.2
149.154.160.0/20
and 91.108.4.0/22
. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.Bot API 4.1
Bot API 4.0.
410 Gone
for all requests for more than 23 hours successively, it can be automatically removed.Bot API 3.6.
Bot API 3.5.
Bot API 3.4.
Bot API 3.3.
Bot API 3.2. Teach your bot to handle stickers and sticker sets.
Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:
Introducing Bot API 3.0.
NEW Payment Platform
See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.
@@ -568,14 +575,15 @@ To learn how to create…">Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.
Bot API 2.3
Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.
Introducing Bot API 2.0. Check out this page for a review of this major update.
setinlinefeedback
command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object./setinline
to @BotFather.@channelusername
) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).The bot platform was officially launched.
+The bot platform is officially launched.