Finalize
This commit is contained in:
parent
979712dd0c
commit
e15b11644a
GPG Key ID:
8C1BE3B34B230CA7
@ -21,7 +21,7 @@ Full info about a [channel/supergroup](https://core.telegram.org/api/channel)
|
||||
|can\_set\_location|[Bool](../types/Bool.md) | Optional|Can we set the geolocation of this group (for geogroups)|
|
||||
|has\_scheduled|[Bool](../types/Bool.md) | Optional|Whether scheduled messages are available|
|
||||
|can\_view\_stats|[Bool](../types/Bool.md) | Optional|Can the user view [channel statistics](https://core.telegram.org/api/stats) for this channel|
|
||||
|blocked|[Bool](../types/Bool.md) | Optional|
|
||||
|blocked|[Bool](../types/Bool.md) | Optional|Whether any anonymous admin of this supergroup was blocked: if set, you won't receive messages from anonymous group admins in discussion replies via @replies|
|
||||
|id|[int](../types/int.md) | Yes|ID of the channel|
|
||||
|about|[string](../types/string.md) | Yes|Info about the channel|
|
||||
|participants\_count|[int](../types/int.md) | Optional|Number of participants of the channel|
|
||||
|
||||
@ -22,7 +22,7 @@ Represents the rights of an admin in a [channel/supergroup](https://core.telegra
|
||||
|invite\_users|[Bool](../types/Bool.md) | Optional|If set, allows the admin to invite users in the [channel/supergroup](https://core.telegram.org/api/channel)|
|
||||
|pin\_messages|[Bool](../types/Bool.md) | Optional|If set, allows the admin to pin messages in the [channel/supergroup](https://core.telegram.org/api/channel)|
|
||||
|add\_admins|[Bool](../types/Bool.md) | Optional|If set, allows the admin to add other admins with the same (or more limited) permissions in the [channel/supergroup](https://core.telegram.org/api/channel)|
|
||||
|anonymous|[Bool](../types/Bool.md) | Optional|
|
||||
|anonymous|[Bool](../types/Bool.md) | Optional|Whether this admin is anonymous|
|
||||
|
||||
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ Represents the rights of a normal user in a [supergroup/channel/chat](https://co
|
||||
|change\_info|[Bool](../types/Bool.md) | Optional|If set, does not allow any user to change the description of a [supergroup/chat](https://core.telegram.org/api/channel)|
|
||||
|invite\_users|[Bool](../types/Bool.md) | Optional|If set, does not allow any user to invite users in a [supergroup/chat](https://core.telegram.org/api/channel)|
|
||||
|pin\_messages|[Bool](../types/Bool.md) | Optional|If set, does not allow any user to pin messages in a [supergroup/chat](https://core.telegram.org/api/channel)|
|
||||
|until\_date|[int](../types/int.md) | Yes|Validity of said permissions (0 = forever, forever = 2^31-1 for now).|
|
||||
|until\_date|[int](../types/int.md) | Yes|Validity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).|
|
||||
|
||||
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: codeSettings
|
||||
description: Settings used by telegram servers for sending the confirm code.
|
||||
|
||||
Example implementations: [telegram for android](https://github.com/DrKLO/Telegram/blob/master/TMessagesProj/src/main/java/org/telegram/ui/LoginActivity.java), [tdlib](https://github.com/tdlib/td/tree/master/td/telegram/SendCodeHelper.cpp).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: codeSettings
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: decryptedMessageActionSetMessageTTL
|
||||
description: Setting of a message lifetime after reading.
|
||||
|
||||
Upon receiving such message the client shall start deleting of all messages of an encrypted chat **ttl\_seconds** seconds after the messages were read by user.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: decryptedMessageActionSetMessageTTL\_8
|
||||
|
||||
@ -1,13 +1,6 @@
|
||||
---
|
||||
title: maskCoords
|
||||
description: Position on a photo where a mask should be placed
|
||||
|
||||
The `n` position indicates where the mask should be placed:
|
||||
|
||||
- 0 => Relative to the forehead
|
||||
- 1 => Relative to the eyes
|
||||
- 2 => Relative to the mouth
|
||||
- 3 => Relative to the chin
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: maskCoords
|
||||
|
||||
@ -15,7 +15,7 @@ Phone call
|
||||
| Name | Type | Required | Description |
|
||||
|----------|---------------|----------|-------------|
|
||||
|p2p\_allowed|[Bool](../types/Bool.md) | Optional|Whether P2P connection to the other peer is allowed|
|
||||
|video|[Bool](../types/Bool.md) | Optional|
|
||||
|video|[Bool](../types/Bool.md) | Optional|Whether this is a video call|
|
||||
|id|[long](../types/long.md) | Yes|Call ID|
|
||||
|access\_hash|[long](../types/long.md) | Yes|Access hash|
|
||||
|date|[int](../types/int.md) | Yes|Date of creation of the call|
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: restrictionReason
|
||||
description: Restriction reason.
|
||||
|
||||
Contains the reason why access to a certain object must be restricted. Clients are supposed to deny access to the channel if the `platform` field is equal to `all` or to the current platform (`ios`, `android`, `wp`, etc.). Platforms can be concatenated (`ios-android`, `ios-wp`), unknown platforms are to be ignored. The `text` is the error message that should be shown to the user.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: restrictionReason
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: statsPercentValue
|
||||
description: [Channel statistics percentage](https://core.telegram.org/api/stats).
|
||||
Compute the percentage simply by doing `part * total / 100`
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: statsPercentValue
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelPinnedMessage
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelPinnedMessage
|
||||
@ -8,8 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelTooLong
|
||||
description: There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
description: There are new updates in the specified channel, the client must fetch them.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelTooLong
|
||||
@ -8,7 +8,8 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
There are new updates in the specified channel, the client must fetch them.
|
||||
If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -9,7 +9,6 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
New group member.
|
||||
This update is also typically emitted as an [updateNewMessage](updateNewMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -9,7 +9,6 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
A member has left the group.
|
||||
This update is also typically emitted as an [updateNewMessage](updateNewMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChatPinnedMessage
|
||||
description: A message was pinned in a [legacy group](https://core.telegram.org/api/channel)
|
||||
description: A message was pinned in a [legacy group](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChatPinnedMessage
|
||||
@ -8,8 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
A message was pinned in a [legacy group](https://core.telegram.org/api/channel)
|
||||
This update is also typically emitted as an [updateNewMessage](updateNewMessage.md) with [messageService](messageService.md).
|
||||
A message was pinned in a [legacy group](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,11 +1,6 @@
|
||||
---
|
||||
title: updates.channelDifferenceTooLong
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
---
|
||||
@ -17,7 +12,7 @@ redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ Extended user info
|
||||
|phone\_calls\_private|[Bool](../types/Bool.md) | Optional|Whether this user's privacy settings allow you to call him|
|
||||
|can\_pin\_message|[Bool](../types/Bool.md) | Optional|Whether you can pin messages in the chat with this user, you can do this only for a chat with yourself|
|
||||
|has\_scheduled|[Bool](../types/Bool.md) | Optional|Whether scheduled messages are available|
|
||||
|video\_calls\_available|[Bool](../types/Bool.md) | Optional|
|
||||
|video\_calls\_available|[Bool](../types/Bool.md) | Optional|Whether the user can receive video calls|
|
||||
|user|[User](../types/User.md) | Optional|Remaining user info|
|
||||
|about|[string](../types/string.md) | Optional|Bio of the user|
|
||||
|settings|[PeerSettings](../types/PeerSettings.md) | Yes|Peer settings|
|
||||
|
||||
@ -1,10 +1,6 @@
|
||||
---
|
||||
title: auth.acceptLoginToken
|
||||
description: Accept QR code login token, logging in the app that generated it.
|
||||
|
||||
Returns info about the new session.
|
||||
|
||||
For more info, see [login via QR code](https://core.telegram.org/api/qr-login).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_acceptLoginToken.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,9 +1,6 @@
|
||||
---
|
||||
title: auth.exportLoginToken
|
||||
description: Generate a login token, for [login via QR code](https://core.telegram.org/api/qr-login).
|
||||
The generated login token should be encoded using base64url, then shown as a `tg://login?token=base64encodedtoken` URL in the QR code.
|
||||
|
||||
For more info, see [login via QR code](https://core.telegram.org/api/qr-login).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_exportLoginToken.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.importLoginToken
|
||||
description: Login using a redirected login token, generated in case of DC mismatch during [QR code login](https://core.telegram.org/api/qr-login).
|
||||
|
||||
For more info, see [login via QR code](https://core.telegram.org/api/qr-login).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_importLoginToken.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: channels.getParticipants
|
||||
description: Get the participants of a channel
|
||||
description: Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
---
|
||||
@ -9,7 +9,7 @@ redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
|
||||
|
||||
|
||||
Get the participants of a supergroup/channel
|
||||
Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
|
||||
### Parameters:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.addContact
|
||||
description: Add an existing telegram user as contact.
|
||||
|
||||
Use [contacts.importContacts](../methods/contacts.importContacts.md) to add contacts by phone number, without knowing their Telegram ID.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_addContact.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: help.getAppChangelog
|
||||
description: Get changelog of current app.
|
||||
Typically, an [updates](../constructors/updates.md) constructor will be returned, containing one or more [updateServiceNotification](../constructors/updateServiceNotification.md) updates with app-specific changelogs.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/help_getAppChangelog.html
|
||||
---
|
||||
|
||||
@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
* <a href="messages.getSearchCounters.html" name="messages.getSearchCounters">Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters</a>
|
||||
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a channel: channels.getParticipants</a>
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a supergroup/channel: channels.getParticipants</a>
|
||||
|
||||
* <a href="account.getTheme.html" name="account.getTheme">Get theme information: account.getTheme</a>
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: messages.setBotPrecheckoutResults
|
||||
description: Once the user has confirmed their payment and shipping details, the bot receives an [updateBotPrecheckoutQuery](../constructors/updateBotPrecheckoutQuery.md) update.
|
||||
Use this method to respond to such pre-checkout queries.
|
||||
**Note**: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/messages_setBotPrecheckoutResults.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: users.setSecureValueErrors
|
||||
description: Notify the user that the sent [passport](https://core.telegram.org/passport) data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).
|
||||
|
||||
Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/users_setSecureValueErrors.html
|
||||
---
|
||||
|
||||
@ -91,8 +91,7 @@ You can find examples for nearly every MadelineProto function in
|
||||
* [Handling updates (new messages)](https://docs.madelineproto.xyz/docs/UPDATES.html)
|
||||
* [Self-restart on webhosts](https://docs.madelineproto.xyz/docs/UPDATES.html#self-restart-on-webhosts)
|
||||
* [Async Event driven](https://docs.madelineproto.xyz/docs/UPDATES.html#async-event-driven)
|
||||
* [Multi-account: Async Event driven](https://docs.madelineproto.xyz/docs/UPDATES.html#async-event-driven)
|
||||
* [Async Callback](https://docs.madelineproto.xyz/docs/UPDATES.html#async-callback)
|
||||
* [Async Event driven multi-account](https://docs.madelineproto.xyz/docs/UPDATES.html#async-event-driven-multiaccount)
|
||||
* [Noop (default)](https://docs.madelineproto.xyz/docs/UPDATES.html#noop)
|
||||
* [Fetch all updates from the beginning](https://docs.madelineproto.xyz/docs/UPDATES.html#fetch-all-updates-from-the-beginning)
|
||||
* [Settings](https://docs.madelineproto.xyz/docs/SETTINGS.html)
|
||||
@ -357,7 +356,7 @@ You can find examples for nearly every MadelineProto function in
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/account.getTmpPassword.html" name="account.getTmpPassword">Get temporary payment password: account.getTmpPassword</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/channels.getAdminLog.html" name="channels.getAdminLog">Get the admin log of a channel/supergroup: channels.getAdminLog</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/messages.getSearchCounters.html" name="messages.getSearchCounters">Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/channels.getParticipants.html" name="channels.getParticipants">Get the participants of a channel: channels.getParticipants</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/channels.getParticipants.html" name="channels.getParticipants">Get the participants of a supergroup/channel: channels.getParticipants</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/account.getTheme.html" name="account.getTheme">Get theme information: account.getTheme</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/messages.getUnreadMentions.html" name="messages.getUnreadMentions">Get unread messages where we were mentioned: messages.getUnreadMentions</a>
|
||||
* <a href="https://docs.madelineproto.xyz/API_docs/methods/account.getWebAuthorizations.html" name="account.getWebAuthorizations">Get web login widget authorizations: account.getWebAuthorizations</a>
|
||||
|
||||
@ -15,7 +15,7 @@ Indicates a service message
|
||||
| Name | Type | Required | Description |
|
||||
|----------|---------------|----------|-------------|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Yes|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Yes|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|action|[MessageAction](../types/MessageAction.md) | Optional|Event connected with the service message|
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -15,7 +15,7 @@ Indicates a service message
|
||||
| Name | Type | Required | Description |
|
||||
|----------|---------------|----------|-------------|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Yes|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Yes|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|action|[MessageAction](../types/MessageAction.md) | Optional|Event connected with the service message|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -19,7 +19,7 @@ Indicates a service message
|
||||
|mentioned|[Bool](../types/Bool.md) | Optional|Whether we were mentioned in the message|
|
||||
|media\_unread|[Bool](../types/Bool.md) | Optional|Whether the message contains unread media|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Optional|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Optional|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|action|[MessageAction](../types/MessageAction.md) | Optional|Event connected with the service message|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelTooLong
|
||||
description: There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
description: There are new updates in the specified channel, the client must fetch them.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelTooLong
|
||||
@ -8,7 +8,8 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
There are new updates in the specified channel, the client must fetch them.
|
||||
If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,11 +1,6 @@
|
||||
---
|
||||
title: updates.channelDifferenceTooLong
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
---
|
||||
@ -17,7 +12,7 @@ redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
|
||||
|
||||
@ -134,7 +134,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
* <a href="messages.getStickers.html" name="messages.getStickers">Get stickers by emoji: messages.getStickers</a>
|
||||
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a channel: channels.getParticipants</a>
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a supergroup/channel: channels.getParticipants</a>
|
||||
|
||||
* <a href="messages.search.html" name="messages.search">Gets back found messages: messages.search</a>
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: channels.getParticipants
|
||||
description: Get the participants of a channel
|
||||
description: Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
---
|
||||
@ -9,7 +9,7 @@ redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
|
||||
|
||||
|
||||
Get the participants of a channel
|
||||
Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
|
||||
### Parameters:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: help.getAppChangelog
|
||||
description: Get changelog of current app.
|
||||
Typically, an [updates](../constructors/updates.md) constructor will be returned, containing one or more [updateServiceNotification](../constructors/updateServiceNotification.md) updates with app-specific changelogs.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/help_getAppChangelog.html
|
||||
---
|
||||
|
||||
@ -19,7 +19,7 @@ Indicates a service message
|
||||
|mentioned|[Bool](../types/Bool.md) | Optional|Whether we were mentioned in the message|
|
||||
|media\_unread|[Bool](../types/Bool.md) | Optional|Whether the message contains unread media|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Optional|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Optional|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|action|[MessageAction](../types/MessageAction.md) | Optional|Event connected with the service message|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelTooLong
|
||||
description: There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
description: There are new updates in the specified channel, the client must fetch them.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelTooLong
|
||||
@ -8,7 +8,8 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
There are new updates in the specified channel, the client must fetch them.
|
||||
If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,11 +1,6 @@
|
||||
---
|
||||
title: updates.channelDifferenceTooLong
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
---
|
||||
@ -17,7 +12,7 @@ redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
|
||||
|
||||
@ -134,7 +134,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
* <a href="messages.getStickers.html" name="messages.getStickers">Get stickers by emoji: messages.getStickers</a>
|
||||
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a channel: channels.getParticipants</a>
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a supergroup/channel: channels.getParticipants</a>
|
||||
|
||||
* <a href="messages.search.html" name="messages.search">Gets back found messages: messages.search</a>
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: channels.getParticipants
|
||||
description: Get the participants of a channel
|
||||
description: Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
---
|
||||
@ -9,7 +9,7 @@ redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
|
||||
|
||||
|
||||
Get the participants of a channel
|
||||
Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
|
||||
### Parameters:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: help.getAppChangelog
|
||||
description: Get changelog of current app.
|
||||
Typically, an [updates](../constructors/updates.md) constructor will be returned, containing one or more [updateServiceNotification](../constructors/updateServiceNotification.md) updates with app-specific changelogs.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/help_getAppChangelog.html
|
||||
---
|
||||
|
||||
@ -21,7 +21,7 @@ Indicates a service message
|
||||
|silent|[Bool](../types/Bool.md) | Optional|Whether the message is silent|
|
||||
|post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Optional|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Optional|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|reply\_to\_msg\_id|[int](../types/int.md) | Optional|ID of the message this message replies to|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelPinnedMessage
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelPinnedMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelTooLong
|
||||
description: There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
description: There are new updates in the specified channel, the client must fetch them.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelTooLong
|
||||
@ -8,7 +8,8 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
There are new updates in the specified channel, the client must fetch them.
|
||||
If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,11 +1,6 @@
|
||||
---
|
||||
title: updates.channelDifferenceTooLong
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
---
|
||||
@ -17,7 +12,7 @@ redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
|
||||
|
||||
@ -148,7 +148,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
* <a href="messages.getStickers.html" name="messages.getStickers">Get stickers by emoji: messages.getStickers</a>
|
||||
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a channel: channels.getParticipants</a>
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a supergroup/channel: channels.getParticipants</a>
|
||||
|
||||
* <a href="messages.search.html" name="messages.search">Gets back found messages: messages.search</a>
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: channels.getParticipants
|
||||
description: Get the participants of a channel
|
||||
description: Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
---
|
||||
@ -9,7 +9,7 @@ redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
|
||||
|
||||
|
||||
Get the participants of a channel
|
||||
Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
|
||||
### Parameters:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: help.getAppChangelog
|
||||
description: Get changelog of current app.
|
||||
Typically, an [updates](../constructors/updates.md) constructor will be returned, containing one or more [updateServiceNotification](../constructors/updateServiceNotification.md) updates with app-specific changelogs.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/help_getAppChangelog.html
|
||||
---
|
||||
|
||||
@ -20,7 +20,7 @@ Indicates a service message
|
||||
|silent|[Bool](../types/Bool.md) | Optional|Whether the message is silent|
|
||||
|post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Optional|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Optional|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|reply\_to\_msg\_id|[int](../types/int.md) | Optional|ID of the message this message replies to|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelPinnedMessage
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelPinnedMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelTooLong
|
||||
description: There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
description: There are new updates in the specified channel, the client must fetch them.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelTooLong
|
||||
@ -8,7 +8,8 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
There are new updates in the specified channel, the client must fetch them.
|
||||
If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: updateServiceNotification
|
||||
description: A service message for the user.
|
||||
|
||||
The app must show the message to the user upon receiving this update. In case the **popup** parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id `777000` (Telegram Notifications).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateServiceNotification
|
||||
|
||||
@ -1,11 +1,6 @@
|
||||
---
|
||||
title: updates.channelDifferenceTooLong
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
description: The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
---
|
||||
@ -17,7 +12,7 @@ redirect_from: /API_docs/constructors/updates_channelDifferenceTooLong.html
|
||||
The provided `pts + limit < remote pts`. Simply, there are too many updates to be fetched (more than `limit`), the client has to resolve the update gap in one of the following ways:
|
||||
|
||||
1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with [getHistory](../methods/messages.getHistory.md). It is easy to implement, but suddenly disappearing messages looks awful for the user.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, he will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to [getHistory](../methods/messages.getHistory.md). It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of [getHistory](../methods/messages.getHistory.md) and [getMessages](../methods/messages.getMessages.md) must be used to update state of deleted and edited messages left in the memory.
|
||||
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
|
||||
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
|
||||
|
||||
|
||||
@ -152,7 +152,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
* <a href="messages.getStickers.html" name="messages.getStickers">Get stickers by emoji: messages.getStickers</a>
|
||||
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a channel: channels.getParticipants</a>
|
||||
* <a href="channels.getParticipants.html" name="channels.getParticipants">Get the participants of a supergroup/channel: channels.getParticipants</a>
|
||||
|
||||
* <a href="messages.search.html" name="messages.search">Gets back found messages: messages.search</a>
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.bindTempAuthKey
|
||||
description: Binds a temporary authorization key `temp_auth_key_id` to the permanent authorization key `perm_auth_key_id`. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.
|
||||
|
||||
For more information, see [Perfect Forward Secrecy](https://core.telegram.org/api/pfs).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_bindTempAuthKey.html
|
||||
---
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: auth.resetAuthorizations
|
||||
description: Terminates all user's authorized sessions except for the current one.
|
||||
|
||||
After calling this method it is necessary to reregister the current device using the method [account.registerDevice](../methods/account.registerDevice.md)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/auth_resetAuthorizations.html
|
||||
---
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: channels.getParticipants
|
||||
description: Get the participants of a channel
|
||||
description: Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
---
|
||||
@ -9,7 +9,7 @@ redirect_from: /API_docs/methods/channels_getParticipants.html
|
||||
|
||||
|
||||
|
||||
Get the participants of a channel
|
||||
Get the participants of a [supergroup/channel](https://core.telegram.org/api/channel)
|
||||
|
||||
### Parameters:
|
||||
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
---
|
||||
title: contacts.importContacts
|
||||
description: Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
|
||||
|
||||
Use [contacts.addContact](../methods/contacts.addContact.md) to add Telegram contacts without actually using their phone number.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/contacts_importContacts.html
|
||||
---
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: help.getAppChangelog
|
||||
description: Get changelog of current app.
|
||||
Typically, an [updates](../constructors/updates.md) constructor will be returned, containing one or more [updateServiceNotification](../constructors/updateServiceNotification.md) updates with app-specific changelogs.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
redirect_from: /API_docs/methods/help_getAppChangelog.html
|
||||
---
|
||||
|
||||
@ -20,7 +20,7 @@ Indicates a service message
|
||||
|silent|[Bool](../types/Bool.md) | Optional|Whether the message is silent|
|
||||
|post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post|
|
||||
|id|[int](../types/int.md) | Yes|Message ID|
|
||||
|from\_id|[int](../types/int.md) | Optional|Id of te sender of the message|
|
||||
|from\_id|[int](../types/int.md) | Optional|ID of the sender of this message|
|
||||
|to\_id|[Peer](../types/Peer.md) | Yes|ID of the destination of the message|
|
||||
|reply\_to\_msg\_id|[int](../types/int.md) | Optional|ID of the message this message replies to|
|
||||
|date|[int](../types/int.md) | Yes|Message date|
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: stickerPack
|
||||
description: A stickerpack is a group of stickers associated to the same emoji.
|
||||
It is **not** a sticker pack the way it is usually intended, you may be looking for a [StickerSet](../types/StickerSet.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: stickerPack
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelPinnedMessage
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
description: A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelPinnedMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel).
|
||||
A message was pinned in a [channel/supergroup](https://core.telegram.org/api/channel). This update is also typically emitted as an [updateNewChannelMessage](updateNewChannelMessage.md) with [messageService](messageService.md).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateChannelTooLong
|
||||
description: There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
description: There are new updates in the specified channel, the client must fetch them.
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateChannelTooLong
|
||||
@ -8,7 +8,8 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
There are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
|
||||
There are new updates in the specified channel, the client must fetch them.
|
||||
If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: updateNewMessage
|
||||
description: New message.
|
||||
description: New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
---
|
||||
# Constructor: updateNewMessage
|
||||
@ -8,7 +8,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
|
||||
|
||||
|
||||
|
||||
New message.
|
||||
New message in a private chat or in a [legacy group](https://core.telegram.org/api/channel).
|
||||
|
||||
### Attributes:
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user