Update content of files

data/web/corefork.telegram.org/api/bots/inline.html

@@ -104,7 +104,7 @@ Just like its <a href="/bots/api#answerinlinequery">bot API counterpart</a>, the
 
 <a href='/method/messages.sendInlineBotResult'>messages.sendInlineBotResult</a>#d3fbdccb flags:<a href='/type/%23'>#</a> silent:flags.5?<a href='/constructor/true'>true</a> background:flags.6?<a href='/constructor/true'>true</a> clear_draft:flags.7?<a href='/constructor/true'>true</a> hide_via:flags.11?<a href='/constructor/true'>true</a> peer:<a href='/type/InputPeer'>InputPeer</a> reply_to_msg_id:flags.0?<a href='/type/int'>int</a> top_msg_id:flags.9?<a href='/type/int'>int</a> random_id:<a href='/type/long'>long</a> query_id:<a href='/type/long'>long</a> id:<a href='/type/string'>string</a> schedule_date:flags.10?<a href='/type/int'>int</a> send_as:flags.13?<a href='/type/InputPeer'>InputPeer</a> = <a href='/type/Updates'>Updates</a>;</code></pre>
 <p>The user client should display the <a href="/constructor/messages.botResults">messages.botResults</a>.<code>results</code> obtained <a href="#1-making-an-inline-query">during querying</a> in a list, making sure to handle eventual bot timeouts in the form of a <code>BOT_RESPONSE_TIMEOUT</code> RPC error, by simply not displaying anything.  </p>
-<p>If either the <a href="/constructor/messages.botResults">messages.botResults</a>.<code>switch_pm</code> or <a href="/constructor/messages.botResults">messages.botResults</a>.<code>switch_webview</code> flags are populated, a button should be displayed on top of the result list, that when clicked, instead of sending an inline result to the chat, switches the user to a private chat with the bot (<code>switch_pm</code>) or to a <a href="/api/bots/webapps#simple-web-apps">bot web app</a> (<code>switch_webview</code>),.</p>
+<p>If either the <a href="/constructor/messages.botResults">messages.botResults</a>.<code>switch_pm</code> or <a href="/constructor/messages.botResults">messages.botResults</a>.<code>switch_webview</code> flags are populated, a button should be displayed on top of the result list, that when clicked, instead of sending an inline result to the chat, switches the user to a private chat with the bot (<code>switch_pm</code>) or to a <a href="/api/bots/webapps#simple-web-apps">bot web app</a> (<code>switch_webview</code>).  </p>
 <p>If the user instead chooses a specific <code>BotInlineResult</code> from the normal <code>results</code> list, the <a href="/method/messages.sendInlineBotResult">messages.sendInlineBotResult</a> method should be invoked, passing:</p>
 <ul>
 <li>The <code>query_id</code> from <code>messages.botResults</code></li>

data/web/corefork.telegram.org/api/config.html

@@ -334,6 +334,7 @@ When fetching the admin list of a supergroup using <a href="/method/channels.get
 <h4><a class="anchor" href="#whitelisted-domains" id="whitelisted-domains" name="whitelisted-domains"><i class="anchor-icon"></i></a><code>whitelisted_domains</code></h4>
 <p>A list of Telegram domains that can always be opened without additional user confirmation, when clicking on in-app links where the URL is not fully displayed (i.e. <a href="/constructor/messageEntityTextUrl">messageEntityTextUrl</a> entities). (array of strings)</p>
 <p>Note that when opening <a href="/api/links#named-bot-web-app-links">named bot web app links</a> for the first time, confirmation should still be requested from the user, even if the domain of the containing deep link is whitelisted (i.e. <code>t.me/&lt;bot_username&gt;/&lt;short_name&gt;?startapp=&lt;start_parameter&gt;</code>, where <code>t.me</code> is whitelisted).  </p>
+<p>Confirmation should <strong>always</strong> be asked, even if we already opened the <a href="/api/links#named-bot-web-app-links">named bot web app</a> before, if the link is not visible (i.e. <a href="/constructor/messageEntityTextUrl">messageEntityTextUrl</a> text links, inline buttons etc.).  </p>
 <h4><a class="anchor" href="#round-video-encoding" id="round-video-encoding" name="round-video-encoding"><i class="anchor-icon"></i></a><code>round_video_encoding</code></h4>
 <p>Contains a set of recommended codec parameters for round videos.  (object, as described in the example)</p>
 <h4><a class="anchor" href="#chat-read-mark-size-threshold" id="chat-read-mark-size-threshold" name="chat-read-mark-size-threshold"><i class="anchor-icon"></i></a><code>chat_read_mark_size_threshold</code></h4>

data/web/corefork.telegram.org/api/wallpapers.html

@@ -153,7 +153,7 @@ Note that calling this method will also automatically save the wallpaper, if it'
 As mentioned earlier, <a href="#fill-wallpapers">fill wallpapers</a> can't be saved to the server using <a href="/method/account.installWallPaper">account.installWallPaper</a> or <a href="/method/account.saveWallPaper">account.saveWallPaper</a>: an <a href="/constructor/inputWallPaperNoFile">inputWallPaperNoFile</a> is available for fill wallpapers but can <strong>only</strong> be used when working with <a href="/api/themes">themes »</a> or when using <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a>.</li>
 </ul>
 <p>Wallpapers can also be installed in a specific chat, by using <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a>: this will emit a <a href="/constructor/messageActionSetChatWallPaper">messageActionSetChatWallPaper</a> service message, displaying the wallpaper in the UI along with an invitation for the other user to apply the same wallpaper.  </p>
-<p>If the other user decides to apply the same wallpaper to the chat, <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a> should be invoked passing the wallpaper <code>settings</code> received in the <a href="/constructor/messageActionSetChatWallPaper">messageActionSetChatWallPaper</a> service message, along with the <code>id</code> of the <a href="/constructor/messageActionSetChatWallPaper">messageActionSetChatWallPaper</a> service message, <strong>without</strong> the <code>wallpaper</code>: this way, the action will emit a different <a href="/constructor/messageActionSetSameChatWallPaper">messageActionSetSameChatWallPaper</a>, which should be displayed in the UI as a simple acknowledgment service message, without the full wallpaper and without an invitation for the other user to apply it (since both participants already just did that).  </p>
+<p>If the other user decides to apply the same wallpaper to the chat, <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a> should be invoked passing the wallpaper <code>settings</code> received in the <a href="/constructor/messageActionSetChatWallPaper">messageActionSetChatWallPaper</a> service message (or some different settings, if the user customized them before applying the wallpaper), along with the <code>id</code> of the <a href="/constructor/messageActionSetChatWallPaper">messageActionSetChatWallPaper</a> service message, <strong>without</strong> the <code>wallpaper</code>: this way, the action will emit a different <a href="/constructor/messageActionSetSameChatWallPaper">messageActionSetSameChatWallPaper</a>, which should be displayed in the UI as a simple acknowledgment service message, without the full wallpaper and without an invitation for the other user to apply it (since both participants already just did that).  </p>
 <p>Note that in order to pass <a href="#image-wallpapers">image</a> or <a href="#pattern-wallpapers">pattern</a> wallpapers to <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a>, the <code>for_chat</code> flag must be set when <a href="#uploading-wallpapers">uploading them with account.uploadWallPaper</a>.  </p>
 <p>Also note that unlike <a href="/method/account.installWallPaper">account.installWallPaper</a> or <a href="/method/account.saveWallPaper">account.saveWallPaper</a>, <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a> accepts <a href="#fill-wallpapers">fill wallpapers</a> as well.</p></div>
   

data/web/corefork.telegram.org/constructor/messageEntityTextUrl.html

@@ -42,7 +42,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/messageEntityTextUrl" >messageEntityTextUrl</a></li></ul></div>
   <h1 id="dev_page_title">messageEntityTextUrl</h1>
   
-  <div id="dev_page_content"><p>Message entity representing a <a href="https://google.com">text url</a>: for in-text urls like <a href="https://google.com">https://google.com</a> use <a href="/constructor/messageEntityUrl">messageEntityUrl</a>.  </p>
+  <div id="dev_page_content"><p>Message entity representing a <a href="https://google.com">text url</a>: for in-text urls like <a href="https://google.com">https://google.com</a> use <a href="/constructor/messageEntityUrl">messageEntityUrl</a>.</p>
 <p>Note that an additional confirmation popup with the full URL must be displayed to the user before opening this link, unless the domain is one of the whitelisted domains specified in the <a href="/api/config#whitelisted-domains"><code>whitelisted_domains</code> client configuration parameter »</a>.</p>
 <p><div class="clearfix">
   <ul class="dev_layer_select slightly-pull-right nav nav-pills">
@@ -90,7 +90,9 @@
 <h4><a class="anchor" href="#styled-text-with-message-entities" id="styled-text-with-message-entities" name="styled-text-with-message-entities"><i class="anchor-icon"></i></a><a href="/api/entities">Styled text with message entities</a></h4>
 <p>How to create styled text with message entities</p>
 <h4><a class="anchor" href="#messageentityurl" id="messageentityurl" name="messageentityurl"><i class="anchor-icon"></i></a><a href="/constructor/messageEntityUrl">messageEntityUrl</a></h4>
-<p>Message entity representing an in-text url: <a href="https://google.com">https://google.com</a>; for <a href="https://google.com">text urls</a>, use <a href="/constructor/messageEntityTextUrl">messageEntityTextUrl</a>.</p></div>
+<p>Message entity representing an in-text url: <a href="https://google.com">https://google.com</a>; for <a href="https://google.com">text urls</a>, use <a href="/constructor/messageEntityTextUrl">messageEntityTextUrl</a>.</p>
+<h4><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a><a href="/api/config">Client configuration</a></h4>
+<p>The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.</p></div>
   
 </div>
           

data/web/corefork.telegram.org/constructor/messageEntityUrl.html

@@ -84,7 +84,8 @@
 <h4><a class="anchor" href="#styled-text-with-message-entities" id="styled-text-with-message-entities" name="styled-text-with-message-entities"><i class="anchor-icon"></i></a><a href="/api/entities">Styled text with message entities</a></h4>
 <p>How to create styled text with message entities</p>
 <h4><a class="anchor" href="#messageentitytexturl" id="messageentitytexturl" name="messageentitytexturl"><i class="anchor-icon"></i></a><a href="/constructor/messageEntityTextUrl">messageEntityTextUrl</a></h4>
-<p>Message entity representing a <a href="https://google.com">text url</a>: for in-text urls like <a href="https://google.com">https://google.com</a> use <a href="/constructor/messageEntityUrl">messageEntityUrl</a>.</p></div>
+<p>Message entity representing a <a href="https://google.com">text url</a>: for in-text urls like <a href="https://google.com">https://google.com</a> use <a href="/constructor/messageEntityUrl">messageEntityUrl</a>.</p>
+<p>Note that an additional confirmation popup with the full URL must be displayed to the user before opening this link, unless the domain is one of the whitelisted domains specified in the <a href="/api/config#whitelisted-domains"><code>whitelisted_domains</code> client configuration parameter »</a>.</p></div>
   
 </div>
           

data/web/corefork.telegram.org/type/MessageEntity.html

@@ -127,7 +127,7 @@
 </tr>
 <tr>
 <td><a href="/constructor/messageEntityTextUrl">messageEntityTextUrl</a></td>
-<td>Message entity representing a <a href="https://google.com">text url</a>: for in-text urls like <a href="https://google.com">https://google.com</a> use <a href="/constructor/messageEntityUrl">messageEntityUrl</a>.</td>
+<td>Message entity representing a <a href="https://google.com">text url</a>: for in-text urls like <a href="https://google.com">https://google.com</a> use <a href="/constructor/messageEntityUrl">messageEntityUrl</a>.<br><br>Note that an additional confirmation popup with the full URL must be displayed to the user before opening this link, unless the domain is one of the whitelisted domains specified in the <a href="/api/config#whitelisted-domains"><code>whitelisted_domains</code> client configuration parameter »</a>.</td>
 </tr>
 <tr>
 <td><a href="/constructor/messageEntityMentionName">messageEntityMentionName</a></td>