From 153ab70200b11982be56722d4dd18bd789aaa026 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Tue, 11 Apr 2023 20:01:13 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/forum.html | 4 +- .../web/corefork.telegram.org/api/layers.html | 2 +- data/web/corefork.telegram.org/api/links.html | 4 +- .../constructor/messageActionBotAllowed.html | 6 ++- .../constructor/messages.sponsoredMessages | 2 +- .../premiumSubscriptionOption.html | 6 +-- .../constructor/sponsoredMessage.html | 4 +- .../updateGroupInvitePrivacyForbidden.html | 39 +++++++++---------- .../method/channels.inviteToChannel | 8 +++- .../method/messages.addChatUser | 8 +++- .../method/messages.createChat | 7 +++- data/web/corefork.telegram.org/methods.html | 6 +-- .../corefork.telegram.org/type/Update.html | 2 +- .../corefork.telegram.org/type/Updates.html | 6 +-- 14 files changed, 61 insertions(+), 43 deletions(-) diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html index 6a953c1840..a1dccc977f 100644 --- a/data/web/corefork.telegram.org/api/forum.html +++ b/data/web/corefork.telegram.org/api/forum.html @@ -87,9 +87,9 @@ If the group is a basic group, it should

Forums can have multiple topics where users may interact.

To fetch the topic list of a forum, use channels.getForumTopics; the same method can be used to search topics by their name.
To fetch information about one or more topics by their ID, use channels.getForumTopicsByID.

-

Every forum has a non-deletable "General" topic, with id=1; other topics will have other IDs, equal to the messageActionTopicCreate service message that created the topic.

+

Every forum has a non-deletable "General" topic, with id=1; other topics will have other IDs, equal to the messageActionTopicCreate service message that created the topic.

To send messages to the "General" topic, just 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.
+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.
Replies to messages within a topic work as usual (simply pass the ID of the message to reply to to reply_msg_id, ignoring the topic ID), however, 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).

diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index c8c0e32e2e..d6accb6e78 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -80,7 +80,7 @@
  • Added appWebViewResultUrl - Contains the link that must be used to open a bot web app.
  • Added inlineBotWebView - Specifies a bot web app button, shown on top of the inline query results list.
  • Added readParticipantDate - Contains info about when a certain participant has read a message
    • -
  • Added updateGroupInvitePrivacyForbidden -
    • +
  • Added updateGroupInvitePrivacyForbidden - 0-N updates of this type may be returned only when invoking messages.addChatUser, channels.inviteToChannel or messages.createChat: it indicates we couldn't add a user to a chat because of their privacy settings; if required, an invite link can be shared with the user, instead.
    • Changed Constructors