diff --git a/docs/API_docs/constructors/channelFull.md b/docs/API_docs/constructors/channelFull.md index ad57fd00..30702727 100644 --- a/docs/API_docs/constructors/channelFull.md +++ b/docs/API_docs/constructors/channelFull.md @@ -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| diff --git a/docs/API_docs/constructors/chatAdminRights.md b/docs/API_docs/constructors/chatAdminRights.md index b0540e84..e46ad17c 100644 --- a/docs/API_docs/constructors/chatAdminRights.md +++ b/docs/API_docs/constructors/chatAdminRights.md @@ -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| diff --git a/docs/API_docs/constructors/chatBannedRights.md b/docs/API_docs/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/docs/API_docs/constructors/chatBannedRights.md +++ b/docs/API_docs/constructors/chatBannedRights.md @@ -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).| diff --git a/docs/API_docs/constructors/codeSettings.md b/docs/API_docs/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/docs/API_docs/constructors/codeSettings.md +++ b/docs/API_docs/constructors/codeSettings.md @@ -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 diff --git a/docs/API_docs/constructors/decryptedMessageActionSetMessageTTL_8.md b/docs/API_docs/constructors/decryptedMessageActionSetMessageTTL_8.md index 9101797f..72761233 100644 --- a/docs/API_docs/constructors/decryptedMessageActionSetMessageTTL_8.md +++ b/docs/API_docs/constructors/decryptedMessageActionSetMessageTTL_8.md @@ -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 diff --git a/docs/API_docs/constructors/maskCoords.md b/docs/API_docs/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/docs/API_docs/constructors/maskCoords.md +++ b/docs/API_docs/constructors/maskCoords.md @@ -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 diff --git a/docs/API_docs/constructors/phoneCall.md b/docs/API_docs/constructors/phoneCall.md index 883d375d..93d5ff15 100644 --- a/docs/API_docs/constructors/phoneCall.md +++ b/docs/API_docs/constructors/phoneCall.md @@ -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| diff --git a/docs/API_docs/constructors/restrictionReason.md b/docs/API_docs/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/docs/API_docs/constructors/restrictionReason.md +++ b/docs/API_docs/constructors/restrictionReason.md @@ -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 diff --git a/docs/API_docs/constructors/statsPercentValue.md b/docs/API_docs/constructors/statsPercentValue.md index 1f5386b8..507591e2 100644 --- a/docs/API_docs/constructors/statsPercentValue.md +++ b/docs/API_docs/constructors/statsPercentValue.md @@ -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 diff --git a/docs/API_docs/constructors/stickerPack.md b/docs/API_docs/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/docs/API_docs/constructors/stickerPack.md +++ b/docs/API_docs/constructors/stickerPack.md @@ -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 diff --git a/docs/API_docs/constructors/updateChannelPinnedMessage.md b/docs/API_docs/constructors/updateChannelPinnedMessage.md index 7897b806..8d94d001 100644 --- a/docs/API_docs/constructors/updateChannelPinnedMessage.md +++ b/docs/API_docs/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/docs/API_docs/constructors/updateChannelTooLong.md b/docs/API_docs/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/docs/API_docs/constructors/updateChannelTooLong.md +++ b/docs/API_docs/constructors/updateChannelTooLong.md @@ -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: diff --git a/docs/API_docs/constructors/updateChatParticipantAdd.md b/docs/API_docs/constructors/updateChatParticipantAdd.md index 559d6361..baaef950 100644 --- a/docs/API_docs/constructors/updateChatParticipantAdd.md +++ b/docs/API_docs/constructors/updateChatParticipantAdd.md @@ -8,8 +8,7 @@ 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). +New group member. ### Attributes: diff --git a/docs/API_docs/constructors/updateChatParticipantDelete.md b/docs/API_docs/constructors/updateChatParticipantDelete.md index b57882e0..31872336 100644 --- a/docs/API_docs/constructors/updateChatParticipantDelete.md +++ b/docs/API_docs/constructors/updateChatParticipantDelete.md @@ -8,8 +8,7 @@ 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). +A member has left the group. ### Attributes: diff --git a/docs/API_docs/constructors/updateChatPinnedMessage.md b/docs/API_docs/constructors/updateChatPinnedMessage.md index b678f413..9bc1b6fd 100644 --- a/docs/API_docs/constructors/updateChatPinnedMessage.md +++ b/docs/API_docs/constructors/updateChatPinnedMessage.md @@ -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: diff --git a/docs/API_docs/constructors/updateNewMessage.md b/docs/API_docs/constructors/updateNewMessage.md index abb4eda2..e144485d 100644 --- a/docs/API_docs/constructors/updateNewMessage.md +++ b/docs/API_docs/constructors/updateNewMessage.md @@ -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 diff --git a/docs/API_docs/constructors/updateServiceNotification.md b/docs/API_docs/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/docs/API_docs/constructors/updateServiceNotification.md +++ b/docs/API_docs/constructors/updateServiceNotification.md @@ -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 diff --git a/docs/API_docs/constructors/updates.channelDifferenceTooLong.md b/docs/API_docs/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/docs/API_docs/constructors/updates.channelDifferenceTooLong.md +++ b/docs/API_docs/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/docs/API_docs/constructors/userFull.md b/docs/API_docs/constructors/userFull.md index 675a671c..6dcb555e 100644 --- a/docs/API_docs/constructors/userFull.md +++ b/docs/API_docs/constructors/userFull.md @@ -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| diff --git a/docs/API_docs/methods/auth.acceptLoginToken.md b/docs/API_docs/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/docs/API_docs/methods/auth.acceptLoginToken.md +++ b/docs/API_docs/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/docs/API_docs/methods/auth.bindTempAuthKey.md b/docs/API_docs/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/docs/API_docs/methods/auth.bindTempAuthKey.md +++ b/docs/API_docs/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/docs/API_docs/methods/auth.exportLoginToken.md b/docs/API_docs/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/docs/API_docs/methods/auth.exportLoginToken.md +++ b/docs/API_docs/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/docs/API_docs/methods/auth.importLoginToken.md b/docs/API_docs/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/docs/API_docs/methods/auth.importLoginToken.md +++ b/docs/API_docs/methods/auth.importLoginToken.md @@ -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 --- diff --git a/docs/API_docs/methods/auth.resetAuthorizations.md b/docs/API_docs/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/docs/API_docs/methods/auth.resetAuthorizations.md +++ b/docs/API_docs/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/docs/API_docs/methods/channels.getParticipants.md b/docs/API_docs/methods/channels.getParticipants.md index b4d66989..7a33d393 100644 --- a/docs/API_docs/methods/channels.getParticipants.md +++ b/docs/API_docs/methods/channels.getParticipants.md @@ -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: diff --git a/docs/API_docs/methods/contacts.addContact.md b/docs/API_docs/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/docs/API_docs/methods/contacts.addContact.md +++ b/docs/API_docs/methods/contacts.addContact.md @@ -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 --- diff --git a/docs/API_docs/methods/contacts.importContacts.md b/docs/API_docs/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/docs/API_docs/methods/contacts.importContacts.md +++ b/docs/API_docs/methods/contacts.importContacts.md @@ -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 --- diff --git a/docs/API_docs/methods/help.getAppChangelog.md b/docs/API_docs/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/docs/API_docs/methods/help.getAppChangelog.md +++ b/docs/API_docs/methods/help.getAppChangelog.md @@ -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 --- diff --git a/docs/API_docs/methods/index.md b/docs/API_docs/methods/index.md index 50cb8bef..ef251bfa 100644 --- a/docs/API_docs/methods/index.md +++ b/docs/API_docs/methods/index.md @@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/docs/API_docs/methods/messages.setBotPrecheckoutResults.md b/docs/API_docs/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/docs/API_docs/methods/messages.setBotPrecheckoutResults.md +++ b/docs/API_docs/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/docs/API_docs/methods/users.setSecureValueErrors.md b/docs/API_docs/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/docs/API_docs/methods/users.setSecureValueErrors.md +++ b/docs/API_docs/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/docs/index.md b/docs/index.md index f04e0013..1d9af97c 100644 --- a/docs/index.md +++ b/docs/index.md @@ -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 * Get temporary payment password: account.getTmpPassword * Get the admin log of a channel/supergroup: channels.getAdminLog * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters - * Get the participants of a channel: channels.getParticipants + * Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme * Get unread messages where we were mentioned: messages.getUnreadMentions * Get web login widget authorizations: account.getWebAuthorizations diff --git a/old_docs/API_docs_v0/constructors/messageService.md b/old_docs/API_docs_v0/constructors/messageService.md index 7ef0f312..700af4f1 100644 --- a/old_docs/API_docs_v0/constructors/messageService.md +++ b/old_docs/API_docs_v0/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v0/constructors/updateNewMessage.md b/old_docs/API_docs_v0/constructors/updateNewMessage.md index aa9fc679..cbf63f36 100644 --- a/old_docs/API_docs_v0/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v0/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v0/constructors/updateServiceNotification.md b/old_docs/API_docs_v0/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v0/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v0/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v0/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v0/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v0/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v0/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v0/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v0/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v0/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v0/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v0/methods/contacts.importContacts.md b/old_docs/API_docs_v0/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v0/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v0/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v1/constructors/messageService.md b/old_docs/API_docs_v1/constructors/messageService.md index 7ef0f312..700af4f1 100644 --- a/old_docs/API_docs_v1/constructors/messageService.md +++ b/old_docs/API_docs_v1/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v1/constructors/stickerPack.md b/old_docs/API_docs_v1/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v1/constructors/stickerPack.md +++ b/old_docs/API_docs_v1/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v1/constructors/updateNewMessage.md b/old_docs/API_docs_v1/constructors/updateNewMessage.md index aa9fc679..cbf63f36 100644 --- a/old_docs/API_docs_v1/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v1/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v1/constructors/updateServiceNotification.md b/old_docs/API_docs_v1/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v1/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v1/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v1/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v1/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v1/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v1/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v1/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v1/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v1/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v1/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v1/methods/contacts.importContacts.md b/old_docs/API_docs_v1/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v1/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v1/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v10/constructors/messageService.md b/old_docs/API_docs_v10/constructors/messageService.md index c0d05fe7..3d7c59f4 100644 --- a/old_docs/API_docs_v10/constructors/messageService.md +++ b/old_docs/API_docs_v10/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v10/constructors/stickerPack.md b/old_docs/API_docs_v10/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v10/constructors/stickerPack.md +++ b/old_docs/API_docs_v10/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v10/constructors/updateChannelTooLong.md b/old_docs/API_docs_v10/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v10/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v10/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v10/constructors/updateNewMessage.md b/old_docs/API_docs_v10/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v10/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v10/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v10/constructors/updateServiceNotification.md b/old_docs/API_docs_v10/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v10/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v10/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v10/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v10/constructors/updates.channelDifferenceTooLong.md index ac2778d2..b56d43c3 100644 --- a/old_docs/API_docs_v10/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v10/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v10/methods/README.md b/old_docs/API_docs_v10/methods/README.md index a48d56bf..0e4613c9 100644 --- a/old_docs/API_docs_v10/methods/README.md +++ b/old_docs/API_docs_v10/methods/README.md @@ -134,7 +134,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v10/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v10/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v10/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v10/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v10/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v10/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v10/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v10/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v10/methods/channels.getParticipants.md b/old_docs/API_docs_v10/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v10/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v10/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v10/methods/contacts.importContacts.md b/old_docs/API_docs_v10/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v10/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v10/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v10/methods/help.getAppChangelog.md b/old_docs/API_docs_v10/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v10/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v10/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v11/constructors/messageService.md b/old_docs/API_docs_v11/constructors/messageService.md index c0d05fe7..3d7c59f4 100644 --- a/old_docs/API_docs_v11/constructors/messageService.md +++ b/old_docs/API_docs_v11/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v11/constructors/stickerPack.md b/old_docs/API_docs_v11/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v11/constructors/stickerPack.md +++ b/old_docs/API_docs_v11/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v11/constructors/updateChannelTooLong.md b/old_docs/API_docs_v11/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v11/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v11/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v11/constructors/updateNewMessage.md b/old_docs/API_docs_v11/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v11/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v11/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v11/constructors/updateServiceNotification.md b/old_docs/API_docs_v11/constructors/updateServiceNotification.md index 67ac976f..fd890fe3 100644 --- a/old_docs/API_docs_v11/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v11/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v11/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v11/constructors/updates.channelDifferenceTooLong.md index 5bf49076..3289b0dd 100644 --- a/old_docs/API_docs_v11/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v11/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v11/methods/README.md b/old_docs/API_docs_v11/methods/README.md index a48d56bf..0e4613c9 100644 --- a/old_docs/API_docs_v11/methods/README.md +++ b/old_docs/API_docs_v11/methods/README.md @@ -134,7 +134,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v11/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v11/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v11/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v11/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v11/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v11/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v11/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v11/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v11/methods/channels.getParticipants.md b/old_docs/API_docs_v11/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v11/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v11/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v11/methods/contacts.importContacts.md b/old_docs/API_docs_v11/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v11/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v11/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v11/methods/help.getAppChangelog.md b/old_docs/API_docs_v11/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v11/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v11/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v12/constructors/messageService.md b/old_docs/API_docs_v12/constructors/messageService.md index e8f5a930..ddbe4997 100644 --- a/old_docs/API_docs_v12/constructors/messageService.md +++ b/old_docs/API_docs_v12/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v12/constructors/stickerPack.md b/old_docs/API_docs_v12/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v12/constructors/stickerPack.md +++ b/old_docs/API_docs_v12/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v12/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v12/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v12/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v12/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v12/constructors/updateChannelTooLong.md b/old_docs/API_docs_v12/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v12/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v12/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v12/constructors/updateNewMessage.md b/old_docs/API_docs_v12/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v12/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v12/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v12/constructors/updateServiceNotification.md b/old_docs/API_docs_v12/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v12/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v12/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v12/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v12/constructors/updates.channelDifferenceTooLong.md index ac2778d2..b56d43c3 100644 --- a/old_docs/API_docs_v12/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v12/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v12/methods/README.md b/old_docs/API_docs_v12/methods/README.md index 61b67911..ae6608f3 100644 --- a/old_docs/API_docs_v12/methods/README.md +++ b/old_docs/API_docs_v12/methods/README.md @@ -148,7 +148,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v12/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v12/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v12/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v12/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v12/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v12/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v12/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v12/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v12/methods/channels.getParticipants.md b/old_docs/API_docs_v12/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v12/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v12/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v12/methods/contacts.importContacts.md b/old_docs/API_docs_v12/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v12/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v12/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v12/methods/help.getAppChangelog.md b/old_docs/API_docs_v12/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v12/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v12/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v13/constructors/messageService.md b/old_docs/API_docs_v13/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v13/constructors/messageService.md +++ b/old_docs/API_docs_v13/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v13/constructors/stickerPack.md b/old_docs/API_docs_v13/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v13/constructors/stickerPack.md +++ b/old_docs/API_docs_v13/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v13/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v13/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v13/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v13/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v13/constructors/updateChannelTooLong.md b/old_docs/API_docs_v13/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v13/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v13/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v13/constructors/updateNewMessage.md b/old_docs/API_docs_v13/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v13/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v13/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v13/constructors/updateServiceNotification.md b/old_docs/API_docs_v13/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v13/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v13/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v13/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v13/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v13/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v13/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v13/methods/README.md b/old_docs/API_docs_v13/methods/README.md index 13edeef0..4627fb21 100644 --- a/old_docs/API_docs_v13/methods/README.md +++ b/old_docs/API_docs_v13/methods/README.md @@ -152,7 +152,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v13/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v13/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v13/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v13/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v13/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v13/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v13/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v13/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v13/methods/channels.getParticipants.md b/old_docs/API_docs_v13/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v13/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v13/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v13/methods/contacts.importContacts.md b/old_docs/API_docs_v13/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v13/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v13/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v13/methods/help.getAppChangelog.md b/old_docs/API_docs_v13/methods/help.getAppChangelog.md index 3c1a75df..be3ca0c4 100644 --- a/old_docs/API_docs_v13/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v13/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v14/constructors/messageService.md b/old_docs/API_docs_v14/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v14/constructors/messageService.md +++ b/old_docs/API_docs_v14/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v14/constructors/stickerPack.md b/old_docs/API_docs_v14/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v14/constructors/stickerPack.md +++ b/old_docs/API_docs_v14/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v14/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v14/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v14/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v14/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v14/constructors/updateChannelTooLong.md b/old_docs/API_docs_v14/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v14/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v14/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v14/constructors/updateNewMessage.md b/old_docs/API_docs_v14/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v14/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v14/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v14/constructors/updateServiceNotification.md b/old_docs/API_docs_v14/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v14/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v14/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v14/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v14/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v14/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v14/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v14/methods/README.md b/old_docs/API_docs_v14/methods/README.md index 4ca7ae12..02682cb4 100644 --- a/old_docs/API_docs_v14/methods/README.md +++ b/old_docs/API_docs_v14/methods/README.md @@ -164,7 +164,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v14/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v14/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v14/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v14/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v14/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v14/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v14/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v14/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v14/methods/channels.getParticipants.md b/old_docs/API_docs_v14/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v14/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v14/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v14/methods/contacts.importContacts.md b/old_docs/API_docs_v14/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v14/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v14/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v14/methods/help.getAppChangelog.md b/old_docs/API_docs_v14/methods/help.getAppChangelog.md index 3c1a75df..be3ca0c4 100644 --- a/old_docs/API_docs_v14/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v14/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v15/constructors/maskCoords.md b/old_docs/API_docs_v15/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v15/constructors/maskCoords.md +++ b/old_docs/API_docs_v15/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v15/constructors/messageService.md b/old_docs/API_docs_v15/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v15/constructors/messageService.md +++ b/old_docs/API_docs_v15/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v15/constructors/stickerPack.md b/old_docs/API_docs_v15/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v15/constructors/stickerPack.md +++ b/old_docs/API_docs_v15/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v15/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v15/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v15/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v15/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v15/constructors/updateChannelTooLong.md b/old_docs/API_docs_v15/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v15/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v15/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v15/constructors/updateNewMessage.md b/old_docs/API_docs_v15/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v15/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v15/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v15/constructors/updateServiceNotification.md b/old_docs/API_docs_v15/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v15/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v15/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v15/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v15/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v15/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v15/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v15/methods/README.md b/old_docs/API_docs_v15/methods/README.md index cf1180a3..94193fd7 100644 --- a/old_docs/API_docs_v15/methods/README.md +++ b/old_docs/API_docs_v15/methods/README.md @@ -174,7 +174,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers attached to a photo or video: messages.getAttachedStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v15/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v15/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v15/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v15/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v15/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v15/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v15/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v15/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v15/methods/channels.getParticipants.md b/old_docs/API_docs_v15/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v15/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v15/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v15/methods/contacts.importContacts.md b/old_docs/API_docs_v15/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v15/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v15/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v15/methods/help.getAppChangelog.md b/old_docs/API_docs_v15/methods/help.getAppChangelog.md index 3c1a75df..be3ca0c4 100644 --- a/old_docs/API_docs_v15/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v15/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v16/constructors/maskCoords.md b/old_docs/API_docs_v16/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v16/constructors/maskCoords.md +++ b/old_docs/API_docs_v16/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v16/constructors/messageService.md b/old_docs/API_docs_v16/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v16/constructors/messageService.md +++ b/old_docs/API_docs_v16/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v16/constructors/stickerPack.md b/old_docs/API_docs_v16/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v16/constructors/stickerPack.md +++ b/old_docs/API_docs_v16/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v16/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v16/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v16/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v16/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v16/constructors/updateChannelTooLong.md b/old_docs/API_docs_v16/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v16/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v16/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v16/constructors/updateNewMessage.md b/old_docs/API_docs_v16/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v16/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v16/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v16/constructors/updateServiceNotification.md b/old_docs/API_docs_v16/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v16/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v16/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v16/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v16/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v16/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v16/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v16/methods/README.md b/old_docs/API_docs_v16/methods/README.md index f8c8a6b5..7e5788bc 100644 --- a/old_docs/API_docs_v16/methods/README.md +++ b/old_docs/API_docs_v16/methods/README.md @@ -184,7 +184,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers attached to a photo or video: messages.getAttachedStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v16/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v16/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v16/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v16/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v16/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v16/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v16/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v16/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v16/methods/channels.getParticipants.md b/old_docs/API_docs_v16/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v16/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v16/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v16/methods/contacts.importContacts.md b/old_docs/API_docs_v16/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v16/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v16/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v16/methods/help.getAppChangelog.md b/old_docs/API_docs_v16/methods/help.getAppChangelog.md index 3c1a75df..be3ca0c4 100644 --- a/old_docs/API_docs_v16/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v16/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v17/constructors/maskCoords.md b/old_docs/API_docs_v17/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v17/constructors/maskCoords.md +++ b/old_docs/API_docs_v17/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v17/constructors/messageService.md b/old_docs/API_docs_v17/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v17/constructors/messageService.md +++ b/old_docs/API_docs_v17/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v17/constructors/stickerPack.md b/old_docs/API_docs_v17/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v17/constructors/stickerPack.md +++ b/old_docs/API_docs_v17/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v17/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v17/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v17/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v17/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v17/constructors/updateChannelTooLong.md b/old_docs/API_docs_v17/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v17/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v17/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v17/constructors/updateNewMessage.md b/old_docs/API_docs_v17/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v17/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v17/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v17/constructors/updateServiceNotification.md b/old_docs/API_docs_v17/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v17/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v17/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v17/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v17/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v17/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v17/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v17/methods/README.md b/old_docs/API_docs_v17/methods/README.md index 017c542e..5c981ee6 100644 --- a/old_docs/API_docs_v17/methods/README.md +++ b/old_docs/API_docs_v17/methods/README.md @@ -198,7 +198,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get temporary payment password: account.getTmpPassword -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v17/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v17/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v17/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v17/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v17/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v17/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v17/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v17/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v17/methods/channels.getParticipants.md b/old_docs/API_docs_v17/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v17/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v17/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v17/methods/contacts.importContacts.md b/old_docs/API_docs_v17/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v17/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v17/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v17/methods/help.getAppChangelog.md b/old_docs/API_docs_v17/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v17/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v17/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v17/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v17/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v17/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v17/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v18/constructors/maskCoords.md b/old_docs/API_docs_v18/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v18/constructors/maskCoords.md +++ b/old_docs/API_docs_v18/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v18/constructors/messageService.md b/old_docs/API_docs_v18/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v18/constructors/messageService.md +++ b/old_docs/API_docs_v18/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v18/constructors/stickerPack.md b/old_docs/API_docs_v18/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v18/constructors/stickerPack.md +++ b/old_docs/API_docs_v18/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v18/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v18/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v18/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v18/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v18/constructors/updateChannelTooLong.md b/old_docs/API_docs_v18/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v18/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v18/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v18/constructors/updateNewMessage.md b/old_docs/API_docs_v18/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v18/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v18/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v18/constructors/updateServiceNotification.md b/old_docs/API_docs_v18/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v18/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v18/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v18/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v18/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v18/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v18/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v18/methods/README.md b/old_docs/API_docs_v18/methods/README.md index 948a1725..4acbdbe5 100644 --- a/old_docs/API_docs_v18/methods/README.md +++ b/old_docs/API_docs_v18/methods/README.md @@ -202,7 +202,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get temporary payment password: account.getTmpPassword -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v18/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v18/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v18/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v18/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v18/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v18/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v18/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v18/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v18/methods/channels.getParticipants.md b/old_docs/API_docs_v18/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v18/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v18/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v18/methods/contacts.importContacts.md b/old_docs/API_docs_v18/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v18/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v18/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v18/methods/help.getAppChangelog.md b/old_docs/API_docs_v18/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v18/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v18/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v18/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v18/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v18/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v18/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v19/constructors/maskCoords.md b/old_docs/API_docs_v19/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v19/constructors/maskCoords.md +++ b/old_docs/API_docs_v19/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v19/constructors/messageService.md b/old_docs/API_docs_v19/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v19/constructors/messageService.md +++ b/old_docs/API_docs_v19/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v19/constructors/stickerPack.md b/old_docs/API_docs_v19/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v19/constructors/stickerPack.md +++ b/old_docs/API_docs_v19/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v19/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v19/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v19/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v19/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v19/constructors/updateChannelTooLong.md b/old_docs/API_docs_v19/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v19/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v19/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v19/constructors/updateNewMessage.md b/old_docs/API_docs_v19/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v19/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v19/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v19/constructors/updateServiceNotification.md b/old_docs/API_docs_v19/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v19/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v19/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v19/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v19/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v19/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v19/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v19/methods/README.md b/old_docs/API_docs_v19/methods/README.md index 17e7cbe2..284860a0 100644 --- a/old_docs/API_docs_v19/methods/README.md +++ b/old_docs/API_docs_v19/methods/README.md @@ -220,7 +220,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v19/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v19/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v19/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v19/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v19/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v19/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v19/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v19/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v19/methods/channels.getParticipants.md b/old_docs/API_docs_v19/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v19/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v19/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v19/methods/contacts.importContacts.md b/old_docs/API_docs_v19/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v19/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v19/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v19/methods/help.getAppChangelog.md b/old_docs/API_docs_v19/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v19/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v19/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v19/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v19/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v19/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v19/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v2/constructors/messageService.md b/old_docs/API_docs_v2/constructors/messageService.md index 7ef0f312..700af4f1 100644 --- a/old_docs/API_docs_v2/constructors/messageService.md +++ b/old_docs/API_docs_v2/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v2/constructors/stickerPack.md b/old_docs/API_docs_v2/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v2/constructors/stickerPack.md +++ b/old_docs/API_docs_v2/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v2/constructors/updateNewMessage.md b/old_docs/API_docs_v2/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v2/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v2/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v2/constructors/updateServiceNotification.md b/old_docs/API_docs_v2/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v2/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v2/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v2/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v2/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v2/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v2/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v2/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v2/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v2/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v2/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v2/methods/contacts.importContacts.md b/old_docs/API_docs_v2/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v2/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v2/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v20/constructors/maskCoords.md b/old_docs/API_docs_v20/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v20/constructors/maskCoords.md +++ b/old_docs/API_docs_v20/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v20/constructors/messageService.md b/old_docs/API_docs_v20/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v20/constructors/messageService.md +++ b/old_docs/API_docs_v20/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v20/constructors/stickerPack.md b/old_docs/API_docs_v20/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v20/constructors/stickerPack.md +++ b/old_docs/API_docs_v20/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v20/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v20/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v20/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v20/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v20/constructors/updateChannelTooLong.md b/old_docs/API_docs_v20/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v20/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v20/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v20/constructors/updateNewMessage.md b/old_docs/API_docs_v20/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v20/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v20/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v20/constructors/updateServiceNotification.md b/old_docs/API_docs_v20/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v20/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v20/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v20/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v20/constructors/updates.channelDifferenceTooLong.md index 29d3f160..f7b9ab22 100644 --- a/old_docs/API_docs_v20/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v20/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v20/methods/README.md b/old_docs/API_docs_v20/methods/README.md index 4a1166eb..0583bae9 100644 --- a/old_docs/API_docs_v20/methods/README.md +++ b/old_docs/API_docs_v20/methods/README.md @@ -222,7 +222,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v20/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v20/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v20/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v20/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v20/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v20/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v20/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v20/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v20/methods/channels.getParticipants.md b/old_docs/API_docs_v20/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v20/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v20/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v20/methods/contacts.importContacts.md b/old_docs/API_docs_v20/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v20/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v20/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v20/methods/help.getAppChangelog.md b/old_docs/API_docs_v20/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v20/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v20/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v20/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v20/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v20/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v20/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v21/constructors/maskCoords.md b/old_docs/API_docs_v21/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v21/constructors/maskCoords.md +++ b/old_docs/API_docs_v21/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v21/constructors/messageService.md b/old_docs/API_docs_v21/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v21/constructors/messageService.md +++ b/old_docs/API_docs_v21/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v21/constructors/stickerPack.md b/old_docs/API_docs_v21/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v21/constructors/stickerPack.md +++ b/old_docs/API_docs_v21/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v21/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v21/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v21/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v21/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v21/constructors/updateChannelTooLong.md b/old_docs/API_docs_v21/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v21/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v21/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v21/constructors/updateNewMessage.md b/old_docs/API_docs_v21/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v21/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v21/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v21/constructors/updateServiceNotification.md b/old_docs/API_docs_v21/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v21/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v21/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v21/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v21/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v21/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v21/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v21/methods/README.md b/old_docs/API_docs_v21/methods/README.md index 85b38ecb..019a5b7b 100644 --- a/old_docs/API_docs_v21/methods/README.md +++ b/old_docs/API_docs_v21/methods/README.md @@ -228,7 +228,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v21/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v21/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v21/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v21/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v21/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v21/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v21/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v21/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v21/methods/channels.getParticipants.md b/old_docs/API_docs_v21/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v21/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v21/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v21/methods/contacts.importContacts.md b/old_docs/API_docs_v21/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v21/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v21/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v21/methods/help.getAppChangelog.md b/old_docs/API_docs_v21/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v21/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v21/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v21/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v21/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v21/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v21/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v22/constructors/maskCoords.md b/old_docs/API_docs_v22/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v22/constructors/maskCoords.md +++ b/old_docs/API_docs_v22/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v22/constructors/messageService.md b/old_docs/API_docs_v22/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v22/constructors/messageService.md +++ b/old_docs/API_docs_v22/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v22/constructors/stickerPack.md b/old_docs/API_docs_v22/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v22/constructors/stickerPack.md +++ b/old_docs/API_docs_v22/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v22/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v22/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v22/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v22/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v22/constructors/updateChannelTooLong.md b/old_docs/API_docs_v22/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v22/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v22/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v22/constructors/updateNewMessage.md b/old_docs/API_docs_v22/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v22/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v22/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v22/constructors/updateServiceNotification.md b/old_docs/API_docs_v22/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v22/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v22/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v22/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v22/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v22/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v22/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v22/methods/README.md b/old_docs/API_docs_v22/methods/README.md index 3ba66dc6..0d0e2fd1 100644 --- a/old_docs/API_docs_v22/methods/README.md +++ b/old_docs/API_docs_v22/methods/README.md @@ -234,7 +234,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v22/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v22/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v22/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v22/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v22/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v22/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v22/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v22/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v22/methods/channels.getParticipants.md b/old_docs/API_docs_v22/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v22/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v22/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v22/methods/contacts.importContacts.md b/old_docs/API_docs_v22/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v22/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v22/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v22/methods/help.getAppChangelog.md b/old_docs/API_docs_v22/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v22/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v22/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v22/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v22/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v22/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v22/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v23/constructors/maskCoords.md b/old_docs/API_docs_v23/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v23/constructors/maskCoords.md +++ b/old_docs/API_docs_v23/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v23/constructors/messageService.md b/old_docs/API_docs_v23/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v23/constructors/messageService.md +++ b/old_docs/API_docs_v23/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v23/constructors/stickerPack.md b/old_docs/API_docs_v23/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v23/constructors/stickerPack.md +++ b/old_docs/API_docs_v23/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v23/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v23/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v23/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v23/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v23/constructors/updateChannelTooLong.md b/old_docs/API_docs_v23/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v23/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v23/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v23/constructors/updateNewMessage.md b/old_docs/API_docs_v23/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v23/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v23/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v23/constructors/updateServiceNotification.md b/old_docs/API_docs_v23/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v23/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v23/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v23/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v23/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v23/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v23/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v23/methods/README.md b/old_docs/API_docs_v23/methods/README.md index 5a141ab3..b1d41156 100644 --- a/old_docs/API_docs_v23/methods/README.md +++ b/old_docs/API_docs_v23/methods/README.md @@ -234,7 +234,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v23/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v23/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v23/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v23/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v23/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v23/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v23/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v23/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v23/methods/channels.getParticipants.md b/old_docs/API_docs_v23/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v23/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v23/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v23/methods/contacts.importContacts.md b/old_docs/API_docs_v23/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v23/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v23/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v23/methods/help.getAppChangelog.md b/old_docs/API_docs_v23/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v23/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v23/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v23/methods/messages.forwardMessages.md b/old_docs/API_docs_v23/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v23/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v23/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v23/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v23/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v23/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v23/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v24/constructors/maskCoords.md b/old_docs/API_docs_v24/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v24/constructors/maskCoords.md +++ b/old_docs/API_docs_v24/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v24/constructors/messageService.md b/old_docs/API_docs_v24/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v24/constructors/messageService.md +++ b/old_docs/API_docs_v24/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v24/constructors/stickerPack.md b/old_docs/API_docs_v24/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v24/constructors/stickerPack.md +++ b/old_docs/API_docs_v24/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v24/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v24/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v24/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v24/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v24/constructors/updateChannelTooLong.md b/old_docs/API_docs_v24/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v24/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v24/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v24/constructors/updateNewMessage.md b/old_docs/API_docs_v24/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v24/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v24/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v24/constructors/updateServiceNotification.md b/old_docs/API_docs_v24/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v24/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v24/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v24/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v24/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v24/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v24/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v24/methods/README.md b/old_docs/API_docs_v24/methods/README.md index 77271b66..df1f36dd 100644 --- a/old_docs/API_docs_v24/methods/README.md +++ b/old_docs/API_docs_v24/methods/README.md @@ -236,7 +236,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v24/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v24/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v24/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v24/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v24/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v24/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v24/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v24/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v24/methods/channels.getParticipants.md b/old_docs/API_docs_v24/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v24/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v24/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v24/methods/contacts.importContacts.md b/old_docs/API_docs_v24/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v24/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v24/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v24/methods/help.getAppChangelog.md b/old_docs/API_docs_v24/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v24/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v24/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v24/methods/messages.forwardMessages.md b/old_docs/API_docs_v24/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v24/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v24/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v24/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v24/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v24/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v24/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v25/constructors/maskCoords.md b/old_docs/API_docs_v25/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v25/constructors/maskCoords.md +++ b/old_docs/API_docs_v25/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v25/constructors/messageService.md b/old_docs/API_docs_v25/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v25/constructors/messageService.md +++ b/old_docs/API_docs_v25/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v25/constructors/stickerPack.md b/old_docs/API_docs_v25/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v25/constructors/stickerPack.md +++ b/old_docs/API_docs_v25/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v25/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v25/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v25/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v25/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v25/constructors/updateChannelTooLong.md b/old_docs/API_docs_v25/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v25/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v25/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v25/constructors/updateNewMessage.md b/old_docs/API_docs_v25/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v25/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v25/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v25/constructors/updateServiceNotification.md b/old_docs/API_docs_v25/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v25/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v25/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v25/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v25/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v25/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v25/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v25/methods/README.md b/old_docs/API_docs_v25/methods/README.md index 02eb58bc..7654e5e5 100644 --- a/old_docs/API_docs_v25/methods/README.md +++ b/old_docs/API_docs_v25/methods/README.md @@ -258,7 +258,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v25/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v25/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v25/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v25/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v25/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v25/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v25/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v25/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v25/methods/channels.getParticipants.md b/old_docs/API_docs_v25/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v25/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v25/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v25/methods/contacts.importContacts.md b/old_docs/API_docs_v25/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v25/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v25/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v25/methods/help.getAppChangelog.md b/old_docs/API_docs_v25/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v25/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v25/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v25/methods/messages.forwardMessages.md b/old_docs/API_docs_v25/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v25/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v25/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v25/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v25/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v25/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v25/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v25/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v25/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v25/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v25/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v26/constructors/maskCoords.md b/old_docs/API_docs_v26/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v26/constructors/maskCoords.md +++ b/old_docs/API_docs_v26/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v26/constructors/messageService.md b/old_docs/API_docs_v26/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v26/constructors/messageService.md +++ b/old_docs/API_docs_v26/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v26/constructors/stickerPack.md b/old_docs/API_docs_v26/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v26/constructors/stickerPack.md +++ b/old_docs/API_docs_v26/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v26/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v26/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v26/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v26/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v26/constructors/updateChannelTooLong.md b/old_docs/API_docs_v26/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v26/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v26/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v26/constructors/updateNewMessage.md b/old_docs/API_docs_v26/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v26/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v26/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v26/constructors/updateServiceNotification.md b/old_docs/API_docs_v26/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v26/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v26/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v26/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v26/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v26/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v26/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v26/methods/README.md b/old_docs/API_docs_v26/methods/README.md index d4add305..fc2f06d2 100644 --- a/old_docs/API_docs_v26/methods/README.md +++ b/old_docs/API_docs_v26/methods/README.md @@ -262,7 +262,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v26/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v26/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v26/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v26/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v26/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v26/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v26/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v26/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v26/methods/channels.getParticipants.md b/old_docs/API_docs_v26/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v26/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v26/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v26/methods/contacts.importContacts.md b/old_docs/API_docs_v26/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v26/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v26/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v26/methods/help.getAppChangelog.md b/old_docs/API_docs_v26/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v26/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v26/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v26/methods/messages.forwardMessages.md b/old_docs/API_docs_v26/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v26/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v26/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v26/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v26/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v26/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v26/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v26/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v26/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v26/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v26/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v27/constructors/maskCoords.md b/old_docs/API_docs_v27/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v27/constructors/maskCoords.md +++ b/old_docs/API_docs_v27/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v27/constructors/messageService.md b/old_docs/API_docs_v27/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v27/constructors/messageService.md +++ b/old_docs/API_docs_v27/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v27/constructors/stickerPack.md b/old_docs/API_docs_v27/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v27/constructors/stickerPack.md +++ b/old_docs/API_docs_v27/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v27/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v27/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v27/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v27/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v27/constructors/updateChannelTooLong.md b/old_docs/API_docs_v27/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v27/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v27/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v27/constructors/updateNewMessage.md b/old_docs/API_docs_v27/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v27/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v27/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v27/constructors/updateServiceNotification.md b/old_docs/API_docs_v27/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v27/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v27/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v27/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v27/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v27/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v27/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v27/methods/README.md b/old_docs/API_docs_v27/methods/README.md index 6c37d4ee..d0b6d672 100644 --- a/old_docs/API_docs_v27/methods/README.md +++ b/old_docs/API_docs_v27/methods/README.md @@ -266,7 +266,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v27/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v27/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v27/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v27/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v27/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v27/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v27/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v27/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v27/methods/channels.getParticipants.md b/old_docs/API_docs_v27/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v27/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v27/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v27/methods/contacts.importContacts.md b/old_docs/API_docs_v27/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v27/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v27/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v27/methods/help.getAppChangelog.md b/old_docs/API_docs_v27/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v27/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v27/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v27/methods/messages.forwardMessages.md b/old_docs/API_docs_v27/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v27/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v27/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v27/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v27/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v27/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v27/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v27/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v27/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v27/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v27/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v28/constructors/maskCoords.md b/old_docs/API_docs_v28/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v28/constructors/maskCoords.md +++ b/old_docs/API_docs_v28/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v28/constructors/messageService.md b/old_docs/API_docs_v28/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v28/constructors/messageService.md +++ b/old_docs/API_docs_v28/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v28/constructors/stickerPack.md b/old_docs/API_docs_v28/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v28/constructors/stickerPack.md +++ b/old_docs/API_docs_v28/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v28/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v28/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v28/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v28/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v28/constructors/updateChannelTooLong.md b/old_docs/API_docs_v28/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v28/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v28/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v28/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v28/constructors/updateChatPinnedMessage.md index 660961f9..97257e93 100644 --- a/old_docs/API_docs_v28/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v28/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v28/constructors/updateNewMessage.md b/old_docs/API_docs_v28/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v28/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v28/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v28/constructors/updateServiceNotification.md b/old_docs/API_docs_v28/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v28/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v28/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v28/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v28/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v28/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v28/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v28/methods/README.md b/old_docs/API_docs_v28/methods/README.md index 84fc28b8..c8568811 100644 --- a/old_docs/API_docs_v28/methods/README.md +++ b/old_docs/API_docs_v28/methods/README.md @@ -274,7 +274,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v28/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v28/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v28/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v28/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v28/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v28/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v28/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v28/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v28/methods/channels.getParticipants.md b/old_docs/API_docs_v28/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v28/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v28/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v28/methods/contacts.importContacts.md b/old_docs/API_docs_v28/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v28/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v28/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v28/methods/help.getAppChangelog.md b/old_docs/API_docs_v28/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v28/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v28/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v28/methods/messages.forwardMessages.md b/old_docs/API_docs_v28/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v28/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v28/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v28/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v28/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v28/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v28/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v28/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v28/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v28/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v28/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v29/constructors/maskCoords.md b/old_docs/API_docs_v29/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v29/constructors/maskCoords.md +++ b/old_docs/API_docs_v29/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v29/constructors/messageService.md b/old_docs/API_docs_v29/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v29/constructors/messageService.md +++ b/old_docs/API_docs_v29/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v29/constructors/stickerPack.md b/old_docs/API_docs_v29/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v29/constructors/stickerPack.md +++ b/old_docs/API_docs_v29/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v29/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v29/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v29/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v29/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v29/constructors/updateChannelTooLong.md b/old_docs/API_docs_v29/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v29/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v29/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v29/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v29/constructors/updateChatPinnedMessage.md index 660961f9..97257e93 100644 --- a/old_docs/API_docs_v29/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v29/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v29/constructors/updateNewMessage.md b/old_docs/API_docs_v29/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v29/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v29/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v29/constructors/updateServiceNotification.md b/old_docs/API_docs_v29/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v29/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v29/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v29/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v29/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v29/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v29/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v29/methods/README.md b/old_docs/API_docs_v29/methods/README.md index afae1020..f2edc65a 100644 --- a/old_docs/API_docs_v29/methods/README.md +++ b/old_docs/API_docs_v29/methods/README.md @@ -282,7 +282,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v29/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v29/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v29/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v29/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v29/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v29/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v29/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v29/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v29/methods/channels.getParticipants.md b/old_docs/API_docs_v29/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v29/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v29/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v29/methods/contacts.importContacts.md b/old_docs/API_docs_v29/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v29/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v29/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v29/methods/help.getAppChangelog.md b/old_docs/API_docs_v29/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v29/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v29/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v29/methods/messages.forwardMessages.md b/old_docs/API_docs_v29/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v29/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v29/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v29/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v29/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v29/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v29/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v29/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v29/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v29/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v29/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v3/constructors/messageService.md b/old_docs/API_docs_v3/constructors/messageService.md index 7ef0f312..700af4f1 100644 --- a/old_docs/API_docs_v3/constructors/messageService.md +++ b/old_docs/API_docs_v3/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v3/constructors/stickerPack.md b/old_docs/API_docs_v3/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v3/constructors/stickerPack.md +++ b/old_docs/API_docs_v3/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v3/constructors/updateNewMessage.md b/old_docs/API_docs_v3/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v3/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v3/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v3/constructors/updateServiceNotification.md b/old_docs/API_docs_v3/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v3/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v3/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v3/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v3/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v3/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v3/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v3/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v3/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v3/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v3/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v3/methods/contacts.importContacts.md b/old_docs/API_docs_v3/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v3/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v3/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v30/constructors/chatBannedRights.md b/old_docs/API_docs_v30/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v30/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v30/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v30/constructors/codeSettings.md b/old_docs/API_docs_v30/constructors/codeSettings.md index ce7055fa..cea3ca08 100644 --- a/old_docs/API_docs_v30/constructors/codeSettings.md +++ b/old_docs/API_docs_v30/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v30/constructors/maskCoords.md b/old_docs/API_docs_v30/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v30/constructors/maskCoords.md +++ b/old_docs/API_docs_v30/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v30/constructors/messageService.md b/old_docs/API_docs_v30/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v30/constructors/messageService.md +++ b/old_docs/API_docs_v30/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v30/constructors/stickerPack.md b/old_docs/API_docs_v30/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v30/constructors/stickerPack.md +++ b/old_docs/API_docs_v30/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v30/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v30/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v30/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v30/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v30/constructors/updateChannelTooLong.md b/old_docs/API_docs_v30/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v30/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v30/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v30/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v30/constructors/updateChatPinnedMessage.md index 660961f9..97257e93 100644 --- a/old_docs/API_docs_v30/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v30/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v30/constructors/updateNewMessage.md b/old_docs/API_docs_v30/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v30/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v30/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v30/constructors/updateServiceNotification.md b/old_docs/API_docs_v30/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v30/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v30/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v30/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v30/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v30/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v30/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v30/methods/README.md b/old_docs/API_docs_v30/methods/README.md index 6ce9ec4b..55a928ec 100644 --- a/old_docs/API_docs_v30/methods/README.md +++ b/old_docs/API_docs_v30/methods/README.md @@ -292,7 +292,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v30/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v30/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v30/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v30/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v30/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v30/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v30/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v30/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v30/methods/channels.getParticipants.md b/old_docs/API_docs_v30/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v30/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v30/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v30/methods/contacts.importContacts.md b/old_docs/API_docs_v30/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v30/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v30/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v30/methods/help.getAppChangelog.md b/old_docs/API_docs_v30/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v30/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v30/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v30/methods/messages.forwardMessages.md b/old_docs/API_docs_v30/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v30/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v30/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v30/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v30/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v30/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v30/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v30/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v30/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v30/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v30/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v31/constructors/chatBannedRights.md b/old_docs/API_docs_v31/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v31/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v31/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v31/constructors/codeSettings.md b/old_docs/API_docs_v31/constructors/codeSettings.md index ce7055fa..cea3ca08 100644 --- a/old_docs/API_docs_v31/constructors/codeSettings.md +++ b/old_docs/API_docs_v31/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v31/constructors/maskCoords.md b/old_docs/API_docs_v31/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v31/constructors/maskCoords.md +++ b/old_docs/API_docs_v31/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v31/constructors/messageService.md b/old_docs/API_docs_v31/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v31/constructors/messageService.md +++ b/old_docs/API_docs_v31/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v31/constructors/stickerPack.md b/old_docs/API_docs_v31/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v31/constructors/stickerPack.md +++ b/old_docs/API_docs_v31/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v31/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v31/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v31/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v31/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v31/constructors/updateChannelTooLong.md b/old_docs/API_docs_v31/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v31/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v31/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v31/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v31/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v31/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v31/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v31/constructors/updateNewMessage.md b/old_docs/API_docs_v31/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v31/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v31/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v31/constructors/updateServiceNotification.md b/old_docs/API_docs_v31/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v31/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v31/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v31/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v31/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v31/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v31/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v31/methods/README.md b/old_docs/API_docs_v31/methods/README.md index a80e4d95..3b938ec5 100644 --- a/old_docs/API_docs_v31/methods/README.md +++ b/old_docs/API_docs_v31/methods/README.md @@ -300,7 +300,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v31/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v31/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v31/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v31/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v31/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v31/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v31/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v31/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v31/methods/channels.getParticipants.md b/old_docs/API_docs_v31/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v31/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v31/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v31/methods/contacts.importContacts.md b/old_docs/API_docs_v31/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v31/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v31/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v31/methods/help.getAppChangelog.md b/old_docs/API_docs_v31/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v31/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v31/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v31/methods/messages.forwardMessages.md b/old_docs/API_docs_v31/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v31/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v31/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v31/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v31/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v31/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v31/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v31/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v31/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v31/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v31/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v32/constructors/chatBannedRights.md b/old_docs/API_docs_v32/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v32/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v32/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v32/constructors/codeSettings.md b/old_docs/API_docs_v32/constructors/codeSettings.md index ce7055fa..cea3ca08 100644 --- a/old_docs/API_docs_v32/constructors/codeSettings.md +++ b/old_docs/API_docs_v32/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v32/constructors/maskCoords.md b/old_docs/API_docs_v32/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v32/constructors/maskCoords.md +++ b/old_docs/API_docs_v32/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v32/constructors/messageService.md b/old_docs/API_docs_v32/constructors/messageService.md index 52d4832b..c01670dd 100644 --- a/old_docs/API_docs_v32/constructors/messageService.md +++ b/old_docs/API_docs_v32/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v32/constructors/stickerPack.md b/old_docs/API_docs_v32/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v32/constructors/stickerPack.md +++ b/old_docs/API_docs_v32/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v32/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v32/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v32/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v32/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v32/constructors/updateChannelTooLong.md b/old_docs/API_docs_v32/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v32/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v32/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v32/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v32/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v32/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v32/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v32/constructors/updateNewMessage.md b/old_docs/API_docs_v32/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v32/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v32/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v32/constructors/updateServiceNotification.md b/old_docs/API_docs_v32/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v32/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v32/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v32/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v32/constructors/updates.channelDifferenceTooLong.md index 387163dd..17986397 100644 --- a/old_docs/API_docs_v32/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v32/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v32/methods/README.md b/old_docs/API_docs_v32/methods/README.md index e22ebe4a..a2712877 100644 --- a/old_docs/API_docs_v32/methods/README.md +++ b/old_docs/API_docs_v32/methods/README.md @@ -302,7 +302,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the admin log of a channel/supergroup: channels.getAdminLog -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v32/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v32/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v32/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v32/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v32/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v32/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v32/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v32/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v32/methods/channels.getParticipants.md b/old_docs/API_docs_v32/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v32/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v32/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v32/methods/contacts.importContacts.md b/old_docs/API_docs_v32/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v32/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v32/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v32/methods/help.getAppChangelog.md b/old_docs/API_docs_v32/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v32/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v32/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v32/methods/messages.forwardMessages.md b/old_docs/API_docs_v32/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v32/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v32/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v32/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v32/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v32/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v32/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v32/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v32/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v32/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v32/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v33/constructors/chatBannedRights.md b/old_docs/API_docs_v33/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v33/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v33/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v33/constructors/codeSettings.md b/old_docs/API_docs_v33/constructors/codeSettings.md index ce7055fa..cea3ca08 100644 --- a/old_docs/API_docs_v33/constructors/codeSettings.md +++ b/old_docs/API_docs_v33/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v33/constructors/maskCoords.md b/old_docs/API_docs_v33/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v33/constructors/maskCoords.md +++ b/old_docs/API_docs_v33/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v33/constructors/messageService.md b/old_docs/API_docs_v33/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v33/constructors/messageService.md +++ b/old_docs/API_docs_v33/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v33/constructors/stickerPack.md b/old_docs/API_docs_v33/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v33/constructors/stickerPack.md +++ b/old_docs/API_docs_v33/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v33/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v33/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v33/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v33/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v33/constructors/updateChannelTooLong.md b/old_docs/API_docs_v33/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v33/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v33/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v33/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v33/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v33/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v33/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v33/constructors/updateNewMessage.md b/old_docs/API_docs_v33/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v33/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v33/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v33/constructors/updateServiceNotification.md b/old_docs/API_docs_v33/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v33/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v33/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v33/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v33/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v33/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v33/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v33/methods/README.md b/old_docs/API_docs_v33/methods/README.md index ae6da3ec..dc28ba8f 100644 --- a/old_docs/API_docs_v33/methods/README.md +++ b/old_docs/API_docs_v33/methods/README.md @@ -314,7 +314,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v33/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v33/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v33/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v33/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v33/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v33/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v33/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v33/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v33/methods/channels.getParticipants.md b/old_docs/API_docs_v33/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v33/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v33/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v33/methods/contacts.importContacts.md b/old_docs/API_docs_v33/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v33/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v33/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v33/methods/help.getAppChangelog.md b/old_docs/API_docs_v33/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v33/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v33/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v33/methods/messages.forwardMessages.md b/old_docs/API_docs_v33/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v33/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v33/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v33/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v33/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v33/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v33/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v33/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v33/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v33/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v33/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v34/constructors/chatBannedRights.md b/old_docs/API_docs_v34/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v34/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v34/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v34/constructors/codeSettings.md b/old_docs/API_docs_v34/constructors/codeSettings.md index ce7055fa..cea3ca08 100644 --- a/old_docs/API_docs_v34/constructors/codeSettings.md +++ b/old_docs/API_docs_v34/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v34/constructors/maskCoords.md b/old_docs/API_docs_v34/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v34/constructors/maskCoords.md +++ b/old_docs/API_docs_v34/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v34/constructors/messageService.md b/old_docs/API_docs_v34/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v34/constructors/messageService.md +++ b/old_docs/API_docs_v34/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v34/constructors/stickerPack.md b/old_docs/API_docs_v34/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v34/constructors/stickerPack.md +++ b/old_docs/API_docs_v34/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v34/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v34/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v34/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v34/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v34/constructors/updateChannelTooLong.md b/old_docs/API_docs_v34/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v34/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v34/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v34/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v34/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v34/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v34/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v34/constructors/updateNewMessage.md b/old_docs/API_docs_v34/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v34/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v34/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v34/constructors/updateServiceNotification.md b/old_docs/API_docs_v34/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v34/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v34/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v34/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v34/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v34/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v34/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v34/methods/README.md b/old_docs/API_docs_v34/methods/README.md index c61b5b6b..bdc66df9 100644 --- a/old_docs/API_docs_v34/methods/README.md +++ b/old_docs/API_docs_v34/methods/README.md @@ -320,7 +320,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v34/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v34/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v34/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v34/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v34/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v34/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v34/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v34/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v34/methods/channels.getParticipants.md b/old_docs/API_docs_v34/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v34/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v34/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v34/methods/contacts.addContact.md b/old_docs/API_docs_v34/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v34/methods/contacts.addContact.md +++ b/old_docs/API_docs_v34/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v34/methods/contacts.importContacts.md b/old_docs/API_docs_v34/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v34/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v34/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v34/methods/help.getAppChangelog.md b/old_docs/API_docs_v34/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v34/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v34/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v34/methods/messages.forwardMessages.md b/old_docs/API_docs_v34/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v34/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v34/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v34/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v34/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v34/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v34/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v34/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v34/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v34/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v34/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v35/constructors/chatBannedRights.md b/old_docs/API_docs_v35/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v35/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v35/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v35/constructors/codeSettings.md b/old_docs/API_docs_v35/constructors/codeSettings.md index ce7055fa..cea3ca08 100644 --- a/old_docs/API_docs_v35/constructors/codeSettings.md +++ b/old_docs/API_docs_v35/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v35/constructors/maskCoords.md b/old_docs/API_docs_v35/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v35/constructors/maskCoords.md +++ b/old_docs/API_docs_v35/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v35/constructors/messageService.md b/old_docs/API_docs_v35/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v35/constructors/messageService.md +++ b/old_docs/API_docs_v35/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v35/constructors/stickerPack.md b/old_docs/API_docs_v35/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v35/constructors/stickerPack.md +++ b/old_docs/API_docs_v35/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v35/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v35/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v35/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v35/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v35/constructors/updateChannelTooLong.md b/old_docs/API_docs_v35/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v35/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v35/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v35/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v35/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v35/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v35/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v35/constructors/updateNewMessage.md b/old_docs/API_docs_v35/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v35/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v35/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v35/constructors/updateServiceNotification.md b/old_docs/API_docs_v35/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v35/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v35/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v35/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v35/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v35/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v35/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v35/methods/README.md b/old_docs/API_docs_v35/methods/README.md index c61b5b6b..bdc66df9 100644 --- a/old_docs/API_docs_v35/methods/README.md +++ b/old_docs/API_docs_v35/methods/README.md @@ -320,7 +320,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v35/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v35/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v35/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v35/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v35/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v35/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v35/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v35/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v35/methods/channels.getParticipants.md b/old_docs/API_docs_v35/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v35/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v35/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v35/methods/contacts.addContact.md b/old_docs/API_docs_v35/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v35/methods/contacts.addContact.md +++ b/old_docs/API_docs_v35/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v35/methods/contacts.importContacts.md b/old_docs/API_docs_v35/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v35/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v35/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v35/methods/help.getAppChangelog.md b/old_docs/API_docs_v35/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v35/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v35/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v35/methods/messages.forwardMessages.md b/old_docs/API_docs_v35/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v35/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v35/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v35/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v35/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v35/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v35/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v35/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v35/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v35/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v35/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v36/constructors/chatBannedRights.md b/old_docs/API_docs_v36/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v36/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v36/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v36/constructors/codeSettings.md b/old_docs/API_docs_v36/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v36/constructors/codeSettings.md +++ b/old_docs/API_docs_v36/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v36/constructors/maskCoords.md b/old_docs/API_docs_v36/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v36/constructors/maskCoords.md +++ b/old_docs/API_docs_v36/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v36/constructors/messageService.md b/old_docs/API_docs_v36/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v36/constructors/messageService.md +++ b/old_docs/API_docs_v36/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v36/constructors/stickerPack.md b/old_docs/API_docs_v36/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v36/constructors/stickerPack.md +++ b/old_docs/API_docs_v36/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v36/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v36/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v36/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v36/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v36/constructors/updateChannelTooLong.md b/old_docs/API_docs_v36/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v36/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v36/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v36/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v36/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v36/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v36/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v36/constructors/updateNewMessage.md b/old_docs/API_docs_v36/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v36/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v36/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v36/constructors/updateServiceNotification.md b/old_docs/API_docs_v36/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v36/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v36/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v36/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v36/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v36/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v36/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v36/methods/README.md b/old_docs/API_docs_v36/methods/README.md index d8a6c706..7b72be34 100644 --- a/old_docs/API_docs_v36/methods/README.md +++ b/old_docs/API_docs_v36/methods/README.md @@ -320,7 +320,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get unread messages where we were mentioned: messages.getUnreadMentions diff --git a/old_docs/API_docs_v36/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v36/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v36/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v36/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v36/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v36/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v36/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v36/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v36/methods/channels.getParticipants.md b/old_docs/API_docs_v36/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v36/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v36/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v36/methods/contacts.addContact.md b/old_docs/API_docs_v36/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v36/methods/contacts.addContact.md +++ b/old_docs/API_docs_v36/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v36/methods/contacts.importContacts.md b/old_docs/API_docs_v36/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v36/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v36/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v36/methods/help.getAppChangelog.md b/old_docs/API_docs_v36/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v36/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v36/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v36/methods/messages.forwardMessages.md b/old_docs/API_docs_v36/methods/messages.forwardMessages.md index f27ae652..7533b169 100644 --- a/old_docs/API_docs_v36/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v36/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v36/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v36/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v36/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v36/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v36/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v36/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v36/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v36/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v37/constructors/chatBannedRights.md b/old_docs/API_docs_v37/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v37/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v37/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v37/constructors/codeSettings.md b/old_docs/API_docs_v37/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v37/constructors/codeSettings.md +++ b/old_docs/API_docs_v37/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v37/constructors/maskCoords.md b/old_docs/API_docs_v37/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v37/constructors/maskCoords.md +++ b/old_docs/API_docs_v37/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v37/constructors/messageService.md b/old_docs/API_docs_v37/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v37/constructors/messageService.md +++ b/old_docs/API_docs_v37/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v37/constructors/restrictionReason.md b/old_docs/API_docs_v37/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v37/constructors/restrictionReason.md +++ b/old_docs/API_docs_v37/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v37/constructors/stickerPack.md b/old_docs/API_docs_v37/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v37/constructors/stickerPack.md +++ b/old_docs/API_docs_v37/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v37/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v37/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v37/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v37/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v37/constructors/updateChannelTooLong.md b/old_docs/API_docs_v37/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v37/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v37/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v37/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v37/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v37/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v37/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v37/constructors/updateNewMessage.md b/old_docs/API_docs_v37/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v37/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v37/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v37/constructors/updateServiceNotification.md b/old_docs/API_docs_v37/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v37/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v37/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v37/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v37/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v37/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v37/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v37/methods/README.md b/old_docs/API_docs_v37/methods/README.md index c5738cbc..6ea9a032 100644 --- a/old_docs/API_docs_v37/methods/README.md +++ b/old_docs/API_docs_v37/methods/README.md @@ -330,7 +330,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v37/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v37/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v37/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v37/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v37/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v37/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v37/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v37/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v37/methods/channels.getParticipants.md b/old_docs/API_docs_v37/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v37/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v37/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v37/methods/contacts.addContact.md b/old_docs/API_docs_v37/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v37/methods/contacts.addContact.md +++ b/old_docs/API_docs_v37/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v37/methods/contacts.importContacts.md b/old_docs/API_docs_v37/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v37/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v37/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v37/methods/help.getAppChangelog.md b/old_docs/API_docs_v37/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v37/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v37/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v37/methods/messages.forwardMessages.md b/old_docs/API_docs_v37/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v37/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v37/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v37/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v37/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v37/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v37/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v37/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v37/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v37/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v37/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v38/constructors/chatBannedRights.md b/old_docs/API_docs_v38/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v38/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v38/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v38/constructors/codeSettings.md b/old_docs/API_docs_v38/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v38/constructors/codeSettings.md +++ b/old_docs/API_docs_v38/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v38/constructors/maskCoords.md b/old_docs/API_docs_v38/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v38/constructors/maskCoords.md +++ b/old_docs/API_docs_v38/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v38/constructors/messageService.md b/old_docs/API_docs_v38/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v38/constructors/messageService.md +++ b/old_docs/API_docs_v38/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v38/constructors/restrictionReason.md b/old_docs/API_docs_v38/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v38/constructors/restrictionReason.md +++ b/old_docs/API_docs_v38/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v38/constructors/stickerPack.md b/old_docs/API_docs_v38/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v38/constructors/stickerPack.md +++ b/old_docs/API_docs_v38/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v38/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v38/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v38/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v38/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v38/constructors/updateChannelTooLong.md b/old_docs/API_docs_v38/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v38/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v38/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v38/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v38/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v38/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v38/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v38/constructors/updateNewMessage.md b/old_docs/API_docs_v38/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v38/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v38/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v38/constructors/updateServiceNotification.md b/old_docs/API_docs_v38/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v38/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v38/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v38/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v38/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v38/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v38/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v38/methods/README.md b/old_docs/API_docs_v38/methods/README.md index db2efaaf..2d696b4f 100644 --- a/old_docs/API_docs_v38/methods/README.md +++ b/old_docs/API_docs_v38/methods/README.md @@ -342,7 +342,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v38/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v38/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v38/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v38/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v38/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v38/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v38/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/auth.exportLoginToken.md b/old_docs/API_docs_v38/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v38/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v38/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/auth.importLoginToken.md b/old_docs/API_docs_v38/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v38/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v38/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v38/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v38/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v38/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/channels.getParticipants.md b/old_docs/API_docs_v38/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v38/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v38/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v38/methods/contacts.addContact.md b/old_docs/API_docs_v38/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v38/methods/contacts.addContact.md +++ b/old_docs/API_docs_v38/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/contacts.importContacts.md b/old_docs/API_docs_v38/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v38/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v38/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/help.getAppChangelog.md b/old_docs/API_docs_v38/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v38/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v38/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/messages.forwardMessages.md b/old_docs/API_docs_v38/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v38/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v38/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v38/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v38/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v38/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v38/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v38/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v38/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v38/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v38/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v39/constructors/chatBannedRights.md b/old_docs/API_docs_v39/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v39/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v39/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v39/constructors/codeSettings.md b/old_docs/API_docs_v39/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v39/constructors/codeSettings.md +++ b/old_docs/API_docs_v39/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v39/constructors/maskCoords.md b/old_docs/API_docs_v39/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v39/constructors/maskCoords.md +++ b/old_docs/API_docs_v39/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v39/constructors/messageService.md b/old_docs/API_docs_v39/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v39/constructors/messageService.md +++ b/old_docs/API_docs_v39/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v39/constructors/restrictionReason.md b/old_docs/API_docs_v39/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v39/constructors/restrictionReason.md +++ b/old_docs/API_docs_v39/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v39/constructors/stickerPack.md b/old_docs/API_docs_v39/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v39/constructors/stickerPack.md +++ b/old_docs/API_docs_v39/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v39/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v39/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v39/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v39/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v39/constructors/updateChannelTooLong.md b/old_docs/API_docs_v39/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v39/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v39/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v39/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v39/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v39/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v39/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v39/constructors/updateNewMessage.md b/old_docs/API_docs_v39/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v39/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v39/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v39/constructors/updateServiceNotification.md b/old_docs/API_docs_v39/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v39/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v39/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v39/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v39/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v39/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v39/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v39/methods/README.md b/old_docs/API_docs_v39/methods/README.md index d6b360db..8fa4fc94 100644 --- a/old_docs/API_docs_v39/methods/README.md +++ b/old_docs/API_docs_v39/methods/README.md @@ -346,7 +346,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v39/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v39/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v39/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v39/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v39/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v39/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v39/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/auth.exportLoginToken.md b/old_docs/API_docs_v39/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v39/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v39/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/auth.importLoginToken.md b/old_docs/API_docs_v39/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v39/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v39/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v39/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v39/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v39/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/channels.getParticipants.md b/old_docs/API_docs_v39/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v39/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v39/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v39/methods/contacts.addContact.md b/old_docs/API_docs_v39/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v39/methods/contacts.addContact.md +++ b/old_docs/API_docs_v39/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/contacts.importContacts.md b/old_docs/API_docs_v39/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v39/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v39/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/help.getAppChangelog.md b/old_docs/API_docs_v39/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v39/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v39/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/messages.forwardMessages.md b/old_docs/API_docs_v39/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v39/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v39/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v39/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v39/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v39/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v39/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v39/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v39/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v39/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v39/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v4/constructors/messageService.md b/old_docs/API_docs_v4/constructors/messageService.md index 7ef0f312..700af4f1 100644 --- a/old_docs/API_docs_v4/constructors/messageService.md +++ b/old_docs/API_docs_v4/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v4/constructors/stickerPack.md b/old_docs/API_docs_v4/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v4/constructors/stickerPack.md +++ b/old_docs/API_docs_v4/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v4/constructors/updateNewMessage.md b/old_docs/API_docs_v4/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v4/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v4/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v4/constructors/updateServiceNotification.md b/old_docs/API_docs_v4/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v4/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v4/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v4/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v4/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v4/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v4/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v4/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v4/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v4/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v4/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v4/methods/contacts.importContacts.md b/old_docs/API_docs_v4/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v4/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v4/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v4/methods/help.getAppChangelog.md b/old_docs/API_docs_v4/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v4/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v4/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v40/constructors/chatBannedRights.md b/old_docs/API_docs_v40/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v40/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v40/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v40/constructors/codeSettings.md b/old_docs/API_docs_v40/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v40/constructors/codeSettings.md +++ b/old_docs/API_docs_v40/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v40/constructors/maskCoords.md b/old_docs/API_docs_v40/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v40/constructors/maskCoords.md +++ b/old_docs/API_docs_v40/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v40/constructors/messageService.md b/old_docs/API_docs_v40/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v40/constructors/messageService.md +++ b/old_docs/API_docs_v40/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v40/constructors/restrictionReason.md b/old_docs/API_docs_v40/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v40/constructors/restrictionReason.md +++ b/old_docs/API_docs_v40/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v40/constructors/statsPercentValue.md b/old_docs/API_docs_v40/constructors/statsPercentValue.md index 1f5386b8..507591e2 100644 --- a/old_docs/API_docs_v40/constructors/statsPercentValue.md +++ b/old_docs/API_docs_v40/constructors/statsPercentValue.md @@ -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 diff --git a/old_docs/API_docs_v40/constructors/stickerPack.md b/old_docs/API_docs_v40/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v40/constructors/stickerPack.md +++ b/old_docs/API_docs_v40/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v40/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v40/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v40/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v40/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v40/constructors/updateChannelTooLong.md b/old_docs/API_docs_v40/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v40/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v40/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v40/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v40/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v40/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v40/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v40/constructors/updateNewMessage.md b/old_docs/API_docs_v40/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v40/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v40/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v40/constructors/updateServiceNotification.md b/old_docs/API_docs_v40/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v40/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v40/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v40/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v40/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v40/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v40/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v40/methods/README.md b/old_docs/API_docs_v40/methods/README.md index 2a1a2058..59bf6274 100644 --- a/old_docs/API_docs_v40/methods/README.md +++ b/old_docs/API_docs_v40/methods/README.md @@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v40/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v40/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v40/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v40/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v40/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v40/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v40/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/auth.exportLoginToken.md b/old_docs/API_docs_v40/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v40/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v40/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/auth.importLoginToken.md b/old_docs/API_docs_v40/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v40/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v40/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v40/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v40/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v40/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/channels.getParticipants.md b/old_docs/API_docs_v40/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v40/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v40/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v40/methods/contacts.addContact.md b/old_docs/API_docs_v40/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v40/methods/contacts.addContact.md +++ b/old_docs/API_docs_v40/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/contacts.importContacts.md b/old_docs/API_docs_v40/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v40/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v40/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/help.getAppChangelog.md b/old_docs/API_docs_v40/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v40/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v40/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/messages.forwardMessages.md b/old_docs/API_docs_v40/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v40/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v40/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v40/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v40/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v40/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v40/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v40/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v40/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v40/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v40/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v41/constructors/chatBannedRights.md b/old_docs/API_docs_v41/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v41/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v41/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v41/constructors/codeSettings.md b/old_docs/API_docs_v41/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v41/constructors/codeSettings.md +++ b/old_docs/API_docs_v41/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v41/constructors/maskCoords.md b/old_docs/API_docs_v41/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v41/constructors/maskCoords.md +++ b/old_docs/API_docs_v41/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v41/constructors/messageService.md b/old_docs/API_docs_v41/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v41/constructors/messageService.md +++ b/old_docs/API_docs_v41/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v41/constructors/restrictionReason.md b/old_docs/API_docs_v41/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v41/constructors/restrictionReason.md +++ b/old_docs/API_docs_v41/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v41/constructors/statsPercentValue.md b/old_docs/API_docs_v41/constructors/statsPercentValue.md index 1f5386b8..507591e2 100644 --- a/old_docs/API_docs_v41/constructors/statsPercentValue.md +++ b/old_docs/API_docs_v41/constructors/statsPercentValue.md @@ -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 diff --git a/old_docs/API_docs_v41/constructors/stickerPack.md b/old_docs/API_docs_v41/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v41/constructors/stickerPack.md +++ b/old_docs/API_docs_v41/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v41/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v41/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v41/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v41/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v41/constructors/updateChannelTooLong.md b/old_docs/API_docs_v41/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v41/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v41/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v41/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v41/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v41/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v41/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v41/constructors/updateNewMessage.md b/old_docs/API_docs_v41/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v41/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v41/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v41/constructors/updateServiceNotification.md b/old_docs/API_docs_v41/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v41/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v41/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v41/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v41/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v41/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v41/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v41/methods/README.md b/old_docs/API_docs_v41/methods/README.md index d5392da1..53754f1f 100644 --- a/old_docs/API_docs_v41/methods/README.md +++ b/old_docs/API_docs_v41/methods/README.md @@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v41/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v41/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v41/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v41/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v41/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v41/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v41/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/auth.exportLoginToken.md b/old_docs/API_docs_v41/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v41/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v41/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/auth.importLoginToken.md b/old_docs/API_docs_v41/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v41/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v41/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v41/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v41/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v41/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/channels.getParticipants.md b/old_docs/API_docs_v41/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v41/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v41/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v41/methods/contacts.addContact.md b/old_docs/API_docs_v41/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v41/methods/contacts.addContact.md +++ b/old_docs/API_docs_v41/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/contacts.importContacts.md b/old_docs/API_docs_v41/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v41/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v41/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/help.getAppChangelog.md b/old_docs/API_docs_v41/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v41/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v41/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/messages.forwardMessages.md b/old_docs/API_docs_v41/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v41/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v41/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v41/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v41/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v41/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v41/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v41/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v41/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v41/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v41/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v42/constructors/chatBannedRights.md b/old_docs/API_docs_v42/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v42/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v42/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v42/constructors/codeSettings.md b/old_docs/API_docs_v42/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v42/constructors/codeSettings.md +++ b/old_docs/API_docs_v42/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v42/constructors/maskCoords.md b/old_docs/API_docs_v42/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v42/constructors/maskCoords.md +++ b/old_docs/API_docs_v42/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v42/constructors/messageService.md b/old_docs/API_docs_v42/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v42/constructors/messageService.md +++ b/old_docs/API_docs_v42/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v42/constructors/restrictionReason.md b/old_docs/API_docs_v42/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v42/constructors/restrictionReason.md +++ b/old_docs/API_docs_v42/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v42/constructors/statsPercentValue.md b/old_docs/API_docs_v42/constructors/statsPercentValue.md index 1f5386b8..507591e2 100644 --- a/old_docs/API_docs_v42/constructors/statsPercentValue.md +++ b/old_docs/API_docs_v42/constructors/statsPercentValue.md @@ -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 diff --git a/old_docs/API_docs_v42/constructors/stickerPack.md b/old_docs/API_docs_v42/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v42/constructors/stickerPack.md +++ b/old_docs/API_docs_v42/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v42/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v42/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v42/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v42/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v42/constructors/updateChannelTooLong.md b/old_docs/API_docs_v42/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v42/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v42/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v42/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v42/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v42/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v42/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v42/constructors/updateNewMessage.md b/old_docs/API_docs_v42/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v42/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v42/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v42/constructors/updateServiceNotification.md b/old_docs/API_docs_v42/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v42/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v42/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v42/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v42/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v42/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v42/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v42/methods/README.md b/old_docs/API_docs_v42/methods/README.md index 536f4914..0c8f5f9f 100644 --- a/old_docs/API_docs_v42/methods/README.md +++ b/old_docs/API_docs_v42/methods/README.md @@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v42/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v42/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v42/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v42/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v42/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v42/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v42/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/auth.exportLoginToken.md b/old_docs/API_docs_v42/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v42/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v42/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/auth.importLoginToken.md b/old_docs/API_docs_v42/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v42/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v42/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v42/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v42/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v42/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/channels.getParticipants.md b/old_docs/API_docs_v42/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v42/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v42/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v42/methods/contacts.addContact.md b/old_docs/API_docs_v42/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v42/methods/contacts.addContact.md +++ b/old_docs/API_docs_v42/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/contacts.importContacts.md b/old_docs/API_docs_v42/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v42/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v42/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/help.getAppChangelog.md b/old_docs/API_docs_v42/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v42/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v42/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/messages.forwardMessages.md b/old_docs/API_docs_v42/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v42/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v42/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v42/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v42/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v42/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v42/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v42/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v42/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v42/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v42/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v43/constructors/chatBannedRights.md b/old_docs/API_docs_v43/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v43/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v43/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v43/constructors/codeSettings.md b/old_docs/API_docs_v43/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v43/constructors/codeSettings.md +++ b/old_docs/API_docs_v43/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v43/constructors/maskCoords.md b/old_docs/API_docs_v43/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v43/constructors/maskCoords.md +++ b/old_docs/API_docs_v43/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v43/constructors/messageService.md b/old_docs/API_docs_v43/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v43/constructors/messageService.md +++ b/old_docs/API_docs_v43/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v43/constructors/restrictionReason.md b/old_docs/API_docs_v43/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v43/constructors/restrictionReason.md +++ b/old_docs/API_docs_v43/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v43/constructors/statsPercentValue.md b/old_docs/API_docs_v43/constructors/statsPercentValue.md index 1f5386b8..507591e2 100644 --- a/old_docs/API_docs_v43/constructors/statsPercentValue.md +++ b/old_docs/API_docs_v43/constructors/statsPercentValue.md @@ -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 diff --git a/old_docs/API_docs_v43/constructors/stickerPack.md b/old_docs/API_docs_v43/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v43/constructors/stickerPack.md +++ b/old_docs/API_docs_v43/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v43/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v43/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v43/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v43/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v43/constructors/updateChannelTooLong.md b/old_docs/API_docs_v43/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v43/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v43/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v43/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v43/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v43/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v43/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v43/constructors/updateNewMessage.md b/old_docs/API_docs_v43/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v43/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v43/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v43/constructors/updateServiceNotification.md b/old_docs/API_docs_v43/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v43/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v43/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v43/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v43/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v43/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v43/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v43/methods/README.md b/old_docs/API_docs_v43/methods/README.md index 536f4914..0c8f5f9f 100644 --- a/old_docs/API_docs_v43/methods/README.md +++ b/old_docs/API_docs_v43/methods/README.md @@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v43/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v43/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v43/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v43/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v43/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v43/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v43/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/auth.exportLoginToken.md b/old_docs/API_docs_v43/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v43/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v43/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/auth.importLoginToken.md b/old_docs/API_docs_v43/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v43/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v43/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v43/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v43/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v43/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/channels.getParticipants.md b/old_docs/API_docs_v43/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v43/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v43/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v43/methods/contacts.addContact.md b/old_docs/API_docs_v43/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v43/methods/contacts.addContact.md +++ b/old_docs/API_docs_v43/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/contacts.importContacts.md b/old_docs/API_docs_v43/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v43/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v43/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/help.getAppChangelog.md b/old_docs/API_docs_v43/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v43/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v43/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/messages.forwardMessages.md b/old_docs/API_docs_v43/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v43/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v43/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v43/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v43/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v43/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v43/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v43/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v43/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v43/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v43/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v44/constructors/chatBannedRights.md b/old_docs/API_docs_v44/constructors/chatBannedRights.md index f53db6d3..a678973a 100644 --- a/old_docs/API_docs_v44/constructors/chatBannedRights.md +++ b/old_docs/API_docs_v44/constructors/chatBannedRights.md @@ -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).| diff --git a/old_docs/API_docs_v44/constructors/codeSettings.md b/old_docs/API_docs_v44/constructors/codeSettings.md index b8a92d46..aa9b40bd 100644 --- a/old_docs/API_docs_v44/constructors/codeSettings.md +++ b/old_docs/API_docs_v44/constructors/codeSettings.md @@ -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 diff --git a/old_docs/API_docs_v44/constructors/maskCoords.md b/old_docs/API_docs_v44/constructors/maskCoords.md index 9e83fb87..d3ea40a1 100644 --- a/old_docs/API_docs_v44/constructors/maskCoords.md +++ b/old_docs/API_docs_v44/constructors/maskCoords.md @@ -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 diff --git a/old_docs/API_docs_v44/constructors/messageService.md b/old_docs/API_docs_v44/constructors/messageService.md index 553a4973..504b4c75 100644 --- a/old_docs/API_docs_v44/constructors/messageService.md +++ b/old_docs/API_docs_v44/constructors/messageService.md @@ -21,7 +21,7 @@ Indicates a service message |post|[Bool](../types/Bool.md) | Optional|Whether it's a channel post| |legacy|[Bool](../types/Bool.md) | Optional|This is a legacy message: it has to be refetched with the new layer| |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| diff --git a/old_docs/API_docs_v44/constructors/phoneCall.md b/old_docs/API_docs_v44/constructors/phoneCall.md index 883d375d..93d5ff15 100644 --- a/old_docs/API_docs_v44/constructors/phoneCall.md +++ b/old_docs/API_docs_v44/constructors/phoneCall.md @@ -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| diff --git a/old_docs/API_docs_v44/constructors/restrictionReason.md b/old_docs/API_docs_v44/constructors/restrictionReason.md index 918027a4..8d59e164 100644 --- a/old_docs/API_docs_v44/constructors/restrictionReason.md +++ b/old_docs/API_docs_v44/constructors/restrictionReason.md @@ -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 diff --git a/old_docs/API_docs_v44/constructors/statsPercentValue.md b/old_docs/API_docs_v44/constructors/statsPercentValue.md index 1f5386b8..507591e2 100644 --- a/old_docs/API_docs_v44/constructors/statsPercentValue.md +++ b/old_docs/API_docs_v44/constructors/statsPercentValue.md @@ -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 diff --git a/old_docs/API_docs_v44/constructors/stickerPack.md b/old_docs/API_docs_v44/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v44/constructors/stickerPack.md +++ b/old_docs/API_docs_v44/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v44/constructors/updateChannelPinnedMessage.md b/old_docs/API_docs_v44/constructors/updateChannelPinnedMessage.md index 51ec6752..8d94d001 100644 --- a/old_docs/API_docs_v44/constructors/updateChannelPinnedMessage.md +++ b/old_docs/API_docs_v44/constructors/updateChannelPinnedMessage.md @@ -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: diff --git a/old_docs/API_docs_v44/constructors/updateChannelTooLong.md b/old_docs/API_docs_v44/constructors/updateChannelTooLong.md index 97bd3ff5..72a1668a 100644 --- a/old_docs/API_docs_v44/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v44/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v44/constructors/updateChatPinnedMessage.md b/old_docs/API_docs_v44/constructors/updateChatPinnedMessage.md index 1f3c75c5..9bc1b6fd 100644 --- a/old_docs/API_docs_v44/constructors/updateChatPinnedMessage.md +++ b/old_docs/API_docs_v44/constructors/updateChatPinnedMessage.md @@ -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,7 +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) +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: diff --git a/old_docs/API_docs_v44/constructors/updateNewMessage.md b/old_docs/API_docs_v44/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v44/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v44/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v44/constructors/updateServiceNotification.md b/old_docs/API_docs_v44/constructors/updateServiceNotification.md index 5e16ab4f..666e12cd 100644 --- a/old_docs/API_docs_v44/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v44/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v44/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v44/constructors/updates.channelDifferenceTooLong.md index 21b49a24..e868e016 100644 --- a/old_docs/API_docs_v44/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v44/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v44/constructors/userFull.md b/old_docs/API_docs_v44/constructors/userFull.md index 675a671c..6dcb555e 100644 --- a/old_docs/API_docs_v44/constructors/userFull.md +++ b/old_docs/API_docs_v44/constructors/userFull.md @@ -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| diff --git a/old_docs/API_docs_v44/methods/README.md b/old_docs/API_docs_v44/methods/README.md index 2c3acd97..11af3791 100644 --- a/old_docs/API_docs_v44/methods/README.md +++ b/old_docs/API_docs_v44/methods/README.md @@ -352,7 +352,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get the number of results that would be found by a messages.search call with the same parameters: messages.getSearchCounters -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Get theme information: account.getTheme diff --git a/old_docs/API_docs_v44/methods/auth.acceptLoginToken.md b/old_docs/API_docs_v44/methods/auth.acceptLoginToken.md index 0f7353dc..7d9d5e02 100644 --- a/old_docs/API_docs_v44/methods/auth.acceptLoginToken.md +++ b/old_docs/API_docs_v44/methods/auth.acceptLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v44/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v44/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v44/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/auth.exportLoginToken.md b/old_docs/API_docs_v44/methods/auth.exportLoginToken.md index 7cba4bab..1d14d7a3 100644 --- a/old_docs/API_docs_v44/methods/auth.exportLoginToken.md +++ b/old_docs/API_docs_v44/methods/auth.exportLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/auth.importLoginToken.md b/old_docs/API_docs_v44/methods/auth.importLoginToken.md index b5d453ce..74e8045f 100644 --- a/old_docs/API_docs_v44/methods/auth.importLoginToken.md +++ b/old_docs/API_docs_v44/methods/auth.importLoginToken.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v44/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v44/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v44/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/channels.getParticipants.md b/old_docs/API_docs_v44/methods/channels.getParticipants.md index bcb34180..7a33d393 100644 --- a/old_docs/API_docs_v44/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v44/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v44/methods/contacts.addContact.md b/old_docs/API_docs_v44/methods/contacts.addContact.md index 7fef619c..1cc33c4f 100644 --- a/old_docs/API_docs_v44/methods/contacts.addContact.md +++ b/old_docs/API_docs_v44/methods/contacts.addContact.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/contacts.importContacts.md b/old_docs/API_docs_v44/methods/contacts.importContacts.md index 79109bae..d36d5683 100644 --- a/old_docs/API_docs_v44/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v44/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/help.getAppChangelog.md b/old_docs/API_docs_v44/methods/help.getAppChangelog.md index b9d2f146..c9432cec 100644 --- a/old_docs/API_docs_v44/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v44/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/messages.forwardMessages.md b/old_docs/API_docs_v44/methods/messages.forwardMessages.md index cd39fe32..5ddfa6e3 100644 --- a/old_docs/API_docs_v44/methods/messages.forwardMessages.md +++ b/old_docs/API_docs_v44/methods/messages.forwardMessages.md @@ -18,7 +18,7 @@ Forwards messages by their IDs. |silent|[Bool](../types/Bool.md) | Whether to send messages silently (no notification will be triggered on the destination clients) | Optional| |background|[Bool](../types/Bool.md) | Whether to send the message in background | Optional| |with\_my\_score|[Bool](../types/Bool.md) | When forwarding games, whether to include your score in the game | Optional| -|grouped|[Bool](../types/Bool.md) | Whether the specified messages represent an album (grouped media) | Optional| +|grouped|[Bool](../types/Bool.md) | | Optional| |from\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Source of messages | Optional| |id|Array of [int](../types/int.md) | IDs of messages | Yes| |to\_peer|[Username, chat ID, Update, Message or InputPeer](../types/InputPeer.md) | Destination peer | Optional| diff --git a/old_docs/API_docs_v44/methods/messages.setBotPrecheckoutResults.md b/old_docs/API_docs_v44/methods/messages.setBotPrecheckoutResults.md index c03da836..6b952143 100644 --- a/old_docs/API_docs_v44/methods/messages.setBotPrecheckoutResults.md +++ b/old_docs/API_docs_v44/methods/messages.setBotPrecheckoutResults.md @@ -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 --- diff --git a/old_docs/API_docs_v44/methods/users.setSecureValueErrors.md b/old_docs/API_docs_v44/methods/users.setSecureValueErrors.md index 636245ca..926d6487 100644 --- a/old_docs/API_docs_v44/methods/users.setSecureValueErrors.md +++ b/old_docs/API_docs_v44/methods/users.setSecureValueErrors.md @@ -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 --- diff --git a/old_docs/API_docs_v5/constructors/messageService.md b/old_docs/API_docs_v5/constructors/messageService.md index eaef7252..6c727a8c 100644 --- a/old_docs/API_docs_v5/constructors/messageService.md +++ b/old_docs/API_docs_v5/constructors/messageService.md @@ -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) | 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| diff --git a/old_docs/API_docs_v5/constructors/stickerPack.md b/old_docs/API_docs_v5/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v5/constructors/stickerPack.md +++ b/old_docs/API_docs_v5/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v5/constructors/updateChannelTooLong.md b/old_docs/API_docs_v5/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v5/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v5/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v5/constructors/updateNewMessage.md b/old_docs/API_docs_v5/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v5/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v5/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v5/constructors/updateServiceNotification.md b/old_docs/API_docs_v5/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v5/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v5/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v5/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v5/constructors/updates.channelDifferenceTooLong.md index 87786a54..2b06812b 100644 --- a/old_docs/API_docs_v5/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v5/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v5/methods/README.md b/old_docs/API_docs_v5/methods/README.md index f812e9f7..2973d603 100644 --- a/old_docs/API_docs_v5/methods/README.md +++ b/old_docs/API_docs_v5/methods/README.md @@ -126,7 +126,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v5/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v5/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v5/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v5/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v5/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v5/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v5/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v5/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v5/methods/channels.getParticipants.md b/old_docs/API_docs_v5/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v5/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v5/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v5/methods/contacts.importContacts.md b/old_docs/API_docs_v5/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v5/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v5/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v5/methods/help.getAppChangelog.md b/old_docs/API_docs_v5/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v5/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v5/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v6/constructors/messageService.md b/old_docs/API_docs_v6/constructors/messageService.md index eaef7252..6c727a8c 100644 --- a/old_docs/API_docs_v6/constructors/messageService.md +++ b/old_docs/API_docs_v6/constructors/messageService.md @@ -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) | 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| diff --git a/old_docs/API_docs_v6/constructors/stickerPack.md b/old_docs/API_docs_v6/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v6/constructors/stickerPack.md +++ b/old_docs/API_docs_v6/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v6/constructors/updateChannelTooLong.md b/old_docs/API_docs_v6/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v6/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v6/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v6/constructors/updateNewMessage.md b/old_docs/API_docs_v6/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v6/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v6/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v6/constructors/updateServiceNotification.md b/old_docs/API_docs_v6/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v6/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v6/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v6/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v6/constructors/updates.channelDifferenceTooLong.md index 87786a54..2b06812b 100644 --- a/old_docs/API_docs_v6/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v6/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v6/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v6/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v6/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v6/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v6/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v6/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v6/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v6/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v6/methods/contacts.importContacts.md b/old_docs/API_docs_v6/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v6/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v6/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v6/methods/help.getAppChangelog.md b/old_docs/API_docs_v6/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v6/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v6/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v7/constructors/messageService.md b/old_docs/API_docs_v7/constructors/messageService.md index c0d05fe7..3d7c59f4 100644 --- a/old_docs/API_docs_v7/constructors/messageService.md +++ b/old_docs/API_docs_v7/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v7/constructors/stickerPack.md b/old_docs/API_docs_v7/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v7/constructors/stickerPack.md +++ b/old_docs/API_docs_v7/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v7/constructors/updateChannelTooLong.md b/old_docs/API_docs_v7/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v7/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v7/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v7/constructors/updateNewMessage.md b/old_docs/API_docs_v7/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v7/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v7/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v7/constructors/updateServiceNotification.md b/old_docs/API_docs_v7/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v7/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v7/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v7/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v7/constructors/updates.channelDifferenceTooLong.md index ac2778d2..b56d43c3 100644 --- a/old_docs/API_docs_v7/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v7/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v7/methods/README.md b/old_docs/API_docs_v7/methods/README.md index be4ebc0d..0ea0d57d 100644 --- a/old_docs/API_docs_v7/methods/README.md +++ b/old_docs/API_docs_v7/methods/README.md @@ -126,7 +126,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v7/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v7/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v7/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v7/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v7/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v7/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v7/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v7/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v7/methods/channels.getParticipants.md b/old_docs/API_docs_v7/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v7/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v7/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v7/methods/contacts.importContacts.md b/old_docs/API_docs_v7/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v7/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v7/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v7/methods/help.getAppChangelog.md b/old_docs/API_docs_v7/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v7/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v7/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v8/constructors/messageService.md b/old_docs/API_docs_v8/constructors/messageService.md index c0d05fe7..3d7c59f4 100644 --- a/old_docs/API_docs_v8/constructors/messageService.md +++ b/old_docs/API_docs_v8/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v8/constructors/stickerPack.md b/old_docs/API_docs_v8/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v8/constructors/stickerPack.md +++ b/old_docs/API_docs_v8/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v8/constructors/updateChannelTooLong.md b/old_docs/API_docs_v8/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v8/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v8/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v8/constructors/updateNewMessage.md b/old_docs/API_docs_v8/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v8/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v8/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v8/constructors/updateServiceNotification.md b/old_docs/API_docs_v8/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v8/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v8/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v8/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v8/constructors/updates.channelDifferenceTooLong.md index ac2778d2..b56d43c3 100644 --- a/old_docs/API_docs_v8/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v8/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v8/methods/README.md b/old_docs/API_docs_v8/methods/README.md index be4ebc0d..0ea0d57d 100644 --- a/old_docs/API_docs_v8/methods/README.md +++ b/old_docs/API_docs_v8/methods/README.md @@ -126,7 +126,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v8/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v8/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v8/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v8/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v8/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v8/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v8/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v8/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v8/methods/channels.getParticipants.md b/old_docs/API_docs_v8/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v8/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v8/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v8/methods/contacts.importContacts.md b/old_docs/API_docs_v8/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v8/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v8/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v8/methods/help.getAppChangelog.md b/old_docs/API_docs_v8/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v8/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v8/methods/help.getAppChangelog.md @@ -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 --- diff --git a/old_docs/API_docs_v9/constructors/messageService.md b/old_docs/API_docs_v9/constructors/messageService.md index c0d05fe7..3d7c59f4 100644 --- a/old_docs/API_docs_v9/constructors/messageService.md +++ b/old_docs/API_docs_v9/constructors/messageService.md @@ -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| diff --git a/old_docs/API_docs_v9/constructors/stickerPack.md b/old_docs/API_docs_v9/constructors/stickerPack.md index c3ef344b..17d34cc2 100644 --- a/old_docs/API_docs_v9/constructors/stickerPack.md +++ b/old_docs/API_docs_v9/constructors/stickerPack.md @@ -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 diff --git a/old_docs/API_docs_v9/constructors/updateChannelTooLong.md b/old_docs/API_docs_v9/constructors/updateChannelTooLong.md index cee734e7..35ff13f1 100644 --- a/old_docs/API_docs_v9/constructors/updateChannelTooLong.md +++ b/old_docs/API_docs_v9/constructors/updateChannelTooLong.md @@ -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: diff --git a/old_docs/API_docs_v9/constructors/updateNewMessage.md b/old_docs/API_docs_v9/constructors/updateNewMessage.md index 571e660a..e144485d 100644 --- a/old_docs/API_docs_v9/constructors/updateNewMessage.md +++ b/old_docs/API_docs_v9/constructors/updateNewMessage.md @@ -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: diff --git a/old_docs/API_docs_v9/constructors/updateServiceNotification.md b/old_docs/API_docs_v9/constructors/updateServiceNotification.md index b4f2638f..76f26ee8 100644 --- a/old_docs/API_docs_v9/constructors/updateServiceNotification.md +++ b/old_docs/API_docs_v9/constructors/updateServiceNotification.md @@ -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 diff --git a/old_docs/API_docs_v9/constructors/updates.channelDifferenceTooLong.md b/old_docs/API_docs_v9/constructors/updates.channelDifferenceTooLong.md index ac2778d2..b56d43c3 100644 --- a/old_docs/API_docs_v9/constructors/updates.channelDifferenceTooLong.md +++ b/old_docs/API_docs_v9/constructors/updates.channelDifferenceTooLong.md @@ -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. diff --git a/old_docs/API_docs_v9/methods/README.md b/old_docs/API_docs_v9/methods/README.md index 6cc5addd..fafd3ae4 100644 --- a/old_docs/API_docs_v9/methods/README.md +++ b/old_docs/API_docs_v9/methods/README.md @@ -128,7 +128,7 @@ image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png * Get stickers by emoji: messages.getStickers -* Get the participants of a channel: channels.getParticipants +* Get the participants of a supergroup/channel: channels.getParticipants * Gets back found messages: messages.search diff --git a/old_docs/API_docs_v9/methods/auth.bindTempAuthKey.md b/old_docs/API_docs_v9/methods/auth.bindTempAuthKey.md index 10257a3e..ada9cfc8 100644 --- a/old_docs/API_docs_v9/methods/auth.bindTempAuthKey.md +++ b/old_docs/API_docs_v9/methods/auth.bindTempAuthKey.md @@ -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 --- diff --git a/old_docs/API_docs_v9/methods/auth.resetAuthorizations.md b/old_docs/API_docs_v9/methods/auth.resetAuthorizations.md index ea1a880d..e379a040 100644 --- a/old_docs/API_docs_v9/methods/auth.resetAuthorizations.md +++ b/old_docs/API_docs_v9/methods/auth.resetAuthorizations.md @@ -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 --- diff --git a/old_docs/API_docs_v9/methods/channels.getParticipants.md b/old_docs/API_docs_v9/methods/channels.getParticipants.md index 97c3ba76..46b0dbaa 100644 --- a/old_docs/API_docs_v9/methods/channels.getParticipants.md +++ b/old_docs/API_docs_v9/methods/channels.getParticipants.md @@ -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: diff --git a/old_docs/API_docs_v9/methods/contacts.importContacts.md b/old_docs/API_docs_v9/methods/contacts.importContacts.md index 950df61c..d758c214 100644 --- a/old_docs/API_docs_v9/methods/contacts.importContacts.md +++ b/old_docs/API_docs_v9/methods/contacts.importContacts.md @@ -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 --- diff --git a/old_docs/API_docs_v9/methods/help.getAppChangelog.md b/old_docs/API_docs_v9/methods/help.getAppChangelog.md index d8ee189d..f2c38b3e 100644 --- a/old_docs/API_docs_v9/methods/help.getAppChangelog.md +++ b/old_docs/API_docs_v9/methods/help.getAppChangelog.md @@ -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 ---