From 6b0aa85955b29d4feedfc59604207c1c76bc6277 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 22 Nov 2023 21:53:25 +0000 Subject: [PATCH] Update content of files --- .../constructor/authorization.html | 2 ++ .../constructor/sponsoredWebPage.html | 24 ++----------------- .../constructor/updateNewAuthorization.html | 2 ++ .../updates.channelDifferenceTooLong.html | 4 ++-- .../account.changeAuthorizationSettings.html | 2 ++ .../account.updatePasswordSettings.html | 10 ++++---- .../method/messages.forwardMessages.html | 10 ++++---- .../method/stories.editStory.html | 2 ++ .../method/stories.sendStory.html | 4 ++-- .../type/SponsoredWebPage.html | 16 +++---------- .../type/updates.ChannelDifference.html | 2 +- 11 files changed, 28 insertions(+), 50 deletions(-) diff --git a/data/web/corefork.telegram.org/constructor/authorization.html b/data/web/corefork.telegram.org/constructor/authorization.html index b37fa11743..96b2ec98ec 100644 --- a/data/web/corefork.telegram.org/constructor/authorization.html +++ b/data/web/corefork.telegram.org/constructor/authorization.html @@ -166,6 +166,8 @@

Type

Authorization

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

Creating your Telegram Application

How to get your application identifier and create a new Telegram app.

diff --git a/data/web/corefork.telegram.org/constructor/sponsoredWebPage.html b/data/web/corefork.telegram.org/constructor/sponsoredWebPage.html index 4a09d1e401..c00747d41d 100644 --- a/data/web/corefork.telegram.org/constructor/sponsoredWebPage.html +++ b/data/web/corefork.telegram.org/constructor/sponsoredWebPage.html @@ -4,30 +4,10 @@ sponsoredWebPage - + - + diff --git a/data/web/corefork.telegram.org/constructor/updateNewAuthorization.html b/data/web/corefork.telegram.org/constructor/updateNewAuthorization.html index 730e095919..9e27c1a53f 100644 --- a/data/web/corefork.telegram.org/constructor/updateNewAuthorization.html +++ b/data/web/corefork.telegram.org/constructor/updateNewAuthorization.html @@ -101,6 +101,8 @@

Type

Update

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

Pagination in the API

How to fetch results from large lists of objects.

diff --git a/data/web/corefork.telegram.org/constructor/updates.channelDifferenceTooLong.html b/data/web/corefork.telegram.org/constructor/updates.channelDifferenceTooLong.html index 31696d31f7..c98a4c0db3 100644 --- a/data/web/corefork.telegram.org/constructor/updates.channelDifferenceTooLong.html +++ b/data/web/corefork.telegram.org/constructor/updates.channelDifferenceTooLong.html @@ -4,10 +4,10 @@ updates.channelDifferenceTooLong - + - + diff --git a/data/web/corefork.telegram.org/method/account.changeAuthorizationSettings.html b/data/web/corefork.telegram.org/method/account.changeAuthorizationSettings.html index dd46cc1a46..ef08cce035 100644 --- a/data/web/corefork.telegram.org/method/account.changeAuthorizationSettings.html +++ b/data/web/corefork.telegram.org/method/account.changeAuthorizationSettings.html @@ -116,6 +116,8 @@

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

authorization

Logged-in session

account.getAuthorizations

diff --git a/data/web/corefork.telegram.org/method/account.updatePasswordSettings.html b/data/web/corefork.telegram.org/method/account.updatePasswordSettings.html index 1d05c9c373..7afe283ddf 100644 --- a/data/web/corefork.telegram.org/method/account.updatePasswordSettings.html +++ b/data/web/corefork.telegram.org/method/account.updatePasswordSettings.html @@ -95,11 +95,6 @@ 400 -EMAIL_UNCONFIRMED_%d -The provided email isn't confirmed, %d is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email. - - -400 EMAIL_INVALID The specified email is invalid. @@ -110,6 +105,11 @@ 400 +EMAIL_UNCONFIRMED_%d +The provided email isn't confirmed, %d is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email. + + +400 NEW_SALT_INVALID The new salt is invalid. diff --git a/data/web/corefork.telegram.org/method/messages.forwardMessages.html b/data/web/corefork.telegram.org/method/messages.forwardMessages.html index 3743546528..570bf573ed 100644 --- a/data/web/corefork.telegram.org/method/messages.forwardMessages.html +++ b/data/web/corefork.telegram.org/method/messages.forwardMessages.html @@ -329,16 +329,16 @@ You can't send messages as the specified peer. -420 -SLOWMODE_WAIT_%d -Slowmode is enabled in this chat: wait %d seconds before sending another message to this chat. - - 400 SLOWMODE_MULTI_MSGS_DISABLED Slowmode is enabled, you cannot forward multiple messages to this group. +420 +SLOWMODE_WAIT_%d +Slowmode is enabled in this chat: wait %d seconds before sending another message to this chat. + + 406 TOPIC_CLOSED This topic was closed, you can't send messages to it anymore. diff --git a/data/web/corefork.telegram.org/method/stories.editStory.html b/data/web/corefork.telegram.org/method/stories.editStory.html index 6b48fb572c..fd63a8c013 100644 --- a/data/web/corefork.telegram.org/method/stories.editStory.html +++ b/data/web/corefork.telegram.org/method/stories.editStory.html @@ -145,6 +145,8 @@

Telegram users and channels can easily post and view stories through the API.

Styled text with message entities

How to create styled text with message entities

+

Client configuration

+

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

Privacy

Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.

diff --git a/data/web/corefork.telegram.org/method/stories.sendStory.html b/data/web/corefork.telegram.org/method/stories.sendStory.html index 683754fa70..9c693e9c54 100644 --- a/data/web/corefork.telegram.org/method/stories.sendStory.html +++ b/data/web/corefork.telegram.org/method/stories.sendStory.html @@ -200,10 +200,10 @@

Telegram users and channels can easily post and view stories through the API.

Styled text with message entities

How to create styled text with message entities

-

Privacy

-

Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.

Client configuration

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

+

Privacy

+

Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.

Telegram Premium

Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.

diff --git a/data/web/corefork.telegram.org/type/SponsoredWebPage.html b/data/web/corefork.telegram.org/type/SponsoredWebPage.html index b9ae46134c..dc2fbec10c 100644 --- a/data/web/corefork.telegram.org/type/SponsoredWebPage.html +++ b/data/web/corefork.telegram.org/type/SponsoredWebPage.html @@ -4,20 +4,10 @@ SponsoredWebPage - + - + @@ -77,7 +67,7 @@ sponsoredWebPage sponsoredWebPage -  +Represents a sponsored website. diff --git a/data/web/corefork.telegram.org/type/updates.ChannelDifference.html b/data/web/corefork.telegram.org/type/updates.ChannelDifference.html index 0edbd9bc39..4920b4fea6 100644 --- a/data/web/corefork.telegram.org/type/updates.ChannelDifference.html +++ b/data/web/corefork.telegram.org/type/updates.ChannelDifference.html @@ -77,7 +77,7 @@ updates.channelDifferenceTooLong -The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways (assuming the existence of a persistent database to locally store messages):

1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with messages.getHistory. It is easy to implement, but suddenly disappearing messages look awful to the user.
2. Save all messages loaded in the memory until application restart, but delete all messages from the database. Messages left in the memory must be lazily updated using calls to messages.getHistory.
It will look much smoother to the user, they will need to redownload messages only after client restart.
Unsynchronized messages left in memory shouldn't be saved to the database, results of messages.getHistory and messages.getMessages must be used to update the state of deleted and edited messages left in the memory.
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges.
Messages in the database will be excluded when paginating through or searching the local message history after application restart and will be available only through individual message queries.
Every message should still be checked using messages.getHistory.
It has more disadvantages over 2) than advantages.
4. Save all messages with saving all data about continuous message ranges.
Messages from the database may be used when paginating through or searching the local message history.
The messages should still be lazily checked using messages.getHistory, but they are still available offline.
It is the best way for gaps support, but it is pretty hard to implement correctly.

It should be also noted that some messages like live location messages shouldn't be deleted. +The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways (assuming the existence of a persistent database to locally store messages):

1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with messages.getHistory. It is easy to implement, but suddenly disappearing messages look awful to the user.
2. Save all messages loaded in the memory until application restart, but delete all messages from the database. Messages left in the memory must be lazily updated using calls to messages.getHistory.
It will look much smoother to the user, they will need to redownload messages only after client restart.
Unsynchronized messages left in memory shouldn't be saved to the database, results of messages.getHistory and messages.getMessages must be used to update the state of deleted and edited messages left in the memory.
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges.
Messages in the database will be excluded when paginating through or searching the local message history after application restart and will be available only through individual message queries.
Every message should still be checked using messages.getHistory.
It has more disadvantages over 2) than advantages.
4. Save all messages with saving all data about continuous message ranges.
Messages from the database may be used when paginating through or searching the local message history.
The messages should still be lazily checked using messages.getHistory, but they are still available offline.
It is the best way for gaps support, but it is pretty hard to implement correctly.

It should be also noted that some messages like live location messages shouldn't be deleted. updates.channelDifference