From c4084fc2c582feae1f88609191c6afe2323c5851 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Thu, 29 Sep 2022 13:59:53 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/config.html | 2 +- data/web/corefork.telegram.org/api/reactions.html | 4 ++-- data/web/corefork.telegram.org/method/messages.sendMultiMedia | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/data/web/corefork.telegram.org/api/config.html b/data/web/corefork.telegram.org/api/config.html index 34be536bf1..c8274b580f 100644 --- a/data/web/corefork.telegram.org/api/config.html +++ b/data/web/corefork.telegram.org/api/config.html @@ -302,7 +302,7 @@ While help.getConfig returns MTProto-specif

groupcall_video_participants_max

Maximum number of participants in a group call (livestreams allow ∞ participants) (integer)

reactions_uniq_max

-

Maximum number of unique reactions for any given message: for example, if there are 2000 👍 and 1000 custom emoji 😁 reactions and reactions_uniq_max = 2, you can't add a 👎 reaction, because that would raise the number of unique reaction-emojis to 3 > 2. (integer)

+

Maximum number of unique reactions for any given message: for example, if there are 2000 👍 and 1000 custom emoji 😁 reactions and reactions_uniq_max = 2, you can't add a 👎 reaction, because that would raise the number of unique reactions to 3 > 2. (integer)

reactions_in_chat_max

(integer)

reactions_user_max_default

diff --git a/data/web/corefork.telegram.org/api/reactions.html b/data/web/corefork.telegram.org/api/reactions.html index 59c606863d..81fbc795d6 100644 --- a/data/web/corefork.telegram.org/api/reactions.html +++ b/data/web/corefork.telegram.org/api/reactions.html @@ -73,8 +73,8 @@ messages.reportReaction#3f64c076 peer:InputPeer id:int reaction_peer:InputPeer = Bool;

Users can react to a message with one or more reactions using messages.sendReaction.
After sending the reaction, the chosen_order field of reactionCount will be set for the reaction. The integer value indicates when was the reaction added: the bigger the value, the newer the reaction, use this value to appropriately sort the messages.sendReaction:reaction vector when adding new reactions.
-Reactions should be sent in ascending order (new reactions at the end in the messages.sendReaction:reaction vector), and when adding more reactions to the same message, older reactions should be removed to keep the total number of sent/modified reactions within reactions_user_max_default/reactions_user_max_premium reactions.
-The reactions_uniq_max configuration field also indicates the maximum number of unique reactions that can be added to a message: for example, if there are 2000 👍 and 1000 custom emoji 😁 reactions and reactions_uniq_max = 2, you can't add a 👎 reaction, because that would raise the number of unique reaction-emojis to 3 > 2.

+Reactions should be sent in ascending order (new reactions at the end in the messages.sendReaction:reaction vector), and when adding more reactions to the same message, older reactions should be removed to keep the total number of sent reactions within reactions_user_max_default/reactions_user_max_premium reactions.
+The reactions_uniq_max configuration field also indicates the maximum number of unique reactions that can be added to a message: for example, if there are 2000 👍 and 1000 custom emoji 😁 reactions and reactions_uniq_max = 2, you can't add a 👎 reaction, because that would raise the number of unique reactions to 3 > 2.

The big flag can be optionally set to elicit a bigger reaction.
Send a reactionEmoji to react using a normal emoji, and a reactionCustomEmoji to react using a custom emoji.
Message authors will receive an updateMessageReactions update when a user reacts to their message.

diff --git a/data/web/corefork.telegram.org/method/messages.sendMultiMedia b/data/web/corefork.telegram.org/method/messages.sendMultiMedia index 96f3ac9de2..cd08360843 100644 --- a/data/web/corefork.telegram.org/method/messages.sendMultiMedia +++ b/data/web/corefork.telegram.org/method/messages.sendMultiMedia @@ -117,7 +117,7 @@ multi_media Vector<InputSingleMedia> -The medias to send +The medias to send: note that they must be separately uploaded using messages.uploadMedia first, using raw inputMediaUploaded* constructors is not supported. schedule_date