diff --git a/data/web/corefork.telegram.org/api/bots/buttons.html b/data/web/corefork.telegram.org/api/bots/buttons.html index 32c960f7b8..eb1cdad220 100644 --- a/data/web/corefork.telegram.org/api/bots/buttons.html +++ b/data/web/corefork.telegram.org/api/bots/buttons.html @@ -77,7 +77,7 @@ This article describes the full button flow, using the MTProto API.

  • replyKeyboardMarkup - Sends a custom reply keyboard.
    User clients receiving such a constructor should display a special keyboard with custom reply options.
  • replyKeyboardHide - Hides the custom reply keyboard.
    User clients receiving this constructor should hide the custom reply keyboard opened by replyKeyboardMarkup
  • replyKeyboardForceReply - Sends a force reply constructor
    User clients receiving a message with this constructor should act as if the user had clicked on the reply button of the message, displaying the reply UI.
    • -
  • replyInlineMarkup - Attaches an inline keyboard to the message, allowing users to send callback data to the bot without sending actual messages to the current chat, see here for more info ».
    • +
  • replyInlineMarkup - Attaches an inline keyboard to the message, allowing users to send callback data to the bot without sending actual messages to the current chat.

    • Pressing buttons

    keyboardButton#a2fa4880 text:string = KeyboardButton;
@@ -99,10 +99,10 @@ This article describes the full button flow, using the MTProto API.  
    
 Each row can have a different number of columns, and user clients should properly handle clicking buttons of every type.  
    
 
    Buttons available only in reply keyboards:
    
 
 
    Buttons available only in inline keyboards:
    
 
-
    Sent by the client to report the payment status of an invoice obtained from a web_app_open_invoice event ».  
    
+
    Sent by the client to report the payment status of an invoice obtained from a web_app_open_invoice event ».  
    
 
    viewport_changed
    
 
    Params: a JSON object with the following fields:
    
 
 
 
-
    Emitted when requested by the web app using a web_app_request_theme event », or when the app theme changes.  
    
+
    Emitted when requested by the web app using a web_app_request_theme event », or when the app theme changes.  
    
 
    popup_closed
    
 
    Params: a JSON object with an optional button_id string field.
    
-
    Emitted when the user presses a button or cancels a popup brought up by a previous web_app_open_popup event ».  
    
+
    Emitted when the user presses a button or cancels a popup brought up by a previous web_app_open_popup event ».  
    
 
    Simple web apps
    
 
    Schema:
    
 
    replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
@@ -122,7 +122,7 @@
 
    Simple webapps can only send back data to the bot through the MTProto API via a web_app_data_send JS event ».  
    
 
    Simple webapps can only be opened from a keyboardButtonSimpleWebView button contained in a reply keyboard identified by a replyKeyboardMarkup constructor.  
    
 
    To open them, users should call messages.requestSimpleWebView, and then open a webview using the url contained in the returned simpleWebViewResultUrl.  
    
-
    Upon receiving a web_app_data_send JS event » from the web app, clients should invoke messages.sendWebViewData, passing the following arguments:
    
+
    Upon receiving a web_app_data_send JS event » from the web app, clients should invoke messages.sendWebViewData, passing the following arguments:
    
 
      
 
    • bot - Bot ID
      • 
 
    • random_id - Unique random ID to avoid resending the same event multiple times
      • 
@@ -160,7 +160,7 @@
 
    • An attachment menu »
      • 
 
    
 
    To open them, clients should call messages.requestWebView, and then open a webview using the url contained in the returned webViewResultUrl.  
    
-
    After loading the webview, until it is closed by a web_app_close event, the user client must invoke messages.prolongWebView every 60 seconds.  
    
+
    After loading the webview, until it is closed by a web_app_close event, the user client must invoke messages.prolongWebView every 60 seconds.  
    
 
    The opened URL's fragment parameters already contain basic information about the user and a query_id parameter, that is exposed by the bot web apps JS library: this query_id can then be used by the bot to invoke messages.sendWebViewResultMessage, passing an InputBotInlineResult constructor that will automatically send a message with optionally attached media, and even inline buttons on behalf of the user.  
    
   
 
diff --git a/data/web/corefork.telegram.org/api/config.html b/data/web/corefork.telegram.org/api/config.html
index 64c0541e1a..06f40b0e0b 100644
--- a/data/web/corefork.telegram.org/api/config.html
+++ b/data/web/corefork.telegram.org/api/config.html
@@ -324,9 +324,9 @@ While help.getConfig returns MTProto-specif
 
    saved_gifs_limit_premium
    
 
    The maximum number of GIFs a Premium user may save (integer)
    
 
    stickers_faved_limit_default
    
-
    The maximum number of stickers a non-Premium user may add to Favorites » (integer)
    
+
    The maximum number of stickers a non-Premium user may add to Favorites » (integer)
    
 
    stickers_faved_limit_premium
    
-
    The maximum number of stickers a Premium user may add to Favorites » (integer)
    
+
    The maximum number of stickers a Premium user may add to Favorites » (integer)
    
 
    dialog_filters_limit_default
    
 
    The maximum number of folders a non-Premium user may create (integer)
    
 
    dialog_filters_limit_premium
    
diff --git a/data/web/corefork.telegram.org/api/delete-account.html b/data/web/corefork.telegram.org/api/delete-account.html
deleted file mode 100644
index 2eb3c8c869..0000000000
--- a/data/web/corefork.telegram.org/api/delete-account.html
+++ /dev/null
@@ -1,118 +0,0 @@
-
-
-  
-    
-    Page not found
-    
-    
-    
-    
-    
-    
-
-
-
-
-    
-    
-    
-    
-  
-  
-    
    
-      
    
-        
    
-          
    
-            
-            
-          
    
-        
    
-      
    
-      
    
-        
    
-          
    
-  
    
-  
    Page not found
    
-  
-  
    The page has not been saved
    
-  
-
    
-          
-        
    
-      
    
-      
    
-  
    
-    
    
-      
    Telegram
    
-      
    
-      Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
-    
    
-
-    
    
-      
    About
    
-      
-    
    
-    
    
-      
    Mobile Apps
    
-      
-    
    
-    
    
-      
    Desktop Apps
    
-      
-    
    
-    
    
-      
    Platform
    
-      
-    
    
-  
    
-  
    
-    
    
-      
    About
    
-    
    
-    
    
-      
    Blog
    
-    
    
-    
    
-      
    Apps
    
-    
    
-    
    
-      
    Platform
    
-    
    
-    
    
-      
    Twitter
    
-    
    
-  
    
-
    
-    
    
-    
-    
-    
-  
-
-
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index dc3ab080d5..58cc1e4206 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -125,7 +125,7 @@ Also introducing new messageEntitySpoiler#32ca960f offset:int length:int = MessageEntity;
 messageEntityCustomEmoji#c8cf05f8 offset:int length:int document_id:long = MessageEntity;
    
 
    Layer 143
    
-
    Telegram Premium, voice message transcription, invoices, bot description photos/animations, immediate account deletion, recurring payments and attachment menu improvements.
    
+
    Telegram Premium, voice message transcription, invoices, bot description photos/animations, immediate account deletion, recurring payments and attachment menu improvements.
    
 Also, discussion group admins can now require users to join before commenting.
    
 
    The main and E2E schemes were also modified to eventually support uploading and downloading files bigger than 4GB: the current supported maximum filesize is dynamically specified, and can be fetched from the new upload_max_fileparts_default » and upload_max_fileparts_premium » app configuration fields.
    
 
    Schema changes
    
diff --git a/data/web/corefork.telegram.org/api/links.html b/data/web/corefork.telegram.org/api/links.html
index 520f52288d..8b14fd0c33 100644
--- a/data/web/corefork.telegram.org/api/links.html
+++ b/data/web/corefork.telegram.org/api/links.html
@@ -58,7 +58,7 @@
 
  • tg:path?query
    • 
 
  • tg://path?query
    • 
 
-
    The #fragment part is always ignored when parsing links.  
    
+
    The #fragment part is always ignored.  
    
 
    Public username links
    
 
    Used to link to public users, groups and channels, see here for more info on how to handle them ».  
    
 
    t.me syntax:
    
@@ -224,7 +224,7 @@ tg://resolve?domain=<username>&livestream=<invite_hash>    
 
 
    Stickerset links
    
-
    Used to import stickersets as described here ».
    
+
    Used to import stickersets as described here ».
    
 
    t.me syntax:
    
 
    t.me/addstickers/<slug>
    
 
    tg: syntax:
    
@@ -242,12 +242,12 @@ tg://resolve?domain=<username>&livestream=<invite_hash>
 slug
 Required
-Stickerset short name, used when installing stickers.
+Stickerset short name, used when installing stickers.
 
 
 
 
    Custom emoji stickerset links
    
-
    Used to import custom emoji stickersets as described here ».
    
+
    Used to import custom emoji stickersets as described here ».
    
 
    t.me syntax:
    
 
    t.me/addemoji/<slug>
    
 
    tg: syntax:
    
@@ -265,7 +265,7 @@ tg://resolve?domain=<username>&livestream=<invite_hash>
 slug
 Required
-Stickerset short name, used when installing stickers.
+Stickerset short name, used when installing stickers.
 
 
 
diff --git a/data/web/corefork.telegram.org/api/payments.html b/data/web/corefork.telegram.org/api/payments.html
index ff5edcc23b..0a2f27bdf5 100644
--- a/data/web/corefork.telegram.org/api/payments.html
+++ b/data/web/corefork.telegram.org/api/payments.html
@@ -149,9 +149,9 @@ The recurring flag will be set for recurring payments, and re
 payments.validateRequestedInfo#b6c8f12b flags:# save:flags.0?true invoice:InputInvoice info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

    If any data at all is requested by the invoice (name_requested, phone_requested, email_requested, shipping_address_requested), the user must call payments.validateRequestedInfo, providing the required data (as usual, msg_id is the ID of the invoice message). The user can choose to save order information for future use by setting the save flag. -Data can be autofilled as described in autofill.

    +Data can be autofilled as described in autofill.

    If no errors are found in the submitted info, the response of the method will contain an id flag, to be used later to complete the payment.

    -

    If the flexible flag of the invoice is set, calling the payments.validateRequestedInfo method will send a shipping query update to the bot, to which the bot will reply with the available shipping options for the specified address as described here ». +

    If the flexible flag of the invoice is set, calling the payments.validateRequestedInfo method will send a shipping query update to the bot, to which the bot will reply with the available shipping options for the specified address as described here ». The return value in this case will also contain a shipping_options field with the available shipping options.

    If any errors are found in the submitted data, a service notification will be sent to the user, with a description of the error from the bot.

    2.3.1 Autofill

    @@ -173,9 +173,9 @@ The return value in this case will also contain a shipping_options ---functions--- messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool; -

    If a shipping address was requested and the bot included the parameter flexible, when the user validates order information the Telegram API will send an updateBotShippingQuery to the bot. +

    If a shipping address was requested and the bot included the parameter flexible, when the user validates order information the Telegram API will send an updateBotShippingQuery to the bot. The bot must respond using messages.setBotShippingResults either with a list of possible delivery options and the relevant delivery prices, or with an error (for example, if delivery to the specified address is not possible).

    -

    The returned shipping options or the shipping error will be returned to the user while validating order information.

    +

    The returned shipping options or the shipping error will be returned to the user while validating order information.

    3. Payment

    inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
 inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
@@ -267,16 +267,16 @@ Full credit card info is not saved on Telegram Servers, and can
 ---functions---
 
 payments.sendPaymentForm#2d03522f flags:# form_id:long invoice:InputInvoice requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
    -

    After verifying order information, the final step for the client is to call payments.sendPaymentForm, with the following parameters:

    +

    After verifying order information, the final step for the client is to call payments.sendPaymentForm, with the following parameters:

    Payment method info can also be saved to the Telegram Servers and reused, by setting the save flag of inputPaymentCredentials when sending the form. This is only possible on accounts with 2FA enabled.

    -

    The bot then replies to the received precheckout query, finally the user proceeds to checkout.

    +

    The bot then replies to the received precheckout query, finally the user proceeds to checkout.

    Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify their identity by opening the provided url and following instructions. Once the user finishes working with the webpage, the client can proceed to checkout.

    Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in service updates.

    diff --git a/data/web/corefork.telegram.org/api/premium.html b/data/web/corefork.telegram.org/api/premium.html index 0dd4b95a83..158128933b 100644 --- a/data/web/corefork.telegram.org/api/premium.html +++ b/data/web/corefork.telegram.org/api/premium.html @@ -105,7 +105,7 @@ The keys in video_sections correspond to a specific feature identif