diff --git a/data/corefork.telegram.org.html b/data/corefork.telegram.org.html
index cce89d5518..7adcd67da8 100644
--- a/data/corefork.telegram.org.html
+++ b/data/corefork.telegram.org.html
@@ -91,8 +91,8 @@
How to subscribe to updates and handle them properly.
How to subscribe and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram offers detailed channel statistics for channels and supergroups.
@@ -140,7 +140,7 @@
Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
-Channels, legacy groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
+Channels, basic groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.
diff --git a/data/corefork.telegram.org/api.html b/data/corefork.telegram.org/api.html
index cce89d5518..7adcd67da8 100644
--- a/data/corefork.telegram.org/api.html
+++ b/data/corefork.telegram.org/api.html
@@ -91,8 +91,8 @@
How to subscribe to updates and handle them properly.
How to subscribe and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram offers detailed channel statistics for channels and supergroups.
@@ -140,7 +140,7 @@
Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
-Channels, legacy groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
+Channels, basic groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.
diff --git a/data/corefork.telegram.org/api/auth.html b/data/corefork.telegram.org/api/auth.html
index d3a86b5dde..486e1a5c42 100644
--- a/data/corefork.telegram.org/api/auth.html
+++ b/data/corefork.telegram.org/api/auth.html
@@ -44,64 +44,74 @@
-
Authorization is associated with a client's encryption key identifier: auth_key_id . No additional parameters need to be passed into methods following authorization.
-
To log in as a bot , follow these instructions » .
-
+
Authorization is associated with a client's encryption key identifier: auth_key_id . No additional parameters need to be passed into methods following authorization.
+
To log in as a bot , follow these instructions » .
+
Example implementations: telegram for android , tdlib .
-
To show a nicely formatted and validated phone number field, the help.countriesList constructor can be obtained using the help.getCountriesList method.help.countriesList config is then used as described here » .
-
Then, a text message containing an authorization code is sent to the user's phone using auth.sendCode .
-
-
When invoking auth.logOut on a previously authorized session with 2FA enabled, the server may return a future_auth_token, which should be stored in the local database.auth.sendCode , all logout tokens present in the database should be provided to codeSettings.logout_tokens.auth.sendCode will directly return a SESSION_PASSWORD_NEEDED RPC error, directly asking the user to enter the 2FA password , without sending any authorization code.
+
To show a nicely formatted and validated phone number field, the help.countriesList constructor can be obtained using the help.getCountriesList method.help.countriesList config is then used as described here » .
+
Then, a text message containing an authorization code is sent to the user's phone using auth.sendCode .
+
+
When invoking auth.logOut on a previously authorized session with 2FA enabled, the server may return a future_auth_token, which should be stored in the local database.auth.sendCode , all logout tokens present in the database should be provided to codeSettings.logout_tokens.auth.sendCode will directly return a SESSION_PASSWORD_NEEDED RPC error, directly asking the user to enter the 2FA password , without sending any authorization code.
Otherwise, the system will send an authorization code using the following logic:
-
+
The system will automatically choose how to send the authorization code; there are multiple possible ways the code can arrive:
-Logout tokens » Logout tokens » Telegram code SMS code Phone call : a synthesized voice will tell the user which verification code to input.Flash phone call : the code will be sent via a flash phone call, that will be closed immediately.auth.sentCodeTypeFlashCall ).Flash phone call : the code will be sent via a flash phone call, that will be closed immediately.
+In the last case, the phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern (see auth.sentCodeTypeFlashCall ).Missed phone call : the code will be sent via a flash phone call, that will be closed immediately. The last digits of the phone number that calls are the code that must be entered manually by the user.
-
The auth.sendCode method also has parameters for enabling/disabling use of flash calls and missed calls, and allows passing an SMS token that will be included in the sent SMS.android SMS receiver APIs .
+
The auth.sendCode method also has parameters for enabling/disabling use of flash calls and missed calls, and allows passing an SMS token that will be included in the sent SMS.
+For example, the latter is required in newer versions of android, to use the android SMS receiver APIs .
The returned auth.SentCode object will contain multiple parameters:
-
If the message takes too long (timeout seconds) to arrive at the phone, the auth.resendCode method may be invoked to resend a code of type next_type.auth.resendCode with the next_type returned by the previous call to auth.resendCode .auth.cancelCode .
-
+
If the message takes too long (timeout seconds) to arrive at the phone, the auth.resendCode method may be invoked to resend a code of type next_type.
+If the same happens again, you can use auth.resendCode with the next_type returned by the previous call to auth.resendCode .
+To cancel the verification code use auth.cancelCode .
+
When user enters verification code, the auth.signIn method must be used to validate it and possibly sign user in.
-
If the code was entered correctly, but the method returns auth.authorizationSignUpRequired , it means that account with this phone number doesn't exist yet: user needs to provide basic information, accept terms of service and then the new user registration method (auth.signUp ) must be invoked.
-
-
When trying to sign in using auth.signIn , an error 400 SESSION_PASSWORD_NEEDED may be returned, if the user has two-factor authentication enabled.SRP 2FA authentication must be followed.
+
If the code was entered correctly, but the method returns auth.authorizationSignUpRequired , it means that account with this phone number doesn't exist yet: user needs to provide basic information, accept terms of service and then the new user registration method (auth.signUp ) must be invoked.
+
+
When trying to sign in using auth.signIn , an error 400 SESSION_PASSWORD_NEEDED may be returned, if the user has two-factor authentication enabled.
+In this case, instructions for SRP 2FA authentication must be followed.
To set up two-factor authorization on an already authorized account, follow the SRP 2FA authentication docs .
-
+
Each phone number is limited to only a certain amount of logins per day (e.g. 5, but this is subject to change) after which the API will return a FLOOD error until the next day. This might not be enough for testing the implementation of User Authorization flows in client applications.
There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are available in API development tools panel after api_id was obtained , URI format for HTTPS/Websocket transport).
If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).
@@ -110,8 +120,8 @@
To help you with working on production DCs, logins with the same phone number with which the api_id was registered have more generous flood limits.
-
-
As a result of authorization, the client key, auth_key_id , becomes associated with the user, and each subsequent API call with this key will be executed with that user's identity. The authorization method itself returns the relevant user. It is best to immediately store the User ID locally in a binding with the key.
+
+
As a result of authorization, the client key, auth_key_id , becomes associated with the user, and each subsequent API call with this key will be executed with that user's identity. The authorization method itself returns the relevant user. It is best to immediately store the User ID locally in a binding with the key.
Only a small portion of the API methods are available to unauthorized users:
-
Other methods will result in an error: 401 UNAUTHORIZED
-
Other methods will result in an error: 401 UNAUTHORIZED
diff --git a/data/corefork.telegram.org/api/channel.html b/data/corefork.telegram.org/api/channel.html
index 953225384b..f5b490e0d3 100644
--- a/data/corefork.telegram.org/api/channel.html
+++ b/data/corefork.telegram.org/api/channel.html
@@ -2,12 +2,12 @@
Channels, supergroups, gigagroups and legacy groups
+ Channels, supergroups, gigagroups and basic groups
-
-
Channels, supergroups, gigagroups and legacy groups
+
+
Channels, supergroups, gigagroups and basic groups
@@ -58,11 +58,11 @@ Supergroups can also be assigned a
geo_point to become
when prompted by the API using suggestions » , can convert a megagroup into a gigagroup using
channels.convertToGigagroup (one way only).
After that, only admins will be able to write in the group (like when
send_messages rights are disabled for all group participants by default), but the participant limit is removed and the group can become much bigger than a supergroup (e.g. >200,000 currently).
Also, one can't invite people into gigagroups and participants of voice chats in gigagroups are muted by default.
-
-
In previous versions of telegram, only legacy groups (represented by chat constructors) could be created using messages.createChat : these groups have fewer features, and can only have 200 members at max.user's message box » : this means that all legacy groups and all private chats share the same, single message ID and PTS sequence.
+
+
In previous versions of telegram, only basic groups (represented by chat constructors) could be created using messages.createChat : these groups have fewer features, and can only have 200 members at max.user's message box » : this means that all basic groups and all private chats share the same, single message ID and PTS sequence.
-
To upgrade a legacy group to a supergroup, messages.migrateChat can be used.
+
To upgrade a basic group to a supergroup, messages.migrateChat can be used.
The chats field of the result will have two objects:
A chat constructor with a migrated_to field, indicating the address of the new supergroup
@@ -71,12 +71,12 @@ The chats field of the result will have two objects:
When getting full info about the migrated channel, the channelFull object will have migrated_from_chat_id and migrated_from_max_id fields indicating the original ID of the chat, and the message ID in the original chat at which the group was migrated.
All users of the chat will receive an updateNewMessage from the old chat with a messageService containing a messageActionChatMigrateTo constructor.
All new messages have to be sent to the new supergroup.
-When working with migrated groups clients need to handle loading of the message history (as well as search results et cetera) from both the legacy group and the new supergroup. This is done by merging the two messages lists (requested with different Peer values) client side.
+When working with migrated groups clients need to handle loading of the message history (as well as search results et cetera) from both the basic group and the new supergroup. This is done by merging the two messages lists (requested with different Peer values) client side.
Channels, legacy groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
+Channels, basic groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
For more info on how to work with public usernames, invite links and join requests, see here » .
Channels, legacy groups and supergroups allow setting granular permissions both for admins and specific users; channels, supergroups and legacy groups also allow setting global granular permissions for users.
+Channels, basic groups and supergroups allow setting granular permissions both for admins and specific users; channels, supergroups and basic groups also allow setting global granular permissions for users.
For more info on how to set and modify rights, see here » .
Telegram allows pinning multiple messages on top in a chat, group, supergroup or channel.
diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html
index bfa8523ca8..af203c0300 100644
--- a/data/corefork.telegram.org/api/config.html
+++ b/data/corefork.telegram.org/api/config.html
@@ -45,287 +45,314 @@
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
-
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
-nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+config #330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector <DcOption > dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config ;
+nearestDc #8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc ;
---functions---
-help.getConfig#c4f9186b = Config;
-help.getNearestDc#1fb33026 = NearestDc;help.getConfig #c4f9186b = Config ;
+help.getNearestDc #1fb33026 = NearestDc ;The huge config constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the constructor page for more information.
-
-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+jsonObjectValue #c0de1bd9 key:string value:JSONValue = JSONObjectValue ;
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+jsonNull #3f6d7b68 = JSONValue ;
+jsonBool #c7345e6a value:Bool = JSONValue ;
+jsonNumber #2be0dfa4 value:double = JSONValue ;
+jsonString #b71e767a value:string = JSONValue ;
+jsonArray #f7444763 value:Vector <JSONValue > = JSONValue ;
+jsonObject #99c1d49d value:Vector <JSONObjectValue > = JSONValue ;
---functions---
-help.getAppConfig#98914110 = JSONValue;The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.help.getConfig returns MTProto-specific configuration with information about server-side limitations and other MTProto-related information, help.getAppConfig returns configuration parameters useful for graphical Telegram clients.
-Typical fields included in the resulting JSON object are: emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)
- keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean) background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)
- emojies_send_dice - A list of supported animated dice stickers (array of strings). emojies_send_dice_success - For animated dice emojis other than the basic value and frame_start float values)
- emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji ; the file reference field should be base64-decoded before downloading the file (map of file IDs , with emoji string keys) gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)
- gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis) stickers_emoji_suggest_only_api - Specifies that the app should not display local sticker suggestions for emojis at all and just use the result of messages.getStickers (bool)
- stickers_emoji_cache_time - Specifies the validity period of the local cache of messages.getStickers , also relevant when generating the pagination hash when invoking the method. (int) qr_login_camera - Whether the Settings->Devices menu should show an option to scan a QR login code (boolean)
- qr_login_code - Whether the login screen should show a QR code login option , possibly as default login method (string, “disabled”, “primary” or “secondary”) dialog_filters_enabled - Whether clients should show an option for managing dialog filters AKA folders (boolean)
- dialog_filters_tooltip - Whether clients should actively show a tooltip, inviting the user to configure dialog filters AKA folders ; typically this happens when the chat list is long enough to start getting cluttered. (boolean) autoarchive_setting_available - Whether clients can invoke account.setGlobalPrivacySettings with globalPrivacySettings.archive_and_mute_new_noncontact_peers = boolTrue pending_suggestions - Contains a list of suggestions that should be actively shown as a tooltip to the user. (Array of strings, possible values shown in the suggestions section » . url_auth_domains - A list of domains that support automatic login with manual user confirmation, click here for more info on URL authorization » . (array of strings)
- autologin_domains - A list of Telegram domains that support automatic login with no user confirmation, click here for more info on URL authorization » . (array of strings) autologin_token - Autologin token, click here for more info on URL authorization » . (string)
- round_video_encoding - Contains a set of recommended codec parameters for round videos. chat_read_mark_size_threshold - Per-user read receipts, fetchable using messages.getMessageReadParticipants , will be available in groups with an amount of participants less or equal to chat_read_mark_size_threshold. (int)
- chat_read_mark_expire_period - To protect user privacy, read receipts are only stored for chat_read_mark_expire_period seconds after the message was sent. (int) groupcall_video_participants_max - Maximum number of participants in a group call (livestreams allow ∞ participants) (int)
- reactions_default - Default emoji reaction to use in the quick reaction menu, this value can be changed using messages.setDefaultReaction (string)reactions_uniq_max - Maximum number of unique reaction-emojis for any given message: for example, if there are 2000
+help.getAppConfig #98914110 = JSONValue ;
+
The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.help.getConfig returns MTProto-specific configuration with information about server-side limitations and other MTProto-related information, help.getAppConfig returns configuration parameters useful for graphical Telegram clients.
+
Typical fields included in the resulting JSON object are:
+
+emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean)background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)emojies_send_dice - A list of supported animated dice stickers (array of strings).emojies_send_dice_success - For animated dice emojis other than the basic value and frame_start float values)emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji ; the file reference field should be base64-decoded before downloading the file (map of file IDs , with emoji string keys)gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis)stickers_emoji_suggest_only_api - Specifies that the app should not display local sticker suggestions for emojis at all and just use the result of messages.getStickers (bool)stickers_emoji_cache_time - Specifies the validity period of the local cache of messages.getStickers , also relevant when generating the pagination hash when invoking the method. (int)qr_login_camera - Whether the Settings->Devices menu should show an option to scan a QR login code (boolean)qr_login_code - Whether the login screen should show a QR code login option , possibly as default login method (string, "disabled", "primary" or "secondary")dialog_filters_enabled - Whether clients should show an option for managing dialog filters AKA folders (boolean)dialog_filters_tooltip - Whether clients should actively show a tooltip, inviting the user to configure dialog filters AKA folders ; typically this happens when the chat list is long enough to start getting cluttered. (boolean)autoarchive_setting_available - Whether clients can invoke account.setGlobalPrivacySettings with globalPrivacySettings.archive_and_mute_new_noncontact_peers = boolTruepending_suggestions - Contains a list of suggestions that should be actively shown as a tooltip to the user. (Array of strings, possible values shown in the suggestions section » . url_auth_domains - A list of domains that support automatic login with manual user confirmation, click here for more info on URL authorization » . (array of strings)autologin_domains - A list of Telegram domains that support automatic login with no user confirmation, click here for more info on URL authorization » . (array of strings)autologin_token - Autologin token, click here for more info on URL authorization » . (string)round_video_encoding - Contains a set of recommended codec parameters for round videos. chat_read_mark_size_threshold - Per-user read receipts, fetchable using messages.getMessageReadParticipants , will be available in groups with an amount of participants less or equal to chat_read_mark_size_threshold. (int)chat_read_mark_expire_period - To protect user privacy, read receipts are only stored for chat_read_mark_expire_period seconds after the message was sent. (int)groupcall_video_participants_max - Maximum number of participants in a group call (livestreams allow ∞ participants) (int)reactions_default - Default emoji reaction to use in the quick reaction menu, this value can be changed using messages.setDefaultReaction (string)reactions_uniq_max - Maximum number of unique reaction-emojis for any given message: for example, if there are 2000
Example value:
-
{
- "test": 1,
- "emojies_animated_zoom": 0.625,
- "keep_alive_service": true,
- "background_connection": true,
- "emojies_send_dice": [
- "\ud83c\udfb2",
- "\ud83c\udfaf",
- "\ud83c\udfc0",
- "\u26bd",
- "\u26bd\ufe0f",
- "\ud83c\udfb0",
- "\ud83c\udfb3"
+{
+ "test": 1,
+ "emojies_animated_zoom": 0.625,
+ "keep_alive_service": true,
+ "background_connection": true,
+ "emojies_send_dice": [
+ "\ud83c\udfb2",
+ "\ud83c\udfaf",
+ "\ud83c\udfc0",
+ "\u26bd",
+ "\u26bd\ufe0f",
+ "\ud83c\udfb0",
+ "\ud83c\udfb3"
],
- "emojies_send_dice_success": {
- "\ud83c\udfaf": {
- "value": 6,
- "frame_start": 62
+ "emojies_send_dice_success": {
+ "\ud83c\udfaf": {
+ "value": 6,
+ "frame_start": 62
},
- "\ud83c\udfc0": {
- "value": 5,
- "frame_start": 110
+ "\ud83c\udfc0": {
+ "value": 5,
+ "frame_start": 110
},
- "\u26bd": {
- "value": 5,
- "frame_start": 110
+ "\u26bd": {
+ "value": 5,
+ "frame_start": 110
},
- "\u26bd\ufe0f": {
- "value": 5,
- "frame_start": 110
+ "\u26bd\ufe0f": {
+ "value": 5,
+ "frame_start": 110
},
- "\ud83c\udfb0": {
- "value": 64,
- "frame_start": 110
+ "\ud83c\udfb0": {
+ "value": 64,
+ "frame_start": 110
},
- "\ud83c\udfb3": {
- "value": 6,
- "frame_start": 110
+ "\ud83c\udfb3": {
+ "value": 6,
+ "frame_start": 110
}
},
- "emojies_sounds": {
- "\ud83c\udf83": {
- "id": "4956223179606458539",
- "access_hash": "-2107001400913062971",
- "file_reference_base64": "AGIaeBZckszt-s71DzCHhSkfZI_l"
+ "emojies_sounds": {
+ "\ud83c\udf83": {
+ "id": "4956223179606458539",
+ "access_hash": "-2107001400913062971",
+ "file_reference_base64": "AGIaeBZckszt-s71DzCHhSkfZI_l"
},
- "\u26b0": {
- "id": "4956223179606458540",
- "access_hash": "-1498869544183595185",
- "file_reference_base64": "AGIaeBZRfKxsAgnaLEDh5XIa8Gri"
+ "\u26b0": {
+ "id": "4956223179606458540",
+ "access_hash": "-1498869544183595185",
+ "file_reference_base64": "AGIaeBZRfKxsAgnaLEDh5XIa8Gri"
},
- "\ud83e\udddf\u200d\u2642": {
- "id": "4960929110848176331",
- "access_hash": "3986395821757915468",
- "file_reference_base64": "AGIaeBZcFga_bS9BsPvVNA2zuYCI"
+ "\ud83e\udddf\u200d\u2642": {
+ "id": "4960929110848176331",
+ "access_hash": "3986395821757915468",
+ "file_reference_base64": "AGIaeBZcFga_bS9BsPvVNA2zuYCI"
},
- "\ud83e\udddf": {
- "id": "4960929110848176332",
- "access_hash": "-8929417974289765626",
- "file_reference_base64": "AGIaeBbUbidUDCl4nImJXPTl2wWj"
+ "\ud83e\udddf": {
+ "id": "4960929110848176332",
+ "access_hash": "-8929417974289765626",
+ "file_reference_base64": "AGIaeBbUbidUDCl4nImJXPTl2wWj"
},
- "\ud83e\udddf\u200d\u2640": {
- "id": "4960929110848176333",
- "access_hash": "9161696144162881753",
- "file_reference_base64": "AGIaeBb-ulJ2E-rSI2B8EKyAXs-8"
+ "\ud83e\udddf\u200d\u2640": {
+ "id": "4960929110848176333",
+ "access_hash": "9161696144162881753",
+ "file_reference_base64": "AGIaeBb-ulJ2E-rSI2B8EKyAXs-8"
},
- "\ud83c\udf51": {
- "id": "4963180910661861548",
- "access_hash": "-7431729439735063448",
- "file_reference_base64": "AGIaeBa940aXpIVLThj0J2ctxYFe"
+ "\ud83c\udf51": {
+ "id": "4963180910661861548",
+ "access_hash": "-7431729439735063448",
+ "file_reference_base64": "AGIaeBa940aXpIVLThj0J2ctxYFe"
},
- "\ud83c\udf8a": {
- "id": "5094064004578410732",
- "access_hash": "8518192996098758509",
- "file_reference_base64": "AGIaeBZFqTTp5drt0JZ86DGDAu1t"
+ "\ud83c\udf8a": {
+ "id": "5094064004578410732",
+ "access_hash": "8518192996098758509",
+ "file_reference_base64": "AGIaeBZFqTTp5drt0JZ86DGDAu1t"
},
- "\ud83c\udf84": {
- "id": "5094064004578410733",
- "access_hash": "-4142643820629256996",
- "file_reference_base64": "AGIaeBbEqu-gV0qAUdP5lD3MxLSK"
+ "\ud83c\udf84": {
+ "id": "5094064004578410733",
+ "access_hash": "-4142643820629256996",
+ "file_reference_base64": "AGIaeBbEqu-gV0qAUdP5lD3MxLSK"
},
- "\ud83e\uddbe": {
- "id": "5094064004578410734",
- "access_hash": "-8934384022571962340",
- "file_reference_base64": "AGIaeBZ0YCp8_Zl_cmP4nvKkkSfF"
+ "\ud83e\uddbe": {
+ "id": "5094064004578410734",
+ "access_hash": "-8934384022571962340",
+ "file_reference_base64": "AGIaeBZ0YCp8_Zl_cmP4nvKkkSfF"
}
},
- "gif_search_branding": "tenor",
- "gif_search_emojies": [
- "\ud83d\udc4d",
- "\ud83d\ude18",
- "\ud83d\ude0d",
- "\ud83d\ude21",
- "\ud83e\udd73",
- "\ud83d\ude02",
- "\ud83d\ude2e",
- "\ud83d\ude44",
- "\ud83d\ude0e",
- "\ud83d\udc4e"
+ "gif_search_branding": "tenor",
+ "gif_search_emojies": [
+ "\ud83d\udc4d",
+ "\ud83d\ude18",
+ "\ud83d\ude0d",
+ "\ud83d\ude21",
+ "\ud83e\udd73",
+ "\ud83d\ude02",
+ "\ud83d\ude2e",
+ "\ud83d\ude44",
+ "\ud83d\ude0e",
+ "\ud83d\udc4e"
],
- "stickers_emoji_suggest_only_api": false,
- "stickers_emoji_cache_time": 86400,
- "groupcall_video_participants_max": 1000,
- "qr_login_camera": true,
- "qr_login_code": "primary",
- "dialog_filters_enabled": true,
- "dialog_filters_tooltip": true,
- "autoarchive_setting_available": false,
- "pending_suggestions": [
- "AUTOARCHIVE_POPULAR",
- "VALIDATE_PASSWORD",
- "VALIDATE_PHONE_NUMBER",
- "NEWCOMER_TICKS"
+ "stickers_emoji_suggest_only_api": false,
+ "stickers_emoji_cache_time": 86400,
+ "groupcall_video_participants_max": 1000,
+ "qr_login_camera": true,
+ "qr_login_code": "primary",
+ "dialog_filters_enabled": true,
+ "dialog_filters_tooltip": true,
+ "autoarchive_setting_available": false,
+ "pending_suggestions": [
+ "AUTOARCHIVE_POPULAR",
+ "VALIDATE_PASSWORD",
+ "VALIDATE_PHONE_NUMBER",
+ "NEWCOMER_TICKS"
],
- "autologin_token": "string",
- "autologin_domains": [
- "instantview.telegram.org",
- "translations.telegram.org",
- "contest.dev",
- "contest.com",
- "bugs.telegram.org",
- "suggestions.telegram.org",
- "themes.telegram.org",
- "promote.telegram.org"
+ "autologin_token": "string",
+ "autologin_domains": [
+ "instantview.telegram.org",
+ "translations.telegram.org",
+ "contest.dev",
+ "contest.com",
+ "bugs.telegram.org",
+ "suggestions.telegram.org",
+ "themes.telegram.org",
+ "promote.telegram.org"
],
- "round_video_encoding": {
- "diameter": 384,
- "video_bitrate": 1000,
- "audio_bitrate": 64,
- "max_size": 12582912
+ "round_video_encoding": {
+ "diameter": 384,
+ "video_bitrate": 1000,
+ "audio_bitrate": 64,
+ "max_size": 12582912
},
- "chat_read_mark_expire_period": 604800,
- "chat_read_mark_size_threshold": 100,
- "reactions_default": "\ud83d\udc4d",
- "reactions_uniq_max": 11
+ "chat_read_mark_expire_period": 604800,
+ "chat_read_mark_size_threshold": 100,
+ "reactions_default": "\ud83d\udc4d",
+ "reactions_uniq_max": 11
}The API can return a set of useful suggestions for users of graphical clients.
-jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+jsonObjectValue #c0de1bd9 key:string value:JSONValue = JSONObjectValue ;
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+jsonNull #3f6d7b68 = JSONValue ;
+jsonBool #c7345e6a value:Bool = JSONValue ;
+jsonNumber #2be0dfa4 value:double = JSONValue ;
+jsonString #b71e767a value:string = JSONValue ;
+jsonArray #f7444763 value:Vector <JSONValue > = JSONValue ;
+jsonObject #99c1d49d value:Vector <JSONObjectValue > = JSONValue ;
---functions---
-help.getAppConfig#98914110 = JSONValue;The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.Client Configuration section » , but we're mostly interested in the pending_suggestions and autoarchive_setting_available fields of the returned JSON object:
+help.getAppConfig #98914110 = JSONValue ;The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.Client Configuration section » , but we're mostly interested in the pending_suggestions and autoarchive_setting_available fields of the returned JSON object:
-messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+messages.chatFull #e5d7d19c full_chat:ChatFull chats:Vector <Chat > users:Vector <User > = messages.ChatFull ;
-channelFull#e13c3d20 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string requests_pending:flags.28?int recent_requesters:flags.28?Vector<long> default_send_as:flags.29?Peer available_reactions:flags.30?Vector<string> = ChatFull;
+channelFull #e13c3d20 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector <BotInfo > migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector <string > groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string requests_pending:flags.28?int recent_requesters:flags.28?Vector <long > default_send_as:flags.29?Peer available_reactions:flags.30?Vector <string > = ChatFull ;
---functions---
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;Some channel/supergroup -related suggestions can also be contained in the pending_suggestions field of the channelFull constructor, returned by channels.getFullChannel .CONVERT_GIGAGROUP - The supergroup has many participants: the admin should call channels.convertToGigagroup to convert it to a gigagroup.
-boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
+channels.getFullChannel #8736a09 channel:InputChannel = messages.ChatFull ;Some channel/supergroup -related suggestions can also be contained in the pending_suggestions field of the channelFull constructor, returned by channels.getFullChannel .
+
+boolFalse #bc799737 = Bool ;
+boolTrue #997275b5 = Bool ;
---functions---
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;help.dismissSuggestion can be used to dismiss a suggestion.inputPeerEmpty to peer for basic suggestions and the channel/supergroup 's peer for channel suggestions .
-help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
+help.dismissSuggestion #f50dbaa1 peer:InputPeer suggestion:string = Bool ;help.dismissSuggestion can be used to dismiss a suggestion.inputPeerEmpty to peer for basic suggestions and the channel/supergroup 's peer for channel suggestions .
+help.appUpdate #ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector <MessageEntity > document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate ;
+help.noAppUpdate #c45a6536 = help.AppUpdate ;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+updates #74ae4240 updates:Vector <Update > users:Vector <User > chats:Vector <Chat > date:int seq:int = Updates ;
+updateServiceNotification #ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector <MessageEntity > = Update ;
-help.inviteText#18cb9f78 message:string = help.InviteText;
+help.inviteText #18cb9f78 message:string = help.InviteText ;
---functions---
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+help.getAppUpdate #522d5a7d source:string = help.AppUpdate ;
+help.getAppChangelog #9010ef6f prev_app_version:string = Updates ;
-help.getInviteText#4d392343 = help.InviteText;help.getInviteText #4d392343 = help.InviteText ;
help.getAppUpdate - Get info about an application update, can contain the updated application binary in the attached documenthelp.getAppChangelog - Get a list of service messages with app-specific changelogshelp.getInviteText - Returns a localized invitation message that can be sent via SMS to contacts that haven't signed up to Telegram yethelp.getInviteText - Returns a localized invitation message that can be sent via SMS to contacts that haven't signed up to Telegram yet
-help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdateEmpty #e3309f7f expires:int = help.TermsOfServiceUpdate ;
+help.termsOfServiceUpdate #28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate ;
-help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
+help.termsOfService #780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector <MessageEntity > min_age_confirm:flags.1?int = help.TermsOfService ;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+auth.authorizationSignUpRequired #44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization ;
---functions---
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+help.getTermsOfServiceUpdate #2ca51fd1 = help.TermsOfServiceUpdate ;
+help.acceptTermsOfService #ee72f79a id:DataJSON = Bool ;
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+auth.signIn #bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization ;
-account.deleteAccount#418d4e0b reason:string = Bool;These methods can be used for managing consent to Telegram's Terms Of Service .
-Typically, before a user signs up by invoking auth.signUp , apps should show a pop-up (if the popup flag of the help.termsOfService method is set), asking the user to accept Telegram's terms of service; in case of denial, the user is to be returned to the initial page of the login flow.
+account.deleteAccount #418d4e0b reason:string = Bool ;These methods can be used for managing consent to Telegram's Terms Of Service .
+Typically, before a user signs up by invoking auth.signUp , apps should show a pop-up (if the popup flag of the help.termsOfService method is set), asking the user to accept Telegram's terms of service; in case of denial, the user is to be returned to the initial page of the login flow.
When signing up for the first time, the help.termsOfService is to be obtained from the auth.authorizationSignUpRequired constructor returned by the auth.signIn .
-After signing up, or when logging in as an existing user, apps are supposed to call help.getTermsOfServiceUpdate to check for any updates to the Terms of Service; this call should be repeated after expires seconds have elapsed.help.acceptTermsOfService , providing the termsOfService id JSON object ; in case of denial, clients are to delete the account using account.deleteAccount , providing Decline ToS update as deletion reason.
+After signing up, or when logging in as an existing user, apps are supposed to call help.getTermsOfServiceUpdate to check for any updates to the Terms of Service; this call should be repeated after expires seconds have elapsed.help.acceptTermsOfService , providing the termsOfService id JSON object ; in case of denial, clients are to delete the account using account.deleteAccount , providing Decline ToS update as deletion reason.
Example implementation: android (signup) , android (after login)
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+user #3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector <RestrictionReason > bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User ;
-help.support#17c6b5f6 phone_number:string user:User = help.Support;
-help.supportName#8c05f1c9 name:string = help.SupportName;
+help.support #17c6b5f6 phone_number:string user:User = help.Support ;
+help.supportName #8c05f1c9 name:string = help.SupportName ;
---functions---
-help.getSupport#9cdf08cd = help.Support;
-help.getSupportName#d360e72c = help.SupportName;These methods can be used for fetching info about Telegram's support user, that users can use to get support and ask questions about the app.help.getSupport - Will return the user object that can be used for contacting support.help.getSupportName - Will return a localized name for the support chat.
-help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
+help.getSupport #9cdf08cd = help.Support ;
+help.getSupportName #d360e72c = help.SupportName ;These methods can be used for fetching info about Telegram's support user, that users can use to get support and ask questions about the app.
+
+help.countryCode #4203c5ef flags:# country_code:string prefixes:flags.0?Vector <string > patterns:flags.1?Vector <string > = help.CountryCode ;
-help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
+help.country #c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector <help.CountryCode > = help.Country ;
-help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+help.countriesListNotModified #93cc1f32 = help.CountriesList ;
+help.countriesList #87d0759e countries:Vector <help.Country > hash:int = help.CountriesList ;
---functions---
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;help.getCountriesList #735787a8 lang_code:string hash:int = help.CountriesList ;help.getCountriesList can be used to fetch a list of localized names for all available countries and phone code patterns for logging in.
-The phone code pattern should be used when showing the login screen, or when changing phone number: for example, a pattern value of XXX XXX XXX with country_code +39 indicates that the phone field for login should accept a spaced pattern like +39 123 456 789.123 456 789) should match one of the prefixes, if any were returned.
-
+The phone code pattern should be used when showing the login screen, or when changing phone number: for example, a pattern value of XXX XXX XXX with country_code +39 indicates that the phone field for login should accept a spaced pattern like +39 123 456 789.123 456 789) should match one of the prefixes, if any were returned.
diff --git a/data/corefork.telegram.org/api/discussion.html b/data/corefork.telegram.org/api/discussion.html
index eb255e368a..8f8761e088 100644
--- a/data/corefork.telegram.org/api/discussion.html
+++ b/data/corefork.telegram.org/api/discussion.html
@@ -62,7 +62,7 @@ The discussion group can be accessed in the client by clicking on the discuss bu
The comment section of a particular post can be disabled by removing the channel post message from the discussion group.
To obtain a list of admined supergroups that a channel admin can possibly associate to a channel, use channels.getGroupsForDiscussion .legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.basic group chats must be first upgraded to supergroups before they can be set as a discussion group.channels.togglePreHistoryHidden .
To set a returned supergroup as a discussion group use channels.setDiscussionGroup .
Schema:
diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html
index ade1549b33..95b558aaac 100644
--- a/data/corefork.telegram.org/api/files.html
+++ b/data/corefork.telegram.org/api/files.html
@@ -151,7 +151,7 @@ The SHA256 hash of the file is computed, and it is passed along with the file's
Animated profile pictures are also supported, by populating the video constructor: square MPEG4 videos up to 1080x1080 are supported, 800x800 is the recommended resolution.video_start_ts is a floating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.
-
Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (legacy groups ) or channels.editPhoto (channels, supergroups ).
Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (basic groups ) or channels.editPhoto (channels, supergroups ).inputChatPhoto to reuse previously uploaded profile pictures.
There are methods available to download files which have been successfully uploaded. The schema of the types and methods used is presented below:
diff --git a/data/corefork.telegram.org/api/push-updates.html b/data/corefork.telegram.org/api/push-updates.html
index a10074c65e..87a1e3bf52 100644
--- a/data/corefork.telegram.org/api/push-updates.html
+++ b/data/corefork.telegram.org/api/push-updates.html
@@ -105,7 +105,7 @@
contact_id - Telegram user identifier of contact that joined Telegram in CONTACT_JOINED
msg_id - Message ID for new message event or reaction event
channel_id - Identifier of the channel/supergroup where the event occurred
-
chat_id - Identifier of the legacy group where the event occurred
+
chat_id - Identifier of the basic group where the event occurred
from_id - User ID where the event occurred
chat_from_broadcast_id - If the group message was sent as a channel, this field will contain the sender channel ID
chat_from_group_id - If the group message was sent as a supergroup, this field will contain the sender supergroup ID
diff --git a/data/corefork.telegram.org/api/rights.html b/data/corefork.telegram.org/api/rights.html
index d37efe86ea..70898271ec 100644
--- a/data/corefork.telegram.org/api/rights.html
+++ b/data/corefork.telegram.org/api/rights.html
@@ -45,18 +45,18 @@
Channels and supergroups allow setting granular permissions both for admins and specific users.
-Channels, supergroups and legacy groups also allow setting global granular permissions for users.
+
Channels, supergroups and basic groups also allow setting global granular permissions for users.
They can be modified as follows:
channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup.
-Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.
+
Basic groups do not allow setting granular admin permissions,
messages.editChatAdmin has to be used, instead.
Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).
channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things.
-Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser : however, setting global granular permissions with legacy groups is supported .
+
Basic groups do not allow setting granular user permissions for single users, single users can only be removed from groups using
messages.deleteChatUser : however, setting
global granular permissions with basic groups is supported .
Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.
-
messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel , supergroup or legacy group , to restrict them from doing certain things.
+
messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel , supergroup or basic group , to restrict them from doing certain things.
Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.
diff --git a/data/corefork.telegram.org/api/updates.html b/data/corefork.telegram.org/api/updates.html
index 6e6100be87..950c188d96 100644
--- a/data/corefork.telegram.org/api/updates.html
+++ b/data/corefork.telegram.org/api/updates.html
@@ -72,7 +72,7 @@
All boxes are completely independent, and each pts sequence is tied to just one box (see below).
Update object may contain info about multiple events (for example, updateDeleteMessages ).
That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).
-
Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence .
+
Each channel and supergroup has its message box and its event sequence as a result; private chats and basic groups of one user have another common event sequence .
Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence .
To recap, the client has to take care of the integrity of the following sequences to properly handle updates:
diff --git a/data/corefork.telegram.org/bots/2-0-intro.html b/data/corefork.telegram.org/bots/2-0-intro.html
index 47431eca4e..1ac9d5346c 100644
--- a/data/corefork.telegram.org/bots/2-0-intro.html
+++ b/data/corefork.telegram.org/bots/2-0-intro.html
@@ -4,11 +4,11 @@
Introducing Bot API 2.0
-Howdy! This text assumes that you‘re familiar with Telegram’s bot platform.Introduction to Bots
+Howdy! This text assumes that you're familiar with Telegram's bot platform.Introduction to Bots
-
Today we‘re introducing the biggest change to Telegram’s Bot Platform since June 2015. These new tools will help you create fluid and intuitive interfaces for your bots. And bots are becoming a lot more capable. They can now send any type of content supported on Telegram, provide location-based services and integrate with other services deeply based on users' phone numbers.
+
Today we're introducing the biggest change to Telegram's Bot Platform since June 2015. These new tools will help you create fluid and intuitive interfaces for your bots. And bots are becoming a lot more capable. They can now send any type of content supported on Telegram, provide location-based services and integrate with other services deeply based on users' phone numbers.
If you'd like a more concise changelog, you can find one in the Bot API Manual
To begin with, we're adding a new type of keyboard that is integrated directly into the message it belongs to. Inline keyboards are available for messages sent both in chat mode and inline mode.
@@ -87,9 +87,9 @@ If this is not the case, kindly check out our…">
-Sample bot @sticker – This sticker search bot offers a ‘switch to inline’ button to teach users how to use it in inline mode.
+Sample bot @sticker – This sticker search bot offers a 'switch to inline' button to teach users how to use it in inline mode.
Since inline keyboards don‘t send additional messages to the chat, it made sense to give bots a way of manipulating their existing messages, so that they don’t have to send a new message each time they need to update something. This helps reduce clutter and build more fluid interfaces.
+Since inline keyboards don't send additional messages to the chat, it made sense to give bots a way of manipulating their existing messages, so that they don't have to send a new message each time they need to update something. This helps reduce clutter and build more fluid interfaces.
@@ -103,7 +103,7 @@ If this is not the case, kindly check out our…">
Manual: Updating messages »
Some bots need extra data from the user to work properly. For example, knowing the user‘s location helps provide more relevant geo-specific results. The user’s phone number can be very useful for integrations with other services, like banks, etc.
+Some bots need extra data from the user to work properly. For example, knowing the user's location helps provide more relevant geo-specific results. The user's phone number can be very useful for integrations with other services, like banks, etc.
We've added an easy way for bots to ask the user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.
@@ -133,20 +133,20 @@ If this is not the case, kindly check out our…">
You can now display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query
-Sample bots @youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.
+You can now display a special 'Switch to PM' button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query
+Sample bots @youtube – Shows a 'Sign in to YouTube' button, then suggests personalized results.
Manual: Switch to PM
Since sending content via inline bots works differently from sending ordinary messages, we‘ve changed the interface a little. There’s hardly a more effective way of explaining that there‘s no need to hit ’Send':
+Since sending content via inline bots works differently from sending ordinary messages, we've changed the interface a little. There's hardly a more effective way of explaining that there's no need to hit 'Send':
-Tapping on the cross icon once will clear the query, tapping twice will give the ‘Send’ button back to the user.
+Tapping on the cross icon once will clear the query, tapping twice will give the 'Send' button back to the user.
As a dessert, we‘re beginning to roll out tools that will allow you to create bot solutions for group admins. As the first step, we’ve added methods to remove members from groups and supergroups.
+As a dessert, we're beginning to roll out tools that will allow you to create bot solutions for group admins. As the first step, we've added methods to remove members from groups and supergroups.
Manual: Group management »
diff --git a/data/corefork.telegram.org/bots/api-changelog.html b/data/corefork.telegram.org/bots/api-changelog.html
index 906c9f0500..8c884e7557 100644
--- a/data/corefork.telegram.org/bots/api-changelog.html
+++ b/data/corefork.telegram.org/bots/api-changelog.html
@@ -47,22 +47,23 @@ To learn how to create…">
-The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.Introduction to Bots »
+The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
+To learn how to create and set up a bot, please consult our Introduction to Bots »
You will find all changes to our Bot API
-
+
Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk
-
+
Bot API 6.0
-login_url inline keyboard buttons.
+login_url inline keyboard buttons.
-
+
Bot API 5.7
-
+
Bot API 5.6
Improved support for Protected Content .
Added the parameter protect_content to the methods sendMessage , sendPhoto , sendVideo , sendAnimation , sendAudio , sendDocument , sendSticker , sendVideoNote , sendVoice , sendLocation , sendVenue , sendContact , sendPoll , sendDice , sendInvoice , sendGame , sendMediaGroup , copyMessage , forwardMessage to allow sending messages with protected content to any chat.
Added support for spoiler entities , which will work in Telegram versions released after December 30, 2021. Older clients will display unsupported message .
-Added new MessageEntity type “spoiler”.
+Added new MessageEntity type "spoiler".
Added the ability to specify spoiler entities using HTML and MarkdownV2 formatting options.
-
+
Bot API 5.5
-Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
+Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message .
Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
@@ -103,7 +105,7 @@ To learn how to create…">
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
Added the the parameter 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 ).
@@ -115,10 +117,11 @@ To learn how to create…">
-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.
+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
@@ -126,8 +129,8 @@ To learn how to create…">
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, read more on the blog .
+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, read more on the blog .
Custom Placeholders
@@ -142,35 +145,39 @@ To learn how to create…">
-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.
+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
Support for Payments 2.0 , see this manual for more details about the Bot Payments API .
Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
Allowed sending invoices to group, supergroup and channel chats.
Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
-The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
+The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
Added the field chat_type to the class InlineQuery , containing the type of the chat, from which the inline request was sent.
Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message .
-Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
+Fixed an error in sendChatAction documentation to correctly mention "record_voice" and "upload_voice" instead of "record_audio" and "upload_audio" for related to voice note actions. Old action names will still work for backward compatibility.
-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 .
+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 .
-
+
-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.
+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
@@ -199,14 +206,15 @@ To learn how to create…">
-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.
+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 source code is now available at telegram-bot-api . You can now run your own Bot API server locally, boosting your bots' performance.
+Bot API source code is now available at telegram-bot-api . You can now run your own Bot API server locally, boosting your bots' performance.
Added the method logOut , which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
Added the method close , which can be used to close the bot instance before moving it from one local server to another.
@@ -222,7 +230,7 @@ To learn how to create…">
Working with Groups
-The getChat request now returns the user's bio for private chats if available.
+The getChat request now returns the user's bio for private chats if available.
The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
The getChat request now returns the location to which the supergroup is connected (see Local Groups ). Added the class ChatLocation to represent the location.
Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
@@ -245,7 +253,7 @@ To learn how to create…">
Live Locations
Added the field live_period to the class Location , representing a maximum period for which the live location can be updated.
-Added support for live location heading : added the field heading to the classes Location , InlineQueryResultLocation , InputLocationMessageContent and the parameter heading to the methods sendLocation and editMessageLiveLocation .
+Added support for live location [heading](https://en.wikipedia.org/wiki/Heading_(navigation) ;): added the field heading to the classes Location , InlineQueryResultLocation , InputLocationMessageContent and the parameter heading to the methods sendLocation and editMessageLiveLocation .
Added support for proximity alerts in live locations: added the field proximity_alert_radius to the classes Location , InlineQueryResultLocation , InputLocationMessageContent and the parameter proximity_alert_radius to the methods sendLocation and editMessageLiveLocation .
Added the type ProximityAlertTriggered and the field proximity_alert_triggered to the class Message .
Added possibility to specify the horizontal accuracy of a location. Added the field horizontal_accuracy to the classes Location , InlineQueryResultLocation , InputLocationMessageContent and the parameter horizontal_accuracy to the methods sendLocation and editMessageLiveLocation .
@@ -269,14 +277,14 @@ To learn how to create…">
Supported the new football and slot machine animations for the random dice . Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice .
-Bot API 4.9
Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
Supported video thumbnails for inline GIF and MPEG4 animations.
Supported the new basketball animation for the random dice . Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice .
-Bot API 4.8
Supported explanations for Quizzes 2.0 . Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll .
@@ -286,19 +294,19 @@ To learn how to create…">
Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice .
Added the field emoji to the Dice object.
-Bot API 4.7
-Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die . But it's awkward, and we decided to help it change. One dice at a time!)
+Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the "proper" singular of die . But it's awkward, and we decided to help it change. One dice at a time!)
Added the field dice to the Message object.
-Added the method getMyCommands for getting the current list of the bot's commands.
-Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather .
+Added the method getMyCommands for getting the current list of the bot's commands.
+Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather .
Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet .
Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet .
Added the field thumb to the StickerSet object.
Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb .
-Bot API 4.6
Supported Polls 2.0 .
@@ -310,19 +318,19 @@ To learn how to create…">
Added more information about the bot in response to the getMe request: added the fields can_join_groups , can_read_all_group_messages and supports_inline_queries to the User object.
Added the optional field language to the MessageEntity object.
-Bot API 4.5
Added support for two new MessageEntity types, underline and strikethrough .
Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
Added a new parse mode, MarkdownV2 , which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
-Added the field file_unique_id to the objects Animation , Audio , Document , PassportFile , PhotoSize , Sticker , Video , VideoNote , Voice , File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto . The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
+Added the field file_unique_id to the objects Animation , Audio , Document , PassportFile , PhotoSize , Sticker , Video , VideoNote , Voice , File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto . The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
Added the field custom_title to the ChatMember object.
Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
Added the field slow_mode_delay to the Chat object.
-Bot API 4.4
Added support for animated stickers is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker .
@@ -330,49 +338,48 @@ To learn how to create…">
The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info , can_invite_users , can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions . The old way of passing parameters will keep working for a while for backward compatibility.
-Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
-Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
+Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
+Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
-All webhook requests from the Bot API are now coming from the subnets 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 .
+All webhook requests from the Bot API are now coming from the subnets 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 .
As of the next Bot API update (version 4.5 ), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
-Bot API 4.3
Added support for Seamless Telegram Login
Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
-
+
Also in this update:
Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url , login_url , switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
Bots now receive the edited_message Update even if only Message.reply_markup has changed.
Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
-Don't forget that starting in July 2019 , webhook requests from Bot API will be coming from the subnets 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 .
+Don't forget that starting in July 2019 , webhook requests from Bot API will be coming from the subnets 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
Added support for native polls: added the object Poll , the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
-Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage , and receive the pinned group message in Chat object.
+Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage , and receive the pinned group message in Chat object.
Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
-Starting in July 2019, webhook requests from Bot API will be coming from the subnets 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 .
+Starting in July 2019, webhook requests from Bot API will be coming from the subnets 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 .
Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
-Bot API 4.1
-Bot API 4.0 .
Added support for Telegram Passport blog and the manual for details.
@@ -384,35 +391,35 @@ To learn how to create…">
Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
Added two new MessageEntity types: cashtag and phone_number .
Added support for Foursquare venues: added the new field foursquare_type to the objects Venue , InlineQueryResultVenue and InputVenueMessageContent , and the parameter foursquare_type to the sendVenue method.
-You can now create inline mentions of users, who have pressed your bot's callback buttons.
+You can now create inline mentions of users, who have pressed your bot's callback buttons.
You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
Added vCard support when sharing contacts: added the field vcard to the objects Contact , InlineQueryResultContact , InputContactMessageContent and the method sendContact .
-Bot API 3.6 .
Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML ) when you provide a caption.
-In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
-Added the new field connected_website to Message . The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
+In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
+Added the new field connected_website to Message . The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
-Bot API 3.5 .
-Bot API 3.4 .
-Bot API 3.3 .
Bots can now mention users via inline mentions , without using usernames.
@@ -420,13 +427,13 @@ To learn how to create…">
Added the new fields author_signature and forward_signature to the Message object.
Added the new field is_bot to the User object.
-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:
Added new methods restrictChatMember and promoteChatMember to manage users and admins, added new parameter until_date to kickChatMember for temporary bans.
@@ -434,10 +441,10 @@ To learn how to create…">
Added the new fields photo , description and invite_link to the Chat object.
Added the new fields until_date , can_be_edited , can_change_info , can_post_messages , can_edit_messages , can_delete_messages , can_invite_users , can_restrict_members , can_pin_messages , can_promote_members , can_send_messages , can_send_media_messages , can_send_other_messages and can_add_web_page_previews to the ChatMember object.
-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.
+See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.
Your bot can now accept payments for goods and services via Telegram.
Added new kinds of updates , shipping_query and pre_checkout_query , and new types of message content, invoice and successful_payment .
@@ -451,7 +458,7 @@ To learn how to create…">
NEW Multilingual Bots
-The User object now may have a language_code field that contains the IETF language tag of the user's language.
+The User object now may have a language_code field that contains the IETF language tag of the user's language.
Thanks to this, your bot can now offer localized responses to users that speak different languages.
More power to admin bots
@@ -465,29 +472,44 @@ To learn how to create…">
Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif .
-Introducing Bot API 2.3.1 , a nifty little update that will give you more control over how your bot gets its updates.
-Use the new field max_connections in setWebhook to optimize your bot's server load
+Use the new field max_connections in setWebhook to optimize your bot's server load
Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
deleteWebhook moved out of setWebhook to get a whole separate method for itself.
-Bot API 2.3
-Modified bot privacy mode
-Your bot can now get updates about posts in channels . Added new fields channel_post and edited_channel_post to Update .
+
+Modified bot privacy mode
-You can now update high scores to a lower value by using the new force parameter in setGameScore . Handy for punishing cheaters or fixing errors in your game's High Score table.
+
+Your bot can now get updates about posts in channels . Added new fields channel_post and edited_channel_post to Update .
+
+
+You can now update high scores to a lower value by using the new force parameter in setGameScore . Handy for punishing cheaters or fixing errors in your game's High Score table.
+
+
+Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
+
+
+The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
+
+
+Added the new field forward_from_message_id to Message .
+
+
+Added the new parameter cache_time to answerCallbackQuery . Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
+
+
+Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
-Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
-The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
-Added the new field forward_from_message_id to Message .
-Added the new parameter cache_time to answerCallbackQuery . Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
-Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
-Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.this user-friendly blog post
+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
Other changes
-Making life easier for webhook users. Added a detailed Guide to All Things Webhook
-New method getWebhookInfo to check current webhook status.
+
+Making life easier for webhook users. Added a detailed Guide to All Things Webhook
-Added the option to specify an HTTP URL for a file in all methods where InputFile or file_id can be used (except voice messages). Telegram will get the file from the specified URL and send it to the user. Files must be smaller than 5 MB for photos and smaller than 20 MB for all other types of content.
+
+New method getWebhookInfo to check current webhook status.
+
+
+Added the option to specify an HTTP URL for a file in all methods where InputFile or file_id can be used (except voice messages). Telegram will get the file from the specified URL and send it to the user. Files must be smaller than 5 MB for photos and smaller than 20 MB for all other types of content.
+
+
+Use the new url parameter in answerCallbackQuery to create buttons that open your bot with user-specific parameters.
+
+
+Added new field switch_inline_query_current_chat in InlineKeyboardButton .
+
+
+Added caption fields to sendAudio , sendVoice , InlineQueryResultAudio , InlineQueryResultVoice , InlineQueryResultCachedAudio , and InlineQueryResultCachedVoice .
-Use the new url parameter in answerCallbackQuery to create buttons that open your bot with user-specific parameters.
-Added new field switch_inline_query_current_chat in InlineKeyboardButton .
-Added caption fields to sendAudio , sendVoice , InlineQueryResultAudio , InlineQueryResultVoice , InlineQueryResultCachedAudio , and InlineQueryResultCachedVoice .
New field all_members_are_administrators in the Chat object.
Certain server responses may now contain the new parameters
-
-Bot API 2.1. Added more tools for group administrator bots. Your bot can now get a list of administrators and members count in a group, check a user's current status (administrator, creator, left the group, kicked from the group), and leave a group.Bot API 2.1. Added more tools for group administrator bots. Your bot can now get a list of administrators and members count in a group, check a user's current status (administrator, creator, left the group, kicked from the group), and leave a group.Added new methods: getChat , leaveChat , getChatAdministrators , getChatMember , getChatMembersCount .
Added support for edited messages and new mentions from Telegram v.3.9. New fields: edited_message in Update , edit_date in Message , user in MessageEntity . New value text_mention for the type field in MessageEntity .
-
Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
Added the field forward_from_chat to the Message object for messages forwarded from channels.
-Introducing Bot API 2.0 . Check out this page for a review of this major update.
-
Added the disable_notification parameter to all methods that send messages or any kind.
Removed backward compatibility from the method sendAudio . Voice messages now must be sent using the method sendVoice . There is no more need to specify a non-empty title or performer while sending the audio by file_id .
-
-By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
+By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
-
You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult , new field chosen_inline_result to the Update object.
-
-Added support for supergroups . The Type field in the Chat object can now contain 'supergroup'.
+Added support for supergroups . The Type field in the Chat object can now contain 'supergroup'.
New optional fields added to the Message object: supergroup_chat_created , migrate_to_chat_id , migrate_from_chat_id and channel_chat_created .
-
Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
The Chat field in the Message is now of the new type Chat .
-You can now pass a channel username (in the format @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).
+You can now pass a channel username (in the format @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).
-
Bots can now download files and media sent by users.
Added getFile and File .
-
-You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
+You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
Added very basic markdown support . New field parse_mode added to sendMessage . For the moment messages with markdown will be displayed correctly only in Telegram for Android . Other official apps will catch up soon.
-
Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
You can now make new requests when responding to webhook updates.
-
Added new type Voice sendVoice
Earlier Audio sendAudio sendAudio sendVoice
Added optional fields performer , title to the Audio sendAudio
Added optional field voice to the Message
-
The thumb field is now optional for Video , Sticker and Document objects
The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
caption and duration optional fields have been added to the sendVideo method.Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
-The bot platform was officially launched .
Back to the Bot API Manual »
-
-
+
diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html b/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html
index c6b77aaf73..2ae09da9b8 100644
--- a/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html
+++ b/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html
@@ -61,8 +61,8 @@
BotCommandScope
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChats.html b/data/corefork.telegram.org/constructor/botCommandScopeChats.html
index c7fb5e6750..6d2cf43da1 100644
--- a/data/corefork.telegram.org/constructor/botCommandScopeChats.html
+++ b/data/corefork.telegram.org/constructor/botCommandScopeChats.html
@@ -61,8 +61,8 @@
BotCommandScope
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html b/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html
index 227751ac0a..9a312de623 100644
--- a/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html
+++ b/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html
@@ -76,8 +76,8 @@
BotCommandScope
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html
index b1dc09e6ba..170e963d88 100644
--- a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html
+++ b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html
@@ -81,8 +81,8 @@
BotCommandScope
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/channel.html b/data/corefork.telegram.org/constructor/channel.html
index 8d087bb40c..22c77371e6 100644
--- a/data/corefork.telegram.org/constructor/channel.html
+++ b/data/corefork.telegram.org/constructor/channel.html
@@ -157,6 +157,16 @@
Whether this channel or group is protected , thus does not allow forwarding messages from it
+join_to_send flags .28?true
+
+
+join_request flags .29?true
+
+
id long ID of the channel
@@ -218,8 +228,8 @@
In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.
diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html
index 9264e2f76c..fda9bf0d09 100644
--- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html
+++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html
@@ -76,8 +76,8 @@
ChannelAdminLogEventAction
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/channelFull.html b/data/corefork.telegram.org/constructor/channelFull.html
index c50d4ae9b0..a056fc15db 100644
--- a/data/corefork.telegram.org/constructor/channelFull.html
+++ b/data/corefork.telegram.org/constructor/channelFull.html
@@ -299,8 +299,8 @@
Groups can be associated to a channel as a discussion group , to allow users to discuss about posts.
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram allows pinning multiple messages on top of a specific chat.
diff --git a/data/corefork.telegram.org/constructor/chat.html b/data/corefork.telegram.org/constructor/chat.html
index 0c9580f39b..e734eff91b 100644
--- a/data/corefork.telegram.org/constructor/chat.html
+++ b/data/corefork.telegram.org/constructor/chat.html
@@ -77,11 +77,6 @@
Whether the current user is the creator of the group
-kicked flags .1?true Whether the current user was kicked from the group
-
-
left flags .2?true Whether the current user has left the group
@@ -156,8 +151,8 @@
Chat
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.
diff --git a/data/corefork.telegram.org/constructor/chatAdminRights.html b/data/corefork.telegram.org/constructor/chatAdminRights.html
index 174c33e800..75760d4ff5 100644
--- a/data/corefork.telegram.org/constructor/chatAdminRights.html
+++ b/data/corefork.telegram.org/constructor/chatAdminRights.html
@@ -131,8 +131,8 @@
ChatAdminRights
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/chatBannedRights.html b/data/corefork.telegram.org/constructor/chatBannedRights.html
index 29bdbd7ec2..802f11ed8b 100644
--- a/data/corefork.telegram.org/constructor/chatBannedRights.html
+++ b/data/corefork.telegram.org/constructor/chatBannedRights.html
@@ -141,8 +141,8 @@
ChatBannedRights
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/chatFull.html b/data/corefork.telegram.org/constructor/chatFull.html
index 9ed625e2a8..ad2eedcbe7 100644
--- a/data/corefork.telegram.org/constructor/chatFull.html
+++ b/data/corefork.telegram.org/constructor/chatFull.html
@@ -4,10 +4,10 @@
chatFull
chatFull
- Full info about a legacy group .
+
Full info about a basic group .
@@ -178,8 +178,8 @@
Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
ChatInvite
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
diff --git a/data/corefork.telegram.org/constructor/config.html b/data/corefork.telegram.org/constructor/config.html
index af19e30acf..e9410b858f 100644
--- a/data/corefork.telegram.org/constructor/config.html
+++ b/data/corefork.telegram.org/constructor/config.html
@@ -337,8 +337,8 @@
Binding temporary authorization key to permanent ones.
Returns current configuration, including data center configuration.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Forwards messages by their IDs.
diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html
index 30f46ef3c3..bb20eebb69 100644
--- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html
+++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html
@@ -61,8 +61,8 @@
InlineQueryPeerType
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html
index 9c86c5bcee..636043383f 100644
--- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html
+++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html
@@ -61,8 +61,8 @@
InlineQueryPeerType
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html
index 4d14125b9a..0a057f71d0 100644
--- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html
+++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html
@@ -61,8 +61,8 @@
InlineQueryPeerType
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html
index 25b2e89d56..3a121e9b8a 100644
--- a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html
+++ b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html
@@ -61,8 +61,8 @@
InputNotifyPeer
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html
index 038cf84e68..24b3ff9db3 100644
--- a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html
+++ b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html
@@ -81,8 +81,8 @@
MessageAction
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html
index aecdc0b700..6287b64d4d 100644
--- a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html
+++ b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html
@@ -76,8 +76,8 @@
MessageAction
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/messageReplyHeader.html b/data/corefork.telegram.org/constructor/messageReplyHeader.html
index dcf6ef6fa2..1cddd6f772 100644
--- a/data/corefork.telegram.org/constructor/messageReplyHeader.html
+++ b/data/corefork.telegram.org/constructor/messageReplyHeader.html
@@ -72,6 +72,11 @@
Flags, see TL conditional fields
+reply_to_scheduled flags .2?true
+
+
reply_to_msg_id int ID of message to which this message is replying
diff --git a/data/corefork.telegram.org/constructor/messages.chatFull b/data/corefork.telegram.org/constructor/messages.chatFull
index a3e6777d8a..6391be488f 100644
--- a/data/corefork.telegram.org/constructor/messages.chatFull
+++ b/data/corefork.telegram.org/constructor/messages.chatFull
@@ -4,10 +4,10 @@
messages.chatFull
messages.chatFull
- Full info about a channel , supergroup , gigagroup or legacy group .
+
Full info about a channel , supergroup , gigagroup or basic group .
@@ -86,8 +86,8 @@
messages.ChatFull
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateChannelParticipant.html b/data/corefork.telegram.org/constructor/updateChannelParticipant.html
index 45428eb550..d1aa21ffc0 100644
--- a/data/corefork.telegram.org/constructor/updateChannelParticipant.html
+++ b/data/corefork.telegram.org/constructor/updateChannelParticipant.html
@@ -116,8 +116,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to subscribe to updates and handle them properly.
diff --git a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html
index 906552275c..7d2b365e1d 100644
--- a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html
+++ b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html
@@ -81,8 +81,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html
index cec92cc766..b162efbb41 100644
--- a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html
+++ b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html
@@ -98,8 +98,8 @@
Telegram allows commenting on a channel post or on a generic supergroup message , thanks to message threads.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateChannelWebPage.html b/data/corefork.telegram.org/constructor/updateChannelWebPage.html
index af23e17de1..71a29e45ab 100644
--- a/data/corefork.telegram.org/constructor/updateChannelWebPage.html
+++ b/data/corefork.telegram.org/constructor/updateChannelWebPage.html
@@ -91,8 +91,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to subscribe to updates and handle them properly.
diff --git a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html
index 8e513a4c22..3529a1259e 100644
--- a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html
+++ b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html
@@ -86,8 +86,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateChatParticipant.html b/data/corefork.telegram.org/constructor/updateChatParticipant.html
index a27de97d22..6908e35c82 100644
--- a/data/corefork.telegram.org/constructor/updateChatParticipant.html
+++ b/data/corefork.telegram.org/constructor/updateChatParticipant.html
@@ -116,8 +116,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to subscribe to updates and handle them properly.
diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html
index b625c76747..c65ec75661 100644
--- a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html
+++ b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html
@@ -4,10 +4,10 @@
updateChatParticipantAdmin
updateChatParticipantAdmin
- Admin permissions of a user in a legacy group were changed
+
Admin permissions of a user in a basic group were changed
@@ -91,8 +91,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to subscribe to updates and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html
index 6c469ff68f..10ba78853b 100644
--- a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html
+++ b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html
@@ -88,8 +88,8 @@
How to subscribe to updates and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateGroupCall.html b/data/corefork.telegram.org/constructor/updateGroupCall.html
index 3fbcafde40..10c8b8f341 100644
--- a/data/corefork.telegram.org/constructor/updateGroupCall.html
+++ b/data/corefork.telegram.org/constructor/updateGroupCall.html
@@ -81,8 +81,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html
index dde9794235..f27f56d58a 100644
--- a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html
+++ b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html
@@ -88,8 +88,8 @@
How to subscribe to updates and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateNewMessage.html b/data/corefork.telegram.org/constructor/updateNewMessage.html
index 34bedd9820..c7fd4d4a12 100644
--- a/data/corefork.telegram.org/constructor/updateNewMessage.html
+++ b/data/corefork.telegram.org/constructor/updateNewMessage.html
@@ -4,10 +4,10 @@
updateNewMessage
updateNewMessage
- New message in a private chat or in a legacy group .
+
New message in a private chat or in a basic group .
diff --git a/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html b/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html
index 78448cf1f0..e3be7ddf38 100644
--- a/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html
+++ b/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html
@@ -103,8 +103,8 @@
How to subscribe to updates and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram allows commenting on a channel post or on a generic supergroup message , thanks to message threads.
diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html
index 8cf95d0c02..b7acb0693c 100644
--- a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html
+++ b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html
@@ -86,8 +86,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram allows commenting on a channel post or on a generic supergroup message , thanks to message threads.
diff --git a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html
index 946ba0e3c0..824eaf5119 100644
--- a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html
+++ b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html
@@ -105,8 +105,8 @@
Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
How to subscribe to updates and handle them properly.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html
index 9029248261..94b51e82db 100644
--- a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html
+++ b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html
@@ -81,8 +81,8 @@
Update
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/account.initTakeoutSession b/data/corefork.telegram.org/method/account.initTakeoutSession
index 6126560c3f..562989a6be 100644
--- a/data/corefork.telegram.org/method/account.initTakeoutSession
+++ b/data/corefork.telegram.org/method/account.initTakeoutSession
@@ -86,7 +86,7 @@
message_chats flags .2?true Whether to export messages in legacy groups
+Whether to export messages in basic groups
message_megagroups How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.checkUsername b/data/corefork.telegram.org/method/channels.checkUsername
index d922dafd34..9d20ec5af0 100644
--- a/data/corefork.telegram.org/method/channels.checkUsername
+++ b/data/corefork.telegram.org/method/channels.checkUsername
@@ -116,8 +116,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.convertToGigagroup b/data/corefork.telegram.org/method/channels.convertToGigagroup
index ebee3a681b..bc96ae7c14 100644
--- a/data/corefork.telegram.org/method/channels.convertToGigagroup
+++ b/data/corefork.telegram.org/method/channels.convertToGigagroup
@@ -106,8 +106,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel
index 8da3be864c..9770c01d71 100644
--- a/data/corefork.telegram.org/method/channels.createChannel
+++ b/data/corefork.telegram.org/method/channels.createChannel
@@ -156,8 +156,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats » .
diff --git a/data/corefork.telegram.org/method/channels.deleteChannel b/data/corefork.telegram.org/method/channels.deleteChannel
index 6edcc3584d..374c85bc7c 100644
--- a/data/corefork.telegram.org/method/channels.deleteChannel
+++ b/data/corefork.telegram.org/method/channels.deleteChannel
@@ -126,8 +126,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.deleteHistory b/data/corefork.telegram.org/method/channels.deleteHistory
index 0945285ad7..1b1c217ab7 100644
--- a/data/corefork.telegram.org/method/channels.deleteHistory
+++ b/data/corefork.telegram.org/method/channels.deleteHistory
@@ -106,8 +106,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.deleteMessages b/data/corefork.telegram.org/method/channels.deleteMessages
index f567cc99ab..8a6f3bd206 100644
--- a/data/corefork.telegram.org/method/channels.deleteMessages
+++ b/data/corefork.telegram.org/method/channels.deleteMessages
@@ -116,8 +116,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.editAdmin b/data/corefork.telegram.org/method/channels.editAdmin
index 504342d1eb..ad6b91f8c1 100644
--- a/data/corefork.telegram.org/method/channels.editAdmin
+++ b/data/corefork.telegram.org/method/channels.editAdmin
@@ -227,8 +227,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.editBanned b/data/corefork.telegram.org/method/channels.editBanned
index d11ad7f597..196c73b697 100644
--- a/data/corefork.telegram.org/method/channels.editBanned
+++ b/data/corefork.telegram.org/method/channels.editBanned
@@ -157,8 +157,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.editLocation b/data/corefork.telegram.org/method/channels.editLocation
index aafd343a26..9692d15dfe 100644
--- a/data/corefork.telegram.org/method/channels.editLocation
+++ b/data/corefork.telegram.org/method/channels.editLocation
@@ -116,8 +116,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.editPhoto b/data/corefork.telegram.org/method/channels.editPhoto
index 9cc159bd05..7a03afca6a 100644
--- a/data/corefork.telegram.org/method/channels.editPhoto
+++ b/data/corefork.telegram.org/method/channels.editPhoto
@@ -147,8 +147,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to handle file references.
diff --git a/data/corefork.telegram.org/method/channels.editTitle b/data/corefork.telegram.org/method/channels.editTitle
index 55bba7052f..04993ac038 100644
--- a/data/corefork.telegram.org/method/channels.editTitle
+++ b/data/corefork.telegram.org/method/channels.editTitle
@@ -132,8 +132,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.exportMessageLink b/data/corefork.telegram.org/method/channels.exportMessageLink
index a6e7cfb189..55bb47610b 100644
--- a/data/corefork.telegram.org/method/channels.exportMessageLink
+++ b/data/corefork.telegram.org/method/channels.exportMessageLink
@@ -130,8 +130,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getAdminLog b/data/corefork.telegram.org/method/channels.getAdminLog
index b6113af50a..38a7354eb8 100644
--- a/data/corefork.telegram.org/method/channels.getAdminLog
+++ b/data/corefork.telegram.org/method/channels.getAdminLog
@@ -152,8 +152,8 @@
How to fetch results from large lists of objects.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels
index 998558e45a..d9b47667a4 100644
--- a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels
+++ b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels
@@ -111,8 +111,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Check if a username is free and can be assigned to a channel/supergroup
diff --git a/data/corefork.telegram.org/method/channels.getChannels b/data/corefork.telegram.org/method/channels.getChannels
index f93db2a58a..a5e6dbd4fd 100644
--- a/data/corefork.telegram.org/method/channels.getChannels
+++ b/data/corefork.telegram.org/method/channels.getChannels
@@ -112,8 +112,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getFullChannel b/data/corefork.telegram.org/method/channels.getFullChannel
index 5161120dfb..19b5c4ea60 100644
--- a/data/corefork.telegram.org/method/channels.getFullChannel
+++ b/data/corefork.telegram.org/method/channels.getFullChannel
@@ -116,8 +116,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion
index dee93359ec..7358b1b622 100644
--- a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion
+++ b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion
@@ -43,7 +43,7 @@
channels.getGroupsForDiscussion
Get all groups that can be used as discussion groups .
-
Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
Returned basic group chats must be first upgraded to supergroups before they can be set as a discussion group.channels.togglePreHistoryHidden , first.
@@ -68,8 +68,8 @@ To set a returned supergroup as a discussion group, access to its old messages m
Groups can be associated to a channel as a discussion group , to allow users to discuss about posts.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Hide/unhide message history for new channel/supergroup users
diff --git a/data/corefork.telegram.org/method/channels.getLeftChannels b/data/corefork.telegram.org/method/channels.getLeftChannels
index 7380acc1cd..24e2eaae7f 100644
--- a/data/corefork.telegram.org/method/channels.getLeftChannels
+++ b/data/corefork.telegram.org/method/channels.getLeftChannels
@@ -98,8 +98,8 @@
How to fetch results from large lists of objects.
-
-
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getMessages b/data/corefork.telegram.org/method/channels.getMessages
index d9b878ccd9..01766687d5 100644
--- a/data/corefork.telegram.org/method/channels.getMessages
+++ b/data/corefork.telegram.org/method/channels.getMessages
@@ -124,8 +124,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getParticipant b/data/corefork.telegram.org/method/channels.getParticipant
index 8090bd5951..efb579ad05 100644
--- a/data/corefork.telegram.org/method/channels.getParticipant
+++ b/data/corefork.telegram.org/method/channels.getParticipant
@@ -131,8 +131,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.getParticipants b/data/corefork.telegram.org/method/channels.getParticipants
index d47f4bebc9..ac56de1083 100644
--- a/data/corefork.telegram.org/method/channels.getParticipants
+++ b/data/corefork.telegram.org/method/channels.getParticipants
@@ -129,8 +129,8 @@
How to fetch results from large lists of objects.
-
-How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.leaveChannel b/data/corefork.telegram.org/method/channels.leaveChannel
index db29fef609..24c2eb9dfc 100644
--- a/data/corefork.telegram.org/method/channels.leaveChannel
+++ b/data/corefork.telegram.org/method/channels.leaveChannel
@@ -132,8 +132,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.readHistory b/data/corefork.telegram.org/method/channels.readHistory
index e405a49674..8f163b0195 100644
--- a/data/corefork.telegram.org/method/channels.readHistory
+++ b/data/corefork.telegram.org/method/channels.readHistory
@@ -111,8 +111,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.readMessageContents b/data/corefork.telegram.org/method/channels.readMessageContents
index 5657b5891e..d28daeb4fb 100644
--- a/data/corefork.telegram.org/method/channels.readMessageContents
+++ b/data/corefork.telegram.org/method/channels.readMessageContents
@@ -111,8 +111,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/channels.toggleSlowMode b/data/corefork.telegram.org/method/channels.toggleSlowMode
index 18e57ea89a..15e17503b6 100644
--- a/data/corefork.telegram.org/method/channels.toggleSlowMode
+++ b/data/corefork.telegram.org/method/channels.toggleSlowMode
@@ -116,8 +116,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/messages.deleteChat b/data/corefork.telegram.org/method/messages.deleteChat
index 350e565fd6..445398cfa1 100644
--- a/data/corefork.telegram.org/method/messages.deleteChat
+++ b/data/corefork.telegram.org/method/messages.deleteChat
@@ -106,8 +106,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/messages.editChatAbout b/data/corefork.telegram.org/method/messages.editChatAbout
index 5c0b4a5046..546d84d991 100644
--- a/data/corefork.telegram.org/method/messages.editChatAbout
+++ b/data/corefork.telegram.org/method/messages.editChatAbout
@@ -142,8 +142,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/messages.editChatAdmin b/data/corefork.telegram.org/method/messages.editChatAdmin
index 0991c09573..5ade77be8a 100644
--- a/data/corefork.telegram.org/method/messages.editChatAdmin
+++ b/data/corefork.telegram.org/method/messages.editChatAdmin
@@ -4,10 +4,10 @@
messages.editChatAdmin
messages.editChatAdmin
- Make a user admin in a legacy group .
+
Make a user admin in a basic group .
@@ -121,8 +121,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/messages.getDiscussionMessage b/data/corefork.telegram.org/method/messages.getDiscussionMessage
index d7bc8dde5e..838afca782 100644
--- a/data/corefork.telegram.org/method/messages.getDiscussionMessage
+++ b/data/corefork.telegram.org/method/messages.getDiscussionMessage
@@ -110,8 +110,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram allows commenting on a channel post or on a generic supergroup message , thanks to message threads.
diff --git a/data/corefork.telegram.org/method/messages.getFullChat b/data/corefork.telegram.org/method/messages.getFullChat
index ee921741a2..c352ef4259 100644
--- a/data/corefork.telegram.org/method/messages.getFullChat
+++ b/data/corefork.telegram.org/method/messages.getFullChat
@@ -4,10 +4,10 @@
messages.getFullChat
messages.getFullChat
- Get full info about a legacy group .
+
Get full info about a basic group .
@@ -71,7 +71,7 @@
chat_id long Legacy group ID.Basic group ID.
@@ -101,8 +101,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
messages.messageReactionsList #31bd492d flags:# count:int reactions:Vector <MessagePeerReaction > chats:Vector <Chat > users:Vector <User > next_offset:flags.0?string = messages.MessageReactionsList ;
---functions---
messages.getMessageReactionsList #e0ee6b77 flags:# peer:InputPeer id:int reaction:flags.0?string offset:flags.1?string limit:int = messages.MessageReactionsList ;messages.MessageReactionsList
-List of message reactions »
-
+List of peers that reacted to a specific message
+
How to fetch results from large lists of objects.
-
-Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
-
+
+Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
diff --git a/data/corefork.telegram.org/method/messages.getMessagesViews b/data/corefork.telegram.org/method/messages.getMessagesViews
index fe0efffa9c..bfef1894ec 100644
--- a/data/corefork.telegram.org/method/messages.getMessagesViews
+++ b/data/corefork.telegram.org/method/messages.getMessagesViews
@@ -125,8 +125,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/messages.migrateChat b/data/corefork.telegram.org/method/messages.migrateChat
index 5416afdd36..48913d77cd 100644
--- a/data/corefork.telegram.org/method/messages.migrateChat
+++ b/data/corefork.telegram.org/method/messages.migrateChat
@@ -4,10 +4,10 @@
messages.migrateChat
messages.migrateChat
- Turn a legacy group into a supergroup
+
Turn a basic group into a supergroup
@@ -77,7 +77,7 @@
chat_id long Legacy group to migrateBasic group to migrate
@@ -116,8 +116,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/method/stats.getMegagroupStats b/data/corefork.telegram.org/method/stats.getMegagroupStats
index b1da8b78bd..962dd81c36 100644
--- a/data/corefork.telegram.org/method/stats.getMegagroupStats
+++ b/data/corefork.telegram.org/method/stats.getMegagroupStats
@@ -115,8 +115,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram offers detailed channel statistics for channels and supergroups.
diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html
index f8ce7474c5..622e75f930 100644
--- a/data/corefork.telegram.org/methods.html
+++ b/data/corefork.telegram.org/methods.html
@@ -584,7 +584,7 @@
channels.getGroupsForDiscussion Get all groups that can be used as discussion groups .legacy group chats must be first upgraded to supergroups before they can be set as a discussion group. channels.togglePreHistoryHidden , first.
+Get all groups that can be used as discussion groups .basic group chats must be first upgraded to supergroups before they can be set as a discussion group. channels.togglePreHistoryHidden , first.
channels.getMessages
messages.editChatAdmin Make a user admin in a legacy group .
+Make a user admin in a basic group .
messages.editChatDefaultBannedRights
messages.getFullChat Get full info about a legacy group .
+Get full info about a basic group .
messages.migrateChat Turn a legacy group into a supergroup
+Turn a basic group into a supergroup
channels.convertToGigagroup
messages.editChatAdmin Make a user admin in a legacy group .
+Make a user admin in a basic group .
messages.reorderStickerSets How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/type/ChatBannedRights.html b/data/corefork.telegram.org/type/ChatBannedRights.html
index c1ae5422f7..175bf6ccdb 100644
--- a/data/corefork.telegram.org/type/ChatBannedRights.html
+++ b/data/corefork.telegram.org/type/ChatBannedRights.html
@@ -72,8 +72,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/type/ChatFull.html b/data/corefork.telegram.org/type/ChatFull.html
index 0d8ef02216..4beac45755 100644
--- a/data/corefork.telegram.org/type/ChatFull.html
+++ b/data/corefork.telegram.org/type/ChatFull.html
@@ -4,10 +4,10 @@
ChatFull
ChatFull
- Full info about a channel , supergroup , gigagroup or legacy group .
+
Full info about a channel , supergroup , gigagroup or basic group .
@@ -77,8 +77,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/type/StatsGroupTopInviter.html b/data/corefork.telegram.org/type/StatsGroupTopInviter.html
index 951b4e03bd..318e2c602c 100644
--- a/data/corefork.telegram.org/type/StatsGroupTopInviter.html
+++ b/data/corefork.telegram.org/type/StatsGroupTopInviter.html
@@ -72,8 +72,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/type/StatsGroupTopPoster.html b/data/corefork.telegram.org/type/StatsGroupTopPoster.html
index 92728d38ea..80a51c4398 100644
--- a/data/corefork.telegram.org/type/StatsGroupTopPoster.html
+++ b/data/corefork.telegram.org/type/StatsGroupTopPoster.html
@@ -72,8 +72,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
diff --git a/data/corefork.telegram.org/type/Update.html b/data/corefork.telegram.org/type/Update.html
index 9ead7370b5..9405fdf498 100644
--- a/data/corefork.telegram.org/type/Update.html
+++ b/data/corefork.telegram.org/type/Update.html
@@ -282,7 +282,7 @@
updateChatParticipantAdmin Admin permissions of a user in a legacy group were changed
+Admin permissions of a user in a basic group were changed
updateNewStickerSet
messages.migrateChat Turn a legacy group into a supergroup
+Turn a basic group into a supergroup
messages.sendInlineBotResult messages.ChatFull
messages.ChatFull
- Full info about a channel , supergroup , gigagroup or legacy group .
+
Full info about a channel , supergroup , gigagroup or basic group .
@@ -73,7 +73,7 @@
messages.chatFull Full info about a channel , supergroup , gigagroup or legacy group .
+Full info about a channel , supergroup , gigagroup or basic group .
@@ -97,8 +97,8 @@
How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.
+
+
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 
(object with emoji keys and object values, containing 
and 1000 
reactions and reactions_uniq_max = 2, you can't add a 
reaction, because that would raise the number of unique reaction-emojis to 3 > 2. (integer)
+
, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 
(object with emoji keys and object values, containing 
and 1000 
reactions and reactions_uniq_max = 2, you can't add a 
reaction, because that would raise the number of unique reaction-emojis to 3 > 2. (integer)