From 7467352d446b0667279e10b3fc32b331906c7f6e Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 24 Jul 2024 15:44:34 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org/api/peers.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/data/web/corefork.telegram.org/api/peers.html b/data/web/corefork.telegram.org/api/peers.html index f986133ba0..13f406ea13 100644 --- a/data/web/corefork.telegram.org/api/peers.html +++ b/data/web/corefork.telegram.org/api/peers.html @@ -118,8 +118,9 @@ Info about these IDs may be fetched with the zero access hash even by users.
  • account.toggleUsername, account.reorderUsernames - For ourselves
  • bots.toggleUsername, bots.reorderUsernames - For the bot whose username we updated
    • +
  • channels.toggleUsername, channels.reorderUsernames - For the channel whose username we updated
    • -

    Info should only be manually refreshed with a call to users.getUsers if the new username order/active username cannot be applied locally (i.e. the method call successfully set as active some username that isn't associated to the user in our local cache, and so on), otherwise the username and usernames fields of the peer info database should be updated locally, using the info that was passed to the toggle/reorder methods by the user.

    +

    Info should only be manually refreshed with a call to users.getUsers, channels.getChannels if the new username order/active username cannot be applied locally (i.e. the method call successfully set as active some username that isn't associated to the peer in our local cache, and so on), otherwise the username and usernames fields of the peer info database should be updated locally, using the info that was passed to the toggle/reorder methods by the user.

    Do not refresh peer information in any other case, to avoid overloading the server by continuously requesting changes for the same unchanged information.