OpenSource/telegram-crawler
OpenSource/telegram-crawler
1
0
Fork 0
mirror of https://github.com/MarshalX/telegram-crawler.git synced 2025-01-20 16:15:08 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update content of files

Browse source
This commit is contained in:
GitHub Action 2024-08-05 14:00:03 +00:00
parent e867e326b5
commit 72c1e85792
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
data/web/corefork.telegram.org/api/peers.html
View file

@ -159,7 +159,8 @@ Info about these IDs may be fetched with the zero access hash even by users. </
<p>After failing to download a peer photo.</p>
</li>
</ul>
<p><strong>Do not</strong> manually refresh peer information in any other case, to avoid overloading the server by continuously requesting changes for the same unchanged information. </p>
<p>It is not recommended to manually refresh peer information in any other case, to avoid overloading the server by continuously requesting changes for the same unchanged information.<br>
Note that in some cases, since it is impossible to send updates about all Telegram users, the peer info database might still be outdated as relative updates might not get sent; however, this is <a href="#quality-of-life-checks">usually not a big problem »</a>. </p>
<p>The only exception to the above rule is <a href="/method/contacts.getStatuses">contacts.getStatuses</a>, which should be invoked by clients every <code>70000-100000</code> seconds to update the <a href="/constructor/user">user</a>.<code>status</code> field of contacts.<br>
The exact contact status polling interval should be randomly chosen between <code>70000</code> and <code>100000</code>, and re-chosen every time <a href="/method/contacts.getStatuses">contacts.getStatuses</a> is invoked.<br>
If a <a href="/method/contacts.getStatuses">contacts.getStatuses</a> query fails, repeat the method call after <code>5</code> to <code>10</code> seconds.</p>