diff --git a/data/web/corefork.telegram.org/api/folders.html b/data/web/corefork.telegram.org/api/folders.html index 032e12ec4a..a14da8cdf5 100644 --- a/data/web/corefork.telegram.org/api/folders.html +++ b/data/web/corefork.telegram.org/api/folders.html @@ -121,9 +121,9 @@ An optional name for the shared link may also be specified using titleUse chatlists.getExportedInvites to list all links generated for a folder, use chatlists.editExportedInvite to edit the title or list of peers of a specific link and chatlists.deleteExportedInvite to revoke an exported link, preventing new users from importing it.

Use chatlists.checkChatlistInvite to obtain information about a chat folder deep link before importing it with chatlists.joinChatlistInvite, specifying in peers which channels and groups to join (excluding inaccessible channels/supergroups, i.e. the user may not join a supergroup/channel where they were banned, corresponding to a channelForbidden constructor).
If the user can't join any of the peers of a folder, the folder can't be imported.

-

Users that import a folder should retrieve additions made to the peer list by invoking chatlists.getChatlistUpdates at most every chatlist_update_period seconds (a client configuration parameter »).
+

Users that import a folder should retrieve additions made to the peer list by invoking chatlists.getChatlistUpdates at most every chatlist_update_period seconds (a client configuration parameter »).
If the returned missing_peers list is non-empty, the client should present it to the user, who may choose to join all or a subset of them (excluding inaccessible channels/supergroups), passing them to the peers parameter of chatlists.joinChatlistUpdates.
-If, after excluding inaccessible peers and peers deselected by the user, the peers parameter is empty, invoke chatlists.hideChatlistUpdates instead of chatlists.joinChatlistUpdates.

+If, after excluding inaccessible peers and peers deselected by the user the peers list is empty, invoke chatlists.hideChatlistUpdates instead of chatlists.joinChatlistUpdates.

Peer folders

The API also has another method for identifying groups of peers, used by archived chats.

Schema:

diff --git a/data/web/corefork.telegram.org/api/fragment.html b/data/web/corefork.telegram.org/api/fragment.html index 1a3a3126bd..407146732c 100644 --- a/data/web/corefork.telegram.org/api/fragment.html +++ b/data/web/corefork.telegram.org/api/fragment.html @@ -67,13 +67,13 @@ channels.deactivateAllUsernames#0a245dd3 channel:InputChannel = Bool;

Collectible usernames work just like basic @usernames, they appear in Global Search results and have deep links », just like basic usernames.

The ownership of collectible usernames is secured by TON, a fast and scalable blockchain network. They can be bought and sold through the Fragment platform », giving a simple and secure way to acquire and exchange valuable Telegram domains.

-

On the Fragment platform, clients may associate or dissociate purchased collectible usernames either to their Telegram account, or to a channel/supergroup they own.

+

On the Fragment platform, clients may associate or dissociate purchased collectible usernames either to their Telegram account, or to a bot/channel/supergroup they own.

If any collectible username is associated to an account, channel or supergroup, user.username and channel.username won't be set, and user.usernames and channel.usernames will be set, instead: these fields contain an array of username constructors, which indicate whether a certain username is a basic username (editable is set) or a collectible username (editable is not set); and whether a collectible username is active or not.
The first username in the usernames vector must be shown in-UI as the main username.

-

Immediately after association, a username is marked as not active (i.e. only the owner can see it in the usernames list): use account.toggleUsername and channels.toggleUsername to mark it as active.
+

Immediately after association, a username is marked as not active (i.e. only the owner can see it in the usernames list): use account.toggleUsername, bots.toggleUsername or channels.toggleUsername to mark it as active.
Note that you can't mark as inactive the basic (non-collectible) username, if any.

channels.deactivateAllUsernames may also be used to mark as inactive all collectible usernames associated to a certain supergroup or channel.

-

Use account.reorderUsernames/channels.reorderUsernames to change the order of the usernames associated to an account, channel or supergroup: all currently active usernames must be specified.

+

Use account.reorderUsernames/bots.reorderUsernames/channels.reorderUsernames to change the order of the usernames associated to an account, channel or supergroup: all currently active usernames must be specified.

diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index ab509adf7b..1e0e94a313 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -49,16 +49,16 @@

Schema changes

New Methods
New Constructors
New Constructors