url to log into the Fragment platform with your wallet and view the code. allow_firebase flag is set. safety_net_token, along with the phone_number and the phone_code_hash.allow_firebase flag is set.nonce to the SafetyNet Attestation API, and then pass the obtained JWS object to auth.requestFirebaseSms.safety_net_token, along with the phone_number and the phone_code_hash.next_type authentication method must be used, with auth.resendCode.token.push_timeout seconds.push_timeout seconds, the next_type authentication method must be used, with auth.resendCode.receipt and ios_push_secret fields, and the value of the receipt field matches codeSettings.receipt, the value of ios_push_secret is passed to auth.requestFirebaseSms.ios_push_secret, along with the phone_number and the phone_code_hash.next_type authentication method must be used, with auth.resendCode.receipt and push_timeout fields of auth.sentCodeTypeFirebaseSms are populated, request_write_access and the user granted it with write_allowed.
Bot web apps can be themed according to the following theme parameters, passed as a JSON object to the theme_params parameter of the messages.requestSimpleWebView and messages.requestWebView methods.
This JSON object has the the following keys, containing color theme information (hex string, RGB, no alpha) to pass to the web app:
+This JSON object has the following keys, containing color theme information (hex string, RGB, no alpha) to pass to the web app:
bg_color - Background colorsecondary_bg_color - Secondary background colorAPI peer folders are typically used only by archived chats, and are really handy for distinguishing groups of peers, since most peer-related constructors (updates, chat info) will contain the folder_id assigned the the specified chat.
API peer folders are typically used only by archived chats, and are really handy for distinguishing groups of peers, since most peer-related constructors (updates, chat info) will contain the folder_id assigned the specified chat.
In Telegram apps, API peer folders are used only to implement the chat archive, identified by folder_id 1; all other peers are in folder_id 0 by default; no other folder_id is allowed at the moment.
Most importantly, added support for Safetynet/Firebase SMS authentication, which is now mandatory when requesting SMS codes to log in or sign up to Telegram.
-Currently, only official apps can make use of Safetynet/Firebase SMS authentication: this means that only the official applications can be used to sign up to Telegram, or receive the login code via SMS/call. Third-party apps may log in using any of the other code delivery methods (Telegram codes, Fragment codes, email codes, future auth tokens).
Most importantly, added support for Firebase SMS authentication, which is now mandatory when requesting SMS codes to log in or sign up to Telegram.
+Currently, only official apps can make use of Firebase SMS authentication: this means that only the official applications can be used to sign up to Telegram, or receive the login code via SMS/call. Third-party apps may log in using any of the other code delivery methods (Telegram codes, Fragment codes, email codes, future auth tokens).
reply_mark
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
The user receives an invoice deep link or an updateNewMessage constructor from the bot, containing a messageMediaInvoice constructor with basic info about the product.
For invoice messages, the message will also have a replyInlineMarkup keyboard attached to it. -The the first button of the keyboard will always be a keyboardButtonBuy button.
+The first button of the keyboard will always be a keyboardButtonBuy button.inputInvoiceMessage#c5b56859 peer:InputPeer msg_id:int = InputInvoice;
inputInvoiceSlug#c326caef slug:string = InputInvoice;
diff --git a/data/web/corefork.telegram.org/api/reactions.html b/data/web/corefork.telegram.org/api/reactions.html
index 25d400d947..04524464af 100644
--- a/data/web/corefork.telegram.org/api/reactions.html
+++ b/data/web/corefork.telegram.org/api/reactions.html
@@ -51,7 +51,7 @@
reactionCount#a3d1cb80 flags:# chosen_order:flags.0?int reaction:Reaction count:int = ReactionCount;
-messagePeerReaction#8c79b63c flags:# big:flags.0?true unread:flags.1?true peer_id:Peer date:int reaction:Reaction = MessagePeerReaction;
+messagePeerReaction#8c79b63c flags:# big:flags.0?true unread:flags.1?true my:flags.2?true peer_id:Peer date:int reaction:Reaction = MessagePeerReaction;
messageReactions#4f2b9479 flags:# min:flags.0?true can_see_list:flags.2?true results:Vector<ReactionCount> recent_reactions:flags.1?Vector<MessagePeerReaction> = MessageReactions;
diff --git a/data/web/corefork.telegram.org/api/threads.html b/data/web/corefork.telegram.org/api/threads.html
index 89ade13e64..e55ce455a1 100644
--- a/data/web/corefork.telegram.org/api/threads.html
+++ b/data/web/corefork.telegram.org/api/threads.html
@@ -99,7 +99,7 @@ Its ID for main and testing endpoints can be seen in the discussion groupreply_to.reply_to_msg_id set to the ID of our messagereply_to.reply_to_top_id set to the thread IDBot API 5.4
creates_join_request to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests (read more about this on our blog).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).creates_join_request and pending_join_request_count to the class ChatInviteLink.name to the class ChatInviteLink and the parameters name to the methods createChatInviteLink and editChatInviteLink for managing invite link names.Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.
Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.
+Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.
| token | flags.8?string | -+ | Used only by official iOS apps for Firebase auth: device token for apple push. |
| app_sandbox | flags.8?Bool | -+ | Used only by official iOS apps for firebase auth: whether a sandbox-certificate will be used during transmission of the push notification. |
The passport_secret can now be used to decrypt encrypted passport data stored on telegram servers:
To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The the data is encrypted according to the following scheme:
+To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The data is encrypted according to the following scheme:
Data is padded to a length that is divisible by 16 bytes. To achieve this, 32 to 255 bytes are added at the beginning, where the first byte always holds the number of added bytes and the rest are random.