From 48f9594ceb7b88726073e547136e71bb096c971d Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Mon, 5 Aug 2024 08:59:01 +0000
Subject: [PATCH] Update content of files

---
 .../web/corefork.telegram.org/api/layers.html |  1 +
 data/web/corefork.telegram.org/api/peers.html |  2 +-
 .../constructor/channel.html                  | 31 +++++++++++++++++--
 3 files changed, 31 insertions(+), 3 deletions(-)

diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index 916519c78b..b12dca942b 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -51,6 +51,7 @@
 <ul>
 <li><a href="/api/bots/ids">Bot API dialog IDs »</a></li>
 <li><a href="/api/peers">Peer database »</a></li>
+<li>Added documentation for <a href="/api/min">min merging logic</a> and <a href="/api/peers">peer cache invalidation logic</a>, including in the constructor pages for <a href="/constructor/user">user</a>s and <a href="/constructor/channel">channels/supergroups</a>.</li>
 <li><a href="/api/gifs">Working with GIFs »</a></li>
 <li><a href="/api/emoji-categories">Emoji categories »</a></li>
 <li><a href="/api/profile">Profile page »</a></li>
diff --git a/data/web/corefork.telegram.org/api/peers.html b/data/web/corefork.telegram.org/api/peers.html
index bc03c77557..41858792fe 100644
--- a/data/web/corefork.telegram.org/api/peers.html
+++ b/data/web/corefork.telegram.org/api/peers.html
@@ -165,7 +165,7 @@ Note that <a href="/constructor/chat">chat</a>s (<a href="/api/channel">basic gr
 <a href="/constructor/user">user</a>s and <a href="/constructor/channel">channel</a>s (<a href="/api/channel">supergroups and channels »</a>) have an access hash, and it can come in various flavors:</p>
 <ul>
 <li>Full access hash: can be used everywhere in the API.</li>
-<li>Min access hash: received from <a href="/api/min">min constructors »</a>, can only be used to fetch the profile pictures using <a href="/constructor/inputPeerPhotoFileLocation"><code>inputPeerPhotoFileLocation</code> »</a>.  </li>
+<li>Min access hash: received from <a href="/api/min">min constructors »</a>, can only be used to fetch profile pictures using <a href="/constructor/inputPeerPhotoFileLocation"><code>inputPeerPhotoFileLocation</code> »</a>.  </li>
 <li>From-message access hash: not a real access hash, constructed as specified <a href="/api/min">here »</a>, must be used when only a min access hash is available locally, but a full access hash is required. </li>
 <li>Zero access hash: equal to <code>0</code>, must be used by bots when only a min access hash (or no access hash) is available locally, but a full access hash is required. </li>
 </ul>
diff --git a/data/web/corefork.telegram.org/constructor/channel.html b/data/web/corefork.telegram.org/constructor/channel.html
index a5a02fcfb3..9d169aec50 100644
--- a/data/web/corefork.telegram.org/constructor/channel.html
+++ b/data/web/corefork.telegram.org/constructor/channel.html
@@ -43,6 +43,33 @@
   <h1 id="dev_page_title">channel</h1>
   
   <div id="dev_page_content"><p>Channel/supergroup info</p>
+<p>When updating the <a href="/api/peers">local peer database</a>, all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).  </p>
+<p>The only exception to the above rule is when the <code>min</code> flag is set, in which case <strong>only</strong> the following fields must be applied over any locally stored version: </p>
+<ul>
+<li><code>title</code></li>
+<li><code>megagroup</code></li>
+<li><code>color</code></li>
+<li><code>photo</code> </li>
+<li><code>username</code></li>
+<li><code>usernames</code></li>
+<li><code>has_geo</code></li>
+<li><code>noforwards</code></li>
+<li><code>emoji_status</code></li>
+<li><code>has_link</code></li>
+<li><code>is_slow_mode_enabled</code></li>
+<li><code>scam</code></li>
+<li><code>fake</code></li>
+<li><code>gigagroup</code></li>
+<li><code>forum</code></li>
+<li><code>level</code></li>
+<li><code>restricted</code></li>
+<li><code>restricted_reason</code></li>
+<li><code>join_to_send</code></li>
+<li><code>join_request</code></li>
+<li><code>is_verified</code></li>
+<li><code>default_banned_rights</code></li>
+</ul>
+<p>See <a href="https://github.com/tdlib/td/blob/a24af0992245f838f2b4b418a0a2d5fa9caa27b5/td/telegram/ChatManager.cpp#L8329">here »</a> for an implementation of the logic to use when updating the <a href="/api/peers">local user peer database</a>.</p>
 <p><div class="clearfix">
   <ul class="dev_layer_select slightly-pull-right nav nav-pills">
     <li class="dropdown">
@@ -99,7 +126,7 @@
 <tr>
 <td><strong>restricted</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.9?<a href="/constructor/true">true</a></td>
-<td>Whether viewing/writing in this channel for a reason (see <code>restriction_reason</code></td>
+<td>Whether viewing/writing in this channel for a reason (see <code>restriction_reason</code>)</td>
 </tr>
 <tr>
 <td><strong>signatures</strong></td>
@@ -119,7 +146,7 @@
 <tr>
 <td><strong>has_link</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.20?<a href="/constructor/true">true</a></td>
-<td>Whether this channel has a private join link</td>
+<td>Whether this channel has a linked <a href="/api/discussion">discussion group »</a></td>
 </tr>
 <tr>
 <td><strong>has_geo</strong></td>