From de4c8bb631a91d417b072ebda91ebb37bf34bf68 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Fri, 14 Oct 2022 12:14:22 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/config.html | 2 +- data/web/corefork.telegram.org/api/links.html | 4 ++-- data/web/corefork.telegram.org/api/web-events.html | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/data/web/corefork.telegram.org/api/config.html b/data/web/corefork.telegram.org/api/config.html index 9381628026..005fb463c8 100644 --- a/data/web/corefork.telegram.org/api/config.html +++ b/data/web/corefork.telegram.org/api/config.html @@ -266,7 +266,7 @@ While help.getConfig returns MTProto-specif

emojies_send_dice_success

For animated dice emojis other than the basic 🎲, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 🎆 (object with emoji keys and object values, containing value and frame_start float values)

emojies_sounds

-

A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs, with emoji string keys)

+

A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs (inputDocument.id), with emoji string keys)

gif_search_branding

Specifies the name of the service providing GIF search through gif_search_username (string)

gif_search_emojies

diff --git a/data/web/corefork.telegram.org/api/links.html b/data/web/corefork.telegram.org/api/links.html index 1a5e818ad3..9740924472 100644 --- a/data/web/corefork.telegram.org/api/links.html +++ b/data/web/corefork.telegram.org/api/links.html @@ -107,7 +107,7 @@ -

Note that chat invite links have the same syntax, but <phone_number> is not a valid phone number.

+

Note that chat invite links have the same syntax, but <phone_number> won't be a valid phone number.

Chat invite links

Used to invite users to private groups and channels, see here for more info on how to generate such links ».

t.me syntax:

@@ -229,7 +229,7 @@ t.me/share/url?url=<url>&text=<text>

Video chat/Livestream links

Used to join video/voice chats in groups, and livestreams in channels.
Such links are generated using phone.exportGroupCallInvite.
-Note that voicechat links are deprecated, the API will always export videochat links even for voice chats, clients should support parsing the old link format only for backwards compatibility.

+Note that voicechat links are deprecated, the API will always export videochat links for video and voice chats in groups, clients should support parsing the old link format only for backwards compatibility.

t.me syntax:

t.me/<username>?videochat
 t.me/<username>?videochat=<invite_hash>
diff --git a/data/web/corefork.telegram.org/api/web-events.html b/data/web/corefork.telegram.org/api/web-events.html
index 7c2ce3f910..a6dffd6aa0 100644
--- a/data/web/corefork.telegram.org/api/web-events.html
+++ b/data/web/corefork.telegram.org/api/web-events.html
@@ -179,11 +179,11 @@ The GamingCommunication and bot web apps libraries by default will use '*'
 Credit card details will be handled only by the payment system, see the payment documentation for more info ».  

 
share_score

 
No event payload.

-
Will be called by games when the user explicitly clicks on the share score button to share the game, along with his score.

+
Will be called by games when the user explicitly clicks on the share score button to share the game, along with their score.

 Typically done by using messages.forwardMessages on the game message with the with_my_score flag.  

 
share_game

 
No event payload.

-
Will be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.

+
Will be called by games when the user explicitly clicks on the share game button to share the game, without sharing their score.

 Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's deep link.

 
game_over

 
No event payload.