From 079e0d4a32005d3b7b9ee0a227469f1d02aa1804 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Fri, 4 Mar 2022 18:21:45 +0000 Subject: [PATCH] Update content of files --- data/corefork.telegram.org/api/invites.html | 14 ++++++-------- .../constructor/chatFull.html | 4 +++- .../constructor/chatInvite.html | 4 +++- .../constructor/updateBotChatInviteRequester.html | 2 ++ 4 files changed, 14 insertions(+), 10 deletions(-) diff --git a/data/corefork.telegram.org/api/invites.html b/data/corefork.telegram.org/api/invites.html index 4469cb2967..bdf4634046 100644 --- a/data/corefork.telegram.org/api/invites.html +++ b/data/corefork.telegram.org/api/invites.html @@ -4,10 +4,10 @@ Invites - + - + @@ -43,10 +43,7 @@

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.

Public usernames

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
 
 ---functions---
 
@@ -104,7 +101,8 @@ The first matching group can be passed to the hash parameter of messages.checkChatInvite may return chatInvitePeek, in which case the user may directly use to fetch chat messages until the time indicate by the expires unixtime field.

 
Newly created groups, supergroups and channel already have a default invite link.

 To generate a new one, use messages.exportChatInvite.

-To get info about existing chat invites, optionally filtering only links created by a given admin, use messages.getExportedChatInvites; messages.getExportedChatInvite can be used to obtain info about a specific invite link.  

+To get info about existing chat invites, optionally filtering only links created by a given admin, use messages.getExportedChatInvites.

+messages.getExportedChatInvite can be used to obtain info about a specific invite link.  

 
messages.editExportedChatInvite is used to edit or revoke existing invite links: revoked links cannot be used by users to join the group, but info about revoked links can still be fetched using messages.getExportedChatInvites with the revoke flag set.

 Use messages.deleteExportedChatInvite to permanently remove an invite link, and messages.deleteRevokedExportedChatInvites to permanently remove a revoked invite link.  

 
messages.getChatInviteImporters can be used to fetch info about users that joined using a specific invite link.  

@@ -136,7 +134,7 @@ Use messages.deleteExportedC
 
Bot administrators will receive a updateBotChatInviteRequester update for each separate join request.

 User administrators will receive an updatePendingJoinRequests, and should invoke messages.getChatInviteImporters with the requested flag set to obtain a list of users waiting to be admitted into the group.  

 
Administrators can then use messages.hideChatJoinRequest to approve or dismiss a join request, and messages.hideAllChatJoinRequests to approve or dismiss in bulk multiple join requests.  

-
Administrators can also choose to message the user before admitting them into the group: in this case, graphical clients on the user side should display a message on the dialog bar of the chat with the admin, indicating that the chat was initiated by the admin of a chat/channel they have recently requested to join, according to the information contained in the peerSettings ».  

+
Administrators can also choose send a message to the user before admitting them into the group: in this case, graphical clients on the user side should display a message on the dialog bar of the chat with the admin, indicating that the chat was initiated by the admin of a chat/channel they have recently requested to join, according to the information contained in the peerSettings ».  

   
 
           
diff --git a/data/corefork.telegram.org/constructor/chatFull.html b/data/corefork.telegram.org/constructor/chatFull.html
index 83c520df80..0263042414 100644
--- a/data/corefork.telegram.org/constructor/chatFull.html
+++ b/data/corefork.telegram.org/constructor/chatFull.html
@@ -170,7 +170,9 @@
 
Folders

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

 
phone.getGroupCallJoinAs

-
Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+
Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+
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/chatInvite.html b/data/corefork.telegram.org/constructor/chatInvite.html
index daab383398..b36f0bf4a4 100644
--- a/data/corefork.telegram.org/constructor/chatInvite.html
+++ b/data/corefork.telegram.org/constructor/chatInvite.html
@@ -124,7 +124,9 @@
 
ChatInvite

 
Related pages

 
Channels

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

+
How to handle channels, supergroups, 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/updateBotChatInviteRequester.html b/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html
index f6e2f8fadd..c99996d32b 100644
--- a/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html
+++ b/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html
@@ -98,6 +98,8 @@
 
Type

 
Update

 
Related pages

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

 
Working with Updates

 
How to subscribe to updates and handle them properly.

 
updatePendingJoinRequests