diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html index 6b1ac043d9..695f9cdd89 100644 --- a/data/web/corefork.telegram.org/api/forum.html +++ b/data/web/corefork.telegram.org/api/forum.html @@ -85,7 +85,7 @@ If the group is a basic group, it should channels.reorderPinnedForumTopics#2950a18f flags:# force:flags.0?true channel:InputChannel order:Vector<int> = Updates;

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.

+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.

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.
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index dcfd3656a4..daae7d755e 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -536,7 +536,7 @@ Added support for thread IDs in message deep channels.updatePinnedForumTopic#6c2d9026 channel:InputChannel topic_id:int pinned:Bool = Updates; channels.deleteTopicHistory#34435f2d channel:InputChannel top_msg_id:int = messages.AffectedHistory;

Layer 147

-

Keywords for custom emojis, web token authorization.

+

Keywords for custom emojis and non-mask stickers, web token authorization.

Schema changes

New Methods