From 843d2338c50bff48bf99d3cb4cca67533b4afc20 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Tue, 18 Apr 2023 20:32:58 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/auth.html | 4 ++-- data/web/corefork.telegram.org/api/layers.html | 2 +- .../web/corefork.telegram.org/method/channels.getFullChannel | 5 ----- data/web/corefork.telegram.org/method/channels.getMessages | 5 ----- .../corefork.telegram.org/method/channels.toggleJoinRequest | 2 +- .../web/corefork.telegram.org/method/messages.getPeerDialogs | 5 ----- data/web/corefork.telegram.org/method/users.getUsers | 5 ----- data/web/corefork.telegram.org/methods.html | 2 +- 8 files changed, 5 insertions(+), 25 deletions(-) diff --git a/data/web/corefork.telegram.org/api/auth.html b/data/web/corefork.telegram.org/api/auth.html index cd9024e15c..3942f50b75 100644 --- a/data/web/corefork.telegram.org/api/auth.html +++ b/data/web/corefork.telegram.org/api/auth.html @@ -56,7 +56,7 @@ However, this is not always the case, if future auth tokens are used:

Future auth tokens

When invoking auth.logOut on a previously authorized session with 2FA enabled, the server may return a future_auth_token, which should be stored in the local database.
A future_auth_token is also contained in the auth.authorization returned when logging in.
-At all times, the future auth token database should contain at most 20 tokens: evict older tokens as new tokens are added.
+At all times, the future auth token database should contain at most 20 tokens: evict older tokens as new tokens are added to stay below this limit.
When invoking auth.sendCode, all future auth tokens present in the database should be provided to codeSettings.logout_tokens.
If any of the future auth tokens matches the account we're trying to login into and the token hasn't expired, auth.sendCode will directly return a SESSION_PASSWORD_NEEDED RPC error, directly asking the user to enter the 2FA password, without sending any authorization code.

Otherwise, the system will send an authorization code using the following logic:

@@ -84,7 +84,7 @@ If any of the future auth tokens matches the account we're trying to login into auth.requestFirebaseSms#89464b50 flags:# phone_number:string phone_code_hash:string safety_net_token:flags.0?string ios_push_secret:flags.1?string = Bool;

The auth.sendCode method has parameters for enabling/disabling use of flash calls and missed calls, and allows passing an SMS token that will be included in the sent SMS. For example, the latter is required in newer versions of android, to use the android SMS receiver APIs.

-

The returned auth.SentCode object will contain multiple parameters:

+

The returned auth.sentCode object will contain multiple parameters:

diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index daae7d755e..37c5636f4b 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -540,7 +540,7 @@ Added support for thread IDs in message deep

Schema changes

New Methods
New Constructors
- - - - - diff --git a/data/web/corefork.telegram.org/method/channels.getMessages b/data/web/corefork.telegram.org/method/channels.getMessages index 4e0acc72d0..5fc7fcd4d3 100644 --- a/data/web/corefork.telegram.org/method/channels.getMessages +++ b/data/web/corefork.telegram.org/method/channels.getMessages @@ -116,11 +116,6 @@ - - - - - diff --git a/data/web/corefork.telegram.org/method/channels.toggleJoinRequest b/data/web/corefork.telegram.org/method/channels.toggleJoinRequest index 9a75a2e928..cfbb959c90 100644 --- a/data/web/corefork.telegram.org/method/channels.toggleJoinRequest +++ b/data/web/corefork.telegram.org/method/channels.toggleJoinRequest @@ -116,7 +116,7 @@ - +
channel/supergroup not available.
500CHAT_FROM_USERNAME_CHANGED 
400 CHAT_NOT_MODIFIED The pinned message wasn't modified.Invalid message ID provided.
500NEED_DOC_INVALID 
400 USER_BANNED_IN_CHANNEL You're banned from sending messages in supergroups/channels.
400 CHAT_PUBLIC_REQUIRED You can only enable join requests in public groups.
diff --git a/data/web/corefork.telegram.org/method/messages.getPeerDialogs b/data/web/corefork.telegram.org/method/messages.getPeerDialogs index 82926a7075..c26d5c4dd3 100644 --- a/data/web/corefork.telegram.org/method/messages.getPeerDialogs +++ b/data/web/corefork.telegram.org/method/messages.getPeerDialogs @@ -103,11 +103,6 @@ Invalid message ID provided. -500 -NEED_DOC_INVALID -  - - 400 PEER_ID_INVALID The provided peer id is invalid. diff --git a/data/web/corefork.telegram.org/method/users.getUsers b/data/web/corefork.telegram.org/method/users.getUsers index 44bfdaca0e..3a495b7284 100644 --- a/data/web/corefork.telegram.org/method/users.getUsers +++ b/data/web/corefork.telegram.org/method/users.getUsers @@ -107,11 +107,6 @@ Invalid message ID provided. -500 -NEED_DOC_INVALID -  - - 400 USER_BANNED_IN_CHANNEL You're banned from sending messages in supergroups/channels. diff --git a/data/web/corefork.telegram.org/methods.html b/data/web/corefork.telegram.org/methods.html index 9f5c3d0e4d..426339fea2 100644 --- a/data/web/corefork.telegram.org/methods.html +++ b/data/web/corefork.telegram.org/methods.html @@ -2785,7 +2785,7 @@ auth.importWebTokenAuthorization -  +Login by importing an authorization token