From d577b6c18e18b75ea27ac157347c93127e240917 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Fri, 21 Jun 2024 19:08:45 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/layers.html | 2 +- .../web/corefork.telegram.org/api/saved-messages.html | 11 ++++++----- data/web/corefork.telegram.org/methods.html | 2 +- 3 files changed, 8 insertions(+), 7 deletions(-) diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index 0d6aa69e26..4df5ea168a 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -629,7 +629,7 @@

Schema changes

New Methods
diff --git a/data/web/corefork.telegram.org/api/saved-messages.html b/data/web/corefork.telegram.org/api/saved-messages.html index 9a1578df87..ca2f02dfe8 100644 --- a/data/web/corefork.telegram.org/api/saved-messages.html +++ b/data/web/corefork.telegram.org/api/saved-messages.html @@ -46,6 +46,7 @@

The Saved Messages chat allows users to bookmark messages and media: it's a personal cloud storage for any messages or media you may want to send or forward there.

Internally, the Saved Messages chat is simply the private chat with ourselves (i.e. the chat with inputPeerSelf): the only difference between the Saved Messages chat and a chat with any other user, is that additional features are available to better organize messages and media sent to it.

+

Saved message dialogs

Schema:

message#94345242 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true invert_media:flags.27?true flags2:# offline:flags2.1?true id:int from_id:flags.8?Peer from_boosts_applied:flags.29?int peer_id:Peer saved_peer_id:flags.28?Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long via_business_bot_id:flags2.0?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int quick_reply_shortcut_id:flags.30?int effect:flags2.2?long factcheck:flags2.3?FactCheck = Message;
 messageFwdHeader#4e4df4bb flags:# imported:flags.7?true saved_out:flags.11?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int saved_from_id:flags.8?Peer saved_from_name:flags.9?string saved_date:flags.10?int psa_type:flags.6?string = MessageFwdHeader;
@@ -148,7 +149,7 @@ if (message.peer_id == user_id) {
 messages.getDefaultTagReactions#bdf93428 hash:long = messages.Reactions;
 
 messages.updateSavedReactionTag#60297dec flags:# reaction:Reaction title:flags.0?string = Bool;
-messages.getSavedReactionTags#761ddacf hash:long = messages.SavedReactionTags;
+messages.getSavedReactionTags#3637e05b flags:# peer:flags.0?InputPeer hash:long = messages.SavedReactionTags;

Tags are based on reactions »: adding a tag to a saved message is as easy as reacting to it » using messages.sendReaction.

Reactions are considered as tags only for saved messages, if the following conditions are met: