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

Update content of files

Browse source
This commit is contained in:
GitHub Action 2023-03-28 20:15:37 +00:00
parent 6f941cbfa1
commit 8ed970f72c
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
data/web/corefork.telegram.org/api/forum.html
View file

@ -92,7 +92,7 @@ To fetch information about one or more topics by their ID, use <a href="/method/
On the other hand, topics with <code>id != 1</code> are just the <a href="/api/threads">message thread</a> of the <a href="/method/messageActionTopicCreate">messageActionTopicCreate</a> service message that created that topic.<br>
This means that topics should be treated similarly to <a href="/api/threads">message threads</a> by the client.<br>
To send messages to these topics, pass the topic ID to the <code>reply_msg_id</code> parameter of <a href="/method/messages.sendMessage">messages.sendMessage</a>, <a href="/method/messages.sendMedia">messages.sendMedia</a> et cetera.<br>
Replies to messages within a topic work as usual, however, since <a href="/api/threads">message threads</a> can't have nested message threads, topics (except for the "General" topic) also can't have message threads (so replies to messages within topics won't generate further message threads). </p>
Replies to messages within a topic work as usual (simply pass the ID of the message to reply to to <code>reply_msg_id</code>, ignoring the topic ID), however, since <a href="/api/threads">message threads</a> can't have nested message threads, topics (except for the "General" topic) also can't have message threads (so replies to messages within topics won't generate further message threads). </p>
<p>Topics have a name (<code>title</code>) and an icon: the icon can be a <a href="/api/custom-emoji">custom emoji</a> specified by the <code>icon_emoji_id</code>, or a default chat icon if <code>icon_emoji_id</code> is not set, filled with the color specified in <code>icon_color</code>.<br>
Topics can be temporarily <code>closed</code>, preventing further messages from being sent to the topic.<br>
Additionally, the "General" topic may also be <code>hidden</code>.<br>

4
data/web/corefork.telegram.org/constructor/dialog.html
View file

@ -129,7 +129,7 @@
<tr>
<td><strong>draft</strong></td>
<td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.1?<a href="/type/DraftMessage">DraftMessage</a></td>
<td>Message draft</td>
<td>Message <a href="/api/drafts">draft</a></td>
</tr>
<tr>
<td><strong>folder_id</strong></td>
@ -139,7 +139,7 @@
<tr>
<td><strong>ttl_period</strong></td>
<td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.5?<a href="/type/int">int</a></td>
<td> </td>
<td>Time-to-live of all messages sent in this dialog</td>
</tr>
</tbody>
</table>