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:
parent
e4b891a022
commit
f5dde292bf
9 changed files with 29 additions and 35 deletions
|
@ -86,7 +86,7 @@
|
|||
<p>Increase your productivity by creating bots for <strong>specific tasks</strong> – like converting files, managing chats or fetching today’s forecast. Users can chat directly with bots, or add them to groups and channels to introduce extra features.</p>
|
||||
<div class="blog_video_player_wrap" style="max-width: 600px; margin: 20px auto 20px;">
|
||||
<video class="blog_video_player tl_blog_vid_autoplay" onclick="videoTogglePlay(this)" autoplay loop controls muted poster="/file/464001084/12c1d/eNLdXm8moqA.134736/e28dd8ea6d49eee57d" style="max-width: 600px;" title="" alt="Custom tools">
|
||||
<source src="/file/464001310/11c34/aj8L8Ja6Oa4.3626069.mp4/1fa3a6a1e212051984" type="video/mp4">
|
||||
<source src="/file/464001127/10a99/GC0dSHYQTb0.3621529.mp4/75439f14147e13b6fb" type="video/mp4">
|
||||
</video>
|
||||
</div>
|
||||
|
||||
|
|
|
@ -4,12 +4,10 @@
|
|||
<meta charset="utf-8">
|
||||
<title>Bot API Library Examples</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta property="description" content="If you want to learn more about Telegram bots, start with our Introduction to Bots »
|
||||
Check out the FAQ, if you have questions.…">
|
||||
<meta property="description" content="A full tutorial covering everything from configuring your environment to deploying your finished bot is available here.…">
|
||||
<meta property="og:title" content="Bot API Library Examples">
|
||||
<meta property="og:image" content="">
|
||||
<meta property="og:description" content="If you want to learn more about Telegram bots, start with our Introduction to Bots »
|
||||
Check out the FAQ, if you have questions.…">
|
||||
<meta property="og:description" content="A full tutorial covering everything from configuring your environment to deploying your finished bot is available here.…">
|
||||
<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">
|
||||
|
@ -45,13 +43,10 @@ Check out the FAQ, if you have questions.…">
|
|||
<h1 id="dev_page_title">Bot API Library Examples</h1>
|
||||
|
||||
<div id="dev_page_content"><blockquote>
|
||||
<p>If you want to learn more about Telegram bots, start with our <a href="/bots"><strong>Introduction to Bots »</strong></a><br>Check out the <a href="/bots/faq"><strong>FAQ</strong></a>, if you have questions.</p>
|
||||
</blockquote>
|
||||
<p>A <strong>full tutorial</strong> covering everything from <a href="/bots/tutorial#getting-ready">configuring your environment</a> to <a href="/bots/tutorial#hosting">deploying</a> your finished bot is available <a href="/bots/tutorial">on this page</a>.</p>
|
||||
<p>Below are some libraries and frameworks <strong>developed by the Telegram community</strong> – you should take care to report any bugs you may find to the respective developers, as these projects are not maintained by Telegram.</p>
|
||||
<blockquote>
|
||||
<p>Ping us on <a href="https://telegram.me/botsupport">BotSupport</a> if you would like your library to appear on this page.</p>
|
||||
<p>A <strong>full tutorial</strong> covering everything from <a href="/bots/tutorial#getting-ready">configuring your environment</a> to <a href="/bots/tutorial#hosting">deploying</a> your finished bot is available <a href="/bots/tutorial">here</a>.</p>
|
||||
</blockquote>
|
||||
<p>This page lists some libraries and frameworks <strong>developed by the Telegram community</strong> – you should take care to report any bugs you may find to the respective developers, as these projects are not maintained by Telegram.</p>
|
||||
<p>Ping us on <a href="https://telegram.me/botsupport">@BotSupport</a> if you would like your library to appear on this page.</p>
|
||||
<h4><a class="anchor" name="php" href="#php"><i class="anchor-icon"></i></a>PHP</h4>
|
||||
<ul>
|
||||
<li><p><strong>PHP Telegram Bot</strong>. PHP Telegram Bot based on the official Telegram Bot API.<br><a href="https://github.com/php-telegram-bot/core">https://github.com/php-telegram-bot/core</a></p>
|
||||
|
|
|
@ -86,7 +86,7 @@
|
|||
<p>Increase your productivity by creating bots for <strong>specific tasks</strong> – like converting files, managing chats or fetching today’s forecast. Users can chat directly with bots, or add them to groups and channels to introduce extra features.</p>
|
||||
<div class="blog_video_player_wrap" style="max-width: 600px; margin: 20px auto 20px;">
|
||||
<video class="blog_video_player tl_blog_vid_autoplay" onclick="videoTogglePlay(this)" autoplay loop controls muted poster="/file/464001084/12c1d/eNLdXm8moqA.134736/e28dd8ea6d49eee57d" style="max-width: 600px;" title="" alt="Custom tools">
|
||||
<source src="/file/464001310/11c34/aj8L8Ja6Oa4.3626069.mp4/1fa3a6a1e212051984" type="video/mp4">
|
||||
<source src="/file/464001127/10a99/GC0dSHYQTb0.3621529.mp4/75439f14147e13b6fb" type="video/mp4">
|
||||
</video>
|
||||
</div>
|
||||
|
||||
|
|
|
@ -4,12 +4,10 @@
|
|||
<meta charset="utf-8">
|
||||
<title>Bot API Library Examples</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta property="description" content="If you want to learn more about Telegram bots, start with our Introduction to Bots »
|
||||
Check out the FAQ, if you have questions.…">
|
||||
<meta property="description" content="A full tutorial covering everything from configuring your environment to deploying your finished bot is available here.…">
|
||||
<meta property="og:title" content="Bot API Library Examples">
|
||||
<meta property="og:image" content="">
|
||||
<meta property="og:description" content="If you want to learn more about Telegram bots, start with our Introduction to Bots »
|
||||
Check out the FAQ, if you have questions.…">
|
||||
<meta property="og:description" content="A full tutorial covering everything from configuring your environment to deploying your finished bot is available here.…">
|
||||
<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">
|
||||
|
@ -45,13 +43,10 @@ Check out the FAQ, if you have questions.…">
|
|||
<h1 id="dev_page_title">Bot API Library Examples</h1>
|
||||
|
||||
<div id="dev_page_content"><blockquote>
|
||||
<p>If you want to learn more about Telegram bots, start with our <a href="/bots"><strong>Introduction to Bots »</strong></a><br>Check out the <a href="/bots/faq"><strong>FAQ</strong></a>, if you have questions.</p>
|
||||
</blockquote>
|
||||
<p>A <strong>full tutorial</strong> covering everything from <a href="/bots/tutorial#getting-ready">configuring your environment</a> to <a href="/bots/tutorial#hosting">deploying</a> your finished bot is available <a href="/bots/tutorial">on this page</a>.</p>
|
||||
<p>Below are some libraries and frameworks <strong>developed by the Telegram community</strong> – you should take care to report any bugs you may find to the respective developers, as these projects are not maintained by Telegram.</p>
|
||||
<blockquote>
|
||||
<p>Ping us on <a href="https://telegram.me/botsupport">BotSupport</a> if you would like your library to appear on this page.</p>
|
||||
<p>A <strong>full tutorial</strong> covering everything from <a href="/bots/tutorial#getting-ready">configuring your environment</a> to <a href="/bots/tutorial#hosting">deploying</a> your finished bot is available <a href="/bots/tutorial">here</a>.</p>
|
||||
</blockquote>
|
||||
<p>This page lists some libraries and frameworks <strong>developed by the Telegram community</strong> – you should take care to report any bugs you may find to the respective developers, as these projects are not maintained by Telegram.</p>
|
||||
<p>Ping us on <a href="https://telegram.me/botsupport">@BotSupport</a> if you would like your library to appear on this page.</p>
|
||||
<h4><a class="anchor" name="php" href="#php"><i class="anchor-icon"></i></a>PHP</h4>
|
||||
<ul>
|
||||
<li><p><strong>PHP Telegram Bot</strong>. PHP Telegram Bot based on the official Telegram Bot API.<br><a href="https://github.com/php-telegram-bot/core">https://github.com/php-telegram-bot/core</a></p>
|
||||
|
|
|
@ -4,12 +4,10 @@
|
|||
<meta charset="utf-8">
|
||||
<title>Bot API Library Examples</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<meta property="description" content="If you want to learn more about Telegram bots, start with our Introduction to Bots »
|
||||
Check out the FAQ, if you have questions.…">
|
||||
<meta property="description" content="A full tutorial covering everything from configuring your environment to deploying your finished bot is available here.…">
|
||||
<meta property="og:title" content="Bot API Library Examples">
|
||||
<meta property="og:image" content="">
|
||||
<meta property="og:description" content="If you want to learn more about Telegram bots, start with our Introduction to Bots »
|
||||
Check out the FAQ, if you have questions.…">
|
||||
<meta property="og:description" content="A full tutorial covering everything from configuring your environment to deploying your finished bot is available here.…">
|
||||
<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">
|
||||
|
@ -45,13 +43,10 @@ Check out the FAQ, if you have questions.…">
|
|||
<h1 id="dev_page_title">Bot API Library Examples</h1>
|
||||
|
||||
<div id="dev_page_content"><blockquote>
|
||||
<p>If you want to learn more about Telegram bots, start with our <a href="/bots"><strong>Introduction to Bots »</strong></a><br>Check out the <a href="/bots/faq"><strong>FAQ</strong></a>, if you have questions.</p>
|
||||
</blockquote>
|
||||
<p>A <strong>full tutorial</strong> covering everything from <a href="/bots/tutorial#getting-ready">configuring your environment</a> to <a href="/bots/tutorial#hosting">deploying</a> your finished bot is available <a href="/bots/tutorial">on this page</a>.</p>
|
||||
<p>Below are some libraries and frameworks <strong>developed by the Telegram community</strong> – you should take care to report any bugs you may find to the respective developers, as these projects are not maintained by Telegram.</p>
|
||||
<blockquote>
|
||||
<p>Ping us on <a href="https://telegram.me/botsupport">BotSupport</a> if you would like your library to appear on this page.</p>
|
||||
<p>A <strong>full tutorial</strong> covering everything from <a href="/bots/tutorial#getting-ready">configuring your environment</a> to <a href="/bots/tutorial#hosting">deploying</a> your finished bot is available <a href="/bots/tutorial">here</a>.</p>
|
||||
</blockquote>
|
||||
<p>This page lists some libraries and frameworks <strong>developed by the Telegram community</strong> – you should take care to report any bugs you may find to the respective developers, as these projects are not maintained by Telegram.</p>
|
||||
<p>Ping us on <a href="https://telegram.me/botsupport">@BotSupport</a> if you would like your library to appear on this page.</p>
|
||||
<h4><a class="anchor" name="php" href="#php"><i class="anchor-icon"></i></a>PHP</h4>
|
||||
<ul>
|
||||
<li><p><strong>PHP Telegram Bot</strong>. PHP Telegram Bot based on the official Telegram Bot API.<br><a href="https://github.com/php-telegram-bot/core">https://github.com/php-telegram-bot/core</a></p>
|
||||
|
|
|
@ -81,6 +81,9 @@
|
|||
<img src="/img/tl_card_castle.png" class="blog_side_image"/>
|
||||
</div>
|
||||
|
||||
<blockquote>
|
||||
<p><strong>UPD:</strong> See <a href="https://core.telegram.org/bug-bounty">this page</a> for the latest details about the <a href="https://core.telegram.org/bug-bounty">Telegram Bug Bounty Program</a>.</p>
|
||||
</blockquote>
|
||||
<p>A few days ago we launched a <a href="http://telegram.org/crypto_contest"><strong>contest</strong></a> to improve Telegram's security and are delighted to already have the first results. A <a href="http://habrahabr.ru">Russian IT-community</a> user identified a potentially vulnerable spot in our secret chat implementation. While this would not help him decipher the traffic and win <a href="http://telegram.org/crypto_contest">the contest</a>, his achievement deserves a notice — and a big prize.</p>
|
||||
<blockquote>
|
||||
<p>The habrahabr user <a href="http://habrahabr.ru/users/x7mz/">x7mz</a> had discovered that in case the Telegram server could be seized by a malicious third party, it could send different nonce numbers to each of the clients participating in a secret chat.</p>
|
||||
|
|
|
@ -82,8 +82,8 @@
|
|||
</div>
|
||||
|
||||
<blockquote>
|
||||
<p>This contest is <a href="https://telegram.org/blog/cryptocontest-ends">over</a>, but Telegram's <strong>bug bounty program</strong> is always open.</p>
|
||||
<p><strong>Security researchers</strong> are welcome to submit any issues they find in the Telegram <strong>apps</strong> or <strong>protocol</strong> to us at <strong>security@telegram.org</strong>. All submissions which result in a change of code or configuration are eligible for bounties, ranging from <strong>$500</strong> to <a href="https://telegram.org/blog/crowdsourcing-a-more-secure-future"><strong>$100,000</strong></a> or more, depending on the severity of the issue.</p>
|
||||
<p>This contest is <a href="https://telegram.org/blog/cryptocontest-ends">over</a>, but the <a href="https://core.telegram.org/bug-bounty">Telegram Bug Bounty Program</a> is <strong>always open</strong>.</p>
|
||||
<p><strong>Security researchers</strong> are welcome to submit any issues they find in the Telegram <strong>apps</strong> or <strong>protocol</strong> to us at <strong>security@telegram.org</strong>. All submissions which result in a change of code or configuration are eligible for bounties, ranging from <strong>$100</strong> to <a href="https://telegram.org/blog/crowdsourcing-a-more-secure-future"><strong>$100,000</strong></a> or more, depending on the severity of the issue.</p>
|
||||
</blockquote>
|
||||
<p>Earlier this year we had a <a href="/blog/winter-contest-ends">contest</a> to decipher intercepted Telegram messages, that did not produce a winner. Today we announce a new contest with an easier task and a larger prize — <strong>$300,000</strong> for cracking <a href="https://core.telegram.org/api/end-to-end">Telegram's encryption</a>, and this time contestants can not only monitor traffic, but also act as the Telegram server and use active attacks, which vastly increases their capabilities.</p>
|
||||
<p>In this contest you assume the role of a malicious entity in full control of both the communication lines and the Telegram servers themselves.</p>
|
||||
|
@ -94,7 +94,7 @@
|
|||
<h4><a class="anchor" name="contest-interface" href="#contest-interface"><i class="anchor-icon"></i></a>Contest Interface</h4>
|
||||
<p>In order to facilitate the task, we have created an interface, using which you can act as the server and determine which side gets what data. For more details, please check out the <strong><a href="https://core.telegram.org/contest300K">Cracking Contest Description</a></strong>.</p>
|
||||
<h4><a class="anchor" name="objectives" href="#objectives"><i class="anchor-icon"></i></a>Objectives</h4>
|
||||
<p>In order to confirm that Telegram crypto was indeed cracked and claim your <strong>$300,000</strong>, you‘ll need to send an email to the secret email address that you’ve extracted from one of the messages exchanged by Paul and Nick.</p>
|
||||
<p>In order to confirm that Telegram crypto was indeed cracked and claim your <strong>$300,000</strong>, you'll need to send an email to the secret email address that you've extracted from one of the messages exchanged by Paul and Nick.</p>
|
||||
<p>Your email must contain:<br>- The entire text of the message that contained the secret email.<br>- Session logs for the successful attempt with your user_id.<br>- A detailed explanation of the attack on the protocol.<br>- Your bank account details to receive the $300,000 prize.</p>
|
||||
<p>There is also a bonus objective with an independent prize of <strong>$100,000</strong>.<br><a href="https://core.telegram.org/contest300K#bonus-objective">See full description for details »</a></p>
|
||||
<h4><a class="anchor" name="end-date" href="#end-date"><i class="anchor-icon"></i></a>End Date</h4>
|
||||
|
|
|
@ -81,6 +81,9 @@
|
|||
<img src="/img/tl_card_brick.png" class="blog_side_image"/>
|
||||
</div>
|
||||
|
||||
<blockquote>
|
||||
<p><strong>UPD:</strong> See <a href="https://core.telegram.org/bug-bounty">this page</a> for the latest details about the <a href="https://core.telegram.org/bug-bounty">Telegram Bug Bounty Program</a>.</p>
|
||||
</blockquote>
|
||||
<p>The <a href="/crypto_contest">contest</a> to decrypt intercepted traffic of Telegram produced no winners as of March, 1. As promised, today we are publishing the encryption keys necessary to decrypt the traffic.</p>
|
||||
<pre><code>SECRET CHAT:
|
||||
2e 20 9f 9d 99 c9 fc 8a 3d dc d5 6d 21 26 46 c9 d8 1a 26 f8 ec f7 f2 7e c9 28 65 95 52 dc 1c 21 bb 95 60 b1 d8 5f 94 5f 43 8d 7e 8e 96 fa e6 89 91 a9 90 39 8b df ef 50 22 06 f8 52 80 e6 50 20 62 71 c4 b2 f5 f8 88 4d 83 ae 66 ec fe cd ec 92 26 69 72 5e 85 f9 ea 58 b0 d6 9f 5b 1e b7 68 15 76 5b 12 88 3d 17 f6 62 49 8b 1f 9d 7a 11 94 67 8d d1 ee d6 55 50 d4 51 c0 5e a5 9a 1a eb 8a 8c 7c 44 1b db 96 5a fd cd 85 47 5b f0 8a 1e b8 d6 74 a4 c7 e7 af 19 3f a6 0a ff e5 3b 9f c4 fc ea 59 af f6 72 60 16 6f 40 af 58 95 98 06 0c 22 00 d7 3d be 96 19 56 54 06 74 d2 6b 38 8d c2 a0 97 62 6d e4 10 99 b9 cf d5 0f 56 9d d3 bb 49 86 d5 15 23 86 03 c3 52 67 82 77 5e 53 e9 ba e8 63 58 ed 55 b0 ef ec 69 65 a0 e5 1d e4 b6 6e 5a 3d 5f 9b 9a 20 67 f5 d5 c4 d7 60 14 c6 56 2d 12 1b 0a
|
||||
|
|
|
@ -398,6 +398,9 @@ Check out our Advanced FAQ for more technical information.…">
|
|||
<h4><a class="anchor" name="q-do-i-need-to-trust-telegram-for-this-to-be-secure" href="#q-do-i-need-to-trust-telegram-for-this-to-be-secure"><i class="anchor-icon"></i></a>Q: Do I need to trust Telegram for this to be secure?</h4>
|
||||
<p>When it comes to <a href="#secret-chats">secret chats</a>, you don't — just make sure that the visualized key of your secret chat matches the one in your friend's secret chat settings. <a href="faq#q-what-is-this-39encryption-key-39-thing">More about this below</a>.</p>
|
||||
<h4><a class="anchor" name="q-what-if-my-hacker-friend-says-they-could-decipher-telegram-mes" href="#q-what-if-my-hacker-friend-says-they-could-decipher-telegram-mes"><i class="anchor-icon"></i></a>Q: What if my hacker friend says they could decipher Telegram messages?</h4>
|
||||
<blockquote>
|
||||
<p>See <a href="https://core.telegram.org/bug-bounty">this page</a> for the latest details about the <a href="https://core.telegram.org/bug-bounty">Telegram Bug Bounty Program</a>.</p>
|
||||
</blockquote>
|
||||
<p>Anyone who claims that Telegram messages can be deciphered is welcome to prove that claim in our competition and <a href="https://telegram.org/blog/cryptocontest">win $300,000</a>. You can check out the <a href="https://core.telegram.org/contest300K">Cracking Contest Description</a> to learn more.</p>
|
||||
<p>Any comments on Telegram's security are welcome at <a href="mailto:security@telegram.org">security@telegram.org</a>. All submissions which result in a change of code or configuration are eligible for bounties, ranging from <strong>$100</strong> to <a href="https://telegram.org/blog/crowdsourcing-a-more-secure-future"><strong>$100,000</strong></a> or more, depending on the severity of the issue. Please note that we can not offer bounties for issues that are disclosed to the public before they are fixed.</p>
|
||||
<h4><a class="anchor" name="q-can-telegram-protect-me-against-everything" href="#q-can-telegram-protect-me-against-everything"><i class="anchor-icon"></i></a>Q: Can Telegram protect me against everything?</h4>
|
||||
|
|
Loading…
Reference in a new issue