From fe307e635feca4bb7f3058755f9a7cb326cd407a Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Sat, 16 Oct 2021 13:14:08 +0000
Subject: [PATCH] Update content of files

---
 .../api/animated-emojis.html                  |  4 +-
 data/corefork.telegram.org/api/files.html     | 37 +++++++++++++------
 data/corefork.telegram.org/api/layers.html    |  2 +-
 .../inputPhotoLegacyFileLocation.html         |  6 +--
 4 files changed, 32 insertions(+), 17 deletions(-)

diff --git a/data/corefork.telegram.org/api/animated-emojis.html b/data/corefork.telegram.org/api/animated-emojis.html
index 40fffba270..1e2bc586a5 100644
--- a/data/corefork.telegram.org/api/animated-emojis.html
+++ b/data/corefork.telegram.org/api/animated-emojis.html
@@ -97,11 +97,11 @@ If a set of reactions for the <img class="emoji" src="//telegram.org/img/emoji/4
 <p>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.<br>
 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:  </p>
 <p>At each tap, clients should store the relative timestamp of the tap (starting from the first one @ <code>0</code>) in a list.<br>
-After 500 milliseconds have elapsed with no more taps, the list should be cleared and the stored taps should be sent using <a href="/method/messages.setTyping">messages.setTyping</a>, passing a <a href="/constructor/sendMessageEmojiInteraction">sendMessageEmojiInteraction</a> constructor with the following fields:  </p>
+After 500 milliseconds have elapsed with no more taps, the list should be cleared and stored taps should be sent using <a href="/method/messages.setTyping">messages.setTyping</a>, passing a <a href="/constructor/sendMessageEmojiInteraction">sendMessageEmojiInteraction</a> constructor with the following fields:  </p>
 <ul>
 <li><code>emoticon</code> - The emoji we're reacting to</li>
 <li><code>msg_id</code> - Message ID of the animated emoji that was clicked</li>
-<li>A JSON object with interaction info, containing the following keys:<ul>
+<li><code>interaction</code> - A JSON object with interaction info, containing the following keys:<ul>
 <li><code>v</code> - An integer indicating the object version, currently <code>1</code></li>
 <li><code>a</code> - An array of JSON objects, each containing the following keys:<ul>
 <li><code>t</code> - float, relative timestamp of the tap in seconds, the first one being <code>0.0</code>.</li>
diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html
index d098186795..263290e315 100644
--- a/data/corefork.telegram.org/api/files.html
+++ b/data/corefork.telegram.org/api/files.html
@@ -179,6 +179,7 @@ The data for the input parameter of the <a href="/type/InputFileLocation">InputF
 <a href='/constructor/inputPhotoLegacyFileLocation'>inputPhotoLegacyFileLocation</a>#d83466f3 id:<a href='/type/long'>long</a> access_hash:<a href='/type/long'>long</a> file_reference:<a href='/type/bytes'>bytes</a> volume_id:<a href='/type/long'>long</a> local_id:<a href='/type/int'>int</a> secret:<a href='/type/long'>long</a> = <a href='/type/InputFileLocation'>InputFileLocation</a>;
 <a href='/constructor/inputPeerPhotoFileLocation'>inputPeerPhotoFileLocation</a>#37257e99 flags:<a href='/type/%23'>#</a> big:flags.0?<a href='/constructor/true'>true</a> peer:<a href='/type/InputPeer'>InputPeer</a> photo_id:<a href='/type/long'>long</a> = <a href='/type/InputFileLocation'>InputFileLocation</a>;
 <a href='/constructor/inputStickerSetThumb'>inputStickerSetThumb</a>#9d84f3db stickerset:<a href='/type/InputStickerSet'>InputStickerSet</a> thumb_version:<a href='/type/int'>int</a> = <a href='/type/InputFileLocation'>InputFileLocation</a>;
+<a href='/constructor/inputGroupCallStream'>inputGroupCallStream</a>#598a92a flags:<a href='/type/%23'>#</a> call:<a href='/type/InputGroupCall'>InputGroupCall</a> time_ms:<a href='/type/long'>long</a> scale:<a href='/type/int'>int</a> video_channel:flags.0?<a href='/type/int'>int</a> video_quality:flags.0?<a href='/type/int'>int</a> = <a href='/type/InputFileLocation'>InputFileLocation</a>;
 
 <a href='/constructor/inputStickerSetEmpty'>inputStickerSetEmpty</a>#ffb62b95 = <a href='/type/InputStickerSet'>InputStickerSet</a>;
 <a href='/constructor/inputStickerSetID'>inputStickerSetID</a>#9de7a269 id:<a href='/type/long'>long</a> access_hash:<a href='/type/long'>long</a> = <a href='/type/InputStickerSet'>InputStickerSet</a>;
@@ -196,7 +197,10 @@ The data for the input parameter of the <a href="/type/InputFileLocation">InputF
 <a href='/constructor/document'>document</a>#1e87342b flags:<a href='/type/%23'>#</a> id:<a href='/type/long'>long</a> access_hash:<a href='/type/long'>long</a> file_reference:<a href='/type/bytes'>bytes</a> date:<a href='/type/int'>int</a> mime_type:<a href='/type/string'>string</a> size:<a href='/type/int'>int</a> thumbs:flags.0?<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/PhotoSize'>PhotoSize</a>&gt; video_thumbs:flags.1?<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/VideoSize'>VideoSize</a>&gt; dc_id:<a href='/type/int'>int</a> attributes:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/DocumentAttribute'>DocumentAttribute</a>&gt; = <a href='/type/Document'>Document</a>;
 
 <a href='/constructor/photoSize'>photoSize</a>#75c78e60 type:<a href='/type/string'>string</a> w:<a href='/type/int'>int</a> h:<a href='/type/int'>int</a> size:<a href='/type/int'>int</a> = <a href='/type/PhotoSize'>PhotoSize</a>;
-<a href='/constructor/photoCachedSize'>photoCachedSize</a>#21e1ad6 type:<a href='/type/string'>string</a> w:<a href='/type/int'>int</a> h:<a href='/type/int'>int</a> bytes:<a href='/type/bytes'>bytes</a> = <a href='/type/PhotoSize'>PhotoSize</a>;</code></pre>
+<a href='/constructor/photoCachedSize'>photoCachedSize</a>#21e1ad6 type:<a href='/type/string'>string</a> w:<a href='/type/int'>int</a> h:<a href='/type/int'>int</a> bytes:<a href='/type/bytes'>bytes</a> = <a href='/type/PhotoSize'>PhotoSize</a>;
+
+<a href='/constructor/chatPhoto'>chatPhoto</a>#1c6e1c11 flags:<a href='/type/%23'>#</a> has_video:flags.0?<a href='/constructor/true'>true</a> photo_id:<a href='/type/long'>long</a> stripped_thumb:flags.1?<a href='/type/bytes'>bytes</a> dc_id:<a href='/type/int'>int</a> = <a href='/type/ChatPhoto'>ChatPhoto</a>;
+<a href='/constructor/userProfilePhoto'>userProfilePhoto</a>#82d1f706 flags:<a href='/type/%23'>#</a> has_video:flags.0?<a href='/constructor/true'>true</a> photo_id:<a href='/type/long'>long</a> stripped_thumb:flags.1?<a href='/type/bytes'>bytes</a> dc_id:<a href='/type/int'>int</a> = <a href='/type/UserProfilePhoto'>UserProfilePhoto</a>;</code></pre>
 <ul>
 <li>
 <p>For photos, <a href="/constructor/inputPhotoFileLocation">inputPhotoFileLocation</a> is used:</p>
@@ -206,10 +210,11 @@ The data for the input parameter of the <a href="/type/InputFileLocation">InputF
 </ul>
 </li>
 <li>
-<p>For profile pictures of users, channels, supergroups and groups, since in most occasions they are encountered as simple <a href="/constructor/fileLocationToBeDeprecated">fileLocationToBeDeprecated</a> constructors without an associated <a href="/constructor/photo">photo</a>, <a href="/constructor/inputPeerPhotoFileLocation">inputPeerPhotoFileLocation</a> has to be used:</p>
+<p>For profile pictures of users, channels, supergroups and groups, <a href="/constructor/inputPeerPhotoFileLocation">inputPeerPhotoFileLocation</a> has to be used:</p>
 <ul>
 <li><code>peer</code> is the identifier of the peer whose photo we want to download</li>
-<li><code>volume_id</code> and <code>local_id</code> are extracted from the <a href="/constructor/fileLocationToBeDeprecated">fileLocationToBeDeprecated</a> of the desired quality (the logic for selecting the quality of profile pictures will be changed soon)</li>
+<li><code>big</code> is used to choose whether to download the full-resolution picture, or just the thumbnail</li>
+<li><code>photo_id</code> is extracted from the <a href="/constructor/chatPhoto">chatPhoto</a> or <a href="/constructor/userProfilePhoto">userProfilePhoto</a> of the desired profile photo</li>
 </ul>
 </li>
 <li>
@@ -220,19 +225,29 @@ The data for the input parameter of the <a href="/type/InputFileLocation">InputF
 </ul>
 </li>
 <li>
-<p>For encrypted secret chat and telegram passport documents, respectively <a href="/constructor/inputEncryptedFileLocation">inputEncryptedFileLocation</a> and <a href="/constructor/inputSecureFileLocation">inputSecureFileLocation</a> have to be used, with parameters extracted from <a href="/constructor/encryptedFile">encryptedFile</a> and <a href="/constructor/secureFile">secureFile</a> (<a href="/passport">passport docs</a>).</p>
-</li>
-<li>
-<p>For previews of sticker sets, <a href="/constructor/inputStickerSetThumb">inputStickerSetThumb</a> is used (note: to download stickers and previews of stickers use the document method described above):</p>
+<p>For previews of sticker sets, <a href="/constructor/inputStickerSetThumb">inputStickerSetThumb</a> is used (note: to download stickers and previews of stickers use the document method described above for documents):</p>
 <ul>
-<li><code>stickerset</code> is set to the <a href="/type/InputStickerSet">InputStickerSet</a> constructor generated from the <a href="/type/StickerSet">StickerSet</a></li>
-<li><code>volume_id</code> and <code>local_id</code> are extracted from the <a href="/constructor/fileLocationToBeDeprecated">fileLocationToBeDeprecated</a> from the <code>thumb</code> <a href="/type/PhotoSize">PhotoSize</a> of the <a href="/type/StickerSet">StickerSet</a> (the logic for downloading stickerset previews will be changed soon)</li>
+<li><code>stickerset</code> is set to the <a href="/type/InputStickerSet">InputStickerSet</a> constructor generated from <a href="/constructor/stickerSet">stickerSet</a></li>
+<li><code>thumb_version</code> is copied from the same field in <a href="/constructor/stickerSet">stickerSet</a></li>
 </ul>
 </li>
 <li>
-<p>For old <strong>deprecated</strong> photos, if the client has cached some old fileLocations with the <strong>deprecated</strong> <code>secret</code> identifier, <a href="/constructor/inputPhotoLegacyFileLocation">inputFileLocation</a> is used (this is mainly used for backwards compatiblity with bot API file IDs, all user clients must use the modern <a href="/constructor/inputPhotoFileLocation">inputPhotoFileLocation</a> file IDs): </p>
+<p>For encrypted secret chat and telegram passport documents, respectively <a href="/constructor/inputEncryptedFileLocation">inputEncryptedFileLocation</a> and <a href="/constructor/inputSecureFileLocation">inputSecureFileLocation</a> have to be used, with parameters extracted from <a href="/constructor/encryptedFile">encryptedFile</a> and <a href="/constructor/secureFile">secureFile</a> (<a href="/passport">passport docs</a>).</p>
+</li>
+<li>
+<p>For livestream chunks, <a href="/constructor/inputGroupCallStream">inputGroupCallStream</a> is used:</p>
 <ul>
-<li>All fields are taken from the previously cached fileLocation except for <code>id</code>, <code>file_reference</code> and <code>access_hash</code> taken from the <a href="/constructor/photo">photo</a> constructor</li>
+<li><code>call</code> contains the related group call ID+access hash, taken from the <a href="/constructor/groupCall">groupCall</a> constructor.</li>
+<li><code>time_ms</code> specifies the timestamp to fetch</li>
+<li><code>scale</code> specifies the duration of the video segment to fetch in milliseconds, by bitshifting <code>1000</code> to the right scale times: <code>duration_ms := 1000 &gt;&gt; scale</code></li>
+<li><code>video_channel</code> specifies the video channel to fetch</li>
+<li><code>video_quality</code> specifies the selected video quality (0 = lowest, 1 = medium, 2 = best)</li>
+</ul>
+</li>
+<li>
+<p>For old <strong>deprecated</strong> photos, if the client has cached some old fileLocations with the <strong>deprecated</strong> <code>secret</code> identifier, <a href="/constructor/inputFileLocation">inputFileLocation</a> or <a href="/constructor/inputPhotoLegacyFileLocation">inputPhotoLegacyFileLocation</a> is used (this is mainly used for backwards compatiblity with bot API file IDs, all user clients must use the modern <a href="/constructor/inputPhotoFileLocation">inputPhotoFileLocation</a> file IDs): </p>
+<ul>
+<li>All fields are taken from the previously cached fileLocation except for <code>file_reference</code>, <code>access_hash</code> and <code>id</code> (the last two only if present, in which case <a href="/constructor/inputPhotoLegacyFileLocation">inputPhotoLegacyFileLocation</a> is used instead of <a href="/constructor/inputFileLocation">inputFileLocation</a>) taken from the <a href="/constructor/photo">photo</a> constructor.</li>
 </ul>
 </li>
 </ul>
diff --git a/data/corefork.telegram.org/api/layers.html b/data/corefork.telegram.org/api/layers.html
index 93599a9f9c..cee556bc2d 100644
--- a/data/corefork.telegram.org/api/layers.html
+++ b/data/corefork.telegram.org/api/layers.html
@@ -1649,7 +1649,7 @@ Notice that all <code>PINNED_*</code> <a href="https://core.telegram.org/api/pus
 </ul>
 <h5><a class="anchor" href="#new-constructors" id="new-constructors" name="new-constructors"><i class="anchor-icon"></i></a>New Constructors</h5>
 <ul>
-<li>Added <a href="/constructor/inputPhotoLegacyFileLocation">inputPhotoLegacyFileLocation</a> - Legacy photo file location</li>
+<li>Added <a href="/constructor/inputPhotoLegacyFileLocation">inputPhotoLegacyFileLocation</a> - DEPRECATED legacy photo file location</li>
 <li>Added <a href="/constructor/updateGeoLiveViewed">updateGeoLiveViewed</a> - Live geoposition message was viewed</li>
 <li>Added <a href="/constructor/updateLoginToken">updateLoginToken</a> - A login token (for login via QR code) was accepted.</li>
 <li>Added <a href="/constructor/auth.loginToken">auth.loginToken</a> - Login token (for <a href="/api/qr-login">QR code login</a>)</li>
diff --git a/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html b/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html
index 11c6372cd9..58389a960f 100644
--- a/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html
+++ b/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>inputPhotoLegacyFileLocation</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Legacy photo file location">
+    <meta property="description" content="DEPRECATED legacy photo file location">
     <meta property="og:title" content="inputPhotoLegacyFileLocation">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Legacy photo file location">
+    <meta property="og:description" content="DEPRECATED legacy photo file location">
     <link rel="shortcut icon" href="/favicon.ico?4" type="image/x-icon" />
 
     <link href="/css/bootstrap.min.css?3" rel="stylesheet">
@@ -39,7 +39,7 @@
   <div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a  href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/schema" >TL-schema</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/constructor/inputPhotoLegacyFileLocation" >inputPhotoLegacyFileLocation</a></li></ul></div>
   <h1 id="dev_page_title">inputPhotoLegacyFileLocation</h1>
   
-  <div id="dev_page_content"><p>Legacy photo file location</p>
+  <div id="dev_page_content"><p>DEPRECATED legacy photo file location</p>
 <p><div class="clearfix">
   <ul class="dev_layer_select slightly-pull-right nav nav-pills">
     <li class="dropdown">