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).
Note that since a forum topic ID is actually the ID of the service message that created the topic, whenever the client resolves a message link that points to a messageActionTopicCreate service message, it should open the topic, instead.
+
Note that since a forum topic ID is actually the ID of the service message that created the topic, whenever the client resolves a message link that points to a messageActionTopicCreate service message, it should open the topic, instead.
Also, if the message ID is 1 and the linked-to supergroup is a forum, the "General" topic should be opened instead of the first message of the supergroup.
Used to link to a specific forum topic.
-The syntax is exactly the same as for message links, because the topic ID is actually the ID of the service message that created the topic, so whenever the client resolves a message link that points to a messageActionTopicCreate service message, it should open the topic, instead.
+The syntax is exactly the same as for message links, because the topic ID is actually the ID of the service message that created the topic, so whenever the client resolves a message link that points to a messageActionTopicCreate service message, it should open the topic, instead.
Also, if the message ID is 1 and the linked-to supergroup is a forum, the "General" topic should be opened instead of the first message of the supergroup.
Used to share a prepared message and URL into a chosen chat's text field.
diff --git a/data/web/corefork.telegram.org/constructor/messageActionBotAllowed.html b/data/web/corefork.telegram.org/constructor/messageActionBotAllowed.html
index aebc010ab0..eebd7c1854 100644
--- a/data/web/corefork.telegram.org/constructor/messageActionBotAllowed.html
+++ b/data/web/corefork.telegram.org/constructor/messageActionBotAllowed.html
@@ -91,7 +91,11 @@
Bots can install attachment menu entries, offering conveniently accessible, versatile web apps.
+Bots can offer users interactive HTML5 web apps to completely replace any website.
diff --git a/data/web/corefork.telegram.org/constructor/messages.sponsoredMessages b/data/web/corefork.telegram.org/constructor/messages.sponsoredMessages index 22cd6100c5..d28ca33bd0 100644 --- a/data/web/corefork.telegram.org/constructor/messages.sponsoredMessages +++ b/data/web/corefork.telegram.org/constructor/messages.sponsoredMessages @@ -74,7 +74,7 @@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.
+ + +Adds a user to a chat and sends a service message on it.
+May also return 0-N updates of type updateGroupInvitePrivacyForbidden: 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.
+Invite users to a channel/supergroup
+May also return 0-N updates of type updateGroupInvitePrivacyForbidden: 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.
+Creates a new chat.
+May also return 0-N updates of type updateGroupInvitePrivacyForbidden: 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.
+Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
Invite users to a channel/supergroup
+May also return 0-N updates of type updateGroupInvitePrivacyForbidden: 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.
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.
+Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
Adds a user to a chat and sends a service message on it.
+May also return 0-N updates of type updateGroupInvitePrivacyForbidden: 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.
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.
+Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
Creates a new chat.
+May also return 0-N updates of type updateGroupInvitePrivacyForbidden: 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.
Changes the default value of the Time-To-Live setting, applied to all new chats.
Changes the default value of the Time-To-Live setting, applied to all new chats.
+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.
+Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.