From 2afd12cdd035efae787f874d4cc089a440d67e24 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 7 Feb 2024 22:21:43 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/colors.html | 1 - .../corefork.telegram.org/api/saved-messages.html | 14 ++++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/data/web/corefork.telegram.org/api/colors.html b/data/web/corefork.telegram.org/api/colors.html index d54ff7f1bb..57529a0fe5 100644 --- a/data/web/corefork.telegram.org/api/colors.html +++ b/data/web/corefork.telegram.org/api/colors.html @@ -82,7 +82,6 @@ If the hidden flag is set it should not be displayed as an option t

Use account.updateColor to update the color palette of the current account's message accents and/or profile page; note that the current account must be subscribed to Telegram Premium in order to call the method.
Use channels.updateColor to update the color palette of the channel's message/profile page accents.

Note that channels can use a palette only after reaching at least the boost level specified in the channel_min_level field of the help.peerColorOption constructor for the chosen palette: this is the only limitation for channel message accent palettes, while to change profile palettes, channels must also reach at least the boost level specified in the channel_profile_bg_icon_level_min config parameter.

-

To use emojis in message/profile channel palettes, channels must have reached at least the boost level specified channel_bg_icon_level_min config parameter/channel_profile_bg_icon_level_min config parameter, respectively.

The chosen message accent palette will be visible to other users in the channel.color and user.color fields.

The chosen user and channel profile palettes will be visible in the user.profile_color and channel.profile_color fields.

diff --git a/data/web/corefork.telegram.org/api/saved-messages.html b/data/web/corefork.telegram.org/api/saved-messages.html index 26b123d344..7c509614df 100644 --- a/data/web/corefork.telegram.org/api/saved-messages.html +++ b/data/web/corefork.telegram.org/api/saved-messages.html @@ -111,6 +111,20 @@ To add new dialogs to the saved dialog list, simply forward messages from any no

Saving messages from private chats with users with forward privacy enabled will add them to a saved dialog entry of a special anonymous user with id=2666000.

+

Clients may use the following pseudocode to manually populate the saved_peer_id of old layer < 170 messages stored in the local database.

+
// user_id is the ID of the current user.
+
+if (message.peer_id == user_id) {
+  if (message.fwd_from.saved_from_peer) {
+    message.saved_peer_id = message.fwd_from.saved_from_peer
+  } elseif (message.fwd_from.from_id) {
+    message.saved_peer_id = user_id;
+  } elseif (message.fwd_from.from_name) {
+    message.saved_peer_id = 2666000;
+  } else {
+    message.saved_peer_id = user_id;
+  }
+}

Sending (not forwarding from another dialog) new messages directly to ourselves will add them to a saved dialog entry with ourselves.

A set of methods can then be used to obtain this dialog list, pin/unpin dialogs inside of it, view and remove messages from saved dialogs: messages.getSavedDialogs, messages.getSavedHistory, messages.deleteSavedHistory, messages.getPinnedSavedDialogs, messages.toggleSavedDialogPin, messages.reorderPinnedSavedDialogs work just like their counterparts messages.getDialogs, messages.getHistory, messages.deleteHistory, messages.getPinnedDialogs, messages.toggleDialogPin, messages.reorderPinnedDialogs, with the sole difference that they affect the saved dialog list, instead of the main dialog list.

To search for messages within a saved dialog, use the usual messages.search, messages.getSearchCounters, messages.getSearchResultsCalendar, messages.getSearchResultsPositions methods with peer=inputPeerSelf and saved_peer_id=id of the saved dialog.