diff --git a/data/corefork.telegram.org/api/animated-emojis.html b/data/corefork.telegram.org/api/animated-emojis.html index 53b8095e69..40fffba270 100644 --- a/data/corefork.telegram.org/api/animated-emojis.html +++ b/data/corefork.telegram.org/api/animated-emojis.html @@ -50,7 +50,8 @@

On startup, clients should fetch the animated emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmoji to the stickerset field.
The returned stickerset will contain a set of animated stickers, one for each of the supported emojis.

Clients should substitute messages containing only one instance of one of the allowed emojis with the respective animated sticker.

-

Animated emojis should loop only once when first sent or received, or when clicked.

+

Animated emojis should loop only once when first sent or received, or when clicked.
+For supported emojis, clients on both sides of private chats with users are supposed to show a reaction animation when any of the two users clicks on the animated emoji: click here for more info ».

For special dice emojis like 🎲, 🎯, or 🏀, clients are supposed to behave differently both when sending and receiving such emojis: click here for more info ».

Emojis with sounds

Certained animated emojis should play sound when clicked, as specified by server-side configuration.

@@ -72,7 +73,44 @@ The returned stickerset will contain a set of animated stickers, one for each of "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g" }, } -

The file reference field should be base64-decoded before downloading the file

+

The file reference field should be base64-decoded before downloading the file.

+

Emoji reactions

+
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
+
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
+
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+

On startup, clients should fetch the animated reaction emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmojiAnimations to the stickerset field.
+The returned stickerset will contain a set of animated emoji reactions, one or more for each of the supported emojis.
+If a set of reactions for the ❤ emoji is returned, the same reactions should also be assigned to the 🧡, 💛, 💚, 💙, 💜, 🖤, 🤍 and 🤎 emojis.

+

Clients on both sides of private chats with users should overlay one of the appropriate reaction animations over the animated sticker when any of the two users clicks on a supported animated emoji.
+The reaction animation for each separate tap should be chosen randomly from all the available reactions for a given emoji, and multiple taps should be aggregated and sent to the other user as follows:

+

At each tap, clients should store the relative timestamp of the tap (starting from the first one @ 0) in a list.
+After 500 milliseconds have elapsed with no more taps, the list should be cleared and the stored taps should be sent using messages.setTyping, passing a sendMessageEmojiInteraction constructor with the following fields:

+ diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html index 57e319635c..d098186795 100644 --- a/data/corefork.telegram.org/api/files.html +++ b/data/corefork.telegram.org/api/files.html @@ -183,6 +183,9 @@ The data for the input parameter of the InputF inputStickerSetEmpty#ffb62b95 = InputStickerSet; inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet; inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet; +inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet; +inputStickerSetDice#e67f520e emoticon:string = InputStickerSet; +inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet; inputPeerSelf#7da07ec9 = InputPeer; inputPeerChat#35a95cb9 chat_id:long = InputPeer; diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html index acd366b5bc..04c6f5954f 100644 --- a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html +++ b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html @@ -4,10 +4,10 @@ sendMessageEmojiInteraction - + - + @@ -39,7 +39,7 @@

sendMessageEmojiInteraction

-

User has clicked on an animated emoji, triggering a reaction

+

User has clicked on an animated emoji triggering a reaction, click here for more info ».

+

SendMessageAction

+

Related pages

+

Animated Emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html index 34e30a227e..b3832c1439 100644 --- a/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html +++ b/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html @@ -4,10 +4,10 @@ sendMessageEmojiInteractionSeen - + - + @@ -39,7 +39,7 @@

sendMessageEmojiInteractionSeen

-

User is watching an animated emoji reaction triggered by another user

+

User is watching an animated emoji reaction triggered by another user, click here for more info ».

+

SendMessageAction

+

Related pages

+

Animated Emojis

+

Graphical telegram clients should transform emojis into their respective animated version.