diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html
index 331bc12843..6b1ac043d9 100644
--- a/data/web/corefork.telegram.org/api/forum.html
+++ b/data/web/corefork.telegram.org/api/forum.html
@@ -90,8 +90,10 @@ 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.
-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).
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 reply_msg_id
, and, unless we're replying to a message in the "General" topic, pass the topic ID to top_msg_id
.
+Note that when replying to messages in a topic, the 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
.
Topics can be temporarily closed
, preventing further messages from being sent to the topic.
Additionally, (only) the "General" topic may also be hidden
.
diff --git a/data/web/corefork.telegram.org/method/messages.requestWebView b/data/web/corefork.telegram.org/method/messages.requestWebView
index 40e5ff9a73..793083e128 100644
--- a/data/web/corefork.telegram.org/method/messages.requestWebView
+++ b/data/web/corefork.telegram.org/method/messages.requestWebView
@@ -122,7 +122,7 @@
reply_to_msg_id
is set and reply_to_msg_id != topicID
and topicID != 1
). reply_to_msg_id
is set and reply_to_msg_id != topicID
and topicID != 1
). reply_to_msg_id
is set and reply_to_msg_id != topicID
and topicID != 1
). reply_to_msg_id
is set and reply_to_msg_id != topicID
and topicID != 1
).