From 81acf9b5696792959e63d8e49f1f2bca59544f00 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Mon, 5 Aug 2024 10:33:44 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/business.html | 2 +- data/web/corefork.telegram.org/constructor/user.html | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/data/web/corefork.telegram.org/api/business.html b/data/web/corefork.telegram.org/api/business.html index 0748d6d1d1..eb587fd71c 100644 --- a/data/web/corefork.telegram.org/api/business.html +++ b/data/web/corefork.telegram.org/api/business.html @@ -167,7 +167,7 @@ foreach (quick_replies as quick_reply) { hash_ints[] = top_message.edit_date || 0; }

The method will return messages.quickRepliesNotModified if the passed hash is equal to the server-side hash, meaning that the order, names and last messages of the quick replies haven't changed.

-

Editing some intermediate message in a quick reply will not change the hash, which is why messages.getQuickReplyMessages should be used to fetch (a subset or all) messages in a quick reply shortcut, and its hash is generated as follows (from the full message list of a shortcut, obviously):

+

Editing some intermediate message in a quick reply will not change the hash, which is why messages.getQuickReplyMessages should be used to fetch (a subset or all) messages in a quick reply shortcut, and its hash is generated as follows:

hash_ints = [];
 foreach (messages as message) {
   hash_ints[] = message.id;
diff --git a/data/web/corefork.telegram.org/constructor/user.html b/data/web/corefork.telegram.org/constructor/user.html
index 3a53850b0b..63f28cb06a 100644
--- a/data/web/corefork.telegram.org/constructor/user.html
+++ b/data/web/corefork.telegram.org/constructor/user.html
@@ -91,7 +91,7 @@
 
 deleted
 flags.13?true
-Whether the account of this user was deleted
+Whether the account of this user was deleted. 
Changes to this flag should invalidate the local userFull cache for this user ID.
 
 
 bot
@@ -226,7 +226,7 @@
 
 username
 flags.3?string
-Main active username. 
When updating the local peer database, apply changes to this field only if: 
- The min flag is not set OR 
- The min flag is set AND 
- The min flag of the locally cached user entry is set.
+Main active username. 
When updating the local peer database, apply changes to this field only if: 
- The min flag is not set OR 
- The min flag is set AND 
- The min flag of the locally cached user entry is set. 
Changes to this flag should invalidate the local userFull cache for this user ID if the above conditions are respected and the bot_can_edit flag is also set.
 
 
 phone