From f6acce6300a9a2341de038f4727003f6125cfdb1 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Thu, 10 Mar 2022 19:05:54 +0000 Subject: [PATCH] Update content of files --- data/corefork.telegram.org/api/channel.html | 29 +++++++++++-------- .../corefork.telegram.org/api/discussion.html | 2 +- data/corefork.telegram.org/api/files.html | 2 +- .../api/push-updates.html | 6 ++-- data/corefork.telegram.org/api/updates.html | 2 +- .../botCommandScopeChatAdmins.html | 2 +- .../constructor/botCommandScopeChats.html | 2 +- .../botCommandScopePeerAdmins.html | 2 +- .../constructor/botCommandScopePeerUser.html | 2 +- .../constructor/channel.html | 2 +- ...LogEventActionParticipantJoinByInvite.html | 2 +- .../constructor/channelFull.html | 2 +- .../constructor/chat.html | 2 +- .../constructor/chatAdminRights.html | 2 +- .../constructor/chatBannedRights.html | 2 +- .../constructor/chatInvite.html | 2 +- .../constructor/config.html | 2 +- .../inlineQueryPeerTypeBroadcast.html | 2 +- .../constructor/inlineQueryPeerTypeChat.html | 2 +- .../inlineQueryPeerTypeMegagroup.html | 2 +- .../constructor/inputNotifyBroadcasts.html | 2 +- .../messageActionChannelMigrateFrom.html | 2 +- .../messageActionChatMigrateTo.html | 2 +- .../updateChannelAvailableMessages.html | 2 +- .../constructor/updateChannelParticipant.html | 2 +- .../updateChannelReadMessagesContents.html | 2 +- .../constructor/updateChannelUserTyping.html | 2 +- .../constructor/updateChannelWebPage.html | 2 +- .../updateChatDefaultBannedRights.html | 2 +- .../constructor/updateChatParticipant.html | 2 +- .../updateChatParticipantAdmin.html | 2 +- .../updateDeleteChannelMessages.html | 2 +- .../constructor/updateEditChannelMessage.html | 2 +- .../constructor/updateGroupCall.html | 2 +- .../constructor/updateNewChannelMessage.html | 2 +- .../updatePinnedChannelMessages.html | 2 +- .../updateReadChannelDiscussionInbox.html | 2 +- .../updateReadChannelDiscussionOutbox.html | 2 +- .../constructor/updateReadChannelInbox.html | 2 +- .../constructor/updateReadChannelOutbox.html | 2 +- .../method/account.initTakeoutSession | 2 +- .../method/channels.checkUsername | 2 +- .../method/channels.convertToGigagroup | 2 +- .../method/channels.createChannel | 2 +- .../method/channels.deleteChannel | 2 +- .../method/channels.deleteHistory | 2 +- .../method/channels.deleteMessages | 2 +- .../method/channels.editAdmin | 2 +- .../method/channels.editBanned | 2 +- .../method/channels.editLocation | 2 +- .../method/channels.editPhoto | 2 +- .../method/channels.editTitle | 2 +- .../method/channels.exportMessageLink | 2 +- .../method/channels.getAdminLog | 2 +- .../method/channels.getAdminedPublicChannels | 2 +- .../method/channels.getChannels | 2 +- .../method/channels.getGroupsForDiscussion | 2 +- .../method/channels.getLeftChannels | 2 +- .../method/channels.getMessages | 2 +- .../method/channels.getParticipant | 2 +- .../method/channels.getParticipants | 2 +- .../method/channels.leaveChannel | 2 +- .../method/channels.readHistory | 2 +- .../method/channels.readMessageContents | 2 +- .../method/channels.toggleSlowMode | 2 +- .../method/messages.deleteChat | 2 +- .../method/messages.editChatAbout | 2 +- .../method/messages.editChatAdmin | 2 +- .../messages.editChatDefaultBannedRights | 2 +- .../method/messages.getDiscussionMessage | 2 +- .../method/messages.getMessagesViews | 2 +- .../method/messages.migrateChat | 2 +- .../method/phone.createGroupCall | 2 +- .../method/stats.getMegagroupStats | 2 +- data/corefork.telegram.org/methods.html | 6 ++-- .../type/ChatAdminRights.html | 2 +- .../type/ChatBannedRights.html | 2 +- .../type/StatsGroupTopAdmin.html | 2 +- .../type/StatsGroupTopInviter.html | 2 +- .../type/StatsGroupTopPoster.html | 2 +- 80 files changed, 100 insertions(+), 95 deletions(-) diff --git a/data/corefork.telegram.org/api/channel.html b/data/corefork.telegram.org/api/channel.html index 85e0e86ebd..209ce46bff 100644 --- a/data/corefork.telegram.org/api/channel.html +++ b/data/corefork.telegram.org/api/channel.html @@ -2,12 +2,12 @@ - Channels + Channels, supergroups, gigagroups and legacy groups - - + + - + @@ -36,24 +36,29 @@
-
-

Channels

+
+

Channels, supergroups, gigagroups and legacy groups

-

Channels, chats, supergroups & gigagroups

+

Channels

Channels are a tool for broadcasting your messages to large audiences. They can have an unlimited number of subscribers, they can be public with a permanent URL and each post in a channel has its own view counter.
Technically, they are represented by channel constructors.

+

Channels can be created using the channels.createChannel method, by setting the broadcast flag.

+

Supergroups

Supergroups are a powerful tool for building communities and can support up to 200,000 members each.
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.

+

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).
After that, only admins will be able to write in the group (like when send_messages rights are disabled for all group participants by default), but the participant limit is removed and the group can become much bigger than a supergroup (e.g. >200,000 currently).
Also, one can't invite people into gigagroups and participants of voice chats in gigagroups are muted by default.

-

Channels and supergroups can be created using the channels.createChannel method, by setting the appropriate broadcast or megagroup flags.
-Supergroups can also be assigned a geo_point to become geochats.

-

In previous versions of telegram, only normal groups (represented by chat constructors) could be created using messages.createChat: these groups have fewer features, and can only have 200 members at max.

-

Migration

+

Legacy groups

+

In previous versions of telegram, only legacy groups (represented by chat constructors) could be created using messages.createChat: these groups have fewer features, and can only have 200 members at max.
+Messages from all legacy groups are stored in the user's message box »: this means that all legacy groups and all private chats share the same, single message ID and PTS sequence.

+

Migration

To upgrade a legacy group to a supergroup, messages.migrateChat can be used. The chats field of the result will have two objects:

    @@ -64,7 +69,7 @@ The chats field of the result will have two objects:

    All users of the chat will receive an updateNewMessage from the old chat with a messageService containing a messageActionChatMigrateTo constructor.

    All new messages have to be sent to the new supergroup.

    When working with migrated groups clients need to handle loading of the message history (as well as search results et cetera) from both the legacy group and the new supergroup. This is done by merging the two messages lists (requested with different Peer values) client side.

    -

    Invite links and join requests

    +

    Invite links and join requests

    Channels, legacy groups and supergroups may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.

    For more info on how to work with public usernames, invite links and join requests, see here ».

    Rights

    diff --git a/data/corefork.telegram.org/api/discussion.html b/data/corefork.telegram.org/api/discussion.html index 287aa6ebdb..5fda5c6e48 100644 --- a/data/corefork.telegram.org/api/discussion.html +++ b/data/corefork.telegram.org/api/discussion.html @@ -59,7 +59,7 @@ The discussion group can be accessed in the client by clicking on the discuss bu The comment section of a particular post can be disabled by removing the channel post message from the discussion group.

    Linking a discussion group

    To obtain a list of admined supergroups that a channel admin can possibly associate to a channel, use channels.getGroupsForDiscussion.
    -Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
    +Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
    Before linking a supergroup to a channel, access to the supergroup's old messages must also be enabled using channels.togglePreHistoryHidden.

    To set a returned supergroup as a discussion group use channels.setDiscussionGroup.

    Schema:

    diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html index e252cdc4e5..3c317ab1b8 100644 --- a/data/corefork.telegram.org/api/files.html +++ b/data/corefork.telegram.org/api/files.html @@ -148,7 +148,7 @@ The SHA256 hash of the file is computed, and it is passed along with the file's

    Animated profile pictures

    Animated profile pictures are also supported, by populating the video constructor: square MPEG4 videos up to 1080x1080 are supported, 800x800 is the recommended resolution.
    The video_start_ts is a floating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.

    -

    Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (legacy groups) or channels.editPhoto (channels, supergroups).
    +

    Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (legacy groups) or channels.editPhoto (channels, supergroups).
    Use the inputChatPhoto to reuse previously uploaded profile pictures.

    Downloading files

    There are methods available to download files which have been successfully uploaded. The schema of the types and methods used is presented below:

    diff --git a/data/corefork.telegram.org/api/push-updates.html b/data/corefork.telegram.org/api/push-updates.html index 36caffe383..ba6a4534ed 100644 --- a/data/corefork.telegram.org/api/push-updates.html +++ b/data/corefork.telegram.org/api/push-updates.html @@ -71,8 +71,8 @@

Notification encryption

For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to account.registerDevice (secret). This key (auth_key) is used to encrypt the payloads using MTProto v2.

-

The FCM payload will be a JSON payload, containing a p field with the base64-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

-

Example implementation.

+

The FCM payload will be a JSON payload, containing a p field with the base64url-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

+

Example implementation.

As mentioned above, payloads can also be encrypted using P-256 Elliptic Curve Diffie-Hellman when using web push.

Notification structure

An (optionally encrypted) notification is provided as a JSON object in the following format:

@@ -102,7 +102,7 @@
  • contact_id - Telegram user identifier of contact that joined Telegram in CONTACT_JOINED
  • msg_id - Message ID for new message event or reaction event
  • channel_id - Identifier of the channel/supergroup where the event occurred
    • -
  • chat_id - Identifier of the legacy group where the event occurred
    • +
  • chat_id - Identifier of the legacy group where the event occurred
  • from_id - User ID where the event occurred
  • chat_from_broadcast_id - If the group message was sent as a channel, this field will contain the sender channel ID
  • chat_from_group_id - If the group message was sent as a supergroup, this field will contain the sender supergroup ID
    • diff --git a/data/corefork.telegram.org/api/updates.html b/data/corefork.telegram.org/api/updates.html index 7bbca7a6b1..8e7d33d44a 100644 --- a/data/corefork.telegram.org/api/updates.html +++ b/data/corefork.telegram.org/api/updates.html @@ -69,7 +69,7 @@ All boxes are completely independent, and each pts sequence is tied to just one box (see below).

    Update object may contain info about multiple events (for example, updateDeleteMessages). That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).

    -

    Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. +

    Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence.

    To recap, the client has to take care of the integrity of the following sequences to properly handle updates:

      diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html b/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html index f3091c0242..9906707d6f 100644 --- a/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html +++ b/data/corefork.telegram.org/constructor/botCommandScopeChatAdmins.html @@ -58,7 +58,7 @@

      Type

      BotCommandScope

      Related pages

      -

      Channels

      +

      Channels, supergroups, gigagroups and legacy groups

      How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChats.html b/data/corefork.telegram.org/constructor/botCommandScopeChats.html index 8e8ec80b7c..f452723090 100644 --- a/data/corefork.telegram.org/constructor/botCommandScopeChats.html +++ b/data/corefork.telegram.org/constructor/botCommandScopeChats.html @@ -58,7 +58,7 @@

    Type

    BotCommandScope

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html b/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html index 95686eb796..ad4fe41e18 100644 --- a/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html +++ b/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html @@ -73,7 +73,7 @@

    Type

    BotCommandScope

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html index b76984a488..73d004390e 100644 --- a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html +++ b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html @@ -78,7 +78,7 @@

    Type

    BotCommandScope

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/channel.html b/data/corefork.telegram.org/constructor/channel.html index ad942d4ac9..0de6949d78 100644 --- a/data/corefork.telegram.org/constructor/channel.html +++ b/data/corefork.telegram.org/constructor/channel.html @@ -215,7 +215,7 @@

    Related pages

    Min constructors

    In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Admin, banned, default rights

    How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

    diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html index f35b9e9a68..b9bb8a8008 100644 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html @@ -73,7 +73,7 @@

    Type

    ChannelAdminLogEventAction

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/channelFull.html b/data/corefork.telegram.org/constructor/channelFull.html index 61c722dc9c..2d4b3d30ec 100644 --- a/data/corefork.telegram.org/constructor/channelFull.html +++ b/data/corefork.telegram.org/constructor/channelFull.html @@ -296,7 +296,7 @@

    Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

    Admin, banned, default rights

    How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Pinned messages

    Telegram allows pinning multiple messages on top of a specific chat.

    diff --git a/data/corefork.telegram.org/constructor/chat.html b/data/corefork.telegram.org/constructor/chat.html index 51949ca4f7..204ec56e15 100644 --- a/data/corefork.telegram.org/constructor/chat.html +++ b/data/corefork.telegram.org/constructor/chat.html @@ -153,7 +153,7 @@

    Type

    Chat

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Admin, banned, default rights

    How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

    diff --git a/data/corefork.telegram.org/constructor/chatAdminRights.html b/data/corefork.telegram.org/constructor/chatAdminRights.html index c96487cc97..e35c7e476f 100644 --- a/data/corefork.telegram.org/constructor/chatAdminRights.html +++ b/data/corefork.telegram.org/constructor/chatAdminRights.html @@ -128,7 +128,7 @@

    Type

    ChatAdminRights

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/chatBannedRights.html b/data/corefork.telegram.org/constructor/chatBannedRights.html index 65669bfbc6..1170a6f704 100644 --- a/data/corefork.telegram.org/constructor/chatBannedRights.html +++ b/data/corefork.telegram.org/constructor/chatBannedRights.html @@ -138,7 +138,7 @@

    Type

    ChatBannedRights

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/chatInvite.html b/data/corefork.telegram.org/constructor/chatInvite.html index fc5423dcc4..807793bc32 100644 --- a/data/corefork.telegram.org/constructor/chatInvite.html +++ b/data/corefork.telegram.org/constructor/chatInvite.html @@ -123,7 +123,7 @@

    Type

    ChatInvite

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Invites

    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.

    diff --git a/data/corefork.telegram.org/constructor/config.html b/data/corefork.telegram.org/constructor/config.html index eeb167bff3..3d7502b903 100644 --- a/data/corefork.telegram.org/constructor/config.html +++ b/data/corefork.telegram.org/constructor/config.html @@ -334,7 +334,7 @@

    Binding temporary authorization key to permanent ones.

    help.getConfig

    Returns current configuration, including data center configuration.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    messages.forwardMessages

    Forwards messages by their IDs.

    diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html index 04ae2ad28c..456ee8c65f 100644 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html @@ -58,7 +58,7 @@

    Type

    InlineQueryPeerType

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html index 4ae55ff3a7..2e33dcd279 100644 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeChat.html @@ -58,7 +58,7 @@

    Type

    InlineQueryPeerType

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html index eef494a8e9..b244ef3784 100644 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html @@ -58,7 +58,7 @@

    Type

    InlineQueryPeerType

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html index b5fc12596d..507f316585 100644 --- a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html +++ b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html @@ -58,7 +58,7 @@

    Type

    InputNotifyPeer

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html index 322a351bc7..ab8a67848d 100644 --- a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html +++ b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html @@ -78,7 +78,7 @@

    Type

    MessageAction

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html index 4079690414..8e0b8f007d 100644 --- a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html +++ b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html @@ -73,7 +73,7 @@

    Type

    MessageAction

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html b/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html index b4200a66c1..bfef854360 100644 --- a/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html +++ b/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html @@ -78,7 +78,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateChannelParticipant.html b/data/corefork.telegram.org/constructor/updateChannelParticipant.html index 1cc289f51d..3400bc9049 100644 --- a/data/corefork.telegram.org/constructor/updateChannelParticipant.html +++ b/data/corefork.telegram.org/constructor/updateChannelParticipant.html @@ -113,7 +113,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Working with Updates

    How to subscribe to updates and handle them properly.

    diff --git a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html index 0e7a2b2a96..2a24077fc8 100644 --- a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html +++ b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html @@ -78,7 +78,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html index 4766688006..d1bcb503c5 100644 --- a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html +++ b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html @@ -95,7 +95,7 @@

    Related pages

    Threads

    Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateChannelWebPage.html b/data/corefork.telegram.org/constructor/updateChannelWebPage.html index 6b56a91598..60dac4c255 100644 --- a/data/corefork.telegram.org/constructor/updateChannelWebPage.html +++ b/data/corefork.telegram.org/constructor/updateChannelWebPage.html @@ -88,7 +88,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Working with Updates

    How to subscribe to updates and handle them properly.

    diff --git a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html index 99c8d77718..1eaf1cba65 100644 --- a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html +++ b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html @@ -83,7 +83,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateChatParticipant.html b/data/corefork.telegram.org/constructor/updateChatParticipant.html index e3ade33ae0..b7b484044d 100644 --- a/data/corefork.telegram.org/constructor/updateChatParticipant.html +++ b/data/corefork.telegram.org/constructor/updateChatParticipant.html @@ -113,7 +113,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Working with Updates

    How to subscribe to updates and handle them properly.

    diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html index 08e80ddece..3afecd11f3 100644 --- a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html +++ b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html @@ -88,7 +88,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html index 6f4b6b5f5c..97ae7219c6 100644 --- a/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html +++ b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html @@ -90,7 +90,7 @@

    Related pages

    Working with Updates

    How to subscribe to updates and handle them properly.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html index 65964fab68..3fcda82a08 100644 --- a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html +++ b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html @@ -85,7 +85,7 @@

    Related pages

    Working with Updates

    How to subscribe to updates and handle them properly.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateGroupCall.html b/data/corefork.telegram.org/constructor/updateGroupCall.html index cda0ab8958..7e93e3cd57 100644 --- a/data/corefork.telegram.org/constructor/updateGroupCall.html +++ b/data/corefork.telegram.org/constructor/updateGroupCall.html @@ -78,7 +78,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html index f8b1c09405..f31b71d1bb 100644 --- a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html +++ b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html @@ -85,7 +85,7 @@

    Related pages

    Working with Updates

    How to subscribe to updates and handle them properly.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html b/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html index 552c0cf716..8c7b2f2fff 100644 --- a/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html +++ b/data/corefork.telegram.org/constructor/updatePinnedChannelMessages.html @@ -100,7 +100,7 @@

    Related pages

    Working with Updates

    How to subscribe to updates and handle them properly.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html index 12d5155551..8ab79c1296 100644 --- a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html +++ b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html @@ -98,7 +98,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Threads

    Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

    diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html index aa7281a406..83e7a9e8c1 100644 --- a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html +++ b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html @@ -83,7 +83,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Threads

    Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

    diff --git a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html index 3d43969d05..4fcd38a773 100644 --- a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html +++ b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html @@ -102,7 +102,7 @@

    Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

    Working with Updates

    How to subscribe to updates and handle them properly.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html index 5879300d35..e65ffe3740 100644 --- a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html +++ b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html @@ -78,7 +78,7 @@

    Type

    Update

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/account.initTakeoutSession b/data/corefork.telegram.org/method/account.initTakeoutSession index ffedf512e0..89b99138c1 100644 --- a/data/corefork.telegram.org/method/account.initTakeoutSession +++ b/data/corefork.telegram.org/method/account.initTakeoutSession @@ -127,7 +127,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.checkUsername b/data/corefork.telegram.org/method/channels.checkUsername index 3191f5199a..822f218b78 100644 --- a/data/corefork.telegram.org/method/channels.checkUsername +++ b/data/corefork.telegram.org/method/channels.checkUsername @@ -113,7 +113,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.convertToGigagroup b/data/corefork.telegram.org/method/channels.convertToGigagroup index b6ec3bd6a2..cd31f360ef 100644 --- a/data/corefork.telegram.org/method/channels.convertToGigagroup +++ b/data/corefork.telegram.org/method/channels.convertToGigagroup @@ -103,7 +103,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Client configuration

    The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

    diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel index a0b9879a7d..d74a980f98 100644 --- a/data/corefork.telegram.org/method/channels.createChannel +++ b/data/corefork.telegram.org/method/channels.createChannel @@ -153,7 +153,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    messages.initHistoryImport

    Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

    diff --git a/data/corefork.telegram.org/method/channels.deleteChannel b/data/corefork.telegram.org/method/channels.deleteChannel index d737e2f625..b478f28498 100644 --- a/data/corefork.telegram.org/method/channels.deleteChannel +++ b/data/corefork.telegram.org/method/channels.deleteChannel @@ -123,7 +123,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.deleteHistory b/data/corefork.telegram.org/method/channels.deleteHistory index 255d2b7e99..601bb16e8c 100644 --- a/data/corefork.telegram.org/method/channels.deleteHistory +++ b/data/corefork.telegram.org/method/channels.deleteHistory @@ -103,7 +103,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.deleteMessages b/data/corefork.telegram.org/method/channels.deleteMessages index 09ac421ced..6d3f3f299b 100644 --- a/data/corefork.telegram.org/method/channels.deleteMessages +++ b/data/corefork.telegram.org/method/channels.deleteMessages @@ -113,7 +113,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.editAdmin b/data/corefork.telegram.org/method/channels.editAdmin index 70262b3732..f0efb22b6e 100644 --- a/data/corefork.telegram.org/method/channels.editAdmin +++ b/data/corefork.telegram.org/method/channels.editAdmin @@ -224,7 +224,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.editBanned b/data/corefork.telegram.org/method/channels.editBanned index 2279fdb057..6bd23cb9e7 100644 --- a/data/corefork.telegram.org/method/channels.editBanned +++ b/data/corefork.telegram.org/method/channels.editBanned @@ -154,7 +154,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.editLocation b/data/corefork.telegram.org/method/channels.editLocation index abfb152295..d54b405e7f 100644 --- a/data/corefork.telegram.org/method/channels.editLocation +++ b/data/corefork.telegram.org/method/channels.editLocation @@ -113,7 +113,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.editPhoto b/data/corefork.telegram.org/method/channels.editPhoto index 8e6eeef223..e36734a223 100644 --- a/data/corefork.telegram.org/method/channels.editPhoto +++ b/data/corefork.telegram.org/method/channels.editPhoto @@ -144,7 +144,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    File references

    How to handle file references.

    diff --git a/data/corefork.telegram.org/method/channels.editTitle b/data/corefork.telegram.org/method/channels.editTitle index e845295109..8a2a001eea 100644 --- a/data/corefork.telegram.org/method/channels.editTitle +++ b/data/corefork.telegram.org/method/channels.editTitle @@ -129,7 +129,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.exportMessageLink b/data/corefork.telegram.org/method/channels.exportMessageLink index e893286dde..f4d1418bec 100644 --- a/data/corefork.telegram.org/method/channels.exportMessageLink +++ b/data/corefork.telegram.org/method/channels.exportMessageLink @@ -127,7 +127,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.getAdminLog b/data/corefork.telegram.org/method/channels.getAdminLog index 5f32a760e0..748bb7e2a1 100644 --- a/data/corefork.telegram.org/method/channels.getAdminLog +++ b/data/corefork.telegram.org/method/channels.getAdminLog @@ -149,7 +149,7 @@

    Related pages

    Pagination in the API

    How to fetch results from large lists of objects.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels index 5c187ec6b3..63f66f8054 100644 --- a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels +++ b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels @@ -108,7 +108,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    channels.checkUsername

    Check if a username is free and can be assigned to a channel/supergroup

    diff --git a/data/corefork.telegram.org/method/channels.getChannels b/data/corefork.telegram.org/method/channels.getChannels index cf5caa8f7c..b7c0562761 100644 --- a/data/corefork.telegram.org/method/channels.getChannels +++ b/data/corefork.telegram.org/method/channels.getChannels @@ -109,7 +109,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion index 2e8abeb394..3cd3b679c6 100644 --- a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion +++ b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion @@ -65,7 +65,7 @@ To set a returned supergroup as a discussion group, access to its old messages m

    Related pages

    Discussion groups

    Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    channels.togglePreHistoryHidden

    Hide/unhide message history for new channel/supergroup users

    diff --git a/data/corefork.telegram.org/method/channels.getLeftChannels b/data/corefork.telegram.org/method/channels.getLeftChannels index 09c4808ea3..6542ba8323 100644 --- a/data/corefork.telegram.org/method/channels.getLeftChannels +++ b/data/corefork.telegram.org/method/channels.getLeftChannels @@ -95,7 +95,7 @@

    Related pages

    Pagination in the API

    How to fetch results from large lists of objects.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.getMessages b/data/corefork.telegram.org/method/channels.getMessages index 3acbe6cea6..28c09187ff 100644 --- a/data/corefork.telegram.org/method/channels.getMessages +++ b/data/corefork.telegram.org/method/channels.getMessages @@ -121,7 +121,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.getParticipant b/data/corefork.telegram.org/method/channels.getParticipant index a1180c59b9..978f74e16f 100644 --- a/data/corefork.telegram.org/method/channels.getParticipant +++ b/data/corefork.telegram.org/method/channels.getParticipant @@ -128,7 +128,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.getParticipants b/data/corefork.telegram.org/method/channels.getParticipants index 7333577ee2..208cf83dde 100644 --- a/data/corefork.telegram.org/method/channels.getParticipants +++ b/data/corefork.telegram.org/method/channels.getParticipants @@ -126,7 +126,7 @@

    Related pages

    Pagination in the API

    How to fetch results from large lists of objects.

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.leaveChannel b/data/corefork.telegram.org/method/channels.leaveChannel index b58711db96..b5812ba154 100644 --- a/data/corefork.telegram.org/method/channels.leaveChannel +++ b/data/corefork.telegram.org/method/channels.leaveChannel @@ -129,7 +129,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.readHistory b/data/corefork.telegram.org/method/channels.readHistory index 074968a75d..77bd21390c 100644 --- a/data/corefork.telegram.org/method/channels.readHistory +++ b/data/corefork.telegram.org/method/channels.readHistory @@ -108,7 +108,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.readMessageContents b/data/corefork.telegram.org/method/channels.readMessageContents index 1540a1769c..454965612b 100644 --- a/data/corefork.telegram.org/method/channels.readMessageContents +++ b/data/corefork.telegram.org/method/channels.readMessageContents @@ -108,7 +108,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/channels.toggleSlowMode b/data/corefork.telegram.org/method/channels.toggleSlowMode index fcc311a105..8337cda36a 100644 --- a/data/corefork.telegram.org/method/channels.toggleSlowMode +++ b/data/corefork.telegram.org/method/channels.toggleSlowMode @@ -113,7 +113,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/messages.deleteChat b/data/corefork.telegram.org/method/messages.deleteChat index 9f38b71507..94699b8c8c 100644 --- a/data/corefork.telegram.org/method/messages.deleteChat +++ b/data/corefork.telegram.org/method/messages.deleteChat @@ -103,7 +103,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/messages.editChatAbout b/data/corefork.telegram.org/method/messages.editChatAbout index 73f35268ef..58bdf4380e 100644 --- a/data/corefork.telegram.org/method/messages.editChatAbout +++ b/data/corefork.telegram.org/method/messages.editChatAbout @@ -139,7 +139,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/messages.editChatAdmin b/data/corefork.telegram.org/method/messages.editChatAdmin index f76538c56c..3b9e8743d0 100644 --- a/data/corefork.telegram.org/method/messages.editChatAdmin +++ b/data/corefork.telegram.org/method/messages.editChatAdmin @@ -118,7 +118,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights b/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights index a8ad52ab16..cf61aaf615 100644 --- a/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights +++ b/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights @@ -129,7 +129,7 @@

    Bots can use this method

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/messages.getDiscussionMessage b/data/corefork.telegram.org/method/messages.getDiscussionMessage index 6b14cdb444..61e92b2d91 100644 --- a/data/corefork.telegram.org/method/messages.getDiscussionMessage +++ b/data/corefork.telegram.org/method/messages.getDiscussionMessage @@ -107,7 +107,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Threads

    Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

    diff --git a/data/corefork.telegram.org/method/messages.getMessagesViews b/data/corefork.telegram.org/method/messages.getMessagesViews index bad2562f91..9490eaf9a1 100644 --- a/data/corefork.telegram.org/method/messages.getMessagesViews +++ b/data/corefork.telegram.org/method/messages.getMessagesViews @@ -122,7 +122,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/messages.migrateChat b/data/corefork.telegram.org/method/messages.migrateChat index 10012672fd..39b01ff664 100644 --- a/data/corefork.telegram.org/method/messages.migrateChat +++ b/data/corefork.telegram.org/method/messages.migrateChat @@ -113,7 +113,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/phone.createGroupCall b/data/corefork.telegram.org/method/phone.createGroupCall index 86b1d70f1a..53879d716c 100644 --- a/data/corefork.telegram.org/method/phone.createGroupCall +++ b/data/corefork.telegram.org/method/phone.createGroupCall @@ -133,7 +133,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/method/stats.getMegagroupStats b/data/corefork.telegram.org/method/stats.getMegagroupStats index f942b64f40..24b2d8be66 100644 --- a/data/corefork.telegram.org/method/stats.getMegagroupStats +++ b/data/corefork.telegram.org/method/stats.getMegagroupStats @@ -112,7 +112,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    Channel statistics

    Telegram offers detailed channel statistics for channels and supergroups.

    diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html index adecc12903..dca08e1c92 100644 --- a/data/corefork.telegram.org/methods.html +++ b/data/corefork.telegram.org/methods.html @@ -581,7 +581,7 @@ channels.getGroupsForDiscussion -Get all groups that can be used as discussion groups.

    Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
    To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first. +Get all groups that can be used as discussion groups.

    Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
    To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first. channels.getMessages @@ -727,7 +727,7 @@ messages.editChatAdmin -Make a user admin in a legacy group. +Make a user admin in a legacy group. messages.editChatDefaultBannedRights @@ -763,7 +763,7 @@ messages.migrateChat -Turn a legacy group into a supergroup +Turn a legacy group into a supergroup channels.convertToGigagroup diff --git a/data/corefork.telegram.org/type/ChatAdminRights.html b/data/corefork.telegram.org/type/ChatAdminRights.html index a981bb2cfb..1d462ad343 100644 --- a/data/corefork.telegram.org/type/ChatAdminRights.html +++ b/data/corefork.telegram.org/type/ChatAdminRights.html @@ -69,7 +69,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/type/ChatBannedRights.html b/data/corefork.telegram.org/type/ChatBannedRights.html index 57af5426b1..66dbced87d 100644 --- a/data/corefork.telegram.org/type/ChatBannedRights.html +++ b/data/corefork.telegram.org/type/ChatBannedRights.html @@ -69,7 +69,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/type/StatsGroupTopAdmin.html b/data/corefork.telegram.org/type/StatsGroupTopAdmin.html index 92449861f4..46e2ad58c4 100644 --- a/data/corefork.telegram.org/type/StatsGroupTopAdmin.html +++ b/data/corefork.telegram.org/type/StatsGroupTopAdmin.html @@ -69,7 +69,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/type/StatsGroupTopInviter.html b/data/corefork.telegram.org/type/StatsGroupTopInviter.html index c7245462a4..35f2432c93 100644 --- a/data/corefork.telegram.org/type/StatsGroupTopInviter.html +++ b/data/corefork.telegram.org/type/StatsGroupTopInviter.html @@ -69,7 +69,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.

    diff --git a/data/corefork.telegram.org/type/StatsGroupTopPoster.html b/data/corefork.telegram.org/type/StatsGroupTopPoster.html index 3f9b035226..1224475eb4 100644 --- a/data/corefork.telegram.org/type/StatsGroupTopPoster.html +++ b/data/corefork.telegram.org/type/StatsGroupTopPoster.html @@ -69,7 +69,7 @@

    Related pages

    -

    Channels

    +

    Channels, supergroups, gigagroups and legacy groups

    How to handle channels, supergroups, gigagroups, legacy groups, and what's the difference between them.