From 61ab4a71d4dafda9326a9370d46ad95b25a0fb38 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sun, 26 Nov 2023 14:40:57 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/forum.html | 4 +- .../web/corefork.telegram.org/api/layers.html | 6 +- .../corefork.telegram.org/api/stickers.html | 4 +- .../method/bots.allowSendMessage.html | 39 +- .../method/bots.canSendMessage.html | 39 +- .../bots.invokeWebViewCustomMethod.html | 48 +- data/web/corefork.telegram.org/methods.html | 115 +++-- .../mtproto/samples-auth_key.html | 412 +++++++++--------- data/web/corefork.telegram.org/type/Bool.html | 2 +- .../corefork.telegram.org/type/DataJSON.html | 2 +- .../corefork.telegram.org/type/Updates.html | 2 +- 11 files changed, 289 insertions(+), 384 deletions(-) diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html index 588eb38325..017ef843c4 100644 --- a/data/web/corefork.telegram.org/api/forum.html +++ b/data/web/corefork.telegram.org/api/forum.html @@ -92,8 +92,8 @@ To fetch information about one or more topics by their ID, use messages.sendMessage as usual, as if you were writing to a normal supergroup.
On the other hand, topics with id != 1 are just the message thread of the messageActionTopicCreate service message that created that topic.
This means that topics should be treated similarly to message threads by the client.
-To send messages to these topics, pass the topic ID to the reply_msg_id parameter of messages.sendMessage, messages.sendMedia et cetera.

-

To reply to messages within a topic, pass the ID of the message to reply to to inputReplyToMessage.reply_msg_id, and, unless we're replying to a message in the "General" topic, pass the topic ID to inputReplyToMessage.top_msg_id.
+To send messages to these topics, pass the topic ID to the reply_to_msg_id parameter of inputReplyToMessage, passed to reply_to when invoking messages.sendMessage, messages.sendMedia et cetera.

+

To reply to messages within a topic, pass the ID of the message to reply to to inputReplyToMessage.reply_to_msg_id, and, unless we're replying to a message in the "General" topic, pass the topic ID to inputReplyToMessage.top_msg_id.
Note that when replying to messages in a topic, the inputReplyToMessage.top_msg_id field must contain the topic ID if and only if we're replying to messages in forum topics different from the "General" topic (i.e. reply_to_msg_id is set and reply_to_msg_id != topicID and topicID != 1): this way, if the replied-to message is deleted before the method finishes execution, the value in this field will be used to send the message to the correct topic, instead of the "General" topic.
Also note that since message threads can't have nested message threads, topics (except for the "General" topic) also can't have message threads (so replies to messages within topics won't generate further message threads).

Topics have a name (title) and an icon: the icon can be a custom emoji specified by the icon_emoji_id, or a default chat icon if icon_emoji_id is not set, filled with the color specified in icon_color.
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index df9b740299..924b77970b 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -69,9 +69,9 @@

  • Added stories.activateStealthMode - Activates stories stealth mode, see here » for more info.
  • Added contacts.setBlocked - Replace the contents of an entire blocklist, see here for more info ».
  • Added stories.sendReaction - React to a story.
    • -
  • Added bots.canSendMessage -
    • -
  • Added bots.allowSendMessage -
    • -
  • Added bots.invokeWebViewCustomMethod -
    • +
  • Added bots.canSendMessage - Check whether the specified bot can send us messages
    • +
  • Added bots.allowSendMessage - Allow the specified bot to send us messages
    • +
  • Added bots.invokeWebViewCustomMethod - Send a custom request from a mini bot app
  • Added stories.getPeerStories - Fetch the full active story list of a specific peer.
  • Added stories.getAllReadPeerStories - Obtain the latest read story ID for all peers when first logging in, returned as a list of updateReadStories updates, see here » for more info.
  • Added stories.getPeerMaxIDs -
    • diff --git a/data/web/corefork.telegram.org/api/stickers.html b/data/web/corefork.telegram.org/api/stickers.html index 4375a3a907..73f63c1199 100644 --- a/data/web/corefork.telegram.org/api/stickers.html +++ b/data/web/corefork.telegram.org/api/stickers.html @@ -79,7 +79,7 @@

    Static stickers

    Static stickers are WebP images with the following specs:

    @@ -103,7 +103,7 @@