OpenSource/telegram-crawler
OpenSource/telegram-crawler
1
0
Fork 0
mirror of https://github.com/MarshalX/telegram-crawler.git synced 2024-12-29 15:59:13 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update content of files

Browse source
This commit is contained in:
GitHub Action 2022-10-15 15:40:44 +00:00
parent e4555f200e
commit 80cd49f288
3 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
data/web/corefork.telegram.org/api/push-updates.html
View file

@ -48,7 +48,7 @@
<p>To be able to send APNS notifications to Apple servers or GCM notifications to Google servers, application certificates (APNS) or an application key (GCM) must be specified in the <a href="/myapp">application settings</a>.</p>
<h3><a class="anchor" href="#subscribing-to-notifications" id="subscribing-to-notifications" name="subscribing-to-notifications"><i class="anchor-icon"></i></a>Subscribing to notifications</h3>
<p>To subscribe to notifications, the client must invoke the <a href="/method/account.registerDevice">account.registerDevice</a> query, passing in <strong>token_type</strong> and <strong>token</strong> as parameters that identify the current device. It is useful to repeat this query at least once every 24 hours or when restarting the application. Use <a href="/method/account.unregisterDevice">account.unregisterDevice</a> to unsubscribe.</p>
<p>The following modes are supported:</p>
<p>The following <strong>token_type</strong>s are supported:</p>
<ul>
<li><code>1</code> - APNS (device token for apple push)</li>
<li><code>2</code> - FCM (firebase token for google firebase)</li>

4
data/web/corefork.telegram.org/method/account.registerDevice
View file

@ -82,12 +82,12 @@
<tr>
<td><strong>token_type</strong></td>
<td style="text-align: center;"><a href="/type/int">int</a></td>
<td>Device token type.<br><strong>Possible values</strong>:<br><code>1</code> - APNS (device token for apple push)<br><code>2</code> - FCM (firebase token for google firebase)<br><code>3</code> - MPNS (channel URI for microsoft push)<br><code>4</code> - Simple push (endpoint for firefox's simple push API)<br><code>5</code> - Ubuntu phone (token for ubuntu push)<br><code>6</code> - Blackberry (token for blackberry push)<br><code>7</code> - Unused<br><code>8</code> - WNS (windows push)<br><code>9</code> - APNS VoIP (token for apple push VoIP)<br><code>10</code> - Web push (web push, see below)<br><code>11</code> - MPNS VoIP (token for microsoft push VoIP)<br><code>12</code> - Tizen (token for tizen push)<br><br>For <code>10</code> web push, the token must be a JSON-encoded object containing the keys described in <a href="/api/push-updates">PUSH updates</a></td>
<td>Device token type, see <a href="/api/push-updates#subscribing-to-notifications">PUSH updates</a> for the possible values.</td>
</tr>
<tr>
<td><strong>token</strong></td>
<td style="text-align: center;"><a href="/type/string">string</a></td>
<td>Device token</td>
<td>Device token, see <a href="/api/push-updates#subscribing-to-notifications">PUSH updates</a> for the possible values.</td>
</tr>
<tr>
<td><strong>app_sandbox</strong></td>

4
data/web/corefork.telegram.org/method/account.unregisterDevice
View file

@ -72,12 +72,12 @@
<tr>
<td><strong>token_type</strong></td>
<td style="text-align: center;"><a href="/type/int">int</a></td>
<td>Device token type.<br><strong>Possible values</strong>:<br><code>1</code> - APNS (device token for apple push)<br><code>2</code> - FCM (firebase token for google firebase)<br><code>3</code> - MPNS (channel URI for microsoft push)<br><code>4</code> - Simple push (endpoint for firefox's simple push API)<br><code>5</code> - Ubuntu phone (token for ubuntu push)<br><code>6</code> - Blackberry (token for blackberry push)<br><code>7</code> - Unused<br><code>8</code> - WNS (windows push)<br><code>9</code> - APNS VoIP (token for apple push VoIP)<br><code>10</code> - Web push (web push, see below)<br><code>11</code> - MPNS VoIP (token for microsoft push VoIP)<br><code>12</code> - Tizen (token for tizen push)<br><br>For <code>10</code> web push, the token must be a JSON-encoded object containing the keys described in <a href="/api/push-updates">PUSH updates</a></td>
<td>Device token type, see <a href="/api/push-updates#subscribing-to-notifications">PUSH updates</a> for the possible values.</td>
</tr>
<tr>
<td><strong>token</strong></td>
<td style="text-align: center;"><a href="/type/string">string</a></td>
<td>Device token</td>
<td>Device token, see <a href="/api/push-updates#subscribing-to-notifications">PUSH updates</a> for the possible values.</td>
</tr>
<tr>
<td><strong>other_uids</strong></td>