From 6f941cbfa134d8b64e4ea62e45ebd2f82fd6d61f Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Tue, 28 Mar 2023 20:03:41 +0000 Subject: [PATCH] Update content of files --- .../corefork.telegram.org/api/channel.html | 2 + data/web/corefork.telegram.org/api/forum.html | 7 ++- .../constructor/forumTopic.html | 55 +++++++++---------- 3 files changed, 31 insertions(+), 33 deletions(-) diff --git a/data/web/corefork.telegram.org/api/channel.html b/data/web/corefork.telegram.org/api/channel.html index d2d4ef73e9..fd059beba1 100644 --- a/data/web/corefork.telegram.org/api/channel.html +++ b/data/web/corefork.telegram.org/api/channel.html @@ -53,6 +53,8 @@ Technically, they are represented by channel Technically, supergroups are actually channels: they are represented by channel constructors, with the megagroup flag set to true.

Channels can be created using the channels.createChannel method, by setting the megagroup flag.
Supergroups can also be assigned a geo_point to become geochats.

+

Forums

+

Supergroups can be converted into forums, splitting conversion into distinct forum topics, see the forum documentation for more info ».

Gigagroups

Gigagroups are something between a channel and a supergroup.
An admin, when prompted by the API using suggestions », can convert a megagroup into a gigagroup using channels.convertToGigagroup (one way only).
diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html index f8949a5f9d..659262fd04 100644 --- a/data/web/corefork.telegram.org/api/forum.html +++ b/data/web/corefork.telegram.org/api/forum.html @@ -53,7 +53,8 @@ channels.createChannel#91006707 flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true forum:flags.5?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string ttl_period:flags.4?int = Updates; channels.toggleForum#a4298b29 channel:InputChannel enabled:Bool = Updates; -

Forums may be created either by invoking channels.createChannel with the forum flag set, or by converting an existing supergroup into a forum using channels.toggleForum with enabled=true.

+

Forums may be created either by invoking channels.createChannel with the forum flag set, or by converting an existing supergroup into a forum using channels.toggleForum with enabled=true.
+If the group is a basic group, it should be upgraded to a supergroup before converting it into a forum.

Forums can also be converted back to supergroups using channels.toggleForum with enabled=false.

Note that the channels.toggleForum method can only be invoked by admins with owner rights.

Forums have the channel.forum flag set, and conversation happens in distinct forum topics.

@@ -88,9 +89,9 @@ 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 hands, 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, sendMedia et cetera.
+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, 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).

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.
diff --git a/data/web/corefork.telegram.org/constructor/forumTopic.html b/data/web/corefork.telegram.org/constructor/forumTopic.html index 9d7a8b1b48..22bd99b347 100644 --- a/data/web/corefork.telegram.org/constructor/forumTopic.html +++ b/data/web/corefork.telegram.org/constructor/forumTopic.html @@ -4,7 +4,8 @@ forumTopic - +Whether…"> - +Whether…"> @@ -68,7 +62,8 @@ pinned…">

forumTopic

-

+

Represents a forum topic.

+

  • Layer 155 @@ -99,17 +94,17 @@ pinned…"> my flags.1?true -  +Whether the topic was created by the current user closed flags.2?true -  +Whether the topic is closed (no messages can be sent to it) pinned flags.3?true -  +Whether the topic is pinned short @@ -119,22 +114,22 @@ pinned…"> hidden flags.6?true -  +Whether the topic is hidden (only valid for the "General" topic, id=1) id int -  +Topic ID date int -  +Topic creation date title string -  +Topic title icon_color @@ -149,47 +144,47 @@ pinned…"> top_message int -  +ID of the last message that was sent to this topic read_inbox_max_id int -  +Position up to which all incoming messages are read. read_outbox_max_id int -  +Position up to which all outgoing messages are read. unread_count int -  +Number of unread messages unread_mentions_count int -  +Number of unread mentions unread_reactions_count int -  +Number of unread reactions to messages you sent from_id Peer -  +ID of the peer that created the topic notify_settings PeerNotifySettings -  +Notification settings draft -flags.4?DraftMessage -  +flags.1?DraftMessage +Message draft