mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-12-28 23:38:26 +01:00
Update content of files
This commit is contained in:
GitHub Action
parent
9d92ac5b2e
commit
6f0c96d3f8
12 changed files with 56 additions and 18 deletions
|
|
@ -203,6 +203,8 @@ This allows the server to filter messages based on a text query, and even on the
|
|||
<p>How to transcribe voice messages.</p>
|
||||
<h4><a class="anchor" href="#message-translation" id="message-translation" name="message-translation"><i class="anchor-icon"></i></a><a href="/api/translation">Message translation</a></h4>
|
||||
<p>Telegram allows translating chat messages, and <a href="/api/premium">Telegram Premium</a> users may even enable real-time chat translation. </p>
|
||||
<h4><a class="anchor" href="#native-antispam-system" id="native-antispam-system" name="native-antispam-system"><i class="anchor-icon"></i></a><a href="/api/antispam">Native antispam system</a></h4>
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p>
|
||||
<h4><a class="anchor" href="#web-events" id="web-events" name="web-events"><i class="anchor-icon"></i></a><a href="/api/web-events">Web events</a></h4>
|
||||
<p>When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.</p></div>
|
||||
|
||||
|
|
|
|||
|
|
@ -203,6 +203,8 @@ This allows the server to filter messages based on a text query, and even on the
|
|||
<p>How to transcribe voice messages.</p>
|
||||
<h4><a class="anchor" href="#message-translation" id="message-translation" name="message-translation"><i class="anchor-icon"></i></a><a href="/api/translation">Message translation</a></h4>
|
||||
<p>Telegram allows translating chat messages, and <a href="/api/premium">Telegram Premium</a> users may even enable real-time chat translation. </p>
|
||||
<h4><a class="anchor" href="#native-antispam-system" id="native-antispam-system" name="native-antispam-system"><i class="anchor-icon"></i></a><a href="/api/antispam">Native antispam system</a></h4>
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p>
|
||||
<h4><a class="anchor" href="#web-events" id="web-events" name="web-events"><i class="anchor-icon"></i></a><a href="/api/web-events">Web events</a></h4>
|
||||
<p>When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.</p></div>
|
||||
|
||||
|
|
|
|||
|
|
@ -2,12 +2,12 @@
|
|||
<html class="">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<title>Page not found</title>
|
||||
<title>Native antispam system</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta property="description" content="">
|
||||
<meta property="og:title" content="Page not found">
|
||||
<meta property="description" content="Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.">
|
||||
<meta property="og:title" content="Native antispam system">
|
||||
<meta property="og:image" content="">
|
||||
<meta property="og:description" content="">
|
||||
<meta property="og:description" content="Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.">
|
||||
<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,10 +39,26 @@
|
|||
<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></li></ul></div>
|
||||
<h1 id="dev_page_title">Page not found</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/antispam" >Native antispam system</a></li></ul></div>
|
||||
<h1 id="dev_page_title">Native antispam system</h1>
|
||||
|
||||
<div id="dev_page_content">The page has not been saved</div>
|
||||
<div id="dev_page_content"><!-- scroll_nav -->
|
||||
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p>
|
||||
<p>Schema:</p>
|
||||
<pre><code><a href='/constructor/channelFull'>channelFull</a>#f2355507 flags:<a href='/type/%23'>#</a> can_view_participants:flags.3?<a href='/constructor/true'>true</a> can_set_username:flags.6?<a href='/constructor/true'>true</a> can_set_stickers:flags.7?<a href='/constructor/true'>true</a> hidden_prehistory:flags.10?<a href='/constructor/true'>true</a> can_set_location:flags.16?<a href='/constructor/true'>true</a> has_scheduled:flags.19?<a href='/constructor/true'>true</a> can_view_stats:flags.20?<a href='/constructor/true'>true</a> blocked:flags.22?<a href='/constructor/true'>true</a> flags2:<a href='/type/%23'>#</a> can_delete_channel:flags2.0?<a href='/constructor/true'>true</a> antispam:flags2.1?<a href='/constructor/true'>true</a> participants_hidden:flags2.2?<a href='/constructor/true'>true</a> translations_disabled:flags2.3?<a href='/constructor/true'>true</a> id:<a href='/type/long'>long</a> about:<a href='/type/string'>string</a> participants_count:flags.0?<a href='/type/int'>int</a> admins_count:flags.1?<a href='/type/int'>int</a> kicked_count:flags.2?<a href='/type/int'>int</a> banned_count:flags.2?<a href='/type/int'>int</a> online_count:flags.13?<a href='/type/int'>int</a> read_inbox_max_id:<a href='/type/int'>int</a> read_outbox_max_id:<a href='/type/int'>int</a> unread_count:<a href='/type/int'>int</a> chat_photo:<a href='/type/Photo'>Photo</a> notify_settings:<a href='/type/PeerNotifySettings'>PeerNotifySettings</a> exported_invite:flags.23?<a href='/type/ExportedChatInvite'>ExportedChatInvite</a> bot_info:<a href='/type/Vector%20t'>Vector</a><<a href='/type/BotInfo'>BotInfo</a>> migrated_from_chat_id:flags.4?<a href='/type/long'>long</a> migrated_from_max_id:flags.4?<a href='/type/int'>int</a> pinned_msg_id:flags.5?<a href='/type/int'>int</a> stickerset:flags.8?<a href='/type/StickerSet'>StickerSet</a> available_min_id:flags.9?<a href='/type/int'>int</a> folder_id:flags.11?<a href='/type/int'>int</a> linked_chat_id:flags.14?<a href='/type/long'>long</a> location:flags.15?<a href='/type/ChannelLocation'>ChannelLocation</a> slowmode_seconds:flags.17?<a href='/type/int'>int</a> slowmode_next_send_date:flags.18?<a href='/type/int'>int</a> stats_dc:flags.12?<a href='/type/int'>int</a> pts:<a href='/type/int'>int</a> call:flags.21?<a href='/type/InputGroupCall'>InputGroupCall</a> ttl_period:flags.24?<a href='/type/int'>int</a> pending_suggestions:flags.25?<a href='/type/Vector%20t'>Vector</a><<a href='/type/string'>string</a>> groupcall_default_join_as:flags.26?<a href='/type/Peer'>Peer</a> theme_emoticon:flags.27?<a href='/type/string'>string</a> requests_pending:flags.28?<a href='/type/int'>int</a> recent_requesters:flags.28?<a href='/type/Vector%20t'>Vector</a><<a href='/type/long'>long</a>> default_send_as:flags.29?<a href='/type/Peer'>Peer</a> available_reactions:flags.30?<a href='/type/ChatReactions'>ChatReactions</a> = <a href='/type/ChatFull'>ChatFull</a>;
|
||||
|
||||
<a href='/constructor/channelAdminLogEventActionToggleAntiSpam'>channelAdminLogEventActionToggleAntiSpam</a>#64f36dfc new_value:<a href='/type/Bool'>Bool</a> = <a href='/type/ChannelAdminLogEventAction'>ChannelAdminLogEventAction</a>;
|
||||
<a href='/constructor/channelAdminLogEventActionDeleteMessage'>channelAdminLogEventActionDeleteMessage</a>#42e047bb message:<a href='/type/Message'>Message</a> = <a href='/type/ChannelAdminLogEventAction'>ChannelAdminLogEventAction</a>;
|
||||
|
||||
---functions---
|
||||
|
||||
<a href='/method/channels.toggleAntiSpam'>channels.toggleAntiSpam</a>#68f3e4eb channel:<a href='/type/InputChannel'>InputChannel</a> enabled:<a href='/type/Bool'>Bool</a> = <a href='/type/Updates'>Updates</a>;
|
||||
<a href='/method/channels.reportAntiSpamFalsePositive'>channels.reportAntiSpamFalsePositive</a>#a850a693 channel:<a href='/type/InputChannel'>InputChannel</a> msg_id:<a href='/type/int'>int</a> = <a href='/type/Bool'>Bool</a>;</code></pre>
|
||||
<p>Native antispam functionality can be enabled for <a href="/api/channel">supergroups</a> using <a href="/method/channels.toggleAntiSpam">channels.toggleAntiSpam</a>, if the supergroup has at least <code>telegram_antispam_group_size_min</code> members, as specified by the <a href="/api/config#client-configuration">client configuration parameters</a>.</p>
|
||||
<p>Once enabled, Telegram's native antispam system will start monitoring the supergrup, automatically deleting spam messages using the official Telegram Antispam bot, with ID equal to <code>telegram_antispam_user_id</code>, as specified by the <a href="/api/config#client-configuration">client configuration parameters</a>.<br>
|
||||
Note that this bot <strong>does not</strong> have to be added as participant or admin to the supergroup for the native antispam system to work, just invoking <a href="/method/channels.toggleAntiSpam">channels.toggleAntiSpam</a> is enough; however, it should still be locally shown as a group admin when displaying the admin list to the user (clients should simply append it to the admin list <em>without</em> invoking <a href="/method/channels.editAdmin">channels.editAdmin</a>). </p>
|
||||
<p>False positive message deletions can be reported by admins by navigating through the <a href="/api/recent-actions">admin log</a>, and invoking <a href="/method/channels.reportAntiSpamFalsePositive">channels.reportAntiSpamFalsePositive</a> for mistaken <a href="/constructor/channelAdminLogEventActionDeleteMessage">channelAdminLogEventActionDeleteMessage</a> events made by the <code>telegram_antispam_user_id</code> bot.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
@ -109,8 +125,11 @@
|
|||
</div>
|
||||
</div>
|
||||
<script src="/js/main.js?47"></script>
|
||||
|
||||
<script>backToTopInit("Go up");
|
||||
<script src="/js/jquery.min.js?1"></script>
|
||||
<script src="/js/bootstrap.min.js?1"></script>
|
||||
|
||||
<script>window.initDevPageNav&&initDevPageNav();
|
||||
backToTopInit("Go up");
|
||||
removePreloadInit();
|
||||
</script>
|
||||
</body>
|
||||
|
|
|
|||
|
|
@ -315,7 +315,10 @@ While <a href="/method/help.getConfig">help.getConfig</a> returns MTProto-specif
|
|||
<h4><a class="anchor" href="#forum-upgrade-participants-min" id="forum-upgrade-participants-min" name="forum-upgrade-participants-min"><i class="anchor-icon"></i></a><code>forum_upgrade_participants_min</code></h4>
|
||||
<h4><a class="anchor" href="#topics-pinned-limit" id="topics-pinned-limit" name="topics-pinned-limit"><i class="anchor-icon"></i></a><code>topics_pinned_limit</code></h4>
|
||||
<h4><a class="anchor" href="#telegram-antispam-user-id" id="telegram-antispam-user-id" name="telegram-antispam-user-id"><i class="anchor-icon"></i></a><code>telegram_antispam_user_id</code></h4>
|
||||
<p>The ID of the official <a href="/api/antispam">native antispam bot</a>, that will automatically delete spam messages if enabled as specified in the <a href="/api/antispam">native antispam documentation »</a>.<br>
|
||||
When fetching the admin list of a supergroup using <a href="/method/channels.getParticipants">channels.getParticipants</a>, if native antispam functionality in the specified supergroup, the bot should be manually added to the admin list displayed to the user. </p>
|
||||
<h4><a class="anchor" href="#telegram-antispam-group-size-min" id="telegram-antispam-group-size-min" name="telegram-antispam-group-size-min"><i class="anchor-icon"></i></a><code>telegram_antispam_group_size_min</code></h4>
|
||||
<p>Minimum number of members required to enable <a href="/api/antispam">native antispam functionality</a>.</p>
|
||||
<h4><a class="anchor" href="#fragment-prefixes" id="fragment-prefixes" name="fragment-prefixes"><i class="anchor-icon"></i></a><code>fragment_prefixes</code></h4>
|
||||
<h4><a class="anchor" href="#hidden-members-group-size-min" id="hidden-members-group-size-min" name="hidden-members-group-size-min"><i class="anchor-icon"></i></a><code>hidden_members_group_size_min</code></h4>
|
||||
<h4><a class="anchor" href="#ios-disable-parallel-channel-reset" id="ios-disable-parallel-channel-reset" name="ios-disable-parallel-channel-reset"><i class="anchor-icon"></i></a><code>ios_disable_parallel_channel_reset</code></h4>
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@
|
|||
<li>Added <a href="/constructor/inputBotAppShortName">inputBotAppShortName</a> - Used to fetch information about a <a href="/api/bots/webapps#bot-web-apps">bot web app</a> by its short name</li>
|
||||
<li>Added <a href="/constructor/botAppNotModified">botAppNotModified</a> - Bot app info hasn't changed.</li>
|
||||
<li>Added <a href="/constructor/botApp">botApp</a> - Contains information about a <a href="/api/bots/webapps#bot-web-apps">bot web app</a>.</li>
|
||||
<li>Added <a href="/constructor/messages.botApp">messages.botApp</a> - Contains information about a <a href="/api/bots/webapps#bot-web-app">bot web app</a></li>
|
||||
<li>Added <a href="/constructor/messages.botApp">messages.botApp</a> - Contains information about a <a href="/api/bots/webapps#bot-web-apps">bot web app</a></li>
|
||||
<li>Added <a href="/constructor/appWebViewResultUrl">appWebViewResultUrl</a> - Contains the link that must be used to open a <a href="/api/bots/webapps#bot-web-apps">bot web app</a>.</li>
|
||||
<li>Added <a href="/constructor/inlineBotWebView">inlineBotWebView</a> - Specifies a <a href="/api/bots/webapps#simple-web-apps">bot web app</a> button, shown on top of the inline query results list.</li>
|
||||
<li>Added <a href="/constructor/readParticipantDate">readParticipantDate</a> - Contains info about when a certain participant has read a message</li>
|
||||
|
|
|
|||
|
|
@ -334,7 +334,7 @@ Note that these methods will only work on packs <strong>created by the bot that
|
|||
<ul>
|
||||
<li>Your interfaces, texts and <a href="/bots/api#answerinlinequery">inline results</a> should adapt seamlessly to the <em>language_code</em>, without user intervention.</li>
|
||||
<li>Connected <a href="/bots/webapps">WebApps</a> will receive the user's <em>language_code</em> – your HTML page should account for it.</li>
|
||||
<li><a href="/bots/html5-games">HTML5 Games</a> can obtain language information if you specify it as a <a href="/bots/games#using-url-parameters">URL parameter</a>. You can generate this parameter from the <em>language_code</em> field in the <a href="/bots/api#user">User</a> object served with the initial game <a href="/bots/api#callbackquery">CallbackQuery</a>.</li>
|
||||
<li><a href="/bots/games">HTML5 Games</a> can obtain language information if you specify it as a <a href="/bots/games#using-url-parameters">URL parameter</a>. You can generate this parameter from the <em>language_code</em> field in the <a href="/bots/api#user">User</a> object served with the initial game <a href="/bots/api#callbackquery">CallbackQuery</a>.</li>
|
||||
<li>Command lists can also be specified for individual languages – more on this <a href="#commands">here</a>.</li>
|
||||
</ul>
|
||||
<div class="blog_video_player_wrap" style="max-width: 400px; margin: 20px auto 20px;">
|
||||
|
|
@ -529,7 +529,7 @@ You can only transfer a bot to users who have interacted with it at least once.<
|
|||
<li>/setabouttext – change the bot's <strong>about info</strong>, a shorter text up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.</li>
|
||||
<li>/setuserpic – change the bot's <strong>profile picture</strong>. </li>
|
||||
<li>/setcommands – change the list of <strong>commands</strong> supported by your bot. Users will see these commands as suggestions when they type <code>/</code> in the chat with your bot. See <a href="#commands">commands</a> for more info.</li>
|
||||
<li>/setdomain – link a <strong>website domain</strong> to your bot. See the <a href="#login-widget">login widget</a> section.</li>
|
||||
<li>/setdomain – link a <strong>website domain</strong> to your bot. See the <a href="#widgets">login widget</a> section.</li>
|
||||
<li>/deletebot – delete your bot and <strong>free its username</strong>. Cannot be undone.</li>
|
||||
</ul>
|
||||
<p>Or you can use the <code>/mybots</code> command, tap on your bot and use the modern inline interface to edit it.</p>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,10 @@
|
|||
</tbody>
|
||||
</table>
|
||||
<h3><a class="anchor" href="#type" id="type" name="type"><i class="anchor-icon"></i></a>Type</h3>
|
||||
<p><a href="/type/ChannelAdminLogEventAction">ChannelAdminLogEventAction</a></p></div>
|
||||
<p><a href="/type/ChannelAdminLogEventAction">ChannelAdminLogEventAction</a></p>
|
||||
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
|
||||
<h4><a class="anchor" href="#native-antispam-system" id="native-antispam-system" name="native-antispam-system"><i class="anchor-icon"></i></a><a href="/api/antispam">Native antispam system</a></h4>
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -322,6 +322,8 @@
|
|||
<p>Telegram offers detailed channel statistics for channels and supergroups.</p>
|
||||
<h4><a class="anchor" href="#discussion-groups" id="discussion-groups" name="discussion-groups"><i class="anchor-icon"></i></a><a href="/api/discussion">Discussion groups</a></h4>
|
||||
<p>Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.</p>
|
||||
<h4><a class="anchor" href="#native-antispam-system" id="native-antispam-system" name="native-antispam-system"><i class="anchor-icon"></i></a><a href="/api/antispam">Native antispam system</a></h4>
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p>
|
||||
<h4><a class="anchor" href="#translation" id="translation" name="translation"><i class="anchor-icon"></i></a><a href="/api/translation">Translation</a></h4>
|
||||
<p>Telegram allows translating chat messages: Telegram Premium users may even enable real-time chat translation.</p>
|
||||
<h4><a class="anchor" href="#admin-banned-default-rights" id="admin-banned-default-rights" name="admin-banned-default-rights"><i class="anchor-icon"></i></a><a href="/api/rights">Admin, banned, default rights</a></h4>
|
||||
|
|
|
|||
|
|
@ -85,6 +85,8 @@
|
|||
<p><a href="/type/Bool">Bool</a></p>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3>
|
||||
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
|
||||
<h4><a class="anchor" href="#native-antispam-system" id="native-antispam-system" name="native-antispam-system"><i class="anchor-icon"></i></a><a href="/api/antispam">Native antispam system</a></h4>
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p>
|
||||
<h4><a class="anchor" href="#admin-log" id="admin-log" name="admin-log"><i class="anchor-icon"></i></a><a href="/api/recent-actions">Admin log</a></h4>
|
||||
<p>Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.</p></div>
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@
|
|||
<tr>
|
||||
<td><strong>channel</strong></td>
|
||||
<td style="text-align: center;"><a href="/type/InputChannel">InputChannel</a></td>
|
||||
<td>Supergroup ID</td>
|
||||
<td>Supergroup ID. The specified supergroup must have at least <code>telegram_antispam_group_size_min</code> members to enable antispam functionality, as specified by the <a href="/api/config#client-configuration">client configuration parameters</a>.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>enabled</strong></td>
|
||||
|
|
@ -88,7 +88,12 @@
|
|||
</table>
|
||||
<h3><a class="anchor" href="#result" id="result" name="result"><i class="anchor-icon"></i></a>Result</h3>
|
||||
<p><a href="/type/Updates">Updates</a></p>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3></div>
|
||||
<h3><a class="anchor" href="#bots-can-use-this-method" id="bots-can-use-this-method" name="bots-can-use-this-method"><i class="anchor-icon"></i></a>Bots can use this method</h3>
|
||||
<h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
|
||||
<h4><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a><a href="/api/config">Client configuration</a></h4>
|
||||
<p>The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.</p>
|
||||
<h4><a class="anchor" href="#native-antispam-system" id="native-antispam-system" name="native-antispam-system"><i class="anchor-icon"></i></a><a href="/api/antispam">Native antispam system</a></h4>
|
||||
<p>Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.</p></div>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -164,7 +164,7 @@ Multiple transport protocols are defined:</p>
|
|||
<h3><a class="anchor" href="#recap" id="recap" name="recap"><i class="anchor-icon"></i></a>Recap</h3>
|
||||
<p>To recap, using the <a href="https://en.wikipedia.org/wiki/OSI_model#Layer_architecture">ISO/OSI stack as comparison</a>: </p>
|
||||
<ul>
|
||||
<li>Layer 7 (Application): <a href="#high-level-component-rpc-query-language-api">High-level RPC API</a></li>
|
||||
<li>Layer 7 (Application): <a href="#high-level-component-rpc-query-languageapi">High-level RPC API</a></li>
|
||||
<li>Layer 6 (Presentation): <a href="/mtproto/TL">Type Language</a></li>
|
||||
<li>Layer 5 (Session): <a href="https://core.telegram.org/mtproto/description#session">MTProto session</a></li>
|
||||
<li>Layer 4 (Transport):<ul>
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@
|
|||
<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="/schema" >TL-schema</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/type/messages.BotApp" >messages.BotApp</a></li></ul></div>
|
||||
<h1 id="dev_page_title">messages.BotApp</h1>
|
||||
|
||||
<div id="dev_page_content"><p>Contains information about a <a href="/api/bots/webapps#bot-web-app">bot web app</a></p>
|
||||
<div id="dev_page_content"><p>Contains information about a <a href="/api/bots/webapps#bot-web-apps">bot web app</a></p>
|
||||
<p><div class="clearfix">
|
||||
<ul class="dev_layer_select slightly-pull-right nav nav-pills">
|
||||
<li class="dropdown">
|
||||
|
|
@ -71,7 +71,7 @@
|
|||
<tbody>
|
||||
<tr>
|
||||
<td><a href="/constructor/messages.botApp">messages.botApp</a></td>
|
||||
<td>Contains information about a <a href="/api/bots/webapps#bot-web-app">bot web app</a></td>
|
||||
<td>Contains information about a <a href="/api/bots/webapps#bot-web-apps">bot web app</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
|
|||
Loading…
Reference in a new issue