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

Update content of files

Browse source
This commit is contained in:
GitHub Action 2024-07-25 15:40:51 +00:00
parent 92236ec62c
commit b4a1f1c82a
3 changed files with 15 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
data/web/corefork.telegram.org/api/layers.html
View file

@ -270,6 +270,13 @@
<li><a href="/method/stickers.replaceSticker">Replace single stickers in stickersets »</a></li>
<li><a href="/method/messages.getMyStickers">Fetch all stickersets owned by the current account »</a></li>
<li>A refactored and improved <a href="/api/invites#direct-invites">channel/supergroup/group invitation flow »</a></li>
<li>Improvements for <a href="/constructor/keyboardButtonRequestPeer">keyboardButtonRequestPeer</a>.<br>
Now bots will also receive the selected peer's name, username, photo (if present and requested by the new bot-side <a href="/constructor/inputKeyboardButtonRequestPeer">inputKeyboardButtonRequestPeer</a> button).<br>
Previously, just the peer's ID was sent, which could only be used to fetch the name/photo if the bot had already previously cached the peer's <a href="/api/peers#access-hash">access hash »</a>. <ul>
<li>Bots will now receive the requested info as a <a href="/constructor/messageActionRequestedPeerSentMe">messageActionRequestedPeerSentMe</a> constructor instead of the old <a href="/constructor/messageActionRequestedPeer">messageActionRequestedPeer</a> constructor, which will only be received by users that shared the info. </li>
<li>Bots must now use <a href="/constructor/inputKeyboardButtonRequestPeer">inputKeyboardButtonRequestPeer</a> to send <a href="/constructor/keyboardButtonRequestPeer">keyboardButtonRequestPeer</a> buttons.</li>
</ul>
</li>
</ul>
<h4><a class="anchor" href="#schema-changes" id="schema-changes" name="schema-changes"><i class="anchor-icon"></i></a>Schema changes</h4>
<h5><a class="anchor" href="#new-methods" id="new-methods" name="new-methods"><i class="anchor-icon"></i></a>New Methods</h5>

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

@ -2,12 +2,12 @@
<html class="">
<head>
<meta charset="utf-8">
<title>Peers</title>
<title>Peer database</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta property="description" content="Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively…">
<meta property="og:title" content="Peers">
<meta property="description" content="Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively (passively) when received via updates or by other means (as specified in the documentation), to avoid overloading the server by continuously requesting changes for the same unchanged information.">
<meta property="og:title" content="Peer database">
<meta property="og:image" content="">
<meta property="og:description" content="Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively…">
<meta property="og:description" content="Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively (passively) when received via updates or by other means (as specified in the documentation), to avoid overloading the server by continuously requesting changes for the same unchanged information.">
<link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
<link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@ -39,8 +39,8 @@
<div class="container clearfix">
<div class="dev_page">
<div id="dev_page_content_wrap" class=" ">
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/api/peers" >Peers</a></li></ul></div>
<h1 id="dev_page_title">Peers</h1>
<div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/api/peers" >Peer database</a></li></ul></div>
<h1 id="dev_page_title">Peer database</h1>
<div id="dev_page_content"><!-- scroll_nav -->
@ -148,6 +148,7 @@ Info about these IDs may be fetched with the zero access hash even by users. </
</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>Note: some other, non-peer-related constructors (i.e. not <a href="/constructor/user">user</a>, <a href="/constructor/chat">chat</a> or <a href="/constructor/channel">channel</a>) may also contain access hashes, which should be stored in a different database. </p>
<h4><a class="anchor" href="#peer-id" id="peer-id" name="peer-id"><i class="anchor-icon"></i></a>Peer ID</h4>
<p>The peer <code>id</code> is a unique 64-bit ID used to identify a specific user, chat or channel. </p>
<p>This field should be used as primary key in the channel, chat and user databases. </p>

2
data/web/corefork.telegram.org/api/qr-login.html
View file

@ -69,7 +69,7 @@ After the expiration of the current QR code, the <a href="/method/auth.exportLog
The token must be extracted from the <code>tg://login</code> URI and <a href="https://tools.ietf.org/html/rfc4648#section-5">base64url-decoded</a> before using it in the method.</p>
<p>Possible <a href="/api/errors">errors</a> returned by the method are: </p>
<ul>
<li>400 - <code>AUTH_TOKEN_INVALID</code>, an invalid authorization token was provided</li>
<li>400 - <code>AUTH_TOKEN_INVALID</code>, <code>AUTH_TOKEN_INVALID1</code>, an invalid authorization token was provided</li>
<li>400 - <code>AUTH_TOKEN_EXPIRED</code>, the provided authorization token has expired and the updated QR-code must be re-scanned</li>
<li>400 - <code>AUTH_TOKEN_ALREADY_ACCEPTED</code>, the authorization token was already used</li>
</ul>