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 2022-09-09 16:04:25 +00:00
parent caf95e2d54
commit 6c0c5a87f5
5 changed files with 11 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -125,7 +125,7 @@ Also introducing new <a href="https://telegram.org/blog/custom-emoji#privacy-set
<a href="/constructor/messageEntitySpoiler">messageEntitySpoiler</a>#32ca960f offset:<a href="/type/int">int</a> length:<a href="/type/int">int</a> = <a href="/type/MessageEntity">MessageEntity</a>;
<a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a>#c8cf05f8 offset:<a href="/type/int">int</a> length:<a href="/type/int">int</a> document_id:<a href="/type/long">long</a> = <a href="/type/MessageEntity">MessageEntity</a>;<br></code></pre></div>
<h3><a class="anchor" href="#layer-143" id="layer-143" name="layer-143"><i class="anchor-icon"></i></a><a href="/schema?layer=143">Layer 143</a></h3>
<p><a href="/api/premium">Telegram Premium</a>, <a href="/api/transcribe">voice message transcription</a>, <a href="/api/links#invoice-links">invoices</a>, bot description photos/animations, and <a href="/api/bots/attach">attachment menu</a> improvements.<br>
<p><a href="/api/premium">Telegram Premium</a>, <a href="/api/transcribe">voice message transcription</a>, <a href="/api/links#invoice-links">invoices</a>, bot description photos/animations, recurring <a href="/api/payments">payments</a> and <a href="/api/bots/attach">attachment menu</a> improvements.<br>
Also, discussion group admins can now <a href="/api/discussion#requiring-users-to-join-the-group">require users to join</a> before commenting.</p>
<p>The main and E2E schemes were also modified to eventually support uploading and downloading files bigger than 4GB: the current supported maximum filesize is dynamically specified, and can be fetched from the new <a href="/api/config#upload-max-fileparts-default">upload_max_fileparts_default »</a> and <a href="/api/config#upload-max-fileparts-premium">upload_max_fileparts_premium »</a> app configuration fields.</p>
<h4><a class="anchor" href="#schema-changes" id="schema-changes" name="schema-changes"><i class="anchor-icon"></i></a>Schema changes</h4>
@ -138,7 +138,7 @@ Also, discussion group admins can now <a href="/api/discussion#requiring-users-t
<li>Added <a href="/method/messages.rateTranscribedAudio">messages.rateTranscribedAudio</a> - Rate <a href="/api/transcribe">transcribed voice message</a></li>
<li>Added <a href="/method/payments.assignAppStoreTransaction">payments.assignAppStoreTransaction</a> - Informs server about a purchase made through the App Store: for official applications only.</li>
<li>Added <a href="/method/payments.assignPlayMarketTransaction">payments.assignPlayMarketTransaction</a> - Informs server about a purchase made through the Play Store: for official applications only.</li>
<li>Added <a href="/method/payments.canPurchasePremium">payments.canPurchasePremium</a> - Checks whether Telegram Premium purchase is possible. Must be called before in-store Premium purchase.</li>
<li>Added <a href="/method/payments.canPurchasePremium">payments.canPurchasePremium</a> - Checks whether Telegram Premium purchase is possible. Must be called before in-store Premium purchase, official apps only.</li>
<li>Added <a href="/method/help.getPremiumPromo">help.getPremiumPromo</a> - Get Telegram Premim promotion information</li>
</ul>
<h5><a class="anchor" href="#changed-methods" id="changed-methods" name="changed-methods"><i class="anchor-icon"></i></a>Changed Methods</h5>

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

@ -133,7 +133,8 @@ The the first button of the keyboard will always be a <a href="/constructor/keyb
</ul>
<p>The returned form will contain fields that should be passed to the payment provider along with the full <a href="/constructor/invoice">invoice</a>.
The payment form also contains info about previously saved payment credentials and order information (name, phone number, email, shipping address &amp; so on).</p>
<p>The full <a href="/constructor/invoice">invoice</a> contains info about the information required for the order, the price and the currency, and whether this is a <code>test</code> order.</p>
<p>The full <a href="/constructor/invoice">invoice</a> contains info about the information required for the order, the price and the currency, and whether this is a <code>test</code> order.
The <code>recurring</code> flag will be set for recurring payments, and <code>recurring_terms_url</code> will link to the terms of service of the recurring payment: the user must read and accept them before continuing. </p>
<h4><a class="anchor" href="#23-verifying-information" id="23-verifying-information" name="23-verifying-information"><i class="anchor-icon"></i></a>2.3 Verifying information</h4>
<pre><code><a href='/constructor/invoice'>invoice</a>#3e85a91b flags:<a href='/type/%23'>#</a> test:flags.0?<a href='/constructor/true'>true</a> name_requested:flags.1?<a href='/constructor/true'>true</a> phone_requested:flags.2?<a href='/constructor/true'>true</a> email_requested:flags.3?<a href='/constructor/true'>true</a> shipping_address_requested:flags.4?<a href='/constructor/true'>true</a> flexible:flags.5?<a href='/constructor/true'>true</a> phone_to_provider:flags.6?<a href='/constructor/true'>true</a> email_to_provider:flags.7?<a href='/constructor/true'>true</a> recurring:flags.9?<a href='/constructor/true'>true</a> currency:<a href='/type/string'>string</a> prices:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/LabeledPrice'>LabeledPrice</a>&gt; max_tip_amount:flags.8?<a href='/type/long'>long</a> suggested_tip_amounts:flags.8?<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/long'>long</a>&gt; recurring_terms_url:flags.9?<a href='/type/string'>string</a> = <a href='/type/Invoice'>Invoice</a>;
@ -314,7 +315,9 @@ The bot must reply using <a href="/method/messages.setBotPrecheckoutResults">mes
Clients should treat invoice messages with a <code>receipt_msg_id</code> field as receipt messages, <strong>locally</strong> modifying the label of the <a href="/constructor/keyboardButtonBuy">keyboardButtonBuy</a> button to a localized version of the word <code>Receipt</code>.
From this point, clicking on the <code>Receipt</code> button should trigger a call to <a href="/method/payments.getPaymentReceipt">payments.getPaymentReceipt</a>, providing the <code>receipt_msg_id</code> to the <code>msg_id</code> field, which will return info about the transaction.</p>
<p>The payment will also generate one service message of type <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> or <a href="/constructor/messageActionPaymentSentMe">messageActionPaymentSentMe</a>, replying to the invoice.
For bots, the service message will be of type <a href="/constructor/messageActionPaymentSentMe">messageActionPaymentSentMe</a>, for users it will be a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a>.</p>
For bots, the service message will be of type <a href="/constructor/messageActionPaymentSentMe">messageActionPaymentSentMe</a>, for users it will be a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a>.<br>
The <code>recurring_init</code> flag will be set if this payment also enables future recurring payments.<br>
Further recurring payments will automatically send <a href="/constructor/messageActionPaymentSentMe">messageActionPaymentSentMe</a> and <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> messages with the <code>recurring_used</code> flag set. </p>
<pre><code><a href='/constructor/messageActionPaymentSentMe'>messageActionPaymentSentMe</a>#8f31b327 flags:<a href='/type/%23'>#</a> recurring_init:flags.2?<a href='/constructor/true'>true</a> recurring_used:flags.3?<a href='/constructor/true'>true</a> currency:<a href='/type/string'>string</a> total_amount:<a href='/type/long'>long</a> payload:<a href='/type/bytes'>bytes</a> info:flags.0?<a href='/type/PaymentRequestedInfo'>PaymentRequestedInfo</a> shipping_option_id:flags.1?<a href='/type/string'>string</a> charge:<a href='/type/PaymentCharge'>PaymentCharge</a> = <a href='/type/MessageAction'>MessageAction</a>;
<a href='/constructor/messageActionPaymentSent'>messageActionPaymentSent</a>#96163f56 flags:<a href='/type/%23'>#</a> recurring_init:flags.2?<a href='/constructor/true'>true</a> recurring_used:flags.3?<a href='/constructor/true'>true</a> currency:<a href='/type/string'>string</a> total_amount:<a href='/type/long'>long</a> invoice_slug:flags.0?<a href='/type/string'>string</a> = <a href='/type/MessageAction'>MessageAction</a>;</code></pre></div>

4
data/web/corefork.telegram.org/api/premium.html
View file

@ -149,8 +149,8 @@ Then, when the user clicks on the subscribe button in the sent invoice, follow t
---functions---
<a href='/method/users.getFullUser'>users.getFullUser</a>#b60f5918 id:<a href='/type/InputUser'>InputUser</a> = <a href='/type/users.UserFull'>users.UserFull</a>;</code></pre>
<p>If after calling <a href="/method/users.getFullUser">users.getFullUser</a> the resulting <a href="/constructor/userFull">userFull</a> constructor has one or more <a href="/constructor/premiumGiftOption">premiumGiftOptions</a> in the <code>premium_gifts</code> field, we can gift a Telegram Premium subscription to this user. </p>
<p>The <a href="/constructor/premiumGiftOption">premiumGiftOption</a> constructors contain an ordered list of Premium gift offers with discounts over the base price: to process the gift payment open the <a href="/api/links">deep link</a> contained in the <code>bot_url</code> field. </p>
<p>If after calling <a href="/method/users.getFullUser">users.getFullUser</a> the resulting <a href="/constructor/userFull">userFull</a> constructor has one or more <a href="/constructor/premiumGiftOption">premiumGiftOptions</a> in the <code>premium_gifts</code> field, we can gift a non-recurring Telegram Premium subscription to this user. </p>
<p>The <a href="/constructor/premiumGiftOption">premiumGiftOption</a> constructors contain an ordered list of Premium gift offers with discounts over the base price, according to the subscription duration: to process the gift payment open the <a href="/api/links">deep link</a> contained in the <code>bot_url</code> field. </p>
<p>Once the payment is successfully processed, the user to which the gift was sent will automatically receive a <a href="/constructor/messageService">messageService</a> from the user that sent the gift, containing a <a href="/constructor/messageActionGiftPremium">messageActionGiftPremium</a> constructor with further info about the price and duration of the gifted Telegram Premium subscription.<br>
Clients should display this message, along with a sticker from the <a href="/constructor/inputStickerSetPremiumGifts">inputStickerSetPremiumGifts</a> <a href="/api/stickers">stickerset</a>: here's an <a href="https://telegram.org/blog/custom-emoji#gifting-telegram-premium">example</a>. </p>
<h3><a class="anchor" href="#blocked-telegram-premium" id="blocked-telegram-premium" name="blocked-telegram-premium"><i class="anchor-icon"></i></a>Blocked Telegram Premium</h3>

2
data/web/corefork.telegram.org/method/payments.canPurchasePremium
View file

@ -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="/methods" >All Methods</a></li><i class="icon icon-breadcrumb-divider"></i><li><a href="/method/payments.canPurchasePremium" >payments.canPurchasePremium</a></li></ul></div>
<h1 id="dev_page_title">payments.canPurchasePremium</h1>
<div id="dev_page_content"><p>Checks whether Telegram Premium purchase is possible. Must be called before in-store Premium purchase.</p>
<div id="dev_page_content"><p>Checks whether Telegram Premium purchase is possible. Must be called before in-store Premium purchase, official apps only.</p>
<p><div class="clearfix">
<ul class="dev_layer_select slightly-pull-right nav nav-pills">
<li class="dropdown">

2
data/web/corefork.telegram.org/type/Bool.html
View file

@ -692,7 +692,7 @@
</tr>
<tr>
<td><a href="/method/payments.canPurchasePremium">payments.canPurchasePremium</a></td>
<td>Checks whether Telegram Premium purchase is possible. Must be called before in-store Premium purchase.</td>
<td>Checks whether Telegram Premium purchase is possible. Must be called before in-store Premium purchase, official apps only.</td>
</tr>
</tbody>
</table></div>