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

Update content of files

Browse source
This commit is contained in:
GitHub Action 2022-03-03 18:28:18 +00:00
parent 1f3cb1139d
commit e33e55d3d4
7 changed files with 19 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong
View file

@ -4,10 +4,10 @@
<meta charset="utf-8">
<title>updates.channelDifferenceTooLong</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta property="description" content="The provided pts + limit &lt; remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:">
<meta property="description" content="The provided pts + limit &lt; remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways (assuming the existence of a persistent database to locally store messages):">
<meta property="og:title" content="updates.channelDifferenceTooLong">
<meta property="og:image" content="">
<meta property="og:description" content="The provided pts + limit &lt; remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:">
<meta property="og:description" content="The provided pts + limit &lt; remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways (assuming the existence of a persistent database to locally store messages):">
<link rel="shortcut icon" href="/favicon.ico?4" type="image/x-icon" />
<link href="/css/bootstrap.min.css?3" rel="stylesheet">
@ -41,22 +41,20 @@
<div id="dev_page_content"><p>The provided <code>pts + limit &lt; remote pts</code>. Simply, there are too many updates to be fetched (more than <code>limit</code>), the client has to resolve the update gap in one of the following ways (assuming the existence of a persistent database to locally store messages):</p>
<ol>
<li>Delete all known messages in the chat, begin from scratch by refetching all messages manually with <a href="/method/messages.getHistory">messages.getHistory</a>.
It is easy to implement, but suddenly disappearing messages look awful to the user.</li>
<li>Save all messages loaded in the memory until application restart, but delete all messages from the database.
Messages left in the memory must be lazily updated using calls to <a href="/method/messages.getHistory">messages.getHistory</a>.<br>
<li>Delete all known messages in the chat, begin from scratch by refetching all messages manually with <a href="/method/messages.getHistory">messages.getHistory</a>. It is easy to implement, but suddenly disappearing messages look awful to the user.</li>
<li>Save all messages loaded in the memory until application restart, but delete all messages from the database. Messages left in the memory must be lazily updated using calls to <a href="/method/messages.getHistory">messages.getHistory</a>.<br>
It will look much smoother to the user, they will need to redownload messages only after client restart.<br>
Unsynchronized messages left in memory shouldn't be saved to the database, results of <a href="/method/messages.getHistory">messages.getHistory</a> and <a href="/method/messages.getMessages">messages.getMessages</a> must be used to update the state of deleted and edited messages left in the memory. </li>
Unsynchronized messages left in memory shouldn't be saved to the database, results of <a href="/method/messages.getHistory">messages.getHistory</a> and <a href="/method/messages.getMessages">messages.getMessages</a> must be used to update the state of deleted and edited messages left in the memory.</li>
<li>Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges.<br>
Messages in the database will be excluded when paginating through or searching the local message history after application restart and will be available only through individual message queries.<br>
Every message should still be checked using <a href="/method/messages.getHistory">messages.getHistory</a>.<br>
It has more disadvantages over 2) than advantages. </li>
It has more disadvantages over 2) than advantages.</li>
<li>Save all messages with saving all data about continuous message ranges.<br>
Messages from the database may be used when paginating through or searching the local message history.<br>
The messages should still be lazily checked using <a href="/method/messages.getHistory">messages.getHistory</a>, but they are still available offline.<br>
It is the best way for gaps support, but it is pretty hard to implement correctly. </li>
It is the best way for gaps support, but it is pretty hard to implement correctly.</li>
</ol>
<p>It should be also noted that some messages like live location messages shouldn't be deleted. </p>
<p>It should be also noted that some messages like live location messages shouldn't be deleted.</p>
<p><div class="clearfix">
<ul class="dev_layer_select slightly-pull-right nav nav-pills">
<li class="dropdown">

2
data/corefork.telegram.org/method/account.initTakeoutSession
View file

@ -122,7 +122,7 @@
<tr>
<td>420</td>
<td>TAKEOUT_INIT_DELAY_%d</td>
<td>Wait %d seconds before initing takeout.</td>
<td>Wait %d seconds before initializing takeout.</td>
</tr>
</tbody>
</table>

2
data/corefork.telegram.org/method/channels.setStickers
View file

@ -103,7 +103,7 @@
<tr>
<td>406</td>
<td>STICKERSET_OWNER_ANONYMOUS</td>
<td>Provided stickerset can't be installed as group stickerset to prevent admin deanonymisation.</td>
<td>Provided stickerset can't be installed as group stickerset to prevent admin deanonymization.</td>
</tr>
</tbody>
</table>

4
data/corefork.telegram.org/method/messages.sendMedia
View file

@ -368,7 +368,7 @@
<tr>
<td>400</td>
<td>QUIZ_CORRECT_ANSWERS_TOO_MUCH</td>
<td>You specified too many correct answers in a quiz, quizes can only have one right answer!</td>
<td>You specified too many correct answers in a quiz, quizzes can only have one right answer!</td>
</tr>
<tr>
<td>400</td>
@ -378,7 +378,7 @@
<tr>
<td>400</td>
<td>QUIZ_MULTIPLE_INVALID</td>
<td>Quizes can't have the multiple_choice flag set!</td>
<td>Quizzes can't have the multiple_choice flag set!</td>
</tr>
<tr>
<td>500</td>

5
data/corefork.telegram.org/method/messages.sendReaction
View file

@ -122,6 +122,11 @@
</tr>
<tr>
<td>400</td>
<td>MESSAGE_NOT_MODIFIED</td>
<td>The message text has not changed.</td>
</tr>
<tr>
<td>400</td>
<td>PEER_ID_INVALID</td>
<td>The provided peer id is invalid.</td>
</tr>

2
data/corefork.telegram.org/method/messages.setTyping
View file

@ -169,7 +169,7 @@
<h4><a class="anchor" href="#layers" id="layers" name="layers"><i class="anchor-icon"></i></a><a href="/api/layers">Layers</a></h4>
<p>Below you will find information on schema changes. For more details on the use of layers, see <a href="/api/invoking#layers">Invoking API methods</a>.</p>
<h4><a class="anchor" href="#sendmessageaction" id="sendmessageaction" name="sendmessageaction"><i class="anchor-icon"></i></a><a href="/type/SendMessageAction">SendMessageAction</a></h4>
<p>User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.</p></div>
<p>User actions. Use this to provide users with detailed info about their chat partner's actions: typing or sending attachments of all kinds.</p></div>
</div>

2
data/corefork.telegram.org/methods.html
View file

@ -2043,7 +2043,7 @@
</tr>
<tr>
<td><a href="/method/messages.faveSticker">messages.faveSticker</a></td>
<td>Mark a sticker as favorite</td>
<td>Mark or unmark a sticker as favorite</td>
</tr>
<tr>
<td><a href="/method/messages.getAllStickers">messages.getAllStickers</a></td>