From 4fe206138db0dab8112f3100f051d9f02f5e5819 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 9 Oct 2021 16:23:51 +0000 Subject: [PATCH] Update content of files --- data/corefork.telegram.org/api/config.html | 71 ++++++++++++++----- data/corefork.telegram.org/api/layers.html | 4 +- .../constructor/inputThemeSettings.html | 2 +- .../constructor/themeSettings.html | 2 +- .../constructor/wallPaperNoFile.html | 7 +- .../method/auth.checkRecoveryPassword | 32 +++------ .../method/channels.createChannel | 9 ++- .../method/messages.initHistoryImport | 2 +- .../method/phone.checkGroupCall | 36 ++-------- data/corefork.telegram.org/methods.html | 4 +- data/corefork.telegram.org/type/Bool.html | 2 +- .../type/messages.HistoryImport | 2 +- 12 files changed, 93 insertions(+), 80 deletions(-) diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html index 2f1b271daf..19a94c757f 100644 --- a/data/corefork.telegram.org/api/config.html +++ b/data/corefork.telegram.org/api/config.html @@ -82,18 +82,17 @@ While help.getConfig returns MTProto-specif
  • 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)

    • 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\udfb0",
+        "\ud83c\udfb3"
     ],
     "emojies_send_dice_success": {
         "\ud83c\udfaf": {
@@ -115,43 +114,57 @@ While help.getConfig returns MTProto-specif
         "\ud83c\udfb0": {
             "value": 64,
             "frame_start": 110
+        },
+        "\ud83c\udfb3": {
+            "value": 6,
+            "frame_start": 110
         }
     },
     "emojies_sounds": {
         "\ud83c\udf83": {
             "id": "4956223179606458539",
             "access_hash": "-2107001400913062971",
-            "file_reference_base64": "AF-4ApC7ukC0UWEPZN0TeSJURe7T"
+            "file_reference_base64": "AGFhvoKbftK5O9K9RpgN1ZtgSzWy"
         },
         "\u26b0": {
             "id": "4956223179606458540",
             "access_hash": "-1498869544183595185",
-            "file_reference_base64": "AF-4ApCLKMGt96WCvLm58kbqZHd3"
+            "file_reference_base64": "AGFhvoJIm8Uz0qSMIdm3AsKlK7wJ"
         },
         "\ud83e\udddf\u200d\u2642": {
             "id": "4960929110848176331",
             "access_hash": "3986395821757915468",
-            "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g"
+            "file_reference_base64": "AGFhvoLtXSSIclmvfg6ePz3KsHQF"
         },
         "\ud83e\udddf": {
             "id": "4960929110848176332",
             "access_hash": "-8929417974289765626",
-            "file_reference_base64": "AF-4ApArGURtGa2KVC-Yovh1kQoW"
+            "file_reference_base64": "AGFhvoImaz5Umt4GvMUD5nocIu0W"
         },
         "\ud83e\udddf\u200d\u2640": {
             "id": "4960929110848176333",
             "access_hash": "9161696144162881753",
-            "file_reference_base64": "AF-4ApD-eOqXvTBmcszAEkzQN615"
+            "file_reference_base64": "AGFhvoIm1QZsb48xlpRfh4Mq7EMG"
         },
         "\ud83c\udf51": {
             "id": "4963180910661861548",
             "access_hash": "-7431729439735063448",
-            "file_reference_base64": "AF-4ApBimvRxhcXg-iQ5Gw4Eelit"
+            "file_reference_base64": "AGFhvoKLrwl_WKr5LR0Jjs7o3RyT"
         },
-        "\u2764": {
-            "id": "4978826754966683841",
-            "access_hash": "3926211553285686901",
-            "file_reference_base64": "AF-4ApDBkyjgN2Tk9zJvXPhfJXPA"
+        "\ud83c\udf8a": {
+            "id": "5094064004578410732",
+            "access_hash": "8518192996098758509",
+            "file_reference_base64": "AGFhvoKMNffRV2J3vKED0O6d8e42"
+        },
+        "\ud83c\udf84": {
+            "id": "5094064004578410733",
+            "access_hash": "-4142643820629256996",
+            "file_reference_base64": "AGFhvoJ1ulPBbXEURlTZWwJFx6xZ"
+        },
+        "\ud83e\uddbe": {
+            "id": "5094064004578410734",
+            "access_hash": "-8934384022571962340",
+            "file_reference_base64": "AGFhvoL4zdMRmYv9z3L8KPaX4JQL"
         }
     },
     "gif_search_branding": "tenor",
@@ -167,10 +180,34 @@ While help.getConfig returns MTProto-specif
         "\ud83d\ude0e",
         "\ud83d\udc4e"
     ],
-    "qr_login_camera": true,
-    "qr_login_code": "secondary",
+    "stickers_emoji_suggest_only_api": false,
+    "stickers_emoji_cache_time": 86400,
+    "groupcall_video_participants_max": 1000,
+    "youtube_pip": "inapp",
+    "qr_login_camera": false,
+    "qr_login_code": "disabled",
     "dialog_filters_enabled": true,
-    "dialog_filters_tooltip": false
+    "dialog_filters_tooltip": false,
+    "autoarchive_setting_available": false,
+    "pending_suggestions": [
+        "VALIDATE_PHONE_NUMBER"
+    ],
+    "autologin_token": "yPsoJyg7wwd1xOC7GJchrRjcH8S-vnyc-NgdjPbnNy5hYb6CFgAAAABGkwcvAKSBUUgM3V0NdMeDpfmRzGyqTigcHSU0zwly2_EAJ9YN",
+    "autologin_domains": [
+        "instantview.telegram.org",
+        "translations.telegram.org",
+        "contest.dev",
+        "contest.com",
+        "bugs.telegram.org",
+        "suggestions.telegram.org",
+        "themes.telegram.org"
+    ],
+    "round_video_encoding": {
+        "diameter": 384,
+        "video_bitrate": 1000,
+        "audio_bitrate": 64,
+        "max_size": 12582912
+    }
 }
    
 
    App-specific configuration
    
 
    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;
diff --git a/data/corefork.telegram.org/api/layers.html b/data/corefork.telegram.org/api/layers.html
index 0bb1de0b54..5d9f1c0428 100644
--- a/data/corefork.telegram.org/api/layers.html
+++ b/data/corefork.telegram.org/api/layers.html
@@ -458,7 +458,7 @@ Layer…">
 
 
    Changed Methods
    
 
 
    Changed Methods
    
 
      
diff --git a/data/corefork.telegram.org/constructor/inputThemeSettings.html b/data/corefork.telegram.org/constructor/inputThemeSettings.html
index afcfcd8130..133feea8a5 100644
--- a/data/corefork.telegram.org/constructor/inputThemeSettings.html
+++ b/data/corefork.telegram.org/constructor/inputThemeSettings.html
@@ -91,7 +91,7 @@
 
 message_colors
 flags.0?Vector<int>
-The fill to be used as a background for outgoing messages, in RGB24 format. \
      If just one or two equal colors are provided, describes a solid fill of a background. \
      If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.\
      If three or four colors are provided, describes a freeform gradient fill of a background.
+The fill to be used as a background for outgoing messages, in RGB24 format. 
      If just one or two equal colors are provided, describes a solid fill of a background. 
      If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
      If three or four colors are provided, describes a freeform gradient fill of a background.
 
 
 wallpaper
diff --git a/data/corefork.telegram.org/constructor/themeSettings.html b/data/corefork.telegram.org/constructor/themeSettings.html
index 9646dd36dd..1e94cf4161 100644
--- a/data/corefork.telegram.org/constructor/themeSettings.html
+++ b/data/corefork.telegram.org/constructor/themeSettings.html
@@ -91,7 +91,7 @@
 
 message_colors
 flags.0?Vector<int>
-The fill to be used as a background for outgoing messages, in RGB24 format. \
      If just one or two equal colors are provided, describes a solid fill of a background. \
      If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.\
      If three or four colors are provided, describes a freeform gradient fill of a background.
+The fill to be used as a background for outgoing messages, in RGB24 format. 
      If just one or two equal colors are provided, describes a solid fill of a background. 
      If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
      If three or four colors are provided, describes a freeform gradient fill of a background.
 
 
 wallpaper
diff --git a/data/corefork.telegram.org/constructor/wallPaperNoFile.html b/data/corefork.telegram.org/constructor/wallPaperNoFile.html
index 3fd1855ac1..bc162f3027 100644
--- a/data/corefork.telegram.org/constructor/wallPaperNoFile.html
+++ b/data/corefork.telegram.org/constructor/wallPaperNoFile.html
@@ -66,7 +66,7 @@
 
 id
 long
- 
+Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
 
 
 flags
@@ -91,7 +91,10 @@
 
 
 
      Type
      
-
      WallPaper
      
+
      WallPaper
      
+
      Related pages
      
+
      account.saveWallPaper
      
+
      Install/uninstall wallpaper
      
   
 
           
diff --git a/data/corefork.telegram.org/method/auth.checkRecoveryPassword b/data/corefork.telegram.org/method/auth.checkRecoveryPassword
index 686e0cbb08..998ae8578f 100644
--- a/data/corefork.telegram.org/method/auth.checkRecoveryPassword
+++ b/data/corefork.telegram.org/method/auth.checkRecoveryPassword
@@ -4,26 +4,10 @@
     
     auth.checkRecoveryPassword
     
-    
+    
     
     
-    
+    
     
 
     
@@ -55,7 +39,8 @@ Bool">
   
      
   
      auth.checkRecoveryPassword
      
   
-  
      
+  
      Check if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
      
+
      
   
      
+
      Bool
      
+
      Related pages
      
+
      auth.requestPasswordRecovery
      
+
      Request recovery code of a 2FA password, only for accounts with a recovery email configured.
      
+
      auth.recoverPassword
      
+
      Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
      
   
 
      
           
diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel
index d932bbb2a3..a20af15846 100644
--- a/data/corefork.telegram.org/method/channels.createChannel
+++ b/data/corefork.telegram.org/method/channels.createChannel
@@ -89,7 +89,7 @@
 
 for_import
 flags.3?true
- 
+Whether the supergroup is being created to import messages from a foreign chat service using messages.initHistoryImport
 
 
 title
@@ -154,7 +154,12 @@
 
 
      Related pages
      
 
      Channels
      
-
      How to handle channels, supergroups, groups, and what's the difference between them.
      
+
      How to handle channels, supergroups, groups, and what's the difference between them.
      
+
      messages.initHistoryImport
      
+
      Import chat history from a foreign chat app into a specific Telegram chat.
      
+Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
      
+Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».
      
+
      After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
      
   
 
           
diff --git a/data/corefork.telegram.org/method/messages.initHistoryImport b/data/corefork.telegram.org/method/messages.initHistoryImport
index 47aeb22600..c514db8c5c 100644
--- a/data/corefork.telegram.org/method/messages.initHistoryImport
+++ b/data/corefork.telegram.org/method/messages.initHistoryImport
@@ -41,7 +41,7 @@
   
   
      Import chat history from a foreign chat app into a specific Telegram chat.
      
 Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
      
-Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».
      
+Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».
      
 
      After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
      
 
      
   
        
diff --git a/data/corefork.telegram.org/method/phone.checkGroupCall b/data/corefork.telegram.org/method/phone.checkGroupCall
index c42aa8babf..c16b645734 100644
--- a/data/corefork.telegram.org/method/phone.checkGroupCall
+++ b/data/corefork.telegram.org/method/phone.checkGroupCall
@@ -4,34 +4,10 @@
     
     phone.checkGroupCall
     
-    
+    
     
     
-    
+    
     
 
     
@@ -63,7 +39,8 @@ Bots can use this method">
   
        
   
        phone.checkGroupCall
        
   
-  
        
+  
        Check whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs
        
+
        
   
          
     
        • 
       Layer 133 
@@ -90,17 +67,18 @@ Bots can use this method">
 
 call
 InputGroupCall
- 
+Group call
 
 
 sources
 Vector<int>
- 
+Source IDs
 
 
 
 
          Result
          
 
          Vector<int>
          
+
          Returns an intersection of the source IDs specified in sources, and the source IDs currently being forwarded by the SFU.
          
 
          Bots can use this method
        
   
 
        
diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html
index f9adbc61f0..50ddd3fcbf 100644
--- a/data/corefork.telegram.org/methods.html
+++ b/data/corefork.telegram.org/methods.html
@@ -229,7 +229,7 @@
 
 
 auth.checkRecoveryPassword
- 
+Check if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
 
 
 auth.dropTempAuthKeys
@@ -1434,7 +1434,7 @@
 
 
 phone.checkGroupCall
- 
+Check whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs
 
 
 phone.createGroupCall
diff --git a/data/corefork.telegram.org/type/Bool.html b/data/corefork.telegram.org/type/Bool.html
index dbb61287d7..30091b29c0 100644
--- a/data/corefork.telegram.org/type/Bool.html
+++ b/data/corefork.telegram.org/type/Bool.html
@@ -635,7 +635,7 @@
 
 
 auth.checkRecoveryPassword
- 
+Check if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
 
 
 channels.viewSponsoredMessage
diff --git a/data/corefork.telegram.org/type/messages.HistoryImport b/data/corefork.telegram.org/type/messages.HistoryImport
index 62d25f46d6..11b85bb406 100644
--- a/data/corefork.telegram.org/type/messages.HistoryImport
+++ b/data/corefork.telegram.org/type/messages.HistoryImport
@@ -83,7 +83,7 @@
 
 
 messages.initHistoryImport
-Import chat history from a foreign chat app into a specific Telegram chat.  
        Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.  
        Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info    administrator rights ».

        After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
+Import chat history from a foreign chat app into a specific Telegram chat.  
        Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.  
        Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

        After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.