From af1c5af8e81836e974e6ff2162b47cc9203b602c Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Fri, 4 Mar 2022 18:16:20 +0000 Subject: [PATCH] Update content of files --- data/corefork.telegram.org.html | 2 + data/corefork.telegram.org/api.html | 2 + data/corefork.telegram.org/api/channel.html | 3 + data/corefork.telegram.org/api/entities.html | 3 +- data/corefork.telegram.org/api/invites.html | 215 ++++++++++++++++++ data/corefork.telegram.org/api/layers.html | 4 +- .../api/obtaining_api_id.html | 2 +- data/corefork.telegram.org/api/passport.html | 2 +- data/corefork.telegram.org/bots/api.html | 2 +- .../constructor/channelFull.html | 2 +- .../constructor/chatFull.html | 2 +- .../constructor/chatInvite.html | 2 +- .../constructor/chatInviteImporter.html | 4 +- .../constructor/peerSettings.html | 4 +- .../updateBotChatInviteRequester.html | 4 +- .../updatePendingJoinRequests.html | 2 +- .../method/messages.getChatInviteImporters | 4 +- .../method/messages.hideAllChatJoinRequests | 6 +- .../method/messages.hideChatJoinRequest | 6 +- data/corefork.telegram.org/methods.html | 4 +- data/corefork.telegram.org/passport.html | 2 +- .../passport/sdk-javascript.html | 2 +- data/corefork.telegram.org/type/Updates.html | 4 +- 23 files changed, 253 insertions(+), 30 deletions(-) create mode 100644 data/corefork.telegram.org/api/invites.html diff --git a/data/corefork.telegram.org.html b/data/corefork.telegram.org.html index 67599db71c..1700b90669 100644 --- a/data/corefork.telegram.org.html +++ b/data/corefork.telegram.org.html @@ -134,6 +134,8 @@ This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

Polls

Telegram allows sending polls and quizzes, that can be voted on by thousands, if not millions of users in chats and channels.

+

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.

Admin, banned and default rights for channels, supergroups and groups

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

Discussion groups

diff --git a/data/corefork.telegram.org/api.html b/data/corefork.telegram.org/api.html index 67599db71c..1700b90669 100644 --- a/data/corefork.telegram.org/api.html +++ b/data/corefork.telegram.org/api.html @@ -134,6 +134,8 @@ This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

Polls

Telegram allows sending polls and quizzes, that can be voted on by thousands, if not millions of users in chats and channels.

+

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.

Admin, banned and default rights for channels, supergroups and groups

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

Discussion groups

diff --git a/data/corefork.telegram.org/api/channel.html b/data/corefork.telegram.org/api/channel.html index f35fb28944..85e0e86ebd 100644 --- a/data/corefork.telegram.org/api/channel.html +++ b/data/corefork.telegram.org/api/channel.html @@ -64,6 +64,9 @@ 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

+

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

Channels, legacy groups and supergroups allow setting granular permissions both for admins and specific users; channels, supergroups and legacy groups also allow setting global granular permissions for users.

For more info on how to set and modify rights, see here ».

diff --git a/data/corefork.telegram.org/api/entities.html b/data/corefork.telegram.org/api/entities.html index f07a6e1748..7bf2318651 100644 --- a/data/corefork.telegram.org/api/entities.html +++ b/data/corefork.telegram.org/api/entities.html @@ -61,7 +61,8 @@ code + +

A number of other entities are also available, see the type page for the full list ».

diff --git a/data/corefork.telegram.org/api/invites.html b/data/corefork.telegram.org/api/invites.html new file mode 100644 index 0000000000..4469cb2967 --- /dev/null +++ b/data/corefork.telegram.org/api/invites.html @@ -0,0 +1,215 @@ + + + + + Invites + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+
+
+
+

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.

+

Public usernames

+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+
+---functions---
+
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;
+
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
+

Only supergroups and channels may have a public usernames: normal groups must be migrated to a supergroup before they can be assigned a username, see the migration docs » for more info.

+

channels.updateUsername can be used to directly assign or change the public username of a supergroup or channel.
+You can use channels.checkUsername before assigning the username to make sure that the specified username is valid and available.

+

channels.joinChannel can be used to join a supergroup or channel using peer information obtained using contacts.resolveUsername.

+

Invite links

+
chatInviteExported#ab4a819 flags:# revoked:flags.0?true permanent:flags.5?true request_needed:flags.6?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int requested:flags.7?int title:flags.8?string = ExportedChatInvite;
+
+messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+
+messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+
+chatInviteImporter#8c5adfd9 flags:# requested:flags.0?true user_id:long date:int about:flags.2?string approved_by:flags.1?long = ChatInviteImporter;
+
+messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+
+chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;
+
+messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+
+chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#300c44c1 flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true request_needed:flags.6?true title:string about:flags.5?string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+
+---functions---
+
+messages.exportChatInvite#a02ce5d5 flags:# legacy_revoke_permanent:flags.2?true request_needed:flags.3?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int title:flags.4?string = ExportedChatInvite;
+
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+
+messages.editExportedChatInvite#bdca2f75 flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int request_needed:flags.3?Bool title:flags.4?string = messages.ExportedChatInvite;
+
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
+
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;
+messages.getChatInviteImporters#df04dd4e flags:# requested:flags.0?true peer:InputPeer link:flags.1?string q:flags.2?string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;
+
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;
+messages.importChatInvite#6c50051c hash:string = Updates;
+

Private invite links can optionally have an expiration date, a usage limit, and can even be set to only allow users into the channel, supergroup or group upon explicit approval of an admin: see join requests » for more info.

+

Invite links match the following regex: @(?:t|telegram)\.(?:me|dog)/(joinchat/|\+)?([\w-]+)@i.
+The first matching group can be passed to the hash parameter of messages.checkChatInvite to get info about the chat, and messages.importChatInvite to join the chat.
+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.

+

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.

+

Some basic stats about the number of invite links generated by a given admin can be fetched using messages.getAdminsWithInvites.

+

Join requests

+
chatInvite#300c44c1 flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true request_needed:flags.6?true title:string about:flags.5?string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+
+updatePendingJoinRequests#7063c3db peer:Peer requests_pending:int recent_requesters:Vector<long> = Update;
+updateBotChatInviteRequester#11dfa986 peer:Peer date:int user_id:long about:string invite:ExportedChatInvite qts:int = Update;
+
+messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+peerSettings#a518110d flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true request_chat_broadcast:flags.10?true geo_distance:flags.6?int request_chat_title:flags.9?string request_chat_date:flags.9?int = PeerSettings;
+
+messageActionChatJoinedByRequest#ebbca3cb = MessageAction;
+
+channelAdminLogEventActionParticipantJoinByRequest#afb6144a invite:ExportedChatInvite approved_by:long = ChannelAdminLogEventAction;
+
+---functions---
+
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;
+messages.importChatInvite#6c50051c hash:string = Updates;
+
+messages.getChatInviteImporters#df04dd4e flags:# requested:flags.0?true peer:InputPeer link:flags.1?string q:flags.2?string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;
+
+messages.hideChatJoinRequest#7fe7e815 flags:# approved:flags.0?true peer:InputPeer user_id:InputUser = Updates;
+messages.hideAllChatJoinRequests#e085f4ea flags:# approved:flags.0?true peer:InputPeer link:flags.1?string = Updates;
+

If the request_needed flag is set when generating or editing an invite link, users importing the invite link using messages.importChatInvite will receive an INVITE_REQUEST_SENT RPC error, indicating that an join request was successfully sent to the chat admins.

+

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

+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/layers.html b/data/corefork.telegram.org/api/layers.html index 58657dfd19..04140c3d3e 100644 --- a/data/corefork.telegram.org/api/layers.html +++ b/data/corefork.telegram.org/api/layers.html @@ -296,13 +296,13 @@ Layer…"> account.changeAuthorizationSettings#40f48462 flags:# hash:long encrypted_requests_disabled:flags.0?Bool call_requests_disabled:flags.1?Bool = Bool;
channels.deleteParticipantHistory#367544db channel:InputChannel participant:InputPeer = messages.AffectedHistory;

Layer 134

-

Join requests, delete by date, global chat themes, hyper-speed scrolling and calendar view for shared media, sponsored channel posts.

+

Join requests, delete by date, global chat themes, hyper-speed scrolling and calendar view for shared media, sponsored channel posts.

Schema changes

New Methods
Changed Methods