From 5347278dce0c6d19c1af2759a1f726d20b431412 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 24 Jul 2024 15:35:11 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/folders.html | 2 +- data/web/corefork.telegram.org/api/forum.html | 2 +- data/web/corefork.telegram.org/api/peers.html | 2 +- data/web/corefork.telegram.org/constructor/phoneCall.html | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/data/web/corefork.telegram.org/api/folders.html b/data/web/corefork.telegram.org/api/folders.html index 9a1ce6ed43..59db28935c 100644 --- a/data/web/corefork.telegram.org/api/folders.html +++ b/data/web/corefork.telegram.org/api/folders.html @@ -102,7 +102,7 @@ Clients can also receive updateDialog

If the new value of the toggle is different, the method will emit an updateDialogFilters to all other currently-logged in sessions, which should trigger a call to messages.toggleDialogFilterTags to load the new value of the toggle, in messages.dialogFilters.tags_enabled.

If folder tags are enabled, clients should add folder tags (one for each folder the dialog entry is a part of, except for the "All chats" folder represented by dialogFilterDefault and tags with color=-1) to all dialog entries, under the preview of the latest message.

These folder tags should contain the name of the folder, and should be colored with the color specified in the dialog folder entry.
-The color is an integer ranging from -1 to to 6; if -1, the tag must not be shown in the dialog list; use red, orange, violet, green, cyan, blue, pink for indexes 0 to 6 (i.e. the same colors used for randomized fallback message accent colors).

+The color is an integer ranging from -1 to 6; if -1, the tag must not be shown in the dialog list; use red, orange, violet, green, cyan, blue, pink for indexes 0 to 6 (i.e. the same colors used for randomized fallback message accent colors).

The tag color may only be changed if the user has a Premium subscription and tags are enabled.

Shared folders

inputChatlistDialogFilter#f3e0da33 filter_id:int = InputChatlist;
diff --git a/data/web/corefork.telegram.org/api/forum.html b/data/web/corefork.telegram.org/api/forum.html
index 42a150759b..bb94a34942 100644
--- a/data/web/corefork.telegram.org/api/forum.html
+++ b/data/web/corefork.telegram.org/api/forum.html
@@ -95,7 +95,7 @@ To fetch information about one or more topics by their ID, use message thread of the messageActionTopicCreate service message that created that topic.

 This means that topics should be treated similarly to message threads by the client.

 To send messages to these topics, pass the topic ID to the reply_to_msg_id parameter of inputReplyToMessage, passed to reply_to when invoking messages.sendMessage, messages.sendMedia et cetera.  

-
To reply to messages within a topic, pass the ID of the message to reply to to inputReplyToMessage.reply_to_msg_id, and, unless we're replying to a message in the "General" topic, pass the topic ID to inputReplyToMessage.top_msg_id.

+
To reply to messages within a topic, pass the ID of the message to reply to inputReplyToMessage.reply_to_msg_id, and, unless we're replying to a message in the "General" topic, pass the topic ID to inputReplyToMessage.top_msg_id.

 Note that when replying to messages in a topic, the inputReplyToMessage.top_msg_id field must contain the topic ID if and only if we're replying to messages in forum topics different from the "General" topic (i.e. reply_to_msg_id is set and reply_to_msg_id != topicID and topicID != 1): this way, if the replied-to message is deleted before the method finishes execution, the value in this field will be used to send the message to the correct topic, instead of the "General" topic.

 Also note that since message threads can't have nested message threads, topics (except for the "General" topic) also can't have message threads (so replies to messages within topics won't generate further message threads).  

 
Topics have a name (title) and an icon: the icon can be a custom emoji specified by the icon_emoji_id, or a default chat icon if icon_emoji_id is not set, filled with the color specified in icon_color.

diff --git a/data/web/corefork.telegram.org/api/peers.html b/data/web/corefork.telegram.org/api/peers.html
index 011f8ea23c..f986133ba0 100644
--- a/data/web/corefork.telegram.org/api/peers.html
+++ b/data/web/corefork.telegram.org/api/peers.html
@@ -119,7 +119,7 @@ Info about these IDs may be fetched with the zero access hash even by users.  account.toggleUsername, account.reorderUsernames - For ourselves
 
  • bots.toggleUsername, bots.reorderUsernames - For the bot whose username we updated
    • 
 
-
    Info should only be manually refreshed with a call to users.getUsers if the new username order/active username cannot be applied locally (i.e. the methods successfully set as active some username that isn't associated to the user in our local cache, and so on), otherwise the username and usernames fields of the peer info database should be updated locally, using the info that was passed to to the toggle/reorder methods by the user.  
    
+
    Info should only be manually refreshed with a call to users.getUsers if the new username order/active username cannot be applied locally (i.e. the method call successfully set as active some username that isn't associated to the user in our local cache, and so on), otherwise the username and usernames fields of the peer info database should be updated locally, using the info that was passed to the toggle/reorder methods by the user.  
    
 
 
 
    Do not refresh peer information in any other case, to avoid overloading the server by continuously requesting changes for the same unchanged information.  
    
diff --git a/data/web/corefork.telegram.org/constructor/phoneCall.html b/data/web/corefork.telegram.org/constructor/phoneCall.html
index 9051c8b16d..92b26d77d1 100644
--- a/data/web/corefork.telegram.org/constructor/phoneCall.html
+++ b/data/web/corefork.telegram.org/constructor/phoneCall.html
@@ -124,7 +124,7 @@
 
 connections
 Vector<PhoneConnection>
-List of endpoints the user can connect to to exchange call data
+List of endpoints the user can connect to exchange call data
 
 
 start_date