From 83fc12b81ead602ac43bbbef240582301a5f64a4 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Thu, 24 Feb 2022 18:51:11 +0000 Subject: [PATCH] Update content of files --- data/contest.com.html | 291 +++ .../api/account-deletion.html | 129 + data/core.telegram.org/api/auth.html | 202 ++ data/core.telegram.org/api/bots.html | 142 + data/core.telegram.org/api/bots/games.html | 171 ++ data/core.telegram.org/api/datacenter.html | 152 ++ .../core.telegram.org/api/end-to-end/pfs.html | 176 ++ .../api/end-to-end/seq_no.html | 173 ++ .../api/end-to-end/video-calls.html | 215 ++ data/core.telegram.org/api/errors.html | 189 ++ data/core.telegram.org/api/mentions.html | 152 ++ data/core.telegram.org/api/passport.html | 674 +++++ data/core.telegram.org/api/pfs.html | 138 + data/core.telegram.org/api/poll.html | 199 ++ data/core.telegram.org/api/updates.html | 226 ++ .../api/url-authorization.html | 160 ++ data/core.telegram.org/api/web-events.html | 177 ++ data/core.telegram.org/bots.html | 437 ++++ data/core.telegram.org/bots/self-signed.html | 161 ++ data/core.telegram.org/cdn.html | 210 ++ .../constructor/account.autoDownloadSettings | 157 ++ .../constructor/account.resetPasswordOk | 132 + .../constructor/account.sentChangePhoneCode | 161 ++ .../constructor/account.wallPapers | 155 ++ .../constructor/accountDaysTTL.html | 147 ++ .../constructor/auth.loginTokenSuccess | 147 ++ .../constructor/auth.sentCode | 172 ++ .../constructor/auth.sentCodeTypeFlashCall | 150 ++ .../constructor/bankCardOpenUrl.html | 152 ++ .../constructor/baseThemeDay.html | 132 + .../constructor/baseThemeTinted.html | 132 + .../constructor/botCommandScopeChats.html | 135 + .../constructor/cdnConfig.html | 149 ++ .../constructor/channel.html | 289 +++ ...elAdminLogEventActionChangeLinkedChat.html | 152 ++ ...elAdminLogEventActionChangeStickerSet.html | 152 ++ ...nnelAdminLogEventActionChangeUsername.html | 152 ++ ...nelAdminLogEventActionParticipantJoin.html | 132 + ...nLogEventActionToggleGroupCallSetting.html | 147 ++ .../constructor/channelParticipant.html | 152 ++ .../channelParticipantsAdmins.html | 132 + .../channelParticipantsContacts.html | 147 ++ .../channelParticipantsKicked.html | 147 ++ .../constructor/channels.adminLogResults | 157 ++ .../constructor/channels.channelParticipant | 157 ++ .../constructor/channels.channelParticipants | 162 ++ .../constructor/chatBannedRights.html | 216 ++ .../constructor/chatEmpty.html | 147 ++ .../constructor/chatForbidden.html | 152 ++ .../constructor/chatInviteImporter.html | 152 ++ .../constructor/chatInvitePeek.html | 152 ++ .../constructor/chatParticipantAdmin.html | 157 ++ .../constructor/chatParticipantCreator.html | 147 ++ .../constructor/chatParticipants.html | 157 ++ .../constructor/chatTheme.html | 157 ++ .../constructor/contacts.found | 162 ++ .../constructor/contacts.importedContacts | 165 ++ .../constructor/contacts.topPeers | 157 ++ .../constructor/contacts.topPeersNotModified | 132 + .../decryptedMessageActionNoop.html | 133 + .../decryptedMessageActionRequestKey.html | 155 ++ .../decryptedMessageActionTyping.html | 148 ++ .../decryptedMessageMediaContact.html | 163 ++ .../decryptedMessageMediaGeoPoint.html | 153 ++ .../constructor/dialogFilterSuggested.html | 155 ++ .../constructor/dialogPeer.html | 147 ++ .../documentAttributeAnimated.html | 132 + .../documentAttributeHasStickers.html | 132 + .../constructor/emojiKeyword.html | 152 ++ .../constructor/emojiLanguage.html | 147 ++ .../constructor/encryptedChatEmpty.html | 147 ++ .../constructor/encryptedChatWaiting.html | 167 ++ .../constructor/encryptedFile.html | 167 ++ .../constructor/encryptedMessageService.html | 165 ++ .../core.telegram.org/constructor/folder.html | 177 ++ .../constructor/folderPeer.html | 155 ++ .../groupCallParticipantVideo.html | 167 ++ .../constructor/help.passportConfig | 156 ++ .../constructor/help.recentMeUrls | 157 ++ .../constructor/help.supportName | 147 ++ .../constructor/help.userInfoEmpty | 132 + .../constructor/highScore.html | 157 ++ .../inlineQueryPeerTypeMegagroup.html | 135 + .../inlineQueryPeerTypeSameBotPM.html | 132 + .../inputBotInlineResultDocument.html | 179 ++ .../inputBotInlineResultPhoto.html | 164 ++ .../constructor/inputChannelEmpty.html | 132 + .../constructor/inputChatPhoto.html | 147 ++ .../constructor/inputChatPhotoEmpty.html | 132 + .../constructor/inputCheckPasswordEmpty.html | 132 + .../constructor/inputDocumentEmpty.html | 132 + .../constructor/inputEncryptedFileEmpty.html | 132 + .../constructor/inputFileBig.html | 160 ++ .../inputKeyboardButtonUrlAuth.html | 176 ++ .../constructor/inputMediaContact.html | 162 ++ .../constructor/inputMediaGeoPoint.html | 147 ++ .../constructor/inputMediaPhotoExternal.html | 157 ++ .../constructor/inputMediaUploadedPhoto.html | 165 ++ .../constructor/inputMessagePinned.html | 132 + .../constructor/inputMessagesFilterGeo.html | 132 + .../constructor/inputMessagesFilterMusic.html | 132 + .../inputMessagesFilterMyMentions.html | 135 + .../inputMessagesFilterRoundVideo.html | 132 + .../inputMessagesFilterRoundVoice.html | 132 + .../inputPeerPhotoFileLocation.html | 162 ++ .../inputPrivacyKeyChatInvite.html | 132 + .../constructor/inputPrivacyKeyForwards.html | 132 + .../constructor/inputPrivacyKeyPhoneCall.html | 132 + .../inputPrivacyKeyStatusTimestamp.html | 132 + .../inputPrivacyValueAllowUsers.html | 147 ++ .../inputPrivacyValueDisallowUsers.html | 147 ++ .../inputReportReasonGeoIrrelevant.html | 132 + .../constructor/inputReportReasonOther.html | 132 + .../constructor/inputStickerSetID.html | 152 ++ .../constructor/inputStickerSetThumb.html | 155 ++ .../constructor/inputStickeredMediaPhoto.html | 147 ++ .../constructor/inputTheme.html | 152 ++ .../constructor/inputThemeSettings.html | 182 ++ .../constructor/jsonObject.html | 147 ++ .../constructor/jsonString.html | 147 ++ .../constructor/keyboardButtonCallback.html | 167 ++ .../constructor/keyboardButtonGame.html | 147 ++ .../keyboardButtonRequestPhone.html | 147 ++ .../constructor/keyboardButtonRow.html | 147 ++ .../constructor/messageActionChatAddUser.html | 147 ++ .../messageActionChatEditPhoto.html | 147 ++ .../constructor/messageActionEmpty.html | 132 + .../constructor/messageEntityBankCard.html | 152 ++ .../constructor/messageEntityBlockquote.html | 152 ++ .../constructor/messageEntityBotCommand.html | 152 ++ .../constructor/messageEntityEmail.html | 152 ++ .../constructor/messageEntityMention.html | 155 ++ .../constructor/messageEntityMentionName.html | 162 ++ .../constructor/messageEntityPhone.html | 152 ++ .../constructor/messageEntityUnderline.html | 152 ++ .../constructor/messageEntityUnknown.html | 152 ++ .../constructor/messageMediaAudio.html | 147 ++ .../constructor/messageMediaInvoice.html | 198 ++ .../constructor/messageMediaPoll.html | 152 ++ .../constructor/messageMediaUnsupported.html | 132 + .../constructor/messages.chatsSlice | 155 ++ .../constructor/messages.dhConfig | 162 ++ .../constructor/messages.exportedChatInvite | 152 ++ .../constructor/messages.exportedChatInvites | 157 ++ .../constructor/messages.highScores | 152 ++ .../constructor/messages.historyImportParsed | 166 ++ .../constructor/messages.savedGifsNotModified | 132 + .../constructor/messages.sentEncryptedMessage | 147 ++ .../constructor/messages.stickers | 155 ++ data/core.telegram.org/constructor/null.html | 132 + .../constructor/pageBlockBlockquote.html | 152 ++ .../constructor/pageBlockCollage.html | 152 ++ .../constructor/pageBlockDivider.html | 132 + .../constructor/pageBlockFooter.html | 147 ++ .../constructor/pageBlockVideo.html | 167 ++ .../constructor/pageListItemBlocks.html | 147 ++ .../constructor/pageListItemText.html | 147 ++ .../constructor/pageListOrderedItemText.html | 152 ++ .../constructor/paymentRequestedInfo.html | 167 ++ .../constructor/payments.paymentForm | 210 ++ .../constructor/payments.paymentResult | 147 ++ .../constructor/peerLocated.html | 157 ++ .../constructor/peerUser.html | 147 ++ .../constructor/phone.groupParticipants | 175 ++ .../constructor/phoneCallAccepted.html | 189 ++ .../constructor/photoPathSize.html | 155 ++ .../constructor/photoSizeEmpty.html | 150 ++ .../constructor/photoStrippedSize.html | 159 ++ .../constructor/photos.photo | 152 ++ .../constructor/pollAnswer.html | 155 ++ .../constructor/pollResults.html | 184 ++ .../constructor/postAddress.html | 172 ++ .../constructor/privacyKeyAddedByPhone.html | 132 + .../privacyValueAllowContacts.html | 132 + .../constructor/recentMeUrlUnknown.html | 147 ++ .../constructor/recentMeUrlUser.html | 152 ++ .../constructor/replyInlineMarkup.html | 147 ++ .../constructor/replyKeyboardHide.html | 152 ++ .../constructor/secureFile.html | 180 ++ .../constructor/secureFileEmpty.html | 132 + .../securePasswordKdfAlgoSHA512.html | 147 ++ .../securePasswordKdfAlgoUnknown.html | 132 + .../constructor/securePlainPhone.html | 150 ++ .../constructor/secureRequiredType.html | 167 ++ .../constructor/secureSecretSettings.html | 157 ++ .../constructor/secureValue.html | 194 ++ .../constructor/secureValueErrorData.html | 175 ++ .../secureValueErrorTranslationFiles.html | 178 ++ .../secureValueTypeInternalPassport.html | 134 + .../constructor/secureValueTypePassport.html | 132 + .../constructor/secureValueTypePhone.html | 132 + .../secureValueTypeRentalAgreement.html | 132 + .../secureValueTypeTemporaryRegistration.html | 132 + .../sendMessageChooseContactAction.html | 132 + .../sendMessageRecordRoundAction.html | 132 + .../sendMessageUploadVideoAction.html | 147 ++ .../constructor/stats.broadcastStats | 220 ++ .../constructor/statsGroupTopAdmin.html | 165 ++ .../constructor/statsGroupTopInviter.html | 155 ++ .../constructor/statsGroupTopPoster.html | 160 ++ .../constructor/stickerSet.html | 217 ++ .../constructor/storage.filePartial | 132 + .../constructor/storage.filePng | 132 + .../constructor/storage.fileWebp | 132 + .../constructor/textAnchor.html | 152 ++ .../constructor/textMarked.html | 147 ++ .../constructor/textPlain.html | 147 ++ .../constructor/textSuperscript.html | 147 ++ .../topPeerCategoryCorrespondents.html | 132 + .../topPeerCategoryForwardUsers.html | 132 + data/core.telegram.org/constructor/true.html | 134 + .../constructor/updateBotCallbackQuery.html | 182 ++ .../constructor/updateBotInlineQuery.html | 177 ++ .../constructor/updateBotInlineSend.html | 172 ++ .../updateBotPrecheckoutQuery.html | 184 ++ .../constructor/updateBotShippingQuery.html | 162 ++ .../updateChannelAvailableMessages.html | 155 ++ .../updateChannelMessageViews.html | 157 ++ .../constructor/updateChannelUserTyping.html | 172 ++ .../updateChatParticipantAdmin.html | 165 ++ .../constructor/updateDialogFilter.html | 160 ++ .../constructor/updateDialogPinned.html | 165 ++ .../updateGroupCallConnection.html | 157 ++ .../updateInlineBotCallbackQuery.html | 177 ++ .../constructor/updateLangPack.html | 147 ++ .../constructor/updateNewMessage.html | 157 ++ .../constructor/updatePeerHistoryTTL.html | 157 ++ .../updatePhoneCallSignalingData.html | 152 ++ .../updateReadChannelDiscussionOutbox.html | 162 ++ .../constructor/updateReadChannelOutbox.html | 155 ++ .../updateReadFeaturedStickers.html | 132 + .../constructor/updateShortSentMessage.html | 192 ++ .../constructor/updateTheme.html | 147 ++ .../constructor/updateUserBlocked.html | 159 ++ .../constructor/updateUserName.html | 167 ++ .../constructor/updates.differenceSlice | 175 ++ .../constructor/updates.state | 172 ++ .../constructor/userProfilePhoto.html | 172 ++ .../constructor/userProfilePhotoEmpty.html | 132 + .../constructor/userStatusLastMonth.html | 132 + .../constructor/userStatusOffline.html | 147 ++ .../constructor/userStatusOnline.html | 147 ++ .../core.telegram.org/constructor/vector.html | 134 + .../constructor/wallPaperSolid.html | 162 ++ .../constructor/webPageAttributeTheme.html | 157 ++ data/core.telegram.org/contest300K.html | 237 ++ data/core.telegram.org/getProxyConfig.html | 24 + data/core.telegram.org/import-stickers.html | 159 ++ .../method/account.acceptAuthorization | 170 ++ .../method/account.confirmPasswordEmail | 175 ++ .../method/account.confirmPhone | 180 ++ .../method/account.createTheme | 186 ++ .../method/account.finishTakeoutSession | 172 ++ .../method/account.getAuthorizationForm | 176 ++ .../account.getContactSignUpNotification | 135 + .../method/account.installWallPaper | 172 ++ .../method/account.reportPeer | 182 ++ .../method/account.resetWebAuthorizations | 137 + .../method/account.saveTheme | 155 ++ .../method/account.sendChangePhoneCode | 186 ++ .../method/account.sendConfirmPhoneCode | 174 ++ .../method/account.sendVerifyPhoneCode | 173 ++ .../account.setContactSignUpNotification | 150 ++ .../method/account.setContentSettings | 172 ++ .../method/account.setPrivacy | 181 ++ .../method/account.updateDeviceLocked | 153 ++ .../method/account.updatePasswordSettings | 207 ++ .../method/account.updateStatus | 155 ++ .../method/account.updateTheme | 196 ++ .../method/account.updateUsername | 182 ++ .../method/auth.bindTempAuthKey | 252 ++ .../method/auth.importBotAuthorization | 205 ++ .../method/auth.requestPasswordRecovery | 159 ++ .../method/auth.resetAuthorizations | 156 ++ .../core.telegram.org/method/auth.sendInvites | 157 ++ .../method/bots.resetBotCommands | 156 ++ .../method/channels.deleteHistory | 180 ++ .../method/channels.exportMessageLink | 204 ++ .../method/channels.getAdminLog | 226 ++ .../method/channels.getInactiveChannels | 134 + .../method/channels.getLeftChannels | 172 ++ .../method/channels.getParticipant | 205 ++ .../method/channels.getSponsoredMessages | 154 ++ .../method/channels.reportSpam | 192 ++ .../method/contacts.getBlocked | 155 ++ .../method/contacts.getContactIDs | 151 ++ .../method/contacts.getSaved | 150 ++ .../method/contacts.getStatuses | 133 + .../method/contacts.importContacts | 154 ++ .../method/contacts.resetSaved | 135 + .../method/folders.deleteFolder | 175 ++ .../method/help.acceptTermsOfService | 150 ++ .../method/help.getInviteText | 134 + .../method/help.getPromoData | 135 + .../method/help.getRecentMeUrls | 149 ++ .../core.telegram.org/method/help.getUserInfo | 167 ++ .../method/help.hidePromoData | 150 ++ data/core.telegram.org/method/help.saveAppLog | 150 ++ .../method/invokeAfterMsgs.html | 154 ++ .../method/langpack.getLangPack | 171 ++ .../method/messages.acceptEncryption | 190 ++ .../method/messages.acceptUrlAuth | 179 ++ .../method/messages.checkHistoryImport | 152 ++ .../method/messages.deleteExportedChatInvite | 155 ++ .../messages.deleteRevokedExportedChatInvites | 155 ++ .../method/messages.discardEncryption | 187 ++ .../method/messages.editChatAbout | 216 ++ .../messages.editChatDefaultBannedRights | 206 ++ .../method/messages.editChatTitle | 193 ++ .../method/messages.forwardMessages | 363 +++ .../method/messages.getAdminsWithInvites | 149 ++ .../method/messages.getArchivedStickers | 167 ++ .../method/messages.getBotCallbackAnswer | 226 ++ .../method/messages.getChatInviteImporters | 172 ++ .../method/messages.getChats | 173 ++ .../method/messages.getDialogUnreadMarks | 133 + .../method/messages.getExportedChatInvite | 155 ++ .../method/messages.getFeaturedStickers | 153 ++ .../method/messages.getMessagesViews | 199 ++ .../method/messages.getOldFeaturedStickers | 163 ++ .../method/messages.getRecentLocations | 165 ++ .../method/messages.initHistoryImport | 191 ++ .../method/messages.readHistory | 186 ++ .../method/messages.receivedQueue | 170 ++ .../method/messages.reorderPinnedDialogs | 185 ++ .../method/messages.searchGifs | 177 ++ .../method/messages.sendEncrypted | 210 ++ .../method/messages.sendMultiMedia | 263 ++ .../method/messages.sendScheduledMessages | 182 ++ .../method/messages.setBotCallbackAnswer | 203 ++ .../method/messages.setChatTheme | 185 ++ .../method/messages.setHistoryTTL | 182 ++ .../method/messages.setInlineBotResults | 358 +++ .../method/messages.setInlineGameScore | 198 ++ .../method/messages.uninstallStickerSet | 167 ++ .../method/messages.updateDialogFilter | 190 ++ .../core.telegram.org/method/phone.acceptCall | 193 ++ .../method/phone.confirmCall | 188 ++ .../method/phone.createGroupCall | 200 ++ .../method/phone.editGroupCallParticipant | 225 ++ .../method/phone.exportGroupCallInvite | 159 ++ .../method/phone.getGroupCallJoinAs | 149 ++ .../method/phone.saveCallDebug | 177 ++ .../method/phone.setCallRating | 192 ++ .../method/photos.getUserPhotos | 193 ++ .../method/photos.uploadProfilePhoto | 221 ++ .../method/stats.getBroadcastStats | 194 ++ .../method/stats.loadAsyncGraph | 193 ++ .../method/stickers.checkShortName | 172 ++ .../method/upload.getFileHashes | 171 ++ data/core.telegram.org/methods.html | 2306 +++++++++++++++++ .../mtproto/TL-combinators.html | 251 ++ .../mtproto/TL-dependent.html | 236 ++ .../mtproto/TL-polymorph.html | 170 ++ data/core.telegram.org/mtproto/TL.html | 210 ++ .../mtproto/security_guidelines.html | 177 ++ .../passport/sdk-android.html | 180 ++ data/core.telegram.org/schema.html | 1800 +++++++++++++ data/core.telegram.org/schema/mtproto.html | 204 ++ data/core.telegram.org/techfaq.html | 333 +++ .../type/AccountDaysTTL.html | 162 ++ .../type/BankCardOpenUrl.html | 143 + data/core.telegram.org/type/Bool.html | 718 +++++ data/core.telegram.org/type/CdnPublicKey.html | 145 ++ .../type/ChannelAdminLogEventsFilter.html | 143 + .../type/ChannelParticipant.html | 168 ++ data/core.telegram.org/type/ChatOnlines.html | 162 ++ .../type/DecryptedDataBlock.html | 128 + .../type/DecryptedMessage.html | 140 + data/core.telegram.org/type/Dialog.html | 148 ++ .../type/DisabledFeature.html | 128 + data/core.telegram.org/type/Document.html | 173 ++ .../type/DocumentAttribute.html | 173 ++ data/core.telegram.org/type/EmojiKeyword.html | 148 ++ .../core.telegram.org/type/EncryptedChat.html | 187 ++ .../core.telegram.org/type/EncryptedFile.html | 167 ++ .../type/EncryptedMessage.html | 148 ++ .../type/ExportedMessageLink.html | 162 ++ data/core.telegram.org/type/FileHash.html | 143 + data/core.telegram.org/type/Game.html | 143 + data/core.telegram.org/type/GeoPoint.html | 148 ++ data/core.telegram.org/type/GroupCall.html | 148 ++ .../type/GroupCallParticipant.html | 143 + .../type/GroupCallParticipantVideo.html | 143 + .../type/InputEncryptedChat.html | 143 + .../core.telegram.org/type/InputGeoPoint.html | 148 ++ data/core.telegram.org/type/InputMedia.html | 213 ++ data/core.telegram.org/type/InputPeer.html | 173 ++ .../type/InputPeerNotifySettings.html | 143 + .../type/LangPackLanguage.html | 162 ++ data/core.telegram.org/type/MaskCoords.html | 143 + .../core.telegram.org/type/MessageAction.html | 283 ++ .../type/MessageInteractionCounters.html | 143 + data/core.telegram.org/type/MessageMedia.html | 232 ++ .../type/MessageUserVote.html | 153 ++ data/core.telegram.org/type/NearestDc.html | 162 ++ data/core.telegram.org/type/PageCaption.html | 143 + .../type/PaymentSavedCredentials.html | 143 + data/core.telegram.org/type/Peer.html | 153 ++ data/core.telegram.org/type/PhoneCall.html | 168 ++ .../type/PhoneCallDiscardReason.html | 158 ++ .../type/PhoneCallProtocol.html | 143 + data/core.telegram.org/type/Poll.html | 143 + data/core.telegram.org/type/PostAddress.html | 143 + .../type/ReceivedNotifyMessage.html | 143 + data/core.telegram.org/type/ReplyMarkup.html | 158 ++ data/core.telegram.org/type/SecureData.html | 146 ++ data/core.telegram.org/type/SecureValue.html | 162 ++ .../type/SecureValueError.html | 183 ++ data/core.telegram.org/type/Theme.html | 172 ++ .../type/WebAuthorization.html | 143 + .../type/WebPageAttribute.html | 143 + .../type/account.Authorizations | 162 ++ .../type/account.ResetPasswordResult | 175 ++ .../type/account.SentChangePhoneCode | 128 + .../type/account.WebAuthorizations | 162 ++ .../type/auth.PasswordRecovery | 165 ++ data/core.telegram.org/type/auth.SentCodeType | 158 ++ data/core.telegram.org/type/bytes.html | 125 + data/core.telegram.org/type/double.html | 118 + data/core.telegram.org/type/help.Country | 143 + data/core.telegram.org/type/help.PromoData | 167 ++ .../type/messages.AffectedFoundMessages | 162 ++ .../type/messages.CheckedHistoryImportPeer | 165 ++ .../type/messages.ExportedChatInvite | 172 ++ .../type/messages.FavedStickers | 167 ++ .../type/messages.MessageEditData | 162 ++ .../type/messages.PeerDialogs | 167 ++ .../type/messages.SearchCounter | 143 + .../type/messages.SponsoredMessages | 166 ++ .../type/messages.StickerSet | 188 ++ .../type/payments.BankCardData | 162 ++ .../type/payments.PaymentReceipt | 162 ++ .../type/phone.ExportedGroupCallInvite | 162 ++ data/core.telegram.org/type/storage.FileType | 188 ++ data/core.telegram.org/type/string.html | 126 + data/core.telegram.org/type/upload.CdnFile | 167 ++ data/core.telegram.org/type/upload.File | 167 ++ .../api/end-to-end/voice-calls.html | 178 ++ data/corefork.telegram.org/api/files.html | 568 ++++ data/corefork.telegram.org/api/import.html | 173 ++ data/corefork.telegram.org/api/poll.html | 199 ++ data/corefork.telegram.org/api/rights.html | 133 + data/corefork.telegram.org/api/threads.html | 182 ++ .../api/url-authorization.html | 160 ++ .../bots/samples/hellobot.html | 287 ++ data/corefork.telegram.org/bots/webhooks.html | 827 ++++++ .../account.resetPasswordFailedWait | 147 ++ .../constructor/account.themesNotModified | 132 + .../auth.authorizationSignUpRequired | 155 ++ .../constructor/auth.codeTypeCall | 132 + .../constructor/auth.codeTypeSms | 132 + .../constructor/baseThemeArctic.html | 132 + .../constructor/baseThemeClassic.html | 132 + .../constructor/boolTrue.html | 132 + .../constructor/botCommandScopeDefault.html | 132 + .../constructor/botInlineResult.html | 189 ++ .../constructor/channelAdminLogEvent.html | 162 ++ ...nnelAdminLogEventActionChangeLocation.html | 152 ++ ...elAdminLogEventActionDiscardGroupCall.html | 147 ++ ...nnelAdminLogEventActionStartGroupCall.html | 147 ++ ...elAdminLogEventActionToggleNoForwards.html | 162 ++ .../constructor/channelParticipantAdmin.html | 190 ++ .../channelParticipantsAdmins.html | 132 + .../channelParticipantsRecent.html | 132 + .../channelParticipantsSearch.html | 147 ++ .../constructor/chatAdminRights.html | 205 ++ .../constructor/chatBannedRights.html | 215 ++ .../constructor/chatInvitePeek.html | 152 ++ .../constructor/chatOnlines.html | 147 ++ .../constructor/codeSettings.html | 176 ++ .../constructor/contactStatus.html | 152 ++ .../constructor/contacts.blockedSlice | 162 ++ .../constructor/contacts.contacts | 157 ++ .../decryptedMessageActionAcceptKey.html | 160 ++ .../decryptedMessageActionResend.html | 155 ++ .../decryptedMessageMediaGeoPoint.html | 153 ++ .../decryptedMessageMediaPhoto.html | 191 ++ .../decryptedMessageMediaVideo.html | 207 ++ .../decryptedMessageMediaWebPage.html | 148 ++ .../constructor/decryptedMessageService.html | 156 ++ .../constructor/dialog.html | 219 ++ .../constructor/dialogFilterSuggested.html | 155 ++ .../constructor/dialogPeerFolder.html | 150 ++ .../constructor/document.html | 200 ++ .../constructor/documentAttributeAudio.html | 172 ++ .../documentAttributeFilename.html | 147 ++ .../documentAttributeHasStickers.html | 132 + .../constructor/emojiLanguage.html | 147 ++ .../constructor/encryptedChatWaiting.html | 167 ++ .../constructor/fileLocationUnavailable.html | 179 ++ .../constructor/game.html | 182 ++ .../constructor/groupCall.html | 235 ++ .../constructor/help.appUpdate | 190 ++ .../constructor/help.countriesList | 155 ++ .../constructor/help.countriesListNotModified | 132 + .../constructor/help.deepLinkInfoEmpty | 132 + .../constructor/help.noAppUpdate | 132 + .../constructor/help.passportConfig | 156 ++ .../constructor/help.support | 152 ++ .../constructor/help.supportName | 147 ++ .../inlineQueryPeerTypeMegagroup.html | 135 + .../inputBotInlineMessageMediaContact.html | 172 ++ .../constructor/inputBotInlineResult.html | 189 ++ .../constructor/inputChannelEmpty.html | 132 + .../constructor/inputChatUploadedPhoto.html | 165 ++ .../constructor/inputCheckPasswordEmpty.html | 132 + .../constructor/inputDocument.html | 162 ++ .../constructor/inputDocumentEmpty.html | 132 + .../constructor/inputGroupCall.html | 152 ++ .../constructor/inputGroupCallStream.html | 172 ++ .../inputKeyboardButtonUserProfile.html | 173 ++ .../constructor/inputMediaPhoto.html | 157 ++ .../constructor/inputMessageReplyTo.html | 147 ++ .../inputMessagesFilterChatPhotos.html | 132 + .../constructor/inputMessagesFilterEmpty.html | 132 + .../constructor/inputMessagesFilterGeo.html | 132 + .../constructor/inputMessagesFilterVideo.html | 132 + .../inputPaymentCredentialsGooglePay.html | 147 ++ .../inputPeerPhotoFileLocation.html | 162 ++ .../constructor/inputPrivacyKeyPhoneCall.html | 132 + .../inputPrivacyKeyPhoneNumber.html | 132 + .../inputReportReasonPornography.html | 132 + .../constructor/inputReportReasonSpam.html | 132 + .../constructor/inputSecureFileUploaded.html | 169 ++ .../constructor/inputSecureValue.html | 190 ++ .../constructor/inputStickerSetID.html | 152 ++ .../constructor/inputStickerSetThumb.html | 155 ++ .../constructor/inputUserSelf.html | 132 + .../inputWebFileGeoPointLocation.html | 172 ++ .../constructor/inputWebFileLocation.html | 152 ++ .../constructor/jsonArray.html | 147 ++ .../constructor/message.html | 312 +++ .../messageActionCustomAction.html | 147 ++ .../constructor/messageActionGameScore.html | 152 ++ .../messageActionInviteToGroupCall.html | 152 ++ .../messageActionSetChatTheme.html | 147 ++ .../constructor/messageEntityBlockquote.html | 152 ++ .../constructor/messageEntityBotCommand.html | 152 ++ .../constructor/messageEntityItalic.html | 152 ++ .../constructor/messageEntityStrike.html | 152 ++ .../constructor/messageEntityUnderline.html | 152 ++ .../constructor/messageEntityUnknown.html | 152 ++ .../messageInteractionCounters.html | 157 ++ .../constructor/messageMediaDocument.html | 157 ++ .../constructor/messageMediaGame.html | 147 ++ .../constructor/messageMediaGeo.html | 147 ++ .../constructor/messageMediaPhoto.html | 157 ++ .../constructor/messageRange.html | 152 ++ .../constructor/messageReplies.html | 189 ++ .../constructor/messageService.html | 212 ++ .../constructor/messageUserVote.html | 157 ++ .../constructor/messageViews.html | 165 ++ .../messages.affectedFoundMessages | 165 ++ .../constructor/messages.affectedHistory | 157 ++ .../messages.allStickersNotModified | 132 + .../constructor/messages.archivedStickers | 152 ++ .../messages.availableReactionsNotModified | 137 + .../constructor/messages.botCallbackAnswer | 177 ++ .../constructor/messages.botResults | 182 ++ .../messages.chatAdminsWithInvites | 152 ++ .../constructor/messages.chatFull | 157 ++ .../constructor/messages.dialogsNotModified | 147 ++ .../constructor/messages.discussionMessage | 185 ++ .../messages.exportedChatInviteReplaced | 157 ++ .../constructor/messages.exportedChatInvites | 157 ++ .../messages.featuredStickersNotModified | 147 ++ .../constructor/messages.historyImport | 150 ++ .../constructor/messages.inactiveChats | 157 ++ .../constructor/messages.messages | 157 ++ .../constructor/messages.messagesSlice | 185 ++ .../constructor/messages.savedGifs | 155 ++ .../constructor/messages.sponsoredMessages | 157 ++ .../messages.stickerSetNotModified | 137 + .../constructor/messages.votesList | 170 ++ .../constructor/notifyPeer.html | 147 ++ .../constructor/pageBlockCover.html | 147 ++ .../constructor/pageBlockDivider.html | 132 + .../constructor/pageBlockList.html | 147 ++ .../constructor/pageBlockPullquote.html | 152 ++ .../constructor/pageBlockSubtitle.html | 147 ++ .../constructor/pageBlockTable.html | 167 ++ .../constructor/pageBlockUnsupported.html | 132 + .../constructor/pageBlockVideo.html | 167 ++ .../constructor/paymentCharge.html | 152 ++ .../payments.paymentVerificationNeeded | 147 ++ .../constructor/peerChannel.html | 147 ++ .../constructor/peerNotifySettings.html | 182 ++ .../constructor/peerSettings.html | 212 ++ .../constructor/phone.phoneCall | 152 ++ .../phoneCallDiscardReasonHangup.html | 132 + .../constructor/photoCachedSize.html | 167 ++ .../constructor/photoSizeEmpty.html | 150 ++ .../constructor/photos.photos | 152 ++ .../constructor/pollAnswer.html | 155 ++ .../constructor/privacyKeyChatInvite.html | 132 + .../constructor/privacyKeyPhoneP2P.html | 132 + .../privacyValueDisallowUsers.html | 147 ++ .../constructor/recentMeUrlChatInvite.html | 152 ++ .../constructor/recentMeUrlStickerSet.html | 152 ++ .../constructor/recentMeUrlUnknown.html | 147 ++ .../constructor/recentMeUrlUser.html | 152 ++ .../constructor/replyKeyboardMarkup.html | 172 ++ .../constructor/searchResultPosition.html | 184 ++ .../searchResultsCalendarPeriod.html | 195 ++ .../constructor/secureData.html | 160 ++ .../constructor/secureFileEmpty.html | 132 + .../securePasswordKdfAlgoUnknown.html | 132 + .../constructor/securePlainPhone.html | 150 ++ .../constructor/secureRequiredTypeOneOf.html | 147 ++ .../constructor/secureValueErrorFiles.html | 168 ++ .../secureValueErrorFrontSide.html | 166 ++ .../secureValueErrorReverseSide.html | 162 ++ .../secureValueTypeBankStatement.html | 132 + .../secureValueTypePersonalDetails.html | 132 + .../secureValueTypeTemporaryRegistration.html | 132 + .../sendMessageGeoLocationAction.html | 132 + .../constructor/sendMessageTypingAction.html | 132 + .../sendMessageUploadDocumentAction.html | 147 ++ .../speakingInGroupCallAction.html | 132 + .../constructor/stats.broadcastStats | 220 ++ .../constructor/statsGraphAsync.html | 152 ++ .../constructor/statsURL.html | 147 ++ .../constructor/stickerSetCovered.html | 152 ++ .../constructor/stickerSetMultiCovered.html | 152 ++ .../constructor/stickers.suggestedShortName | 147 ++ .../constructor/textAnchor.html | 152 ++ .../constructor/textItalic.html | 147 ++ .../constructor/textUnderline.html | 147 ++ .../constructor/textUrl.html | 157 ++ .../topPeerCategoryForwardUsers.html | 132 + .../constructor/topPeerCategoryPeers.html | 157 ++ .../constructor/true.html | 134 + .../updateBotChatInviteRequester.html | 211 ++ .../constructor/updateBotShippingQuery.html | 162 ++ .../updateChannelMessageViews.html | 157 ++ .../constructor/updateChannelParticipant.html | 192 ++ .../constructor/updateChannelWebPage.html | 167 ++ .../constructor/updateChatParticipants.html | 147 ++ .../constructor/updateContactsReset.html | 132 + .../constructor/updateDcOptions.html | 147 ++ .../updateDeleteChannelMessages.html | 167 ++ .../constructor/updateDialogFilter.html | 160 ++ .../constructor/updateDialogFilterOrder.html | 150 ++ .../constructor/updateFavedStickers.html | 135 + .../constructor/updateLoginToken.html | 132 + .../constructor/updateMessagePoll.html | 162 ++ .../constructor/updateNewChannelMessage.html | 162 ++ .../constructor/updateNotifySettings.html | 152 ++ .../updatePendingJoinRequests.html | 184 ++ .../updatePhoneCallSignalingData.html | 152 ++ .../constructor/updatePinnedMessages.html | 175 ++ .../constructor/updateReadHistoryInbox.html | 182 ++ .../constructor/updateSavedGifs.html | 132 + .../constructor/updateShortChatMessage.html | 232 ++ .../constructor/updateStickerSetsOrder.html | 157 ++ .../constructor/updateUserName.html | 167 ++ .../constructor/updateUserTyping.html | 155 ++ .../constructor/updateWebPage.html | 160 ++ .../constructor/updates.differenceSlice | 175 ++ .../constructor/updates.differenceTooLong | 150 ++ .../constructor/upload.cdnFile | 149 ++ .../constructor/upload.file | 157 ++ .../constructor/urlAuthResultRequest.html | 165 ++ .../constructor/userEmpty.html | 147 ++ .../constructor/userStatusLastWeek.html | 132 + .../constructor/vector.html | 134 + .../constructor/wallPaper.html | 192 ++ .../constructor/wallPaperNoFile.html | 171 ++ .../constructor/webPageEmpty.html | 147 ++ .../corefork.telegram.org/getProxyConfig.html | 24 + .../method/account.changePhone | 195 ++ .../method/account.confirmPhone | 180 ++ .../account.getContactSignUpNotification | 135 + .../method/account.getContentSettings | 134 + .../method/account.getMultiWallPapers | 148 ++ .../method/account.getTmpPassword | 176 ++ .../method/account.installTheme | 170 ++ .../method/account.registerDevice | 217 ++ .../method/account.reportPeer | 182 ++ .../method/account.reportProfilePhoto | 165 ++ .../method/account.saveWallPaper | 177 ++ .../method/account.setAuthorizationTTL | 195 ++ .../method/account.updateProfile | 187 ++ .../method/account.uploadWallPaper | 182 ++ .../method/auth.acceptLoginToken | 176 ++ .../method/auth.bindTempAuthKey | 252 ++ .../method/auth.cancelCode | 180 ++ .../method/auth.checkPassword | 180 ++ .../method/auth.exportLoginToken | 183 ++ .../method/auth.importBotAuthorization | 200 ++ .../method/auth.requestPasswordRecovery | 159 ++ .../method/auth.sendCall | 175 ++ .../corefork.telegram.org/method/auth.sendSms | 167 ++ .../method/bots.sendCustomRequest | 177 ++ .../method/channels.createChannel | 232 ++ .../method/channels.deleteUserHistory | 197 ++ .../method/channels.editAdmin | 301 +++ .../method/channels.editTitle | 206 ++ .../method/channels.exportMessageLink | 204 ++ .../method/channels.getAdminedPublicChannels | 191 ++ .../method/channels.getGroupsForDiscussion | 144 + .../method/channels.getParticipants | 203 ++ .../method/contacts.acceptContact | 190 ++ .../method/contacts.addContact | 217 ++ .../method/contacts.block | 182 ++ .../method/contacts.deleteByPhones | 150 ++ .../method/contacts.getContactIDs | 151 ++ .../method/contacts.getContacts | 155 ++ .../method/contacts.getStatuses | 133 + .../method/contacts.getTopPeers | 226 ++ .../method/contacts.resolveUsername | 177 ++ .../method/folders.editPeerFolders | 180 ++ .../method/help.dismissSuggestion | 160 ++ .../method/help.getDeepLinkInfo | 150 ++ .../method/help.getNearestDc | 134 + .../method/help.getProxyData | 132 + .../method/initConnection.html | 216 ++ .../method/invokeAfterMsgs.html | 154 ++ .../method/invokeWithLayer.html | 194 ++ .../method/invokeWithMessagesRange.html | 154 ++ .../method/langpack.getLanguage | 154 ++ .../method/langpack.getLanguages | 165 ++ .../method/langpack.getStrings | 175 ++ .../method/messages.clearAllDrafts | 138 + .../method/messages.createChat | 202 ++ .../method/messages.deleteMessages | 182 ++ .../method/messages.discardEncryption | 187 ++ .../method/messages.editChatAdmin | 195 ++ .../method/messages.editChatPhoto | 203 ++ .../method/messages.editExportedChatInvite | 208 ++ .../method/messages.forwardMessage | 177 ++ .../method/messages.forwardMessages | 388 +++ .../method/messages.getArchivedStickers | 167 ++ .../method/messages.getAvailableReactions | 168 ++ .../method/messages.getDhConfig | 175 ++ .../method/messages.getDialogFilters | 136 + .../method/messages.getEmojiKeywords | 149 ++ .../messages.getEmojiKeywordsDifference | 154 ++ .../method/messages.getHistory | 227 ++ .../method/messages.getInlineGameHighScores | 177 ++ .../method/messages.getMessagesViews | 199 ++ .../method/messages.getScheduledHistory | 182 ++ .../method/messages.getSearchResultsPositions | 198 ++ .../method/messages.getWebPage | 177 ++ .../method/messages.markDialogUnread | 177 ++ .../method/messages.readMentions | 181 ++ .../method/messages.readReactions | 167 ++ .../method/messages.requestEncryption | 185 ++ .../method/messages.saveDraft | 202 ++ .../method/messages.saveRecentSticker | 182 ++ .../method/messages.search | 291 +++ .../method/messages.searchGifs | 177 ++ .../method/messages.searchGlobal | 226 ++ .../method/messages.sendMedia | 543 ++++ .../messages.sendScreenshotNotification | 187 ++ .../method/messages.sendVote | 220 ++ .../method/messages.setChatAvailableReactions | 184 ++ .../method/messages.setInlineBotResults | 363 +++ .../method/messages.toggleStickerSets | 170 ++ .../method/messages.translateText | 199 ++ .../method/messages.updateDialogFiltersOrder | 153 ++ .../method/payments.getPaymentForm | 181 ++ .../method/payments.getPaymentReceipt | 171 ++ .../method/phone.confirmCall | 188 ++ .../method/phone.getCallConfig | 134 + .../method/phone.getGroupCall | 174 ++ .../method/phone.leaveGroupCall | 160 ++ .../method/phone.setCallRating | 192 ++ .../method/phone.startScheduledGroupCall | 155 ++ .../method/phone.toggleGroupCallRecord | 180 ++ .../method/stats.getMegagroupStats | 191 ++ .../method/stats.getMessagePublicForwards | 212 ++ .../method/stats.loadAsyncGraph | 193 ++ .../method/stickers.suggestShortName | 166 ++ .../method/upload.getWebFile | 176 ++ .../method/upload.saveBigFilePart | 208 ++ .../method/users.getFullUser | 177 ++ .../mtproto/TL-combinators.html | 251 ++ .../mtproto/TL-types.html | 124 + .../mtproto/mtproto-transports.html | 294 +++ .../mtproto/samples-auth_key.html | 748 ++++++ .../mtproto/security_guidelines.html | 177 ++ .../mtproto/serialize.html | 240 ++ .../passport/encryption.html | 606 +++++ .../passport/example.html | 585 +++++ .../passport/sdk-android.html | 180 ++ .../passport/sdk-javascript.html | 258 ++ data/corefork.telegram.org/schema/json.html | 1 + .../type/BotInlineMessage.html | 168 ++ .../type/ChannelAdminLogEvent.html | 143 + .../type/ChannelLocation.html | 148 ++ .../type/ChannelMessagesFilter.html | 148 ++ .../type/ChannelParticipant.html | 168 ++ data/corefork.telegram.org/type/Chat.html | 163 ++ .../type/ChatAdminRights.html | 146 ++ .../type/ChatInviteImporter.html | 143 + .../corefork.telegram.org/type/ChatTheme.html | 128 + data/corefork.telegram.org/type/Config.html | 162 ++ data/corefork.telegram.org/type/Contact.html | 143 + .../type/ContactStatus.html | 143 + .../type/EncryptedChat.html | 187 ++ .../type/EncryptedMessage.html | 148 ++ .../corefork.telegram.org/type/GroupCall.html | 148 ++ .../type/InputBotInlineResult.html | 158 ++ .../type/InputCheckPasswordSRP.html | 151 ++ .../type/InputFileLocation.html | 188 ++ .../type/InputGeoPoint.html | 148 ++ .../type/InputPeerNotifySettings.html | 143 + .../type/InputSecureValue.html | 145 ++ .../type/InputSingleMedia.html | 148 ++ .../type/InputStickerSetItem.html | 143 + .../type/InputTheme.html | 148 ++ .../type/InputWebDocument.html | 143 + .../type/InputWebFileLocation.html | 148 ++ data/corefork.telegram.org/type/Invoice.html | 143 + .../type/LabeledPrice.html | 143 + .../type/LangPackLanguage.html | 162 ++ .../type/LangPackString.html | 153 ++ data/corefork.telegram.org/type/Message.html | 153 ++ .../type/MessageEntity.html | 238 ++ .../type/MessageReplyHeader.html | 143 + .../type/MessageViews.html | 143 + .../type/PageCaption.html | 143 + .../type/PageListItem.html | 148 ++ .../type/PageRelatedArticle.html | 143 + .../type/PaymentRequestedInfo.html | 143 + .../type/PaymentSavedCredentials.html | 143 + .../corefork.telegram.org/type/PhoneCall.html | 168 ++ .../type/PhoneConnection.html | 148 ++ .../corefork.telegram.org/type/PhotoSize.html | 168 ++ .../type/PollAnswer.html | 146 ++ .../type/PostAddress.html | 143 + .../type/ReactionCount.html | 143 + .../type/ReceivedNotifyMessage.html | 143 + .../type/SecurePasswordKdfAlgo.html | 155 ++ .../type/SendMessageAction.html | 228 ++ .../type/StatsAbsValueAndPrev.html | 143 + .../type/StatsPercentValue.html | 143 + .../type/StickerSet.html | 143 + .../type/TopPeerCategoryPeers.html | 143 + .../type/UserStatus.html | 168 ++ .../corefork.telegram.org/type/VideoSize.html | 143 + .../type/WallPaperSettings.html | 143 + data/corefork.telegram.org/type/WebPage.html | 177 ++ .../type/account.ChatThemes | 128 + .../type/account.Password | 162 ++ .../type/account.PasswordInputSettings | 146 ++ .../type/account.PasswordSettings | 164 ++ .../type/account.ResetPasswordResult | 175 ++ .../type/account.WallPapers | 167 ++ .../type/auth.CheckedPhone | 128 + .../type/auth.LoginToken | 177 ++ .../type/contacts.ImportedContacts | 162 ++ .../type/contacts.TopPeers | 172 ++ .../type/help.CountriesList | 167 ++ data/corefork.telegram.org/type/help.Country | 143 + .../type/messages.BotCallbackAnswer | 162 ++ .../type/messages.ChatInviteImporters | 162 ++ .../type/messages.DiscussionMessage | 162 ++ .../type/messages.ExportedChatInvite | 172 ++ .../type/messages.ExportedChatInvites | 162 ++ .../type/messages.FavedStickers | 167 ++ .../type/messages.HighScores | 167 ++ .../type/messages.PeerDialogs | 167 ++ .../type/messages.PeerSettings | 179 ++ .../type/messages.RecentStickers | 167 ++ .../type/messages.SearchResultsCalendar | 177 ++ .../type/messages.SearchResultsPositions | 177 ++ data/corefork.telegram.org/type/photos.Photos | 167 ++ .../type/stats.BroadcastStats | 162 ++ .../type/storage.FileType | 188 ++ .../type/updates.ChannelDifference | 172 ++ .../corefork.telegram.org/type/users.UserFull | 179 ++ data/corefork.telegram.org/widgets/post.html | 240 ++ data/corefork.telegram.org/widgets/share.html | 250 ++ data/desktop.telegram.org.html | 76 + data/desktop.telegram.org/changelog.html | 211 ++ data/instantview.telegram.org.html | 293 +++ data/instantview.telegram.org/auth.html | 294 +++ data/instantview.telegram.org/checklist.html | 624 +++++ data/instantview.telegram.org/docs.html | 1527 +++++++++++ data/instantview.telegram.org/rules.html | 251 ++ data/instantview.telegram.org/samples.html | 395 +++ data/instantview.telegram.org/templates.html | 1253 +++++++++ data/macos.telegram.org.html | 521 ++++ data/promote.telegram.org.html | 205 ++ data/promote.telegram.org/auth.html | 206 ++ data/promote.telegram.org/basics.html | 205 ++ .../promote.telegram.org/getting-started.html | 321 +++ data/promote.telegram.org/guidelines.html | 313 +++ data/promote.telegram.org/tos.html | 253 ++ data/telegram.org.html | 283 ++ data/telegram.org/android.html | 79 + data/telegram.org/api.html | 283 ++ data/telegram.org/apple_privacy.html | 178 ++ data/telegram.org/blog.html | 268 ++ data/telegram.org/blog/200-million.html | 222 ++ data/telegram.org/blog/400-million.html | 272 ++ data/telegram.org/blog/6-years.html | 1355 ++++++++++ data/telegram.org/blog/admin-revolution.html | 261 ++ .../blog/albums-saved-messages.html | 268 ++ data/telegram.org/blog/android-2-0.html | 257 ++ data/telegram.org/blog/android-gif.html | 218 ++ data/telegram.org/blog/android-streaming.html | 241 ++ data/telegram.org/blog/android-themes.html | 246 ++ data/telegram.org/blog/android-wear-2-0.html | 224 ++ .../blog/animated-backgrounds.html | 302 +++ data/telegram.org/blog/animated-stickers.html | 261 ++ data/telegram.org/blog/apple-watch.html | 225 ++ data/telegram.org/blog/autodelete-inv2.html | 299 +++ data/telegram.org/blog/autoplay.html | 245 ++ data/telegram.org/blog/backgrounds-2-0.html | 231 ++ data/telegram.org/blog/bot-revolution.html | 279 ++ data/telegram.org/blog/bots-2-0.html | 260 ++ .../telegram.org/blog/cache-and-stickers.html | 231 ++ data/telegram.org/blog/calls.html | 266 ++ data/telegram.org/blog/captions-places.html | 244 ++ data/telegram.org/blog/channels-2-0.html | 246 ++ data/telegram.org/blog/channels.html | 224 ++ ...hemes-interactive-emoji-read-receipts.html | 297 +++ .../blog/contacts-local-groups.html | 272 ++ data/telegram.org/blog/coronavirus.html | 254 ++ .../crowdsourcing-a-more-secure-future.html | 212 ++ .../telegram.org/blog/cryptocontest-ends.html | 214 ++ data/telegram.org/blog/cryptocontest.html | 224 ++ data/telegram.org/blog/desktop-1-0.html | 250 ++ data/telegram.org/blog/desktop-compact.html | 213 ++ .../blog/discover-stickers-and-more.html | 246 ++ data/telegram.org/blog/drafts.html | 242 ++ data/telegram.org/blog/edit.html | 245 ++ data/telegram.org/blog/encrypted-cdns.html | 228 ++ data/telegram.org/blog/export-and-more.html | 238 ++ data/telegram.org/blog/files-on-steroids.html | 240 ++ .../filters-anonymous-admins-comments.html | 261 ++ data/telegram.org/blog/folders.html | 298 +++ data/telegram.org/blog/games.html | 264 ++ data/telegram.org/blog/gif-revolution.html | 224 ++ data/telegram.org/blog/gifs.html | 223 ++ data/telegram.org/blog/inline-bots.html | 234 ++ data/telegram.org/blog/instant-camera.html | 229 ++ .../blog/instant-view-contest-200K.html | 273 ++ data/telegram.org/blog/invite-links.html | 217 ++ data/telegram.org/blog/link-preview.html | 217 ++ data/telegram.org/blog/live-locations.html | 243 ++ .../live-streams-forwarding-next-channel.html | 285 ++ data/telegram.org/blog/login.html | 257 ++ data/telegram.org/blog/masks.html | 248 ++ data/telegram.org/blog/moar-stickers.html | 343 +++ data/telegram.org/blog/move-history.html | 284 ++ .../blog/new-profiles-people-nearby.html | 263 ++ data/telegram.org/blog/now-you-see-me.html | 235 ++ data/telegram.org/blog/passport.html | 233 ++ .../payments-2-0-scheduled-voice-chats.html | 319 +++ data/telegram.org/blog/payments.html | 253 ++ .../blog/permissions-groups-undo.html | 265 ++ .../blog/photo-editor-and-passcodes.html | 252 ++ data/telegram.org/blog/pin-and-ifttt.html | 263 ++ .../pinned-messages-locations-playlists.html | 282 ++ .../world.html | 278 ++ data/telegram.org/blog/polls-2-0-vmq.html | 271 ++ data/telegram.org/blog/polls.html | 230 ++ .../blog/privacy-discussions-web-bots.html | 284 ++ .../telegram.org/blog/privacy-revolution.html | 226 ++ ...profile-videos-people-nearby-and-more.html | 315 +++ ...ected-content-delete-by-date-and-more.html | 324 +++ .../blog/replies-mentions-hashtags.html | 238 ++ .../blog/replies-mentions-stickers.html | 257 ++ .../blog/scheduled-reminders-themes.html | 264 ++ data/telegram.org/blog/search-and-media.html | 232 ++ .../sessions-and-2-step-verification.html | 220 ++ data/telegram.org/blog/share-preview.html | 269 ++ data/telegram.org/blog/shared-files.html | 231 ++ data/telegram.org/blog/shared-links.html | 221 ++ .../blog/silent-messages-slow-mode.html | 296 +++ .../blog/stickers-meet-art-and-history.html | 338 +++ .../blog/stickers-revolution.html | 231 ++ data/telegram.org/blog/stickers.html | 225 ++ data/telegram.org/blog/supergroups.html | 251 ++ data/telegram.org/blog/supergroups5k.html | 232 ++ data/telegram.org/blog/tdlib.html | 228 ++ data/telegram.org/blog/telegram-5-ios.html | 268 ++ .../telegram-me-change-number-and-pfs.html | 228 ++ data/telegram.org/blog/telegram-x.html | 262 ++ data/telegram.org/blog/telegraph.html | 238 ++ data/telegram.org/blog/themes-accounts.html | 247 ++ data/telegram.org/blog/translations-iv2.html | 276 ++ data/telegram.org/blog/trending-stickers.html | 262 ++ data/telegram.org/blog/unread-replace-2x.html | 259 ++ data/telegram.org/blog/unsend-and-usage.html | 273 ++ .../blog/unsend-privacy-emoji.html | 261 ++ .../blog/usernames-and-secret-chats-v2.html | 222 ++ .../blog/verifiable-apps-and-more.html | 392 +++ data/telegram.org/blog/video-1000.html | 354 +++ data/telegram.org/blog/video-calls.html | 234 ++ data/telegram.org/blog/video-editor-gifs.html | 252 ++ .../blog/video-messages-and-telescope.html | 247 ++ .../blog/video-stickers-better-reactions.html | 273 ++ data/telegram.org/blog/voice-2-secret-3.html | 245 ++ .../blog/voice-chats-on-steroids.html | 275 ++ data/telegram.org/blog/voice-chats.html | 311 +++ .../blog/winter-contest-ends.html | 224 ++ data/telegram.org/evolution.html | 1801 +++++++++++++ data/telegram.org/faq.html | 705 +++++ data/telegram.org/faq_channels.html | 165 ++ data/telegram.org/faq_spam.html | 163 ++ data/telegram.org/jobs.html | 156 ++ data/telegram.org/press.html | 194 ++ data/telegram.org/privacy.html | 299 +++ data/telegram.org/privacy/gmailbot.html | 161 ++ data/telegram.org/support.html | 141 + data/telegram.org/teststore.html | 283 ++ data/telegram.org/tos.html | 133 + data/telegram.org/tour.html | 144 + data/telegram.org/tour/channels.html | 294 +++ data/telegram.org/tour/groups.html | 266 ++ data/telegram.org/tour/quizbot.html | 215 ++ data/telegram.org/tour/screenshots.html | 217 ++ data/telegram.org/verify.html | 151 ++ .../what-can-you-do-with-Telegram.html | 283 ++ data/themes.telegram.org.html | 162 ++ data/themes.telegram.org/auth.html | 163 ++ data/translations.telegram.org.html | 298 +++ data/translations.telegram.org/en.html | 335 +++ .../translations.telegram.org/en/android.html | 390 +++ .../en/android_x.html | 390 +++ data/translations.telegram.org/en/ios.html | 390 +++ data/translations.telegram.org/en/macos.html | 390 +++ .../en/tdesktop.html | 390 +++ data/tsf.telegram.org.html | 240 ++ data/tsf.telegram.org/auth.html | 241 ++ data/tsf.telegram.org/manuals.html | 224 ++ .../manuals/answering_questions.html | 265 ++ data/tsf.telegram.org/manuals/bios.html | 331 +++ .../tsf.telegram.org/manuals/bug_herding.html | 334 +++ .../tsf.telegram.org/manuals/bug_hunting.html | 270 ++ data/tsf.telegram.org/manuals/bugs.html | 460 ++++ .../tsf.telegram.org/manuals/come-and-go.html | 229 ++ .../tsf.telegram.org/manuals/e2ee-simple.html | 284 ++ data/tsf.telegram.org/manuals/e2ee.html | 202 ++ .../manuals/feature_philosophy.html | 263 ++ 1041 files changed, 199452 insertions(+) create mode 100644 data/contest.com.html create mode 100644 data/core.telegram.org/api/account-deletion.html create mode 100644 data/core.telegram.org/api/auth.html create mode 100644 data/core.telegram.org/api/bots.html create mode 100644 data/core.telegram.org/api/bots/games.html create mode 100644 data/core.telegram.org/api/datacenter.html create mode 100644 data/core.telegram.org/api/end-to-end/pfs.html create mode 100644 data/core.telegram.org/api/end-to-end/seq_no.html create mode 100644 data/core.telegram.org/api/end-to-end/video-calls.html create mode 100644 data/core.telegram.org/api/errors.html create mode 100644 data/core.telegram.org/api/mentions.html create mode 100644 data/core.telegram.org/api/passport.html create mode 100644 data/core.telegram.org/api/pfs.html create mode 100644 data/core.telegram.org/api/poll.html create mode 100644 data/core.telegram.org/api/updates.html create mode 100644 data/core.telegram.org/api/url-authorization.html create mode 100644 data/core.telegram.org/api/web-events.html create mode 100644 data/core.telegram.org/bots.html create mode 100644 data/core.telegram.org/bots/self-signed.html create mode 100644 data/core.telegram.org/cdn.html create mode 100644 data/core.telegram.org/constructor/account.autoDownloadSettings create mode 100644 data/core.telegram.org/constructor/account.resetPasswordOk create mode 100644 data/core.telegram.org/constructor/account.sentChangePhoneCode create mode 100644 data/core.telegram.org/constructor/account.wallPapers create mode 100644 data/core.telegram.org/constructor/accountDaysTTL.html create mode 100644 data/core.telegram.org/constructor/auth.loginTokenSuccess create mode 100644 data/core.telegram.org/constructor/auth.sentCode create mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall create mode 100644 data/core.telegram.org/constructor/bankCardOpenUrl.html create mode 100644 data/core.telegram.org/constructor/baseThemeDay.html create mode 100644 data/core.telegram.org/constructor/baseThemeTinted.html create mode 100644 data/core.telegram.org/constructor/botCommandScopeChats.html create mode 100644 data/core.telegram.org/constructor/cdnConfig.html create mode 100644 data/core.telegram.org/constructor/channel.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html create mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html create mode 100644 data/core.telegram.org/constructor/channelParticipant.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsAdmins.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsContacts.html create mode 100644 data/core.telegram.org/constructor/channelParticipantsKicked.html create mode 100644 data/core.telegram.org/constructor/channels.adminLogResults create mode 100644 data/core.telegram.org/constructor/channels.channelParticipant create mode 100644 data/core.telegram.org/constructor/channels.channelParticipants create mode 100644 data/core.telegram.org/constructor/chatBannedRights.html create mode 100644 data/core.telegram.org/constructor/chatEmpty.html create mode 100644 data/core.telegram.org/constructor/chatForbidden.html create mode 100644 data/core.telegram.org/constructor/chatInviteImporter.html create mode 100644 data/core.telegram.org/constructor/chatInvitePeek.html create mode 100644 data/core.telegram.org/constructor/chatParticipantAdmin.html create mode 100644 data/core.telegram.org/constructor/chatParticipantCreator.html create mode 100644 data/core.telegram.org/constructor/chatParticipants.html create mode 100644 data/core.telegram.org/constructor/chatTheme.html create mode 100644 data/core.telegram.org/constructor/contacts.found create mode 100644 data/core.telegram.org/constructor/contacts.importedContacts create mode 100644 data/core.telegram.org/constructor/contacts.topPeers create mode 100644 data/core.telegram.org/constructor/contacts.topPeersNotModified create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNoop.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageActionTyping.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaContact.html create mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html create mode 100644 data/core.telegram.org/constructor/dialogFilterSuggested.html create mode 100644 data/core.telegram.org/constructor/dialogPeer.html create mode 100644 data/core.telegram.org/constructor/documentAttributeAnimated.html create mode 100644 data/core.telegram.org/constructor/documentAttributeHasStickers.html create mode 100644 data/core.telegram.org/constructor/emojiKeyword.html create mode 100644 data/core.telegram.org/constructor/emojiLanguage.html create mode 100644 data/core.telegram.org/constructor/encryptedChatEmpty.html create mode 100644 data/core.telegram.org/constructor/encryptedChatWaiting.html create mode 100644 data/core.telegram.org/constructor/encryptedFile.html create mode 100644 data/core.telegram.org/constructor/encryptedMessageService.html create mode 100644 data/core.telegram.org/constructor/folder.html create mode 100644 data/core.telegram.org/constructor/folderPeer.html create mode 100644 data/core.telegram.org/constructor/groupCallParticipantVideo.html create mode 100644 data/core.telegram.org/constructor/help.passportConfig create mode 100644 data/core.telegram.org/constructor/help.recentMeUrls create mode 100644 data/core.telegram.org/constructor/help.supportName create mode 100644 data/core.telegram.org/constructor/help.userInfoEmpty create mode 100644 data/core.telegram.org/constructor/highScore.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html create mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineResultDocument.html create mode 100644 data/core.telegram.org/constructor/inputBotInlineResultPhoto.html create mode 100644 data/core.telegram.org/constructor/inputChannelEmpty.html create mode 100644 data/core.telegram.org/constructor/inputChatPhoto.html create mode 100644 data/core.telegram.org/constructor/inputChatPhotoEmpty.html create mode 100644 data/core.telegram.org/constructor/inputCheckPasswordEmpty.html create mode 100644 data/core.telegram.org/constructor/inputDocumentEmpty.html create mode 100644 data/core.telegram.org/constructor/inputEncryptedFileEmpty.html create mode 100644 data/core.telegram.org/constructor/inputFileBig.html create mode 100644 data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html create mode 100644 data/core.telegram.org/constructor/inputMediaContact.html create mode 100644 data/core.telegram.org/constructor/inputMediaGeoPoint.html create mode 100644 data/core.telegram.org/constructor/inputMediaPhotoExternal.html create mode 100644 data/core.telegram.org/constructor/inputMediaUploadedPhoto.html create mode 100644 data/core.telegram.org/constructor/inputMessagePinned.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterGeo.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMusic.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html create mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html create mode 100644 data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyForwards.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html create mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html create mode 100644 data/core.telegram.org/constructor/inputReportReasonOther.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetID.html create mode 100644 data/core.telegram.org/constructor/inputStickerSetThumb.html create mode 100644 data/core.telegram.org/constructor/inputStickeredMediaPhoto.html create mode 100644 data/core.telegram.org/constructor/inputTheme.html create mode 100644 data/core.telegram.org/constructor/inputThemeSettings.html create mode 100644 data/core.telegram.org/constructor/jsonObject.html create mode 100644 data/core.telegram.org/constructor/jsonString.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonCallback.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonGame.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPhone.html create mode 100644 data/core.telegram.org/constructor/keyboardButtonRow.html create mode 100644 data/core.telegram.org/constructor/messageActionChatAddUser.html create mode 100644 data/core.telegram.org/constructor/messageActionChatEditPhoto.html create mode 100644 data/core.telegram.org/constructor/messageActionEmpty.html create mode 100644 data/core.telegram.org/constructor/messageEntityBankCard.html create mode 100644 data/core.telegram.org/constructor/messageEntityBlockquote.html create mode 100644 data/core.telegram.org/constructor/messageEntityBotCommand.html create mode 100644 data/core.telegram.org/constructor/messageEntityEmail.html create mode 100644 data/core.telegram.org/constructor/messageEntityMention.html create mode 100644 data/core.telegram.org/constructor/messageEntityMentionName.html create mode 100644 data/core.telegram.org/constructor/messageEntityPhone.html create mode 100644 data/core.telegram.org/constructor/messageEntityUnderline.html create mode 100644 data/core.telegram.org/constructor/messageEntityUnknown.html create mode 100644 data/core.telegram.org/constructor/messageMediaAudio.html create mode 100644 data/core.telegram.org/constructor/messageMediaInvoice.html create mode 100644 data/core.telegram.org/constructor/messageMediaPoll.html create mode 100644 data/core.telegram.org/constructor/messageMediaUnsupported.html create mode 100644 data/core.telegram.org/constructor/messages.chatsSlice create mode 100644 data/core.telegram.org/constructor/messages.dhConfig create mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvite create mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvites create mode 100644 data/core.telegram.org/constructor/messages.highScores create mode 100644 data/core.telegram.org/constructor/messages.historyImportParsed create mode 100644 data/core.telegram.org/constructor/messages.savedGifsNotModified create mode 100644 data/core.telegram.org/constructor/messages.sentEncryptedMessage create mode 100644 data/core.telegram.org/constructor/messages.stickers create mode 100644 data/core.telegram.org/constructor/null.html create mode 100644 data/core.telegram.org/constructor/pageBlockBlockquote.html create mode 100644 data/core.telegram.org/constructor/pageBlockCollage.html create mode 100644 data/core.telegram.org/constructor/pageBlockDivider.html create mode 100644 data/core.telegram.org/constructor/pageBlockFooter.html create mode 100644 data/core.telegram.org/constructor/pageBlockVideo.html create mode 100644 data/core.telegram.org/constructor/pageListItemBlocks.html create mode 100644 data/core.telegram.org/constructor/pageListItemText.html create mode 100644 data/core.telegram.org/constructor/pageListOrderedItemText.html create mode 100644 data/core.telegram.org/constructor/paymentRequestedInfo.html create mode 100644 data/core.telegram.org/constructor/payments.paymentForm create mode 100644 data/core.telegram.org/constructor/payments.paymentResult create mode 100644 data/core.telegram.org/constructor/peerLocated.html create mode 100644 data/core.telegram.org/constructor/peerUser.html create mode 100644 data/core.telegram.org/constructor/phone.groupParticipants create mode 100644 data/core.telegram.org/constructor/phoneCallAccepted.html create mode 100644 data/core.telegram.org/constructor/photoPathSize.html create mode 100644 data/core.telegram.org/constructor/photoSizeEmpty.html create mode 100644 data/core.telegram.org/constructor/photoStrippedSize.html create mode 100644 data/core.telegram.org/constructor/photos.photo create mode 100644 data/core.telegram.org/constructor/pollAnswer.html create mode 100644 data/core.telegram.org/constructor/pollResults.html create mode 100644 data/core.telegram.org/constructor/postAddress.html create mode 100644 data/core.telegram.org/constructor/privacyKeyAddedByPhone.html create mode 100644 data/core.telegram.org/constructor/privacyValueAllowContacts.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlUnknown.html create mode 100644 data/core.telegram.org/constructor/recentMeUrlUser.html create mode 100644 data/core.telegram.org/constructor/replyInlineMarkup.html create mode 100644 data/core.telegram.org/constructor/replyKeyboardHide.html create mode 100644 data/core.telegram.org/constructor/secureFile.html create mode 100644 data/core.telegram.org/constructor/secureFileEmpty.html create mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html create mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html create mode 100644 data/core.telegram.org/constructor/securePlainPhone.html create mode 100644 data/core.telegram.org/constructor/secureRequiredType.html create mode 100644 data/core.telegram.org/constructor/secureSecretSettings.html create mode 100644 data/core.telegram.org/constructor/secureValue.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorData.html create mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeInternalPassport.html create mode 100644 data/core.telegram.org/constructor/secureValueTypePassport.html create mode 100644 data/core.telegram.org/constructor/secureValueTypePhone.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html create mode 100644 data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html create mode 100644 data/core.telegram.org/constructor/sendMessageChooseContactAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageRecordRoundAction.html create mode 100644 data/core.telegram.org/constructor/sendMessageUploadVideoAction.html create mode 100644 data/core.telegram.org/constructor/stats.broadcastStats create mode 100644 data/core.telegram.org/constructor/statsGroupTopAdmin.html create mode 100644 data/core.telegram.org/constructor/statsGroupTopInviter.html create mode 100644 data/core.telegram.org/constructor/statsGroupTopPoster.html create mode 100644 data/core.telegram.org/constructor/stickerSet.html create mode 100644 data/core.telegram.org/constructor/storage.filePartial create mode 100644 data/core.telegram.org/constructor/storage.filePng create mode 100644 data/core.telegram.org/constructor/storage.fileWebp create mode 100644 data/core.telegram.org/constructor/textAnchor.html create mode 100644 data/core.telegram.org/constructor/textMarked.html create mode 100644 data/core.telegram.org/constructor/textPlain.html create mode 100644 data/core.telegram.org/constructor/textSuperscript.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html create mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html create mode 100644 data/core.telegram.org/constructor/true.html create mode 100644 data/core.telegram.org/constructor/updateBotCallbackQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotInlineQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotInlineSend.html create mode 100644 data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html create mode 100644 data/core.telegram.org/constructor/updateBotShippingQuery.html create mode 100644 data/core.telegram.org/constructor/updateChannelAvailableMessages.html create mode 100644 data/core.telegram.org/constructor/updateChannelMessageViews.html create mode 100644 data/core.telegram.org/constructor/updateChannelUserTyping.html create mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdmin.html create mode 100644 data/core.telegram.org/constructor/updateDialogFilter.html create mode 100644 data/core.telegram.org/constructor/updateDialogPinned.html create mode 100644 data/core.telegram.org/constructor/updateGroupCallConnection.html create mode 100644 data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html create mode 100644 data/core.telegram.org/constructor/updateLangPack.html create mode 100644 data/core.telegram.org/constructor/updateNewMessage.html create mode 100644 data/core.telegram.org/constructor/updatePeerHistoryTTL.html create mode 100644 data/core.telegram.org/constructor/updatePhoneCallSignalingData.html create mode 100644 data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html create mode 100644 data/core.telegram.org/constructor/updateReadChannelOutbox.html create mode 100644 data/core.telegram.org/constructor/updateReadFeaturedStickers.html create mode 100644 data/core.telegram.org/constructor/updateShortSentMessage.html create mode 100644 data/core.telegram.org/constructor/updateTheme.html create mode 100644 data/core.telegram.org/constructor/updateUserBlocked.html create mode 100644 data/core.telegram.org/constructor/updateUserName.html create mode 100644 data/core.telegram.org/constructor/updates.differenceSlice create mode 100644 data/core.telegram.org/constructor/updates.state create mode 100644 data/core.telegram.org/constructor/userProfilePhoto.html create mode 100644 data/core.telegram.org/constructor/userProfilePhotoEmpty.html create mode 100644 data/core.telegram.org/constructor/userStatusLastMonth.html create mode 100644 data/core.telegram.org/constructor/userStatusOffline.html create mode 100644 data/core.telegram.org/constructor/userStatusOnline.html create mode 100644 data/core.telegram.org/constructor/vector.html create mode 100644 data/core.telegram.org/constructor/wallPaperSolid.html create mode 100644 data/core.telegram.org/constructor/webPageAttributeTheme.html create mode 100644 data/core.telegram.org/contest300K.html create mode 100644 data/core.telegram.org/getProxyConfig.html create mode 100644 data/core.telegram.org/import-stickers.html create mode 100644 data/core.telegram.org/method/account.acceptAuthorization create mode 100644 data/core.telegram.org/method/account.confirmPasswordEmail create mode 100644 data/core.telegram.org/method/account.confirmPhone create mode 100644 data/core.telegram.org/method/account.createTheme create mode 100644 data/core.telegram.org/method/account.finishTakeoutSession create mode 100644 data/core.telegram.org/method/account.getAuthorizationForm create mode 100644 data/core.telegram.org/method/account.getContactSignUpNotification create mode 100644 data/core.telegram.org/method/account.installWallPaper create mode 100644 data/core.telegram.org/method/account.reportPeer create mode 100644 data/core.telegram.org/method/account.resetWebAuthorizations create mode 100644 data/core.telegram.org/method/account.saveTheme create mode 100644 data/core.telegram.org/method/account.sendChangePhoneCode create mode 100644 data/core.telegram.org/method/account.sendConfirmPhoneCode create mode 100644 data/core.telegram.org/method/account.sendVerifyPhoneCode create mode 100644 data/core.telegram.org/method/account.setContactSignUpNotification create mode 100644 data/core.telegram.org/method/account.setContentSettings create mode 100644 data/core.telegram.org/method/account.setPrivacy create mode 100644 data/core.telegram.org/method/account.updateDeviceLocked create mode 100644 data/core.telegram.org/method/account.updatePasswordSettings create mode 100644 data/core.telegram.org/method/account.updateStatus create mode 100644 data/core.telegram.org/method/account.updateTheme create mode 100644 data/core.telegram.org/method/account.updateUsername create mode 100644 data/core.telegram.org/method/auth.bindTempAuthKey create mode 100644 data/core.telegram.org/method/auth.importBotAuthorization create mode 100644 data/core.telegram.org/method/auth.requestPasswordRecovery create mode 100644 data/core.telegram.org/method/auth.resetAuthorizations create mode 100644 data/core.telegram.org/method/auth.sendInvites create mode 100644 data/core.telegram.org/method/bots.resetBotCommands create mode 100644 data/core.telegram.org/method/channels.deleteHistory create mode 100644 data/core.telegram.org/method/channels.exportMessageLink create mode 100644 data/core.telegram.org/method/channels.getAdminLog create mode 100644 data/core.telegram.org/method/channels.getInactiveChannels create mode 100644 data/core.telegram.org/method/channels.getLeftChannels create mode 100644 data/core.telegram.org/method/channels.getParticipant create mode 100644 data/core.telegram.org/method/channels.getSponsoredMessages create mode 100644 data/core.telegram.org/method/channels.reportSpam create mode 100644 data/core.telegram.org/method/contacts.getBlocked create mode 100644 data/core.telegram.org/method/contacts.getContactIDs create mode 100644 data/core.telegram.org/method/contacts.getSaved create mode 100644 data/core.telegram.org/method/contacts.getStatuses create mode 100644 data/core.telegram.org/method/contacts.importContacts create mode 100644 data/core.telegram.org/method/contacts.resetSaved create mode 100644 data/core.telegram.org/method/folders.deleteFolder create mode 100644 data/core.telegram.org/method/help.acceptTermsOfService create mode 100644 data/core.telegram.org/method/help.getInviteText create mode 100644 data/core.telegram.org/method/help.getPromoData create mode 100644 data/core.telegram.org/method/help.getRecentMeUrls create mode 100644 data/core.telegram.org/method/help.getUserInfo create mode 100644 data/core.telegram.org/method/help.hidePromoData create mode 100644 data/core.telegram.org/method/help.saveAppLog create mode 100644 data/core.telegram.org/method/invokeAfterMsgs.html create mode 100644 data/core.telegram.org/method/langpack.getLangPack create mode 100644 data/core.telegram.org/method/messages.acceptEncryption create mode 100644 data/core.telegram.org/method/messages.acceptUrlAuth create mode 100644 data/core.telegram.org/method/messages.checkHistoryImport create mode 100644 data/core.telegram.org/method/messages.deleteExportedChatInvite create mode 100644 data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites create mode 100644 data/core.telegram.org/method/messages.discardEncryption create mode 100644 data/core.telegram.org/method/messages.editChatAbout create mode 100644 data/core.telegram.org/method/messages.editChatDefaultBannedRights create mode 100644 data/core.telegram.org/method/messages.editChatTitle create mode 100644 data/core.telegram.org/method/messages.forwardMessages create mode 100644 data/core.telegram.org/method/messages.getAdminsWithInvites create mode 100644 data/core.telegram.org/method/messages.getArchivedStickers create mode 100644 data/core.telegram.org/method/messages.getBotCallbackAnswer create mode 100644 data/core.telegram.org/method/messages.getChatInviteImporters create mode 100644 data/core.telegram.org/method/messages.getChats create mode 100644 data/core.telegram.org/method/messages.getDialogUnreadMarks create mode 100644 data/core.telegram.org/method/messages.getExportedChatInvite create mode 100644 data/core.telegram.org/method/messages.getFeaturedStickers create mode 100644 data/core.telegram.org/method/messages.getMessagesViews create mode 100644 data/core.telegram.org/method/messages.getOldFeaturedStickers create mode 100644 data/core.telegram.org/method/messages.getRecentLocations create mode 100644 data/core.telegram.org/method/messages.initHistoryImport create mode 100644 data/core.telegram.org/method/messages.readHistory create mode 100644 data/core.telegram.org/method/messages.receivedQueue create mode 100644 data/core.telegram.org/method/messages.reorderPinnedDialogs create mode 100644 data/core.telegram.org/method/messages.searchGifs create mode 100644 data/core.telegram.org/method/messages.sendEncrypted create mode 100644 data/core.telegram.org/method/messages.sendMultiMedia create mode 100644 data/core.telegram.org/method/messages.sendScheduledMessages create mode 100644 data/core.telegram.org/method/messages.setBotCallbackAnswer create mode 100644 data/core.telegram.org/method/messages.setChatTheme create mode 100644 data/core.telegram.org/method/messages.setHistoryTTL create mode 100644 data/core.telegram.org/method/messages.setInlineBotResults create mode 100644 data/core.telegram.org/method/messages.setInlineGameScore create mode 100644 data/core.telegram.org/method/messages.uninstallStickerSet create mode 100644 data/core.telegram.org/method/messages.updateDialogFilter create mode 100644 data/core.telegram.org/method/phone.acceptCall create mode 100644 data/core.telegram.org/method/phone.confirmCall create mode 100644 data/core.telegram.org/method/phone.createGroupCall create mode 100644 data/core.telegram.org/method/phone.editGroupCallParticipant create mode 100644 data/core.telegram.org/method/phone.exportGroupCallInvite create mode 100644 data/core.telegram.org/method/phone.getGroupCallJoinAs create mode 100644 data/core.telegram.org/method/phone.saveCallDebug create mode 100644 data/core.telegram.org/method/phone.setCallRating create mode 100644 data/core.telegram.org/method/photos.getUserPhotos create mode 100644 data/core.telegram.org/method/photos.uploadProfilePhoto create mode 100644 data/core.telegram.org/method/stats.getBroadcastStats create mode 100644 data/core.telegram.org/method/stats.loadAsyncGraph create mode 100644 data/core.telegram.org/method/stickers.checkShortName create mode 100644 data/core.telegram.org/method/upload.getFileHashes create mode 100644 data/core.telegram.org/methods.html create mode 100644 data/core.telegram.org/mtproto/TL-combinators.html create mode 100644 data/core.telegram.org/mtproto/TL-dependent.html create mode 100644 data/core.telegram.org/mtproto/TL-polymorph.html create mode 100644 data/core.telegram.org/mtproto/TL.html create mode 100644 data/core.telegram.org/mtproto/security_guidelines.html create mode 100644 data/core.telegram.org/passport/sdk-android.html create mode 100644 data/core.telegram.org/schema.html create mode 100644 data/core.telegram.org/schema/mtproto.html create mode 100644 data/core.telegram.org/techfaq.html create mode 100644 data/core.telegram.org/type/AccountDaysTTL.html create mode 100644 data/core.telegram.org/type/BankCardOpenUrl.html create mode 100644 data/core.telegram.org/type/Bool.html create mode 100644 data/core.telegram.org/type/CdnPublicKey.html create mode 100644 data/core.telegram.org/type/ChannelAdminLogEventsFilter.html create mode 100644 data/core.telegram.org/type/ChannelParticipant.html create mode 100644 data/core.telegram.org/type/ChatOnlines.html create mode 100644 data/core.telegram.org/type/DecryptedDataBlock.html create mode 100644 data/core.telegram.org/type/DecryptedMessage.html create mode 100644 data/core.telegram.org/type/Dialog.html create mode 100644 data/core.telegram.org/type/DisabledFeature.html create mode 100644 data/core.telegram.org/type/Document.html create mode 100644 data/core.telegram.org/type/DocumentAttribute.html create mode 100644 data/core.telegram.org/type/EmojiKeyword.html create mode 100644 data/core.telegram.org/type/EncryptedChat.html create mode 100644 data/core.telegram.org/type/EncryptedFile.html create mode 100644 data/core.telegram.org/type/EncryptedMessage.html create mode 100644 data/core.telegram.org/type/ExportedMessageLink.html create mode 100644 data/core.telegram.org/type/FileHash.html create mode 100644 data/core.telegram.org/type/Game.html create mode 100644 data/core.telegram.org/type/GeoPoint.html create mode 100644 data/core.telegram.org/type/GroupCall.html create mode 100644 data/core.telegram.org/type/GroupCallParticipant.html create mode 100644 data/core.telegram.org/type/GroupCallParticipantVideo.html create mode 100644 data/core.telegram.org/type/InputEncryptedChat.html create mode 100644 data/core.telegram.org/type/InputGeoPoint.html create mode 100644 data/core.telegram.org/type/InputMedia.html create mode 100644 data/core.telegram.org/type/InputPeer.html create mode 100644 data/core.telegram.org/type/InputPeerNotifySettings.html create mode 100644 data/core.telegram.org/type/LangPackLanguage.html create mode 100644 data/core.telegram.org/type/MaskCoords.html create mode 100644 data/core.telegram.org/type/MessageAction.html create mode 100644 data/core.telegram.org/type/MessageInteractionCounters.html create mode 100644 data/core.telegram.org/type/MessageMedia.html create mode 100644 data/core.telegram.org/type/MessageUserVote.html create mode 100644 data/core.telegram.org/type/NearestDc.html create mode 100644 data/core.telegram.org/type/PageCaption.html create mode 100644 data/core.telegram.org/type/PaymentSavedCredentials.html create mode 100644 data/core.telegram.org/type/Peer.html create mode 100644 data/core.telegram.org/type/PhoneCall.html create mode 100644 data/core.telegram.org/type/PhoneCallDiscardReason.html create mode 100644 data/core.telegram.org/type/PhoneCallProtocol.html create mode 100644 data/core.telegram.org/type/Poll.html create mode 100644 data/core.telegram.org/type/PostAddress.html create mode 100644 data/core.telegram.org/type/ReceivedNotifyMessage.html create mode 100644 data/core.telegram.org/type/ReplyMarkup.html create mode 100644 data/core.telegram.org/type/SecureData.html create mode 100644 data/core.telegram.org/type/SecureValue.html create mode 100644 data/core.telegram.org/type/SecureValueError.html create mode 100644 data/core.telegram.org/type/Theme.html create mode 100644 data/core.telegram.org/type/WebAuthorization.html create mode 100644 data/core.telegram.org/type/WebPageAttribute.html create mode 100644 data/core.telegram.org/type/account.Authorizations create mode 100644 data/core.telegram.org/type/account.ResetPasswordResult create mode 100644 data/core.telegram.org/type/account.SentChangePhoneCode create mode 100644 data/core.telegram.org/type/account.WebAuthorizations create mode 100644 data/core.telegram.org/type/auth.PasswordRecovery create mode 100644 data/core.telegram.org/type/auth.SentCodeType create mode 100644 data/core.telegram.org/type/bytes.html create mode 100644 data/core.telegram.org/type/double.html create mode 100644 data/core.telegram.org/type/help.Country create mode 100644 data/core.telegram.org/type/help.PromoData create mode 100644 data/core.telegram.org/type/messages.AffectedFoundMessages create mode 100644 data/core.telegram.org/type/messages.CheckedHistoryImportPeer create mode 100644 data/core.telegram.org/type/messages.ExportedChatInvite create mode 100644 data/core.telegram.org/type/messages.FavedStickers create mode 100644 data/core.telegram.org/type/messages.MessageEditData create mode 100644 data/core.telegram.org/type/messages.PeerDialogs create mode 100644 data/core.telegram.org/type/messages.SearchCounter create mode 100644 data/core.telegram.org/type/messages.SponsoredMessages create mode 100644 data/core.telegram.org/type/messages.StickerSet create mode 100644 data/core.telegram.org/type/payments.BankCardData create mode 100644 data/core.telegram.org/type/payments.PaymentReceipt create mode 100644 data/core.telegram.org/type/phone.ExportedGroupCallInvite create mode 100644 data/core.telegram.org/type/storage.FileType create mode 100644 data/core.telegram.org/type/string.html create mode 100644 data/core.telegram.org/type/upload.CdnFile create mode 100644 data/core.telegram.org/type/upload.File create mode 100644 data/corefork.telegram.org/api/end-to-end/voice-calls.html create mode 100644 data/corefork.telegram.org/api/files.html create mode 100644 data/corefork.telegram.org/api/import.html create mode 100644 data/corefork.telegram.org/api/poll.html create mode 100644 data/corefork.telegram.org/api/rights.html create mode 100644 data/corefork.telegram.org/api/threads.html create mode 100644 data/corefork.telegram.org/api/url-authorization.html create mode 100644 data/corefork.telegram.org/bots/samples/hellobot.html create mode 100644 data/corefork.telegram.org/bots/webhooks.html create mode 100644 data/corefork.telegram.org/constructor/account.resetPasswordFailedWait create mode 100644 data/corefork.telegram.org/constructor/account.themesNotModified create mode 100644 data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired create mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeCall create mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeSms create mode 100644 data/corefork.telegram.org/constructor/baseThemeArctic.html create mode 100644 data/corefork.telegram.org/constructor/baseThemeClassic.html create mode 100644 data/corefork.telegram.org/constructor/boolTrue.html create mode 100644 data/corefork.telegram.org/constructor/botCommandScopeDefault.html create mode 100644 data/corefork.telegram.org/constructor/botInlineResult.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEvent.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantAdmin.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsAdmins.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsRecent.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsSearch.html create mode 100644 data/corefork.telegram.org/constructor/chatAdminRights.html create mode 100644 data/corefork.telegram.org/constructor/chatBannedRights.html create mode 100644 data/corefork.telegram.org/constructor/chatInvitePeek.html create mode 100644 data/corefork.telegram.org/constructor/chatOnlines.html create mode 100644 data/corefork.telegram.org/constructor/codeSettings.html create mode 100644 data/corefork.telegram.org/constructor/contactStatus.html create mode 100644 data/corefork.telegram.org/constructor/contacts.blockedSlice create mode 100644 data/corefork.telegram.org/constructor/contacts.contacts create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionResend.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html create mode 100644 data/corefork.telegram.org/constructor/decryptedMessageService.html create mode 100644 data/corefork.telegram.org/constructor/dialog.html create mode 100644 data/corefork.telegram.org/constructor/dialogFilterSuggested.html create mode 100644 data/corefork.telegram.org/constructor/dialogPeerFolder.html create mode 100644 data/corefork.telegram.org/constructor/document.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeAudio.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeFilename.html create mode 100644 data/corefork.telegram.org/constructor/documentAttributeHasStickers.html create mode 100644 data/corefork.telegram.org/constructor/emojiLanguage.html create mode 100644 data/corefork.telegram.org/constructor/encryptedChatWaiting.html create mode 100644 data/corefork.telegram.org/constructor/fileLocationUnavailable.html create mode 100644 data/corefork.telegram.org/constructor/game.html create mode 100644 data/corefork.telegram.org/constructor/groupCall.html create mode 100644 data/corefork.telegram.org/constructor/help.appUpdate create mode 100644 data/corefork.telegram.org/constructor/help.countriesList create mode 100644 data/corefork.telegram.org/constructor/help.countriesListNotModified create mode 100644 data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty create mode 100644 data/corefork.telegram.org/constructor/help.noAppUpdate create mode 100644 data/corefork.telegram.org/constructor/help.passportConfig create mode 100644 data/corefork.telegram.org/constructor/help.support create mode 100644 data/corefork.telegram.org/constructor/help.supportName create mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html create mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResult.html create mode 100644 data/corefork.telegram.org/constructor/inputChannelEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputDocument.html create mode 100644 data/corefork.telegram.org/constructor/inputDocumentEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/inputGroupCallStream.html create mode 100644 data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html create mode 100644 data/corefork.telegram.org/constructor/inputMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputMessageReplyTo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html create mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html create mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html create mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonPornography.html create mode 100644 data/corefork.telegram.org/constructor/inputReportReasonSpam.html create mode 100644 data/corefork.telegram.org/constructor/inputSecureFileUploaded.html create mode 100644 data/corefork.telegram.org/constructor/inputSecureValue.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetID.html create mode 100644 data/corefork.telegram.org/constructor/inputStickerSetThumb.html create mode 100644 data/corefork.telegram.org/constructor/inputUserSelf.html create mode 100644 data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html create mode 100644 data/corefork.telegram.org/constructor/inputWebFileLocation.html create mode 100644 data/corefork.telegram.org/constructor/jsonArray.html create mode 100644 data/corefork.telegram.org/constructor/message.html create mode 100644 data/corefork.telegram.org/constructor/messageActionCustomAction.html create mode 100644 data/corefork.telegram.org/constructor/messageActionGameScore.html create mode 100644 data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html create mode 100644 data/corefork.telegram.org/constructor/messageActionSetChatTheme.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityBlockquote.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityBotCommand.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityItalic.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityStrike.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityUnderline.html create mode 100644 data/corefork.telegram.org/constructor/messageEntityUnknown.html create mode 100644 data/corefork.telegram.org/constructor/messageInteractionCounters.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaDocument.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaGame.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaGeo.html create mode 100644 data/corefork.telegram.org/constructor/messageMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/messageRange.html create mode 100644 data/corefork.telegram.org/constructor/messageReplies.html create mode 100644 data/corefork.telegram.org/constructor/messageService.html create mode 100644 data/corefork.telegram.org/constructor/messageUserVote.html create mode 100644 data/corefork.telegram.org/constructor/messageViews.html create mode 100644 data/corefork.telegram.org/constructor/messages.affectedFoundMessages create mode 100644 data/corefork.telegram.org/constructor/messages.affectedHistory create mode 100644 data/corefork.telegram.org/constructor/messages.allStickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.archivedStickers create mode 100644 data/corefork.telegram.org/constructor/messages.availableReactionsNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.botCallbackAnswer create mode 100644 data/corefork.telegram.org/constructor/messages.botResults create mode 100644 data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites create mode 100644 data/corefork.telegram.org/constructor/messages.chatFull create mode 100644 data/corefork.telegram.org/constructor/messages.dialogsNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.discussionMessage create mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced create mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInvites create mode 100644 data/corefork.telegram.org/constructor/messages.featuredStickersNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.historyImport create mode 100644 data/corefork.telegram.org/constructor/messages.inactiveChats create mode 100644 data/corefork.telegram.org/constructor/messages.messages create mode 100644 data/corefork.telegram.org/constructor/messages.messagesSlice create mode 100644 data/corefork.telegram.org/constructor/messages.savedGifs create mode 100644 data/corefork.telegram.org/constructor/messages.sponsoredMessages create mode 100644 data/corefork.telegram.org/constructor/messages.stickerSetNotModified create mode 100644 data/corefork.telegram.org/constructor/messages.votesList create mode 100644 data/corefork.telegram.org/constructor/notifyPeer.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockCover.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockDivider.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockList.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockPullquote.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockSubtitle.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockTable.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockUnsupported.html create mode 100644 data/corefork.telegram.org/constructor/pageBlockVideo.html create mode 100644 data/corefork.telegram.org/constructor/paymentCharge.html create mode 100644 data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded create mode 100644 data/corefork.telegram.org/constructor/peerChannel.html create mode 100644 data/corefork.telegram.org/constructor/peerNotifySettings.html create mode 100644 data/corefork.telegram.org/constructor/peerSettings.html create mode 100644 data/corefork.telegram.org/constructor/phone.phoneCall create mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html create mode 100644 data/corefork.telegram.org/constructor/photoCachedSize.html create mode 100644 data/corefork.telegram.org/constructor/photoSizeEmpty.html create mode 100644 data/corefork.telegram.org/constructor/photos.photos create mode 100644 data/corefork.telegram.org/constructor/pollAnswer.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyChatInvite.html create mode 100644 data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html create mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlUnknown.html create mode 100644 data/corefork.telegram.org/constructor/recentMeUrlUser.html create mode 100644 data/corefork.telegram.org/constructor/replyKeyboardMarkup.html create mode 100644 data/corefork.telegram.org/constructor/searchResultPosition.html create mode 100644 data/corefork.telegram.org/constructor/searchResultsCalendarPeriod.html create mode 100644 data/corefork.telegram.org/constructor/secureData.html create mode 100644 data/corefork.telegram.org/constructor/secureFileEmpty.html create mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html create mode 100644 data/corefork.telegram.org/constructor/securePlainPhone.html create mode 100644 data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFiles.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html create mode 100644 data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html create mode 100644 data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageTypingAction.html create mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html create mode 100644 data/corefork.telegram.org/constructor/speakingInGroupCallAction.html create mode 100644 data/corefork.telegram.org/constructor/stats.broadcastStats create mode 100644 data/corefork.telegram.org/constructor/statsGraphAsync.html create mode 100644 data/corefork.telegram.org/constructor/statsURL.html create mode 100644 data/corefork.telegram.org/constructor/stickerSetCovered.html create mode 100644 data/corefork.telegram.org/constructor/stickerSetMultiCovered.html create mode 100644 data/corefork.telegram.org/constructor/stickers.suggestedShortName create mode 100644 data/corefork.telegram.org/constructor/textAnchor.html create mode 100644 data/corefork.telegram.org/constructor/textItalic.html create mode 100644 data/corefork.telegram.org/constructor/textUnderline.html create mode 100644 data/corefork.telegram.org/constructor/textUrl.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html create mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryPeers.html create mode 100644 data/corefork.telegram.org/constructor/true.html create mode 100644 data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html create mode 100644 data/corefork.telegram.org/constructor/updateBotShippingQuery.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelMessageViews.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelParticipant.html create mode 100644 data/corefork.telegram.org/constructor/updateChannelWebPage.html create mode 100644 data/corefork.telegram.org/constructor/updateChatParticipants.html create mode 100644 data/corefork.telegram.org/constructor/updateContactsReset.html create mode 100644 data/corefork.telegram.org/constructor/updateDcOptions.html create mode 100644 data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogFilter.html create mode 100644 data/corefork.telegram.org/constructor/updateDialogFilterOrder.html create mode 100644 data/corefork.telegram.org/constructor/updateFavedStickers.html create mode 100644 data/corefork.telegram.org/constructor/updateLoginToken.html create mode 100644 data/corefork.telegram.org/constructor/updateMessagePoll.html create mode 100644 data/corefork.telegram.org/constructor/updateNewChannelMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateNotifySettings.html create mode 100644 data/corefork.telegram.org/constructor/updatePendingJoinRequests.html create mode 100644 data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html create mode 100644 data/corefork.telegram.org/constructor/updatePinnedMessages.html create mode 100644 data/corefork.telegram.org/constructor/updateReadHistoryInbox.html create mode 100644 data/corefork.telegram.org/constructor/updateSavedGifs.html create mode 100644 data/corefork.telegram.org/constructor/updateShortChatMessage.html create mode 100644 data/corefork.telegram.org/constructor/updateStickerSetsOrder.html create mode 100644 data/corefork.telegram.org/constructor/updateUserName.html create mode 100644 data/corefork.telegram.org/constructor/updateUserTyping.html create mode 100644 data/corefork.telegram.org/constructor/updateWebPage.html create mode 100644 data/corefork.telegram.org/constructor/updates.differenceSlice create mode 100644 data/corefork.telegram.org/constructor/updates.differenceTooLong create mode 100644 data/corefork.telegram.org/constructor/upload.cdnFile create mode 100644 data/corefork.telegram.org/constructor/upload.file create mode 100644 data/corefork.telegram.org/constructor/urlAuthResultRequest.html create mode 100644 data/corefork.telegram.org/constructor/userEmpty.html create mode 100644 data/corefork.telegram.org/constructor/userStatusLastWeek.html create mode 100644 data/corefork.telegram.org/constructor/vector.html create mode 100644 data/corefork.telegram.org/constructor/wallPaper.html create mode 100644 data/corefork.telegram.org/constructor/wallPaperNoFile.html create mode 100644 data/corefork.telegram.org/constructor/webPageEmpty.html create mode 100644 data/corefork.telegram.org/getProxyConfig.html create mode 100644 data/corefork.telegram.org/method/account.changePhone create mode 100644 data/corefork.telegram.org/method/account.confirmPhone create mode 100644 data/corefork.telegram.org/method/account.getContactSignUpNotification create mode 100644 data/corefork.telegram.org/method/account.getContentSettings create mode 100644 data/corefork.telegram.org/method/account.getMultiWallPapers create mode 100644 data/corefork.telegram.org/method/account.getTmpPassword create mode 100644 data/corefork.telegram.org/method/account.installTheme create mode 100644 data/corefork.telegram.org/method/account.registerDevice create mode 100644 data/corefork.telegram.org/method/account.reportPeer create mode 100644 data/corefork.telegram.org/method/account.reportProfilePhoto create mode 100644 data/corefork.telegram.org/method/account.saveWallPaper create mode 100644 data/corefork.telegram.org/method/account.setAuthorizationTTL create mode 100644 data/corefork.telegram.org/method/account.updateProfile create mode 100644 data/corefork.telegram.org/method/account.uploadWallPaper create mode 100644 data/corefork.telegram.org/method/auth.acceptLoginToken create mode 100644 data/corefork.telegram.org/method/auth.bindTempAuthKey create mode 100644 data/corefork.telegram.org/method/auth.cancelCode create mode 100644 data/corefork.telegram.org/method/auth.checkPassword create mode 100644 data/corefork.telegram.org/method/auth.exportLoginToken create mode 100644 data/corefork.telegram.org/method/auth.importBotAuthorization create mode 100644 data/corefork.telegram.org/method/auth.requestPasswordRecovery create mode 100644 data/corefork.telegram.org/method/auth.sendCall create mode 100644 data/corefork.telegram.org/method/auth.sendSms create mode 100644 data/corefork.telegram.org/method/bots.sendCustomRequest create mode 100644 data/corefork.telegram.org/method/channels.createChannel create mode 100644 data/corefork.telegram.org/method/channels.deleteUserHistory create mode 100644 data/corefork.telegram.org/method/channels.editAdmin create mode 100644 data/corefork.telegram.org/method/channels.editTitle create mode 100644 data/corefork.telegram.org/method/channels.exportMessageLink create mode 100644 data/corefork.telegram.org/method/channels.getAdminedPublicChannels create mode 100644 data/corefork.telegram.org/method/channels.getGroupsForDiscussion create mode 100644 data/corefork.telegram.org/method/channels.getParticipants create mode 100644 data/corefork.telegram.org/method/contacts.acceptContact create mode 100644 data/corefork.telegram.org/method/contacts.addContact create mode 100644 data/corefork.telegram.org/method/contacts.block create mode 100644 data/corefork.telegram.org/method/contacts.deleteByPhones create mode 100644 data/corefork.telegram.org/method/contacts.getContactIDs create mode 100644 data/corefork.telegram.org/method/contacts.getContacts create mode 100644 data/corefork.telegram.org/method/contacts.getStatuses create mode 100644 data/corefork.telegram.org/method/contacts.getTopPeers create mode 100644 data/corefork.telegram.org/method/contacts.resolveUsername create mode 100644 data/corefork.telegram.org/method/folders.editPeerFolders create mode 100644 data/corefork.telegram.org/method/help.dismissSuggestion create mode 100644 data/corefork.telegram.org/method/help.getDeepLinkInfo create mode 100644 data/corefork.telegram.org/method/help.getNearestDc create mode 100644 data/corefork.telegram.org/method/help.getProxyData create mode 100644 data/corefork.telegram.org/method/initConnection.html create mode 100644 data/corefork.telegram.org/method/invokeAfterMsgs.html create mode 100644 data/corefork.telegram.org/method/invokeWithLayer.html create mode 100644 data/corefork.telegram.org/method/invokeWithMessagesRange.html create mode 100644 data/corefork.telegram.org/method/langpack.getLanguage create mode 100644 data/corefork.telegram.org/method/langpack.getLanguages create mode 100644 data/corefork.telegram.org/method/langpack.getStrings create mode 100644 data/corefork.telegram.org/method/messages.clearAllDrafts create mode 100644 data/corefork.telegram.org/method/messages.createChat create mode 100644 data/corefork.telegram.org/method/messages.deleteMessages create mode 100644 data/corefork.telegram.org/method/messages.discardEncryption create mode 100644 data/corefork.telegram.org/method/messages.editChatAdmin create mode 100644 data/corefork.telegram.org/method/messages.editChatPhoto create mode 100644 data/corefork.telegram.org/method/messages.editExportedChatInvite create mode 100644 data/corefork.telegram.org/method/messages.forwardMessage create mode 100644 data/corefork.telegram.org/method/messages.forwardMessages create mode 100644 data/corefork.telegram.org/method/messages.getArchivedStickers create mode 100644 data/corefork.telegram.org/method/messages.getAvailableReactions create mode 100644 data/corefork.telegram.org/method/messages.getDhConfig create mode 100644 data/corefork.telegram.org/method/messages.getDialogFilters create mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywords create mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference create mode 100644 data/corefork.telegram.org/method/messages.getHistory create mode 100644 data/corefork.telegram.org/method/messages.getInlineGameHighScores create mode 100644 data/corefork.telegram.org/method/messages.getMessagesViews create mode 100644 data/corefork.telegram.org/method/messages.getScheduledHistory create mode 100644 data/corefork.telegram.org/method/messages.getSearchResultsPositions create mode 100644 data/corefork.telegram.org/method/messages.getWebPage create mode 100644 data/corefork.telegram.org/method/messages.markDialogUnread create mode 100644 data/corefork.telegram.org/method/messages.readMentions create mode 100644 data/corefork.telegram.org/method/messages.readReactions create mode 100644 data/corefork.telegram.org/method/messages.requestEncryption create mode 100644 data/corefork.telegram.org/method/messages.saveDraft create mode 100644 data/corefork.telegram.org/method/messages.saveRecentSticker create mode 100644 data/corefork.telegram.org/method/messages.search create mode 100644 data/corefork.telegram.org/method/messages.searchGifs create mode 100644 data/corefork.telegram.org/method/messages.searchGlobal create mode 100644 data/corefork.telegram.org/method/messages.sendMedia create mode 100644 data/corefork.telegram.org/method/messages.sendScreenshotNotification create mode 100644 data/corefork.telegram.org/method/messages.sendVote create mode 100644 data/corefork.telegram.org/method/messages.setChatAvailableReactions create mode 100644 data/corefork.telegram.org/method/messages.setInlineBotResults create mode 100644 data/corefork.telegram.org/method/messages.toggleStickerSets create mode 100644 data/corefork.telegram.org/method/messages.translateText create mode 100644 data/corefork.telegram.org/method/messages.updateDialogFiltersOrder create mode 100644 data/corefork.telegram.org/method/payments.getPaymentForm create mode 100644 data/corefork.telegram.org/method/payments.getPaymentReceipt create mode 100644 data/corefork.telegram.org/method/phone.confirmCall create mode 100644 data/corefork.telegram.org/method/phone.getCallConfig create mode 100644 data/corefork.telegram.org/method/phone.getGroupCall create mode 100644 data/corefork.telegram.org/method/phone.leaveGroupCall create mode 100644 data/corefork.telegram.org/method/phone.setCallRating create mode 100644 data/corefork.telegram.org/method/phone.startScheduledGroupCall create mode 100644 data/corefork.telegram.org/method/phone.toggleGroupCallRecord create mode 100644 data/corefork.telegram.org/method/stats.getMegagroupStats create mode 100644 data/corefork.telegram.org/method/stats.getMessagePublicForwards create mode 100644 data/corefork.telegram.org/method/stats.loadAsyncGraph create mode 100644 data/corefork.telegram.org/method/stickers.suggestShortName create mode 100644 data/corefork.telegram.org/method/upload.getWebFile create mode 100644 data/corefork.telegram.org/method/upload.saveBigFilePart create mode 100644 data/corefork.telegram.org/method/users.getFullUser create mode 100644 data/corefork.telegram.org/mtproto/TL-combinators.html create mode 100644 data/corefork.telegram.org/mtproto/TL-types.html create mode 100644 data/corefork.telegram.org/mtproto/mtproto-transports.html create mode 100644 data/corefork.telegram.org/mtproto/samples-auth_key.html create mode 100644 data/corefork.telegram.org/mtproto/security_guidelines.html create mode 100644 data/corefork.telegram.org/mtproto/serialize.html create mode 100644 data/corefork.telegram.org/passport/encryption.html create mode 100644 data/corefork.telegram.org/passport/example.html create mode 100644 data/corefork.telegram.org/passport/sdk-android.html create mode 100644 data/corefork.telegram.org/passport/sdk-javascript.html create mode 100644 data/corefork.telegram.org/schema/json.html create mode 100644 data/corefork.telegram.org/type/BotInlineMessage.html create mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEvent.html create mode 100644 data/corefork.telegram.org/type/ChannelLocation.html create mode 100644 data/corefork.telegram.org/type/ChannelMessagesFilter.html create mode 100644 data/corefork.telegram.org/type/ChannelParticipant.html create mode 100644 data/corefork.telegram.org/type/Chat.html create mode 100644 data/corefork.telegram.org/type/ChatAdminRights.html create mode 100644 data/corefork.telegram.org/type/ChatInviteImporter.html create mode 100644 data/corefork.telegram.org/type/ChatTheme.html create mode 100644 data/corefork.telegram.org/type/Config.html create mode 100644 data/corefork.telegram.org/type/Contact.html create mode 100644 data/corefork.telegram.org/type/ContactStatus.html create mode 100644 data/corefork.telegram.org/type/EncryptedChat.html create mode 100644 data/corefork.telegram.org/type/EncryptedMessage.html create mode 100644 data/corefork.telegram.org/type/GroupCall.html create mode 100644 data/corefork.telegram.org/type/InputBotInlineResult.html create mode 100644 data/corefork.telegram.org/type/InputCheckPasswordSRP.html create mode 100644 data/corefork.telegram.org/type/InputFileLocation.html create mode 100644 data/corefork.telegram.org/type/InputGeoPoint.html create mode 100644 data/corefork.telegram.org/type/InputPeerNotifySettings.html create mode 100644 data/corefork.telegram.org/type/InputSecureValue.html create mode 100644 data/corefork.telegram.org/type/InputSingleMedia.html create mode 100644 data/corefork.telegram.org/type/InputStickerSetItem.html create mode 100644 data/corefork.telegram.org/type/InputTheme.html create mode 100644 data/corefork.telegram.org/type/InputWebDocument.html create mode 100644 data/corefork.telegram.org/type/InputWebFileLocation.html create mode 100644 data/corefork.telegram.org/type/Invoice.html create mode 100644 data/corefork.telegram.org/type/LabeledPrice.html create mode 100644 data/corefork.telegram.org/type/LangPackLanguage.html create mode 100644 data/corefork.telegram.org/type/LangPackString.html create mode 100644 data/corefork.telegram.org/type/Message.html create mode 100644 data/corefork.telegram.org/type/MessageEntity.html create mode 100644 data/corefork.telegram.org/type/MessageReplyHeader.html create mode 100644 data/corefork.telegram.org/type/MessageViews.html create mode 100644 data/corefork.telegram.org/type/PageCaption.html create mode 100644 data/corefork.telegram.org/type/PageListItem.html create mode 100644 data/corefork.telegram.org/type/PageRelatedArticle.html create mode 100644 data/corefork.telegram.org/type/PaymentRequestedInfo.html create mode 100644 data/corefork.telegram.org/type/PaymentSavedCredentials.html create mode 100644 data/corefork.telegram.org/type/PhoneCall.html create mode 100644 data/corefork.telegram.org/type/PhoneConnection.html create mode 100644 data/corefork.telegram.org/type/PhotoSize.html create mode 100644 data/corefork.telegram.org/type/PollAnswer.html create mode 100644 data/corefork.telegram.org/type/PostAddress.html create mode 100644 data/corefork.telegram.org/type/ReactionCount.html create mode 100644 data/corefork.telegram.org/type/ReceivedNotifyMessage.html create mode 100644 data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html create mode 100644 data/corefork.telegram.org/type/SendMessageAction.html create mode 100644 data/corefork.telegram.org/type/StatsAbsValueAndPrev.html create mode 100644 data/corefork.telegram.org/type/StatsPercentValue.html create mode 100644 data/corefork.telegram.org/type/StickerSet.html create mode 100644 data/corefork.telegram.org/type/TopPeerCategoryPeers.html create mode 100644 data/corefork.telegram.org/type/UserStatus.html create mode 100644 data/corefork.telegram.org/type/VideoSize.html create mode 100644 data/corefork.telegram.org/type/WallPaperSettings.html create mode 100644 data/corefork.telegram.org/type/WebPage.html create mode 100644 data/corefork.telegram.org/type/account.ChatThemes create mode 100644 data/corefork.telegram.org/type/account.Password create mode 100644 data/corefork.telegram.org/type/account.PasswordInputSettings create mode 100644 data/corefork.telegram.org/type/account.PasswordSettings create mode 100644 data/corefork.telegram.org/type/account.ResetPasswordResult create mode 100644 data/corefork.telegram.org/type/account.WallPapers create mode 100644 data/corefork.telegram.org/type/auth.CheckedPhone create mode 100644 data/corefork.telegram.org/type/auth.LoginToken create mode 100644 data/corefork.telegram.org/type/contacts.ImportedContacts create mode 100644 data/corefork.telegram.org/type/contacts.TopPeers create mode 100644 data/corefork.telegram.org/type/help.CountriesList create mode 100644 data/corefork.telegram.org/type/help.Country create mode 100644 data/corefork.telegram.org/type/messages.BotCallbackAnswer create mode 100644 data/corefork.telegram.org/type/messages.ChatInviteImporters create mode 100644 data/corefork.telegram.org/type/messages.DiscussionMessage create mode 100644 data/corefork.telegram.org/type/messages.ExportedChatInvite create mode 100644 data/corefork.telegram.org/type/messages.ExportedChatInvites create mode 100644 data/corefork.telegram.org/type/messages.FavedStickers create mode 100644 data/corefork.telegram.org/type/messages.HighScores create mode 100644 data/corefork.telegram.org/type/messages.PeerDialogs create mode 100644 data/corefork.telegram.org/type/messages.PeerSettings create mode 100644 data/corefork.telegram.org/type/messages.RecentStickers create mode 100644 data/corefork.telegram.org/type/messages.SearchResultsCalendar create mode 100644 data/corefork.telegram.org/type/messages.SearchResultsPositions create mode 100644 data/corefork.telegram.org/type/photos.Photos create mode 100644 data/corefork.telegram.org/type/stats.BroadcastStats create mode 100644 data/corefork.telegram.org/type/storage.FileType create mode 100644 data/corefork.telegram.org/type/updates.ChannelDifference create mode 100644 data/corefork.telegram.org/type/users.UserFull create mode 100644 data/corefork.telegram.org/widgets/post.html create mode 100644 data/corefork.telegram.org/widgets/share.html create mode 100644 data/desktop.telegram.org.html create mode 100644 data/desktop.telegram.org/changelog.html create mode 100644 data/instantview.telegram.org.html create mode 100644 data/instantview.telegram.org/auth.html create mode 100644 data/instantview.telegram.org/checklist.html create mode 100644 data/instantview.telegram.org/docs.html create mode 100644 data/instantview.telegram.org/rules.html create mode 100644 data/instantview.telegram.org/samples.html create mode 100644 data/instantview.telegram.org/templates.html create mode 100644 data/macos.telegram.org.html create mode 100644 data/promote.telegram.org.html create mode 100644 data/promote.telegram.org/auth.html create mode 100644 data/promote.telegram.org/basics.html create mode 100644 data/promote.telegram.org/getting-started.html create mode 100644 data/promote.telegram.org/guidelines.html create mode 100644 data/promote.telegram.org/tos.html create mode 100644 data/telegram.org.html create mode 100644 data/telegram.org/android.html create mode 100644 data/telegram.org/api.html create mode 100644 data/telegram.org/apple_privacy.html create mode 100644 data/telegram.org/blog.html create mode 100644 data/telegram.org/blog/200-million.html create mode 100644 data/telegram.org/blog/400-million.html create mode 100644 data/telegram.org/blog/6-years.html create mode 100644 data/telegram.org/blog/admin-revolution.html create mode 100644 data/telegram.org/blog/albums-saved-messages.html create mode 100644 data/telegram.org/blog/android-2-0.html create mode 100644 data/telegram.org/blog/android-gif.html create mode 100644 data/telegram.org/blog/android-streaming.html create mode 100644 data/telegram.org/blog/android-themes.html create mode 100644 data/telegram.org/blog/android-wear-2-0.html create mode 100644 data/telegram.org/blog/animated-backgrounds.html create mode 100644 data/telegram.org/blog/animated-stickers.html create mode 100644 data/telegram.org/blog/apple-watch.html create mode 100644 data/telegram.org/blog/autodelete-inv2.html create mode 100644 data/telegram.org/blog/autoplay.html create mode 100644 data/telegram.org/blog/backgrounds-2-0.html create mode 100644 data/telegram.org/blog/bot-revolution.html create mode 100644 data/telegram.org/blog/bots-2-0.html create mode 100644 data/telegram.org/blog/cache-and-stickers.html create mode 100644 data/telegram.org/blog/calls.html create mode 100644 data/telegram.org/blog/captions-places.html create mode 100644 data/telegram.org/blog/channels-2-0.html create mode 100644 data/telegram.org/blog/channels.html create mode 100644 data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html create mode 100644 data/telegram.org/blog/contacts-local-groups.html create mode 100644 data/telegram.org/blog/coronavirus.html create mode 100644 data/telegram.org/blog/crowdsourcing-a-more-secure-future.html create mode 100644 data/telegram.org/blog/cryptocontest-ends.html create mode 100644 data/telegram.org/blog/cryptocontest.html create mode 100644 data/telegram.org/blog/desktop-1-0.html create mode 100644 data/telegram.org/blog/desktop-compact.html create mode 100644 data/telegram.org/blog/discover-stickers-and-more.html create mode 100644 data/telegram.org/blog/drafts.html create mode 100644 data/telegram.org/blog/edit.html create mode 100644 data/telegram.org/blog/encrypted-cdns.html create mode 100644 data/telegram.org/blog/export-and-more.html create mode 100644 data/telegram.org/blog/files-on-steroids.html create mode 100644 data/telegram.org/blog/filters-anonymous-admins-comments.html create mode 100644 data/telegram.org/blog/folders.html create mode 100644 data/telegram.org/blog/games.html create mode 100644 data/telegram.org/blog/gif-revolution.html create mode 100644 data/telegram.org/blog/gifs.html create mode 100644 data/telegram.org/blog/inline-bots.html create mode 100644 data/telegram.org/blog/instant-camera.html create mode 100644 data/telegram.org/blog/instant-view-contest-200K.html create mode 100644 data/telegram.org/blog/invite-links.html create mode 100644 data/telegram.org/blog/link-preview.html create mode 100644 data/telegram.org/blog/live-locations.html create mode 100644 data/telegram.org/blog/live-streams-forwarding-next-channel.html create mode 100644 data/telegram.org/blog/login.html create mode 100644 data/telegram.org/blog/masks.html create mode 100644 data/telegram.org/blog/moar-stickers.html create mode 100644 data/telegram.org/blog/move-history.html create mode 100644 data/telegram.org/blog/new-profiles-people-nearby.html create mode 100644 data/telegram.org/blog/now-you-see-me.html create mode 100644 data/telegram.org/blog/passport.html create mode 100644 data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html create mode 100644 data/telegram.org/blog/payments.html create mode 100644 data/telegram.org/blog/permissions-groups-undo.html create mode 100644 data/telegram.org/blog/photo-editor-and-passcodes.html create mode 100644 data/telegram.org/blog/pin-and-ifttt.html create mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists.html create mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists/world.html create mode 100644 data/telegram.org/blog/polls-2-0-vmq.html create mode 100644 data/telegram.org/blog/polls.html create mode 100644 data/telegram.org/blog/privacy-discussions-web-bots.html create mode 100644 data/telegram.org/blog/privacy-revolution.html create mode 100644 data/telegram.org/blog/profile-videos-people-nearby-and-more.html create mode 100644 data/telegram.org/blog/protected-content-delete-by-date-and-more.html create mode 100644 data/telegram.org/blog/replies-mentions-hashtags.html create mode 100644 data/telegram.org/blog/replies-mentions-stickers.html create mode 100644 data/telegram.org/blog/scheduled-reminders-themes.html create mode 100644 data/telegram.org/blog/search-and-media.html create mode 100644 data/telegram.org/blog/sessions-and-2-step-verification.html create mode 100644 data/telegram.org/blog/share-preview.html create mode 100644 data/telegram.org/blog/shared-files.html create mode 100644 data/telegram.org/blog/shared-links.html create mode 100644 data/telegram.org/blog/silent-messages-slow-mode.html create mode 100644 data/telegram.org/blog/stickers-meet-art-and-history.html create mode 100644 data/telegram.org/blog/stickers-revolution.html create mode 100644 data/telegram.org/blog/stickers.html create mode 100644 data/telegram.org/blog/supergroups.html create mode 100644 data/telegram.org/blog/supergroups5k.html create mode 100644 data/telegram.org/blog/tdlib.html create mode 100644 data/telegram.org/blog/telegram-5-ios.html create mode 100644 data/telegram.org/blog/telegram-me-change-number-and-pfs.html create mode 100644 data/telegram.org/blog/telegram-x.html create mode 100644 data/telegram.org/blog/telegraph.html create mode 100644 data/telegram.org/blog/themes-accounts.html create mode 100644 data/telegram.org/blog/translations-iv2.html create mode 100644 data/telegram.org/blog/trending-stickers.html create mode 100644 data/telegram.org/blog/unread-replace-2x.html create mode 100644 data/telegram.org/blog/unsend-and-usage.html create mode 100644 data/telegram.org/blog/unsend-privacy-emoji.html create mode 100644 data/telegram.org/blog/usernames-and-secret-chats-v2.html create mode 100644 data/telegram.org/blog/verifiable-apps-and-more.html create mode 100644 data/telegram.org/blog/video-1000.html create mode 100644 data/telegram.org/blog/video-calls.html create mode 100644 data/telegram.org/blog/video-editor-gifs.html create mode 100644 data/telegram.org/blog/video-messages-and-telescope.html create mode 100644 data/telegram.org/blog/video-stickers-better-reactions.html create mode 100644 data/telegram.org/blog/voice-2-secret-3.html create mode 100644 data/telegram.org/blog/voice-chats-on-steroids.html create mode 100644 data/telegram.org/blog/voice-chats.html create mode 100644 data/telegram.org/blog/winter-contest-ends.html create mode 100644 data/telegram.org/evolution.html create mode 100644 data/telegram.org/faq.html create mode 100644 data/telegram.org/faq_channels.html create mode 100644 data/telegram.org/faq_spam.html create mode 100644 data/telegram.org/jobs.html create mode 100644 data/telegram.org/press.html create mode 100644 data/telegram.org/privacy.html create mode 100644 data/telegram.org/privacy/gmailbot.html create mode 100644 data/telegram.org/support.html create mode 100644 data/telegram.org/teststore.html create mode 100644 data/telegram.org/tos.html create mode 100644 data/telegram.org/tour.html create mode 100644 data/telegram.org/tour/channels.html create mode 100644 data/telegram.org/tour/groups.html create mode 100644 data/telegram.org/tour/quizbot.html create mode 100644 data/telegram.org/tour/screenshots.html create mode 100644 data/telegram.org/verify.html create mode 100644 data/telegram.org/what-can-you-do-with-Telegram.html create mode 100644 data/themes.telegram.org.html create mode 100644 data/themes.telegram.org/auth.html create mode 100644 data/translations.telegram.org.html create mode 100644 data/translations.telegram.org/en.html create mode 100644 data/translations.telegram.org/en/android.html create mode 100644 data/translations.telegram.org/en/android_x.html create mode 100644 data/translations.telegram.org/en/ios.html create mode 100644 data/translations.telegram.org/en/macos.html create mode 100644 data/translations.telegram.org/en/tdesktop.html create mode 100644 data/tsf.telegram.org.html create mode 100644 data/tsf.telegram.org/auth.html create mode 100644 data/tsf.telegram.org/manuals.html create mode 100644 data/tsf.telegram.org/manuals/answering_questions.html create mode 100644 data/tsf.telegram.org/manuals/bios.html create mode 100644 data/tsf.telegram.org/manuals/bug_herding.html create mode 100644 data/tsf.telegram.org/manuals/bug_hunting.html create mode 100644 data/tsf.telegram.org/manuals/bugs.html create mode 100644 data/tsf.telegram.org/manuals/come-and-go.html create mode 100644 data/tsf.telegram.org/manuals/e2ee-simple.html create mode 100644 data/tsf.telegram.org/manuals/e2ee.html create mode 100644 data/tsf.telegram.org/manuals/feature_philosophy.html diff --git a/data/contest.com.html b/data/contest.com.html new file mode 100644 index 0000000000..2ffb45b45d --- /dev/null +++ b/data/contest.com.html @@ -0,0 +1,291 @@ + + + + + Developer Challenges + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+ +
+
+
+
+
+ +
+

Recent News

+

Subscribe to the Telegram Contests channel for the latest updates and information about ongoing competitions.

+

About this Platform

+

Everybody is welcome to try out works submitted by the contestants and create issues (with supporting videos and screenshots) if they encounter any problems.

+


+ +

Contestants can respond to issues. They appear on the platform under animal aliases to ensure fairness and transparency in testing. Admins will be around to do their own checks on the apps and tally up the results.

+


+ +

If you're looking for information about contests that are currently open, check the Telegram Contests channel.

+
+
+
+ +

Contests

+ +
Windows 11 Design Contest. $40,000New
+
Dec 30, 2021 – Jan 22
+
+
GIF Contest, Round 2. $50,000New
+
Sep 8 – Nov 9, 2021
+
+
November 2021 Android Contest, Round 2. $50,000
+
Nov 26 – Dec 6, 2021
+
+
November 2021 Android Contest. $50,000
+
Nov 5 – Nov 15, 2021
+
+
Android Design Contest. $30,000
+
Jul 8 – Aug 1, 2021
+
+
Sticker App Contest. $50,000
+
Jun 25 – Jul 4, 2021
+
+
iOS Contest, Round 3 (watchOS)
+
May 19 – Jun 6, 2021
+
+
Data Clustering Contest 2021, Round 2. $50,000
+
Apr 17 – May 2, 2021
+
+
Android Contest 2021, Round 2. $50,000
+
Mar 19 – Apr 4, 2021
+
+
GIF Contest, Round 1. $50,000
+
Mar 17 – Mar 31, 2021
+
+
Animated Sticker Contest 2021. $50,000
+
Mar 11 – Mar 26, 2021
+
+
watchOS Contest 2021. $47,000
+
Mar 5 – Mar 21, 2021
+
+
Android Contest 2021. $60,000
+
Jan 30 – Feb 14, 2021
+
+
iOS Animation Contest 2021. $50,000
+
Jan 15 – Jan 31, 2021
+
+
Aptitude Test Contest. €250,000
+
Dec 31, 2020 – Jan 9, 2021
+
+
JavaScript Contest, Bonus Round
+
Aug 18 – Sep 1, 2020
+
+
JavaScript Contest, Stage 3
+
May 30 – Jun 20, 2020
+
+
Data Clustering Contest, Stage 2. €100,000
+
May 11 – May 25, 2020
+
+
VoIP Contest, Stage 3. €50,000
+
Mar 9 – Mar 30, 2020
+
+
Blockchain Contest, Stage 2: Bonus Prize €80,000
+
Mar 6 – Mar 20, 2020
+
+
JavaScript Contest, Stage 2
+
Jan 31 – Feb 15, 2020
+
+
VoIP Contest, Stage 2. $75,000
+
Jan 14 – Jan 29, 2020
+
+
Blockchain Contest, Stage 2. $100,000
+
Dec 7 – Dec 22, 2019
+
+
Data Clustering Contest. $100,000
+
Nov 18 – Dec 2, 2019
+
+
Javascript Contest, Stage 1. $80,000+
+
Nov 3 – Nov 17, 2019
+
+
VoIP Contest, Stage 1. $50,000+
+
Oct 15 – Oct 26, 2019
+
+
Theme Design Contest. $25,000+
+
Oct 5 – Oct 20, 2019
+
+
Animated Stickers Contest. $25,000+
+
Oct 5 – Oct 20, 2019
+
+
Blockchain Contest. $200,000–400,000
+
Sep 24 – Oct 15, 2019
+
+
Bugs on Telegram
+
Jun 14 – Jun 23, 2019
+
+
Android Chart Competition. $50,000
+
Apr 7 – Apr 15, 2019
+
+
iOS Chart Competition. $50,000
+
Apr 7 – Apr 15, 2019
+
+
JavaScript Chart Competition. $50,000
+
Apr 7 – Apr 15, 2019
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/core.telegram.org/api/account-deletion.html b/data/core.telegram.org/api/account-deletion.html new file mode 100644 index 0000000000..95a7c53e43 --- /dev/null +++ b/data/core.telegram.org/api/account-deletion.html @@ -0,0 +1,129 @@ + + + + + Account deletion + + + + + + + + + + + + + +
+ +
+
+
+ +

Account deletion

+ +

If the user has successfully provided the login code, but they forgot the 2FA password, the account should be reset: this can be done using account.deleteAccount.

+

If the account's 2FA password was modified more than 7 days ago and was active in the last 7 days, account deletion will be delayed for 7 days, and a service message will be sent to the user, containing a link in one of the following formats:

+
    +
  • https://telegram.me/confirmphone?phone=XXX&hash=YYYY
  • +
  • tg://confirmphone?phone=XXX&hash=YYYY
  • +
+

When clicked, account.sendConfirmPhoneCode must be called with the specified hash, using the account with the specified phone number. +This will send a phone number verification code to the phone number associated with the account. +The phone code settings are the same as for the login code, and auth.cancelCode with auth.resendCode can be used as well, to resend or cancel the phone code as for the login code.

+

Once the SMS code is received, the account.confirmPhone method will have to be called with the SMS code and the phone hash received from the account.sendConfirmPhoneCode method.

+

This will cancel deletion of the account and will log out the user that tried to reset it. +Otherwise, if the number isn't confirmed in 7 days, the account will be deleted and the user will be free to recreate it.

+

Related articles

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/auth.html b/data/core.telegram.org/api/auth.html new file mode 100644 index 0000000000..43fec5c314 --- /dev/null +++ b/data/core.telegram.org/api/auth.html @@ -0,0 +1,202 @@ + + + + + User Authorization + + + + + + + + + + + + + +
+ +
+
+
+ +

User Authorization

+ +
+ +

Authorization is associated with a client’s encryption key identifier: auth_key_id. No additional parameters need to be passed into methods following authorization.

+

To log in as a bot, follow these instructions ».

+

Sending a verification code

+

Example implementations: telegram for android, tdlib.

+

To show a nicely formatted and validated phone number field, the help.countriesList constructor can be obtained using the help.getCountriesList method.
The help.countriesList config is then used as described here ».

+

Authorization requires that a text message containing an authorization code first be sent to the user’s phone.
This may be done using the auth.sendCode method.
The system will automatically choose how to send the authorization code; there are four possible ways the code can arrive:

+
    +
  • Telegram code
  • +
  • SMS code
  • +
  • Phone call: a synthesized voice will tell the user which verification code to input
  • +
  • Flash phone call: the code will be sent via a flash phone call, that will be closed immediately.
    In the last case, the phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern (see auth.sentCodeTypeFlashCall).
  • +
+

The auth.sendCode method also has parameters for enabling/disabling use of flash calls, and allows passing an SMS token that will be included in the sent SMS.
For example, the latter is required in newer versions of android, to use the android SMS receiver APIs.

+

The returned auth.SentCode object will contain multiple parameters:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
+

If the message takes too long (timeout seconds) to arrive at the phone, the auth.resendCode method may be invoked to resend a code of type next_type.
If the same happens again, you can use auth.resendCode with the next_type returned by the previous call to auth.resendCode.
To cancel the verification code use auth.cancelCode.

+

Sign in/sign up

+

When user enters verification code, the auth.signIn method must be used to validate it and possibly sign user in.

+

If the code was entered correctly, but the method returns auth.authorizationSignUpRequired, it means that account with this phone number doesn't exist yet: user needs to provide basic information, accept terms of service and then the new user registration method (auth.signUp) must be invoked.

+

2FA

+

When trying to sign in using auth.signIn, an error 400 SESSION_PASSWORD_NEEDED may be returned, if the user has two-factor authentication enabled.
In this case, instructions for SRP 2FA authentication must be followed.

+

To set up two-factor authorization on an already authorized account, follow the SRP 2FA authentication docs.

+

Test Accounts

+

Each phone number is limited to only a certain amount of logins per day (e.g. 5, but this is subject to change) after which the API will return a FLOOD error until the next day. This might not be enough for testing the implementation of User Authorization flows in client applications.

+

There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are availble in API development tools panel after api_id was obtained, URI format for HTTPS/Websocket transport).

+

If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).

+

Do not store any important or private information in the messages of such test accounts; anyone can make use of the simplified authorization mechanism – and we periodically wipe all information stored there.

+

Proceed with User Authorization flows in Production DCs only after you make sure everything works correctly on Test DCs first to avoid reaching flood limits.

+
+

To help you with working on production DCs, logins with the same phone number with which the api_id was registered have more generous flood limits.

+
+

We are authorized

+

As a result of authorization, the client key, auth_key_id, becomes associated with the user, and each subsequent API call with this key will be executed with that user’s identity. The authorization method itself returns the relevant user. It is best to immediately store the User ID locally in a binding with the key.

+

Only a small portion of the API methods are available to unauthorized users:

+ +

Other methods will result in an error: 401 UNAUTHORIZED.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/bots.html b/data/core.telegram.org/api/bots.html new file mode 100644 index 0000000000..b851aac4a2 --- /dev/null +++ b/data/core.telegram.org/api/bots.html @@ -0,0 +1,142 @@ + + + + + Bots + + + + + + + + + + + + + +
+ +
+
+
+ +

Bots

+ +
+ +

Working with bots, using the MTProto API.

+

See here for more info about bots.

+

Please note that you can also use the simplified HTTP Bot API to use bots, see here for more info ».

+

Login

+
---functions---
+
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
+

In order to login as a bot, instead of using the standard login code flow, simply provide the bot token generated by @botfather.
+You must still provide your API ID, as per user logins.

+

After successful authorization, you will be able to use most MTProto API methods, just as any normal user.
+Methods that can be called by bots will have a Bots can use this method notice.

+

Commands

+

Bots offer a set of commands that can be used by users in private, or in a chat.

+

Buttons

+

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

+

Inline queries

+

Users can interact with your bot via inline queries, straight from the text input field in any chat.

+

Games

+

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/bots/games.html b/data/core.telegram.org/api/bots/games.html new file mode 100644 index 0000000000..ba75dd90e6 --- /dev/null +++ b/data/core.telegram.org/api/bots/games.html @@ -0,0 +1,171 @@ + + + + + Games + + + + + + + + + + + + + +
+ +
+
+
+ +

Games

+ +
+ +

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats.

+

Sending a game

+
inputUserSelf#f7c1b13f = InputUser;
+
+inputGameID#32c3e77 id:long access_hash:long = InputGame;
+inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
+
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+
+game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

Bots can directly send a game using messages.sendMedia, providing:

+
    +
  • The bot's shortname obtained from @BotFather to inputGameShortName.short_name
  • +
  • The current bot's info to inputGameShortName.bot_id
  • +
+

The sent message will contain a messageMediaGame with a game, that can then be used by users to forward the game using sendMedia with inputGameID.

+

Starting a game

+

Games are started clicking on the button, which triggers an callback query that returns the game URL, for more info see here &raquo.
+The game should then be opened in a WebView or in native UI (specified by the native_ui flag), exposing the appropriate HTML5 APIs in order to receive various JS game events directly from the code of the game, as described here ».

+

Setting highscores

+
---functions---
+
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+

Games are supposed to report back to the MTProto API every time the user looses a game with a new highscore.
+Since games run in the browser, they cannot directly report data to the API using the bot token, which must be kept secret.
+Instead, they should send highscores to an intermediate server, that will then report scores using messages.setGameScore or messages.setInlineGameScore, depending on the source of the game.

+
    +
  • The edit_message flag should be set if the game message should be automatically edited to include the current scoreboard
  • +
  • The force flag should be set if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters.
  • +
+

Getting highscores

+
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+
+highScore#73a379eb pos:int user_id:long score:int = HighScore;
+
+messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+---functions---
+
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
+

Every time a highscore is reached, and the edit_message flag is set when reporting the score, a messageService with a messageActionGameScore is generated, indicating that the highscore of a certain game has changed, thanks to a certain user_id.
+Our own current position of the scoreboard is also reported as pos.

+

When receiving such an update, graphical clients should refetch the scoreboard using messages.getGameHighScores or messages.getInlineGameHighScores.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/datacenter.html b/data/core.telegram.org/api/datacenter.html new file mode 100644 index 0000000000..f660f4af74 --- /dev/null +++ b/data/core.telegram.org/api/datacenter.html @@ -0,0 +1,152 @@ + + + + + Working with Different Data Centers + + + + + + + + + + + + + +
+ +
+
+
+ +

Working with Different Data Centers

+ +

The servers are divided into several data centers (hereinafter “DCs”) in different parts of the world. +A complete list of proxy access points for these DCs may be obtained using help.getConfig:

+
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+---functions---
+help.getConfig#c4f9186b = Config;
+

In this context, this_dc is the number of the current DC, dc_options is a list of all DCs available at the moment, each of which has an id, ip, and port for establishing a connection. Please note that ip and port may change frequently, based on proxy server load and the user's current location.
+Typically, each DC has at least one IPv4 and one IPv6 endpoint available.

+

To optimize client communication with the API, each client must use the connection to the closest access point for its main queries (sending messages, getting contacts, etc.). Therefore, knowing how to select a DC is required before communicating with the API.

+

Registration/Authorization

+

The auth.sendCode method is the basic entry point when registering a new user or authorizing an existing user. 95% of all redirection cases to a different DC will occure when invoking this method.

+

The client does not yet know which DC it will be associated with; therefore, it establishes an encrypted connection to a random address and sends its query to that address. +Having received a phone_number from a client, we can find out whether or not it is registered in the system. If it is, then, if necessary, instead of sending a text message, we request that it establish a connection with a different DC first (PHONE_MIGRATE_X error). +If we do not yet have a user with this number, we examine its IP-address. We can use it to identify the closest DC. Again, if necessary, we redirect the user to a different DC (NETWORK_MIGRATE_X error).

+

Testing Redirects

+

There are reserved phone number prefixes to test the correctness of the application’s handling of redirects between DCs. Read more in User Authorization article.

+

File Access

+

A file saved by a user with upload.saveFilePart will be available for direct download only from the DC where the query was executed. That is why each file has a dc_id parameter:

+
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
+

To download the file, an encrypted connection to DC dc_id must be established and used to execute the upload.getFile query. +If an attempt is made to download the file over a wrong connection, the FILE_MIGRATE_X error will be returned.

+

Please note that encryption keys are not copied between DCs; therefore, the process of establishing an encrypted connection is started from the very beginning for each new DC. An issued auth_key can be associated with the current authorized user by using an authorization transfer.

+

User Migration

+

During the process of working with the API, user information is accumulated in the DC with which the user is associated. This is the reason a user cannot be associated with a different DC by means of the client. However, in the future, during prolonged communication from an unusual location, we may decide that the user’s data must be moved to a different DC. After some time, the data will be copied and the association will be updated. Once this happens, when executing any query transmitted to the old DC, the API will return the USER_MIGRATE_X error. The client will then have to establish a connection with the new DC and repeat the query.

+

Authorization Transfer

+

The following methods can be used to eliminate the need for users to enter the code from a text message every time:

+
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+---functions---
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
+

auth.exportAuthorization must be executed in the current DC (the DC with which a connection has already been established), passing in dc_id as the value for the new DC. The method should return the user identifier and a long string of random data. An import operation can be performed at the new DC by sending it what was received. Queries requiring authorization can then be successfully executed in the new DC.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/end-to-end/pfs.html b/data/core.telegram.org/api/end-to-end/pfs.html new file mode 100644 index 0000000000..8da37768e9 --- /dev/null +++ b/data/core.telegram.org/api/end-to-end/pfs.html @@ -0,0 +1,176 @@ + + + + + Perfect Forward Secrecy + + + + + + + + + + + + + +
+ +
+
+
+ +

Perfect Forward Secrecy

+ +
+

Telegram supports Perfect Forward Secrecy (PFS) in Secret Chats as of Layer 20. See updating to new layers.

+
+

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

+

Any client participating in a Secret Chat can initiate re-keying as soon as it perceives that the current key has been used for too long or for encrypting too many messages. Please note that you should never initiate a new instance of the re-keying protocol if an uncompleted instance exists, initiated by either party.

+

Note: third-party developers are required to maintain the same level of security. All clients with secret chat support must be able to initiate re-keying and accept relevant service messages. See Security Guidelines.

+

Re-keying protocol

+

New keys are generated by exchanging special messages, using previously established keys for encryption. The re-keying protocol between parties A and B normally consists of four steps:

+
1. decryptedMessageActionRequestKey
+

A (re-keying initiator) generates a new value of a, subject to the same limitations as for the initial Diffie-Hellman key exchange, and sends the value of pow(g,a) to B, embedded in a decryptedMessageService:

+
decryptedMessageActionRequestKey exchange_id:long g_a:string = DecryptedMessageAction;
+
    +
  • exchange_id is a random number identifying this instance of the Re-Keying Protocol for both parties
  • +
  • g_a is the value of pow(g,a) mod p
  • +
+

Note that the same Diffie--Hellman parameters (p,g) as for the initial Diffie--Hellman key exchange in this secret chat are used. They do not need to be re-transmitted explicitly.

+
2. decryptedMessageActionAcceptKey
+

Upon receipt of the above service message, B checks its content, and generates a response with same exchange_id, for a newly generated value of b:

+
decryptedMessageActionAcceptKey exchange_id:long g_b:string key_fingerprint:long = DecryptedMessageAction;
+
    +
  • exchange_id is the same as in the received decryptedMessageActionRequestKey
  • +
  • g_b is the value of pow(g,b) mod p
  • +
  • key_fingerprint is the 64-bit fingerprint of the newly generated key = pow(g_a, b) mod p, used as a sanity check of the implementation
  • +
+

At this stage, B can already compute the new key key = pow(g_a, b) mod p and its key_fingerprint (last 64 bits of its SHA-1). However, it continues using the previous key until the completion of the exchange.

+

Once side B sends decryptedMessageActionAcceptKey, it cannot abort the key exchange; it must be ready to switch to the new key immediately after a decryptedMessageActionCommitKey is received. Therefore, if side B wishes to delay the usage of new key, for example in order to fill some seq_no gaps first, it must delay the decryptedMessageActionAcceptKey answer accordingly.

+
3. decryptedMessageActionCommitKey
+

Once A receives a valid decryptedMessageActionAcceptKey, it performs all necessary checks, and "commits" the new key by means of the following service message:

+
decryptedMessageActionCommitKey exchange_id:long key_fingerprint:long = DecryptedMessageAction;
+
    +
  • exchange_id is the same as in the two previous messages
  • +
  • key_fingerprint is the value of the hash (last 64 bits of SHA-1) of the new key computed by A, for implementation sanity check
  • +
+

After that, A can (and must) encrypt all following messages with the new key.

+

If side A wishes to delay installation of the new key, for example because there are some seq_no gaps that it wants to fill first, it must delay decryptedMessageActionCommitKey answer accordingly.

+
4. Final step
+

When B receives either a decryptedMessageActionCommitKey or a message encrypted by the new key, recognized by the value of key_fingerprint prepended to the encrypted message (it may happen that the decryptedMessageActionCommitKey has been lost and will be re-requested later), it assumes that A has started using the new key for encryption, and does the same.

+

However, the previous key may be kept until there are no gaps in received messages up to the switch to the new key. Once all the gaps have been filled, the old key must be securely discarded.

+

There is one exception to this rule — the SHA-1 of the original key (generated during the establishment of Secret Chat in question) is always stored, in order to show key visualizations on the clients.

+

Aborting protocol

+

Any of the parties may abort any instance of an uncompleted re-keying protocol, unless decryptedMessageActionCommitKey or decryptedMessageActionAcceptKey has been already sent by the party in question. In order to abort re-keying, send

+
decryptedMessageActionAbortKey exchange_id:long = DecryptedMessageAction;
+

This could be done, for example, if the party is already participating in a different instance of the re-keying protocol, or if the received values of g_a, g_b and other parameters do not pass security checks. In the latter case, it might be advisable to abort the Secret Chat altogether.

+

Discarding Previous Keys

+

Once B receives decryptedMessageActionCommitKey, it can safely discard the previous key provided there are no gaps. However, A may only discard the previous key after a message encrypted with the new key has been received. If no ordinary messages are scheduled to be sent, a special no-op message should sent by B for this purpose:

+
decryptedMessageActionNoop = DecryptedMessageAction;
+

Concurrent Re-Keying

+

It may happen that both parties concurrently initiate re-keying by sending decryptedMessageActionRequestKey without knowing that the other party has already done so. If each side aborts re-keying because it is already participating in another instance of the protocol initiated by itself, the re-keying will never happen.

+

Because of this possibility, we suggest that only the instance with the smaller exchange_id is aborted, with the option to re-use its (a,g_a) for the re-keying protocol instance with the larger exchange_id (when compared as a long, i.e. signed little-endian 64-bit integer).

+

In other words, if a decryptedMessageActionRequestKey is received after A has sent its decryptedMessageActionRequestKey, but has not yet received decryptedMessageActionAcceptKey, the following is to be done:

+
    +
  • if exchange_id in the sent decryptedMessageActionRequestKey was larger than that in the decryptionActionRequestKey just received, abort the newly-suggested re-keying protocol instance without sending explicit decryptedMessageActionAbortKey (the other side will do the same according to the next rule).
  • +
  • if exchange_id in our decryptedMessageActionRequestKey was smaller, respond to the newly-received decryptedMessageActionRequestKey with a decryptedMessageActionAcceptKey, and participate only in the re-keying protocol instance initiated by the other side. It is possible to re-use at this stage the value of g_a (now called g_b) that was generated for the original decryptedMessageActionRequestKey, now abandoned, or totally new (b,g_b) can be generated.
  • +
  • in the unlikely (2^{-64}) case both exchange_id are equal, abort both instances without sending an explicit decryptedMessageActionAbortKey. The other side will do the same.
  • +
+
Key Visualization
+

Since all re-keying instances are carried over the secure channel established when the secret chat is created, it is necessary for the user to confirm that no MITM attack had taken place during the initial exchange. The key visualization on the clients uses the first 128-bits of the SHA-1 of the original key created when the Secret Chat was first established, followed by the first 160 bits of the SHA-256 of the key in use when the secret chat was updated to layer 46 (coincides with the original key if chat was created using layer 46).

+
+

Please note that the key_fingerprint parameter was introduced as a maintenance tool (with a misleading name) and is not related to key visualization on the clients.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/end-to-end/seq_no.html b/data/core.telegram.org/api/end-to-end/seq_no.html new file mode 100644 index 0000000000..cec36e31d6 --- /dev/null +++ b/data/core.telegram.org/api/end-to-end/seq_no.html @@ -0,0 +1,173 @@ + + + + + Sequence numbers in Secret Chats + + + + + + + + + + + + + +
+ +
+
+
+ +

Sequence numbers in Secret Chats

+ +

It is necessary to interpret all messages in their original order to protect against reordering, reflection, replay, omission and other manipulations (decryptedMessageActionResend messages are the only exception to this rule, see avoiding concurrent gaps). Secret chats support a special mechanism for handling seq_no counters independently from the server. Note that any service messages in secret chats must also increment the seq_no.

+

All Secret Chats messages in clients using Layer 17 or higher are wrapped in decryptedMessageLayer and have seq_no (sequence number) counters attached to them. The seq_no counters in their raw form are initialized with (out_seq_no, in_seq_no) := (0,0), and incremented strictly by 1 after any message (service or not) is sent/received and processed. They must be protected from mirroring before being sent to the remote client by transformation according to formula 2*raw_seq_no+x, where x is 0 or 1, determined by the following rule:

+ + + + + + + + + + + + + + + + + +
in_seq_noout_seq_no
secret chat initiated by sender01
secret chat initiated by recipient10
+

In this way the least significant bit of each seq_no field included in the message is different for incoming and outgoing messages. This is done to prevent a possible attacker from mirroring the messages. If any of the received in_seq_no or out_seq_no are not consistent in terms of parity (see table above), the client is required to immediately abort the secret chat.

+
+

E.g., the first message the local client sends to any secret chat will have out_seq_no of 0+x_out, the second one will have out_seq_no of 2*1+x_out, and so on, where x_out is 0 if the chat was initiated by the remote client, 1 otherwise; similarly for the received messages, but there x_in is used instead of x_out and is equal to 0 if the chat was initiated by the local client, 1 otherwise.

+
+

Raw sequence numbers will be used in the remaining part of this text, unless otherwise specified.

+

Preventing gaps

+

Your client must ensure that all outgoing secret chat messages are queued on the server in the correct order. This is achieved by correctly placing them into the invokeAfterMsgs chain. Failure to do this may result in gaps on the remote client, which may in turn lead to aborted secret chats. The local client must maintain the correct sequence of in_seq_no for the remote client. To achieve this, assign in_seq_no and out_seq_no to each message at the exact moment when the message is created, and never change them in the future.

+

Security checks

+

Checking out_seq_no

+

Your client must check that it has received each message with the sequence number out_seq_no starting from 0 to some current point C. It should then expect the next message to have the sequence number out_seq_no=C+1. If the out_seq_no in the received message does not match this, the following needs to be done:

+
    +
  • If the received out_seq_no<=C, the local client must drop the message (repeated message). The client should not check the contents of the message because the original message could have been deleted (see Deleting unacknowledged messages).
  • +
  • If the received out_seq_no>C+1, it most likely means that the server left out some messages due to a technical failure or due to the messages becoming obsolete. A temporary solution to this is to simply abort the secret chat. But since this may cause some existing older secret chats to be aborted, it is strongly recommended for the client to properly handle such seq_no gaps. Note that in_seq_no is not increased upon receipt of such a message; it is advanced only after all preceding gaps are filled.
  • +
+

Proper handling of gaps

+

In order to correctly handle incoming messages after a hole has been identified (when received out_seq_no>C+1), it is necessary to put received messages with the wrong seq_no into a "waiting queue" on the local client, and to re-request the missing messages using the special constructor decryptedMessageActionResend start_seq_no:int end_seq_no:int = DecryptedMessageAction;. The sequence numbers used in this constructor must be ready for interpretation by the remote client and therefore cannot be in their raw form: you can easily get the necessary start_seq_no by adding 2 to the out_seq_no of the last message before the hole and the end_seq_no by subtracting 2 from the out_seq_no of the received message with the wrong sequence number.

+

Each hole normally requires only one request to resend messages — if the remote client keeps sending out of sync messages, they should be put into the queue without sending a new request. Having received the missing messages, the local client must first interpret these messages in the right order by their seq_no. Once this is done, the client can proceed to interpret messages from the queue (again, in the right seq_no order).

+

Special cases:

+
    +
  • Note that having two gaps simultaneously is very rare (provided that the remote client and server are operating normally) and it is acceptable to abort the secret chat in this situation.
  • +
  • If a local client receives decryptedMessageActionResend but is unable to satisfy the request, it must abort the secret chat.
  • +
+

Avoiding concurrent gaps

+

In order to avoid getting stuck with concurrent gaps on both sides, decryptedMessageActionResend must always be interpreted immediately upon receipt in all cases, even if its out_seq_no>=C+1. Note that each decryptedMessageActionResend must only be handled once, it must not be interpreted again when we interpret messages in the queue.

+

Checking and handling in_seq_no

+

in_seq_no of all received messages must be valid. To ensure this, perform the following checks:

+
    +
  • in_seq_no must form a non-decreasing sequence of non-negative integer numbers.
  • +
  • in_seq_no must be valid at the moment of receiving the message, that is, if D is the out_seq_no of last message we sent, the received in_seq_no should not be greater than D + 1. This also allows us to insert the received message into its correct place in the secret chat. For example, imagine that the local client has sent 5 secret chat messages, and then receives a secret chat message with the text "Yes" and in_seq_no=2. In this situation the local client must place that message after the second message it sent. This makes manipulations with delayed messages impossible.
  • +
+

If in_seq_no contradicts these criteria, the local client is required to immediately abort the secret chat. This could happen only in case of malicious or buggy behaviour on either server or remote client side.

+

Deleting unacknowledged messages

+

In case the user on the local client has deleted a message before the server (or the remote client, if decryptedMessageActionResend is handled correctly) could acknowledge the message, for security reasons, you must:

+
    +
  • securely destroy the contents of the message (as in case of any other deleted Secret Chat message);
  • +
  • change the local copy of the original message to decryptedMessageActionDeleteMessages with random_id equal to its own random_id;
  • +
  • create a new outgoing message deleting the original message.
  • +
+

This must be done because your client doesn't know whether the remote client really received the message or not. In the case the message was already received, it will be deleted by the second message; otherwise it must arrive as a "self-delete" message to maintain the correct sequence of seq_no.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/end-to-end/video-calls.html b/data/core.telegram.org/api/end-to-end/video-calls.html new file mode 100644 index 0000000000..f0e546831e --- /dev/null +++ b/data/core.telegram.org/api/end-to-end/video-calls.html @@ -0,0 +1,215 @@ + + + + + End-to-End Encrypted Voice and Video Calls + + + + + + + + + + + + + +
+ +
+
+
+ +

End-to-End Encrypted Voice and Video Calls

+ +

This article describes the end-to-end encryption used for Telegram voice and video calls.

+
Related Articles
+

+ +
+

Establishing Calls

+

Before a call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document covers details related to key generation, encryption and security.

+

Key Generation

+

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

+

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

+
    +
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • +
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • +
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • +
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • +
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • +
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • +
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • +
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • +
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • +
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • +
+

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

+

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

+

Encryption

+
+

This document describes encryption in voice and video calls as implemented in Telegram apps with versions 7.0 and above. See this document for details on encryption used in voice calls in app versions released before August 14, 2020.

+
+

The Telegram Voice and Video Call Library uses an optimized version of MTProto 2.0 to send and receive packets, consisting of one or more end-to-end encrypted messages of various types (ice candidates list, video formats, remote video status, audio stream data, video stream data, message ack or empty).

+

This document describes only the encryption process, leaving out encoding and network-dependent parts.

+

The library starts working with:

+
    +
  • An encryption key key shared between the parties, as generated above.
  • +
  • Information whether the call is outgoing or incoming.
  • +
  • Two data transfer channels: signaling, offered by the Telegram API, and transport based on WebRTC.
  • +
+

Both data transfer channels are unreliable (messages may get lost), but signaling is slower and more reliable.

+

Encrypting Call Data

+

The body of a packet (decrypted_body) consists of several messages and their respective seq numbers concatenated together.

+
    +
  • decrypted_body = message_seq1 + message_body1 + message_seq2 + message_body2
  • +
+

Each decrypted_body is unique because no two seq numbers of the first message can be the same. If only old messages need to be re-sent, an empty message with new unique seq is added to the packet first.

+

The encryption key key is used to compute a 128-bit msg_key and then a 256-bit aes_key and a 128-bit aes_iv:

+
    +
  • msg_key_large = SHA256 (substr(key, 88+x, 32) + decrypted_body);
  • +
  • msg_key = substr (msg_key_large, 8, 16);
  • +
  • sha256_a = SHA256 (msg_key + substr (key, x, 36));
  • +
  • sha256_b = SHA256 (substr (key, 40+x, 36) + msg_key);
  • +
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • +
  • aes_iv = substr (sha256_b, 0, 4) + substr (sha256_a, 8, 8) + substr (sha256_b, 24, 4);
  • +
+

x depends on whether the call is outgoing or incoming and on the connection type:

+
    +
  • x = 0 for outgoing + transport
  • +
  • x = 8 for incoming + transport
  • +
  • x = 128 for outgoing + signaling
  • +
  • x = 136 for incoming + signaling
  • +
+

This allows apps to decide which packet types will be sent to which connections and work in these connections independently (with each having its own seq counter).

+

The resulting aes_key and aes_iv are used to encrypt decrypted_body:

+
    +
  • encrypted_body = AES_CTR (decrypted_body, aes_key, aes_iv)
  • +
+

The packet that gets sent consists of msg_key and encrypted_body:

+
    +
  • packet_bytes = msg_key + encrypted_body
  • +
+

When received, the packet gets decrypted using key and msg_key, after which msg_key is checked against the relevant SHA256 substring. If the check fails, the packet must be discarded.

+

Protecting Against Replay Attacks

+

Each of the peers maintains its own 32-bit monotonically increasing counter for outgoing messages, seq, starting with 1. This seq counter is prepended to each sent message and increased by 1 for each new message. No two seq numbers of the first message in a packet can be the same. If only old messages need to be re-sent, an empty message with a new unique seq is added to the packet first. When the seq counter reaches 2^30, the call must be aborted. Each peer stores seq values of all the messages it has received (and processed) which are larger than max_received_seq - 64, where max_received_seq is the largest seq number received so far.

+

If a packet is received, the first message of which has a seq that is smaller or equal to max_received_seq - 64 or its seq had already been received, the message is discarded. Otherwise, the seq values of all incoming messages are memorized and max_received_seq is adjusted. This guarantees that no two packets will be processed twice.

+

Key Verification

+

To verify the key, and ensure that no MITM attack is taking place, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

+

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

+
    +
  • A->B : (generates a and) sends g_a := g^a
  • +
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • +
  • A : computes key (g_b)^a
  • +
+

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

+
    +
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • +
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • +
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • +
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • +
+

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

+

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

+

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

+
+

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/errors.html b/data/core.telegram.org/api/errors.html new file mode 100644 index 0000000000..f195781ddd --- /dev/null +++ b/data/core.telegram.org/api/errors.html @@ -0,0 +1,189 @@ + + + + + Error handling + + + + + + + + + + + + + +
+ +
+
+
+ +

Error handling

+ +

There will be errors when working with the API, and they must be correctly handled on the client.

+

An error is characterized by several parameters:

+

Error Code

+

Numerical value similar to HTTP status. Contains information on the type of error that occurred: for example, a data input error, privacy error, or server error. This is a required parameter.

+

Error Type

+

A string literal in the form of /[A-Z_0-9]+/, which summarizes the problem. For example, AUTH_KEY_UNREGISTERED. This is an optional parameter.

+
+

Error Constructors

+

There should be a way to handle errors that are returned in rpc_error constructors.

+

Below is a list of error codes and their meanings:

+

303 SEE_OTHER

+

The request must be repeated, but directed to a different data center.

+

Examples of Errors:

+
    +
  • FILE_MIGRATE_X: the file to be accessed is currently stored in a different data center.
  • +
  • PHONE_MIGRATE_X: the phone number a user is trying to use for authorization is associated with a different data center.
  • +
  • NETWORK_MIGRATE_X: the source IP address is associated with a different data center (for registration)
  • +
  • USER_MIGRATE_X: the user whose identity is being used to execute queries is associated with a different data center (for registration)
  • +
+

In all these cases, the error description’s string literal contains the number of the data center (instead of the X) to which the repeated query must be sent. +More information about redirects between data centers »

+

400 BAD_REQUEST

+

The query contains errors. In the event that a request was created using a form and contains user generated data, the user should be notified that the data must be corrected before the query is repeated.

+

Examples of Errors:

+
    +
  • FIRSTNAME_INVALID: The first name is invalid
  • +
  • LASTNAME_INVALID: The last name is invalid
  • +
  • PHONE_NUMBER_INVALID: The phone number is invalid
  • +
  • PHONE_CODE_HASH_EMPTY: phone_code_hash is missing
  • +
  • PHONE_CODE_EMPTY: phone_code is missing
  • +
  • PHONE_CODE_EXPIRED: The confirmation code has expired
  • +
  • API_ID_INVALID: The api_id/api_hash combination is invalid
  • +
  • PHONE_NUMBER_OCCUPIED: The phone number is already in use
  • +
  • PHONE_NUMBER_UNOCCUPIED: The phone number is not yet being used
  • +
  • USERS_TOO_FEW: Not enough users (to create a chat, for example)
  • +
  • USERS_TOO_MUCH: The maximum number of users has been exceeded (to create a chat, for example)
  • +
  • TYPE_CONSTRUCTOR_INVALID: The type constructor is invalid
  • +
  • FILE_PART_INVALID: The file part number is invalid
  • +
  • FILE_PARTS_INVALID: The number of file parts is invalid
  • +
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage
  • +
  • MD5_CHECKSUM_INVALID: The MD5 checksums do not match
  • +
  • PHOTO_INVALID_DIMENSIONS: The photo dimensions are invalid
  • +
  • FIELD_NAME_INVALID: The field with the name FIELD_NAME is invalid
  • +
  • FIELD_NAME_EMPTY: The field with the name FIELD_NAME is missing
  • +
  • MSG_WAIT_FAILED: A request that must be completed before processing the current request returned an error
  • +
  • MSG_WAIT_TIMEOUT: A request that must be completed before processing the current request didn't finish processing yet
  • +
+

401 UNAUTHORIZED

+

There was an unauthorized attempt to use functionality available only to authorized users.

+

Examples of Errors:

+
    +
  • AUTH_KEY_UNREGISTERED: The key is not registered in the system
  • +
  • AUTH_KEY_INVALID: The key is invalid
  • +
  • USER_DEACTIVATED: The user has been deleted/deactivated
  • +
  • SESSION_REVOKED: The authorization has been invalidated, because of the user terminating all sessions
  • +
  • SESSION_EXPIRED: The authorization has expired
  • +
  • AUTH_KEY_PERM_EMPTY: The method is unavailble for temporary authorization key, not bound to permanent
  • +
+

403 FORBIDDEN

+

Privacy violation. For example, an attempt to write a message to someone who has blacklisted the current user.

+

404 NOT_FOUND

+

An attempt to invoke a non-existent object, such as a method.

+

406 NOT_ACCEPTABLE

+

Similar to 400 BAD_REQUEST, but the app should not display any error messages to user in UI as a result of this response. The error message will be delivered via updateServiceNotification instead.

+

420 FLOOD

+

The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded. For example, in an attempt to request a large number of text messages (SMS) for the same phone number.

+

Error Example:

+
    +
  • FLOOD_WAIT_X: A wait of X seconds is required (where X is a number)
  • +
+

500 INTERNAL

+

An internal server error occurred while a request was being processed; for example, there was a disruption while accessing a database or file storage.

+

If a client receives a 500 error, or you believe this error should not have occurred, please collect as much information as possible about the query and error and send it to the developers.

+

Other Error Codes

+

If a server returns an error with a code other than the ones listed above, it may be considered the same as a 500 error and treated as an internal server error.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/mentions.html b/data/core.telegram.org/api/mentions.html new file mode 100644 index 0000000000..a6db56c9c3 --- /dev/null +++ b/data/core.telegram.org/api/mentions.html @@ -0,0 +1,152 @@ + + + + + Mentions + + + + + + + + + + + + + +
+ +
+
+
+ +

Mentions

+ +
+ +

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+
messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
+
+---functions---
+
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
+

Mentions are implemented as message entities, passed to the messages.sendMessage method:

+ +

Incoming messages mentioning to the current user will have the mentioned flag set, and will contain one or more messageEntityMention and messageEntityMentionName constructors.

+

Graphical clients can show a list of mentionable users when the user starts entering an @ in the text bar; for this purpose, the channelParticipantsMentions filter can be used in channels.getParticipants.
+This filter can be enhanced by providing an additional query string q (anything the user enters after @); it will also return non-participant users, in case of channel users commenting in post comment sections.

+

Dialog mentions

+
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+
+---functions---
+
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+

Graphical clients are supposed to show a blue mention indicator next to the message counter of chats in the dialog list.
+The dialog constructor contains an unread_mentions_count field to isolate chats with unread mentions; the actual mention counter should be shown inside of the chat itself, above an @ button that can be used, by clicking multiple times, to navigate back (using messages.getUnreadMentions) through the mention history.

+

When the last unread mention is read, or when long-clicking on the @ button, all mentions for a chat should marked as read using messages.readMentions.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/passport.html b/data/core.telegram.org/api/passport.html new file mode 100644 index 0000000000..4527355cfd --- /dev/null +++ b/data/core.telegram.org/api/passport.html @@ -0,0 +1,674 @@ + + + + + Telegram passport + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram passport

+ +
+ +

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn‘t have access to the users’ personal information thanks to end-to-end encryption.

+

This page describes the request flow that client apps must used to send the requested data to the service.

+

Overview

+

From the perspective of a service that requires real-world ID, the process looks like this:

+
    +
  • A user presses “Log in with Telegram” on your website or in your app.
  • +
  • You request the data you need.
  • +
  • The user accepts your privacy policy and agrees to share their data.
  • +
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • +
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • +
  • The user's app encrypts the data with your public key and sends it to you.
  • +
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • +
  • You sign the user up for your service. Tada!
  • +
+

See As a bot to see how to request passport data using a bot, through the MTProto API. +Look at the Passport Manual to see how to request passport data using a bot, through the simplified bot API.

+

From the perspective of a user, the process looks something like this:

+
    +
  • Your app receives an event/intent from one of the SDKs, or from a custom source.
  • +
  • The user accepts your privacy policy and agrees to share their data.
  • +
  • The user's Telegram app downloads the data you requested from the end-to-end encrypted storage on Telegram.
  • +
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • +
  • The user's app encrypts the data with your public key and sends it to the service.
  • +
  • You sign the user up for your service. Tada!
  • +
+

See As a user to see how user client apps should send passport data to a service, through the MTProto API.

+

As a bot

+

A simplified version of this process can be used using the bot API, for more info see the Passport Manual.

+

Using the MTProto API, the process is pretty much the same, up until the actual API calls.

+
+

Note that all binary fields are in raw binary format, unlike in the bot API where they are base64-encoded

+
+

Setting Up Telegram Passport

+

As per the bot API.

+

Requesting Information

+

As per the bot API.

+

Receiving information

+

Schema:

+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+

When the user confirms your request by pressing the 'Authorize' button, the MTProto API sends an updateNewMessage from the user, with a messageService constructor, containing a messageActionSecureValuesSentMe constructor that contains the encrypted Telegram Passport data.

+

Decrypting data

+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
+

To decrypt the received data, first, decrypt the credentials contained in secureCredentialsEncrypted.

+
    +
  1. +

    Decrypt the credentials secret ( secret field in secureCredentialsEncrypted) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    +
  2. +
  3. +

    Use this secret and the credentials hash ( hash field in secureCredentialsEncrypted) to calculate credentials_key and credentials_iv as described below:

    +
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    + credentials_key = slice( credentials_secret_hash, 0, 32 )
    + credentials_iv = slice( credentials_secret_hash, 32, 16 )
    +
  4. +
  5. +

    Decrypt the credentials data ( data field in secureCredentialsEncrypted) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    +
  6. +
  7. +

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    +
  8. +
+
+

Note that all hashes are raw binary data, not hexits

+
+

Credentials

+

The credentials are a JSON-serialized object, structured exactly as in the bot API ». +Since decryption credentials are E2E encrypted, apps have to store the decryption credentials as JSON and not TL payloads.

+

The credentials are used as described in the Passport Manual to decrypt the files attached to the secureValue. +In this case, the container for the E2E encrypted data is in TL, while the encrypted data itself is in JSON.

+
secureValue
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
+

The schema for the secureValue constructor defines the constructor that can be found in each field.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
+

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
+
SecureData
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
+

DataCredentials extracted from the credentials can then be used to decrypt encrypted data from the data field in secureData. +For more info on how to decrypt the data field, see the passport manual.

+
SecureFile
+
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile; 
+
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+
+---functions---
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
+

Files (JPG format when decrypted, max. 10MB) are downloaded chunk by chunk as described in files », except that instead of generating an inputFileLocation, an inputFileLocation should be generated, instead.

+
    +
  • The id field is the id of the secureFile
  • +
  • The access_hash field is the access_hash of the secureFile
  • +
+

FileCredentials extracted from the credentials can then be used to decrypt downloaded encrypted data. +For more info on how to decrypt passport files, see the passport manual.

+
SecurePlainData
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+

The email/phone is passed in plaintext using the respective SecurePlainData constructor. +Emails and phone numbers sent using telegram passport are already verified as described in the passport manual.

+

Fixing errors

+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+inputUser#f21158c6 user_id:long access_hash:long = InputUser;
+
+
+---functions---
+
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+

If the data you received contains errors, the bot can use the users.setSecureValueErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

+

Descriptions of the method parameters can be found in the method's documentation page ».

+

As a user

+

Receiving requests

+

The process starts when your app receives an event from one of the SDKs, or from a custom source.

+

URI format

+

The SDKs trigger a passport authorization request by opening the following Telegram-specific URI:

+
tg://resolve?params
+

With the following query string parameters:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
domainStringYes
bot_idIntegerYes
scopeUriPassportScopeYes
public_keyStringYes
nonceStringYes
callback_urlStringOptional
payloadStringOptional
+

Example URI, generated by the Telegram Passport Example page:

+
tg://resolve?domain=telegrampassport&bot_id=543260180&scope=%7B%22v%22%3A1%2C%22d%22%3A%5B%7B%22_%22%3A%22pd%22%2C%22n%22%3A1%7D%2C%22ad%22%2C%22pn%22%2C%22em%22%2C%7B%22_%22%3A%5B%7B%22_%22%3A%22pp%22%2C%22s%22%3A1%2C%22t%22%3A1%7D%2C%22ip%22%2C%22dl%22%2C%22ic%22%5D%7D%2C%7B%22_%22%3A%5B%22ub%22%2C%22bs%22%2C%22ra%22%2C%22pr%22%2C%22tr%22%5D%7D%5D%7D&public_key=-----BEGIN%20PUBLIC%20KEY-----%0AMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv6m1zBF8lZOCqcxf8hnj%0AkvHwuWdU8s4rBWaxKXH%2FvDDUklcCS5uhSnmjhxWca9suubaG3lW4HxlCilkeJPVf%0Ajimg5Q8ZqWrR3OoOihEpcG9iJZTOEpsEk7VtEiabgacBG3Quv9JslTrDe95Fn801%0At9d21HXwgMrHeHpWDOn31Dr%2BwoEH%2BkwySUWa6L%2FZbnGwSNP7eeDTE7Amz1RMDk3t%0A8EWGq58u0IQatPcEH09aUQlKzk6MIiALkZ9ILBKCBk6d2WCokKnsdBctovNbxwSx%0AhP1qst1r%2BYc8iPBZozsDC0ZsC5jXCkcODI3OC0tkNtYzN2XKalW5R0DjDRUDmGhT%0AzQIDAQAB%0A-----END%20PUBLIC%20KEY-----%0A&nonce=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e&callback_url=https%3A%2F%2Fcore.telegram.org%2Fpassport%2Fexample%3Fpassport_ssid%3Db8e892dc2e0afe63424d101b964f1256_32858210_db259b427f200751ce&payload=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e
+

UriPassportScope

+

This object represents the data to be requested.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
dArray of UriPassportScopeElementList of requested elements, each type may be used only once in the entire array of UriPassportScopeElement objects
vIntegerScope version, must be 1
+
UriPassportScopeElement
+

This object represents a requested element, should be one of:

+ +

Passport document type identifiers are aliased with the following reduced type identifiers:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FullAlias
personal_detailspd
passportpp
driver_licensedl
identity_cardic
internal_passportip
id_documentidd
addressad
utility_billub
bank_statementbs
rental_agreementra
passport_registrationpr
temporary_registrationtr
address_documentadd
phone_numberpn
emailem
+

You can use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

+

UriPassportScopeElementOneOfSeveral

+

This object represents several elements one of which must be provided.

+ + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
_Array of UriPassportScopeElementOneList of elements one of which must be provided; must contain either several of “pp”, “dl”, “ic”, “ip” or several of “ub”, “bs”, “ra”, “pr”, “tr”
sBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
tBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
+

UriPassportScopeElementOne

+

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
_StringElement type. One of "pd", "pp", "dl", "ic", "ip", "ad", "ub", "bs", "ra", "pr", "tr", "pn", "em"
sBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "pp", "dl", "ic" and "ip"
tBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "pp", "dl", "ic", "ip", "ub", "bs", "ra", "pr" and "tr". Note: We suggest to only request translations after you have received a valid document that requires one.
nBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "pd"
+

You can also use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

+

Setting up Telegram Passport

+

The next step for the client app is to request the user's 2FA passport, and configure Telegram Passport/fetch and decrypt remotely saved Telegram Passport parameters as described in the Encryption article ».

+

Fetching the passport form

+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+---functions---
+
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
+

Then, the client app passes the bot ID, scope and public key from the passport authorization request to the Telegram servers using the account.getAuthorizationForm method.

+

The response will be an account.authorizationForm constructor, with info about the required document types, the URL of the service's privacy policy, as well as info about the bot to which the form should be sent. +If the form was already submitted at least once, the constructor will also contain a list of already submitted data, along with eventual errors.

+

The user should accept the privacy policy and proceed to fill in the required data, and the client should encrypt and upload it as described in the Encryption article ».

+

Submitting the passport form

+
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
+
+---functions---
+
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+

Once the user finishes uploading the required documents and clicks on the submit button, the client calls account.acceptAuthorization, submitting the documents to the bot associated to the service.

+
    +
  • As before, bot_id, scope and public_key are taken from the authorization request URI.
  • +
  • value_hashes is used by the server to choose which document of which type to send to the bot: the type field should be set to the document type, and the hash field should be set to the data_hash/file_hash generated when uploading encrypting the data ».
  • +
  • credentials contains the encrypted credentials required by the service to decrypt the sent E2E encrypted secure values: it is generated as described in Passport Credentials ».
  • +
+

Finally, the client opens the callback URL (if present).

+

Handling invalid forms

+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+---functions---
+
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
+

If any of the values of the submitted form are rejected by the service, the bot calls the appropriate method to set information about errors.

+

The user can find out about these errors directly from the service, or, if they decide to restart the process and resend the corrected data, directly from the authorization form (errors field).

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/pfs.html b/data/core.telegram.org/api/pfs.html new file mode 100644 index 0000000000..7f03a3eeee --- /dev/null +++ b/data/core.telegram.org/api/pfs.html @@ -0,0 +1,138 @@ + + + + + Perfect Forward Secrecy + + + + + + + + + + + + + +
+ +
+
+
+ +

Perfect Forward Secrecy

+ +
Related articles
+

+
+

This article is about Perfect Forward Secrecy in cloud chats, see also PFS in Secret Chats.

+
+
+

Telegram supports Perfect Forward Secrecy (PFS).

+

To make this possible, the client generates a permanent authorization key using p_q_inner_data and a temporary key using p_q_inner_data_temp. (See Creating an Authorization Key for more info.) These 2 operations may be done in parallel and even using the same connection. The client must save an expires_at unix timestamp expires_at = time + expires_in.

+

Important: in order to achieve PFS, the client must never use the permanent auth_key_id directly. Every message that is sent to MTProto, must be encrypted by a temp_auth_key_id, that was bound to the perm_auth_key_id.

+

An unbound temp_auth_key_id may only be used with the following methods:

+ +

In order to bind a temporary authorization key to the permanent key the client creates a special binding message and executes the auth.bindTempAuthKey method using temp_auth_key. Once auth.bindTempAuthKey has been executed successfully, the client may signUp / signIn using other auth.* methods and continue using the API as usual; the client must also rewrite client info using initConnection after each binding. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

+

Once the temporary key expires, the client needs to generate a new temporary key using p_q_inner_data_temp. Then it needs to re-bind that new temporary key to the initial permanent key. A new key can also be generated in advance, so that the client has a new key ready by the time the old one has expired.

+

For additional security, the client can store the temporary authorization key in RAM only and never save it in persistent storage.

+

A temporary authorization key may expire at any moment before expires_at, since such keys are also stored only in the RAM on the server-side. Be prepared to handle resulting MTProto errors correctly (non-existent auth_key_id results in a 404 error).

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/api/poll.html b/data/core.telegram.org/api/poll.html new file mode 100644 index 0000000000..e12f1e5996 --- /dev/null +++ b/data/core.telegram.org/api/poll.html @@ -0,0 +1,199 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +
+ +

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

+

Sending a poll

+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+
+---functions---
+
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

+
    +
  • +

    poll is the actual poll constructor, containing:

    +
      +
    • question - The poll title, aka the poll's title
    • +
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • +
    • closed - Whether the poll is closed
    • +
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • +
    • multiple_choice - Whether multiple options can be chosen as answer
    • +
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • +
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • +
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      +These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • +
    +
  • +
  • +

    correct_answers - For quizes, option ID of the only correct answer

    +
  • +
  • +

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    +
  • +
  • +

    solution_entities - Styled text message entities for the solution explanation

    +
  • +
+

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

+

Voting in polls

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+

When receiving a message with a messageMediaPoll, users can vote in it using messages.sendVote, specifying the chosen option identifiers.

+

The method will return an updateMessagePoll, containing an updated pollResults constructor, with the chosen flag set on the options we chose, and the correct flag set on the correct answers.

+

Getting poll votes

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+

Regularly, if new users have voted in polls available to the user, they will receive an updateMessagePoll, with updated pollResults.

+

The same constructor can also be fetched manually using messages.getPollResults.

+

Getting poll voters in non-anonymous polls

+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
+
+messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList; 
+
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+
+---functions---
+
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
+

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
+Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/updates.html b/data/core.telegram.org/api/updates.html new file mode 100644 index 0000000000..4a314b97ea --- /dev/null +++ b/data/core.telegram.org/api/updates.html @@ -0,0 +1,226 @@ + + + + + Working with Updates + + + + + + + + + + + + + +
+ +
+
+
+ +

Working with Updates

+ +
+ +

When a client is being actively used, events will occur that affect the current user and that they must learn about as soon as possible, e.g. when a new message is received. To eliminate the need for the client itself to periodically download these events, there is an update delivery mechanism in which the server sends the user notifications over one of its available connections with the client.

+

Subscribing to Updates

+

Update events are sent to an authorized user into the last active connection (except for connections needed for downloading / uploading files).

+

So to start receiving updates the client needs to init connection and call API method, e.g. to fetch current state.

+

Event sequences

+

All events are received from the socket as a sequence of TL-serialized Updates objects, which might be optionally gzip-compressed in the same way as responses to queries.

+

Each Updates object may contain single or multiple Update objects, representing different events happening.

+

In order to apply all updates in precise order and to guarantee that no update is missed or applied twice there is seq attribute in Updates constructors, and pts (with pts_count) or qts attributes in Update constructors. The client must use those attributes values in combination with locally stored state to correctly apply incoming updates.

+

When a gap in updates sequence occurs, it must be filled via calling one of the API methods. More below »

+

Updates sequence

+

As said earlier, each payload with updates has a TL-type Updates. It can be seen from the schema below that this type has several constructors.

+
updatesTooLong#e317af7e = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+

updatesTooLong indicates that there are too many events pending to be pushed to the client, so one needs to fetch them manually.

+

Events inside updateShort constructors, normally, have lower priority and are broadcast to a large number of users, i.e. one of the chat participants started entering text in a big conversation (updateChatUserTyping).

+

The updateShortMessage, updateShortSentMessage and updateShortChatMessage constructors are redundant but help significantly reduce the transmitted message size for 90% of the updates. They should be transformed to updateShort upon receiving.

+

Two remaining constructors updates and updatesCombined are part of the Updates sequence. Both of them have seq attribute, which indicates the remote Updates state after the generation of the Updates, and seq_start indicates the remote Updates state after the first of the Updates in the packet is generated. For updates, seq_start attribute is omitted, because it is assumed that it is always equal to seq.

+

Message-related event sequences

+

Each event related to a message box (message created, message edited, message deleted, etc) is identified by a unique autoincremented pts, or qts in case of secret chat updates, certain bot updates, etc.

+

Each message box can be considered as some server-side DB table that stores messages and events associated with them. +All boxes are completely independent, and each pts sequence is tied to just one box (see below).

+

Update object may contain info about multiple events (for example, updateDeleteMessages). +That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).

+

Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. +Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence.

+

To recap, the client has to take care of the integrity of the following sequences to properly handle updates:

+
    +
  • Updates sequence (seq)
      +
    • Common message box sequence (pts)
    • +
    • Secondary event sequence (qts)
    • +
    • Channel message box sequence 1 (pts)
    • +
    • Channel message box sequence 2 (pts)
    • +
    • Channel message box sequence 3 (pts)
    • +
    • and so on...
    • +
    +
  • +
+

Fetching state

+

The common update state is represented by the updates.State constructor. +When the user logs in for the first time, call to updates.getState has to be made to store the latest update state (which will not be the absolute initial state, just the latest state at the current time). +The common update state can also be fetched from updates.differenceTooLong.

+

The channel update state is represented simply by the pts of the event sequence: when first logging in, the initial channel state can be obtained from the dialog constructor when fetching dialogs, from the full channel info, or it can be received as an updateChannelTooLong update.

+

The secondary update state is represented by the qts of the secret event sequence, it is contained in the updates.State of the common update state.

+

The Updates sequence state is represented by the date and seq of the Updates sequence, it is contained in the updates.State of the common update state.

+

Update handling

+

Update handling in Telegram clients consists of receiving events, making sure there were no gaps and no events were missed based on the locally stored state of the correspondent event sequence, and then updating the locally stored state based on the parameters received.

+

When the client receives payload with serialized updates, first of all, it needs to walk through all of the nested Update objects and check if they belong to any of message box sequences (have pts or qts parameters). Those updates need to be handled separately according to corresponding local state and new pts/qts values. Details below »

+

After message box updates are handled, if there are any other updates remaining the client needs to handle them with respect to seq. Details below »

+

pts: checking and applying

+

Here, local_pts will be the local state, pts will be the remote state, pts_count will be the number of events in the update.

+

If local_pts + pts_count === pts, the update can be applied. +If local_pts + pts_count > pts, the update was already applied, and must be ignored. +If local_pts + pts_count < pts, there's an update gap that must be filled.

+

For example, let's assume the client has the following local state for the channel 123456789:

+
local_pts = 131
+

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. +Since local_pts + pts_count === pts, the total number of events since the last stored state is, in fact, equal to pts_count: this means the update can be safely accepted and the remote pts applied:

+
local_pts = 132
+

Since:

+
    +
  • pts indicates the server state after the new channel message events are generated
  • +
  • pts_count indicates the number of events in the new channel update
  • +
  • The server state before the new channel message event was generated has to be: pts_before = pts - pts_count = 131, which is, in fact, equal to our local state.
  • +
+

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. +Since local_pts + pts_count > pts (133 > 132), the update is skipped because we've already handled this update (in fact, our current local_pts was set by this same update, and it was resent twice due to network issues or other issues).

+

Now let's assume an updateDeleteChannelMessages from channel 123456789 is received with pts = 140 and pts_count=5. +Since local_pts + pts_count < pts (137 < 140), this means that updates were missed, and the gap must be recovered.

+
Secret chats & bots
+

The whole process is very similar for secret chats and certain bot updates, but there is qts instead of pts, and events are never grouped, so it's assumed that qts_count is always equal to 1.

+

seq: checking and applying

+

On top level when handling received updates and updatesCombined there are three possible cases: +If local_seq + 1 === seq_start, the updates can be applied. +If local_seq + 1 > seq_start, the updates were already applied, and must be ignored. +If local_seq + 1 < seq_start, there's an updates gap that must be filled (updates.getDifference must be used as with common and secret event sequences).

+

If the updates were applied, local Updates state must be updated with seq and date from the constructor.

+

For all the other Updates type constructors there is no need to check seq or change a local state.

+

Recovering gaps

+

To do this, updates.getDifference (common/secret state) or updates.getChannelDifference (channel state) with the respective local states must be called. +These methods should also be called on startup, to fetch new updates (preferably with some flags to reduce server load, see the method's docs). +Manually obtaining updates is also required in the following situations:

+
    +
  • Loss of sync: a gap was found in seq / pts / qts (as described above). It may be useful to wait up to 0.5 seconds in this situation and abort the sync in case a new update arrives, that fills the gap.
  • +
  • Session loss on the server: the client receives a new session created notification. This can be caused by garbage collection on the MTProto server or a server reboot.
  • +
  • Incorrect update: the client cannot deserialize the received data.
  • +
  • Incomplete update: the client is missing data about a chat/user from one of the shortened constructors, such as updateShortChatMessage, etc.
  • +
  • Long period without updates: no updates for 15 minutes or longer.
  • +
  • The server requests the client to fetch the difference using updateChannelTooLong or updatesTooLong.
  • +
+

When calling updates.getDifference if the updates.differenceSlice constructor is returned in response, the full difference was too large to be received in one request. The intermediate status, intermediate_state, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

+

To fetch the updates difference of a channel, updates.getChannelDifference is used. +If the difference is too large to be received in one request, the final flag of the result is not set (see docs). +The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

+

For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.

+

If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.

+

It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.

+

Example implementations

+

Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.

+

Example implementations: tdlib, MadelineProto.

+

An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in MadelineProto ».

+

PUSH Notifications about Updates

+

If a client does not have an active connection at the time of an event, PUSH Notifications will also be useful.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/url-authorization.html b/data/core.telegram.org/api/url-authorization.html new file mode 100644 index 0000000000..5e711e4cd3 --- /dev/null +++ b/data/core.telegram.org/api/url-authorization.html @@ -0,0 +1,160 @@ + + + + + Seamless Telegram Login + + + + + + + + + + + + + +
+ +
+
+
+ +

Seamless Telegram Login

+ +
+ +

Bots or Telegram websites may ask users to login to a certain website via Telegram when clicking on certain links or URL buttons in inline keyboards.

+

Bot URL authorization

+

When the user clicks on keyboardButtonUrlAuth, messages.requestUrlAuth should be called, providing the button_id of the button and the ID and peer of the container message. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The bot parameter will contain info about the bot which will be used for user authorization (example: DiscussBot).
  • +
  • The request_write_access will be set if the bot would like to send messages to the user.
  • +
+

The info should be shown in a prompt:

+
+ TITLE +
+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open, which will include a query string with the requested info and a hash that must be verified upon receival by the service.

+

urlAuthResultDefault could also be returned, instead, in which case the url of the keyboardButtonUrlAuth must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Link URL authorization

+

Telegram supports automatic authorization on certain websites upon opening an HTTP URL in-app, upon clicking a link in a message or clicking on a keyboardButtonUrl.

+

Automatic authorization

+

Clients should automatically authenticate users when opening official Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

Upon clicking a link, the URL must be modified by appending the autologin_token from the client configuration object » to the query string, like so:

+

Original URL: https://somedomain.telegram.org/path?query=string#fragment=value
+Modified URL: https://somedomain.telegram.org/path?query=string&autologin_token=$autologin_token#fragment=value

+

Make sure that the used autologin_token is no more than 10000 seconds old, if it is older it must be refetched before use as described in the client configuration section ».

+

Manual authorization

+

Clients should show a confirmation prompt similar to the one used for bots, to authenticate users when opening certain Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

messages.requestUrlAuth should be called, providing only the original url. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The request_write_access will be set if the website would like to send messages to the user.
  • +
+

The info should be shown in a prompt.

+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open.

+

urlAuthResultDefault could also be returned, instead, in which case the original URL must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Related articles

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/api/web-events.html b/data/core.telegram.org/api/web-events.html new file mode 100644 index 0000000000..fd612b4c95 --- /dev/null +++ b/data/core.telegram.org/api/web-events.html @@ -0,0 +1,177 @@ + + + + + Web events + + + + + + + + + + + + + +
+ +
+
+
+ +

Web events

+ +
+ +

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose APIs to allow receiving data and events from the websites.

+

Event APIs

+

Games and payment gateways can generate events that are meant to be received by the Telegram apps. +Typically events are generated by using the postEvent method of the GamingCommunication library. +The postEvent function will try sending the event to the Telegram app in a number of different ways.

+

WebviewProxy

+

In mobile apps, the event receiver API should be typically exposed as a window.TelegramWebviewProxy object with a postEvent method.

+
window.TelegramWebviewProxy.postEvent(eventType, eventData)
+

window.external

+

Alternatively, a window.external.notify method can be exposed, accepting a string JSON payload with the event type and payload:

+
window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData}));
+

postMessage API

+

Finally, web MTProto clients that need to open a game or process a payment in an iframe can use the postMessage API to receive events from iframes. +The GamingCommunication library by defaultwill use '*' as targetOrigin, sending messages to parent pages regardless of the origin of the embedder.

+
window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), targetOrigin);
+

Event types

+

eventType is a simple string indicating the event type, and eventData is a payload with an object that will be parsed by the Telegram app.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
eventTypeeventDataDescription
payment_form_submitJSON object with data and title fieldstitle is the censored credit card title.
data is a service-specific JSON payload with information about the payment credentials provided by the user to the payment system.
Neither Telegram, nor bots will have access to your credit card information.
Credit card details will be handled only by the payment system.
share_scorenullWill be called by games when the user explicitly clicks on the share score button to share the game, along with his score.
Typically done by using messages.forwardMessages on the game message with the with_my_score flag.
share_gamenullWill be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.
Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's short URL.
game_overnullCan be called by games when the user loses a game
game_loadednullCan be called by games once the game fully loads
resize_frameJSON object with height fieldCalled by supported pages inside of IV iframe embeds, indicates the new size of the embed frame.
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots.html b/data/core.telegram.org/bots.html new file mode 100644 index 0000000000..fa4bec195b --- /dev/null +++ b/data/core.telegram.org/bots.html @@ -0,0 +1,437 @@ + + + + + Bots: An introduction for developers + + + + + + + + + + + + + +
+ +
+
+
+
+

Bots: An introduction for developers

+ +
+ +

Bots are third-party applications that run inside Telegram. Users can interact with bots by sending them messages, commands and inline requests. You control your bots using HTTPS requests to Telegram's Bot API.

+
+

The full API reference for developers is available here.

+
+

1. What can I do with bots?

+
+ +
+ +

To name just a few things, you could use bots to:

+
    +
  • Get customized notifications and news. A bot can act as a smart newspaper, sending you relevant content as soon as it's published.

    +
  • +
  • Integrate with other services. A bot can enrich Telegram chats with content from external services.
    Gmail Bot, GIF bot, IMDB bot, Wiki bot, Music bot, Youtube bot, GitHubBot

    +
  • +
  • Accept payments from Telegram users. A bot can offer paid services or work as a virtual storefront. Read more »
    Demo Shop Bot, Demo Store

    +
  • +
  • Create custom tools. A bot may provide you with alerts, weather forecasts, translations, formatting or other services.
    Markdown bot, Sticker bot, Vote bot, Like bot

    +
  • +
  • Build single- and multiplayer games. A bot can offer rich HTML5 experiences, from simple arcades and puzzles to 3D-shooters and real-time strategy games.
    GameBot, Gamee

    +
  • +
  • Build social services. A bot could connect people looking for conversation partners based on common interests or proximity.

    +
  • +
  • Do virtually anything else. Except for dishes — bots are terrible at doing the dishes.

    +
  • +
+

2. How do bots work?

+

At the core, Telegram Bots are special accounts that do not require an additional phone number to set up. Users can interact with bots in two ways:

+
    +
  • Send messages and commands to bots by opening a chat with them or by adding them to groups.
  • +
  • Send requests directly from the input field by typing the bot's @username and a query. This allows sending content from inline bots directly into any chat, group or channel.
  • +
+

Messages, commands and requests sent by users are passed to the software running on your servers. Our intermediary server handles all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API. We call that interface our Bot API.

+
+

A detailed description of the Bot API is available on this page »

+
+

3. How do I create a bot?

+
+ +
+ +

There's a… bot for that. Just talk to BotFather (described below) and follow a few simple steps. Once you've created a bot and received your authentication token, head down to the Bot API manual to see what you can teach your bot to do.

+
+

You may also like to check out some code examples here »

+
+

4. How are bots different from humans?

+
    +
  • Bots have no online status and no last seen timestamps, the interface shows the label 'bot' instead.
  • +
  • Bots have limited cloud storage — older messages may be removed by the server shortly after they have been processed.
  • +
  • Bots can't initiate conversations with users. A user must either add them to a group or send them a message first. People can use t.me/<bot_username> links or username search to find your bot.
  • +
  • Bot usernames always end in 'bot' (e.g. @TriviaBot, @GitHub_bot).
  • +
  • When added to a group, bots do not receive all messages by default (see Privacy mode).
  • +
  • Bots never eat, sleep or complain (unless expressly programmed otherwise).
  • +
+
+

5. Bot perks

+

Telegram bots are unique in many ways — we offer two kinds of keyboards, additional interfaces for default commands and deep linking as well as text formatting, integrated payments and more.

+

Inline mode

+ + +

Users can interact with your bot via inline queries straight from the text input field in any chat. All they need to do is start a message with your bot's username and then type a query.

+

Having received the query, your bot can return some results. As soon as the user taps one of them, it is sent to the user's currently opened chat. This way, people can request content from your bot in any of their chats, groups or channels.

+

Check out this blog to see a sample inline bot in action. You can also try the @sticker and @music bots to see for yourself.

+
+
+ +
+ +

We've also implemented an easy way for your bot to switch between inline and PM modes.

+
+

Read more about the Inline Mode »

+
+

Payment platform

+ + +

You can use bots to accept payments from Telegram users around the world.

+
    +
  • Send invoices to any chat, including to groups and channels.
  • +
  • Create invoices that can be forwarded and used by multiple buyers to order things.
  • +
  • Use inline mode to help users show your goods and services to their friends and communities.
  • +
  • Allow tips from users with preset and custom amounts.
  • +
  • Accept payments from users on mobile or desktop apps.
  • +
  • Try @ShopBot to create a test invoice – or start a message with @ShopBot ... in any chat for an inline invoice.
  • +
  • Check out Demo Shop for an example of a Telegram Channel used as virtual storefront.
  • +
+
+ +
+ +
+

Read more about the Payments Platform »

+
+

Gaming platform

+

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. The platform allows your bot to keep track of high scores for every game played in every chat. Whenever there’s a new leader in the game, other playing members in the chat are notified that they need to step it up.

+
+ + +
+
+ +

Since the underlying technology is HTML5, the games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. Our team has created a couple of simple demos for you to try out:

+ +

You can also check out the @gamee bot that has more than 20 games.

+
+

Read more about the Gaming Platform »

+
+

Keyboards

+

Traditional chat bots can of course be taught to understand human language. But sometimes you want some more formal input from the user — and this is where custom keyboards can become extremely useful.

+

Whenever your bot sends a message, it can pass along a special keyboard with predefined reply options (see ReplyKeyboardMarkup). Telegram apps that receive the message will display your keyboard to the user. Tapping any of the buttons will immediately send the respective command. This way you can drastically simplify user interaction with your bot.

+

We currently support text and emoji for your buttons. Here are some custom keyboard examples:

+
+
+ + + + + + + +
+ +
+

For more technical information on custom keyboards, please consult the Bot API manual (see sendMessage).

+
+

Inline keyboards and on-the-fly updating

+

There are times when you'd prefer to do things without sending any messages to the chat. For example, when your user is changing settings or flipping through search results. In such cases you can use Inline Keyboards that are integrated directly into the messages they belong to.

+

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

+
+ + + + +
+ +
+ +

When callback buttons are used, your bot can update its existing messages (or just their keyboards) so that the chat remains tidy. Check out these sample bots to see inline keyboards in action: @music, @vote, @like.

+
+

Read more about inline keyboards and on-the-fly editing »

+
+

Commands

+

Commands present a more flexible way to communicate with your bot. The following syntax may be used:

+
/command
+

A command must always start with the '/' symbol and may not be longer than 32 characters. Commands can use latin letters, numbers and underscores. Here are a few examples:

+
/get_messages_stats
+/set_timer 10min Alarm!
+/get_timezone London, UK
+

Messages that start with a slash are always passed to the bot (along with replies to its messages and messages that @mention the bot by username). Telegram apps will:

+
    +
  • Suggest a list of supported commands with descriptions when the user enters a '/' (for this to work, you need to have provided a list of commands to the BotFather). Tapping on a command in the list immediately sends the command.
  • +
  • Show an additional (/) button in the input field in all chats with bots. Tapping it types a '/' and shows the list of commands.
  • +
  • Highlight /commands in messages. When the user taps a highlighted command, the command is sent at once.
  • +
+
+ + + + + + + +
+ + +

If multiple bots are in a group, it is possible to add bot usernames to commands in order to avoid confusion:

+
/start@TriviaBot
+/start@ApocalypseBot
+

This is done automatically when commands are selected via the list of suggestions. Please remember that your bot needs to be able to process commands that are followed by its username.

+
Global commands
+

In order to make it easier for users to navigate the bot multiverse, we ask all developers to support a few basic commands. Telegram apps will have interface shortcuts for these commands.

+
    +
  • /start - begins interaction with the user, e.g., by sending a greeting message. This command can also be used to pass additional parameters to the bot (see Deep linking)
  • +
  • /help - returns a help message. It can be a short text about what your bot can do and a list of commands.
  • +
  • /settings - (if applicable) returns the bot's settings for this user and suggests commands to edit these settings.
  • +
+

Users will see a Start button when they first open a conversation with your bot. Help and Settings links will be available in the menu on the bot's profile page.

+
+ + + + +
+ +

Formatting: bold, italic, fixed-width text and inline links

+

You can use bold, italic or fixed-width text, as well as inline links in your bots' messages. Telegram clients will render them accordingly.

+
+

Read more in the Bot API manual »

+
+

Privacy mode

+

Bots are frequently added to groups in order to augment communication between human users, e.g. by providing news, notifications from external services or additional search functionality. This is especially true for work-related groups. Now, when you share a group with a bot, you tend to ask yourself “How can I be sure that the little rascal isn't selling my chat history to my competitors?” The answer is — privacy mode.

+

A bot running in privacy mode will not receive all messages that people send to the group. Instead, it will only receive:

+
    +
  • Messages that start with a slash '/' (see Commands above)
  • +
  • Replies to the bot's own messages
  • +
  • Service messages (people added or removed from the group, etc.)
  • +
  • Messages from channels where it's a member
  • +
+

On one hand, this helps some of us sleep better at night (in our tinfoil nightcaps), on the other — it allows the bot developer to save a lot of resources, since they won't need to process tens of thousands irrelevant messages each day.

+

Privacy mode is enabled by default for all bots, except bots that were added to the group as admins (bot admins always receive all messages). It can be disabled, so that the bot receives all messages like an ordinary user (the bot will need to be re-added to the group for this change to take effect). We only recommend doing this in cases where it is absolutely necessary for your bot to work — users can always see a bot's current privacy setting in the group members list. In most cases, using the force reply option for the bot's messages should be more than enough.

+

So what messages exactly will my bot get? »

+

Deep linking

+

Telegram bots have a deep linking mechanism, that allows for passing additional parameters to the bot on startup. It could be a command that launches the bot — or an authentication token to connect the user's Telegram account to their account on some external service.

+

Each bot has a link that opens a conversation with it in Telegram — https://t.me/<bot username>. You can add the parameters start or startgroup to this link, with values up to 64 characters long. For example:

+
https://t.me/triviabot?startgroup=test
+

A-Z, a-z, 0-9, _ and - are allowed. We recommend using base64url to encode parameters with binary and other types of content.

+

Following a link with the start parameter will open a one-on-one conversation with the bot, showing a START button in the place of the input field. If the startgroup parameter is used, the user is prompted to select a group to add the bot to. As soon as a user confirms the action (presses the START button in their app or selects a group to add the bot to), your bot will receive a message from that user in this format:

+
/start PAYLOAD
+

PAYLOAD stands for the value of the start or startgroup parameter that was passed in the link.

+
Deep linking Example
+

Suppose the website example.com would like to send notifications to its users via a Telegram bot. Here's what they could do to enable notifications for a user with the ID 123.

+
    +
  1. Create a bot with a suitable username, e.g. @ExampleComBot
  2. +
  3. Set up a webhook for incoming messages
  4. +
  5. Generate a random string of a sufficient length, e.g. $memcache_key = "vCH1vGWJxfSeofSAs0K5PA"
  6. +
  7. Put the value 123 with the key $memcache_key into Memcache for 3600 seconds (one hour)
  8. +
  9. Show our user the button https://t.me/ExampleComBot?start=vCH1vGWJxfSeofSAs0K5PA
  10. +
  11. Configure the webhook processor to query Memcached with the parameter that is passed in incoming messages beginning with /start. If the key exists, record the chat_id passed to the webhook as telegram_chat_id for the user 123. Remove the key from Memcache.
  12. +
  13. Now when we want to send a notification to the user 123, check if they have the field telegram_chat_id. If yes, use the sendMessage method in the Bot API to send them a message in Telegram.
  14. +
+

Location and Number

+

Some bots need extra data from the user to work properly. For example, knowing the user's location helps provide more relevant geo-specific results. The user's phone number can be very useful for integrations with other services, like banks, etc.

+

Bots can ask a user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

+
+
+ +
+ +

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

+
+

Manual: Number and location buttons »

+
+
+

6. BotFather

+
+

Jump to top to learn everything about Telegram bots »

+
+

BotFather is the one bot to rule them all. It will help you create new bots and change settings for existing ones.

+

Creating a new bot

+

Use the /newbot command to create a new bot. The BotFather will ask you for a name and username, then generate an authentication token for your new bot.

+

The name of your bot is displayed in contact details and elsewhere.

+

The Username is a short name, to be used in mentions and t.me links. Usernames are 5-32 characters long and are case insensitive, but may only include Latin characters, numbers, and underscores. Your bot's username must end in 'bot', e.g. 'tetris_bot' or 'TetrisBot'.

+

The token is a string along the lines of 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw that is required to authorize the bot and send requests to the Bot API. Keep your token secure and store it safely, it can be used by anyone to control your bot.

+

Generating an authentication token

+

If your existing token is compromised or you lost it for some reason, use the /token command to generate a new one.

+

Botfather commands

+

The remaining commands are pretty self-explanatory:

+
    +
  • /mybots — returns a list of your bots with handy controls to edit their settings
  • +
  • /mygames — does the same for your games
  • +
+

Edit bots

+
    +
  • /setname – change your bot's name.
  • +
  • /setdescription — change the bot's description, a short text of up to 512 characters, describing your bot. Users will see this text at the beginning of the conversation with the bot, titled 'What can this bot do?'.
  • +
  • /setabouttext — change the bot's about info, an even shorter text of up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.
  • +
  • /setuserpic — change the bot's profile pictures. It's always nice to put a face to a name.
  • +
  • /setcommands — change the list of commands supported by your bot. Users will see these commands as suggestions when they type / in the chat with your bot. Each command has a name (must start with a slash ‘/’, alphanumeric plus underscores, no more than 32 characters, case-insensitive), parameters, and a text description. Users will see the list of commands whenever they type '/' in a conversation with your bot.
  • +
  • /deletebot — delete your bot and free its username.
  • +
+

Edit settings

+
    +
  • /setinline — toggle inline mode for your bot.
  • +
  • /setinlinegeo - request location data to provide location-based inline results.
  • +
  • /setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
  • +
  • /setprivacy — set which messages your bot will receive when added to a group. With privacy mode disabled, the bot will receive all messages. We recommend leaving privacy mode enabled. You will need to re-add the bot to existing groups for this change to take effect.
  • +
+

Manage games

+
    +
  • /newgame — create a new game.
  • +
  • /listgames — get a list of your games.
  • +
  • /editgame — edit a game.
  • +
  • /deletegame — delete an existing game.
  • +
+
+

Please note, that it may take a few minutes for changes to take effect.

+
+

Status alerts

+

Millions choose Telegram for its speed. To stay competitive in this environment, your bot also needs to be responsive. In order to help developers keep their bots in shape, Botfather will send status alerts if it sees something is wrong.

+

We will be checking the number of replies and the request/response conversion rate for popular bots (~300 requests per minute: but don't write this down as the value may change in the future). If we get abnormally low readings, you will receive a notification from Botfather.

+
Responding to alerts
+

By default, you will only get one alert per bot per hour. Each alert has the following buttons:

+
    +
  • Fixed. Use this if you found an issue with your bot and fixed it. If you press the fix button, we will resume sending alerts in the regular way so that you can see if your fix worked within 5-10 minutes instead of having to wait for an hour.
  • +
  • Support. Use this to open a chat with @BotSupport if you don't see any issues with your bot or if you think the problem is on our side.
  • +
  • Mute for 8h/1w. Use this if you can't fix your bot at the moment. This will disable all alerts for the bot in question for the specified period of time. We do not recommend using this option since your users may migrate to a more stable bot. You can unmute alerts in your bot's settings via Botfather.
  • +
+
Monitored issues
+

We will currently notify you about the following issues:

+

1.

+
Too few **private messages** are sent compared to previous weeks: **{value}**
+

Your bot is sending much fewer messages than it did in the previous weeks. This is useful for newsletter-style bots that send out messages without prompts from the users. The larger the value, the more significant the difference.

+

2.

+
Too few replies to incoming **private messages**. Conversion rate: **{value}**
+

Your bot is not replying to all messages that are being sent to it (the request/response conversion rate for your bot was too low for at least two of the last three 5-minute periods). To provide a good user experience, please respond to all messages that are sent to your bot. Respond to message updates by calling send… methods (e.g. sendMessage).

+

3.

+
Too few answers to **inline queries**. Conversion rate: **{value}**
+

Your bot is not replying to all inline queries that are being sent to it, calculated in the same way as above. Respond to inline_query updates by calling answerInlineQuery.

+

4.

+
Too few answers to **callback queries**. Conversion rate: **{value}**
+Too few answers to **callback game queries**. Conversion rate: **{value}**
+

Your bot is not replying to all callback queries that are being sent to it (with or without games), calculated in the same way as above. Respond to callback_query updates by calling answerCallbackQuery.

+
+

Please note that the status alerts feature is still being tested and will be improved in the future.

+
+
+

That's it for the introduction. You are now definitely ready to proceed to the BOT API MANUAL.

+

If you've got any questions, please check out our Bot FAQ »

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/bots/self-signed.html b/data/core.telegram.org/bots/self-signed.html new file mode 100644 index 0000000000..ec670a6a4b --- /dev/null +++ b/data/core.telegram.org/bots/self-signed.html @@ -0,0 +1,161 @@ + + + + + Using self-signed certificates + + + + + + + + + + + + + +
+ +
+
+
+ +

Using self-signed certificates

+ +

Upload your certificate using the certificate parameter in the setWebhook method. The certificate supplied should be PEM encoded (ASCII BASE64), the pem file should only contain the public key (including BEGIN and END portions). When converting from a bundle format, please split the file to only include the public key.

+

Generating a self-signed certificate pair (PEM):

+

Openssl

+
+

Windows binaries for Openssl are available online

+
+

openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"

+

YOURPUBLIC.pem has to be used as input for setting the self-signed webhook.

+

You can inspect the generated certificate with:
openssl x509 -text -noout -in YOURPUBLIC.pem

+

Converting from a previously generated DER:
openssl x509 -inform der -in YOURDER.der -out YOURPEM.pem

+

Converting from a previously generated PKCS12:
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

+
+

More information: https://www.openssl.org/

+
+

Java keystore

+

Generate self-signed JKS:
keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

+

Converting JKS to pkcs12 (intermediate step for conversion to PEM):
keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

+

Convert PKCS12 to PEM (requires openssl):
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

+
+

More information: https://docs.oracle.com

+
+

Windows

+

Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.

+

On the commandline:
certreq -new TEMPLATE.txt RequestFileOut

+

TEMPLATE.txt example file:

+
[NewRequest]
+
+; At least one value must be set in this section
+Subject = "CN=DOMAIN.EXAMPLE"
+KeyLength = 2048
+KeyAlgorithm = RSA
+HashAlgorithm = sha256
+;MachineKeySet = true
+RequestType = Cert
+UseExistingKeySet=false ;generates a new private key (for export)
+Exportable = true ;makes the private key exportable with the PFX
+

A self-signed certificate will be generated and installed, to view the certificate:
certutil -store -user my

+

To export in DER format (intermediate step for conversion to PEM)
certutil -user -store -split my SERIALNUMBER YOURDER.crt

+

Converting to PEM (used for setting the webhook)
certutil -encode YOURDER.crt YOURPEM.cer

+

To delete a certificate from your store:
certutil -delstore -user my SERIALNUMBER (from view)

+

To export in PFX(PKCS12) format
certutil -exportpfx -user YOURDOMAIN.EXAMPLE YOURPKCS.pfx NoChain

+
+

More information: https://technet.microsoft.com

+
+

Converting YOURPKCS.pfx to PEM including the private key is best done with OpenSSL:
openssl pkcs12 -in YOURPKCS.pfx -out YOURPEM.cer

+

Remember that only the public key is needed as input for the self-signed webhook certificate parameter. certmgr.msc can also be used as a GUI to export the public part of self-signed certificates to PEM.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/cdn.html b/data/core.telegram.org/cdn.html new file mode 100644 index 0000000000..197bb8e0e2 --- /dev/null +++ b/data/core.telegram.org/cdn.html @@ -0,0 +1,210 @@ + + + + + Encrypted CDNs for Speed and Security + + + + + + + + + + + + + +
+ +
+
+
+
+

Encrypted CDNs for Speed and Security

+ +

Following the launch of version 4.2 of the official apps, Telegram client apps may be required to download popular files that were published in public channels with more than 100,000 members from secondary Content Delivery Network data centers. These CDN DCs are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

+

The CDN DCs are not a part of the Telegram cloud and should be considered enemy territory. For this reason, each file that is to be sent to these CDN DCs is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

+
+

See also: More about CDNs and governments in the Advanced FAQ

+
+

How this works

+

When a file from a public channel with ~100,000 members becomes popular in a particular region, the Telegram server may encrypt this file with a unique AES-256-CTR key and send it to a relevant CDN DC for storage.

+

When a file is stored in a CDN DC close to the end user, the download speed will be much higher because the data needs to travel smaller distances and will likely avoid many bottlenecks that exist between regions.

+

This is secure because CDN DCs are treated the same way as internet providers / random third parties:

+
    +
  • CDN DCs don‘t have the keys to decrypt files that are stored there, so they can’t access the data even if a DC becomes compromised.
  • +
  • Encrypted files fragments are protected from tampering by their SHA-256 hash which is checked on the client upon receipt.
  • +
  • No private data is stored in or passed to the CDN DCs.
  • +
  • The server only allows media from public channels with more than 100,000 subscribers to be cached in CDN DCs (this includes media forwarded from those channels and viral media that originated from other large public channels).
  • +
+
+ +
+ +

CDNs are very limited when it comes to communication: the master data center only uploads encrypted files for storage and will accept no data from the CDN. The client apps only download encrypted files and accept no other updates. The client apps obtain the keys necessary to decrypt the file from the main Telegram server and verify the integrity of the file by its hash, which means that the CDN may only supply the correct file – anything different will be immediately discarded by the client.

+

CDN DCs do not store files on hard disks – only in memory. When a CDN server runs out of memory, a simple LRU algorithm is used to replace the least popular files with new ones.

+

How CDN DCs are different from the master DCs

+
    +
  • CDNs may not be trusted.
  • +
  • Client developers can use help.getCdnConfig to obtain a list of public RSA keys for CDN DCs, which are different from public RSA keys of the master DCs.
  • +
  • CDNs support only the following methods: upload.getCdnFile, initConnection, invokeWithLayer.
  • +
  • When working with CDNs, client developers must remember that auth_key may be deleted at any given moment (resulting in a -404 error, in which case a new key must be generated).
  • +
  • Client apps must not accept updates from CDN DCs (apps should only accept updates from their main connection to the master DC).
  • +
  • Clients must not allow the CDN DCs to substitute replies to queries sent to other DCs.
  • +
  • Clients must not send private user info that is passed in initConnection to the CDNs.
  • +
+

Getting files from a CDN

+

The API may return the upload.fileCdnRedirect constructor after an upload.getFile query. In this case, the client must request the required file from a CDN DC. The dc_id in the response is the id of the new CDN. The IP address for the connection will be available in help.getConfig, same as with the master DCs. The corresponding dcOption will have the flag cdn:flags.3?true.

+

Once a successful connection to the CDN-dc_id is established, the client must generate an auth_key (after confirming that the public RSA MTProto key of the CDN DC matches one from the list returned in help.getCdnConfig). Then the client must perform an upload.getCdnFile for each offset. For files of an unknown size it is necessary to repeat the query until an empty reply is returned.

+

upload.getCdnFile may return the upload.cdnFileReuploadNeeded constructor. In this case, the client needs to send an upload.reuploadCdnFile request to the DC that got the original upload.getFile request. Once upload.reuploadCdnFile is successfull, the app needs to request the file from the CDN DC again.

+

The main DC for a file is the DC where its main copy is stored (not to be confused with the main DC of the user) – either userProfilePhoto.dc_id, chatPhoto.dc_id, photo.dc_id, or document.dc_id.

+

Decrypting files

+

In upload.fileCdnRedirect, the server sends a decryption key and IV for the file (the fields encryption_key:bytes and encryption_iv:bytes respectively).

+

Having received a portion of encrypted data from the CDN DC inside upload.cdnFile, the client must decrypt this data using AES-256-CTR. For IV, it should use the value of encryption_iv, modified in the following manner: for each offset replace the last 4 bytes of the encryption_iv with offset / 16 in big-endian. This allows to effectively decrypt a file and to use random access to a file's content (e.g., for streaming).

+

Verifying files

+

In order to confirm that the CDN DC passed an untampered file, clients must verify hashes for each downloaded part. upload.fileCdnRedirect, upload.reuploadCdnFile and upload.getCdnFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

+

Before saving each portion of the data received from the CDN DC into the file, the client must confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getCdnFileHashes method to obtain the missing hash.

+

Schema

+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+
+dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+
+cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
+
+
+cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+
+---functions---
+
+// CDN DC
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
+
+// Master DC
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
+
+help.getCdnConfig#52029342 = CdnConfig;
+

Restrictions on upload.getFile and upload.getCdnFile parameters

+
    +
  • offset must be divisible by 4096 bytes
  • +
  • limit must be divisible by 4096 bytes
  • +
  • 1048576 (1MB) must be divisible by limit
  • +
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024)
    (file parts that are being downloaded must always be inside the same megabyte-sized fragment)
  • +
+

Possible errors and their meanings

+ + + + + + + + + + + + + + + + + + +
upload.getCdnFileFILE_TOKEN_INVALIDThe CDN DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileFILE_TOKEN_INVALIDThe master DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileREQUEST_TOKEN_INVALIDThe master DC did not accept the request_token from the CDN DC. Continue downloading the file from the master DC using upload.getFile.
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.autoDownloadSettings b/data/core.telegram.org/constructor/account.autoDownloadSettings new file mode 100644 index 0000000000..e9d893123b --- /dev/null +++ b/data/core.telegram.org/constructor/account.autoDownloadSettings @@ -0,0 +1,157 @@ + + + + + account.autoDownloadSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.autoDownloadSettings

+ +

Media autodownload settings

+

+ +
+
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lowAutoDownloadSettingsLow data usage preset
mediumAutoDownloadSettingsMedium data usage preset
highAutoDownloadSettingsHigh data usage preset
+

Type

+

account.AutoDownloadSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.resetPasswordOk b/data/core.telegram.org/constructor/account.resetPasswordOk new file mode 100644 index 0000000000..017da1a3ab --- /dev/null +++ b/data/core.telegram.org/constructor/account.resetPasswordOk @@ -0,0 +1,132 @@ + + + + + account.resetPasswordOk + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordOk

+ +

The 2FA password was reset successfully.

+

+ +
+
account.resetPasswordOk#e926d63e = account.ResetPasswordResult;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.sentChangePhoneCode b/data/core.telegram.org/constructor/account.sentChangePhoneCode new file mode 100644 index 0000000000..ff48a68f29 --- /dev/null +++ b/data/core.telegram.org/constructor/account.sentChangePhoneCode @@ -0,0 +1,161 @@ + + + + + account.sentChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sentChangePhoneCode

+ +

Sent change phone code

+

+ +
+
Constructor schema is available as of layer 50. Switch »

+

Parameters

+ + + + + + + + + + + + + +
phone_code_hashstringChange phone code hash
send_call_timeoutintCall timeout
+

Type

+

account.SentChangePhoneCode

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/account.wallPapers b/data/core.telegram.org/constructor/account.wallPapers new file mode 100644 index 0000000000..8eb2dd9d90 --- /dev/null +++ b/data/core.telegram.org/constructor/account.wallPapers @@ -0,0 +1,155 @@ + + + + + account.wallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.wallPapers

+ +

Installed wallpapers

+

+ +
+
account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
wallpapersVector<WallPaper>Wallpapers
+

Type

+

account.WallPapers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/accountDaysTTL.html b/data/core.telegram.org/constructor/accountDaysTTL.html new file mode 100644 index 0000000000..c0ef3668e3 --- /dev/null +++ b/data/core.telegram.org/constructor/accountDaysTTL.html @@ -0,0 +1,147 @@ + + + + + accountDaysTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

accountDaysTTL

+ +

Time to live in days of the current account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
daysintThis account will self-destruct in the specified number of days
+

Type

+

AccountDaysTTL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.loginTokenSuccess b/data/core.telegram.org/constructor/auth.loginTokenSuccess new file mode 100644 index 0000000000..887407b1fa --- /dev/null +++ b/data/core.telegram.org/constructor/auth.loginTokenSuccess @@ -0,0 +1,147 @@ + + + + + auth.loginTokenSuccess + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.loginTokenSuccess

+ +

Login via token (QR code) succeded!

+

+ +
+
auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
authorizationauth.AuthorizationAuthorization info
+

Type

+

auth.LoginToken

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCode b/data/core.telegram.org/constructor/auth.sentCode new file mode 100644 index 0000000000..53413116fa --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCode @@ -0,0 +1,172 @@ + + + + + auth.sentCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCode

+ +

Contains info about a sent verification code.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
+

Type

+

auth.SentCode

+

Related pages

+

auth.signIn

+

Signs in a user with a validated phone number.

+

auth.resendCode

+

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall b/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall new file mode 100644 index 0000000000..0ad15e1f94 --- /dev/null +++ b/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall @@ -0,0 +1,150 @@ + + + + + auth.sentCodeTypeFlashCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sentCodeTypeFlashCall

+ +

The code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.

+

+ +
+
auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
patternstringpattern to match
+

Type

+

auth.SentCodeType

+

Related pages

+

Pattern matching

+

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/bankCardOpenUrl.html b/data/core.telegram.org/constructor/bankCardOpenUrl.html new file mode 100644 index 0000000000..131cda896e --- /dev/null +++ b/data/core.telegram.org/constructor/bankCardOpenUrl.html @@ -0,0 +1,152 @@ + + + + + bankCardOpenUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

bankCardOpenUrl

+ +

Credit card info URL provided by the bank

+

+ +
+
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringInfo URL
namestringBank name
+

Type

+

BankCardOpenUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeDay.html b/data/core.telegram.org/constructor/baseThemeDay.html new file mode 100644 index 0000000000..7fa0ff7124 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeDay.html @@ -0,0 +1,132 @@ + + + + + baseThemeDay + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeDay

+ +

Day theme

+

+ +
+
baseThemeDay#fbd81688 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/baseThemeTinted.html b/data/core.telegram.org/constructor/baseThemeTinted.html new file mode 100644 index 0000000000..bc4dea5385 --- /dev/null +++ b/data/core.telegram.org/constructor/baseThemeTinted.html @@ -0,0 +1,132 @@ + + + + + baseThemeTinted + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeTinted

+ +

Tinted theme

+

+ +
+
baseThemeTinted#6d5f77ee = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/botCommandScopeChats.html b/data/core.telegram.org/constructor/botCommandScopeChats.html new file mode 100644 index 0000000000..bf42ab91e4 --- /dev/null +++ b/data/core.telegram.org/constructor/botCommandScopeChats.html @@ -0,0 +1,135 @@ + + + + + botCommandScopeChats + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeChats

+ +

The specified bot commands will be valid in all groups and supergroups.

+

+ +
+
botCommandScopeChats#6fe1a881 = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/cdnConfig.html b/data/core.telegram.org/constructor/cdnConfig.html new file mode 100644 index 0000000000..1157b7340e --- /dev/null +++ b/data/core.telegram.org/constructor/cdnConfig.html @@ -0,0 +1,149 @@ + + + + + cdnConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

cdnConfig

+ +

Configuration for CDN file downloads.

+

+ +
+
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
public_keysVector<CdnPublicKey>Vector of public keys to use only during handshakes to CDN DCs.
+

Type

+

CdnConfig

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channel.html b/data/core.telegram.org/constructor/channel.html new file mode 100644 index 0000000000..73ec97d243 --- /dev/null +++ b/data/core.telegram.org/constructor/channel.html @@ -0,0 +1,289 @@ + + + + + channel + + + + + + + + + + + + + +
+ +
+
+
+ +

channel

+ +

Channel/supergroup info

+

+ +
+
channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this channel
leftflags.2?trueWhether the current user has left this channel
broadcastflags.5?trueIs this a channel?
verifiedflags.7?trueIs this channel verified by telegram?
megagroupflags.8?trueIs this a supergroup?
restrictedflags.9?trueWhether viewing/writing in this channel for a reason (see restriction_reason
signaturesflags.11?trueWhether signatures are enabled (channels)
minflags.12?trueSee min
scamflags.19?trueThis channel/supergroup is probably a scam
has_linkflags.20?trueWhether this channel has a private join link
has_geoflags.21?trueWhether this chanel has a geoposition
slowmode_enabledflags.22?trueWhether slow mode is enabled for groups to prevent flood in chat
call_activeflags.23?trueWhether a group call or livestream is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call or livestream
fakeflags.25?trueIf set, this supergroup/channel was reported by many users as a fake or scam: be careful when interacting with it.
gigagroupflags.26?trueWhether this supergroup is a gigagroup
idlongID of the channel
access_hashflags.13?longAccess hash
titlestringTitle
usernameflags.6?stringUsername
photoChatPhotoProfile photo
dateintDate when the user joined the supergroup/channel, or if the user isn't a member, its creation date
restriction_reasonflags.9?Vector<RestrictionReason>Contains the reason why access to this channel must be restricted.
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in this channel (see rights)
banned_rightsflags.15?ChatBannedRightsBanned rights of the user in this channel (see rights)
default_banned_rightsflags.18?ChatBannedRightsDefault chat rights (see rights)
participants_countflags.17?intParticipant count
+

Type

+

Chat

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html new file mode 100644 index 0000000000..d8470afca7 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeLinkedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeLinkedChat

+ +

The linked chat was changed

+

+ +
+
channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuelongPrevious linked chat
new_valuelongNew linked chat
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html new file mode 100644 index 0000000000..d0d6c768cf --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeStickerSet

+ +

The supergroup's stickerset was changed

+

+ +
+
channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_stickersetInputStickerSetPrevious stickerset
new_stickersetInputStickerSetNew stickerset
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html new file mode 100644 index 0000000000..6c4edcbca6 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeUsername

+ +

Channel/supergroup username was changed

+

+ +
+
channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valuestringOld username
new_valuestringNew username
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html new file mode 100644 index 0000000000..70fa7b1339 --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html @@ -0,0 +1,132 @@ + + + + + channelAdminLogEventActionParticipantJoin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionParticipantJoin

+ +

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

+

+ +
+
channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html new file mode 100644 index 0000000000..998071cb0a --- /dev/null +++ b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionToggleGroupCallSetting + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleGroupCallSetting

+ +

Group call settings were changed

+

+ +
+
channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
join_mutedBoolWhether all users are muted by default upon joining
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipant.html b/data/core.telegram.org/constructor/channelParticipant.html new file mode 100644 index 0000000000..2cb702153b --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipant.html @@ -0,0 +1,152 @@ + + + + + channelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipant

+ +

Channel/supergroup participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongPariticipant user ID
dateintDate joined
+

Type

+

ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsAdmins.html b/data/core.telegram.org/constructor/channelParticipantsAdmins.html new file mode 100644 index 0000000000..62aa8fe76b --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsAdmins.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsAdmins

+ +

Fetch only admin participants

+

+ +
+
channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsContacts.html b/data/core.telegram.org/constructor/channelParticipantsContacts.html new file mode 100644 index 0000000000..2563dfc7ee --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsContacts.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsContacts

+ +

Fetch only participants that are also contacts

+

+ +
+
channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional search query for searching contact participants by name
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channelParticipantsKicked.html b/data/core.telegram.org/constructor/channelParticipantsKicked.html new file mode 100644 index 0000000000..4d7d23f656 --- /dev/null +++ b/data/core.telegram.org/constructor/channelParticipantsKicked.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsKicked + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsKicked

+ +

Fetch only kicked participants

+

+ +
+
channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringOptional filter for searching kicked participants by name (otherwise empty)
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.adminLogResults b/data/core.telegram.org/constructor/channels.adminLogResults new file mode 100644 index 0000000000..4e5cccbfe5 --- /dev/null +++ b/data/core.telegram.org/constructor/channels.adminLogResults @@ -0,0 +1,157 @@ + + + + + channels.adminLogResults + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.adminLogResults

+ +

Admin log events

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
eventsVector<ChannelAdminLogEvent>Admin log events
chatsVector<Chat>Chats mentioned in events
usersVector<User>Users mentioned in events
+

Type

+

channels.AdminLogResults

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.channelParticipant b/data/core.telegram.org/constructor/channels.channelParticipant new file mode 100644 index 0000000000..44fb5b5322 --- /dev/null +++ b/data/core.telegram.org/constructor/channels.channelParticipant @@ -0,0 +1,157 @@ + + + + + channels.channelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipant

+ +

Represents a channel participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
participantChannelParticipantThe channel participant
chatsVector<Chat>Mentioned chats
usersVector<User>Users
+

Type

+

channels.ChannelParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/channels.channelParticipants b/data/core.telegram.org/constructor/channels.channelParticipants new file mode 100644 index 0000000000..5993ce565d --- /dev/null +++ b/data/core.telegram.org/constructor/channels.channelParticipants @@ -0,0 +1,162 @@ + + + + + channels.channelParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.channelParticipants

+ +

Represents multiple channel participants

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of participants that correspond to the given query
participantsVector<ChannelParticipant>Participants
chatsVector<Chat>Mentioned chats
usersVector<User>Users mentioned in participant info
+

Type

+

channels.ChannelParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatBannedRights.html b/data/core.telegram.org/constructor/chatBannedRights.html new file mode 100644 index 0000000000..c211ebffd1 --- /dev/null +++ b/data/core.telegram.org/constructor/chatBannedRights.html @@ -0,0 +1,216 @@ + + + + + chatBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatBannedRights

+ +

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

+

+ +
+
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send polls in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
+

Type

+

ChatBannedRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatEmpty.html b/data/core.telegram.org/constructor/chatEmpty.html new file mode 100644 index 0000000000..59eb91e223 --- /dev/null +++ b/data/core.telegram.org/constructor/chatEmpty.html @@ -0,0 +1,147 @@ + + + + + chatEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

chatEmpty

+ +

Empty constructor, group doesn't exist

+

+ +
+
chatEmpty#29562865 id:long = Chat;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup identifier
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatForbidden.html b/data/core.telegram.org/constructor/chatForbidden.html new file mode 100644 index 0000000000..65ebd13046 --- /dev/null +++ b/data/core.telegram.org/constructor/chatForbidden.html @@ -0,0 +1,152 @@ + + + + + chatForbidden + + + + + + + + + + + + + +
+ +
+
+
+ +

chatForbidden

+ +

A group to which the user has no access. E.g., because the user was kicked from the group.

+

+ +
+
chatForbidden#6592a1a7 id:long title:string = Chat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser identifier
titlestringGroup name
+

Type

+

Chat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInviteImporter.html b/data/core.telegram.org/constructor/chatInviteImporter.html new file mode 100644 index 0000000000..4d8a380fca --- /dev/null +++ b/data/core.telegram.org/constructor/chatInviteImporter.html @@ -0,0 +1,152 @@ + + + + + chatInviteImporter + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInviteImporter

+ +

When and which user joined the chat using a chat invite

+

+ +
+
chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongThe user
dateintWhen did the user join
+

Type

+

ChatInviteImporter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatInvitePeek.html b/data/core.telegram.org/constructor/chatInvitePeek.html new file mode 100644 index 0000000000..bf275ef208 --- /dev/null +++ b/data/core.telegram.org/constructor/chatInvitePeek.html @@ -0,0 +1,152 @@ + + + + + chatInvitePeek + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInvitePeek

+ +

A chat invitation that also allows peeking into the group to read messages without joining it.

+

+ +
+
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
+

Type

+

ChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipantAdmin.html b/data/core.telegram.org/constructor/chatParticipantAdmin.html new file mode 100644 index 0000000000..5847d665ae --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipantAdmin.html @@ -0,0 +1,157 @@ + + + + + chatParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantAdmin

+ +

Chat admin

+

+ +
+
chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of a group member that is admin
inviter_idlongID of the user that added the member to the group
dateintDate when the user was added
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipantCreator.html b/data/core.telegram.org/constructor/chatParticipantCreator.html new file mode 100644 index 0000000000..85d70ec86c --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipantCreator.html @@ -0,0 +1,147 @@ + + + + + chatParticipantCreator + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipantCreator

+ +

Represents the creator of the group

+

+ +
+
chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongID of the user that created the group
+

Type

+

ChatParticipant

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatParticipants.html b/data/core.telegram.org/constructor/chatParticipants.html new file mode 100644 index 0000000000..f85fedd61c --- /dev/null +++ b/data/core.telegram.org/constructor/chatParticipants.html @@ -0,0 +1,157 @@ + + + + + chatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

chatParticipants

+ +

Group members.

+

+ +
+
chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongGroup identifier
participantsVector<ChatParticipant>List of group members
versionintGroup version number
+

Type

+

ChatParticipants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/chatTheme.html b/data/core.telegram.org/constructor/chatTheme.html new file mode 100644 index 0000000000..3d671d7b26 --- /dev/null +++ b/data/core.telegram.org/constructor/chatTheme.html @@ -0,0 +1,157 @@ + + + + + chatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

chatTheme

+ +

A chat theme

+

+ +
+
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringEmoji, identifying this specific chat theme
themeThemeTheme
dark_themeThemeDark mode theme
+

Type

+

ChatTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.found b/data/core.telegram.org/constructor/contacts.found new file mode 100644 index 0000000000..69c2e79636 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.found @@ -0,0 +1,162 @@ + + + + + contacts.found + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.found

+ +

Users found by name substring and auxiliary data.

+

+ +
+
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
my_resultsVector<Peer>Personalized results
resultsVector<Peer>List of found user identifiers
chatsVector<Chat>Found chats
usersVector<User>List of users
+

Type

+

contacts.Found

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.importedContacts b/data/core.telegram.org/constructor/contacts.importedContacts new file mode 100644 index 0000000000..ecd6004dd5 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.importedContacts @@ -0,0 +1,165 @@ + + + + + contacts.importedContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.importedContacts

+ +

Info on succesfully imported contacts.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
importedVector<ImportedContact>List of succesfully imported contacts
popular_invitesVector<PopularContact>Popular contacts
retry_contactsVector<long>List of contact ids that could not be imported due to system limitation and will need to be imported at a later date.
Parameter added in Layer 13
usersVector<User>List of users
+

Type

+

contacts.ImportedContacts

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.topPeers b/data/core.telegram.org/constructor/contacts.topPeers new file mode 100644 index 0000000000..7a12dc54f6 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.topPeers @@ -0,0 +1,157 @@ + + + + + contacts.topPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeers

+ +

Top peers

+

+ +
+
contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoriesVector<TopPeerCategoryPeers>Top peers by top peer category
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/contacts.topPeersNotModified b/data/core.telegram.org/constructor/contacts.topPeersNotModified new file mode 100644 index 0000000000..1e6a36f955 --- /dev/null +++ b/data/core.telegram.org/constructor/contacts.topPeersNotModified @@ -0,0 +1,132 @@ + + + + + contacts.topPeersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.topPeersNotModified

+ +

Top peer info hasn't changed

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

contacts.TopPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNoop.html b/data/core.telegram.org/constructor/decryptedMessageActionNoop.html new file mode 100644 index 0000000000..9ddff65b0d --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionNoop.html @@ -0,0 +1,133 @@ + + + + + decryptedMessageActionNoop + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionNoop

+ +

NOOP action

+

+ +
+
===20===
+decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html b/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html new file mode 100644 index 0000000000..c6169d8bad --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionRequestKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionRequestKey

+ +

Request rekeying, see rekeying process

+

+ +
+
===20===
+decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
g_abytesg_a, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageActionTyping.html b/data/core.telegram.org/constructor/decryptedMessageActionTyping.html new file mode 100644 index 0000000000..b6dee6a583 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageActionTyping.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageActionTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionTyping

+ +

User is preparing a message: typing, recording, uploading, etc.

+

+ +
+
===17===
+decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
actionSendMessageActionType of action
+

Type

+

DecryptedMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaContact.html b/data/core.telegram.org/constructor/decryptedMessageMediaContact.html new file mode 100644 index 0000000000..b308706c91 --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaContact.html @@ -0,0 +1,163 @@ + + + + + decryptedMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaContact

+ +

Contact attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
user_idintTelegram User ID of signed-up contact
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html new file mode 100644 index 0000000000..6bd97831ff --- /dev/null +++ b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html @@ -0,0 +1,153 @@ + + + + + decryptedMessageMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaGeoPoint

+ +

GeoPont attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogFilterSuggested.html b/data/core.telegram.org/constructor/dialogFilterSuggested.html new file mode 100644 index 0000000000..d7e5df87c6 --- /dev/null +++ b/data/core.telegram.org/constructor/dialogFilterSuggested.html @@ -0,0 +1,155 @@ + + + + + dialogFilterSuggested + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFilterSuggested

+ +

Suggested folders

+

+ +
+
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
+

Type

+

DialogFilterSuggested

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/dialogPeer.html b/data/core.telegram.org/constructor/dialogPeer.html new file mode 100644 index 0000000000..46835a4ddb --- /dev/null +++ b/data/core.telegram.org/constructor/dialogPeer.html @@ -0,0 +1,147 @@ + + + + + dialogPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogPeer

+ +

Peer

+

+ +
+
dialogPeer#e56dbf05 peer:Peer = DialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
+

Type

+

DialogPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeAnimated.html b/data/core.telegram.org/constructor/documentAttributeAnimated.html new file mode 100644 index 0000000000..bd8055a20d --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeAnimated.html @@ -0,0 +1,132 @@ + + + + + documentAttributeAnimated + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeAnimated

+ +

Defines an animated GIF

+

+ +
+
documentAttributeAnimated#11b58939 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/documentAttributeHasStickers.html b/data/core.telegram.org/constructor/documentAttributeHasStickers.html new file mode 100644 index 0000000000..08ea716327 --- /dev/null +++ b/data/core.telegram.org/constructor/documentAttributeHasStickers.html @@ -0,0 +1,132 @@ + + + + + documentAttributeHasStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeHasStickers

+ +

Whether the current document has stickers attached

+

+ +
+
documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/emojiKeyword.html b/data/core.telegram.org/constructor/emojiKeyword.html new file mode 100644 index 0000000000..7e34a40c58 --- /dev/null +++ b/data/core.telegram.org/constructor/emojiKeyword.html @@ -0,0 +1,152 @@ + + + + + emojiKeyword + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiKeyword

+ +

Emoji keyword

+

+ +
+
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis associated to keyword
+

Type

+

EmojiKeyword

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/emojiLanguage.html b/data/core.telegram.org/constructor/emojiLanguage.html new file mode 100644 index 0000000000..982cc08851 --- /dev/null +++ b/data/core.telegram.org/constructor/emojiLanguage.html @@ -0,0 +1,147 @@ + + + + + emojiLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiLanguage

+ +

Emoji language

+

+ +
+
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Type

+

EmojiLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedChatEmpty.html b/data/core.telegram.org/constructor/encryptedChatEmpty.html new file mode 100644 index 0000000000..a00b3384eb --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedChatEmpty.html @@ -0,0 +1,147 @@ + + + + + encryptedChatEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatEmpty

+ +

Empty constructor.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedChatWaiting.html b/data/core.telegram.org/constructor/encryptedChatWaiting.html new file mode 100644 index 0000000000..66940da991 --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedChatWaiting.html @@ -0,0 +1,167 @@ + + + + + encryptedChatWaiting + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatWaiting

+ +

Chat waiting for approval of second participant.

+

+ +
+
encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
access_hashlongChecking sum depending on user ID
dateintDate of chat creation
admin_idlongChat creator ID
participant_idlongID of second chat participant
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedFile.html b/data/core.telegram.org/constructor/encryptedFile.html new file mode 100644 index 0000000000..3a306337a9 --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedFile.html @@ -0,0 +1,167 @@ + + + + + encryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedFile

+ +

Encrypted file.

+

+ +
+
encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongFile ID
access_hashlongChecking sum depending on user ID
sizeintFile size in bytes
dc_idintNumber of data centre
key_fingerprintint32-bit fingerprint of key used for file encryption
+

Type

+

EncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/encryptedMessageService.html b/data/core.telegram.org/constructor/encryptedMessageService.html new file mode 100644 index 0000000000..d994207a2d --- /dev/null +++ b/data/core.telegram.org/constructor/encryptedMessageService.html @@ -0,0 +1,165 @@ + + + + + encryptedMessageService + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedMessageService

+ +

Encrypted service message

+

+ +
+
encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
+

Type

+

EncryptedMessage

+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/folder.html b/data/core.telegram.org/constructor/folder.html new file mode 100644 index 0000000000..9dae755722 --- /dev/null +++ b/data/core.telegram.org/constructor/folder.html @@ -0,0 +1,177 @@ + + + + + folder + + + + + + + + + + + + + +
+ +
+
+
+ +

folder

+ +

Folder

+

+ +
+
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
autofill_new_broadcastsflags.0?trueAutomatically add new channels to this folder
autofill_public_groupsflags.1?trueAutomatically add joined new public supergroups to this folder
autofill_new_correspondentsflags.2?trueAutomatically add new private chats to this folder
idintFolder ID
titlestringFolder title
photoflags.3?ChatPhotoFolder picture
+

Type

+

Folder

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/folderPeer.html b/data/core.telegram.org/constructor/folderPeer.html new file mode 100644 index 0000000000..f11703481e --- /dev/null +++ b/data/core.telegram.org/constructor/folderPeer.html @@ -0,0 +1,155 @@ + + + + + folderPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

folderPeer

+ +

Peer in a folder

+

+ +
+
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerFolder peer info
folder_idintPeer folder ID, for more info click here
+

Type

+

FolderPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/groupCallParticipantVideo.html b/data/core.telegram.org/constructor/groupCallParticipantVideo.html new file mode 100644 index 0000000000..7adea98c53 --- /dev/null +++ b/data/core.telegram.org/constructor/groupCallParticipantVideo.html @@ -0,0 +1,167 @@ + + + + + groupCallParticipantVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCallParticipantVideo

+ +

Info about a video stream

+

+ +
+
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pausedflags.0?trueWhether the stream is currently paused
endpointstringEndpoint
source_groupsVector<GroupCallParticipantVideoSourceGroup>Source groups
audio_sourceflags.1?intAudio source ID
+

Type

+

GroupCallParticipantVideo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.passportConfig b/data/core.telegram.org/constructor/help.passportConfig new file mode 100644 index 0000000000..fd58c3692f --- /dev/null +++ b/data/core.telegram.org/constructor/help.passportConfig @@ -0,0 +1,156 @@ + + + + + help.passportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.passportConfig

+ +

Telegram passport configuration

+

+ +
+
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
+

Type

+

help.PassportConfig

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.recentMeUrls b/data/core.telegram.org/constructor/help.recentMeUrls new file mode 100644 index 0000000000..d3941a8020 --- /dev/null +++ b/data/core.telegram.org/constructor/help.recentMeUrls @@ -0,0 +1,157 @@ + + + + + help.recentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

help.recentMeUrls

+ +

Recent t.me URLs

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlsVector<RecentMeUrl>URLs
chatsVector<Chat>Chats
usersVector<User>Users
+

Type

+

help.RecentMeUrls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.supportName b/data/core.telegram.org/constructor/help.supportName new file mode 100644 index 0000000000..1678b3093b --- /dev/null +++ b/data/core.telegram.org/constructor/help.supportName @@ -0,0 +1,147 @@ + + + + + help.supportName + + + + + + + + + + + + + +
+ +
+
+
+ +

help.supportName

+ +

Localized name for telegram support

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
namestringLocalized name
+

Type

+

help.SupportName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/help.userInfoEmpty b/data/core.telegram.org/constructor/help.userInfoEmpty new file mode 100644 index 0000000000..785d3211d1 --- /dev/null +++ b/data/core.telegram.org/constructor/help.userInfoEmpty @@ -0,0 +1,132 @@ + + + + + help.userInfoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.userInfoEmpty

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.UserInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/highScore.html b/data/core.telegram.org/constructor/highScore.html new file mode 100644 index 0000000000..f7d137486c --- /dev/null +++ b/data/core.telegram.org/constructor/highScore.html @@ -0,0 +1,157 @@ + + + + + highScore + + + + + + + + + + + + + +
+ +
+
+
+ +

highScore

+ +

Game highscore

+

+ +
+
highScore#73a379eb pos:int user_id:long score:int = HighScore;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
posintPosition in highscore list
user_idlongUser ID
scoreintScore
+

Type

+

HighScore

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html new file mode 100644 index 0000000000..34576da4ac --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeMegagroup + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeMegagroup

+ +

The inline query was sent in a supergroup

+

+ +
+
inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html new file mode 100644 index 0000000000..22b1e8a59c --- /dev/null +++ b/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html @@ -0,0 +1,132 @@ + + + + + inlineQueryPeerTypeSameBotPM + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeSameBotPM

+ +

The inline query was sent in a private chat with the bot itself

+

+ +
+
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineResultDocument.html b/data/core.telegram.org/constructor/inputBotInlineResultDocument.html new file mode 100644 index 0000000000..7201913625 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineResultDocument.html @@ -0,0 +1,179 @@ + + + + + inputBotInlineResultDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultDocument

+ +

Document (media of any type except for photos)

+

+ +
+
inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
documentInputDocumentDocument to send
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html b/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html new file mode 100644 index 0000000000..cb0d8308c0 --- /dev/null +++ b/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html @@ -0,0 +1,164 @@ + + + + + inputBotInlineResultPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResultPhoto

+ +

Photo

+

+ +
+
inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringResult ID
typestringResult type (see bot API docs)
photoInputPhotoPhoto to send
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChannelEmpty.html b/data/core.telegram.org/constructor/inputChannelEmpty.html new file mode 100644 index 0000000000..cbda28bc2a --- /dev/null +++ b/data/core.telegram.org/constructor/inputChannelEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChannelEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannelEmpty

+ +

Represents the absence of a channel

+

+ +
+
inputChannelEmpty#ee8c1e86 = InputChannel;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChannel

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChatPhoto.html b/data/core.telegram.org/constructor/inputChatPhoto.html new file mode 100644 index 0000000000..6b4d04dc66 --- /dev/null +++ b/data/core.telegram.org/constructor/inputChatPhoto.html @@ -0,0 +1,147 @@ + + + + + inputChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatPhoto

+ +

Existing photo to be set as a chat profile photo.

+

+ +
+
inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoExisting photo
+

Type

+

InputChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputChatPhotoEmpty.html b/data/core.telegram.org/constructor/inputChatPhotoEmpty.html new file mode 100644 index 0000000000..0bbacd38ac --- /dev/null +++ b/data/core.telegram.org/constructor/inputChatPhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChatPhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatPhotoEmpty

+ +

Empty constructor, remove group photo.

+

+ +
+
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChatPhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html new file mode 100644 index 0000000000..6ee3bb2418 --- /dev/null +++ b/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html @@ -0,0 +1,132 @@ + + + + + inputCheckPasswordEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputCheckPasswordEmpty

+ +

There is no password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputCheckPasswordSRP

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputDocumentEmpty.html b/data/core.telegram.org/constructor/inputDocumentEmpty.html new file mode 100644 index 0000000000..fd5b82388f --- /dev/null +++ b/data/core.telegram.org/constructor/inputDocumentEmpty.html @@ -0,0 +1,132 @@ + + + + + inputDocumentEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocumentEmpty

+ +

Empty constructor.

+

+ +
+
inputDocumentEmpty#72f0eaae = InputDocument;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputDocument

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html b/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html new file mode 100644 index 0000000000..d4ff3e220e --- /dev/null +++ b/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html @@ -0,0 +1,132 @@ + + + + + inputEncryptedFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputEncryptedFileEmpty

+ +

Empty constructor.

+

+ +
+
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputEncryptedFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputFileBig.html b/data/core.telegram.org/constructor/inputFileBig.html new file mode 100644 index 0000000000..c173b0a37d --- /dev/null +++ b/data/core.telegram.org/constructor/inputFileBig.html @@ -0,0 +1,160 @@ + + + + + inputFileBig + + + + + + + + + + + + + +
+ +
+
+
+ +

inputFileBig

+ +

Assigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.

+

+ +
+
inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of parts saved
namestringFull file name
+

Type

+

InputFile

+

Related pages

+

upload.saveBigFilePart

+

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html new file mode 100644 index 0000000000..2de7853f5c --- /dev/null +++ b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html @@ -0,0 +1,176 @@ + + + + + inputKeyboardButtonUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

inputKeyboardButtonUrlAuth

+ +

Button to request a user to authorize via URL using Seamless Telegram Login.

+

+ +
+
inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueSet this flag to request the permission for your bot to send messages to the user.
textstringButton text
fwd_textflags.1?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.
NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
botInputUserUsername of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
+

Type

+

KeyboardButton

+

Related pages

+

Telegram Login Widget

+

messages.acceptUrlAuth

+

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaContact.html b/data/core.telegram.org/constructor/inputMediaContact.html new file mode 100644 index 0000000000..0cfb9daa93 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaContact.html @@ -0,0 +1,162 @@ + + + + + inputMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaContact

+ +

Phonebook contact

+

+ +
+
inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringContact vcard
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaGeoPoint.html b/data/core.telegram.org/constructor/inputMediaGeoPoint.html new file mode 100644 index 0000000000..5a5dc83319 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaGeoPoint.html @@ -0,0 +1,147 @@ + + + + + inputMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaGeoPoint

+ +

Map.

+

+ +
+
inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeoPoint
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaPhotoExternal.html b/data/core.telegram.org/constructor/inputMediaPhotoExternal.html new file mode 100644 index 0000000000..1371cdf4df --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaPhotoExternal.html @@ -0,0 +1,157 @@ + + + + + inputMediaPhotoExternal + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPhotoExternal

+ +

New photo that will be uploaded by the server using the specified URL

+

+ +
+
inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the photo
ttl_secondsflags.0?intSelf-destruct time to live of photo
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html new file mode 100644 index 0000000000..809c3dffe9 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html @@ -0,0 +1,165 @@ + + + + + inputMediaUploadedPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaUploadedPhoto

+ +

Photo

+

+ +
+
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileThe uploaded file
stickersflags.0?Vector<InputDocument>Attached mask stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing photo
+

Type

+

InputMedia

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagePinned.html b/data/core.telegram.org/constructor/inputMessagePinned.html new file mode 100644 index 0000000000..8f1e3668e0 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagePinned.html @@ -0,0 +1,132 @@ + + + + + inputMessagePinned + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagePinned

+ +

Pinned message

+

+ +
+
inputMessagePinned#86872538 = InputMessage;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterGeo.html b/data/core.telegram.org/constructor/inputMessagesFilterGeo.html new file mode 100644 index 0000000000..9996ac6dab --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterGeo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterGeo

+ +

Return only messages containing geolocations

+

+ +
+
inputMessagesFilterGeo#e7026d0d = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMusic.html b/data/core.telegram.org/constructor/inputMessagesFilterMusic.html new file mode 100644 index 0000000000..5ede2afb2b --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterMusic.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterMusic + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterMusic

+ +

Return only messages containing audio files

+

+ +
+
inputMessagesFilterMusic#3751b49e = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html b/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html new file mode 100644 index 0000000000..44315d5366 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html @@ -0,0 +1,135 @@ + + + + + inputMessagesFilterMyMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterMyMentions

+ +

Return only messages where the current user was mentioned.

+

+ +
+
inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html new file mode 100644 index 0000000000..1f2ea2876a --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterRoundVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterRoundVideo

+ +

Return only round videos

+

+ +
+
inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html new file mode 100644 index 0000000000..26c674d727 --- /dev/null +++ b/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterRoundVoice + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterRoundVoice

+ +

Return only round videos and voice notes

+

+ +
+
inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html new file mode 100644 index 0000000000..5b30662baa --- /dev/null +++ b/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html @@ -0,0 +1,162 @@ + + + + + inputPeerPhotoFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerPhotoFileLocation

+ +

Location of profile photo of channel/group/supergroup/user

+

+ +
+
inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
bigflags.0?trueWhether to download the high-quality version of the picture
peerInputPeerThe peer whose profile picture should be downloaded
photo_idlongPhoto ID
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html b/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html new file mode 100644 index 0000000000..bf8280fd43 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyChatInvite

+ +

Whether the user can be invited to chats

+

+ +
+
inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html b/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html new file mode 100644 index 0000000000..26ee4c83a1 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyForwards

+ +

Whether messages forwarded from this user will be anonymous

+

+ +
+
inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html new file mode 100644 index 0000000000..27039b54a8 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyPhoneCall

+ +

Whether the user will accept phone calls

+

+ +
+
inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html new file mode 100644 index 0000000000..b5cc1c6b2e --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyStatusTimestamp + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyStatusTimestamp

+ +

Whether we can see the exact last online timestamp of the user

+

+ +
+
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html new file mode 100644 index 0000000000..572c06af8d --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueAllowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueAllowUsers

+ +

Allow only certain users

+

+ +
+
inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>Allowed users
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html new file mode 100644 index 0000000000..57404c0f39 --- /dev/null +++ b/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html @@ -0,0 +1,147 @@ + + + + + inputPrivacyValueDisallowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyValueDisallowUsers

+ +

Disallow only certain users

+

+ +
+
inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>Users to disallow
+

Type

+

InputPrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html b/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html new file mode 100644 index 0000000000..4395262675 --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonGeoIrrelevant + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonGeoIrrelevant

+ +

Report an irrelevant geogroup

+

+ +
+
inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputReportReasonOther.html b/data/core.telegram.org/constructor/inputReportReasonOther.html new file mode 100644 index 0000000000..208a6ae511 --- /dev/null +++ b/data/core.telegram.org/constructor/inputReportReasonOther.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonOther + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonOther

+ +

Other

+

+ +
+
inputReportReasonOther#c1e4a2b1 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetID.html b/data/core.telegram.org/constructor/inputStickerSetID.html new file mode 100644 index 0000000000..021e80cfb8 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetID.html @@ -0,0 +1,152 @@ + + + + + inputStickerSetID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetID

+ +

Stickerset by ID

+

+ +
+
inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickerSetThumb.html b/data/core.telegram.org/constructor/inputStickerSetThumb.html new file mode 100644 index 0000000000..47c63b6c53 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickerSetThumb.html @@ -0,0 +1,155 @@ + + + + + inputStickerSetThumb + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetThumb

+ +

Location of stickerset thumbnail (see files)

+

+ +
+
inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetSticker set
thumb_versionintThumbnail version
+

Type

+

InputFileLocation

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html new file mode 100644 index 0000000000..85e684cd61 --- /dev/null +++ b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html @@ -0,0 +1,147 @@ + + + + + inputStickeredMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickeredMediaPhoto

+ +

A photo with stickers attached

+

+ +
+
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPhotoThe photo
+

Type

+

InputStickeredMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputTheme.html b/data/core.telegram.org/constructor/inputTheme.html new file mode 100644 index 0000000000..2b385c80c6 --- /dev/null +++ b/data/core.telegram.org/constructor/inputTheme.html @@ -0,0 +1,152 @@ + + + + + inputTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

inputTheme

+ +

Theme

+

+ +
+
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/inputThemeSettings.html b/data/core.telegram.org/constructor/inputThemeSettings.html new file mode 100644 index 0000000000..afd0437507 --- /dev/null +++ b/data/core.telegram.org/constructor/inputThemeSettings.html @@ -0,0 +1,182 @@ + + + + + inputThemeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

inputThemeSettings

+ +

Theme settings

+

+ +
+
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message
base_themeBaseThemeDefault theme on which this theme is based
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?InputWallPaperWallpaper
wallpaper_settingsflags.1?WallPaperSettingsWallpaper settings
+

Type

+

InputThemeSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonObject.html b/data/core.telegram.org/constructor/jsonObject.html new file mode 100644 index 0000000000..a8fb071e23 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonObject.html @@ -0,0 +1,147 @@ + + + + + jsonObject + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonObject

+ +

JSON object value

+

+ +
+
jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueVector<JSONObjectValue>Values
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/jsonString.html b/data/core.telegram.org/constructor/jsonString.html new file mode 100644 index 0000000000..7bef87ac42 --- /dev/null +++ b/data/core.telegram.org/constructor/jsonString.html @@ -0,0 +1,147 @@ + + + + + jsonString + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonString

+ +

JSON string

+

+ +
+
jsonString#b71e767a value:string = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valuestringValue
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonCallback.html b/data/core.telegram.org/constructor/keyboardButtonCallback.html new file mode 100644 index 0000000000..5b5263399f --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonCallback.html @@ -0,0 +1,167 @@ + + + + + keyboardButtonCallback + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonCallback

+ +

Callback button

+

+ +
+
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
requires_passwordflags.0?trueWhether the user should verify his identity by entering his 2FA SRP parameters to the messages.getBotCallbackAnswer method. NOTE: telegram and the bot WILL NOT have access to the plaintext password, thanks to SRP. This button is mainly used by the official @botfather bot, for verifying the user's identity before transferring ownership of a bot to another user.
textstringButton text
databytesCallback data
+

Type

+

KeyboardButton

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

messages.getBotCallbackAnswer

+

Press an inline callback button and get a callback answer from the bot

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonGame.html b/data/core.telegram.org/constructor/keyboardButtonGame.html new file mode 100644 index 0000000000..f12baa8348 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonGame.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonGame + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonGame

+ +

Button to start a game

+

+ +
+
keyboardButtonGame#50f41ccf text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html b/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html new file mode 100644 index 0000000000..2d93039361 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRequestPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRequestPhone

+ +

Button to request a user's phone number

+

+ +
+
keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringButton text
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/keyboardButtonRow.html b/data/core.telegram.org/constructor/keyboardButtonRow.html new file mode 100644 index 0000000000..96aacbfdf3 --- /dev/null +++ b/data/core.telegram.org/constructor/keyboardButtonRow.html @@ -0,0 +1,147 @@ + + + + + keyboardButtonRow + + + + + + + + + + + + + +
+ +
+
+
+ +

keyboardButtonRow

+ +

Inline keyboard row

+

+ +
+
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
buttonsVector<KeyboardButton>Bot or inline keyboard buttons
+

Type

+

KeyboardButtonRow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatAddUser.html b/data/core.telegram.org/constructor/messageActionChatAddUser.html new file mode 100644 index 0000000000..659e185341 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatAddUser.html @@ -0,0 +1,147 @@ + + + + + messageActionChatAddUser + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatAddUser

+ +

New member in the group

+

+ +
+
messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Users that were invited to the chat
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionChatEditPhoto.html b/data/core.telegram.org/constructor/messageActionChatEditPhoto.html new file mode 100644 index 0000000000..43c505f3d8 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionChatEditPhoto.html @@ -0,0 +1,147 @@ + + + + + messageActionChatEditPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionChatEditPhoto

+ +

Group profile changed

+

+ +
+
messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
photoPhotoNew group pofile photo
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageActionEmpty.html b/data/core.telegram.org/constructor/messageActionEmpty.html new file mode 100644 index 0000000000..a886e79552 --- /dev/null +++ b/data/core.telegram.org/constructor/messageActionEmpty.html @@ -0,0 +1,132 @@ + + + + + messageActionEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionEmpty

+ +

Empty constructor.

+

+ +
+
messageActionEmpty#b6aef7b0 = MessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBankCard.html b/data/core.telegram.org/constructor/messageEntityBankCard.html new file mode 100644 index 0000000000..d1dc75a1f5 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBankCard.html @@ -0,0 +1,152 @@ + + + + + messageEntityBankCard + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBankCard

+ +

Indicates a credit card number

+

+ +
+
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBlockquote.html b/data/core.telegram.org/constructor/messageEntityBlockquote.html new file mode 100644 index 0000000000..818551c8ff --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBlockquote.html @@ -0,0 +1,152 @@ + + + + + messageEntityBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBlockquote

+ +

Message entity representing a block quote.

+

+ +
+
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityBotCommand.html b/data/core.telegram.org/constructor/messageEntityBotCommand.html new file mode 100644 index 0000000000..594b2c97b6 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityBotCommand.html @@ -0,0 +1,152 @@ + + + + + messageEntityBotCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBotCommand

+ +

Message entity representing a bot /command

+

+ +
+
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityEmail.html b/data/core.telegram.org/constructor/messageEntityEmail.html new file mode 100644 index 0000000000..99324ce92b --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityEmail.html @@ -0,0 +1,152 @@ + + + + + messageEntityEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityEmail

+ +

Message entity representing an email@example.com.

+

+ +
+
messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityMention.html b/data/core.telegram.org/constructor/messageEntityMention.html new file mode 100644 index 0000000000..4584daf19d --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityMention.html @@ -0,0 +1,155 @@ + + + + + messageEntityMention + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityMention

+ +

Message entity mentioning the current user

+

+ +
+
messageEntityMention#fa04579d offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityMentionName.html b/data/core.telegram.org/constructor/messageEntityMentionName.html new file mode 100644 index 0000000000..efcaa4849f --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityMentionName.html @@ -0,0 +1,162 @@ + + + + + messageEntityMentionName + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityMentionName

+ +

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

+

+ +
+
messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idlongIdentifier of the user that was mentioned
+

Type

+

MessageEntity

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

inputMessageEntityMentionName

+

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityPhone.html b/data/core.telegram.org/constructor/messageEntityPhone.html new file mode 100644 index 0000000000..794f1b0197 --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityPhone.html @@ -0,0 +1,152 @@ + + + + + messageEntityPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityPhone

+ +

Message entity representing a phone number.

+

+ +
+
messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityUnderline.html b/data/core.telegram.org/constructor/messageEntityUnderline.html new file mode 100644 index 0000000000..a74348e32e --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityUnderline.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnderline

+ +

Message entity representing underlined text.

+

+ +
+
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageEntityUnknown.html b/data/core.telegram.org/constructor/messageEntityUnknown.html new file mode 100644 index 0000000000..bb67ce7f8c --- /dev/null +++ b/data/core.telegram.org/constructor/messageEntityUnknown.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnknown

+ +

Unknown message entity

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaAudio.html b/data/core.telegram.org/constructor/messageMediaAudio.html new file mode 100644 index 0000000000..4b99bc798d --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaAudio.html @@ -0,0 +1,147 @@ + + + + + messageMediaAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaAudio

+ +

Attached audio file.

+

+ +
+
Constructor schema is available as of layer 46. Switch »

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
audioAudioAudi file
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaInvoice.html b/data/core.telegram.org/constructor/messageMediaInvoice.html new file mode 100644 index 0000000000..e06d694510 --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaInvoice.html @@ -0,0 +1,198 @@ + + + + + messageMediaInvoice + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaInvoice

+ +

Invoice

+

+ +
+
messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueWhether the shipping address was requested
testflags.3?trueWhether this is an example invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
receipt_msg_idflags.2?intMessage ID of receipt: if set, clients should change the text of the first keyboardButtonBuy button always attached to the message to a localized version of the word Receipt
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
start_paramstringUnique bot deep-linking parameter that can be used to generate this invoice
+

Type

+

MessageMedia

+

Related pages

+

keyboardButtonBuy

+

Button to buy a product

+

message

+

A message

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaPoll.html b/data/core.telegram.org/constructor/messageMediaPoll.html new file mode 100644 index 0000000000..d68156fd1b --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaPoll.html @@ -0,0 +1,152 @@ + + + + + messageMediaPoll + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaPoll

+ +

Poll

+

+ +
+
messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
pollPollThe poll
resultsPollResultsThe results of the poll
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messageMediaUnsupported.html b/data/core.telegram.org/constructor/messageMediaUnsupported.html new file mode 100644 index 0000000000..0a7a4728fc --- /dev/null +++ b/data/core.telegram.org/constructor/messageMediaUnsupported.html @@ -0,0 +1,132 @@ + + + + + messageMediaUnsupported + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaUnsupported

+ +

Current version of the client does not support this media type.

+

+ +
+
messageMediaUnsupported#9f84f49e = MessageMedia;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.chatsSlice b/data/core.telegram.org/constructor/messages.chatsSlice new file mode 100644 index 0000000000..22e0895dec --- /dev/null +++ b/data/core.telegram.org/constructor/messages.chatsSlice @@ -0,0 +1,155 @@ + + + + + messages.chatsSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatsSlice

+ +

Partial list of chats, more would have to be fetched with pagination

+

+ +
+
messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of results that were found server-side (not all are included in chats)
chatsVector<Chat>Chats
+

Type

+

messages.Chats

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.dhConfig b/data/core.telegram.org/constructor/messages.dhConfig new file mode 100644 index 0000000000..afb3f3c3f0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.dhConfig @@ -0,0 +1,162 @@ + + + + + messages.dhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dhConfig

+ +

New set of configuring parameters.

+

+ +
+
messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
gintNew value prime, see Wikipedia
pbytesNew value primitive root, see Wikipedia
versionintVestion of set of parameters
randombytesRandom sequence of bytes of assigned length
+

Type

+

messages.DhConfig

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.exportedChatInvite b/data/core.telegram.org/constructor/messages.exportedChatInvite new file mode 100644 index 0000000000..8d965aabd0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.exportedChatInvite @@ -0,0 +1,152 @@ + + + + + messages.exportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvite

+ +

Info about a chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteInfo about the chat invite
usersVector<User>Mentioned users
+

Type

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.exportedChatInvites b/data/core.telegram.org/constructor/messages.exportedChatInvites new file mode 100644 index 0000000000..5fbcb7dc5e --- /dev/null +++ b/data/core.telegram.org/constructor/messages.exportedChatInvites @@ -0,0 +1,157 @@ + + + + + messages.exportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of invites exported by the admin
invitesVector<ExportedChatInvite>Exported invites
usersVector<User>Info about the admin
+

Type

+

messages.ExportedChatInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.highScores b/data/core.telegram.org/constructor/messages.highScores new file mode 100644 index 0000000000..a6da22ce25 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.highScores @@ -0,0 +1,152 @@ + + + + + messages.highScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.highScores

+ +

Highscores in a game

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scoresVector<HighScore>Highscores
usersVector<User>Users, associated to the highscores
+

Type

+

messages.HighScores

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.historyImportParsed b/data/core.telegram.org/constructor/messages.historyImportParsed new file mode 100644 index 0000000000..2c49dcc24e --- /dev/null +++ b/data/core.telegram.org/constructor/messages.historyImportParsed @@ -0,0 +1,166 @@ + + + + + messages.historyImportParsed + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.historyImportParsed

+ +

Contains information about a chat export file generated by a foreign chat app, click here for more info.
+If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pmflags.0?trueThe chat export file was generated from a private chat.
groupflags.1?trueThe chat export file was generated from a group chat.
titleflags.2?stringTitle of the chat.
+

Type

+

messages.HistoryImportParsed

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.savedGifsNotModified b/data/core.telegram.org/constructor/messages.savedGifsNotModified new file mode 100644 index 0000000000..24e390a658 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.savedGifsNotModified @@ -0,0 +1,132 @@ + + + + + messages.savedGifsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.savedGifsNotModified

+ +

No new saved gifs were found

+

+ +
+
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.SavedGifs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.sentEncryptedMessage b/data/core.telegram.org/constructor/messages.sentEncryptedMessage new file mode 100644 index 0000000000..f88f8392e0 --- /dev/null +++ b/data/core.telegram.org/constructor/messages.sentEncryptedMessage @@ -0,0 +1,147 @@ + + + + + messages.sentEncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sentEncryptedMessage

+ +

Message without file attachemts sent to an encrypted file.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dateintDate of sending
+

Type

+

messages.SentEncryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/messages.stickers b/data/core.telegram.org/constructor/messages.stickers new file mode 100644 index 0000000000..9eb9b02d0b --- /dev/null +++ b/data/core.telegram.org/constructor/messages.stickers @@ -0,0 +1,155 @@ + + + + + messages.stickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickers

+ +

Found stickers

+

+ +
+
messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
stickersVector<Document>Stickers
+

Type

+

messages.Stickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/null.html b/data/core.telegram.org/constructor/null.html new file mode 100644 index 0000000000..3c3bb87d9d --- /dev/null +++ b/data/core.telegram.org/constructor/null.html @@ -0,0 +1,132 @@ + + + + + null + + + + + + + + + + + + + +
+ +
+
+
+ +

null

+ +

Corresponds to an arbitrary empty object.

+

+ +
+
null#56730bcc = Null;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Null

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockBlockquote.html b/data/core.telegram.org/constructor/pageBlockBlockquote.html new file mode 100644 index 0000000000..1d207c8fce --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockBlockquote.html @@ -0,0 +1,152 @@ + + + + + pageBlockBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockBlockquote

+ +

Quote (equivalent to the HTML <blockquote>)

+

+ +
+
pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextQuote contents
captionRichTextCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockCollage.html b/data/core.telegram.org/constructor/pageBlockCollage.html new file mode 100644 index 0000000000..f6a8fd5db7 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockCollage.html @@ -0,0 +1,152 @@ + + + + + pageBlockCollage + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockCollage

+ +

Collage of media

+

+ +
+
pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageBlock>Media elements
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockDivider.html b/data/core.telegram.org/constructor/pageBlockDivider.html new file mode 100644 index 0000000000..c760735f55 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockDivider.html @@ -0,0 +1,132 @@ + + + + + pageBlockDivider + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockDivider

+ +

An empty block separating a page

+

+ +
+
pageBlockDivider#db20b188 = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockFooter.html b/data/core.telegram.org/constructor/pageBlockFooter.html new file mode 100644 index 0000000000..b168e0bb1f --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockFooter.html @@ -0,0 +1,147 @@ + + + + + pageBlockFooter + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockFooter

+ +

Page footer

+

+ +
+
pageBlockFooter#48870999 text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextContents
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageBlockVideo.html b/data/core.telegram.org/constructor/pageBlockVideo.html new file mode 100644 index 0000000000..662ddf3ab6 --- /dev/null +++ b/data/core.telegram.org/constructor/pageBlockVideo.html @@ -0,0 +1,167 @@ + + + + + pageBlockVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockVideo

+ +

Video

+

+ +
+
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageListItemBlocks.html b/data/core.telegram.org/constructor/pageListItemBlocks.html new file mode 100644 index 0000000000..93be908282 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListItemBlocks.html @@ -0,0 +1,147 @@ + + + + + pageListItemBlocks + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListItemBlocks

+ +

List item

+

+ +
+
pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
blocksVector<PageBlock>Blocks
+

Type

+

PageListItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageListItemText.html b/data/core.telegram.org/constructor/pageListItemText.html new file mode 100644 index 0000000000..b04f4f3b02 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListItemText.html @@ -0,0 +1,147 @@ + + + + + pageListItemText + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListItemText

+ +

List item

+

+ +
+
pageListItemText#b92fb6cd text:RichText = PageListItem;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageListItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pageListOrderedItemText.html b/data/core.telegram.org/constructor/pageListOrderedItemText.html new file mode 100644 index 0000000000..12982f75d7 --- /dev/null +++ b/data/core.telegram.org/constructor/pageListOrderedItemText.html @@ -0,0 +1,152 @@ + + + + + pageListOrderedItemText + + + + + + + + + + + + + +
+ +
+
+
+ +

pageListOrderedItemText

+ +

Ordered list of text items

+

+ +
+
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
numstringNumber of element within ordered list
textRichTextText
+

Type

+

PageListOrderedItem

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/paymentRequestedInfo.html b/data/core.telegram.org/constructor/paymentRequestedInfo.html new file mode 100644 index 0000000000..2e8b57c64b --- /dev/null +++ b/data/core.telegram.org/constructor/paymentRequestedInfo.html @@ -0,0 +1,167 @@ + + + + + paymentRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentRequestedInfo

+ +

Order info provided by the user

+

+ +
+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
nameflags.0?stringUser's full name
phoneflags.1?stringUser's phone number
emailflags.2?stringUser's email address
shipping_addressflags.3?PostAddressUser's shipping address
+

Type

+

PaymentRequestedInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.paymentForm b/data/core.telegram.org/constructor/payments.paymentForm new file mode 100644 index 0000000000..920813f6f6 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.paymentForm @@ -0,0 +1,210 @@ + + + + + payments.paymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentForm

+ +

Payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_save_credentialsflags.2?trueWhether the user can choose to save credentials.
password_missingflags.3?trueIndicates that the user can save payment credentials, but only after setting up a 2FA password (currently the account doesn't have a 2FA password)
form_idlongForm ID
bot_idlongBot ID
invoiceInvoiceInvoice
provider_idlongPayment provider ID.
urlstringPayment form URL
native_providerflags.4?stringPayment provider name.
One of the following:
- stripe
native_paramsflags.4?DataJSONContains information about the payment provider, if available, to support it natively without the need for opening the URL.
A JSON object that can contain the following fields:

- apple_pay_merchant_id: Apple Pay merchant ID
- google_pay_public_key: Google Pay public key
- need_country: True, if the user country must be provided,
- need_zip: True, if the user ZIP/postal code must be provided,
- need_cardholder_name: True, if the cardholder name must be provided
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
saved_credentialsflags.1?PaymentSavedCredentialsContains information about saved card credentials
usersVector<User>Users
+

Type

+

payments.PaymentForm

+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/payments.paymentResult b/data/core.telegram.org/constructor/payments.paymentResult new file mode 100644 index 0000000000..5306a7d5c5 --- /dev/null +++ b/data/core.telegram.org/constructor/payments.paymentResult @@ -0,0 +1,147 @@ + + + + + payments.paymentResult + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentResult

+ +

Payment result

+

+ +
+
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
updatesUpdatesInfo about the payment
+

Type

+

payments.PaymentResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerLocated.html b/data/core.telegram.org/constructor/peerLocated.html new file mode 100644 index 0000000000..ead8d9e2e3 --- /dev/null +++ b/data/core.telegram.org/constructor/peerLocated.html @@ -0,0 +1,157 @@ + + + + + peerLocated + + + + + + + + + + + + + +
+ +
+
+
+ +

peerLocated

+ +

Peer geolocated nearby

+

+ +
+
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeerPeer
expiresintValidity period of current data
distanceintDistance from the peer in meters
+

Type

+

PeerLocated

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/peerUser.html b/data/core.telegram.org/constructor/peerUser.html new file mode 100644 index 0000000000..dd682b961d --- /dev/null +++ b/data/core.telegram.org/constructor/peerUser.html @@ -0,0 +1,147 @@ + + + + + peerUser + + + + + + + + + + + + + +
+ +
+
+
+ +

peerUser

+ +

Chat partner

+

+ +
+
peerUser#59511722 user_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phone.groupParticipants b/data/core.telegram.org/constructor/phone.groupParticipants new file mode 100644 index 0000000000..639e22c978 --- /dev/null +++ b/data/core.telegram.org/constructor/phone.groupParticipants @@ -0,0 +1,175 @@ + + + + + phone.groupParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.groupParticipants

+ +

Info about the participants of a group call or livestream

+

+ +
+
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of participants
participantsVector<GroupCallParticipant>List of participants
next_offsetstringIf not empty, the specified list of participants is partial, and more participants can be fetched specifying this parameter as offset in phone.getGroupParticipants.
chatsVector<Chat>Mentioned chats
usersVector<User>Mentioned users
versionintVersion info
+

Type

+

phone.GroupParticipants

+

Related pages

+

phone.getGroupParticipants

+

Get group call participants

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/phoneCallAccepted.html b/data/core.telegram.org/constructor/phoneCallAccepted.html new file mode 100644 index 0000000000..86e8ad2759 --- /dev/null +++ b/data/core.telegram.org/constructor/phoneCallAccepted.html @@ -0,0 +1,189 @@ + + + + + phoneCallAccepted + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallAccepted

+ +

An accepted phone call

+

+ +
+
phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongID of accepted phone call
access_hashlongAccess hash of phone call
dateintWhen was the call accepted
admin_idlongID of the call creator
participant_idlongID of the other user in the call
g_bbytesB parameter for secure E2E phone call key exchange
protocolPhoneCallProtocolProtocol to use for phone call
+

Type

+

PhoneCall

+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoPathSize.html b/data/core.telegram.org/constructor/photoPathSize.html new file mode 100644 index 0000000000..51ffd63c8a --- /dev/null +++ b/data/core.telegram.org/constructor/photoPathSize.html @@ -0,0 +1,155 @@ + + + + + photoPathSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoPathSize

+ +

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.

+

+ +
+
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringAlways j
bytesbytesCompressed SVG path payload, see here for decompression instructions
+

Type

+

PhotoSize

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoSizeEmpty.html b/data/core.telegram.org/constructor/photoSizeEmpty.html new file mode 100644 index 0000000000..f32028a6ae --- /dev/null +++ b/data/core.telegram.org/constructor/photoSizeEmpty.html @@ -0,0 +1,150 @@ + + + + + photoSizeEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

photoSizeEmpty

+ +

Empty constructor. Image with this thumbnail is unavailable.

+

+ +
+
photoSizeEmpty#e17e23c type:string = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type (see. photoSize)
+

Type

+

PhotoSize

+

Related pages

+

photoSize

+

Image description.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photoStrippedSize.html b/data/core.telegram.org/constructor/photoStrippedSize.html new file mode 100644 index 0000000000..6fb252ccfb --- /dev/null +++ b/data/core.telegram.org/constructor/photoStrippedSize.html @@ -0,0 +1,159 @@ + + + + + photoStrippedSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoStrippedSize

+ +

A low-resolution compressed JPG payload

+

+ +
+
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
bytesbytesThumbnail data, see here for more info on decompression »
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See the photoSize constructor.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

photoSize

+

Image description.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/photos.photo b/data/core.telegram.org/constructor/photos.photo new file mode 100644 index 0000000000..cdd463d8b2 --- /dev/null +++ b/data/core.telegram.org/constructor/photos.photo @@ -0,0 +1,152 @@ + + + + + photos.photo + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photo

+ +

Photo with auxiliary data.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
photoPhotoPhoto
usersVector<User>Users
+

Type

+

photos.Photo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pollAnswer.html b/data/core.telegram.org/constructor/pollAnswer.html new file mode 100644 index 0000000000..92870d7ac6 --- /dev/null +++ b/data/core.telegram.org/constructor/pollAnswer.html @@ -0,0 +1,155 @@ + + + + + pollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

pollAnswer

+ +

A possible answer of a poll

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
+

Type

+

PollAnswer

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/pollResults.html b/data/core.telegram.org/constructor/pollResults.html new file mode 100644 index 0000000000..f21c0eb9c6 --- /dev/null +++ b/data/core.telegram.org/constructor/pollResults.html @@ -0,0 +1,184 @@ + + + + + pollResults + + + + + + + + + + + + + +
+ +
+
+
+ +

pollResults

+ +

Results of poll

+

+ +
+
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
minflags.0?trueSimilar to min objects, used for poll constructors that are the same for all users so they don't have option chosen by the current user (you can use messages.getPollResults to get the full poll results).
resultsflags.1?Vector<PollAnswerVoters>Poll results
total_votersflags.2?intTotal number of people that voted in the poll
recent_votersflags.3?Vector<long>IDs of the last users that recently voted in the poll
solutionflags.4?stringExplanation of quiz solution
solution_entitiesflags.4?Vector<MessageEntity>Message entities for styled text in quiz solution
+

Type

+

PollResults

+

Related pages

+

Min constructors

+

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

+

messages.getPollResults

+

Get poll results

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/postAddress.html b/data/core.telegram.org/constructor/postAddress.html new file mode 100644 index 0000000000..a278e6fd1e --- /dev/null +++ b/data/core.telegram.org/constructor/postAddress.html @@ -0,0 +1,172 @@ + + + + + postAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

postAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
street_line1stringFirst line for the address
street_line2stringSecond line for the address
citystringCity
statestringState, if applicable (empty otherwise)
country_iso2stringISO 3166-1 alpha-2 country code
post_codestringAddress post code
+

Type

+

PostAddress

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html b/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html new file mode 100644 index 0000000000..90dde99417 --- /dev/null +++ b/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html @@ -0,0 +1,132 @@ + + + + + privacyKeyAddedByPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyAddedByPhone

+ +

Whether people can add you to their contact list by your phone number

+

+ +
+
privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/privacyValueAllowContacts.html b/data/core.telegram.org/constructor/privacyValueAllowContacts.html new file mode 100644 index 0000000000..b93c047dfc --- /dev/null +++ b/data/core.telegram.org/constructor/privacyValueAllowContacts.html @@ -0,0 +1,132 @@ + + + + + privacyValueAllowContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueAllowContacts

+ +

Allow all contacts

+

+ +
+
privacyValueAllowContacts#fffe1bac = PrivacyRule;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlUnknown.html b/data/core.telegram.org/constructor/recentMeUrlUnknown.html new file mode 100644 index 0000000000..48665c4550 --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlUnknown.html @@ -0,0 +1,147 @@ + + + + + recentMeUrlUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUnknown

+ +

Unknown t.me url

+

+ +
+
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/recentMeUrlUser.html b/data/core.telegram.org/constructor/recentMeUrlUser.html new file mode 100644 index 0000000000..b035f11485 --- /dev/null +++ b/data/core.telegram.org/constructor/recentMeUrlUser.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlUser + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUser

+ +

Recent t.me link to a user

+

+ +
+
recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
user_idlongUser ID
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/replyInlineMarkup.html b/data/core.telegram.org/constructor/replyInlineMarkup.html new file mode 100644 index 0000000000..358df9d4e8 --- /dev/null +++ b/data/core.telegram.org/constructor/replyInlineMarkup.html @@ -0,0 +1,147 @@ + + + + + replyInlineMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

replyInlineMarkup

+ +

Bot or inline keyboard

+

+ +
+
replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
rowsVector<KeyboardButtonRow>Bot or inline keyboard rows
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/replyKeyboardHide.html b/data/core.telegram.org/constructor/replyKeyboardHide.html new file mode 100644 index 0000000000..1e81784d4a --- /dev/null +++ b/data/core.telegram.org/constructor/replyKeyboardHide.html @@ -0,0 +1,152 @@ + + + + + replyKeyboardHide + + + + + + + + + + + + + +
+ +
+
+
+ +

replyKeyboardHide

+ +

Hide sent bot keyboard

+

+ +
+
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
selectiveflags.2?trueUse this flag if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureFile.html b/data/core.telegram.org/constructor/secureFile.html new file mode 100644 index 0000000000..e8f04136c0 --- /dev/null +++ b/data/core.telegram.org/constructor/secureFile.html @@ -0,0 +1,180 @@ + + + + + secureFile + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFile

+ +

Secure passport file, for more info see the passport docs »

+

+ +
+
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
sizeintFile size
dc_idintDC ID
dateintDate of upload
file_hashbytesFile hash
secretbytesSecret
+

Type

+

SecureFile

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureFileEmpty.html b/data/core.telegram.org/constructor/secureFileEmpty.html new file mode 100644 index 0000000000..e038aa90f8 --- /dev/null +++ b/data/core.telegram.org/constructor/secureFileEmpty.html @@ -0,0 +1,132 @@ + + + + + secureFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFileEmpty

+ +

Empty constructor

+

+ +
+
secureFileEmpty#64199744 = SecureFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html new file mode 100644 index 0000000000..cc27b9b16d --- /dev/null +++ b/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html @@ -0,0 +1,147 @@ + + + + + securePasswordKdfAlgoSHA512 + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoSHA512

+ +

SHA512 KDF algo

+

+ +
+
securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
saltbytesSalt
+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html new file mode 100644 index 0000000000..efedcb8096 --- /dev/null +++ b/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html @@ -0,0 +1,132 @@ + + + + + securePasswordKdfAlgoUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoUnknown

+ +

Unknown KDF algo (most likely the client has to be updated)

+

+ +
+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/securePlainPhone.html b/data/core.telegram.org/constructor/securePlainPhone.html new file mode 100644 index 0000000000..68faa5d2ad --- /dev/null +++ b/data/core.telegram.org/constructor/securePlainPhone.html @@ -0,0 +1,150 @@ + + + + + securePlainPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

securePlainPhone

+ +

Phone number to use in telegram passport: it must be verified, first ».

+

+ +
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonestringPhone number
+

Type

+

SecurePlainData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureRequiredType.html b/data/core.telegram.org/constructor/secureRequiredType.html new file mode 100644 index 0000000000..0ec1da6d0e --- /dev/null +++ b/data/core.telegram.org/constructor/secureRequiredType.html @@ -0,0 +1,167 @@ + + + + + secureRequiredType + + + + + + + + + + + + + +
+ +
+
+
+ +

secureRequiredType

+ +

Required type

+

+ +
+
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
native_namesflags.0?trueNative names
selfie_requiredflags.1?trueIs a selfie required
translation_requiredflags.2?trueIs a translation required
typeSecureValueTypeSecure value type
+

Type

+

SecureRequiredType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureSecretSettings.html b/data/core.telegram.org/constructor/secureSecretSettings.html new file mode 100644 index 0000000000..256ecbbcd3 --- /dev/null +++ b/data/core.telegram.org/constructor/secureSecretSettings.html @@ -0,0 +1,157 @@ + + + + + secureSecretSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

secureSecretSettings

+ +

Secure settings

+

+ +
+
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
secure_algoSecurePasswordKdfAlgoSecure KDF algo
secure_secretbytesSecure secret
secure_secret_idlongSecret ID
+

Type

+

SecureSecretSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValue.html b/data/core.telegram.org/constructor/secureValue.html new file mode 100644 index 0000000000..9f4304ca11 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValue.html @@ -0,0 +1,194 @@ + + + + + secureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValue

+ +

Secure value

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
+

Type

+

SecureValue

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorData.html b/data/core.telegram.org/constructor/secureValueErrorData.html new file mode 100644 index 0000000000..841de58f46 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorData.html @@ -0,0 +1,175 @@ + + + + + secureValueErrorData + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorData

+ +

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

+

+ +
+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeThe section of the user's Telegram Passport which has the error, one of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeAddress
data_hashbytesData hash
fieldstringName of the data field which has the error
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePersonalDetails

+

Personal details

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+

secureValueTypeAddress

+

Address

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html new file mode 100644 index 0000000000..505f9f2db6 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html @@ -0,0 +1,178 @@ + + + + + secureValueErrorTranslationFiles + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorTranslationFiles

+ +

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation changes.

+

+ +
+
secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>Hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePersonalDetails

+

Personal details

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html b/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html new file mode 100644 index 0000000000..36058bd81f --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html @@ -0,0 +1,134 @@ + + + + + secureValueTypeInternalPassport + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeInternalPassport

+ +

Internal passport

+

+ +
+
secureValueTypeInternalPassport#99a48f23 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypePassport.html b/data/core.telegram.org/constructor/secureValueTypePassport.html new file mode 100644 index 0000000000..17fa521cab --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypePassport.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePassport + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePassport

+ +

Passport

+

+ +
+
secureValueTypePassport#3dac6a00 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypePhone.html b/data/core.telegram.org/constructor/secureValueTypePhone.html new file mode 100644 index 0000000000..4c31fad60b --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypePhone.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePhone + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePhone

+ +

Phone

+

+ +
+
secureValueTypePhone#b320aadb = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html b/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html new file mode 100644 index 0000000000..2e375b1061 --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeRentalAgreement + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeRentalAgreement

+ +

Rental agreement

+

+ +
+
secureValueTypeRentalAgreement#8b883488 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html new file mode 100644 index 0000000000..7312f9e65f --- /dev/null +++ b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeTemporaryRegistration + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeTemporaryRegistration

+ +

Temporary registration

+

+ +
+
secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageChooseContactAction.html b/data/core.telegram.org/constructor/sendMessageChooseContactAction.html new file mode 100644 index 0000000000..43986989ce --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageChooseContactAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageChooseContactAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageChooseContactAction

+ +

User is selecting a contact to share.

+

+ +
+
sendMessageChooseContactAction#628cbc6f = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html b/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html new file mode 100644 index 0000000000..68b47b4573 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageRecordRoundAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageRecordRoundAction

+ +

User is recording a round video to share

+

+ +
+
sendMessageRecordRoundAction#88f27fbc = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html b/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html new file mode 100644 index 0000000000..a27269a0f4 --- /dev/null +++ b/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadVideoAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadVideoAction

+ +

User is uploading a video.

+

+ +
+
sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stats.broadcastStats b/data/core.telegram.org/constructor/stats.broadcastStats new file mode 100644 index 0000000000..39abf285e6 --- /dev/null +++ b/data/core.telegram.org/constructor/stats.broadcastStats @@ -0,0 +1,220 @@ + + + + + stats.broadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.broadcastStats

+ +

Channel statistics.

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
+

Type

+

stats.BroadcastStats

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGroupTopAdmin.html b/data/core.telegram.org/constructor/statsGroupTopAdmin.html new file mode 100644 index 0000000000..479ff8cd4c --- /dev/null +++ b/data/core.telegram.org/constructor/statsGroupTopAdmin.html @@ -0,0 +1,165 @@ + + + + + statsGroupTopAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopAdmin

+ +

Information about an active admin in a supergroup

+

+ +
+
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
deletedintNumber of deleted messages for statistics period in consideration
kickedintNumber of kicked users for statistics period in consideration
bannedintNumber of banned users for statistics period in consideration
+

Type

+

StatsGroupTopAdmin

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGroupTopInviter.html b/data/core.telegram.org/constructor/statsGroupTopInviter.html new file mode 100644 index 0000000000..f007061d0e --- /dev/null +++ b/data/core.telegram.org/constructor/statsGroupTopInviter.html @@ -0,0 +1,155 @@ + + + + + statsGroupTopInviter + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopInviter

+ +

Information about an active supergroup inviter

+

+ +
+
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
invitationsintNumber of invitations for statistics period in consideration
+

Type

+

StatsGroupTopInviter

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/statsGroupTopPoster.html b/data/core.telegram.org/constructor/statsGroupTopPoster.html new file mode 100644 index 0000000000..6af90fbd92 --- /dev/null +++ b/data/core.telegram.org/constructor/statsGroupTopPoster.html @@ -0,0 +1,160 @@ + + + + + statsGroupTopPoster + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGroupTopPoster

+ +

Information about an active user in a supergroup

+

+ +
+
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
messagesintNumber of messages for statistics period in consideration
avg_charsintAverage number of characters per message
+

Type

+

StatsGroupTopPoster

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/stickerSet.html b/data/core.telegram.org/constructor/stickerSet.html new file mode 100644 index 0000000000..df7e9e3c08 --- /dev/null +++ b/data/core.telegram.org/constructor/stickerSet.html @@ -0,0 +1,217 @@ + + + + + stickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSet

+ +

Represents a stickerset (stickerpack)

+

+ +
+
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
archivedflags.1?trueWhether this stickerset was archived (due to too many saved stickers in the current account)
officialflags.2?trueIs this stickerset official
masksflags.3?trueIs this a mask stickerset
animatedflags.5?trueIs this an animated stickerpack
installed_dateflags.0?intWhen was this stickerset installed
idlongID of the stickerset
access_hashlongAccess hash of stickerset
titlestringTitle of stickerset
short_namestringShort name of stickerset to use in tg://addstickers?set=short_name
thumbsflags.4?Vector<PhotoSize>Stickerset thumbnail
thumb_dc_idflags.4?intDC ID of thumbnail
thumb_versionflags.4?intThumbnail version
countintNumber of stickers in pack
hashintHash
+

Type

+

StickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.filePartial b/data/core.telegram.org/constructor/storage.filePartial new file mode 100644 index 0000000000..871ba727db --- /dev/null +++ b/data/core.telegram.org/constructor/storage.filePartial @@ -0,0 +1,132 @@ + + + + + storage.filePartial + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePartial

+ +

Part of a bigger file.

+

+ +
+
storage.filePartial#40bc6f52 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.filePng b/data/core.telegram.org/constructor/storage.filePng new file mode 100644 index 0000000000..0dc8cecafb --- /dev/null +++ b/data/core.telegram.org/constructor/storage.filePng @@ -0,0 +1,132 @@ + + + + + storage.filePng + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.filePng

+ +

PNG image. MIME type: image/png.

+

+ +
+
storage.filePng#a4f63c0 = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/storage.fileWebp b/data/core.telegram.org/constructor/storage.fileWebp new file mode 100644 index 0000000000..faca63bb5c --- /dev/null +++ b/data/core.telegram.org/constructor/storage.fileWebp @@ -0,0 +1,132 @@ + + + + + storage.fileWebp + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.fileWebp

+ +

WEBP image. MIME type: image/webp.

+

+ +
+
storage.fileWebp#1081464c = storage.FileType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

storage.FileType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textAnchor.html b/data/core.telegram.org/constructor/textAnchor.html new file mode 100644 index 0000000000..08b2472a50 --- /dev/null +++ b/data/core.telegram.org/constructor/textAnchor.html @@ -0,0 +1,152 @@ + + + + + textAnchor + + + + + + + + + + + + + +
+ +
+
+
+ +

textAnchor

+ +

Text linking to another section of the page

+

+ +
+
textAnchor#35553762 text:RichText name:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
namestringSection name
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textMarked.html b/data/core.telegram.org/constructor/textMarked.html new file mode 100644 index 0000000000..ffd36bf700 --- /dev/null +++ b/data/core.telegram.org/constructor/textMarked.html @@ -0,0 +1,147 @@ + + + + + textMarked + + + + + + + + + + + + + +
+ +
+
+
+ +

textMarked

+ +

Highlighted text

+

+ +
+
textMarked#34b8621 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textPlain.html b/data/core.telegram.org/constructor/textPlain.html new file mode 100644 index 0000000000..de391188b4 --- /dev/null +++ b/data/core.telegram.org/constructor/textPlain.html @@ -0,0 +1,147 @@ + + + + + textPlain + + + + + + + + + + + + + +
+ +
+
+
+ +

textPlain

+ +

Plain text

+

+ +
+
textPlain#744694e0 text:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textstringText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/textSuperscript.html b/data/core.telegram.org/constructor/textSuperscript.html new file mode 100644 index 0000000000..2efa9771a5 --- /dev/null +++ b/data/core.telegram.org/constructor/textSuperscript.html @@ -0,0 +1,147 @@ + + + + + textSuperscript + + + + + + + + + + + + + +
+ +
+
+
+ +

textSuperscript

+ +

Superscript text

+

+ +
+
textSuperscript#c7fb5e01 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html new file mode 100644 index 0000000000..426095f2a6 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryCorrespondents + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryCorrespondents

+ +

Users we've chatted most frequently with

+

+ +
+
topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html new file mode 100644 index 0000000000..fcb286ba72 --- /dev/null +++ b/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryForwardUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryForwardUsers

+ +

Users to which the users often forwards messages to

+

+ +
+
topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/true.html b/data/core.telegram.org/constructor/true.html new file mode 100644 index 0000000000..a609bce6e3 --- /dev/null +++ b/data/core.telegram.org/constructor/true.html @@ -0,0 +1,134 @@ + + + + + true + + + + + + + + + + + + + +
+ +
+
+
+ +

true

+ +

See predefined identifiers.

+

+ +
+
true#3fedd339 = True;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

True

+

Related pages

+

TL-formal

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotCallbackQuery.html b/data/core.telegram.org/constructor/updateBotCallbackQuery.html new file mode 100644 index 0000000000..5be1adf264 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotCallbackQuery.html @@ -0,0 +1,182 @@ + + + + + updateBotCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotCallbackQuery

+ +

A callback button was pressed, and the button data was sent to the bot that created the button

+

+ +
+
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
peerPeerChat where the inline keyboard was sent
msg_idintMessage ID
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesCallback data
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotInlineQuery.html b/data/core.telegram.org/constructor/updateBotInlineQuery.html new file mode 100644 index 0000000000..f71006b5a3 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotInlineQuery.html @@ -0,0 +1,177 @@ + + + + + updateBotInlineQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotInlineQuery

+ +

An incoming inline query

+

+ +
+
updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongUser that sent the query
querystringText of query
geoflags.0?GeoPointAttached geolocation
peer_typeflags.1?InlineQueryPeerTypeType of the chat from which the inline query was sent.
offsetstringOffset to navigate through results
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotInlineSend.html b/data/core.telegram.org/constructor/updateBotInlineSend.html new file mode 100644 index 0000000000..ec465d9961 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotInlineSend.html @@ -0,0 +1,172 @@ + + + + + updateBotInlineSend + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotInlineSend

+ +

The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.

+

+ +
+
updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongThe user that chose the result
querystringThe query that was used to obtain the result
geoflags.0?GeoPointOptional. Sender location, only for bots that require user location
idstringThe unique identifier for the result that was chosen
msg_idflags.1?InputBotInlineMessageIDIdentifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html b/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html new file mode 100644 index 0000000000..b8ffc0c733 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotPrecheckoutQuery.html @@ -0,0 +1,184 @@ + + + + + updateBotPrecheckoutQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotPrecheckoutQuery

+ +

This object contains information about an incoming pre-checkout query.

+

+ +
+
updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
+

Type

+

Update

+

Related pages

+

Bot Payments API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateBotShippingQuery.html b/data/core.telegram.org/constructor/updateBotShippingQuery.html new file mode 100644 index 0000000000..7e0efdf187 --- /dev/null +++ b/data/core.telegram.org/constructor/updateBotShippingQuery.html @@ -0,0 +1,162 @@ + + + + + updateBotShippingQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotShippingQuery

+ +

This object contains information about an incoming shipping query.

+

+ +
+
updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
shipping_addressPostAddressUser specified shipping address
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelAvailableMessages.html b/data/core.telegram.org/constructor/updateChannelAvailableMessages.html new file mode 100644 index 0000000000..6707dabf0d --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelAvailableMessages.html @@ -0,0 +1,155 @@ + + + + + updateChannelAvailableMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelAvailableMessages

+ +

The history of a channel/supergroup was hidden.

+

+ +
+
updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
available_min_idintIdentifier of a maximum unavailable message in a channel due to hidden history.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelMessageViews.html b/data/core.telegram.org/constructor/updateChannelMessageViews.html new file mode 100644 index 0000000000..bd31194007 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelMessageViews.html @@ -0,0 +1,157 @@ + + + + + updateChannelMessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelMessageViews

+ +

The view counter of a message in a channel has changed

+

+ +
+
updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
idintID of the message
viewsintNew view counter
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChannelUserTyping.html b/data/core.telegram.org/constructor/updateChannelUserTyping.html new file mode 100644 index 0000000000..822be5c625 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChannelUserTyping.html @@ -0,0 +1,172 @@ + + + + + updateChannelUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelUserTyping

+ +

A user is typing in a supergroup, channel or message thread

+

+ +
+
updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
top_msg_idflags.0?intThread ID
from_idPeerThe peer that is typing
actionSendMessageActionWhether the user is typing, sending a media or doing something else
+

Type

+

Update

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdmin.html b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html new file mode 100644 index 0000000000..62c10ebbc4 --- /dev/null +++ b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html @@ -0,0 +1,165 @@ + + + + + updateChatParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipantAdmin

+ +

Admin permissions of a user in a legacy group were changed

+

+ +
+
updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
user_idlongID of the (de)admined user
is_adminBoolWhether the user was rendered admin
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogFilter.html b/data/core.telegram.org/constructor/updateDialogFilter.html new file mode 100644 index 0000000000..eece7615f2 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogFilter.html @@ -0,0 +1,160 @@ + + + + + updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilter

+ +

A new folder was added

+

+ +
+
updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateDialogPinned.html b/data/core.telegram.org/constructor/updateDialogPinned.html new file mode 100644 index 0000000000..9953aab326 --- /dev/null +++ b/data/core.telegram.org/constructor/updateDialogPinned.html @@ -0,0 +1,165 @@ + + + + + updateDialogPinned + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogPinned

+ +

A dialog was pinned/unpinned

+

+ +
+
updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the dialog was pinned
folder_idflags.1?intPeer folder ID, for more info click here
peerDialogPeerThe dialog
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateGroupCallConnection.html b/data/core.telegram.org/constructor/updateGroupCallConnection.html new file mode 100644 index 0000000000..7682a21b61 --- /dev/null +++ b/data/core.telegram.org/constructor/updateGroupCallConnection.html @@ -0,0 +1,157 @@ + + + + + updateGroupCallConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

updateGroupCallConnection

+ +

New WebRTC parameters

+

+ +
+
updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
presentationflags.0?trueAre these parameters related to the screen capture session currently in progress?
paramsDataJSONWebRTC parameters
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html b/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html new file mode 100644 index 0000000000..b2e486a809 --- /dev/null +++ b/data/core.telegram.org/constructor/updateInlineBotCallbackQuery.html @@ -0,0 +1,177 @@ + + + + + updateInlineBotCallbackQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateInlineBotCallbackQuery

+ +

This notification is received by bots when a button is pressed

+

+ +
+
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
msg_idInputBotInlineMessageIDID of the inline message with the button
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesData associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateLangPack.html b/data/core.telegram.org/constructor/updateLangPack.html new file mode 100644 index 0000000000..cd5b069397 --- /dev/null +++ b/data/core.telegram.org/constructor/updateLangPack.html @@ -0,0 +1,147 @@ + + + + + updateLangPack + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLangPack

+ +

Language pack updated

+

+ +
+
updateLangPack#56022f4d difference:LangPackDifference = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
differenceLangPackDifferenceChanged strings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateNewMessage.html b/data/core.telegram.org/constructor/updateNewMessage.html new file mode 100644 index 0000000000..7521944f26 --- /dev/null +++ b/data/core.telegram.org/constructor/updateNewMessage.html @@ -0,0 +1,157 @@ + + + + + updateNewMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewMessage

+ +

New message in a private chat or in a legacy group.

+

+ +
+
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageMessage
ptsintNew quantity of actions in a message box
pts_countintNumber of generated events
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePeerHistoryTTL.html b/data/core.telegram.org/constructor/updatePeerHistoryTTL.html new file mode 100644 index 0000000000..54cb12f894 --- /dev/null +++ b/data/core.telegram.org/constructor/updatePeerHistoryTTL.html @@ -0,0 +1,157 @@ + + + + + updatePeerHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePeerHistoryTTL

+ +

The Time-To-Live for messages sent by the current user in a specific chat has changed

+

+ +
+
updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerPeerThe chat
ttl_periodflags.0?intThe new Time-To-Live
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html new file mode 100644 index 0000000000..55ce7cf3ad --- /dev/null +++ b/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html @@ -0,0 +1,152 @@ + + + + + updatePhoneCallSignalingData + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePhoneCallSignalingData

+ +

Incoming phone call signaling payload

+

+ +
+
updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_call_idlongPhone call ID
databytesSignaling payload
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html new file mode 100644 index 0000000000..c0c57517cb --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html @@ -0,0 +1,162 @@ + + + + + updateReadChannelDiscussionOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelDiscussionOutbox

+ +

Outgoing comments in a discussion thread were marked as read

+

+ +
+
updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongSupergroup ID
top_msg_idintID of the group message that started the thread
read_max_idintMessage ID of latest read outgoing message for this thread
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadChannelOutbox.html b/data/core.telegram.org/constructor/updateReadChannelOutbox.html new file mode 100644 index 0000000000..82976bfc8b --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadChannelOutbox.html @@ -0,0 +1,155 @@ + + + + + updateReadChannelOutbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadChannelOutbox

+ +

Outgoing messages in a channel/supergroup were read

+

+ +
+
updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
max_idintPosition up to which all outgoing messages are read.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateReadFeaturedStickers.html b/data/core.telegram.org/constructor/updateReadFeaturedStickers.html new file mode 100644 index 0000000000..aeb162deee --- /dev/null +++ b/data/core.telegram.org/constructor/updateReadFeaturedStickers.html @@ -0,0 +1,132 @@ + + + + + updateReadFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadFeaturedStickers

+ +

Some featured stickers were marked as read

+

+ +
+
updateReadFeaturedStickers#571d2742 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateShortSentMessage.html b/data/core.telegram.org/constructor/updateShortSentMessage.html new file mode 100644 index 0000000000..a3a338533f --- /dev/null +++ b/data/core.telegram.org/constructor/updateShortSentMessage.html @@ -0,0 +1,192 @@ + + + + + updateShortSentMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortSentMessage

+ +

Shortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).

+

+ +
+
updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
idintID of the sent message
ptsintPTS
pts_countintPTS count
dateintdate
mediaflags.9?MessageMediaAttached media
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateTheme.html b/data/core.telegram.org/constructor/updateTheme.html new file mode 100644 index 0000000000..c987d45e7d --- /dev/null +++ b/data/core.telegram.org/constructor/updateTheme.html @@ -0,0 +1,147 @@ + + + + + updateTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

updateTheme

+ +

A cloud theme was updated

+

+ +
+
updateTheme#8216fba3 theme:Theme = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
themeThemeTheme
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserBlocked.html b/data/core.telegram.org/constructor/updateUserBlocked.html new file mode 100644 index 0000000000..0890b946fd --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserBlocked.html @@ -0,0 +1,159 @@ + + + + + updateUserBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserBlocked

+ +

User was added to the blacklist (method contacts.block) or removed from the blacklist (method contacts.unblock).

+

+ +
+
Constructor schema is available as of layer 119. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idintUser id
blockedBool(boolTrue) if the the user is blocked
+

Type

+

Update

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

contacts.block

+

Adds the user to the blacklist.

+

contacts.unblock

+

Deletes the user from the blacklist.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updateUserName.html b/data/core.telegram.org/constructor/updateUserName.html new file mode 100644 index 0000000000..067c54060a --- /dev/null +++ b/data/core.telegram.org/constructor/updateUserName.html @@ -0,0 +1,167 @@ + + + + + updateUserName + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserName

+ +

Changes the user's first name, last name and username.

+

+ +
+
updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
first_namestringNew first name. Corresponds to the new value of real_first_name field of the userFull constructor.
last_namestringNew last name. Corresponds to the new value of real_last_name field of the userFull constructor.
usernamestringNew username.
Parameter added in Layer 18.
+

Type

+

Update

+

Related pages

+

userFull

+

Extended user info

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.differenceSlice b/data/core.telegram.org/constructor/updates.differenceSlice new file mode 100644 index 0000000000..836ba3aa41 --- /dev/null +++ b/data/core.telegram.org/constructor/updates.differenceSlice @@ -0,0 +1,175 @@ + + + + + updates.differenceSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceSlice

+ +

Incomplete list of occurred events.

+

+ +
+
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/updates.state b/data/core.telegram.org/constructor/updates.state new file mode 100644 index 0000000000..0cb5396b9d --- /dev/null +++ b/data/core.telegram.org/constructor/updates.state @@ -0,0 +1,172 @@ + + + + + updates.state + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.state

+ +

Updates state.

+

+ +
+
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintNumber of events occured in a text box
qtsintPosition in a sequence of updates in secret chats. For further detailes refer to article secret chats
Parameter was added in eigth layer.
dateintDate of condition
seqintNumber of sent updates
unread_countintNumber of unread messages
+

Type

+

updates.State

+

Related pages

+

End-to-End Encryption, Secret Chats

+

New feature for end-to-end-encrypted messaging.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userProfilePhoto.html b/data/core.telegram.org/constructor/userProfilePhoto.html new file mode 100644 index 0000000000..d74ed77ce8 --- /dev/null +++ b/data/core.telegram.org/constructor/userProfilePhoto.html @@ -0,0 +1,172 @@ + + + + + userProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

userProfilePhoto

+ +

User profile photo.

+

+ +
+
userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether an animated profile picture is available for this user
photo_idlongIdentifier of the respective photo
Parameter added in Layer 2
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC ID where the photo is stored
+

Type

+

UserProfilePhoto

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userProfilePhotoEmpty.html b/data/core.telegram.org/constructor/userProfilePhotoEmpty.html new file mode 100644 index 0000000000..cf1ead2630 --- /dev/null +++ b/data/core.telegram.org/constructor/userProfilePhotoEmpty.html @@ -0,0 +1,132 @@ + + + + + userProfilePhotoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userProfilePhotoEmpty

+ +

Profile photo has not been set, or was hidden.

+

+ +
+
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserProfilePhoto

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusLastMonth.html b/data/core.telegram.org/constructor/userStatusLastMonth.html new file mode 100644 index 0000000000..04c6f0d8d8 --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusLastMonth.html @@ -0,0 +1,132 @@ + + + + + userStatusLastMonth + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusLastMonth

+ +

Online status: last seen last month

+

+ +
+
userStatusLastMonth#77ebc742 = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusOffline.html b/data/core.telegram.org/constructor/userStatusOffline.html new file mode 100644 index 0000000000..ad3d0401f7 --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusOffline.html @@ -0,0 +1,147 @@ + + + + + userStatusOffline + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusOffline

+ +

The user's offline status.

+

+ +
+
userStatusOffline#8c703f was_online:int = UserStatus;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
was_onlineintTime the user was last seen online
+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/userStatusOnline.html b/data/core.telegram.org/constructor/userStatusOnline.html new file mode 100644 index 0000000000..4b7f165d9c --- /dev/null +++ b/data/core.telegram.org/constructor/userStatusOnline.html @@ -0,0 +1,147 @@ + + + + + userStatusOnline + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusOnline

+ +

Online status of the user.

+

+ +
+
userStatusOnline#edb93949 expires:int = UserStatus;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
expiresintTime to expiration of the current online status
+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/vector.html b/data/core.telegram.org/constructor/vector.html new file mode 100644 index 0000000000..4b7754b27b --- /dev/null +++ b/data/core.telegram.org/constructor/vector.html @@ -0,0 +1,134 @@ + + + + + vector + + + + + + + + + + + + + +
+ +
+
+
+ +

vector

+ +

A universal vector constructor.

+

+ +
+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Vector t

+

Params additional

+

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/wallPaperSolid.html b/data/core.telegram.org/constructor/wallPaperSolid.html new file mode 100644 index 0000000000..435ebb5bc5 --- /dev/null +++ b/data/core.telegram.org/constructor/wallPaperSolid.html @@ -0,0 +1,162 @@ + + + + + wallPaperSolid + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperSolid

+ +

One-color background wallpaper (no image).

+

+ +
+
Constructor schema is available as of layer 93. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintIdentifier
titlestringName
bg_colorintBackground color (RGB)
colorintBasic background color (RGB)
+

Type

+

WallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/constructor/webPageAttributeTheme.html b/data/core.telegram.org/constructor/webPageAttributeTheme.html new file mode 100644 index 0000000000..7d464abca6 --- /dev/null +++ b/data/core.telegram.org/constructor/webPageAttributeTheme.html @@ -0,0 +1,157 @@ + + + + + webPageAttributeTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageAttributeTheme

+ +

Page theme

+

+ +
+
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentsflags.0?Vector<Document>Theme files
settingsflags.1?ThemeSettingsTheme settings
+

Type

+

WebPageAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/contest300K.html b/data/core.telegram.org/contest300K.html new file mode 100644 index 0000000000..86ddea9c34 --- /dev/null +++ b/data/core.telegram.org/contest300K.html @@ -0,0 +1,237 @@ + + + + + Telegram Cracking Contest Description + + + + + + + + + + + + + +
+ +
+
+
+
+

Telegram Cracking Contest Description

+ +

« Back to Contest Announcement

+
+

The current round of the contest is over. Go to results »

+
+

In this contest you assume the role of a malicious entity in control of Telegram's servers. Your goal is to extract sensitive data (a secret email and password) from a conversation between two peers — Paul and Nick. They are represented by two virtual users that communicate via Secret Chats in Telegram.

+

Paul and Nick are both using clients that perform all the checks from Telegram Security Guidelines and compare their key visualizations over an independent channel as soon as a new Secret Chat is established. If any of these checks fails, they stop accepting messages in that Secret Chat. You control the entire process by sending commands to the Telegram user @CryptoContest, used as an interface for this contest. This enables contestants to try CPA, KPA, MITM and other kinds of active attacks and data tampering.

+

Protocol

+

The protocol used by Paul and Nick to establish Secret Сhats and exchange messages is identical to the one used for Secret Chats in Telegram. Since we assume that the attacker is already in full control of the Telegram servers, basic MTProto encryption is bypassed altogether. In order to further simplify the task for contestants, we have removed irrelevant parameters, such as user_id and random_id.

+

The following TL scheme is used to establish Secret Chats in this contest:

+
contest.dhConfig#01e00a51 g:int p:64*[int] random:64*[int] = contest.DhConfig;
+contest.requestEncryption#3a73a74c g_a:64*[int] = contest.Message;
+contest.acceptEncryption#068e4342 g_b:64*[int] fingerprint:int = contest.Message;
+contest.encryptedMessage#11a6d4b1 id:long message:string = contest.Message;
+---functions---
+contest.getDhConfig#369ee1a6 = contest.DhConfig;
+

For exchange of encrypted messages (see documentation), the up-to-date layer 17 scheme with sequence numbers is used, but with plain text message support only.

+

Each plaintext message is first created as a layer 17 decryptedMessage, then embedded in a decryptedMessageLayer and encrypted as explained in the Secret Chat documentation. For the purpose of this contest, it is the result of this encryption (ciphertext) that is exchanged between the parties.

+

Notice that sending messages in an actual Telegram Secret Chat involves further embedding of that ciphertext into an API call and an additional layer of MTProto encryption for client-server interaction. This step is omitted here, since we assume the attacker to be in control of the Telegram servers, not just of the communication lines between the clients and Telegram servers.

+

Interface

+

To access the interface, find the Telegram user @CryptoContest using the Global Search by username in any of the Telegram apps. This is a special bot we created for this contest. You can control communication between Paul and Nick by sending particularly formed text messages to this bot and processing automatically generated answers to these messages (you may find the unofficial Linux CLI convenient for mass automated queries).

+

You can create as many parallel Secret Chats between Paul and Nick as you like using the bot — each of them will have a separate session_id. All data is represented in hexadecimal format, with the exception of the session_id.

+

Commands

+

Below, A stands for the creator of the Secret Chat, B stands for the second party, S — the Telegram Server.

+

Each Secret Chat session in this contest is divided in two phases:

+ +
1. Creating a Secret Chat
+

In order to create a new Secret Chat, six messages need to be exchanged:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SourceDestinationMessage
AScontest.getDhConfig
SAcontest.DhConfig
ABcontest.requestEncryption
BScontest.getDhConfig
SBcontest.DhConfig
BAcontest.acceptEncryption
+

To create a Secret Chat in this contest:

+
    +
  • Send the START command to the user @CryptoContest in Telegram. You'll get the getDhConfig query, sent by A to the Server, and the answer that the server would normally send to A. You shall also receive the new session_id as the first 32-bit integer. All further messages related to this particular session (Secret Chat instance) must be prefixed with this session_id in decimal form.
  • +
  • After that, use the PASS command to pass the server's answer to A or ANSWER bytes to send a different answer instead. Bytes is represented by a string of an even number of hexadecimal digits. You'll receive the requestEncryption query as the result.
  • +
  • After that, use the PASS command to pass this query to B or ANSWER bytes to arbitrarily change it. You‘ll receive B’s getDhConfig to the server as the result.
  • +
  • As before, you can use either PASS or ANSWER bytes. You'll receive acceptEncryption as the result.
  • +
  • As before, you can use either PASS or ANSWER bytes. You'll receive “Ok” as the result.
  • +
+

You will receive an error text as the result after any of these steps in case the participating clients perceive that something went wrong. This can happen if a security check is failed, or in the case that the first 128 bits of the SHA-1 of the newly created encryption key don‘t match on both parties’ clients when this stage is completed (this corresponds to Paul and Nick comparing the key visualizations for the Secret Chat in their Telegram apps).

+

If you obtain such an error, the session is failed and can no longer be used. You'll have to start new session. Note that the time to complete this phase is limited. Each step should not take longer than one hour, otherwise the Secret Chat will get cancelled.

+

Example:

+
START
+15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b202d33053c2340fd84dd024e8012277e9c6442ad7cd09fe85955c13196e2d32861ad0d8f8139ce5870f1c3563fbff77428632897352abd91cd0a6497a0f64a33d87cd8b53470cf1bc6a052bba7d0121623e9611c0de83ffeb63b7d15831a70187093373cb20df5613bdfab12a54bbc6fff94598d95a8dcdb1374631b021e77c350261bca9ffc16c59b19d3041bee011a20b06fc9806d633b6b9cdd79cbb8b02fe8ef9dde29b6d31d80b030c69d67d6fc4a7edb33ffab532d085796cf3e7635fd42ee72ea24840082186fd40c3c45cf0acef886533d4de7468f88942a662d302928470aa8704529180a6aec2f877398efb91893cc9b549e5123d7269adfe7b6ee
+15 PASS
+15 4ca7733a1a7823b420111d8e86e3fe9a7cff9fc611ce339d6999fc3053973ef6c8276af841b53547fdebdcb057cbad16aff6178be3fb8747889937dec082c984227c974a19232b85ad85ef457521fcf17d5f697a17b7e62952306f0ed086deb1ebcff0c8a32787789fe7afaa4035c2d0e07c10db46c0df6930a1729d3607fb035154e90c02036318862c5a9537e87a55bc656e3fc53db08f41a07f834e4917ebaaace1214409ffb44c5a806a9cb4def209bfb8ab2e59f1cb6257e422f37dfab288170bdc5666e6a63d1b0447a7b935ad3bdac8d53f64278d433b45925c84dc60214473363d57a30e31324d9b3cc42fb56d375aac2d9d1af16331ad3a92b43a9d64e47813
+15 PASS
+15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8adc5a64
+15 ANSWER 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8ad00000
+15 42438e06bbb424bba5fd95122ec2f206c9b502f1f6d4e4fdbf74ed2c946ad60abaefd6fbd6a08e3ef418709d15bc557ef5e486a51d1e304f6c1e943faad948fde4e6273c0cad0df07068ad028fb01dc0fd7221aeed6ed5dc510dbe4824939036b0f3a45e740b40cef86a32f0b73b20234efc41d573f3e14efc08b3f65e9f7be52d5b930de52d41c7aadc4e0e85dfcf3bb1dd2e9cdf94fc236082879aea27207415cb846a5d5969e619040416a7f0f708f56a5b340a8fd0be1a26bfdc3de365a950532d363b427d6d905af7534af574ae8afd3f47658de5da3fa02dd818a31523122ff53dd31ffd7aa22e53cbf2da7772a1589e9a242f28f9cb1130f54553fcb355b3398fc877b80b3ef2cc3d
+15 PASS
+15 Ok
+
2. Sending Text Messages
+

Once the Secret Chat has been established, you can use the following queries to make Paul and Nick exchange text messages inside the Secret Chat:

+
    +
  • ASK [A|B] — asks A or B to send a random plaintext message to the other party. It is guaranteed that at least one of the first ten generated messages will contain the secret email and password that are the goal of this contest. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks. The result to this query is the ciphertext corresponding to the randomly generated plaintext.
  • +
  • TXT [A|B] bytes — asks A or B to encrypt bytes as the (plaintext) contents of a text message and send it to the other party. Note that bytes can be any byte sequence, not necessarily a valid UTF-8 sequence. The result to this query is the ciphertext corresponding to the given plaintext.
  • +
  • MSG [A|B] bytes — send a specified (ciphertext) message (for example, obtained as an answer to an ASK or TXT query) to A or B. You will receive ‘Ok’ if this message was decrypted successfully and accepted by the client, or ‘Fail’ otherwise.
  • +
+

Example:

+
15 ASK A
+15 b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
+15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b0
+15 Fail
+15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
+15 Ok
+15 TXT B abac
+15 b1d4a61101771d42f62323e6fe680000c877b80b3ef2cc3df751e68b935b083a6f5c15ba8d95b94388fc34453a1e7b9b20222402b7698be5dd8a6ff69a5141b01ca2488b0dada8f2b0e47980218f48912168ddd2cebd3b61b1edf2f557c7ec44768595ce1cb42a01f7c14dd4e6e6e7601cb17ab0b6d5a274
+
+

Objectives

+

We are offering a $300,000 reward to the first person to break Telegram's encryption protocol in this contest.

+

Your goal is to extract a secret email address from one of the random messages that are exchanged between Nick and Paul when you use the ASK command. It is guaranteed that at least one of the first ten generated messages within a session will contain the secret address. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks.

+

Once you have the address, you will need to send an email to it. That email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

+

Decrypting messages

+

To prove that the competition was fair, we will add a command that returns the keys used for a particular session by its session_id at the end of the contest. This will be done as soon as a winner is announced, or on February 4, 2015 in case no winner is announced to that date.

+

Bonus objective

+

We are also offering an independent $100,000 reward to the first person to make the bot accept a ciphertext message (i.e. the first person to send a message using MSG [A|B] bytes and receive the result ‘OK’), provided that that ciphertext deciphers to a plaintext that was never encrypted by the bot itself within this session.

+

Should you succeed at this, kindly send an email to security@telegram.org and include the following:
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $100,000 prize.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/getProxyConfig.html b/data/core.telegram.org/getProxyConfig.html new file mode 100644 index 0000000000..7238f2dd28 --- /dev/null +++ b/data/core.telegram.org/getProxyConfig.html @@ -0,0 +1,24 @@ +# force_probability 10 10 +default 2; +proxy_for 1 149.154.X.X:8888; +proxy_for -1 149.154.X.X:8888; +proxy_for 2 149.154.X.X:8888; +proxy_for -2 149.154.X.X:8888; +proxy_for 3 149.154.X.X:8888; +proxy_for -3 149.154.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for -4 149.154.X.X:8888; +proxy_for -4 149.154.X.X:8888; +proxy_for 5 91.108.X.X:8888; +proxy_for 5 91.108.X.X:8888; +proxy_for -5 91.108.X.X:8888; +proxy_for -5 91.108.X.X:8888; diff --git a/data/core.telegram.org/import-stickers.html b/data/core.telegram.org/import-stickers.html new file mode 100644 index 0000000000..c784348887 --- /dev/null +++ b/data/core.telegram.org/import-stickers.html @@ -0,0 +1,159 @@ + + + + + Importing Stickers to Telegram + + + + + + + + + + + + + +
+ +
+
+
+
+

Importing Stickers to Telegram

+ +

The easiest way to create stickers on Telegram is to simply upload them using the @stickers bot. This bot can help you upload new stickers, create sticker packs and get usage stats for your stickers and packs.

+

Telegram also offers a platform for developers of apps that help users make their own stickers. For example, apps that allow people to upload pictures of themselves and turn them into stickers.

+

Who is this for?

+

USE this:

+
    +
  • To help people make their own unique custom stickers.
  • +
  • To help people migrate their unique custom stickers they created from another platform.
  • +
+

DON'T use this:

+ +

In short, if a set of stickers is already available on Telegram – there's no need to import it!

+

Sticker Importing Apps

+

As of version 7.8, Telegram apps support a simple API for importing stickers.

+
+ +
+ +
+

WARNING: Each time a user imports stickers, a new sticker pack is created on Telegram. Do not use the importing feature to share stickers you made with other users. If you want to share your stickers, simply upload them using @stickers and share the link of your pack. For example, here's a link to install some Duck Stickers.

+
+

Importing SDKs

+

We have created libraries and sample apps for iOS and Android which you can use to implement importing stickers to Telegram from your app.

+

Sticker Formats

+

Telegram apps support two sticker types. Regardless of the type, each sticker must be associated with at least one emoji that expresses the emotion corresponding to the sticker.

+

Animated Stickers

+

Must be in TGS format, created using the Bodymovin-TG plugin for Adobe After Effects.

+
+

Note: Animated .WEBP is NOT currently supported, only static .WEBP is supported for static stickers. Animated stickers must be in .TGS format. You can also import .WEBM video stickers.

+
+

Max. size: 64 KB
Dimensions: 512x512 px
FPS: 30-60 FPS
Max. duration: 3 seconds

+
+

For full technical details on Telegram animated stickers, see this page.

+
+

Video Stickers

+

Must be in WEBM format with VP9 and alpha channel encoding (transparency is a temporary requirement).

+

Max. size: 256 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.
FPS: 30
Max. duration: 3 seconds

+

Static Stickers

+

Must be in PNG or WEBP format with a transparent layer. All static stickers should use white stroke and shadow, exactly like in this example: StickerExample.psd

+

Max. size: 512 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.acceptAuthorization b/data/core.telegram.org/method/account.acceptAuthorization new file mode 100644 index 0000000000..41d171d863 --- /dev/null +++ b/data/core.telegram.org/method/account.acceptAuthorization @@ -0,0 +1,170 @@ + + + + + account.acceptAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

account.acceptAuthorization

+ +

Sends a Telegram Passport authorization form, effectively sharing data with the service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idlongBot ID
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
value_hashesVector<SecureValueHash>Types of values sent and their hashes
credentialsSecureCredentialsEncryptedEncrypted values
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.confirmPasswordEmail b/data/core.telegram.org/method/account.confirmPasswordEmail new file mode 100644 index 0000000000..e4402828e6 --- /dev/null +++ b/data/core.telegram.org/method/account.confirmPasswordEmail @@ -0,0 +1,175 @@ + + + + + account.confirmPasswordEmail + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPasswordEmail

+ +

Verify an email to use as 2FA recovery method.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
codestringThe phone code that was received after setting a recovery email
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_INVALIDCode invalid.
400EMAIL_HASH_EXPIREDEmail hash expired.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.confirmPhone b/data/core.telegram.org/method/account.confirmPhone new file mode 100644 index 0000000000..a0c2ab7eec --- /dev/null +++ b/data/core.telegram.org/method/account.confirmPhone @@ -0,0 +1,180 @@ + + + + + account.confirmPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPhone

+ +

Confirm a phone number to cancel account deletion, for more info click here »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_code_hashstringPhone code hash, for more info click here »
phone_codestringSMS code, for more info click here »
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_HASH_INVALIDCode hash invalid.
400PHONE_CODE_EMPTYphone_code is missing.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.createTheme b/data/core.telegram.org/method/account.createTheme new file mode 100644 index 0000000000..80dbc9c1da --- /dev/null +++ b/data/core.telegram.org/method/account.createTheme @@ -0,0 +1,186 @@ + + + + + account.createTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.createTheme

+ +

Create a theme

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+---functions---
+account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
slugstringUnique theme ID
titlestringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_MIME_INVALIDThe theme's MIME type is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.finishTakeoutSession b/data/core.telegram.org/method/account.finishTakeoutSession new file mode 100644 index 0000000000..cfed1c0658 --- /dev/null +++ b/data/core.telegram.org/method/account.finishTakeoutSession @@ -0,0 +1,172 @@ + + + + + account.finishTakeoutSession + + + + + + + + + + + + + +
+ +
+
+
+ +

account.finishTakeoutSession

+ +

Finish account takeout session

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.0?trueData exported successfully
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getAuthorizationForm b/data/core.telegram.org/method/account.getAuthorizationForm new file mode 100644 index 0000000000..70e50136ea --- /dev/null +++ b/data/core.telegram.org/method/account.getAuthorizationForm @@ -0,0 +1,176 @@ + + + + + account.getAuthorizationForm + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getAuthorizationForm

+ +

Returns a Telegram Passport authorization form for sharing data with a service

+

+ +
+
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+---functions---
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
bot_idlongUser identifier of the service's bot
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
+

Result

+

account.AuthorizationForm

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PUBLIC_KEY_REQUIREDA public key is required.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.getContactSignUpNotification b/data/core.telegram.org/method/account.getContactSignUpNotification new file mode 100644 index 0000000000..b97b7bfed7 --- /dev/null +++ b/data/core.telegram.org/method/account.getContactSignUpNotification @@ -0,0 +1,135 @@ + + + + + account.getContactSignUpNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getContactSignUpNotification

+ +

Whether the user will receive notifications when contacts sign up

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.getContactSignUpNotification#9f07c728 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.installWallPaper b/data/core.telegram.org/method/account.installWallPaper new file mode 100644 index 0000000000..74f3f1f1e0 --- /dev/null +++ b/data/core.telegram.org/method/account.installWallPaper @@ -0,0 +1,172 @@ + + + + + account.installWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.installWallPaper

+ +

Install wallpaper

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperWallpaper to install
settingsWallPaperSettingsWallpaper settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.reportPeer b/data/core.telegram.org/method/account.reportPeer new file mode 100644 index 0000000000..054b3723e4 --- /dev/null +++ b/data/core.telegram.org/method/account.reportPeer @@ -0,0 +1,182 @@ + + + + + account.reportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportPeer

+ +

Report a peer for violation of telegram's Terms of Service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer to report
reasonReportReasonThe reason why this peer is being reported
messagestringComment for report moderation
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.resetWebAuthorizations b/data/core.telegram.org/method/account.resetWebAuthorizations new file mode 100644 index 0000000000..149c5e8d00 --- /dev/null +++ b/data/core.telegram.org/method/account.resetWebAuthorizations @@ -0,0 +1,137 @@ + + + + + account.resetWebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetWebAuthorizations

+ +

Reset all active web telegram login sessions

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.resetWebAuthorizations#682d2594 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Telegram Login Widget

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.saveTheme b/data/core.telegram.org/method/account.saveTheme new file mode 100644 index 0000000000..9dcbb739b5 --- /dev/null +++ b/data/core.telegram.org/method/account.saveTheme @@ -0,0 +1,155 @@ + + + + + account.saveTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveTheme

+ +

Save a theme

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
themeInputThemeTheme to save
unsaveBoolUnsave
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendChangePhoneCode b/data/core.telegram.org/method/account.sendChangePhoneCode new file mode 100644 index 0000000000..1985b88e2b --- /dev/null +++ b/data/core.telegram.org/method/account.sendChangePhoneCode @@ -0,0 +1,186 @@ + + + + + account.sendChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendChangePhoneCode

+ +

Verify a new phone number to associate to the current account

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringNew phone number
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_CHANGE_PHONE_FORBIDDENYou can't change phone number right after logging in, please wait at least 24 hours.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendConfirmPhoneCode b/data/core.telegram.org/method/account.sendConfirmPhoneCode new file mode 100644 index 0000000000..5f0a68690e --- /dev/null +++ b/data/core.telegram.org/method/account.sendConfirmPhoneCode @@ -0,0 +1,174 @@ + + + + + account.sendConfirmPhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendConfirmPhoneCode

+ +

Send confirmation code to cancel account deletion, for more info click here »

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashstringThe hash from the service notification, for more info click here »
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.sendVerifyPhoneCode b/data/core.telegram.org/method/account.sendVerifyPhoneCode new file mode 100644 index 0000000000..aba57481a3 --- /dev/null +++ b/data/core.telegram.org/method/account.sendVerifyPhoneCode @@ -0,0 +1,173 @@ + + + + + account.sendVerifyPhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

account.sendVerifyPhoneCode

+ +

Send the verification phone code for telegram passport.

+

+ +
+
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+---functions---
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringThe phone number to verify
settingsCodeSettingsPhone code settings
+

Result

+

auth.SentCode

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setContactSignUpNotification b/data/core.telegram.org/method/account.setContactSignUpNotification new file mode 100644 index 0000000000..25408513ca --- /dev/null +++ b/data/core.telegram.org/method/account.setContactSignUpNotification @@ -0,0 +1,150 @@ + + + + + account.setContactSignUpNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setContactSignUpNotification

+ +

Toggle contact sign up notifications

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
silentBoolWhether to disable contact sign up notifications
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setContentSettings b/data/core.telegram.org/method/account.setContentSettings new file mode 100644 index 0000000000..f043bdcdaf --- /dev/null +++ b/data/core.telegram.org/method/account.setContentSettings @@ -0,0 +1,172 @@ + + + + + account.setContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setContentSettings

+ +

Set sensitive content settings (for viewing or hiding NSFW content)

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueEnable NSFW content
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403SENSITIVE_CHANGE_FORBIDDENYou can't change your sensitive content settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.setPrivacy b/data/core.telegram.org/method/account.setPrivacy new file mode 100644 index 0000000000..951971b764 --- /dev/null +++ b/data/core.telegram.org/method/account.setPrivacy @@ -0,0 +1,181 @@ + + + + + account.setPrivacy + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setPrivacy

+ +

Change privacy settings of current account

+

+ +
+
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+---functions---
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
keyInputPrivacyKeyPeers to which the privacy rules apply
rulesVector<InputPrivacyRule>New privacy rules
+

Result

+

account.PrivacyRules

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
400PRIVACY_TOO_LONGToo many privacy rules were specified, the current limit is 1000.
400PRIVACY_VALUE_INVALIDThe specified privacy rule combination is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateDeviceLocked b/data/core.telegram.org/method/account.updateDeviceLocked new file mode 100644 index 0000000000..1e2cb58dbf --- /dev/null +++ b/data/core.telegram.org/method/account.updateDeviceLocked @@ -0,0 +1,153 @@ + + + + + account.updateDeviceLocked + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateDeviceLocked

+ +

When client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateDeviceLocked#38df3532 period:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
periodintInactivity period after which to start hiding message texts in PUSH notifications.
+

Result

+

Bool

+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updatePasswordSettings b/data/core.telegram.org/method/account.updatePasswordSettings new file mode 100644 index 0000000000..f01f1f0f37 --- /dev/null +++ b/data/core.telegram.org/method/account.updatePasswordSettings @@ -0,0 +1,207 @@ + + + + + account.updatePasswordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updatePasswordSettings

+ +

Set a new 2FA password

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPThe old password (see SRP)
new_settingsaccount.PasswordInputSettingsThe new password (see SRP)
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMAIL_UNCONFIRMEDEmail unconfirmed.
400EMAIL_UNCONFIRMED_XThe provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email.
400NEW_SALT_INVALIDThe new salt is invalid.
400NEW_SETTINGS_INVALIDThe new password settings are invalid.
400PASSWORD_HASH_INVALIDThe old password hash is invalid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+

account.verifyEmail

+

Verify an email address for telegram passport.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateStatus b/data/core.telegram.org/method/account.updateStatus new file mode 100644 index 0000000000..ac302243e0 --- /dev/null +++ b/data/core.telegram.org/method/account.updateStatus @@ -0,0 +1,155 @@ + + + + + account.updateStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateStatus

+ +

Updates online user status.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.updateStatus#6628562c offline:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
offlineBoolIf (boolTrue) is transmitted, user status will change to (userStatusOffline).
+

Result

+

Bool

+

Related pages

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

userStatusOffline

+

The user's offline status.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateTheme b/data/core.telegram.org/method/account.updateTheme new file mode 100644 index 0000000000..65a1ec22dc --- /dev/null +++ b/data/core.telegram.org/method/account.updateTheme @@ -0,0 +1,196 @@ + + + + + account.updateTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateTheme

+ +

Update theme

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+---functions---
+account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme to update
slugflags.0?stringUnique theme ID
titleflags.1?stringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
+

Result

+

Theme

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400THEME_INVALIDInvalid theme provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/account.updateUsername b/data/core.telegram.org/method/account.updateUsername new file mode 100644 index 0000000000..b9437b2210 --- /dev/null +++ b/data/core.telegram.org/method/account.updateUsername @@ -0,0 +1,182 @@ + + + + + account.updateUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateUsername

+ +

Changes username for the current user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.updateUsername#3e0bdd7c username:string = User;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestringusername or empty string if username is to be removed
Accepted characters: a-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
+

Result

+

Returns updated information on the user in a User type object.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400USERNAME_INVALIDUnacceptable username.
400USERNAME_NOT_MODIFIEDUsername is not different from the current username.
400USERNAME_OCCUPIEDUsername is taken.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.bindTempAuthKey b/data/core.telegram.org/method/auth.bindTempAuthKey new file mode 100644 index 0000000000..031bd715ed --- /dev/null +++ b/data/core.telegram.org/method/auth.bindTempAuthKey @@ -0,0 +1,252 @@ + + + + + auth.bindTempAuthKey + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.bindTempAuthKey

+ +

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.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
perm_auth_key_idlongPermanent auth_key_id to bind to
noncelongRandom long from Binding message contents
expires_atintUnix timestamp to invalidate temporary key, see Binding message contents
encrypted_messagebytesSee Generating encrypted_message
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ENCRYPTED_MESSAGE_INVALIDEncrypted message is incorrect.
400TEMP_AUTH_KEY_ALREADY_BOUNDThe passed temporary key is already bound to another perm_auth_key_id.
400TEMP_AUTH_KEY_EMPTYThe request was not performed with a temporary authorization key.
+

Generating encrypted_message

+

The client begins by creating a special binding message:

+

Binding message contents

+
bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
noncelongRandom long
temp_auth_key_idlongTemporary auth_key_id
perm_auth_key_idlongPermanent auth_key_id to bind to
temp_session_idlongSession id, which will be used to invoke auth.bindTempAuthKey method
expires_atintUnix timestamp to invalidate temporary key
+

Encrypting the binding message

+

This binding message is encrypted in the usual way, but with MTProto v1 using the perm_auth_key. In other words, one has to prepend random:int128 (it replaces the customary session_id:long and salt:long that are irrelevant in this case), then append the same msg_id that will be used for the request, a seqno equal to zero, and the correct msg_len (40 bytes in this case); after that, one computes the msg_key:int128 as SHA1 of the resulting string, appends padding necessary for a 16-byte alignment, encrypts the resulting string using the key derived from perm_auth_key and msg_key, and prepends perm_auth_key_id and msg_key to the encrypted data as usual.

+

Binding

+

Once encrypted_message is ready, an auth.bindTempAuthKey request is sent to the server using temp_auth_key and temp_session_id. Don't forget to rewrite client info using initConnection when the binding is completed.

+

Bots can use this method

+

Related pages

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

long

+

A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

+

More on basic types »

+

int

+

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

+

More on basic types »

+

Mobile Protocol: Detailed Description

+

Calling API Methods

+

Additional options for calling methods.

+

initConnection

+

Initialize connection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.importBotAuthorization b/data/core.telegram.org/method/auth.importBotAuthorization new file mode 100644 index 0000000000..7e42ede178 --- /dev/null +++ b/data/core.telegram.org/method/auth.importBotAuthorization @@ -0,0 +1,205 @@ + + + + + auth.importBotAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importBotAuthorization

+ +

Login as a bot

+

+ +
+
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flagsintReserved for future use
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
bot_auth_tokenstringBot token (see bots)
+

Result

+

Returns an auth.Authorization object with information on the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ACCESS_TOKEN_EXPIREDBot token expired.
400ACCESS_TOKEN_INVALIDThe provided token is not valid.
400API_ID_INVALIDThe api_id/api_hash combination is invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_INVALIDAuth key invalid.
+

Bots can use this method

+

Related pages

+

Bots: An introduction for developers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.requestPasswordRecovery b/data/core.telegram.org/method/auth.requestPasswordRecovery new file mode 100644 index 0000000000..d7d23e9d16 --- /dev/null +++ b/data/core.telegram.org/method/auth.requestPasswordRecovery @@ -0,0 +1,159 @@ + + + + + auth.requestPasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.requestPasswordRecovery

+ +

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+---functions---
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

auth.PasswordRecovery

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_EMPTYThe provided password is empty.
400PASSWORD_RECOVERY_NANo email was set, can't recover password via email.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.resetAuthorizations b/data/core.telegram.org/method/auth.resetAuthorizations new file mode 100644 index 0000000000..d09fa29b02 --- /dev/null +++ b/data/core.telegram.org/method/auth.resetAuthorizations @@ -0,0 +1,156 @@ + + + + + auth.resetAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.resetAuthorizations

+ +

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

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.resetAuthorizations#9fab0d1a = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
+

Related pages

+

account.registerDevice

+

Register device to receive PUSH notifications

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/auth.sendInvites b/data/core.telegram.org/method/auth.sendInvites new file mode 100644 index 0000000000..36ea47ee07 --- /dev/null +++ b/data/core.telegram.org/method/auth.sendInvites @@ -0,0 +1,157 @@ + + + + + auth.sendInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendInvites

+ +

Saves information that the current user sent SMS-messages with invitations to its unregistered contacts.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numbersVector<string>List of phone numbers of message recipients in the international format
messagestringMessage text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/bots.resetBotCommands b/data/core.telegram.org/method/bots.resetBotCommands new file mode 100644 index 0000000000..19bc8f9ecf --- /dev/null +++ b/data/core.telegram.org/method/bots.resetBotCommands @@ -0,0 +1,156 @@ + + + + + bots.resetBotCommands + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.resetBotCommands

+ +

Clear bot commands for the specified bot scope and language code

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
+

Result

+

Bool

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.deleteHistory b/data/core.telegram.org/method/channels.deleteHistory new file mode 100644 index 0000000000..370317535f --- /dev/null +++ b/data/core.telegram.org/method/channels.deleteHistory @@ -0,0 +1,180 @@ + + + + + channels.deleteHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteHistory

+ +

Delete the history of a supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup whose history must be deleted
max_idintID of message up to which the history must be deleted
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.exportMessageLink b/data/core.telegram.org/method/channels.exportMessageLink new file mode 100644 index 0000000000..3907f2c777 --- /dev/null +++ b/data/core.telegram.org/method/channels.exportMessageLink @@ -0,0 +1,204 @@ + + + + + channels.exportMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.exportMessageLink

+ +

Get link and embed info of a message in a channel/supergroup

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+---functions---
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
groupedflags.0?trueWhether to include other grouped media (for albums)
threadflags.1?trueWhether to also include a thread ID, if available, inside of the link
channelInputChannelChannel
idintMessage ID
+

Result

+

ExportedMessageLink

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getAdminLog b/data/core.telegram.org/method/channels.getAdminLog new file mode 100644 index 0000000000..59c02d2c89 --- /dev/null +++ b/data/core.telegram.org/method/channels.getAdminLog @@ -0,0 +1,226 @@ + + + + + channels.getAdminLog + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getAdminLog

+ +

Get the admin log of a channel/supergroup

+

+ +
+
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+---functions---
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channelInputChannelChannel
qstringSearch query, can be empty
events_filterflags.0?ChannelAdminLogEventsFilterEvent filter
adminsflags.1?Vector<InputUser>Only show events from these admins
max_idlongMaximum ID of message to return (see pagination)
min_idlongMinimum ID of message to return (see pagination)
limitintMaximum number of results to return, see pagination
+

Result

+

channels.AdminLogResults

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getInactiveChannels b/data/core.telegram.org/method/channels.getInactiveChannels new file mode 100644 index 0000000000..d600060a77 --- /dev/null +++ b/data/core.telegram.org/method/channels.getInactiveChannels @@ -0,0 +1,134 @@ + + + + + channels.getInactiveChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getInactiveChannels

+ +

Get inactive channels and supergroups

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+---functions---
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

messages.InactiveChats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getLeftChannels b/data/core.telegram.org/method/channels.getLeftChannels new file mode 100644 index 0000000000..42d9b61911 --- /dev/null +++ b/data/core.telegram.org/method/channels.getLeftChannels @@ -0,0 +1,172 @@ + + + + + channels.getLeftChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getLeftChannels

+ +

Get a list of channels/supergroups we left

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset for pagination
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getParticipant b/data/core.telegram.org/method/channels.getParticipant new file mode 100644 index 0000000000..979a90ca5a --- /dev/null +++ b/data/core.telegram.org/method/channels.getParticipant @@ -0,0 +1,205 @@ + + + + + channels.getParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getParticipant

+ +

Get info about a channel/supergroup participant

+

+ +
+
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+---functions---
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
participantInputPeerParticipant to get info about
+

Result

+

channels.ChannelParticipant

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.getSponsoredMessages b/data/core.telegram.org/method/channels.getSponsoredMessages new file mode 100644 index 0000000000..ddb1b37570 --- /dev/null +++ b/data/core.telegram.org/method/channels.getSponsoredMessages @@ -0,0 +1,154 @@ + + + + + channels.getSponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getSponsoredMessages

+ +

Get a list of sponsored messages

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+---functions---
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelPeer
+

Result

+

messages.SponsoredMessages

+
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/channels.reportSpam b/data/core.telegram.org/method/channels.reportSpam new file mode 100644 index 0000000000..a2d1633f28 --- /dev/null +++ b/data/core.telegram.org/method/channels.reportSpam @@ -0,0 +1,192 @@ + + + + + channels.reportSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.reportSpam

+ +

Reports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserID of the user that sent the spam messages
idVector<int>IDs of spam messages
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USER_ID_INVALIDThe provided user ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getBlocked b/data/core.telegram.org/method/contacts.getBlocked new file mode 100644 index 0000000000..c7b1e35554 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getBlocked @@ -0,0 +1,155 @@ + + + + + contacts.getBlocked + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getBlocked

+ +

Returns the list of blocked users.

+

+ +
+
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+---functions---
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintThe number of list elements to be skipped
limitintThe number of list elements to be returned
+

Result

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getContactIDs b/data/core.telegram.org/method/contacts.getContactIDs new file mode 100644 index 0000000000..0b2d62f294 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getContactIDs @@ -0,0 +1,151 @@ + + + + + contacts.getContactIDs + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContactIDs

+ +

Get contact by telegram IDs

+

+ +
+
---functions---
+contacts.getContactIDs#7adc669d hash:long = Vector<int>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

Vector<int>

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getSaved b/data/core.telegram.org/method/contacts.getSaved new file mode 100644 index 0000000000..e74fada5e9 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getSaved @@ -0,0 +1,150 @@ + + + + + contacts.getSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getSaved

+ +

Get all contacts

+

+ +
+
---functions---
+contacts.getSaved#82f1e39f = Vector<SavedContact>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<SavedContact>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.getStatuses b/data/core.telegram.org/method/contacts.getStatuses new file mode 100644 index 0000000000..5ad7897b45 --- /dev/null +++ b/data/core.telegram.org/method/contacts.getStatuses @@ -0,0 +1,133 @@ + + + + + contacts.getStatuses + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getStatuses

+ +

Returns the list of contact statuses.

+

+ +
+
---functions---
+contacts.getStatuses#c4a353ee = Vector<ContactStatus>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<ContactStatus>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.importContacts b/data/core.telegram.org/method/contacts.importContacts new file mode 100644 index 0000000000..279b11ca35 --- /dev/null +++ b/data/core.telegram.org/method/contacts.importContacts @@ -0,0 +1,154 @@ + + + + + contacts.importContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.importContacts

+ +

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 to add Telegram contacts without actually using their phone number.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+---functions---
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<InputContact>List of contacts to import
+

Result

+

contacts.ImportedContacts

+

Related pages

+

contacts.addContact

+

Add an existing telegram user as contact.

+

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/contacts.resetSaved b/data/core.telegram.org/method/contacts.resetSaved new file mode 100644 index 0000000000..4fd122e042 --- /dev/null +++ b/data/core.telegram.org/method/contacts.resetSaved @@ -0,0 +1,135 @@ + + + + + contacts.resetSaved + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resetSaved

+ +

Delete saved contacts

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.resetSaved#879537f1 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/folders.deleteFolder b/data/core.telegram.org/method/folders.deleteFolder new file mode 100644 index 0000000000..2e32fc7ff7 --- /dev/null +++ b/data/core.telegram.org/method/folders.deleteFolder @@ -0,0 +1,175 @@ + + + + + folders.deleteFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

folders.deleteFolder

+ +

Delete a peer folder

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+folders.deleteFolder#1c295881 folder_id:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_EMPTYAn empty folder ID was specified.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.acceptTermsOfService b/data/core.telegram.org/method/help.acceptTermsOfService new file mode 100644 index 0000000000..d68ffeee0f --- /dev/null +++ b/data/core.telegram.org/method/help.acceptTermsOfService @@ -0,0 +1,150 @@ + + + + + help.acceptTermsOfService + + + + + + + + + + + + + +
+ +
+
+
+ +

help.acceptTermsOfService

+ +

Accept the new terms of service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idDataJSONID of terms of service
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getInviteText b/data/core.telegram.org/method/help.getInviteText new file mode 100644 index 0000000000..014bbc704d --- /dev/null +++ b/data/core.telegram.org/method/help.getInviteText @@ -0,0 +1,134 @@ + + + + + help.getInviteText + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getInviteText

+ +

Returns localized text of a text message with an invitation.

+

+ +
+
help.inviteText#18cb9f78 message:string = help.InviteText;
+---functions---
+help.getInviteText#4d392343 = help.InviteText;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.InviteText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getPromoData b/data/core.telegram.org/method/help.getPromoData new file mode 100644 index 0000000000..f34cdff29a --- /dev/null +++ b/data/core.telegram.org/method/help.getPromoData @@ -0,0 +1,135 @@ + + + + + help.getPromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getPromoData

+ +

Get MTProxy/Public Service Announcement information

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+---functions---
+help.getPromoData#c0977421 = help.PromoData;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.PromoData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getRecentMeUrls b/data/core.telegram.org/method/help.getRecentMeUrls new file mode 100644 index 0000000000..f60cdd6eee --- /dev/null +++ b/data/core.telegram.org/method/help.getRecentMeUrls @@ -0,0 +1,149 @@ + + + + + help.getRecentMeUrls + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getRecentMeUrls

+ +

Get recently used t.me links

+

+ +
+
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+---functions---
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
refererstringReferer
+

Result

+

help.RecentMeUrls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.getUserInfo b/data/core.telegram.org/method/help.getUserInfo new file mode 100644 index 0000000000..d8eaf8f75f --- /dev/null +++ b/data/core.telegram.org/method/help.getUserInfo @@ -0,0 +1,167 @@ + + + + + help.getUserInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getUserInfo

+ +

Internal use

+

+ +
+
help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+---functions---
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
+

Result

+

help.UserInfo

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
403USER_INVALIDInvalid user provided.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.hidePromoData b/data/core.telegram.org/method/help.hidePromoData new file mode 100644 index 0000000000..c9a15dcf42 --- /dev/null +++ b/data/core.telegram.org/method/help.hidePromoData @@ -0,0 +1,150 @@ + + + + + help.hidePromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.hidePromoData

+ +

Hide MTProxy/Public Service Announcement information

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer to hide
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/help.saveAppLog b/data/core.telegram.org/method/help.saveAppLog new file mode 100644 index 0000000000..1623540eed --- /dev/null +++ b/data/core.telegram.org/method/help.saveAppLog @@ -0,0 +1,150 @@ + + + + + help.saveAppLog + + + + + + + + + + + + + +
+ +
+
+
+ +

help.saveAppLog

+ +

Saves logs of application on the server.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
eventsVector<InputAppEvent>List of input events
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/invokeAfterMsgs.html b/data/core.telegram.org/method/invokeAfterMsgs.html new file mode 100644 index 0000000000..a0e9cda487 --- /dev/null +++ b/data/core.telegram.org/method/invokeAfterMsgs.html @@ -0,0 +1,154 @@ + + + + + invokeAfterMsgs + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeAfterMsgs

+ +

Invokes a query after a successfull completion of previous queries

+

+ +
+
---functions---
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idsVector<long>List of messages on which a current query depends
query!XThe query itself
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/langpack.getLangPack b/data/core.telegram.org/method/langpack.getLangPack new file mode 100644 index 0000000000..2ca79ec8fd --- /dev/null +++ b/data/core.telegram.org/method/langpack.getLangPack @@ -0,0 +1,171 @@ + + + + + langpack.getLangPack + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLangPack

+ +

Get localization pack strings

+

+ +
+
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+---functions---
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
+

Result

+

LangPackDifference

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.acceptEncryption b/data/core.telegram.org/method/messages.acceptEncryption new file mode 100644 index 0000000000..47732802b0 --- /dev/null +++ b/data/core.telegram.org/method/messages.acceptEncryption @@ -0,0 +1,190 @@ + + + + + messages.acceptEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.acceptEncryption

+ +

Confirms creation of a secret chat

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+---functions---
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputEncryptedChatSecret chat ID
g_bbytesB = g ^ b mod p, see Wikipedia
key_fingerprintlong64-bit fingerprint of the received key
+

Result

+

EncryptedChat

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400ENCRYPTION_ALREADY_ACCEPTEDSecret chat already accepted.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.acceptUrlAuth b/data/core.telegram.org/method/messages.acceptUrlAuth new file mode 100644 index 0000000000..99cc2cb187 --- /dev/null +++ b/data/core.telegram.org/method/messages.acceptUrlAuth @@ -0,0 +1,179 @@ + + + + + messages.acceptUrlAuth + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.acceptUrlAuth

+ +

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+---functions---
+messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
write_allowedflags.0?trueSet this flag to allow the bot to send messages to you (if requested)
peerflags.1?InputPeerThe location of the message
msg_idflags.1?intMessage ID of the message with the login button
button_idflags.1?intID of the login button
urlflags.2?stringURL used for link URL authorization, click here for more info »
+

Result

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.checkHistoryImport b/data/core.telegram.org/method/messages.checkHistoryImport new file mode 100644 index 0000000000..9abec2cbc3 --- /dev/null +++ b/data/core.telegram.org/method/messages.checkHistoryImport @@ -0,0 +1,152 @@ + + + + + messages.checkHistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.checkHistoryImport

+ +

Obtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».

+

+ +
+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+---functions---
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
import_headstringBeginning of the message file; up to 100 lines.
+

Result

+

messages.HistoryImportParsed

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteExportedChatInvite b/data/core.telegram.org/method/messages.deleteExportedChatInvite new file mode 100644 index 0000000000..65a67e647d --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteExportedChatInvite @@ -0,0 +1,155 @@ + + + + + messages.deleteExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteExportedChatInvite

+ +

Delete a chat invite

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
linkstringInvite link
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites b/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites new file mode 100644 index 0000000000..3103db9471 --- /dev/null +++ b/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites @@ -0,0 +1,155 @@ + + + + + messages.deleteRevokedExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteRevokedExportedChatInvites

+ +

Delete all revoked chat invites

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
admin_idInputUserID of the admin that originally generated the revoked chat invites
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.discardEncryption b/data/core.telegram.org/method/messages.discardEncryption new file mode 100644 index 0000000000..9e5b37e730 --- /dev/null +++ b/data/core.telegram.org/method/messages.discardEncryption @@ -0,0 +1,187 @@ + + + + + messages.discardEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discardEncryption

+ +

Cancels a request for creation and/or delete info on secret chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
delete_historyflags.0?trueWhether to delete the entire chat history for the other user as well
chat_idintSecret chat ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_EMPTYThe provided chat ID is empty.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatAbout b/data/core.telegram.org/method/messages.editChatAbout new file mode 100644 index 0000000000..206db20474 --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatAbout @@ -0,0 +1,216 @@ + + + + + messages.editChatAbout + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatAbout

+ +

Edit the description of a group/supergroup/channel.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe group/supergroup/channel.
aboutstringThe new description
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ABOUT_NOT_MODIFIEDAbout text has not changed.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatDefaultBannedRights b/data/core.telegram.org/method/messages.editChatDefaultBannedRights new file mode 100644 index 0000000000..caf4ce2cba --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatDefaultBannedRights @@ -0,0 +1,206 @@ + + + + + messages.editChatDefaultBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatDefaultBannedRights

+ +

Edit the default banned rights of a channel/supergroup/group.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer
banned_rightsChatBannedRightsThe new global rights
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BANNED_RIGHTS_INVALIDYou provided some invalid flags in the banned rights.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
400UNTIL_DATE_INVALIDInvalid until date provided.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.editChatTitle b/data/core.telegram.org/method/messages.editChatTitle new file mode 100644 index 0000000000..1cd755c064 --- /dev/null +++ b/data/core.telegram.org/method/messages.editChatTitle @@ -0,0 +1,193 @@ + + + + + messages.editChatTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatTitle

+ +

Chanages chat name and sends a service message on it.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
titlestringNew chat name, different from the old one
+

Result

+

Returns a messages.StatedMessage object containing a service message sent during an action.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.forwardMessages b/data/core.telegram.org/method/messages.forwardMessages new file mode 100644 index 0000000000..35fe91fc45 --- /dev/null +++ b/data/core.telegram.org/method/messages.forwardMessages @@ -0,0 +1,363 @@ + + + + + messages.forwardMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessages

+ +

Forwards messages by their IDs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send messages silently (no notification will be triggered on the destination clients)
backgroundflags.6?trueWhether to send the message in background
with_my_scoreflags.8?trueWhen forwarding games, whether to include your score in the game
drop_authorflags.11?trueWhether to forward messages without quoting the original author
drop_media_captionsflags.12?trueWhether to strip captions from media
from_peerInputPeerSource of messages
idVector<int>IDs of messages
random_idVector<long>Random ID to prevent resending of messages
to_peerInputPeerDestination peer
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400GROUPED_MEDIA_INVALIDInvalid grouped media.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
420P0NY_FLOODWAIT 
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_INVALIDA provided random ID is invalid.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SLOWMODE_MULTI_MSGS_DISABLEDSlowmode is enabled, you cannot forward multiple messages to this group.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getAdminsWithInvites b/data/core.telegram.org/method/messages.getAdminsWithInvites new file mode 100644 index 0000000000..26e37e4b8c --- /dev/null +++ b/data/core.telegram.org/method/messages.getAdminsWithInvites @@ -0,0 +1,149 @@ + + + + + messages.getAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAdminsWithInvites

+ +

Get info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+---functions---
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
+

Result

+

messages.ChatAdminsWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getArchivedStickers b/data/core.telegram.org/method/messages.getArchivedStickers new file mode 100644 index 0000000000..81acf27c79 --- /dev/null +++ b/data/core.telegram.org/method/messages.getArchivedStickers @@ -0,0 +1,167 @@ + + + + + messages.getArchivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getArchivedStickers

+ +

Get all archived stickers

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+---functions---
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueGet mask stickers
offset_idlongOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ArchivedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getBotCallbackAnswer b/data/core.telegram.org/method/messages.getBotCallbackAnswer new file mode 100644 index 0000000000..47db722c11 --- /dev/null +++ b/data/core.telegram.org/method/messages.getBotCallbackAnswer @@ -0,0 +1,226 @@ + + + + + messages.getBotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getBotCallbackAnswer

+ +

Press an inline callback button and get a callback answer from the bot

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+---functions---
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
gameflags.1?trueWhether this is a "play game" button
peerInputPeerWhere was the inline keyboard sent
msg_idintID of the Message with the inline keyboard
dataflags.0?bytesCallback data
passwordflags.2?InputCheckPasswordSRPFor buttons requiring you to verify your identity with your 2FA password, the SRP payload generated using SRP.
+

Result

+

messages.BotCallbackAnswer

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400DATA_INVALIDEncrypted data invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-503TimeoutTimeout while fetching data.
+

Related pages

+

keyboardButtonCallback

+

Callback button

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getChatInviteImporters b/data/core.telegram.org/method/messages.getChatInviteImporters new file mode 100644 index 0000000000..7ee6e1e7b3 --- /dev/null +++ b/data/core.telegram.org/method/messages.getChatInviteImporters @@ -0,0 +1,172 @@ + + + + + messages.getChatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getChatInviteImporters

+ +

Get info about the users that joined the chat using a specific chat invite

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+---functions---
+messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
linkstringInvite link
offset_dateintOffsets for pagination, for more info click here
offset_userInputUserUser ID for pagination
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ChatInviteImporters

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getChats b/data/core.telegram.org/method/messages.getChats new file mode 100644 index 0000000000..a37b1501e6 --- /dev/null +++ b/data/core.telegram.org/method/messages.getChats @@ -0,0 +1,173 @@ + + + + + messages.getChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getChats

+ +

Returns chat basic info on their IDs.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idVector<long>List of chat IDs
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getDialogUnreadMarks b/data/core.telegram.org/method/messages.getDialogUnreadMarks new file mode 100644 index 0000000000..7cf19f4084 --- /dev/null +++ b/data/core.telegram.org/method/messages.getDialogUnreadMarks @@ -0,0 +1,133 @@ + + + + + messages.getDialogUnreadMarks + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogUnreadMarks

+ +

Get dialogs manually marked as unread

+

+ +
+
---functions---
+messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogPeer>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getExportedChatInvite b/data/core.telegram.org/method/messages.getExportedChatInvite new file mode 100644 index 0000000000..26aa13353f --- /dev/null +++ b/data/core.telegram.org/method/messages.getExportedChatInvite @@ -0,0 +1,155 @@ + + + + + messages.getExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getExportedChatInvite

+ +

Get info about a chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+---functions---
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerChat
linkstringInvite link
+

Result

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getFeaturedStickers b/data/core.telegram.org/method/messages.getFeaturedStickers new file mode 100644 index 0000000000..f9d1ae7496 --- /dev/null +++ b/data/core.telegram.org/method/messages.getFeaturedStickers @@ -0,0 +1,153 @@ + + + + + messages.getFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getFeaturedStickers

+ +

Get featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+---functions---
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getMessagesViews b/data/core.telegram.org/method/messages.getMessagesViews new file mode 100644 index 0000000000..a2ab25b93d --- /dev/null +++ b/data/core.telegram.org/method/messages.getMessagesViews @@ -0,0 +1,199 @@ + + + + + messages.getMessagesViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessagesViews

+ +

Get and increase the view counter of a message sent or forwarded from a channel

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+---functions---
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the message was found
idVector<int>ID of message
incrementBoolWhether to mark the message as viewed and increment the view counter
+

Result

+

Vector<int>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getOldFeaturedStickers b/data/core.telegram.org/method/messages.getOldFeaturedStickers new file mode 100644 index 0000000000..1df560d371 --- /dev/null +++ b/data/core.telegram.org/method/messages.getOldFeaturedStickers @@ -0,0 +1,163 @@ + + + + + messages.getOldFeaturedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getOldFeaturedStickers

+ +

Method for fetching previously featured stickers

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+---functions---
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

messages.FeaturedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.getRecentLocations b/data/core.telegram.org/method/messages.getRecentLocations new file mode 100644 index 0000000000..2150b8166e --- /dev/null +++ b/data/core.telegram.org/method/messages.getRecentLocations @@ -0,0 +1,165 @@ + + + + + messages.getRecentLocations + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getRecentLocations

+ +

Get live location history of a certain user

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.initHistoryImport b/data/core.telegram.org/method/messages.initHistoryImport new file mode 100644 index 0000000000..247e72e358 --- /dev/null +++ b/data/core.telegram.org/method/messages.initHistoryImport @@ -0,0 +1,191 @@ + + + + + messages.initHistoryImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.initHistoryImport

+ +

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;
+---functions---
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe Telegram chat where the history should be imported.
fileInputFileFile with messages to import.
media_countintNumber of media files associated with the chat that will be uploaded using messages.uploadImportedMedia.
+

Result

+

messages.HistoryImport

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400IMPORT_FILE_INVALIDThe specified chat export file is invalid.
400IMPORT_FORMAT_UNRECOGNIZEDThe specified chat export file was exported from an unsupported chat app.
406PREVIOUS_CHAT_IMPORT_ACTIVE_WAIT_5MINImport for this chat is already in progress, wait 5 minutes before starting a new one.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

messages.uploadImportedMedia

+

Upload a media file associated with an imported chat, click here for more info ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.readHistory b/data/core.telegram.org/method/messages.readHistory new file mode 100644 index 0000000000..06802b10b5 --- /dev/null +++ b/data/core.telegram.org/method/messages.readHistory @@ -0,0 +1,186 @@ + + + + + messages.readHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readHistory

+ +

Marks message history as read.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerTarget user or group
max_idintIf a positive value is passed, only messages with identifiers less or equal than the given one will be read
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.receivedQueue b/data/core.telegram.org/method/messages.receivedQueue new file mode 100644 index 0000000000..39debae4f5 --- /dev/null +++ b/data/core.telegram.org/method/messages.receivedQueue @@ -0,0 +1,170 @@ + + + + + messages.receivedQueue + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.receivedQueue

+ +

Confirms receipt of messages in a secret chat by client, cancels push notifications.

+

+ +
+
---functions---
+messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
max_qtsintMaximum qts value available at the client
+

Result

+

Method returns a list of random_ids of messages for which push notifications were cancelled in Vector<long>.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MAX_QTS_INVALIDThe specified max_qts is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.reorderPinnedDialogs b/data/core.telegram.org/method/messages.reorderPinnedDialogs new file mode 100644 index 0000000000..0bb8c438db --- /dev/null +++ b/data/core.telegram.org/method/messages.reorderPinnedDialogs @@ -0,0 +1,185 @@ + + + + + messages.reorderPinnedDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.reorderPinnedDialogs

+ +

Reorder pinned dialogs

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueIf set, dialogs pinned server-side but not present in the order field will be unpinned.
folder_idintPeer folder ID, for more info click here
orderVector<InputDialogPeer>New dialog order
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.searchGifs b/data/core.telegram.org/method/messages.searchGifs new file mode 100644 index 0000000000..161693bb23 --- /dev/null +++ b/data/core.telegram.org/method/messages.searchGifs @@ -0,0 +1,177 @@ + + + + + messages.searchGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGifs

+ +

Search for GIFs

+

+ +
+
 Method schema is available as of layer 114. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
qstringText query
offsetintOffset for pagination »
+

Result

+

messages.FoundGifs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendEncrypted b/data/core.telegram.org/method/messages.sendEncrypted new file mode 100644 index 0000000000..b8ff1a69dc --- /dev/null +++ b/data/core.telegram.org/method/messages.sendEncrypted @@ -0,0 +1,210 @@ + + + + + messages.sendEncrypted + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendEncrypted

+ +

Sends a text message to a secret chat.

+

+ +
+
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+---functions---
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueSend encrypted message without a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID, necessary to avoid message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key that was created during chat initialization
+

Result

+

messages.SentEncryptedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_IS_BLOCKEDYou were blocked by this user.
+

Related pages

+

DecryptedMessage

+

Object describes the contents of an encrypted message.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendMultiMedia b/data/core.telegram.org/method/messages.sendMultiMedia new file mode 100644 index 0000000000..cfa150bdf1 --- /dev/null +++ b/data/core.telegram.org/method/messages.sendMultiMedia @@ -0,0 +1,263 @@ + + + + + messages.sendMultiMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMultiMedia

+ +

Send an album or grouped media

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the album silently (no notification triggered)
backgroundflags.6?trueSend in background?
clear_draftflags.7?trueWhether to clear drafts
peerInputPeerThe destination chat
reply_to_msg_idflags.0?intThe message to reply to
multi_mediaVector<InputSingleMedia>The medias to send
schedule_dateflags.10?intScheduled message date for scheduled messages
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MULTI_MEDIA_TOO_LONGToo many media files for album.
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_EMPTYRandom ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: wait X seconds before sending another message to this chat.
+

Bots can use this method

+

Related pages

+

Message drafts

+

How to handle message drafts

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.sendScheduledMessages b/data/core.telegram.org/method/messages.sendScheduledMessages new file mode 100644 index 0000000000..92715f213b --- /dev/null +++ b/data/core.telegram.org/method/messages.sendScheduledMessages @@ -0,0 +1,182 @@ + + + + + messages.sendScheduledMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendScheduledMessages

+ +

Send scheduled messages right away

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setBotCallbackAnswer b/data/core.telegram.org/method/messages.setBotCallbackAnswer new file mode 100644 index 0000000000..befb3bb4a6 --- /dev/null +++ b/data/core.telegram.org/method/messages.setBotCallbackAnswer @@ -0,0 +1,203 @@ + + + + + messages.setBotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setBotCallbackAnswer

+ +

Set the callback answer to a user button press (bots only)

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether to show the message as a popup instead of a toast notification
query_idlongQuery ID
messageflags.0?stringPopup to show
urlflags.2?stringURL to open
cache_timeintCache validity
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_TOO_LONGThe provided message is too long.
400QUERY_ID_INVALIDThe query ID is invalid.
400URL_INVALIDInvalid URL provided.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setChatTheme b/data/core.telegram.org/method/messages.setChatTheme new file mode 100644 index 0000000000..f581091ac8 --- /dev/null +++ b/data/core.telegram.org/method/messages.setChatTheme @@ -0,0 +1,185 @@ + + + + + messages.setChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setChatTheme

+ +

Change the chat theme of a certain chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPrivate chat where to change theme
emoticonstringEmoji, identifying a specific chat theme; a list of chat themes can be fetched using account.getChatThemes
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400EMOJI_INVALIDThe specified theme emoji is valid.
400EMOJI_NOT_MODIFIEDThe theme wasn't changed.
+

Related pages

+

account.getChatThemes

+

Get all available chat themes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setHistoryTTL b/data/core.telegram.org/method/messages.setHistoryTTL new file mode 100644 index 0000000000..0edfce6a9e --- /dev/null +++ b/data/core.telegram.org/method/messages.setHistoryTTL @@ -0,0 +1,182 @@ + + + + + messages.setHistoryTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setHistoryTTL

+ +

Set maximum Time-To-Live of all messages in the specified chat

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
periodintAutomatically delete all messages sent in the chat after this many seconds
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400TTL_PERIOD_INVALIDThe specified TTL period is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setInlineBotResults b/data/core.telegram.org/method/messages.setInlineBotResults new file mode 100644 index 0000000000..7de8b5d0c2 --- /dev/null +++ b/data/core.telegram.org/method/messages.setInlineBotResults @@ -0,0 +1,358 @@ + + + + + messages.setInlineBotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineBotResults

+ +

Answer an inline query, for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueSet this flag if the results are composed of media files
privateflags.1?trueSet this flag if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
query_idlongUnique identifier for the answered query
resultsVector<InputBotInlineResult>Vector of results for the inline query
cache_timeintThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
next_offsetflags.2?stringPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don‘t support pagination. Offset length can’t exceed 64 bytes.
switch_pmflags.3?InlineBotSwitchPMIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with a certain parameter.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ARTICLE_TITLE_EMPTYThe title of the article is empty.
400AUDIO_CONTENT_URL_EMPTYThe remote URL specified in the content field is empty.
400AUDIO_TITLE_EMPTYAn empty audio title was provided.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400DOCUMENT_INVALIDThe specified document is invalid.
400FILE_CONTENT_TYPE_INVALIDFile content-type is invalid.
400FILE_TITLE_EMPTYAn empty file title was specified.
400GIF_CONTENT_TYPE_INVALIDGIF content-type invalid.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400NEXT_OFFSET_INVALIDThe specified offset is longer than 64 bytes.
400PHOTO_CONTENT_TYPE_INVALIDPhoto mime-type invalid.
400PHOTO_CONTENT_URL_EMPTYPhoto URL invalid.
400PHOTO_INVALIDPhoto invalid.
400PHOTO_THUMB_URL_EMPTYPhoto thumbnail URL is empty.
400QUERY_ID_INVALIDThe query ID is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400RESULTS_TOO_MUCHToo many results were provided.
400RESULT_ID_DUPLICATEYou provided a duplicate result ID.
400RESULT_TYPE_INVALIDResult type invalid.
400SEND_MESSAGE_MEDIA_INVALIDInvalid media provided.
400SEND_MESSAGE_TYPE_INVALIDThe message type is invalid.
400START_PARAM_INVALIDStart parameter invalid.
400STICKER_DOCUMENT_INVALIDThe specified sticker document is invalid.
403USER_BOT_INVALIDThis method can only be called by a bot.
400VIDEO_TITLE_EMPTYThe specified video title is empty.
400WEBDOCUMENT_INVALIDInvalid webdocument URL provided.
400WEBDOCUMENT_MIME_INVALIDInvalid webdocument mime type provided.
400WEBDOCUMENT_SIZE_TOO_BIGWebdocument is too big!
400WEBDOCUMENT_URL_INVALIDThe specified webdocument URL is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.setInlineGameScore b/data/core.telegram.org/method/messages.setInlineGameScore new file mode 100644 index 0000000000..e2c2cd24e2 --- /dev/null +++ b/data/core.telegram.org/method/messages.setInlineGameScore @@ -0,0 +1,198 @@ + + + + + messages.setInlineGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineGameScore

+ +

Use this method to set the score of the specified user in a game sent as an inline message (bots only).

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
idInputBotInlineMessageIDID of the inline message
user_idInputUserUser identifier
scoreintNew score
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.uninstallStickerSet b/data/core.telegram.org/method/messages.uninstallStickerSet new file mode 100644 index 0000000000..915b78790f --- /dev/null +++ b/data/core.telegram.org/method/messages.uninstallStickerSet @@ -0,0 +1,167 @@ + + + + + messages.uninstallStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.uninstallStickerSet

+ +

Uninstall a stickerset

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetThe stickerset to uninstall
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/messages.updateDialogFilter b/data/core.telegram.org/method/messages.updateDialogFilter new file mode 100644 index 0000000000..61f26cef9c --- /dev/null +++ b/data/core.telegram.org/method/messages.updateDialogFilter @@ -0,0 +1,190 @@ + + + + + messages.updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updateDialogFilter

+ +

Update folder

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILTER_ID_INVALIDThe specified filter ID is invalid.
400FILTER_INCLUDE_EMPTYThe include_peers vector of the filter is empty.
400FILTER_TITLE_EMPTYThe title field of the filter is empty.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.acceptCall b/data/core.telegram.org/method/phone.acceptCall new file mode 100644 index 0000000000..396248bac2 --- /dev/null +++ b/data/core.telegram.org/method/phone.acceptCall @@ -0,0 +1,193 @@ + + + + + phone.acceptCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.acceptCall

+ +

Accept incoming call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe call to accept
g_bbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.confirmCall b/data/core.telegram.org/method/phone.confirmCall new file mode 100644 index 0000000000..26f29bbc5d --- /dev/null +++ b/data/core.telegram.org/method/phone.confirmCall @@ -0,0 +1,188 @@ + + + + + phone.confirmCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.confirmCall

+ +

Complete phone call E2E encryption key exchange »

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe phone call
g_abytesParameter for E2E encryption key exchange »
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.createGroupCall b/data/core.telegram.org/method/phone.createGroupCall new file mode 100644 index 0000000000..494106b9ca --- /dev/null +++ b/data/core.telegram.org/method/phone.createGroupCall @@ -0,0 +1,200 @@ + + + + + phone.createGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.createGroupCall

+ +

Create a group call or livestream

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerAssociate the group call or livestream to the provided group/supergroup/channel
random_idintUnique client message ID required to prevent creation of duplicate group calls
titleflags.0?stringCall title
schedule_dateflags.1?intFor scheduled group call or livestreams, the absolute date when the group call will start
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.editGroupCallParticipant b/data/core.telegram.org/method/phone.editGroupCallParticipant new file mode 100644 index 0000000000..0b2b587fec --- /dev/null +++ b/data/core.telegram.org/method/phone.editGroupCallParticipant @@ -0,0 +1,225 @@ + + + + + phone.editGroupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.editGroupCallParticipant

+ +

Edit information about a given group call participant

+

Note: flags.N?Bool parameters can have three possible values:

+
    +
  • If the TL flag is not set, the previous value will not be changed.
  • +
  • If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
  • +
  • If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
  • +
+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallThe group call
participantInputPeerThe group call participant (can also be the user itself)
mutedflags.0?BoolWhether to mute or unmute the specified participant
volumeflags.1?intNew volume
raise_handflags.2?BoolRaise or lower hand
video_stoppedflags.3?BoolStart or stop the video stream
video_pausedflags.4?BoolPause or resume the video stream
presentation_pausedflags.5?BoolPause or resume the screen sharing stream
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400USER_VOLUME_INVALIDThe specified user volume is invalid.
+

Related pages

+

Bool

+

Boolean type.

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+

boolFalse

+

Constructor may be interpreted as a booleanfalse value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.exportGroupCallInvite b/data/core.telegram.org/method/phone.exportGroupCallInvite new file mode 100644 index 0000000000..985569dbde --- /dev/null +++ b/data/core.telegram.org/method/phone.exportGroupCallInvite @@ -0,0 +1,159 @@ + + + + + phone.exportGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.exportGroupCallInvite

+ +

Get an invite link for a group call or livestream

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+---functions---
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_self_unmuteflags.0?trueFor livestreams, if set, users that join using this link will be able to speak without explicitly requesting permission by (for example by raising their hand).
callInputGroupCallThe group call
+

Result

+

phone.ExportedGroupCallInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.getGroupCallJoinAs b/data/core.telegram.org/method/phone.getGroupCallJoinAs new file mode 100644 index 0000000000..dea38cc8da --- /dev/null +++ b/data/core.telegram.org/method/phone.getGroupCallJoinAs @@ -0,0 +1,149 @@ + + + + + phone.getGroupCallJoinAs + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupCallJoinAs

+ +

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

+

+ +
+
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+---functions---
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog whose group call or livestream we're trying to join
+

Result

+

phone.JoinAsPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.saveCallDebug b/data/core.telegram.org/method/phone.saveCallDebug new file mode 100644 index 0000000000..43ee57b329 --- /dev/null +++ b/data/core.telegram.org/method/phone.saveCallDebug @@ -0,0 +1,177 @@ + + + + + phone.saveCallDebug + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.saveCallDebug

+ +

Send phone call debug data to server

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallPhone call
debugDataJSONDebug statistics obtained from libtgvoip
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400DATA_JSON_INVALIDThe provided JSON data is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/phone.setCallRating b/data/core.telegram.org/method/phone.setCallRating new file mode 100644 index 0000000000..f8e8a4a273 --- /dev/null +++ b/data/core.telegram.org/method/phone.setCallRating @@ -0,0 +1,192 @@ + + + + + phone.setCallRating + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.setCallRating

+ +

Rate a call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_initiativeflags.0?trueWhether the user decided on their own initiative to rate the call
peerInputPhoneCallThe call to rate
ratingintRating in 1-5 stars
commentstringAn additional comment
+

Result

+

Updates with info about the rating message sent to the official VoIP bot

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/photos.getUserPhotos b/data/core.telegram.org/method/photos.getUserPhotos new file mode 100644 index 0000000000..210930d62c --- /dev/null +++ b/data/core.telegram.org/method/photos.getUserPhotos @@ -0,0 +1,193 @@ + + + + + photos.getUserPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.getUserPhotos

+ +

Returns the list of user photos.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+---functions---
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
offsetintNumber of list elements to be skipped
max_idlongIf a positive value was transferred, the method will return only photos with IDs less than the set one
limitintNumber of list elements to be returned
+

Result

+

photos.Photos

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MAX_ID_INVALIDThe provided max ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/photos.uploadProfilePhoto b/data/core.telegram.org/method/photos.uploadProfilePhoto new file mode 100644 index 0000000000..a0481513af --- /dev/null +++ b/data/core.telegram.org/method/photos.uploadProfilePhoto @@ -0,0 +1,221 @@ + + + + + photos.uploadProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.uploadProfilePhoto

+ +

Updates current user profile photo.

+

+ +
+
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+---functions---
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts by means of upload.saveFilePart method
videoflags.1?InputFileAnimated profile picture video
video_start_tsflags.2?doubleFloating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.
+

Result

+

photos.Photo

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ALBUM_PHOTOS_TOO_MANYToo many .
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400PHOTO_CROP_FILE_MISSINGPhoto crop file missing.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_FILE_MISSINGProfile photo file missing.
400VIDEO_FILE_INVALIDThe specified video file is invalid.
+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.getBroadcastStats b/data/core.telegram.org/method/stats.getBroadcastStats new file mode 100644 index 0000000000..069ce9bb0f --- /dev/null +++ b/data/core.telegram.org/method/stats.getBroadcastStats @@ -0,0 +1,194 @@ + + + + + stats.getBroadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getBroadcastStats

+ +

Get channel statistics

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+---functions---
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelThe channel
+

Result

+

stats.BroadcastStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_REQUIREDThis method can only be called on a channel, please use stats.getMegagroupStats for supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stats.loadAsyncGraph b/data/core.telegram.org/method/stats.loadAsyncGraph new file mode 100644 index 0000000000..e73034a5ea --- /dev/null +++ b/data/core.telegram.org/method/stats.loadAsyncGraph @@ -0,0 +1,193 @@ + + + + + stats.loadAsyncGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.loadAsyncGraph

+ +

Load channel statistics graph asynchronously

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+---functions---
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
tokenstringGraph token from statsGraphAsync constructor
xflags.0?longZoom value, if required
+

Result

+

StatsGraph

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400GRAPH_EXPIRED_RELOADThis graph has expired, please obtain a new graph token.
400GRAPH_INVALID_RELOADInvalid graph token provided, please reload the stats and provide the updated token.
400GRAPH_OUTDATED_RELOADThe graph is outdated, please get a new async token using stats.getBroadcastStats.
+

Related pages

+

statsGraphAsync

+

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/stickers.checkShortName b/data/core.telegram.org/method/stickers.checkShortName new file mode 100644 index 0000000000..d4fe11206b --- /dev/null +++ b/data/core.telegram.org/method/stickers.checkShortName @@ -0,0 +1,172 @@ + + + + + stickers.checkShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.checkShortName

+ +

Check whether the given short name is available

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+stickers.checkShortName#284b3639 short_name:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringShort name
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400SHORT_NAME_INVALIDThe specified short name is invalid.
400SHORT_NAME_OCCUPIEDThe specified short name is already in use.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/method/upload.getFileHashes b/data/core.telegram.org/method/upload.getFileHashes new file mode 100644 index 0000000000..161326a0cc --- /dev/null +++ b/data/core.telegram.org/method/upload.getFileHashes @@ -0,0 +1,171 @@ + + + + + upload.getFileHashes + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getFileHashes

+ +

Get SHA256 hashes for verifying downloaded files

+

+ +
+
---functions---
+upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
locationInputFileLocationFile
offsetintOffset from which to get file hashes
+

Result

+

Vector<FileHash>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/methods.html b/data/core.telegram.org/methods.html new file mode 100644 index 0000000000..1b0c6e7f5a --- /dev/null +++ b/data/core.telegram.org/methods.html @@ -0,0 +1,2306 @@ + + + + + Methods + + + + + + + + + + + + + +
+ +
+
+
+ +

Methods

+ +

Accepting the Terms of Service

+ + + + + + + + + + + + + + + + + +
NameDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
help.acceptTermsOfServiceAccept the new terms of service
+

Dealing with spam and ToS violations

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.reportPeerReport a peer for violation of telegram's Terms of Service
account.reportProfilePhotoReport a profile photo of a dialog
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
messages.reportReport a message in a chat for violation of telegram's Terms of Service
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportEncryptedSpamReport a secret chat for spam
+

Fetching configuration

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.getAppChangelogGet changelog of current app.
Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.
help.getAppConfigGet app-specific configuration, see client configuration for more info on the result.
help.getAppUpdateReturns information on update availability for the current application.
help.getConfigReturns current configuration, including data center configuration.
help.getInviteTextReturns localized text of a text message with an invitation.
help.getNearestDcReturns info on data centre nearest to the user.
help.getSupportReturns the support user for the 'ask a question' feature.
help.getSupportNameGet localized name of the telegram support user
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
help.dismissSuggestionDismiss a suggestion, see here for more info ».
+

Login via QR code

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
auth.exportLoginTokenGenerate a login token, for login via QR code.
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.
auth.acceptLoginTokenAccept 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.
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
+

Miscellaneous

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.saveAppLogSaves logs of application on the server.
initConnectionInitialize connection
invokeAfterMsgInvokes a query after successfull completion of one of the previous queries.
invokeAfterMsgsInvokes a query after a successfull completion of previous queries
invokeWithLayerInvoke the specified query using the specified API layer
invokeWithoutUpdatesInvoke a request without subscribing the used connection for updates (this is enabled by default for file queries).
+

Registration/Authorization

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
auth.bindTempAuthKeyBinds 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.
auth.cancelCodeCancel the login verification code
auth.checkPasswordTry logging to an account protected by a 2FA password.
account.resetPasswordInitiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »
auth.checkRecoveryPasswordCheck if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.logOutLogs out the user.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
auth.resetAuthorizationsTerminates 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
auth.sendCodeSend the verification code for login
auth.signInSigns in a user with a validated phone number.
auth.signUpRegisters a validated phone number in the system.
+

Working with GDPR export

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.initTakeoutSessionInitialize account takeout session
account.finishTakeoutSessionFinish account takeout session
messages.getSplitRangesGet message ranges for saving the user's chat history
channels.getLeftChannelsGet a list of channels/supergroups we left
invokeWithMessagesRangeInvoke with the given message range
invokeWithTakeoutInvoke a method within a takeout session
+

Working with GIFs (actually MPEG4 GIFs)

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getSavedGifsGet saved GIFs
messages.saveGifAdd GIF to saved gifs list
messages.searchGifsSearch for GIFs
+

Working with Public Service Announcement and MTProxy channels

+ + + + + + + + + + + + + + + + + +
NameDescription
help.hidePromoDataHide MTProxy/Public Service Announcement information
help.getPromoDataGet MTProxy/Public Service Announcement information
+

Working with TSF (internal use only)

+ + + + + + + + + + + + + + + + + +
NameDescription
help.editUserInfoInternal use
help.getUserInfoInternal use
+

Working with 2FA login

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getPasswordObtain configuration for two-factor authorization with password
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
account.updatePasswordSettingsSet a new 2FA password
account.declinePasswordResetAbort a pending 2FA password reset, see here for more info »
+

Working with Seamless Telegram Login

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
account.getWebAuthorizationsGet web login widget authorizations
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
+

Working with VoIP calls

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
phone.discardCallRefuse or end running call
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.requestCallStart a telegram phone call
phone.saveCallDebugSend phone call debug data to server
phone.sendSignalingDataSend VoIP signaling data
phone.setCallRatingRate a call
messages.deletePhoneCallHistoryDelete the entire phone call history.
+

Working with channels/supergroups/geogroups

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
channels.createChannelCreate a supergroup/channel.
channels.getInactiveChannelsGet inactive channels and supergroups
channels.deleteChannelDelete a channel/supergroup
channels.deleteHistoryDelete the history of a supergroup
channels.deleteMessagesDelete messages in a channel/supergroup
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editBannedBan/unban/kick a user in a supergroup/channel.
channels.editCreatorTransfer channel ownership
channels.editLocationEdit location of geogroup
channels.editPhotoChange the photo of a channel/supergroup
channels.editTitleEdit the name of a channel/supergroup
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
channels.getAdminLogGet the admin log of a channel/supergroup
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
channels.getChannelsGet info about channels/supergroups
channels.getFullChannelGet full info about a channel
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups.

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.
channels.getMessagesGet channel/supergroup messages
channels.getParticipantGet info about a channel/supergroup participant
channels.getParticipantsGet the participants of a supergroup/channel
channels.inviteToChannelInvite users to a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.readHistoryMark channel/supergroup history as read
channels.readMessageContentsMark channel/supergroup message contents as read
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
channels.setStickersAssociate a stickerset to the supergroup
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
channels.toggleSignaturesEnable/disable message signatures in channels
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
+

Working with chats/supergroups/channels

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getMessageReadParticipantsGet which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
messages.createChatCreates a new chat.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.editChatAboutEdit the description of a group/supergroup/channel.
messages.editChatAdminMake a user admin in a legacy group.
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.editChatTitleChanages chat name and sends a service message on it.
messages.exportChatInviteExport an invite link for a chat
messages.getAllChatsGet all chats, channels and supergroups
messages.getChatsReturns chat basic info on their IDs.
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
messages.deleteExportedChatInviteDelete a chat invite
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteChatDelete a chat
messages.getCommonChatsGet chats in common with a user
messages.getFullChatReturns full chat info according to its ID.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
messages.migrateChatTurn a legacy group into a supergroup
channels.convertToGigagroupConvert a supergroup to a gigagroup, when requested by channel suggestions.
+

Working with deep links

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getDeepLinkInfoGet info about a t.me link
help.getRecentMeUrlsGet recently used t.me links
+

Working with files

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
help.getCdnConfigGet configuration for CDN file downloads.
upload.getCdnFileDownload a CDN file.
upload.getCdnFileHashesGet SHA256 hashes for verifying downloaded CDN files
upload.reuploadCdnFileRequest a reupload of a certain file to a CDN DC.
upload.getFileReturns content of a whole file or its part.
upload.getFileHashesGet SHA256 hashes for verifying downloaded files
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
+

Working with instant view pages

+ + + + + + + + + + + + + + + + + +
NameDescription
messages.getWebPageGet instant view page
messages.getWebPagePreviewGet preview of webpage
+

Working with secret chats

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.acceptEncryptionConfirms creation of a secret chat
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
messages.receivedQueueConfirms receipt of messages in a secret chat by client, cancels push notifications.
+

Working with telegram passport

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
account.verifyPhoneVerify a phone number for telegram passport.
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
account.getAuthorizationsGet logged-in sessions
account.deleteSecureValueDelete stored Telegram Passport documents, for more info see the passport docs »
account.getAllSecureValuesGet all saved Telegram Passport documents, for more info see the passport docs »
account.getSecureValueGet saved Telegram Passport document, for more info see the passport docs »
account.saveSecureValueSecurely save Telegram Passport document, for more info see the passport docs »
help.getPassportConfigGet passport configuration
users.setSecureValueErrorsNotify the user that the sent 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.
+

Working with updates

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
updates.getDifferenceGet new updates.
updates.getStateReturns a current state of updates.
+

Working with bot inline queries and callback buttons

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getInlineBotResultsQuery an inline bot
messages.setInlineBotResultsAnswer an inline query, for bots only
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
messages.editInlineBotMessageEdit an inline bot message
+

Working with bots

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
bots.getBotCommandsObtain a list of bot commands for the specified bot scope and language code
bots.setBotCommandsSet bot command list
+

Working with bots (internal bot API use)

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
bots.sendCustomRequestSends a custom request; for bots only
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
+

Working with cloud themes

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.updateThemeUpdate theme
account.uploadThemeUpload theme
account.getThemesGet installed themes
account.createThemeCreate a theme
account.installThemeInstall a theme
account.saveThemeSave a theme
account.getThemeGet theme information
account.getChatThemesGet all available chat themes
messages.setChatThemeChange the chat theme of a certain chat
+

Working with contacts and top peers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
contacts.addContactAdd an existing telegram user as contact.

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.
contacts.blockAdds the user to the blacklist.
contacts.deleteByPhonesDelete contacts by phone number
contacts.deleteContactsDeletes several contacts from the list.
contacts.getBlockedReturns the list of blocked users.
contacts.getContactIDsGet contact by telegram IDs
contacts.getContactsReturns the current user's contact list.
contacts.getLocatedGet contacts near you
contacts.getSavedGet all contacts
contacts.getStatusesReturns the list of contact statuses.
contacts.getTopPeersGet most used peers
contacts.importContactsImports 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 to add Telegram contacts without actually using their phone number.
contacts.resetSavedDelete saved contacts
contacts.resetTopPeerRatingReset rating of top peer
contacts.searchReturns users found by username substring.
contacts.toggleTopPeersEnable/disable top peers
contacts.unblockDeletes the user from the blacklist.
+

Working with credit cards

+ + + + + + + + + + + + + +
NameDescription
payments.getBankCardDataGet info about a credit card
+

Working with dialogs

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getDialogsReturns the current user dialog list.
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
messages.getDialogUnreadMarksGet dialogs manually marked as unread
messages.markDialogUnreadManually mark dialog as unread
messages.getPeerSettingsGet peer settings
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
messages.getOnlinesGet count of online users in a chat
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
+

Working with drafts

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.clearAllDraftsClear all drafts.
messages.getAllDraftsSave get all message drafts.
messages.saveDraftSave a message draft associated to a chat.
+

Working with emoji keywords

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
messages.getEmojiKeywordsLanguagesGet info about an emoji keyword localization
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
+

Working with folders

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.updateDialogFiltersOrderReorder folders
messages.getDialogFiltersGet folders
messages.getSuggestedDialogFiltersGet suggested folders
messages.updateDialogFilterUpdate folder
folders.deleteFolderDelete a peer folder
folders.editPeerFoldersEdit peers in peer folder
+

Working with games

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
+

Working with group calls & live streaming

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
phone.editGroupCallParticipantEdit information about a given group call participant

Note: flags.N?Bool parameters can have three possible values:

- If the TL flag is not set, the previous value will not be changed.
- If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
- If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
phone.toggleGroupCallRecordStart or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.getGroupParticipantsGet group call participants
phone.checkGroupCallCheck whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs
phone.createGroupCallCreate a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.leaveGroupCallLeave a group call
phone.toggleGroupCallSettingsChange group call settings
phone.inviteToGroupCallInvite a set of users to a group call.
phone.getGroupCallGet info about a group call
phone.joinGroupCallJoin a group call
phone.leaveGroupCallPresentationStop screen sharing in a group call
phone.discardGroupCallTerminate a group call
phone.joinGroupCallPresentationStart screen sharing in a call
phone.startScheduledGroupCallStart a scheduled group call.
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
+

Working with imported chats

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.uploadImportedMediaUpload a media file associated with an imported chat, click here for more info ».
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».
+

Working with localization packs

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
langpack.getDifferenceGet new strings in languagepack
langpack.getLangPackGet localization pack strings
langpack.getLanguageGet information about a language in a localization pack
langpack.getLanguagesGet information about all languages in a localization pack
langpack.getStringsGet strings from a language pack
+

Working with media autodownload settings

+ + + + + + + + + + + + + + + + + +
NameDescription
account.getAutoDownloadSettingsGet media autodownload settings
account.saveAutoDownloadSettingsChange media autodownload settings
+

Working with message threads

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getRepliesGet messages in a reply thread
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
messages.readDiscussionMark a thread as read
+

Working with message reactions

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getMessagesReactionsGet message reactions
messages.sendReactionSend reaction to message
messages.getMessageReactionsListGet full message reaction list
+

Working with messages

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.deleteHistoryDeletes communication history.
messages.deleteMessagesDeletes messages by their identifiers.
messages.editMessageEdit message
messages.forwardMessagesForwards messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.getMessageEditDataFind out if a media message's caption can be edited
messages.getMessagesReturns the list of messages by their IDs.
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
messages.getRecentLocationsGet live location history of a certain user
messages.getSearchCountersGet the number of results that would be found by a messages.search call with the same parameters
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.readHistoryMarks message history as read.
messages.readMentionsMark mentions as read
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
messages.receivedMessagesConfirms receipt of messages by a client, cancels PUSH-notification sending.
messages.searchGets back found messages
messages.searchGlobalSearch for messages and peers globally
messages.sendMediaSend a media
messages.sendMessageSends a message to a chat
messages.sendMultiMediaSend an album or grouped media
messages.updatePinnedMessagePin a message
messages.unpinAllMessagesUnpin all pinned messages
+

Working with notification settings

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.getNotifyExceptionsReturns list of chats with non-default notification settings
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
+

Working with other users

+ + + + + + + + + + + + + + + + + +
NameDescription
users.getFullUserReturns extended user info by ID.
users.getUsersReturns basic user info according to their identifiers.
+

Working with payments

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
payments.getSavedInfoGet saved payment information
payments.clearSavedInfoClear saved payment information
payments.getPaymentFormGet a payment form
payments.validateRequestedInfoSubmit requested order information for validation
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
account.getTmpPasswordGet temporary payment password
payments.sendPaymentFormSend compiled payment form
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery 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.
payments.getPaymentReceiptGet payment receipt
+

Working with polls

+ + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getPollResultsGet poll results
messages.getPollVotesGet poll results for non-anonymous polls
messages.sendVoteVote in a poll
+

Working with scheduled messages

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.sendScheduledMessagesSend scheduled messages right away
messages.getScheduledHistoryGet scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
messages.getScheduledMessagesGet scheduled messages
+

Working with sensitive content (NSFW)

+ + + + + + + + + + + + + + + + + +
NameDescription
account.getContentSettingsGet sensitive content settings
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
+

Working with sponsored messages

+ + + + + + + + + + + + + + + + + +
NameDescription
channels.getSponsoredMessagesGet a list of sponsored messages
channels.viewSponsoredMessageMark a specific sponsored message as read
+

Working with sponsored proxies

+ + + + + + + + + + + + + +
NameDescription
help.getProxyDataGet promotion info of the currently-used MTProxy
+

Working with statistics

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
stats.getBroadcastStatsGet channel statistics
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.
stats.getMegagroupStatsGet supergroup statistics
stats.getMessageStatsGet message statistics
+

Working with stickers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
messages.getOldFeaturedStickersMethod for fetching previously featured stickers
messages.toggleStickerSetsApply changes to multiple stickersets
stickers.suggestShortNameSuggests a short name for a given stickerpack name
stickers.checkShortNameCheck whether the given short name is available
stickers.setStickerSetThumbSet stickerset thumbnail
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
messages.clearRecentStickersClear recent stickers
messages.faveStickerMark a sticker as favorite
messages.getAllStickersGet all installed stickers
messages.getArchivedStickersGet all archived stickers
messages.getAttachedStickersGet stickers attached to a photo or video
messages.getFavedStickersGet faved stickers
messages.getFeaturedStickersGet featured stickers
messages.getMaskStickersGet installed mask stickers
messages.getRecentStickersGet recent stickers
messages.getStickerSetGet info about a stickerset
messages.getStickersGet stickers by emoji
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.installStickerSetInstall a stickerset
messages.readFeaturedStickersMark new featured stickers as read
messages.reorderStickerSetsReorder installed stickersets
messages.searchStickerSetsSearch for stickersets
messages.uninstallStickerSetUninstall a stickerset
+

Working with the user's account

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.changePhoneChange the phone number of the current account
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.getAccountTTLGet days to live of account
account.getPrivacyGet privacy settings of current account
account.resetAuthorizationLog out an active authorized session by its hash
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.setAccountTTLSet account self-destruction period
account.setPrivacyChange privacy settings of current account
account.setGlobalPrivacySettingsSet global privacy settings
account.getGlobalPrivacySettingsGet global privacy settings
account.updateProfileUpdates user profile.
account.updateStatusUpdates online user status.
+

Working with user profile pictures

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
photos.deletePhotosDeletes profile photos.
photos.getUserPhotosReturns the list of user photos.
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
+

Working with usernames

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
account.updateUsernameChanges username for the current user.
account.checkUsernameValidates a username and checks availability.
contacts.resolveUsernameResolve a @username to get peer info
+

Working with wallpapers

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameDescription
account.getMultiWallPapersGet info about multiple wallpapers
account.getWallPaperGet info about a certain wallpaper
account.getWallPapersReturns a list of available wallpapers.
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveWallPaperInstall/uninstall wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-combinators.html b/data/core.telegram.org/mtproto/TL-combinators.html new file mode 100644 index 0000000000..d064ead04c --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-combinators.html @@ -0,0 +1,251 @@ + + + + + Formal description of TL combinators + + + + + + + + + + + + + +
+ +
+
+
+ +

Formal description of TL combinators

+ +

Formal declaration of TL combinators

+

Main article: Formal description of TL. See also TL Language.

+

Combinators in TL are declared as follows:

+
+

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
+full-combinator-id ::= lc-ident-full | _
+combinator-id ::= lc-ident-ns | _
+opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
+args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
+args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
+args ::= [ ! ] type-term
+multiplicity ::= nat-term
+var-ident-opt ::= var-ident | _
+conditional-arg-def ::= var-ident [ . nat-const ] ?
+result-type ::= boxed-type-ident { subexpr }
+result-type ::= boxed-type-ident < subexpr { , subexpr } >

+
+

We shall clarify what all this means.

+
    +
  • +

    A combinator identifier is either an identifier starting with a lowercase Latin letter (lc-ident), or a namespace identifier (also lc-ident) followed by a period and another lc-ident. Therefore, cons and lists.get are valid combinator identifiers.

    +
  • +
  • +

    A combinator has a name, also known as a number (not to be confused with the designation) -- a 32-bit number that unambiguously determines it. It is either calculated automatically (see below) or it is explicitly assigned in the declaration. To do this, a hash mark (#) and exactly 8 hexadecimal digits -- the combinator’s name -- are added to the identifier of the combinator being defined.

    +
  • +
  • +

    A combinator’s declaration begins with its identifier, to which its name (separated by a hash mark) may have been added.

    +
  • +
  • +

    After the combinator identifier comes the main part of the declaration, which consists of declarations of fields (or variables), including an indication of their types.

    +
  • +
  • +

    First come declarations of optional fields (of which there may be several or none at all). Then there are the declarations of the required fields (there may not be any of these either).

    +
  • +
  • +

    Any identifier that begins with an uppercase or lowercase letter and which does not contain references to a namespace can be a field (variable) identifier. Using uc-ident for identifiers of variable types and lc-indent for other variables is good practice.

    +
  • +
  • +

    Next a combinator declaration contains the equals sign (=) and the result type (it may be composite or appearing for the first time). The result type may be polymorphic and/or dependent; any fields of the defined constructor’s fields of type Type or # may be returned (as subexpressions).

    +
  • +
  • +

    A combinator declaration is terminated with a semicolon.

    +
  • +
+

In what follows, a constructor’s fields, variables, and arguments mean the same thing.

+

Optional field declarations

+
    +
  • +

    These have the form { field_1 ... field_k : type-expr }, where field_i is a variable (field) identifier that is unique within the scope of the combinator declaration, and type-expr is a type shared by all of the fields.

    +
  • +
  • +

    If k>1, this entry is functionally equivalent to { field_1 : type-expr } ... { field_k : type-expr }.

    +
  • +
  • +

    All optional fields must be explicitly named (using _ instead of field_i is not allowed).

    +
  • +
  • +

    Moreover, at present the names of all optional fields must share the combinator’s result type (possibly more than once) and themselves be of type # (i,e., nat) or Type. Therefore, if the exact result type is known, it is possible to determine the values of all of the combinator’s implicit parameters (possibly obtaining a contradiction of the form 2=3 in doing so, which means that the combinator is not allowed in the context).

    +
  • +
+

Required field declarations

+
    +
  • +

    These may have the form ( field_1 ... field_k : type-expr ), similar to an optional field declaration, but with parentheses. This entry is equivalent to ( field_1 : type-expr ) ... ( field_k : type-expr ), where the fields are defined one at a time.

    +
  • +
  • +

    The underscore sign (_) can be used as names of one or more fields (field_i), indicating that the field is anonymous (the exact name is unimportant).

    +
  • +
  • +

    One field may be declared without outer parentheses, like this: field_id : type-expr. Here, however, if type-expr is a complex type, parentheses may be necessary around type-expr (this is reflected in BNF).

    +
  • +
  • +

    Furthermore, one anonymous field may be declared using a type-expr entry, functionally equivalent to _ : type-expr.

    +
  • +
  • +

    Required field declarations follow one after another, separated by spaces (by any number of whitespace symbols, to be more precise).

    +
  • +
  • +

    The declared field’s type (type-expr) may use the declared combinator’s previously defined variables (fields) as subexpressions (i.e. parameter values). For example:

    +

    nil {X:Type} = List X; +cons {X:Type} hd:X tl:(list X) = List X; +typed_list (X:Type) (l : list X) = TypedList;

    +
  • +
+

Repetitions

+
    +
  • +

    These may only exist among required parameters. They have the form [ field-id : ] [ multiplicity * ] [ args ], where args has the same format as the combinator’s declaration of (several) required fields, except that all of the enclosing combinator’s previously declared fields may be used in the argument types.

    +
  • +
  • +

    The name of a field of an enclosing combinator that receives a repetition as a value may be specified (field-id), or bypassed, which is equivalent to using the underscore sign as a field-id.

    +
  • +
  • +

    The multiplicity field is an expression of the type # (nat), which can be a real constant, the name of a preceding field of type #, or an expression in the form ( c + v ), where c is a real constant and v is the name of a field of type #. The sense of the multiplicity field is to provide the length of the (repetition) vector, each element of which consists of values of the types enumerated in args.

    +
  • +
  • +

    The multiplicity field may be bypassed. In this case, the last preceding parameter of type # from the enclosing combinator is used (it must be).

    +
  • +
  • +

    Functionally, the repetition field-id : multiplicity * [ args ] is equivalent to the declaration of the single field ( field-id : %Tuple %AuxType multiplicity ), where aux_type is an auxiliary type with a new name defined as aux_type *args* = AuxType. If any of the enclosing type’s fields are used within args, they are added to the auxiliary constructor aux_type and to its AuxType result type as the first (optional) parameters.

    +
  • +
  • +

    If args consists of one anonymous field of type some-type, then some-type can be used directly instead of %AuxType.

    +
  • +
  • +

    If during implementation the repetitions are rewritten as indicated above, it is logical to use instead of aux_type and AuxType, some identifiers that contain the name of the outer combinator being defined and the repetition’s index number inside its definition.

    +
  • +
+

Example:

+
matrix {m n : #} a : m* [ n* [ double ] ] = Matrix m n;
+

is functionally equivalent to

+
aux_type {n : #} (_ : %Tuple double n) = AuxType n;
+matrix {m : #} {n : #} (a : %Tuple %(AuxType n) m) = Matrix m n;
+

Moreover, the built-in types Tuple and Vector could be defined as:

+
tnil {X : Type} = Tuple X 0;
+tcons {X : Type} {n : #} hd:X tl:%(Tuple X n) = Tuple X (S n);
+vector {X : Type} (n : #) (v : %(Tuple X n)) = Vector X;
+

Actually, the following equivalent entry is considered the definition of Vector (i.e. it is specifically this entry that is used to compute the name of the vector constructor and its partial applications):

+
vector {t : Type} # [ t ] = Vector t;
+

If we expand it using Tuple, we obtain the previous definition exactly.

+

Conditional fields

+

The construction

+
+

args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+conditional-arg-def ::= var-ident [ . nat-const ] ?

+
+

permits assigning fields which are only present if the value of a preceding mandatory or optional field of type # is not null (or if its chosen bit is not zero if the special binary bit-selection operator . is applied). +Example:

+
+

user {fields:#} id:int first_name:(fields.0?string) last_name:(fields.1?string) friends:(fields.2?%(Vector int)) = User fields;
+get_users req_fields:# ids:%(Vector int) = Vector %(User req_fields)

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-dependent.html b/data/core.telegram.org/mtproto/TL-dependent.html new file mode 100644 index 0000000000..987e34555b --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-dependent.html @@ -0,0 +1,236 @@ + + + + + TL-dependent + + + + + + + + + + + + + +
+ +
+
+
+ +

TL-dependent

+ +

Main article: TL Language.

+

In certain cases, types may depend not only on other types (polymorphism), but also on the parameters of another type (dependent types). The TL language provides very limited support for this functionality: dependence is only allowed on a natural parameter whose type is designated using # (alias nat, but this is private -- TL doesn’t currently support this synonym). Values of type # are serialized as 32-bit signed numbers from 0 to 2^31-1.

+

Example: integer tuples (vectors)

+

Suppose we want to use induction to define the types “one integer”, “two integers”, and “three integers”. We could try to define them as follows:

+
empty = Empty;
+single x:int = Single;
+pair x:int y:int = Pair;
+triple x:int y:int z:int = Triple;
+quadruple x:int y:int z:int t:int = Quadruple;
+...
+

or as:

+
empty = Empty;
+single x:int empty = Single;
+pair x:int y:single = Pair;
+triple x:int yz:pair = Triple;
+quadruple x:int yzt:triple = Quadruple;
+

or as:

+
tnil = Tuple0;
+tcons0 hd:int tl:Tuple0 = Tuple1;
+tcons1 hd:int tl:Tuple1 = Tuple2;
+tcons2 hd:int tl:Tuple2 = Tuple3;
+...
+tcons_n hd:int tl:Tuple_n = Tuple_(n+1)
+

The first two variations lead to the same serialization. For example, (2 3 9):%triple and (2 (3 9)):%triple serialize as three 32-bit numbers: 2 3 9. The last variation better emphasizes the inductive version of the definition, but it uses boxed types. This is good from a theoretical perspective, but it leads to “superfluous” constructor names in serialization.

+

Therefore, we will write %Type-Ident to indicate the bare type that corresponds to the boxed type Type-Ident with a single constructor. If this constructor is named constructor, then according to the definition %Type-Ident = %constructor. Now we can write our definition like this:

+
tnil = Tuple0;
+tcons_n hd:int tl:%Tuple_n = Tuple_(n+1)
+

If we now abstract n out of the name of the type name and make it like a parameter for a polymorphic (dependent, to be more exact) type, then something like the following can be written in a suitable functional language:

+
NewType Tuple (n : #) :=
+| tnil = Tuple 0
+| tcons n:# hd:int tl:%(Tuple n) = Tuple (S n)
+EndType;
+

In the TL language, it looks like this:

+
tnil = Tuple 0;
+tcons {n:#} hd:int tl:%(Tuple n) = Tuple (S n);
+

The function S : # -> # and the constant O : # (it is 0) are the function for the next natural number (S n = n + 1) and the constant null. Therefore, the type # (alias nat) behaves as if it were defined in TL using the constructors

+
O = nat;
+S nat = nat;
+

or, using syntax more typical of other functional languages,

+
NewType nat :=
+| O
+| S nat
+EndType;
+

Types of all defined combinators:

+
O : #
+S : # -> #
+Tuple : # -> Type
+tnil : Tuple 0
+tcons : forall n : #, int -> Tuple n -> Tuple (S n)
+

or

+
Tuple : forall n : #, Type;
+tcons : forall n : #, forall hd : int, forall tl : Tuple n, Tuple (S n)
+

Note that in this case the constructor tnil does not depend on the parameter n, while tcons does.

+

In an analogous manner, it is possible to define a complete binary tree of height h with strings in the leaf nodes:

+
tleaf value:string = BinTree 0;
+tnode {h:#} left:(BinTree h) right:(BinTree h) = BinTree (S h);
+

Or a random tree whose leaf nodes are all a distance of h from the root and whose nodes are all labeled with integers:

+
hleaf value:int = Tree 0;
+hnode {n:#} left:(Tree n) next:(Tree (S n)) = Tree (S n)
+hnil {n:#} = Tree (S n)
+

Another version:

+
hleaf' value:int = Tree' 0;
+hnode' {n:#} children:(list (Tree' n)) = Tree' (S n)
+

Polymorphic dependent types

+

Let us try to define a type Tuple X n whose values are n-tuples of type X values. In this way, Tuple will be simultaneously polymorphic and dependent:

+
Tuple : Type -> # -> Type;
+

In the familiar syntax of functional languages:

+
NewType Tuple {X : Type} {n : #} :=
+| vnil : Tuple X 0
+| vcons {n:#} hd:X tl:%(Tuple X n) : Tuple X (S n)
+EndType
+

or, in TL syntax,

+
vnil {X:Type} = Tuple X 0;
+vcons {X:Type} {n:#} tl:(%Tuple X n) = Tuple X S n
+

In the end we obtain terms for the following types:

+
vnil : forall X : Type, Tuple X 0
+vcons : forall X : Type, forall n : #, X -> Tuple X n -> Tuple X (S n)
+

or

+
vnil : forall X : Type, Tuple X 0
+vcons : forall X : Type, forall n : #, forall hd : X, forall tl : Tuple X n, Tuple X (S n)
+

Dependent sums

+

The Tuple we just defined differs from the built-in Vector type. Specifically, the Vector type formally depends on a single argument (a type), but our Tuple depends on two (a type and a number):

+
Tuple : Type -> # -> Type;
+Vector : Type -> Type;
+

The built-in Vector could be defined in terms of our Tuple using “summing across all n : #":

+
vector {X:Type} n:# v:(%Tuple X n) = Vector X;
+

Nevertheless, our Tuple has its advantages. For example, we can define data types such as:

+
matrix_10x10 a:(%Tuple (%Tuple double 10) 10) = Matrix_10x10;
+

In any event, remember that during calculation of the matrix_10x10 combinator’s number, all parentheses must be removed and the CRC32 of the string matrix_10x10 a:%Tuple %Tuple double 10 10 = Matrix_10x10 must be computed.

+

Moreover, we can define arbitrarily-sized matrices:

+
matrix {X:Type} m:# n:# a:(%Tuple (%Tuple X m) n) = Matrix X;
+

In this case using vector would result in storing the length of a row (m) in each row, e.g. n times.

+

Note that the serializations of values of type %Tuple X n and vector X (also known as %vector X and %Vector X) nearly match when n > 0: in both cases we obtain a single 32-bit number (equal to n-1 or n depending on the version) followed by the serializations of n objects of type X. (This is slightly untrue: values of type %Tuple X n can only be serialized if n is a constant or value known from one of the preceding fields of the enclosing entry; but then this n won’t be serialized explicitly anywhere).

+

Special syntax for repetitions

+

In view of the importance of the construction presented above, it is built into the TL language in the following manner. A substructure in the form of [ array-field-name ":" ] [ nat-ident "" ] "[" field-descr ... "]” may be used in the declaration of any combinator, where nat-ident* is the name of any previously encountered field of type # (if it is not explicitly indicated, the most recent is used). In abstract, this substructure is equivalent to:

+
aux_type *field-descr* ... = AuxType;
+*current_constructor* ... [ *array-field-name* ":" ] (%Tuple aux_type *nat-ident*)
+

For example, 10x10 matrices, vectors, and arbitrary matrices may be defined in the following way:

+
matrix {X:Type} m:# n:# a:n*[ m*[ X ] ] = Matrix X;
+matrix_10x10 a:10*[ 10*[ double ]] = Matrix_10x10;
+vector {X:Type} # [ X ] = Vector X;
+

We have already encountered the last version as a “definition” of the “built-in type” Vector.

+

Of course, several fields, as complex as desired, may be within the repeating part. Furthermore, besides using n as a repeat counter, one may use expressions of the form (n+const) and (const+n), where const is a small nonnegative constant, which are shorthand for S (S ( ... (S n) ... )):

+
repeat_np1 n:# a:(S n)*[ key:string value:string ] = Dictionary;
+

To calculate the CRC32 these expressions are converted to expressions of the form (const+X) without internal spaces. Additionally, the * in this case is not set off by spaces on the left and right.

+

Serialization of dependent types

+

Serialization of dependent types and polymorphic types is not a fundamental challenge: we have combinators with non-zero arity with Type values. For example, the type Tuple double 10 : Type serializes to 'Tuple' '%double' 10. Note that at present in practice there is virtually no need to serialize types, whether dependent or not.

+

Optional combinator parameters in TL

+

Optional combinator parameters in TL must possess the following properties:

+
    +
  • +

    Optional parameters must be precisely ythe combinator’s first several arguments;

    +
  • +
  • +

    The value of any optional parameter must be entirely determined by the combinator’s result type.

    +
  • +
+

For example, in cons {X:Type} hd:X tl:(list X) = list X the parameter X may be made optional, because it is located at the very beginning of the argument list and is unambiguously determined by the list X result type. Similarly, in tcons {X:Type} {n:#} hd:X tl:(%Tuple X n) = Tuple X (S n) the values of X and n are completely determined based on the Tuple X (S n) result type, therefore they made be made optional parameters.

+

It usually makes sense to move all of a constructor’s arguments satisfying the second condition to the beginning of the list, arrange them in the order they appear in the result type’s parameters, and make them optional. Given such an approach, the full version of a constructor is rarely needed -- only when we want to transmit the value of the polymorphic or dependent type as a value of type Object. In all other cases, the type of the expected value from the context is already known, which means that all optional parameters can be recovered during decomposition.

+

See also Optional combinator parameters and their values.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL-polymorph.html b/data/core.telegram.org/mtproto/TL-polymorph.html new file mode 100644 index 0000000000..c2a4b9cde8 --- /dev/null +++ b/data/core.telegram.org/mtproto/TL-polymorph.html @@ -0,0 +1,170 @@ + + + + + Polymorphism in TL + + + + + + + + + + + + + +
+ +
+
+
+ +

Polymorphism in TL

+ +

It should be noted that in the TL schema of the overwhelming majority of API calls the use of polymorphic types is restricted to the Vector type. Nevertheless, having a view of the big picture is still helpful.

+

Ordinary inductive types

+

For example, let us consider the IntList, which is defined as follows:

+
int_cons hd:int tl:IntList = IntList;
+int_nil = IntList;
+

The “int_cons” and “int_nil” constructors as well as the “IntList” type itself are expressions of the following types (writing A : X means that A is an expression of type X):

+
IntList : Type;
+int_cons : int -> IntList -> IntList;
+int_nil : IntList;
+

The keyword Type is used to denote the type of all types. Note that Type is not Object (Object is the type of all terms). +Here is alternative syntax that could be used in some other functional programming language (but not in TL):

+
NewType IntList :=
+| int_cons hd:int tl:IntList
+| int_nil
+EndType
+

Polymorphic type

+

TL supports the following version (curly brackets indicate optional fields, see below):

+
cons {X:Type} hd:X tl:(List X) = List X;
+nil {X:Type} = List X
+

Here is an alternative formulation in other functional languages with dependent types:

+
NewType List {X:Type} :=
+| cons {X:Type} hd:X tl:(List X)
+| nil {X:Type}
+EndType
+

In any event, these variations are equivalent to one another from the point of view of the formal theory of types and lead to the definition of the following terms:

+
List : Type -> Type;
+cons : forall (X:Type), X -> List X -> List X;
+nil : forall (X:Type), X -> List X;
+

In each case, remember that writing “A -> B” is shorthand for “forall (x : A), B” for any variable x not entering into A and B. For example, the “cons” type could be written as follows:

+
cons : forall (X:Type), forall (hd : X), forall (tl : List X), List X
+

or more compactly:

+
cons : forall (X : Type) (hd : X) (tl : List X), List X
+

See Calculus of constructions. Examples of functional languages with dependent types, which support similar constructions are Coq and Agda.

+

In this case, the entry after a universal quantifier proves to be more content-related than that after an arrow, because the name of a variable bound by the quantifier is used to transmit the name of the corresponding field in the constructor, even if this variable is not used anywhere as it pertains to the expression under the quantifier. Structurally, all of these entries of the “cons” type are equivalent.

+

Serialization of types (values of type Type)

+

As we can see, to serialize a value of type List X, which has been obtained by applying the combinator “cons X:Type hd:X tl:(List X) = List X”, we need to:

+
    +
  1. serialize the name of the “cons” combinator into a 32-bit number;
  2. +
  3. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
  4. +
  5. serialize the head of the list (hd) as a value of type X;
  6. +
  7. serialize the tail of the list as a value of the polymorphic type List X.
  8. +
+

In the first step, the natural question is which string exactly will be used to calculate the CRC32. It is proposed to take "cons X:Type hd:X tl:List X = List X” without the terminating semicolon and without any parentheses (closed type expressions are unambiguously reconstructed based on their construction’s prefix).

+

In the last step, we recursively resolve the very same problem of serializing a value of type List X; we will consider it resolved based on the assumption of induction in the construction of the value being serialized. We will similarly consider the third step understandable (induction in the construction of the value being serialized).

+

We still need to describe how to transmit (serialize) types, e.g. values of type Type. Types in TL schemas currently appear only as constructors’ optional parameters and are therefore never serialized explicitly. Rather, their values are inferred from the previously known type of the value being serialized.

+

For completeness we will describe how it would be possible to serialize types (values of type Type). However, keep in mind that for now this information is not useful. See Type serialization.

+

Optional arguments in polymorphic constructors

+

It was stated above that any subset of (the first few) parameters of any constructor can be identified as optional (by enclosing their declarations in curly brackets), but this is not actually entirely accurate. First, these optional parameters can only be of type Type or # (natural numbers). Second, optional parameters must share the return value’s type, otherwise their value cannot be determined.

+

Note that @'''constr-id''' means the constructor’s “full form” (in which all optional parameters become required), while '''constr-id'’ denotes its abbreviated form (without the optional arguments). If there are no optional arguments, then these two forms are the same. Constructors’ full forms are never used at present.

+

Bare polymorphic types

+

There is a small problem: if we want to serialize the value of the bare type ‘%pair string int’ or ‘%pair string Y’ (which in TL is usually denoted simply as “pair”, though the form “%Pair” is preferable), we cannot simultaneously use both the full constructor @pair and the partial pair, because the constructor’s name will not be serialized. Therefore, we must differentiate the bare types %@pair (type X, type Y, value x:X, and value y:Y are serialized) and %pair (only x:X and y:Y are serialized; types X and Y are known from the context). In practice, we nearly almost always need the bare type %pair, and this is precisely what “pair” means in the type’s context in TL. Therefore,

+
record name:string map:(List (pair int string)) = Record;
+

will be serialized approximately like we want it to be (the serialization of list elements will consist of the serialization of int and the serialization of string, without any additional headers, types, or combinator names). +Incidentally, when calculating the “record” combinator’s name 'record' in the example given above, the CRC32 of record name:string map:List pair int string = Record will be computed.

+

Also note that a more precise description of this type would be

+
record name:string map:(List %(Pair int string)) = Record
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/TL.html b/data/core.telegram.org/mtproto/TL.html new file mode 100644 index 0000000000..fdf733ae29 --- /dev/null +++ b/data/core.telegram.org/mtproto/TL.html @@ -0,0 +1,210 @@ + + + + + TL Language + + + + + + + + + + + + + +
+ +
+
+
+ +

TL Language

+ +

TL (Type Language) serves to describe the used system of types, constructors, and existing functions. In fact, the combinator description format presented in Binary Data Serialization is used.

+

See also:

+ +

Advanced topics:

+ +

Overview

+

A TL program usually consists of two sections separated by keyword ---functions---. The first section consists of declarations of built-in types and aggregate types (i.e. their constructors). The second section consists of the declared functions, i.e. functional combinators.

+

Actually, both the first and second sections consist of combinator declarations, each of which ends with a semicolon. However, the first section contains only constructors, while the second section only involves functions. Each combinator is declared using a “combinator declaration” in the format explained above. However, the combinator number and field names may be explicitly assigned.

+

If additional type declarations are required after functions have been declared, the keyword (section divider) ---types--- is used. Furthermore, a functional combinator may be declared in the type section if its result type begins with an exclamation point (in fact, when the function section is interpreted, this exclamation point is added automatically).

+

To explicitly define 32-bit names of combinators, a hash mark (#) is added immediately after the combinator’s name, followed by 8 hexadecimal digits.

+

Namespaces

+

Composite constructions like <namespace_identifier>.<constructor_identifier> and <namespace_identifier>.<Type_identifier> can be used as constructor- or type identifiers. The portion of the identifier to the left of the period is called the namespace. Moreover, the rule about a first uppercase letter in type identifiers and lowercase letter in constructor identifiers applies to the part of the construction after the period. For example, auth.Message would be a type, while auth.std_message would be a constructor.

+

Namespaces do not require a special declaration.

+

Comments

+

Comments are the same as in C++.

+

Example

+
// built-in types
+int#a8509bda ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+null = Null;
+
+vector {t:Type} # [ t ] = Vector t;
+coupleInt {alpha:Type} int alpha = CoupleInt<alpha>;
+coupleStr {gamma:Type} string gamma = CoupleStr gamma;  
+/* The name of the type variable is irrelevant: "gamma" could be replaced with "alpha"; 
+   However, the combinator number will depend on the specific choice. */
+
+intHash {alpha:Type} vector<coupleInt<alpha>> = IntHash<alpha>;
+strHash {alpha:Type} (vector (coupleStr alpha)) = StrHash alpha;
+intSortedHash {alpha:Type} intHash<alpha> = IntSortedHash<alpha>;
+strSortedHash {alpha:Type} (strHash alpha) = StrSortedHash alpha;
+
+// custom types
+pair x:Object y:Object = Pair;
+triple x:Object y:Object z:Object = Triple;
+
+user#d23c81a3 id:int first_name:string last_name:string = User;
+no_user#c67599d1 id:int = User;
+group id:int title:string last_name:string = Group;
+no_group = Group;
+
+---functions---
+
+// Maybe some built-in arithmetic functions; inverse quotes make "identifiers" out of arbitrary non-alphanumeric strings
+`+` Int Int = Int;
+`-` Int Int = Int;
+`+` Double Double = Double;
+// ...
+
+// API functions (aka RPC functions)
+getUser#b0f732d5 int = User;
+getUsers#2d84d5f5 (Vector int) = Vector User;
+

In this case, the user constructor has been explicitly assigned a number (0xd23c81a3); In fact, this was not necessary, since this value is the CRC32 of the string "user id:int first_name:string last_name:string = User", which would have been used by default.

+

Special constructors are not required for Vector int, Vector User, Vector Object, etc. -- the same universal constructor can be used everywhere:

+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;
+

Note that when the getUsers (Vector int) = Vector User; constructor number is calculated, the CRC32 of the string "getUsers Vector int = Vector User” is computed (from which all parentheses have been removed).

+

Notation T0<T1,T2,...,Tn> is syntactic sugar for (T0 (T1) (T2) ... (Tn)). For example, Vector<User> and (Vector User) are entirely interchangeable.

+

Example of an RPC query

+

Suppose we want to call getUsers([2,3,4]). This query will be serialized into a sequence of 32-bit integers as follows:

+
0x2d84d5f5 0x1cb5c415 0x3 0x2 0x3 0x4
+

Please note that TL serialization yields sequences of 32-bit integers. When it has to be embedded into a byte stream, for example a network packet, each 32-bit integer is represented by four bytes in little-endian order. In this way the above query corresponds to the following byte stream:

+
F5 D5 84 2D 15 C4 B5 1C 03 00 00 00 02 00 00 00 03 00 00 00 04 00 00 00
+

The response might look something like this:

+
0x1cb5c415 0x3 0xd23c81a3 0x2 0x74655005 0x00007265 0x72615006 0x72656b 0xc67599d1 0x3 0xd23c81a3 0x4 0x686f4a04 0x6e 0x656f4403
+

This roughly corresponds to

+
[{"id":2,"first_name":"Peter", "last_name":"Parker"},{},{"id":4,"first_name":"John","last_name":"Doe"}]
+

Note that in both cases the same universal constructor vector#1cb5c415 is used: in the request to serialize the value of type Vector int, and in the serialization of the value of type Vector User in the response. There is no ambiguity because in both cases the type of the value being (de)serialized is known before its (de)serialization begins. For example, after receiving the query, the server sees that the first part is 0x2d84d5f5, which corresponds to the combinator getUsers#2d84d5f5 (Vector int) = Vector User. Thus, it is understood that what follows will be a value of type Vector int. After receiving the response to this query, the client knows that it must receive a value of type Vector User and it deserializes the response accordingly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/mtproto/security_guidelines.html b/data/core.telegram.org/mtproto/security_guidelines.html new file mode 100644 index 0000000000..180cb6991a --- /dev/null +++ b/data/core.telegram.org/mtproto/security_guidelines.html @@ -0,0 +1,177 @@ + + + + + Security Guidelines for Client Developers + + + + + + + + + + + + + +
+ +
+
+
+ +

Security Guidelines for Client Developers

+ +
+ +

See also:

+

+ +

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply.

+
+

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+

Diffie-Hellman key exchange

+

We use DH key exchange in two cases:

+ +

In both cases, there are some verifications to be done whenever DH is used:

+

Validation of DH parameters

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

+

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

g_a and g_b validation

+

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Checking SHA1 hash values during key generation

+

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

+
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
+

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

+

Checking nonce, server_nonce and new_nonce fields

+

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

+

Using secure pseudorandom number generator to create DH secret parameters a and b

+

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

+

MTProto Encrypted Messages

+

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

+

Checking SHA256 hash value of msg_key

+

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA256 of the plaintext obtained as the result of decryption (including the final 12...1024 padding bytes), prepended with 32 bytes taken from the auth_key, as explained in MTProto 2.0 Description.

+

If an error is encountered before this check could be performed, the client must perform the msg_key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

+

Checking message length

+

The client must check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference (i.e. the length of the random padding) lies in the range from 12 to 1024 bytes.

+

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

+

Checking session_id

+

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

+

Checking msg_id

+

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

+

Behavior in case of mismatch

+

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

+

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

+

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

+
+

The previous version of security recommendations relevant for MTProto 1.0 clients is available here.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/passport/sdk-android.html b/data/core.telegram.org/passport/sdk-android.html new file mode 100644 index 0000000000..5060a7f97e --- /dev/null +++ b/data/core.telegram.org/passport/sdk-android.html @@ -0,0 +1,180 @@ + + + + + Android SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Android SDK

+ +
+ +

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Installing from Maven

+

Telegram Passport SDK is available from the Maven repository. +Add this line to the dependencies section in your build.gradle:

+
compile 'org.telegram:passport:1.1'
+

and sync your project.

+

Adding as a module

+

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

+

In settings.gradle, add ':telegrampassport' to includes:

+
include ':app', ':telegrampassport'
+

In the build.gradle file for your app, add this line to the dependencies section:

+
compile ':telegrampassport'
+

and sync your project.

+

Usage

+

Adding the button

+

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

+
TelegramLoginButton telegramButton;
+// ...
+telegramButton=new TelegramLoginButton(this);
+// Optionally you can change the roundness of the button corners
+// to better fit your design.
+telegramButton.setCornerRoundness(1f);
+viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
+

Or from XML:

+
 <org.telegram.passport.TelegramLoginButton
+             android:layout_width="wrap_content"
+             android:layout_height="wrap_content"
+             app:cornerRoundness="0.5"/>
+

Requesting authorization

+

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

+
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
+// ...
+telegramButton.setOnClickListener(new View.OnClickListener(){
+@Override
+public void onClick(View view){
+    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
+    req.botID=/* your bot ID here */;
+    req.publicKey=/* your bot public key here */;
+    req.nonce=/* a unique nonce to pass to the bot server */;
+    // Request either a passport or an ID card with selfie, a driver license, personal details with
+    // name as it appears in the documents, address with any address document, and a phone number.
+    // You could also pass a raw JSON object here if that's what works better for you
+    // (for example, if you already get it from your server in the correct format).
+    req.scope=new PassportScope(
+        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
+        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
+        PassportScope.DRIVER_LICENSE,
+        PassportScope.ADDRESS,
+        PassportScope.ADDRESS_DOCUMENT,
+        PassportScope.PHONE_NUMBER
+    );
+    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
+}});
+

If you need more control over the process, the TelegramPassport class contains several more methods:

+
    +
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • +
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • +
+

Handling the result

+

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/core.telegram.org/schema.html b/data/core.telegram.org/schema.html new file mode 100644 index 0000000000..83765d3d76 --- /dev/null +++ b/data/core.telegram.org/schema.html @@ -0,0 +1,1800 @@ + + + + + Schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Schema

+ +

Below you will find the current TL-schema. More details on TL »

+

See also the detailed schema in JSON »

+

See also TL-Schema for end-to-end encrypted messages »

+
+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+true#3fedd339 = True;
+
+vector#1cb5c415 {t:Type} # [ t ] = Vector t;
+
+error#c4b9f9bb code:int text:string = Error;
+
+null#56730bcc = Null;
+
+inputPeerEmpty#7f3b18ea = InputPeer;
+inputPeerSelf#7da07ec9 = InputPeer;
+inputPeerChat#35a95cb9 chat_id:long = InputPeer;
+inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
+inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
+inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
+inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;
+
+inputUserEmpty#b98886cf = InputUser;
+inputUserSelf#f7c1b13f = InputUser;
+inputUser#f21158c6 user_id:long access_hash:long = InputUser;
+inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;
+
+inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;
+
+inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
+inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;
+
+inputMediaEmpty#9664f57f = InputMedia;
+inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
+inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
+inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
+inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
+inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
+inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+inputMediaDice#e66fbf7b emoticon:string = InputMedia;
+
+inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
+inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
+inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
+
+inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
+
+inputPhotoEmpty#1cd7bf0d = InputPhoto;
+inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
+
+inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
+inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+inputTakeoutFileLocation#29be5899 = InputFileLocation;
+inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
+inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;
+
+peerUser#59511722 user_id:long = Peer;
+peerChat#36c6019a chat_id:long = Peer;
+peerChannel#a2a5371e channel_id:long = Peer;
+
+storage.fileUnknown#aa963b05 = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.filePdf#ae1e508d = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;
+
+userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+
+userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
+
+userStatusEmpty#9d05049 = UserStatus;
+userStatusOnline#edb93949 expires:int = UserStatus;
+userStatusOffline#8c703f was_online:int = UserStatus;
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#7bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;
+
+chatEmpty#29562865 id:long = Chat;
+chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
+chatForbidden#6592a1a7 id:long title:string = Chat;
+channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
+channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;
+
+chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
+channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
+
+chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
+chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
+chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;
+
+chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
+chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;
+
+chatPhotoEmpty#37c1011c = ChatPhoto;
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
+
+messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
+message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
+
+messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+
+messageActionEmpty#b6aef7b0 = MessageAction;
+messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
+messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
+messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
+messageActionChatDeletePhoto#95e3fbef = MessageAction;
+messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
+messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
+messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
+messageActionChannelCreate#95d2ac92 title:string = MessageAction;
+messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
+messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
+messageActionPinMessage#94bd38ed = MessageAction;
+messageActionHistoryClear#9fbab604 = MessageAction;
+messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
+messageActionScreenshotTaken#4792929b = MessageAction;
+messageActionCustomAction#fae69f56 message:string = MessageAction;
+messageActionBotAllowed#abe9affe domain:string = MessageAction;
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
+messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
+messageActionContactSignUp#f3f25f76 = MessageAction;
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;
+
+dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;
+
+photoEmpty#2331b22d id:long = Photo;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+
+photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
+photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
+
+geoPointEmpty#1117dd5f = GeoPoint;
+geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
+
+auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
+
+auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+
+auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
+
+inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
+inputNotifyUsers#193b4417 = InputNotifyPeer;
+inputNotifyChats#4a95e84e = InputNotifyPeer;
+inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;
+
+inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;
+
+peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
+
+peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
+
+wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+
+inputReportReasonSpam#58dbcab8 = ReportReason;
+inputReportReasonViolence#1e22c78d = ReportReason;
+inputReportReasonPornography#2e59d922 = ReportReason;
+inputReportReasonChildAbuse#adf44ee3 = ReportReason;
+inputReportReasonOther#c1e4a2b1 = ReportReason;
+inputReportReasonCopyright#9b89f93a = ReportReason;
+inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
+inputReportReasonFake#f5ddd6e7 = ReportReason;
+
+userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
+
+contact#145ade0b user_id:long mutual:Bool = Contact;
+
+importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;
+
+contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;
+
+contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+
+contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
+
+messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
+messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
+
+messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+
+messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+
+messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
+
+messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+
+inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
+inputMessagesFilterPhotos#9609a51c = MessagesFilter;
+inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
+inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
+inputMessagesFilterDocument#9eddf188 = MessagesFilter;
+inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
+inputMessagesFilterGif#ffc86587 = MessagesFilter;
+inputMessagesFilterVoice#50f5c392 = MessagesFilter;
+inputMessagesFilterMusic#3751b49e = MessagesFilter;
+inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
+inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
+inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
+inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
+inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
+inputMessagesFilterGeo#e7026d0d = MessagesFilter;
+inputMessagesFilterContacts#e062db83 = MessagesFilter;
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateMessageID#4e90bfd6 id:int random_id:long = Update;
+updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
+updateChatParticipants#7761198 participants:ChatParticipants = Update;
+updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
+updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
+updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
+updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
+updateEncryptedChatTyping#1710f156 chat_id:int = Update;
+updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
+updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
+updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
+updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
+updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
+updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
+updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
+updateUserPhone#5492a13 user_id:long phone:string = Update;
+updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
+updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
+updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
+updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
+updateChannel#635b4c09 channel_id:long = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
+updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
+updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
+updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
+updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
+updateStickerSets#43ae3dec = Update;
+updateSavedGifs#9375341e = Update;
+updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
+updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
+updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
+updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
+updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
+updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
+updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
+updateReadFeaturedStickers#571d2742 = Update;
+updateRecentStickers#9a422c20 = Update;
+updateConfig#a229dd06 = Update;
+updatePtsChanged#3354678f = Update;
+updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
+updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
+updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
+updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
+updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
+updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
+updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
+updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
+updateLangPackTooLong#46560264 lang_code:string = Update;
+updateLangPack#56022f4d difference:LangPackDifference = Update;
+updateFavedStickers#e511996d = Update;
+updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
+updateContactsReset#7084a7be = Update;
+updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
+updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
+updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
+updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
+updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
+updateNewScheduledMessage#39a51dfb message:Message = Update;
+updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
+updateTheme#8216fba3 theme:Theme = Update;
+updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
+updateLoginToken#564fe691 = Update;
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;
+updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
+updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
+updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
+updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
+updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
+updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
+updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
+updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
+updateChat#f89a6a4e chat_id:long = Update;
+updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
+updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
+updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
+updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
+updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
+updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
+updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;
+
+updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
+
+updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
+updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
+updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
+updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
+
+updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+
+photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+
+photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+
+upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
+
+config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+
+nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+
+help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
+help.noAppUpdate#c45a6536 = help.AppUpdate;
+
+help.inviteText#18cb9f78 message:string = help.InviteText;
+
+encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;
+
+encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
+inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
+inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
+
+encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;
+
+messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+
+messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
+messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
+
+inputDocumentEmpty#72f0eaae = InputDocument;
+inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;
+
+documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+help.support#17c6b5f6 phone_number:string user:User = help.Support;
+
+notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
+notifyUsers#b4c83b4c = NotifyPeer;
+notifyChats#c007cec3 = NotifyPeer;
+notifyBroadcasts#d612e8ef = NotifyPeer;
+
+sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
+sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
+sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
+speakingInGroupCallAction#d92c2285 = SendMessageAction;
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
+
+contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+
+inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
+inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
+inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
+inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
+inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
+inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
+inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
+inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;
+
+privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
+privacyKeyChatInvite#500e6dfa = PrivacyKey;
+privacyKeyPhoneCall#3d662b7b = PrivacyKey;
+privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
+privacyKeyForwards#69ec56a3 = PrivacyKey;
+privacyKeyProfilePhoto#96151fed = PrivacyKey;
+privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
+privacyKeyAddedByPhone#42ffd42b = PrivacyKey;
+
+inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
+inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
+inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
+inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
+inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
+inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
+inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;
+
+privacyValueAllowContacts#fffe1bac = PrivacyRule;
+privacyValueAllowAll#65427b82 = PrivacyRule;
+privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
+privacyValueDisallowContacts#f888fa1a = PrivacyRule;
+privacyValueDisallowAll#8b73e763 = PrivacyRule;
+privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
+privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
+privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;
+
+account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
+
+accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+
+documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+documentAttributeHasStickers#9801d2f7 = DocumentAttribute;
+
+messages.stickersNotModified#f1749a22 = messages.Stickers;
+messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
+
+messages.allStickersNotModified#e86602c3 = messages.AllStickers;
+messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
+
+messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+
+webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+
+authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+
+account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
+
+account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;
+
+auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+
+receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;
+
+chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
+
+chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
+chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
+chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
+
+inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+botCommand#c27ac8c7 command:string description:string = BotCommand;
+
+botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
+
+keyboardButton#a2fa4880 text:string = KeyboardButton;
+keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
+keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
+keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
+keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
+keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
+keyboardButtonGame#50f41ccf text:string = KeyboardButton;
+keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
+keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
+inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
+keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
+
+keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
+
+replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
+replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
+replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
+
+messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
+messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
+messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
+messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
+messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
+messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;
+
+inputChannelEmpty#ee8c1e86 = InputChannel;
+inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
+inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;
+
+contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+
+messageRange#ae30253 min_id:int max_id:int = MessageRange;
+
+updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+
+channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
+channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;
+
+channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
+channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;
+channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
+channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
+channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;
+
+channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
+channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
+channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
+channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
+channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
+channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
+channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
+channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
+
+channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+
+channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
+
+help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
+
+messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
+messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
+
+inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
+
+inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
+
+botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+
+botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
+botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;
+
+messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
+
+exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+
+messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+auth.codeTypeSms#72a3158c = auth.CodeType;
+auth.codeTypeCall#741cd3e3 = auth.CodeType;
+auth.codeTypeFlashCall#226ccefb = auth.CodeType;
+
+auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;
+auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;
+auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;
+auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;
+
+messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+
+messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+
+inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
+inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;
+
+inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;
+
+messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+
+topPeer#edcdc05b peer:Peer rating:double = TopPeer;
+
+topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
+topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
+topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
+topPeerCategoryGroups#bd17a14a = TopPeerCategory;
+topPeerCategoryChannels#161d9628 = TopPeerCategory;
+topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
+topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
+topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
+
+topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
+
+contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;
+draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;
+
+messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
+messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
+
+messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+
+messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+
+messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
+messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
+
+stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
+stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;
+
+maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;
+
+inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
+inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;
+
+game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
+
+inputGameID#32c3e77 id:long access_hash:long = InputGame;
+inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
+
+highScore#73a379eb pos:int user_id:long score:int = HighScore;
+
+messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+textEmpty#dc3d824f = RichText;
+textPlain#744694e0 text:string = RichText;
+textBold#6724abc4 text:RichText = RichText;
+textItalic#d912a59c text:RichText = RichText;
+textUnderline#c12622c4 text:RichText = RichText;
+textStrike#9bf8bb95 text:RichText = RichText;
+textFixed#6c3f19b9 text:RichText = RichText;
+textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
+textEmail#de5a0dd6 text:RichText email:string = RichText;
+textConcat#7e6260d7 texts:Vector<RichText> = RichText;
+textSubscript#ed6a8504 text:RichText = RichText;
+textSuperscript#c7fb5e01 text:RichText = RichText;
+textMarked#34b8621 text:RichText = RichText;
+textPhone#1ccb966a text:RichText phone:string = RichText;
+textImage#81ccf4f document_id:long w:int h:int = RichText;
+textAnchor#35553762 text:RichText name:string = RichText;
+
+pageBlockUnsupported#13567e8a = PageBlock;
+pageBlockTitle#70abc3fd text:RichText = PageBlock;
+pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
+pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
+pageBlockHeader#bfd064ec text:RichText = PageBlock;
+pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
+pageBlockParagraph#467a0766 text:RichText = PageBlock;
+pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
+pageBlockFooter#48870999 text:RichText = PageBlock;
+pageBlockDivider#db20b188 = PageBlock;
+pageBlockAnchor#ce0d37b0 name:string = PageBlock;
+pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
+pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
+pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
+pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
+pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
+pageBlockCover#39f23300 cover:PageBlock = PageBlock;
+pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
+pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
+pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
+pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
+pageBlockKicker#1e148390 text:RichText = PageBlock;
+pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
+pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
+pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
+pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
+pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;
+
+phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
+phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
+phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
+phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;
+
+dataJSON#7d748d04 data:string = DataJSON;
+
+labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
+
+invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
+
+paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;
+
+postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;
+
+paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
+
+paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
+
+webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+
+inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
+
+inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
+inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
+
+upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+
+payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+
+payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
+
+payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
+payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
+
+payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
+
+inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
+inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
+inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
+
+account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+
+shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
+
+inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;
+
+inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;
+
+phoneCallEmpty#5366c915 id:long = PhoneCall;
+phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
+phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;
+
+phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;
+phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;
+
+phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;
+
+phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+
+upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
+
+cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
+
+langPackString#cad181f6 key:string value:string = LangPackString;
+langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
+langPackStringDeleted#2979eeb2 key:string = LangPackString;
+
+langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
+
+langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+
+channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
+channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
+channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
+channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;
+channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;
+channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;
+channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;
+
+channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
+
+channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
+
+channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;
+
+popularContact#5ce14175 client_id:long importers:int = PopularContact;
+
+messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
+recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
+recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
+recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
+recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;
+
+help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
+
+inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
+
+webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;
+
+account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+
+inputMessageID#a676a322 id:int = InputMessage;
+inputMessageReplyTo#bad88395 id:int = InputMessage;
+inputMessagePinned#86872538 = InputMessage;
+inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;
+
+inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
+
+dialogPeer#e56dbf05 peer:Peer = DialogPeer;
+dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
+
+messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
+messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
+
+fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+inputClientProxy#75588b3f address:string port:int = InputClientProxy;
+
+help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+secureFileEmpty#64199744 = SecureFile;
+secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
+
+secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
+
+secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
+
+secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+
+secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
+
+account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
+
+account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
+
+help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+
+savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;
+
+account.takeout#4dba4501 id:long = account.Takeout;
+
+passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
+passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;
+
+securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
+
+inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
+inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;
+
+secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
+secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;
+
+help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
+help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
+
+inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;
+
+jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
+
+jsonNull#3f6d7b68 = JSONValue;
+jsonBool#c7345e6a value:Bool = JSONValue;
+jsonNumber#2be0dfa4 value:double = JSONValue;
+jsonString#b71e767a value:string = JSONValue;
+jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
+jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
+
+pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;
+
+pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;
+
+pageCaption#6f747657 text:RichText credit:RichText = PageCaption;
+
+pageListItemText#b92fb6cd text:RichText = PageListItem;
+pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;
+
+pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
+pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;
+
+pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;
+
+page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;
+
+help.supportName#8c05f1c9 name:string = help.SupportName;
+
+help.userInfoEmpty#f3ae2eed = help.UserInfo;
+help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
+
+pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+chatOnlines#f041e250 onlines:int = ChatOnlines;
+
+statsURL#47a971e0 url:string = StatsURL;
+
+chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;
+
+chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;
+
+inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
+inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
+inputWallPaperNoFile#967a462e id:long = InputWallPaper;
+
+account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+
+codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;
+
+wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;
+
+autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;
+
+account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
+
+emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
+emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;
+
+emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+
+emojiURL#a575739d url:string = EmojiURL;
+
+emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;
+
+folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;
+
+inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;
+
+folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;
+
+messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
+
+urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
+urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
+urlAuthResultDefault#a9d6db1f = UrlAuthResult;
+
+channelLocationEmpty#bfb5ad8b = ChannelLocation;
+channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;
+
+peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
+peerSelfLocated#f8ec284b expires:int = PeerLocated;
+
+restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;
+
+inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
+inputThemeSlug#f5890df1 slug:string = InputTheme;
+
+theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+
+account.themesNotModified#f41eb622 = account.Themes;
+account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
+
+auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+
+messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
+
+baseThemeClassic#c3a12462 = BaseTheme;
+baseThemeDay#fbd81688 = BaseTheme;
+baseThemeNight#b7b31ea8 = BaseTheme;
+baseThemeTinted#6d5f77ee = BaseTheme;
+baseThemeArctic#5b11125a = BaseTheme;
+
+inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;
+
+themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;
+
+webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;
+
+messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
+
+messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
+
+bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;
+
+payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+
+dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
+
+dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;
+
+statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;
+
+statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;
+
+statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;
+
+statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+
+messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;
+
+stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+
+help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+
+videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
+
+statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
+
+statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
+
+statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
+
+stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+
+globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
+
+help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
+
+help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
+
+help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+
+messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;
+
+messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+
+messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+
+messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+
+peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;
+
+stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
+
+groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;
+
+inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;
+
+groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;
+
+phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+
+phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
+
+inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
+inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
+inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
+inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
+inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;
+
+messages.historyImport#1662af0b id:long = messages.HistoryImport;
+
+messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+
+messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+
+chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;
+
+messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+
+messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;
+
+messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
+
+messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
+
+phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+
+groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;
+
+groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;
+
+stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+
+botCommandScopeDefault#2f6cb2ab = BotCommandScope;
+botCommandScopeUsers#3c4f04d8 = BotCommandScope;
+botCommandScopeChats#6fe1a881 = BotCommandScope;
+botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
+botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
+botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
+botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;
+
+account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;
+
+account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
+account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
+
+sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
+
+messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
+invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
+invokeWithMessagesRange#365275f2 {X:Type} range:MessageRange query:!X = X;
+invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;
+
+auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
+auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+auth.logOut#5717da40 = Bool;
+auth.resetAuthorizations#9fab0d1a = Bool;
+auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
+auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;
+auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;
+
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
+account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;
+account.resetNotifySettings#db7e1747 = Bool;
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
+account.updateStatus#6628562c offline:Bool = Bool;
+account.getWallPapers#7967d36 hash:long = account.WallPapers;
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
+account.checkUsername#2714d86c username:string = Bool;
+account.updateUsername#3e0bdd7c username:string = User;
+account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
+account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;
+account.deleteAccount#418d4e0b reason:string = Bool;
+account.getAccountTTL#8fc711d = AccountDaysTTL;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
+account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;
+account.updateDeviceLocked#38df3532 period:int = Bool;
+account.getAuthorizations#e320c158 = account.Authorizations;
+account.resetAuthorization#df77f3bc hash:long = Bool;
+account.getPassword#548a30f5 = account.Password;
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
+account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;
+account.resetWebAuthorizations#682d2594 = Bool;
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
+account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;
+account.resendPasswordEmail#7a7f2a15 = Bool;
+account.cancelPasswordEmail#c1cbd5b6 = Bool;
+account.getContactSignUpNotification#9f07c728 = Bool;
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
+account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
+account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
+account.resetWallPapers#bb3b9804 = Bool;
+account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;
+account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
+account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;
+account.getThemes#7206e458 format:string hash:long = account.Themes;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.getContentSettings#8b9b4dae = account.ContentSettings;
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;
+account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
+account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
+account.resetPassword#9308ce1b = account.ResetPasswordResult;
+account.declinePasswordReset#4c9409f6 = Bool;
+account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;
+
+users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;
+users.getFullUser#ca30a5b1 id:InputUser = UserFull;
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+
+contacts.getContactIDs#7adc669d hash:long = Vector<int>;
+contacts.getStatuses#c4a353ee = Vector<ContactStatus>;
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;
+contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;
+contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;
+contacts.search#11f812d8 q:string limit:int = contacts.Found;
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
+contacts.resetSaved#879537f1 = Bool;
+contacts.getSaved#82f1e39f = Vector<SavedContact>;
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
+contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
+contacts.acceptContact#f831a20f id:InputUser = Updates;
+contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;
+messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
+messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
+messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
+messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
+messages.reportSpam#cf1592db peer:InputPeer = Bool;
+messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.getChats#49e9528f id:Vector<long> = messages.Chats;
+messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;
+messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
+messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
+messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
+messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
+messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
+messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
+messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;
+messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
+messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;
+messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;
+messages.importChatInvite#6c50051c hash:string = Updates;
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
+messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
+messages.migrateChat#a2875319 chat_id:long = Updates;
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
+messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
+messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
+messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;
+messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
+messages.getAllDrafts#6a3f8d65 = Updates;
+messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
+messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;
+messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;
+messages.getAttachedStickers#cc5b67cc media:InputStickeredMedia = Vector<StickerSetCovered>;
+messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
+messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
+messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
+messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;
+messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
+messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;
+messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;
+messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
+messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;
+messages.clearAllDrafts#7e58ee9c = Bool;
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
+messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;
+messages.getEmojiKeywordsLanguages#4e9963b2 lang_codes:Vector<string> = Vector<EmojiLanguage>;
+messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
+messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
+messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
+messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
+messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
+messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
+messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;
+messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
+messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;
+messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
+messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;
+messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;
+messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
+messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
+messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;
+
+updates.getState#edd4882a = updates.State;
+updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;
+
+photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
+photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
+upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
+upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
+upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;
+
+help.getConfig#c4f9186b = Config;
+help.getNearestDc#1fb33026 = NearestDc;
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
+help.getInviteText#4d392343 = help.InviteText;
+help.getSupport#9cdf08cd = help.Support;
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
+help.getCdnConfig#52029342 = CdnConfig;
+help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;
+help.getAppConfig#98914110 = JSONValue;
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
+help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;
+help.getSupportName#d360e72c = help.SupportName;
+help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
+help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;
+help.getPromoData#c0977421 = help.PromoData;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
+
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
+channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;
+channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;
+channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
+channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;
+channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
+channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
+channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
+channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
+channels.joinChannel#24b524c5 channel:InputChannel = Updates;
+channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
+channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
+channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;
+channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
+channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
+channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
+channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
+channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
+channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
+channels.getInactiveChannels#11e831ee = messages.InactiveChats;
+channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;
+
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;
+
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
+payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
+payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
+payments.getSavedInfo#227d824b = payments.SavedInfo;
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;
+
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;
+stickers.checkShortName#284b3639 short_name:string = Bool;
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;
+
+phone.getCallConfig#55451fa9 = DataJSON;
+phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
+phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
+phone.createGroupCall#48cdc6d8 flags:# rtmp_stream:flags.2?true peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
+phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
+phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
+phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
+phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;
+phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
+phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
+phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
+phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
+phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;
+phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
+phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
+phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
+
+langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
+langpack.getStrings#efea3803 lang_pack:string lang_code:string keys:Vector<string> = Vector<LangPackString>;
+langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;
+langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;
+
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
+folders.deleteFolder#1c295881 folder_id:int = Updates;
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
+stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
+stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
+
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/schema/mtproto.html b/data/core.telegram.org/schema/mtproto.html new file mode 100644 index 0000000000..74d5a9b3d4 --- /dev/null +++ b/data/core.telegram.org/schema/mtproto.html @@ -0,0 +1,204 @@ + + + + + Current MTProto TL-schema + + + + + + + + + + + + + +
+ +
+
+
+ +

Current MTProto TL-schema

+ +

Below you will find the current MTProto TL-schema. More details on TL »

+

See also the detailed schema in JSON »

+


+
int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+
+vector {t:Type} # [ t ] = Vector t;
+
+int128 4*[ int ] = Int128;
+int256 8*[ int ] = Int256;
+
+resPQ#05162463 nonce:int128 server_nonce:int128 pq:bytes server_public_key_fingerprints:Vector<long> = ResPQ;
+
+p_q_inner_data_dc#a9f55f95 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
+p_q_inner_data_temp_dc#56fddf88 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
+
+server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:bytes = Server_DH_Params;
+
+server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:bytes g_a:bytes server_time:int = Server_DH_inner_data;
+
+client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:bytes = Client_DH_Inner_Data;
+
+dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+
+bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
+
+rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
+rpc_error#2144ca19 error_code:int error_message:string = RpcError;
+
+rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
+rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
+rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
+
+future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
+future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
+
+pong#347773c5 msg_id:long ping_id:long = Pong;
+
+destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
+destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
+
+new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession;
+
+msg_container#73f1f8dc messages:vector<%Message> = MessageContainer;
+message msg_id:long seqno:int bytes:int body:Object = Message;
+msg_copy#e06046b2 orig_message:Message = MessageCopy;
+
+gzip_packed#3072cfa1 packed_data:bytes = Object;
+
+msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
+
+bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
+bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
+
+msg_resend_req#7d861a08 msg_ids:Vector<long> = MsgResendReq;
+msgs_state_req#da69fb52 msg_ids:Vector<long> = MsgsStateReq;
+msgs_state_info#04deb57d req_msg_id:long info:bytes = MsgsStateInfo;
+msgs_all_info#8cc0d131 msg_ids:Vector<long> info:bytes = MsgsAllInfo;
+msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
+
+destroy_auth_key_ok#f660e1d4 = DestroyAuthKeyRes;
+destroy_auth_key_none#0a9f2259 = DestroyAuthKeyRes;
+destroy_auth_key_fail#ea109b13 = DestroyAuthKeyRes;
+
+---functions---
+
+req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;
+
+req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:bytes q:bytes public_key_fingerprint:long encrypted_data:bytes = Server_DH_Params;
+
+set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:bytes = Set_client_DH_params_answer;
+
+rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
+get_future_salts#b921bd04 num:int = FutureSalts;
+ping#7abe77ec ping_id:long = Pong;
+ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
+destroy_session#e7512126 session_id:long = DestroySessionRes;
+
+http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
+
+destroy_auth_key#d1435160 = DestroyAuthKeyRes;
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/techfaq.html b/data/core.telegram.org/techfaq.html new file mode 100644 index 0000000000..a9aceb9a38 --- /dev/null +++ b/data/core.telegram.org/techfaq.html @@ -0,0 +1,333 @@ + + + + + FAQ for the Technically Inclined + + + + + + + + + + + + + +
+ +
+
+
+
+

FAQ for the Technically Inclined

+ +
+

This FAQ about MTProto is intended for advanced users. You may also want to check out our Basic FAQ.
Please note, that client developers are required to comply with the Security Guidelines.

+
+

+

General questions

+

Q: Why did you go for a custom protocol?

+

In order to achieve reliability on weak mobile connections as well as speed when dealing with large files (such as photos, large videos and files up to 2 GB each), MTProto uses an original approach. This document is intended to clarify certain details of our setup, as well as address some important points that might be overlooked at first glance.

+

Q: Where can I read more about the protocol?

+

Detailed protocol documentation is available here. Please note that MTProto supports two layers: client-server encryption that is used in Telegram cloud chats and end-to-end encryption that is used in Telegram Secret Chats. See below for more information.

+

If you have any comments, feel free to reach out to security@telegram.org

+

Q: How does server-client encryption work in MTProto?

+

Server-client encryption is used in Telegram Cloud Chats. Here's a brief overview of the setup:

+ + +
Note 1
+

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

+
    +
  • server salt (64-Bit)
  • +
  • session id
  • +
  • message sequence number
  • +
  • message length
  • +
  • time
  • +
+
Note 2
+

See additional comments on our use of IGE and message authentication.

+
Note 3
+

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above.

+

Q: How does end-to-end encryption work in MTProto?

+

End-to-end encryption is used in Telegram Secret Chats, as well as voice and video calls. You can read more about it here: Secret Chats, End-to-End encryption. Here's a brief overview of the setup:

+
+ +
+ +

Please see these articles for details:

+ +

Q: Why are you not using X? (insert solution)

+

While other ways of achieving the same cryptographic goals, undoubtedly, exist, we feel that the present solution is both robust and also sucсeeds at our secondary task of beating unencrypted messengers in terms of delivery time and stability.

+

Q: Why are you mostly relying on classical crypto algorithms?

+

We prefer to use well-known algorithms, created in the days when bandwidth and processing power were both a much rarer commodity. This has valuable side-effects for modern-day mobile development and sending large files, provided one takes care of the known drawbacks.

+

The weakspots of such algorithms are also well-known, and have been exploited for decades. We use these algorithms in such a combination that, to the best of our knowledge, prevents any known attacks.

+

Q: I'm a security expert and I have comments about your setup.

+

Any comments on Telegram's security are welcome at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $100 to $100,000 or more, depending on the severity of the issue.

+

Please note that we can not offer bounties for issues that are disclosed to the public before they are addressed.

+

Encryption

+

Q: How are MTProto messages authenticated?

+

All Telegram apps ensure that msg_key is equal to SHA-256 of a fragment of the auth_key concatenated with the decrypted message (including 12…1024 bytes of random padding). It is important that the plaintext always contains message length, server salt, session_id and other data not known to the attacker.

+

It is crucial that AES decryption keys depend both on msg_key, and on auth_key, known only to the parties involved in the exchange.

+

Q: Are you doing Encrypt-then-MAC, MAC-then-Encrypt or MAC-and-Encrypt?

+

We do none of the above, strictly speaking. For message authentication, we compute SHA-256(auth_key_fragment + AES_decrypt(…,encrypted_message)) upon message receipt and compare this value to the msg_key received with the encrypted message.

+
+

See also: Why not Encrypt-then-MAC?

+
+

Q: Why don't you go for a standard encrypt-then-MAC approach?

+

Using encrypt-then-MAC, e.g. involving GCM (Galois Counter Mode), would enable the receiving party to detect unauthorized or modified ciphertexts, thus eliminating the need to decrypt them in case of tampering.

+

In MTProto, the clients and the server authenticate messages by ensuring that SHA-256(auth_key_fragment + plaintext + padding) = msg_key and that the plaintext always contains message length, server salt, session_id and other data not known to a potential attacker before accepting any message. These security checks performed on the client before any message is accepted ensure that invalid or tampered with messages will always be safely (and silently) discarded.

+

This way we arrive at the same result. The difference is that the security check is performed before decryption in Encrypt-then-MAC and after decryption in MTProto – but in either case before a message is accepted. AES encryption / decryption on devices currently in use is comparable in speed with the additional HMAC computation required for the encrypt-then-MAC approach.

+

Q: Do you still use SHA-1?

+

The current version of the protocol is using SHA-256. MTProto 1.0 used to rely on SHA-1 (see this FAQ for details).

+

In MTProto 2.0, SHA-1 is used only where the choice of hash function is irrelevant for security, e.g.:

+ +

Q: Do you use IGE? IGE is broken!

+

Yes, we use IGE, but it is not broken in our implementation. The fact that we do not use IGE as MAC together with other properties of our system makes the known attacks on IGE irrelevant.

+

IGE, just as the ubiquitous CBC, is vulnerable to blockwise-adaptive CPA. But adaptive attacks are only a threat for as long as the same key can be used in several messages (not so in MTProto).

+

Adaptive attacks are even theoretically impossible in MTProto, because in order to be encrypted the message must be fully formed first, since the key is dependent on the message content. As for non-adaptive CPA, IGE is secure against them, as is CBC.

+

Authentication

+

Q: How is the server authenticated during DH key exchange?

+

The DH exchange is authenticated with the server's public RSA-key that is built into the client (the same RSA-key is also used for protection against MitM attacks).

+

Q: How are clients authenticated?

+

Various secrets (nonce, server_nonce, new_nonce) exchanged during key generation guarantee that the DH-key can only be obtained by the instance that initiated the exchange.

+

Notice that new_nonce is transferred explicitly only once, inside an RSA-encrypted message from the client to the server.

+

Q: How are Secret Chats authenticated?

+

Keys for end-to-end encrypted secret chats are generated by a new instance of DH key exchange, so they are known only to the parties involved and not to the server. To establish the identities of these parties and to ensure that no MitM is in place, it is recommended to compare identicons, generated from hashes of the DH secret chat keys (key visualizations).

+

Q: How are Voice Calls authenticated?

+

Keys for end-to-end encrypted calls are generated using the Diffie-Hellman key exchange. Users who are on a call can ensure that there is no MitM by comparing key visualizations.

+

To make key verification practical in the context of a voice call, Telegram uses a three-message modification of the standard DH key exchange for calls:

+
    +
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • +
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • +
  • A->B : (computes key (g_b)a, then) sends g_a := ga
  • +
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • +
+

The idea is that Alice commits to a specific value of a (and of g_a), but does not reveal g_a to Bob (or Eve) until the very last step. Bob has to choose his value of b and g_b without knowing the true value of g_a. If Eve is performing a Man-in-the-Middle attack, she cannot change a depending on the value of g_b received from Bob and she also can't tune her value of b depending on g_a. As a result, Eve only gets one shot at injecting her parameters — and she must fire this shot with her eyes closed.

+

Thanks to this modification, it becomes possible to prevent eavesdropping (MitM attacks on DH) with a probability of more than 0.9999999999 by using just over 33 bits of entropy in the visualization. These bits are presented to the users in the form of four emoticons. We have selected a pool of 333 emoji that all look quite different from one another and can be easily described in simple words in any language.

+

You can read more about key verification for Telegram calls here.

+

Q: Do you have Forward Secrecy?

+

Telegram's Secret chats support Perfect Forward Secrecy, you can read more about it here.

+

Protection against known attacks

+

Known-Plaintext Attacks

+

By definition, the known-plaintext attack (KPA) is an attack model for cryptanalysis where the attacker has samples of both the plaintext, and its encrypted version (ciphertext).

+

AES IGE that is used in MTProto is robust against KPA attacks (see this, if you wonder how one can securely use IGE). On top of that, the plaintext in MTProto always contains server_salt and session id.

+

Chosen-Plaintext Attacks

+

By definition, a chosen-plaintext attack (CPA) is an attack model for cryptanalysis which presumes that the attacker has the capability to choose arbitrary plaintexts to be encrypted and obtain the corresponding ciphertexts.

+

MTProto uses AES in IGE mode (see this, if you wonder how one can securely use IGE) that is secure against non-adaptive CPAs. IGE is known to be not secure against blockwise-adaptive CPA, but MTProto fixes this in the following manner:

+

Each plaintext message to be encrypted always contains the following to be checked upon decryption:

+
    +
  • server salt (64-Bit)
  • +
  • message sequence number
  • +
  • time
  • +
+

On top of this, in order to replace the plaintext, you would also need to use the right AES key and iv, both dependent on the auth_key. This makes MTProto robust against a CPA.

+

Chosen-Ciphertext Attacks

+

By definition, a chosen-ciphertext attack (CCA) is an attack model for cryptanalysis in which the cryptanalyst gathers information, at least in part, by choosing a ciphertext and obtaining its decryption under an unknown key. In the attack, an adversary has a chance to enter one or more known ciphertexts into the system and obtain the resulting plaintexts. From these pieces of information the adversary can attempt to recover the hidden secret key used for decryption.

+

Each time a message is decrypted in MTProto, a check is performed to see whether msg_key is equal to the SHA-256 of a fragment of the auth_key concatenated with the decrypted message (including 12…1024 bytes of random padding). The plaintext (decrypted data) also always contains message length, server salt and sequence number. This negates known CCAs.

+

What about IND-CCA?

+

MTProto 2.0 satisfies the conditions for indistinguishability under chosen ciphertext attack (IND-CCA).

+
+

Read more about IND-CCA in MTProto 1.0

+
+

Replay attacks

+

Replay attacks are denied because each plaintext to be encrypted contains the server salt and the unique message id and sequence number.

+

This means that each message can only be sent once.

+

Man-in-the-middle attacks

+

Telegram has two modes of communication — ordinary chats using client-server encryption and Secret Chats using end-to-end encryption.

+

Client-Server communication is protected from MiTM-attacks during DH key generation by means of a server RSA public key embedded into client software. After that, if both clients trust the server software, the Secret Chats between them are protected by the server from MiTM attacks.

+

The interface offers a way of comparing Secret Chat keys for users who do not trust the server. Visualizations of the key are presented in the form of identicons (example here). By comparing key visualizations users can make sure no MITM attack had taken place.

+

Hash collisions for Diffie-Hellman Keys

+

Currently, the fingerprint uses 128-bits of SHA-1 concatenated with 160 bits from the SHA-256 of the key, yielding a total of 288 fingerprint bits, thus negating the possibility of hash-collision attacks.

+
+

Read more about fingerprints in earlier versions of Telegram

+
+

Length extension attacks

+

By definition, length extension attacks are a type of attack when certain types of hashes are misused as message authentication codes, allowing for inclusion of extra information.

+

A message in MTProto consists of an msg_key, equal to the SHA-256 of a fragment of the auth_key concatenated with the plaintext (including 12…1024 bytes of random padding and some additional parameters), followed by the ciphertext. The attacker cannot append extra bytes to the end and recompute the SHA-256, since the SHA-256 is computed from the plaintext, not the ciphertext, and the attacker has no way to obtain the ciphertext corresponding to the extra plaintext bytes she may want to add.

+

Apart from that, changing the msg_key would also change the AES decryption key for the message in a way unpredictable for the attacker, so even the original prefix would decrypt to garbage — which would be immediately detected since the app performs a security check to ensure that the SHA-256 of the plaintext (combined with a fragment of the auth_key) matches the msg_key received.

+

Encrypted CDNs

+

As of Telegram 4.2, we support encrypted CDNs for caching media from public channels with over 100.000 members. The CDN caching nodes are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

+
+

For technical details of the implementation, encryption and verification of data, see the CDN manual.

+
+

See this document for a Persian version of this FAQ.
بخش فارسی

+

Q: Why did you decide to use CDNs?

+

We use our own distributed servers to speed up downloads in regions where freedom of speech is guaranteed — and even there we don't take this for granted. But when Telegram becomes immensely popular in other areas, we can only rely on CDNs which we treat rather like ISPs from the technical standpoint in that they only get encrypted data they can't decipher.

+

Thanks to this technology, the download speed for public photos and videos can become significantly higher in regions like Turkey, Indonesia, South America, India, Iran or Iraq without the slightest compromise in security.

+

Q: Can the CDN decipher the files?

+

No. Each file that is to be sent to the CDN is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

+

Q: Can the CDN substitute the data with their own version?

+

No. Data downloaded from CDN caching nodes is always verified by the receiving Telegram app by way of a hash: attackers won’t be able to replace any files with their own versions.

+

Q: Can the CDN delete any files?

+

No. CDN nodes only cache encrypted copies of files, originals are stored on the Telegram servers. The user is notified about receiving the file by the Telegram server. If the CDN caching node doesn't give the file to the user, the user will receive the file from the Telegram server directly.

+

Q: Can CDNs be used for censorship?

+

No. All original files are stored on the Telegram servers. The CDNs only get encrypted data — and they can't decipher it. They can't substitute any data. And in case of any problems with the CDN, the file will be simply delivered to the users directly from the Telegram servers. Users will always get their data, nobody can stop this.

+

Q: Can I verify this?

+

Yes. Anyone can verify our CDN implementation by checking the source code of Telegram apps and inspecting traffic.

+

Q: Does this affect private data?

+

No. The CDN caching nodes are not a part of the Telegram cloud. CDN caching nodes are used only for caching popular public media from massive channels. Private data never goes there.

+

Q: Is this connected with government requests to move private data to their territory?

+

No. We haven't entered in any agreements with any government regarding the CDNs and the CDNs are not part of any deal. The only purpose of CDNs is to securely improve connectivity in high demand regions where Telegram can't place its servers.

+

Q: Does this give some countries any influence over Telegram?

+

No. We have taken special precautions to make sure that no country gains any leverage over Telegram by way of the CDN caching nodes:

+
    +
  • The CDNs do not belong to Telegram – all the risks are on a third-party company that supplies us with CDN nodes around the world.
  • +
  • We did not invest anything in these CDNs and will only be paying for traffic that is used to pass cached items from our main clusters and to the end users.
  • +
+

As the result, if any country decides to mess with the CDN in their region, they gain nothing except for reducing connectivity for their own citizens – and Telegram loses nothing of value.

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/AccountDaysTTL.html b/data/core.telegram.org/type/AccountDaysTTL.html new file mode 100644 index 0000000000..de81618068 --- /dev/null +++ b/data/core.telegram.org/type/AccountDaysTTL.html @@ -0,0 +1,162 @@ + + + + + AccountDaysTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

AccountDaysTTL

+ +

Time-to-live of current account

+

+ +
+
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
+
+---functions---
+
+account.getAccountTTL#8fc711d = AccountDaysTTL;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
accountDaysTTLTime to live in days of the current account
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAccountTTLGet days to live of account
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/BankCardOpenUrl.html b/data/core.telegram.org/type/BankCardOpenUrl.html new file mode 100644 index 0000000000..054636976f --- /dev/null +++ b/data/core.telegram.org/type/BankCardOpenUrl.html @@ -0,0 +1,143 @@ + + + + + BankCardOpenUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

BankCardOpenUrl

+ +

Credit card info URL provided by the bank

+

+ +
+
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
bankCardOpenUrlCredit card info URL provided by the bank
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Bool.html b/data/core.telegram.org/type/Bool.html new file mode 100644 index 0000000000..0f2612e8b6 --- /dev/null +++ b/data/core.telegram.org/type/Bool.html @@ -0,0 +1,718 @@ + + + + + Bool + + + + + + + + + + + + + +
+ +
+
+
+ +

Bool

+ +

Boolean type.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+---functions---
+
+auth.logOut#5717da40 = Bool;
+auth.resetAuthorizations#9fab0d1a = Bool;
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
+auth.checkRecoveryPassword#d36bf79 code:string = Bool;
+
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
+account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
+account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
+account.resetNotifySettings#db7e1747 = Bool;
+account.updateStatus#6628562c offline:Bool = Bool;
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
+account.checkUsername#2714d86c username:string = Bool;
+account.deleteAccount#418d4e0b reason:string = Bool;
+account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
+account.updateDeviceLocked#38df3532 period:int = Bool;
+account.resetAuthorization#df77f3bc hash:long = Bool;
+account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
+account.resetWebAuthorization#2d01b9ef hash:long = Bool;
+account.resetWebAuthorizations#682d2594 = Bool;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
+account.confirmPasswordEmail#8fdf1920 code:string = Bool;
+account.resendPasswordEmail#7a7f2a15 = Bool;
+account.cancelPasswordEmail#c1cbd5b6 = Bool;
+account.getContactSignUpNotification#9f07c728 = Bool;
+account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
+account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
+account.resetWallPapers#bb3b9804 = Bool;
+account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
+account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
+account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
+account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
+account.declinePasswordReset#4c9409f6 = Bool;
+
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
+contacts.block#68cc1411 id:InputPeer = Bool;
+contacts.unblock#bea65d50 id:InputPeer = Bool;
+contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
+contacts.resetSaved#879537f1 = Bool;
+contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
+
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
+messages.reportSpam#cf1592db peer:InputPeer = Bool;
+messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
+messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
+messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
+messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
+messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
+messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
+messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
+messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
+messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
+messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
+messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
+messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
+messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
+messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
+messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
+messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
+messages.clearAllDrafts#7e58ee9c = Bool;
+messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
+messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
+messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
+messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
+messages.deleteChat#5bd0ee50 chat_id:long = Bool;
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
+messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+
+channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
+channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
+channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
+channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
+channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
+channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
+channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
+channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
+
+help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
+help.hidePromoData#1e251c95 peer:InputPeer = Bool;
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+
+bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
+bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
+
+payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
+
+phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
+phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
+phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
+phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
+
+users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
+
+stickers.checkShortName#284b3639 short_name:string = Bool;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
boolFalseConstructor may be interpreted as a booleanfalse value.
boolTrueThe constructor can be interpreted as a booleantrue value.
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
auth.logOutLogs out the user.
auth.resetAuthorizationsTerminates 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
auth.bindTempAuthKeyBinds 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.
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
account.updateStatusUpdates online user status.
account.reportPeerReport a peer for violation of telegram's Terms of Service
contacts.deleteByPhonesDelete contacts by phone number
contacts.blockAdds the user to the blacklist.
contacts.unblockDeletes the user from the blacklist.
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportReport a message in a chat for violation of telegram's Terms of Service
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.reportEncryptedSpamReport a secret chat for spam
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
account.checkUsernameValidates a username and checks availability.
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.setAccountTTLSet account self-destruction period
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.resetAuthorizationLog out an active authorized session by it hash
account.updatePasswordSettingsSet a new 2FA password
messages.uninstallStickerSetUninstall a stickerset
channels.readHistoryMark channel/supergroup history as read
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
messages.editChatAdminMake a user admin in a legacy group.
messages.reorderStickerSetsReorder installed stickersets
messages.saveGifAdd GIF to saved gifs list
messages.setInlineBotResultsAnswer an inline query, for bots only
auth.cancelCodeCancel the login verification code
messages.editInlineBotMessageEdit an inline bot message
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
contacts.resetTopPeerRatingReset rating of top peer
messages.saveDraftSave a message draft associated to a chat.
messages.readFeaturedStickersMark new featured stickers as read
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.clearRecentStickersClear recent stickers
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
payments.clearSavedInfoClear saved payment information
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery 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.
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.saveCallDebugSend phone call debug data to server
channels.setStickersAssociate a stickerset to the supergroup
messages.faveStickerMark a sticker as favorite
channels.readMessageContentsMark channel/supergroup message contents as read
contacts.resetSavedDelete saved contacts
channels.deleteHistoryDelete the history of a supergroup
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
help.acceptTermsOfServiceAccept the new terms of service
account.deleteSecureValueDelete stored telegram passport value
users.setSecureValueErrorsSet secure passport value errors for a user
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.verifyPhoneVerify a phone number for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.finishTakeoutSessionFinish account takeout session
messages.markDialogUnreadManually mark dialog as unread
contacts.toggleTopPeersEnable/disable top peers
messages.clearAllDraftsClear all drafts.
help.saveAppLogSaves logs of application on the server.
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
messages.editChatAboutEdit the description of a group/supergroup/channel.
account.saveWallPaperInstall/uninstall wallpaper
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveAutoDownloadSettingsChange media autodownload settings
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
channels.editLocationEdit location of geogroup
account.saveThemeSave a theme
account.installThemeInstall a theme
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
messages.toggleStickerSetsApply changes to multiple stickersets
messages.updateDialogFilterUpdate folder
messages.updateDialogFiltersOrderReorder folders
bots.setBotCommandsSet bot command list
help.hidePromoDataHide MTProxy/Public Service Announcement information
phone.sendSignalingDataSend VoIP signaling data
help.dismissSuggestionDismiss a suggestion
messages.readDiscussionMark a channel discussion as read
messages.deleteChatDelete a chat
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteExportedChatInviteDelete a chat invite
account.reportProfilePhotoReport a profile photo of a dialog
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
stickers.checkShortNameCheck whether the given short name is available
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
account.declinePasswordResetAbort a pending 2FA password reset
auth.checkRecoveryPasswordCheck if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
channels.viewSponsoredMessageMark a specific sponsored message as read
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/CdnPublicKey.html b/data/core.telegram.org/type/CdnPublicKey.html new file mode 100644 index 0000000000..6ccb82085f --- /dev/null +++ b/data/core.telegram.org/type/CdnPublicKey.html @@ -0,0 +1,145 @@ + + + + + CdnPublicKey + + + + + + + + + + + + + +
+ +
+
+
+ +

CdnPublicKey

+ +

Public key to use only during handshakes to CDN DCs.

+

+ +
+
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
cdnPublicKeyPublic key to use only during handshakes to CDN DCs.
+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html b/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html new file mode 100644 index 0000000000..64712a8d68 --- /dev/null +++ b/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html @@ -0,0 +1,143 @@ + + + + + ChannelAdminLogEventsFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelAdminLogEventsFilter

+ +

Filter for fetching events in the channel admin log

+

+ +
+
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channelAdminLogEventsFilterFilter only certain admin log events
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChannelParticipant.html b/data/core.telegram.org/type/ChannelParticipant.html new file mode 100644 index 0000000000..d2274b1ba4 --- /dev/null +++ b/data/core.telegram.org/type/ChannelParticipant.html @@ -0,0 +1,168 @@ + + + + + ChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelParticipant

+ +

Channel participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
+channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;
+channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
+channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
+channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelParticipantChannel/supergroup participant
channelParticipantSelfMyself
channelParticipantCreatorChannel/supergroup creator
channelParticipantAdminAdmin
channelParticipantBannedBanned/kicked user
channelParticipantLeftA participant that left the channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ChatOnlines.html b/data/core.telegram.org/type/ChatOnlines.html new file mode 100644 index 0000000000..9280a09df5 --- /dev/null +++ b/data/core.telegram.org/type/ChatOnlines.html @@ -0,0 +1,162 @@ + + + + + ChatOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatOnlines

+ +

Number of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;
+
+---functions---
+
+messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatOnlinesNumber of online users in a chat
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getOnlinesGet count of online users in a chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedDataBlock.html b/data/core.telegram.org/type/DecryptedDataBlock.html new file mode 100644 index 0000000000..1ce54fed4a --- /dev/null +++ b/data/core.telegram.org/type/DecryptedDataBlock.html @@ -0,0 +1,128 @@ + + + + + DecryptedDataBlock + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedDataBlock

+ +

VoIP decrypted data block

+

+ +
+
Type schema is not available in the selected layer.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DecryptedMessage.html b/data/core.telegram.org/type/DecryptedMessage.html new file mode 100644 index 0000000000..44487a5b19 --- /dev/null +++ b/data/core.telegram.org/type/DecryptedMessage.html @@ -0,0 +1,140 @@ + + + + + DecryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

DecryptedMessage

+ +

Object describes the contents of an encrypted message.

+

+ +
+
===8===
+decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+===17===
+decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
+
+===45===
+decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
+
+===73===
+decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Dialog.html b/data/core.telegram.org/type/Dialog.html new file mode 100644 index 0000000000..0343ee4052 --- /dev/null +++ b/data/core.telegram.org/type/Dialog.html @@ -0,0 +1,148 @@ + + + + + Dialog + + + + + + + + + + + + + +
+ +
+
+
+ +

Dialog

+ +

Chat info.

+

+ +
+
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
+dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
dialogChat
dialogFolderDialog in folder
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DisabledFeature.html b/data/core.telegram.org/type/DisabledFeature.html new file mode 100644 index 0000000000..5cff87c98c --- /dev/null +++ b/data/core.telegram.org/type/DisabledFeature.html @@ -0,0 +1,128 @@ + + + + + DisabledFeature + + + + + + + + + + + + + +
+ +
+
+
+ +

DisabledFeature

+ +

A disabled feature

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Document.html b/data/core.telegram.org/type/Document.html new file mode 100644 index 0000000000..5a922e2dfa --- /dev/null +++ b/data/core.telegram.org/type/Document.html @@ -0,0 +1,173 @@ + + + + + Document + + + + + + + + + + + + + +
+ +
+
+
+ +

Document

+ +

A document.

+

+ +
+
documentEmpty#36f8c871 id:long = Document;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+---functions---
+
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
+
+account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
documentEmptyEmpty constructor, document doesn't exist.
documentDocument
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
account.uploadThemeUpload theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/DocumentAttribute.html b/data/core.telegram.org/type/DocumentAttribute.html new file mode 100644 index 0000000000..3c8f4eb2bc --- /dev/null +++ b/data/core.telegram.org/type/DocumentAttribute.html @@ -0,0 +1,173 @@ + + + + + DocumentAttribute + + + + + + + + + + + + + +
+ +
+
+
+ +

DocumentAttribute

+ +

Various possible attributes of a document (used to define if it's a sticker, a GIF, a video, a mask sticker, an image, an audio, and so on)

+

+ +
+
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
+documentAttributeAnimated#11b58939 = DocumentAttribute;
+documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
+documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
+documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
+documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
+documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
documentAttributeImageSizeDefines the width and height of an image uploaded as document
documentAttributeAnimatedDefines an animated GIF
documentAttributeStickerDefines a sticker
documentAttributeVideoDefines a video
documentAttributeAudioRepresents an audio file
documentAttributeFilenameA simple document with a file name
documentAttributeHasStickersWhether the current document has stickers attached
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EmojiKeyword.html b/data/core.telegram.org/type/EmojiKeyword.html new file mode 100644 index 0000000000..b9a0b64f8a --- /dev/null +++ b/data/core.telegram.org/type/EmojiKeyword.html @@ -0,0 +1,148 @@ + + + + + EmojiKeyword + + + + + + + + + + + + + +
+ +
+
+
+ +

EmojiKeyword

+ +

Emoji keyword

+

+ +
+
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
+emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
emojiKeywordEmoji keyword
emojiKeywordDeletedDeleted emoji keyword
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EncryptedChat.html b/data/core.telegram.org/type/EncryptedChat.html new file mode 100644 index 0000000000..b7d67a122f --- /dev/null +++ b/data/core.telegram.org/type/EncryptedChat.html @@ -0,0 +1,187 @@ + + + + + EncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedChat

+ +

Object contains info on an encrypted chat.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+---functions---
+
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedChatEmptyEmpty constructor.
encryptedChatWaitingChat waiting for approval of second participant.
encryptedChatRequestedRequest to create an encrypted chat.
encryptedChatEncrypted chat
encryptedChatDiscardedDiscarded or deleted chat.
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.acceptEncryptionConfirms creation of a secret chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EncryptedFile.html b/data/core.telegram.org/type/EncryptedFile.html new file mode 100644 index 0000000000..461b6767b2 --- /dev/null +++ b/data/core.telegram.org/type/EncryptedFile.html @@ -0,0 +1,167 @@ + + + + + EncryptedFile + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedFile

+ +

Seta an encrypted file.

+

+ +
+
encryptedFileEmpty#c21f497e = EncryptedFile;
+encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
+
+---functions---
+
+messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedFileEmptyEmpty constructor, unexisitng file.
encryptedFileEncrypted file.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/EncryptedMessage.html b/data/core.telegram.org/type/EncryptedMessage.html new file mode 100644 index 0000000000..0096c27c9a --- /dev/null +++ b/data/core.telegram.org/type/EncryptedMessage.html @@ -0,0 +1,148 @@ + + + + + EncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedMessage

+ +

Object contains encrypted message.

+

+ +
+
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedMessageEncrypted message.
encryptedMessageServiceEncrypted service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ExportedMessageLink.html b/data/core.telegram.org/type/ExportedMessageLink.html new file mode 100644 index 0000000000..cd7f496ad9 --- /dev/null +++ b/data/core.telegram.org/type/ExportedMessageLink.html @@ -0,0 +1,162 @@ + + + + + ExportedMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

ExportedMessageLink

+ +

HTTP link and embed info of channel message

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+
+---functions---
+
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
exportedMessageLinkLink to a message in a supergroup/channel
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/FileHash.html b/data/core.telegram.org/type/FileHash.html new file mode 100644 index 0000000000..528661d09d --- /dev/null +++ b/data/core.telegram.org/type/FileHash.html @@ -0,0 +1,143 @@ + + + + + FileHash + + + + + + + + + + + + + +
+ +
+
+
+ +

FileHash

+ +

Hash of an uploaded file, to be checked for validity after download

+

+ +
+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
fileHashSHA256 Hash of an uploaded file, to be checked for validity after download
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Game.html b/data/core.telegram.org/type/Game.html new file mode 100644 index 0000000000..dcba7cddad --- /dev/null +++ b/data/core.telegram.org/type/Game.html @@ -0,0 +1,143 @@ + + + + + Game + + + + + + + + + + + + + +
+ +
+
+
+ +

Game

+ +

Indicates an already sent game

+

+ +
+
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
gameIndicates an already sent game
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GeoPoint.html b/data/core.telegram.org/type/GeoPoint.html new file mode 100644 index 0000000000..3011f0e13c --- /dev/null +++ b/data/core.telegram.org/type/GeoPoint.html @@ -0,0 +1,148 @@ + + + + + GeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

GeoPoint

+ +

Object defines a GeoPoint.

+

+ +
+
geoPointEmpty#1117dd5f = GeoPoint;
+geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
geoPointEmptyEmpty constructor.
geoPointGeoPoint.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCall.html b/data/core.telegram.org/type/GroupCall.html new file mode 100644 index 0000000000..13f1d9cf8b --- /dev/null +++ b/data/core.telegram.org/type/GroupCall.html @@ -0,0 +1,148 @@ + + + + + GroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCall

+ +

A group call

+

+ +
+
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
groupCallDiscardedAn ended group call
groupCallInfo about a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCallParticipant.html b/data/core.telegram.org/type/GroupCallParticipant.html new file mode 100644 index 0000000000..b8d2891a5c --- /dev/null +++ b/data/core.telegram.org/type/GroupCallParticipant.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipant

+ +

Info about a group call participant

+

+ +
+
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantInfo about a group call participant
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/GroupCallParticipantVideo.html b/data/core.telegram.org/type/GroupCallParticipantVideo.html new file mode 100644 index 0000000000..d39d5ab6df --- /dev/null +++ b/data/core.telegram.org/type/GroupCallParticipantVideo.html @@ -0,0 +1,143 @@ + + + + + GroupCallParticipantVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCallParticipantVideo

+ +

Info about a video stream

+

+ +
+
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
groupCallParticipantVideoInfo about a video stream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputEncryptedChat.html b/data/core.telegram.org/type/InputEncryptedChat.html new file mode 100644 index 0000000000..f8a4ee9fd3 --- /dev/null +++ b/data/core.telegram.org/type/InputEncryptedChat.html @@ -0,0 +1,143 @@ + + + + + InputEncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

InputEncryptedChat

+ +

Object sets an encrypted chat ID.

+

+ +
+
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputEncryptedChatCreates an encrypted chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputGeoPoint.html b/data/core.telegram.org/type/InputGeoPoint.html new file mode 100644 index 0000000000..7cd476bd42 --- /dev/null +++ b/data/core.telegram.org/type/InputGeoPoint.html @@ -0,0 +1,148 @@ + + + + + InputGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGeoPoint

+ +

Defines a GeoPoint.

+

+ +
+
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputGeoPointEmptyEmpty GeoPoint constructor.
inputGeoPointDefines a GeoPoint by its coordinates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputMedia.html b/data/core.telegram.org/type/InputMedia.html new file mode 100644 index 0000000000..048a3c1d2b --- /dev/null +++ b/data/core.telegram.org/type/InputMedia.html @@ -0,0 +1,213 @@ + + + + + InputMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputMedia

+ +

Defines media content of a message.

+

+ +
+
inputMediaEmpty#9664f57f = InputMedia;
+inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
+inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
+inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
+inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
+inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
+inputMediaGame#d33f43f3 id:InputGame = InputMedia;
+inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
+inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+inputMediaDice#e66fbf7b emoticon:string = InputMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputMediaEmptyEmpty media content of a message.
inputMediaUploadedPhotoPhoto
inputMediaPhotoForwarded photo
inputMediaGeoPointMap.
inputMediaContactPhonebook contact
inputMediaUploadedDocumentNew document
inputMediaDocumentForwarded document
inputMediaVenueCan be used to send a venue geolocation.
inputMediaPhotoExternalNew photo that will be uploaded by the server using the specified URL
inputMediaDocumentExternalDocument that will be downloaded by the telegram servers
inputMediaGameA game
inputMediaInvoiceGenerated invoice of a bot payment
inputMediaGeoLiveLive geographical location
inputMediaPollA poll
inputMediaDiceSend a dice in the chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPeer.html b/data/core.telegram.org/type/InputPeer.html new file mode 100644 index 0000000000..4ab7b227c0 --- /dev/null +++ b/data/core.telegram.org/type/InputPeer.html @@ -0,0 +1,173 @@ + + + + + InputPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeer

+ +

Peer

+

+ +
+
inputPeerEmpty#7f3b18ea = InputPeer;
+inputPeerSelf#7da07ec9 = InputPeer;
+inputPeerChat#35a95cb9 chat_id:long = InputPeer;
+inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
+inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
+inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
+inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputPeerEmptyAn empty constructor, no user or chat is defined.
inputPeerSelfDefines the current user.
inputPeerChatDefines a chat for further interaction.
inputPeerUserDefines a user for further interaction.
inputPeerChannelDefines a channel for further interaction.
inputPeerUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
inputPeerChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/InputPeerNotifySettings.html b/data/core.telegram.org/type/InputPeerNotifySettings.html new file mode 100644 index 0000000000..8d9d1ca7d9 --- /dev/null +++ b/data/core.telegram.org/type/InputPeerNotifySettings.html @@ -0,0 +1,143 @@ + + + + + InputPeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeerNotifySettings

+ +

Notifications settings.

+

+ +
+
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPeerNotifySettingsNotification settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/LangPackLanguage.html b/data/core.telegram.org/type/LangPackLanguage.html new file mode 100644 index 0000000000..29ef8513d7 --- /dev/null +++ b/data/core.telegram.org/type/LangPackLanguage.html @@ -0,0 +1,162 @@ + + + + + LangPackLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackLanguage

+ +

Language pack language

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+
+---functions---
+
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
langPackLanguageIdentifies a localization pack
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
langpack.getLanguageGet information about a language in a localization pack
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MaskCoords.html b/data/core.telegram.org/type/MaskCoords.html new file mode 100644 index 0000000000..fa939dec50 --- /dev/null +++ b/data/core.telegram.org/type/MaskCoords.html @@ -0,0 +1,143 @@ + + + + + MaskCoords + + + + + + + + + + + + + +
+ +
+
+
+ +

MaskCoords

+ +

Mask coordinates (if this is a mask sticker, attached to a photo)

+

+ +
+
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
maskCoordsPosition 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
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageAction.html b/data/core.telegram.org/type/MessageAction.html new file mode 100644 index 0000000000..0df8432505 --- /dev/null +++ b/data/core.telegram.org/type/MessageAction.html @@ -0,0 +1,283 @@ + + + + + MessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageAction

+ +

Object describing actions connected to a service message.

+

+ +
+
messageActionEmpty#b6aef7b0 = MessageAction;
+messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
+messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
+messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
+messageActionChatDeletePhoto#95e3fbef = MessageAction;
+messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
+messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
+messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
+messageActionChannelCreate#95d2ac92 title:string = MessageAction;
+messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
+messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
+messageActionPinMessage#94bd38ed = MessageAction;
+messageActionHistoryClear#9fbab604 = MessageAction;
+messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
+messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
+messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
+messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
+messageActionScreenshotTaken#4792929b = MessageAction;
+messageActionCustomAction#fae69f56 message:string = MessageAction;
+messageActionBotAllowed#abe9affe domain:string = MessageAction;
+messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
+messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
+messageActionContactSignUp#f3f25f76 = MessageAction;
+messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
+messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
+messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
+messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
+messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
+messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageActionEmptyEmpty constructor.
messageActionChatCreateGroup created
messageActionChatEditTitleGroup name changed.
messageActionChatEditPhotoGroup profile changed
messageActionChatDeletePhotoGroup profile photo removed.
messageActionChatAddUserNew member in the group
messageActionChatDeleteUserUser left the group.
messageActionChatJoinedByLinkA user joined the chat via an invite link
messageActionChannelCreateThe channel was created
messageActionChatMigrateToIndicates the chat was migrated to the specified supergroup
messageActionChannelMigrateFromIndicates the channel was migrated from the specified chat
messageActionPinMessageA message was pinned
messageActionHistoryClearChat history was cleared
messageActionGameScoreSomeone scored in a game
messageActionPaymentSentMeA user just sent a payment to me (a bot)
messageActionPaymentSentA payment was sent
messageActionPhoneCallA phone call
messageActionScreenshotTakenA screenshot of the chat was taken
messageActionCustomActionCustom action (most likely not supported by the current layer, an upgrade might be needed)
messageActionBotAllowedThe domain name of the website on which the user has logged in. More about Telegram Login »
messageActionSecureValuesSentMeSecure telegram passport values were received
messageActionSecureValuesSentRequest for secure telegram passport values was sent
messageActionContactSignUpA contact just signed up to telegram
messageActionGeoProximityReachedWe are now in proximity of this user (triggered by the other user, by sending a live geolocation with the proximity_notification_radius flag)
messageActionGroupCallThe group call has ended
messageActionInviteToGroupCallA set of users was invited to the group call
messageActionSetMessagesTTLYou changed the Time-To-Live of your messages in this chat.
messageActionGroupCallScheduledA group call was scheduled
messageActionSetChatThemeThe chat theme was changed
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageInteractionCounters.html b/data/core.telegram.org/type/MessageInteractionCounters.html new file mode 100644 index 0000000000..e5aa85ea07 --- /dev/null +++ b/data/core.telegram.org/type/MessageInteractionCounters.html @@ -0,0 +1,143 @@ + + + + + MessageInteractionCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageInteractionCounters

+ +

Message interaction counters

+

+ +
+
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageInteractionCountersMessage interaction counters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageMedia.html b/data/core.telegram.org/type/MessageMedia.html new file mode 100644 index 0000000000..d69390ddf4 --- /dev/null +++ b/data/core.telegram.org/type/MessageMedia.html @@ -0,0 +1,232 @@ + + + + + MessageMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageMedia

+ +

Media

+

+ +
+
messageMediaEmpty#3ded6320 = MessageMedia;
+messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
+messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
+messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
+messageMediaUnsupported#9f84f49e = MessageMedia;
+messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
+messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
+messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
+messageMediaGame#fdb19008 game:Game = MessageMedia;
+messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
+messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
+
+---functions---
+
+messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageMediaEmptyEmpty constructor.
messageMediaPhotoAttached photo.
messageMediaGeoAttached map.
messageMediaContactAttached contact.
messageMediaUnsupportedCurrent version of the client does not support this media type.
messageMediaDocumentDocument (video, audio, voice, sticker, any media type except photo)
messageMediaWebPagePreview of webpage
messageMediaVenueVenue
messageMediaGameTelegram game
messageMediaInvoiceInvoice
messageMediaGeoLiveIndicates a live geolocation
messageMediaPollPoll
messageMediaDiceDice
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getWebPagePreviewGet preview of webpage
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.uploadImportedMediaUpload a media file associated with an imported chat.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/MessageUserVote.html b/data/core.telegram.org/type/MessageUserVote.html new file mode 100644 index 0000000000..0b040a9e46 --- /dev/null +++ b/data/core.telegram.org/type/MessageUserVote.html @@ -0,0 +1,153 @@ + + + + + MessageUserVote + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageUserVote

+ +

How a user voted in a poll

+

+ +
+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageUserVoteUser ID
messageUserVoteInputOptionHow a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)
messageUserVoteMultipleHow a user voted in a multiple-choice poll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/NearestDc.html b/data/core.telegram.org/type/NearestDc.html new file mode 100644 index 0000000000..b39d7f7256 --- /dev/null +++ b/data/core.telegram.org/type/NearestDc.html @@ -0,0 +1,162 @@ + + + + + NearestDc + + + + + + + + + + + + + +
+ +
+
+
+ +

NearestDc

+ +

Object contains info on nearest data centre.

+

+ +
+
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+
+---functions---
+
+help.getNearestDc#1fb33026 = NearestDc;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
nearestDcNearest data centre, according to geo-ip.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getNearestDcReturns info on data centre nearest to the user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PageCaption.html b/data/core.telegram.org/type/PageCaption.html new file mode 100644 index 0000000000..a90dd9e022 --- /dev/null +++ b/data/core.telegram.org/type/PageCaption.html @@ -0,0 +1,143 @@ + + + + + PageCaption + + + + + + + + + + + + + +
+ +
+
+
+ +

PageCaption

+ +

Page caption

+

+ +
+
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageCaptionPage caption
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PaymentSavedCredentials.html b/data/core.telegram.org/type/PaymentSavedCredentials.html new file mode 100644 index 0000000000..05f6211577 --- /dev/null +++ b/data/core.telegram.org/type/PaymentSavedCredentials.html @@ -0,0 +1,143 @@ + + + + + PaymentSavedCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentSavedCredentials

+ +

Saved payment credentials

+

+ +
+
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentSavedCredentialsCardSaved credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Peer.html b/data/core.telegram.org/type/Peer.html new file mode 100644 index 0000000000..6ba68784c5 --- /dev/null +++ b/data/core.telegram.org/type/Peer.html @@ -0,0 +1,153 @@ + + + + + Peer + + + + + + + + + + + + + +
+ +
+
+
+ +

Peer

+ +

Chat partner or group.

+

+ +
+
peerUser#59511722 user_id:long = Peer;
+peerChat#36c6019a chat_id:long = Peer;
+peerChannel#a2a5371e channel_id:long = Peer;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
peerUserChat partner
peerChatGroup.
peerChannelChannel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneCall.html b/data/core.telegram.org/type/PhoneCall.html new file mode 100644 index 0000000000..52b4674580 --- /dev/null +++ b/data/core.telegram.org/type/PhoneCall.html @@ -0,0 +1,168 @@ + + + + + PhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCall

+ +

Phone call

+

+ +
+
phoneCallEmpty#5366c915 id:long = PhoneCall;
+phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
+phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneCallEmptyEmpty constructor
phoneCallWaitingIncoming phone call
phoneCallRequestedRequested phone call
phoneCallAcceptedAn accepted phone call
phoneCallPhone call
phoneCallDiscardedIndicates a discarded phone call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneCallDiscardReason.html b/data/core.telegram.org/type/PhoneCallDiscardReason.html new file mode 100644 index 0000000000..bdb3fea497 --- /dev/null +++ b/data/core.telegram.org/type/PhoneCallDiscardReason.html @@ -0,0 +1,158 @@ + + + + + PhoneCallDiscardReason + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCallDiscardReason

+ +

Why was the phone call discarded?

+

+ +
+
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
+phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
+phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
+phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneCallDiscardReasonMissedThe phone call was missed
phoneCallDiscardReasonDisconnectThe phone call was disconnected
phoneCallDiscardReasonHangupThe phone call was ended normally
phoneCallDiscardReasonBusyThe phone call was discared because the user is busy in another call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PhoneCallProtocol.html b/data/core.telegram.org/type/PhoneCallProtocol.html new file mode 100644 index 0000000000..1930d6420d --- /dev/null +++ b/data/core.telegram.org/type/PhoneCallProtocol.html @@ -0,0 +1,143 @@ + + + + + PhoneCallProtocol + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCallProtocol

+ +

Phone call protocol

+

+ +
+
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phoneCallProtocolProtocol info for libtgvoip
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Poll.html b/data/core.telegram.org/type/Poll.html new file mode 100644 index 0000000000..567314114c --- /dev/null +++ b/data/core.telegram.org/type/Poll.html @@ -0,0 +1,143 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +

Indicates a poll message

+

+ +
+
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollPoll
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/PostAddress.html b/data/core.telegram.org/type/PostAddress.html new file mode 100644 index 0000000000..6df885b58a --- /dev/null +++ b/data/core.telegram.org/type/PostAddress.html @@ -0,0 +1,143 @@ + + + + + PostAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

PostAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
postAddressShipping address
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ReceivedNotifyMessage.html b/data/core.telegram.org/type/ReceivedNotifyMessage.html new file mode 100644 index 0000000000..d281fb997e --- /dev/null +++ b/data/core.telegram.org/type/ReceivedNotifyMessage.html @@ -0,0 +1,143 @@ + + + + + ReceivedNotifyMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

ReceivedNotifyMessage

+ +

Confirmation of message receipt

+

+ +
+
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/ReplyMarkup.html b/data/core.telegram.org/type/ReplyMarkup.html new file mode 100644 index 0000000000..b15813b492 --- /dev/null +++ b/data/core.telegram.org/type/ReplyMarkup.html @@ -0,0 +1,158 @@ + + + + + ReplyMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

ReplyMarkup

+ +

Reply markup for bot and inline keyboards

+

+ +
+
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
+replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
+replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
+replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
replyKeyboardHideHide sent bot keyboard
replyKeyboardForceReplyForce the user to send a reply
replyKeyboardMarkupBot keyboard
replyInlineMarkupBot or inline keyboard
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureData.html b/data/core.telegram.org/type/SecureData.html new file mode 100644 index 0000000000..d5b3aa24db --- /dev/null +++ b/data/core.telegram.org/type/SecureData.html @@ -0,0 +1,146 @@ + + + + + SecureData + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureData

+ +

Secure passport data, for more info see the passport docs »

+

+ +
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureDataSecure data
+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureValue.html b/data/core.telegram.org/type/SecureValue.html new file mode 100644 index 0000000000..ae0341370c --- /dev/null +++ b/data/core.telegram.org/type/SecureValue.html @@ -0,0 +1,162 @@ + + + + + SecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValue

+ +

Secure tgpassport value

+

+ +
+
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
+
+---functions---
+
+account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
secureValueSecure value
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.saveSecureValueSave secure passport value
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/SecureValueError.html b/data/core.telegram.org/type/SecureValueError.html new file mode 100644 index 0000000000..57d53fa14e --- /dev/null +++ b/data/core.telegram.org/type/SecureValueError.html @@ -0,0 +1,183 @@ + + + + + SecureValueError + + + + + + + + + + + + + +
+ +
+
+
+ +

SecureValueError

+ +

Secure value error

+

+ +
+
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
+secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
+secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
+secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
secureValueErrorDataSecure value error
secureValueErrorFrontSideSecure value error front side
secureValueErrorReverseSideReverse side error
secureValueErrorSelfieSecure value error: invalid selfie
secureValueErrorFileSecure value error file
secureValueErrorFilesSecure value error files
secureValueErrorSecure value error
secureValueErrorTranslationFileTranslation missing
secureValueErrorTranslationFilesTranslation file error
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/Theme.html b/data/core.telegram.org/type/Theme.html new file mode 100644 index 0000000000..a7fbcafad3 --- /dev/null +++ b/data/core.telegram.org/type/Theme.html @@ -0,0 +1,172 @@ + + + + + Theme + + + + + + + + + + + + + +
+ +
+
+
+ +

Theme

+ +

Cloud theme

+

+ +
+
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
+
+---functions---
+
+account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
+account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
themeTheme
+

Methods

+ + + + + + + + + + + + + + + + + + + + + +
MethodDescription
account.createThemeCreate a theme
account.updateThemeUpdate theme
account.getThemeGet theme information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WebAuthorization.html b/data/core.telegram.org/type/WebAuthorization.html new file mode 100644 index 0000000000..722bc888c0 --- /dev/null +++ b/data/core.telegram.org/type/WebAuthorization.html @@ -0,0 +1,143 @@ + + + + + WebAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

WebAuthorization

+ +

Web authorization

+

+ +
+
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
webAuthorizationRepresents a bot logged in using the Telegram login widget
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/WebPageAttribute.html b/data/core.telegram.org/type/WebPageAttribute.html new file mode 100644 index 0000000000..81e361ff36 --- /dev/null +++ b/data/core.telegram.org/type/WebPageAttribute.html @@ -0,0 +1,143 @@ + + + + + WebPageAttribute + + + + + + + + + + + + + +
+ +
+
+
+ +

WebPageAttribute

+ +

Webpage attributes

+

+ +
+
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
webPageAttributeThemePage theme
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.Authorizations b/data/core.telegram.org/type/account.Authorizations new file mode 100644 index 0000000000..9546f70b64 --- /dev/null +++ b/data/core.telegram.org/type/account.Authorizations @@ -0,0 +1,162 @@ + + + + + Account.Authorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.Authorizations

+ +

Logged-in sessions

+

+ +
+
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
+
+---functions---
+
+account.getAuthorizations#e320c158 = account.Authorizations;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.authorizationsLogged-in sessions
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getAuthorizationsGet logged-in sessions
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.ResetPasswordResult b/data/core.telegram.org/type/account.ResetPasswordResult new file mode 100644 index 0000000000..a5c2a6ec9c --- /dev/null +++ b/data/core.telegram.org/type/account.ResetPasswordResult @@ -0,0 +1,175 @@ + + + + + account.ResetPasswordResult + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ResetPasswordResult

+ +

Result of an account.resetPassword request.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+---functions---
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
account.resetPasswordFailedWaitYou requested a password reset too many times, please wait until the specified date before retrying the reset.
account.resetPasswordRequestedWaitYou already requested a password reset, please wait until the specified date before retrying the reset.
account.resetPasswordOkThe 2FA password was reset successfully.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.resetPasswordInitiate a 2FA password reset
+

Related pages

+

account.resetPassword

+

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.SentChangePhoneCode b/data/core.telegram.org/type/account.SentChangePhoneCode new file mode 100644 index 0000000000..c0ce024e0b --- /dev/null +++ b/data/core.telegram.org/type/account.SentChangePhoneCode @@ -0,0 +1,128 @@ + + + + + Account.SentChangePhoneCode + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.SentChangePhoneCode

+ +

Sent phone code

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/account.WebAuthorizations b/data/core.telegram.org/type/account.WebAuthorizations new file mode 100644 index 0000000000..687072af52 --- /dev/null +++ b/data/core.telegram.org/type/account.WebAuthorizations @@ -0,0 +1,162 @@ + + + + + Account.WebAuthorizations + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.WebAuthorizations

+ +

Web authorizations

+

+ +
+
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
+
+---functions---
+
+account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.webAuthorizationsWeb authorizations
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getWebAuthorizationsGet web login widget authorizations
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.PasswordRecovery b/data/core.telegram.org/type/auth.PasswordRecovery new file mode 100644 index 0000000000..94ec06ba24 --- /dev/null +++ b/data/core.telegram.org/type/auth.PasswordRecovery @@ -0,0 +1,165 @@ + + + + + auth.PasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.PasswordRecovery

+ +

Recovery info of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+
+---functions---
+
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
auth.passwordRecoveryRecovery info of a 2FA password, only for accounts with a recovery email configured.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/auth.SentCodeType b/data/core.telegram.org/type/auth.SentCodeType new file mode 100644 index 0000000000..f8c320c6f0 --- /dev/null +++ b/data/core.telegram.org/type/auth.SentCodeType @@ -0,0 +1,158 @@ + + + + + auth.SentCodeType + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.SentCodeType

+ +

Type of the verification code that was sent

+

+ +
+
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;
+auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;
+auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;
+auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.sentCodeTypeAppThe code was sent through the telegram app
auth.sentCodeTypeSmsThe code was sent via SMS
auth.sentCodeTypeCallThe code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.
auth.sentCodeTypeFlashCallThe code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/bytes.html b/data/core.telegram.org/type/bytes.html new file mode 100644 index 0000000000..898629893f --- /dev/null +++ b/data/core.telegram.org/type/bytes.html @@ -0,0 +1,125 @@ + + + + + bytes + + + + + + + + + + + + + +
+ +
+
+
+ +

bytes

+ +

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

+

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

+

Related pages

+

string

+

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

+

Further details on basic types»

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/double.html b/data/core.telegram.org/type/double.html new file mode 100644 index 0000000000..b1a3a9ae88 --- /dev/null +++ b/data/core.telegram.org/type/double.html @@ -0,0 +1,118 @@ + + + + + double + + + + + + + + + + + + + +
+ +
+
+
+ +

double

+ +

A basic bare type, values of which correspond two-element sequences containing 64-bit real numbers in a standard double format.

+

More on basic types»

+

Related pages

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.Country b/data/core.telegram.org/type/help.Country new file mode 100644 index 0000000000..b88bc8e262 --- /dev/null +++ b/data/core.telegram.org/type/help.Country @@ -0,0 +1,143 @@ + + + + + help.Country + + + + + + + + + + + + + +
+ +
+
+
+ +

help.Country

+ +

Name, ISO code, localized name and phone codes/patterns of a specific country

+

+ +
+
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.countryName, ISO code, localized name and phone codes/patterns of a specific country
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/help.PromoData b/data/core.telegram.org/type/help.PromoData new file mode 100644 index 0000000000..2b20632203 --- /dev/null +++ b/data/core.telegram.org/type/help.PromoData @@ -0,0 +1,167 @@ + + + + + help.PromoData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.PromoData

+ +

Info about pinned MTProxy or Public Service Announcement peers.

+

+ +
+
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
+help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
+
+---functions---
+
+help.getPromoData#c0977421 = help.PromoData;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.promoDataEmptyNo PSA/MTProxy info is available
help.promoDataMTProxy/Public Service Announcement information
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getPromoDataGet MTProxy/Public Service Announcement information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.AffectedFoundMessages b/data/core.telegram.org/type/messages.AffectedFoundMessages new file mode 100644 index 0000000000..9e8a731077 --- /dev/null +++ b/data/core.telegram.org/type/messages.AffectedFoundMessages @@ -0,0 +1,162 @@ + + + + + messages.AffectedFoundMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.AffectedFoundMessages

+ +

Messages found and affected by changes

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
+
+---functions---
+
+messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.affectedFoundMessagesMessages found and affected by changes
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.deletePhoneCallHistoryDelete the phone call history with a user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.CheckedHistoryImportPeer b/data/core.telegram.org/type/messages.CheckedHistoryImportPeer new file mode 100644 index 0000000000..0996418f17 --- /dev/null +++ b/data/core.telegram.org/type/messages.CheckedHistoryImportPeer @@ -0,0 +1,165 @@ + + + + + messages.CheckedHistoryImportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.CheckedHistoryImportPeer

+ +

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

+

+ +
+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+---functions---
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.checkedHistoryImportPeerContains a confirmation text to be shown to the user, upon importing chat history.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat.

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.ExportedChatInvite b/data/core.telegram.org/type/messages.ExportedChatInvite new file mode 100644 index 0000000000..998e30f4f6 --- /dev/null +++ b/data/core.telegram.org/type/messages.ExportedChatInvite @@ -0,0 +1,172 @@ + + + + + messages.ExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvite

+ +

Contains info about a chat invite, and eventually a pointer to the newest chat invite.

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+---functions---
+
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInviteInfo about a chat invite
messages.exportedChatInviteReplacedThe specified chat invite was replaced with another one
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.FavedStickers b/data/core.telegram.org/type/messages.FavedStickers new file mode 100644 index 0000000000..e76cb717e7 --- /dev/null +++ b/data/core.telegram.org/type/messages.FavedStickers @@ -0,0 +1,167 @@ + + + + + Messages.FavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FavedStickers

+ +

Favorited stickers

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+---functions---
+
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getFavedStickersGet faved stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.MessageEditData b/data/core.telegram.org/type/messages.MessageEditData new file mode 100644 index 0000000000..8ba8a76e4a --- /dev/null +++ b/data/core.telegram.org/type/messages.MessageEditData @@ -0,0 +1,162 @@ + + + + + Messages.MessageEditData + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.MessageEditData

+ +

Message edit data for media

+

+ +
+
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
+
+---functions---
+
+messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.messageEditDataMessage edit data for media
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getMessageEditDataFind out if a media message's caption can be edited
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.PeerDialogs b/data/core.telegram.org/type/messages.PeerDialogs new file mode 100644 index 0000000000..b4eb333f5b --- /dev/null +++ b/data/core.telegram.org/type/messages.PeerDialogs @@ -0,0 +1,167 @@ + + + + + Messages.PeerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.PeerDialogs

+ +

List of dialogs

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+
+---functions---
+
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.SearchCounter b/data/core.telegram.org/type/messages.SearchCounter new file mode 100644 index 0000000000..61cfea4766 --- /dev/null +++ b/data/core.telegram.org/type/messages.SearchCounter @@ -0,0 +1,143 @@ + + + + + Messages.SearchCounter + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.SearchCounter

+ +

Number of results that would be returned by a search

+

+ +
+
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.searchCounterIndicates how many results would be found by a messages.search call with the same parameters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.SponsoredMessages b/data/core.telegram.org/type/messages.SponsoredMessages new file mode 100644 index 0000000000..f4ee16bf07 --- /dev/null +++ b/data/core.telegram.org/type/messages.SponsoredMessages @@ -0,0 +1,166 @@ + + + + + messages.SponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SponsoredMessages

+ +

A set of sponsored messages associated with a channel

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
+
+---functions---
+
+channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.sponsoredMessagesA set of sponsored messages associated with a channel
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
channels.getSponsoredMessagesGet a list of sponsored messages
+

Related pages

+

Sponsored messages

+

How to implement sponsored messages

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/messages.StickerSet b/data/core.telegram.org/type/messages.StickerSet new file mode 100644 index 0000000000..88abddd05a --- /dev/null +++ b/data/core.telegram.org/type/messages.StickerSet @@ -0,0 +1,188 @@ + + + + + Messages.StickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.StickerSet

+ +

Stickerset

+

+ +
+
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+
+stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
+stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
+stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
+stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
+stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.stickerSetStickerset and stickers inside it
+

Methods

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MethodDescription
messages.getStickerSetGet info about a stickerset
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.setStickerSetThumbSet stickerset thumbnail
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.BankCardData b/data/core.telegram.org/type/payments.BankCardData new file mode 100644 index 0000000000..6268d3ffbb --- /dev/null +++ b/data/core.telegram.org/type/payments.BankCardData @@ -0,0 +1,162 @@ + + + + + payments.BankCardData + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.BankCardData

+ +

Credit card info, provided by the card's bank(s)

+

+ +
+
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
+
+---functions---
+
+payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.bankCardDataCredit card info, provided by the card's bank(s)
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getBankCardDataGet info about a credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/payments.PaymentReceipt b/data/core.telegram.org/type/payments.PaymentReceipt new file mode 100644 index 0000000000..9e1b997c17 --- /dev/null +++ b/data/core.telegram.org/type/payments.PaymentReceipt @@ -0,0 +1,162 @@ + + + + + Payments.PaymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

Payments.PaymentReceipt

+ +

Payment receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+
+---functions---
+
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
payments.paymentReceiptReceipt
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
payments.getPaymentReceiptGet payment receipt
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/phone.ExportedGroupCallInvite b/data/core.telegram.org/type/phone.ExportedGroupCallInvite new file mode 100644 index 0000000000..a7b6c923fd --- /dev/null +++ b/data/core.telegram.org/type/phone.ExportedGroupCallInvite @@ -0,0 +1,162 @@ + + + + + phone.ExportedGroupCallInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.ExportedGroupCallInvite

+ +

An exported group call invitation.

+

+ +
+
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
+
+---functions---
+
+phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
phone.exportedGroupCallInviteAn invite to a group call or livestream
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/storage.FileType b/data/core.telegram.org/type/storage.FileType new file mode 100644 index 0000000000..10f85871df --- /dev/null +++ b/data/core.telegram.org/type/storage.FileType @@ -0,0 +1,188 @@ + + + + + storage.FileType + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.FileType

+ +

Object describes the file type.

+

+ +
+
storage.fileUnknown#aa963b05 = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.filePdf#ae1e508d = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
storage.fileUnknownUnknown type.
storage.filePartialPart of a bigger file.
storage.fileJpegJPEG image. MIME type: image/jpeg.
storage.fileGifGIF image. MIME type: image/gif.
storage.filePngPNG image. MIME type: image/png.
storage.filePdfPDF document image. MIME type: application/pdf.
storage.fileMp3Mp3 audio. MIME type: audio/mpeg.
storage.fileMovQuicktime video. MIME type: video/quicktime.
storage.fileMp4MPEG-4 video. MIME type: video/mp4.
storage.fileWebpWEBP image. MIME type: image/webp.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/string.html b/data/core.telegram.org/type/string.html new file mode 100644 index 0000000000..ad86e71f6b --- /dev/null +++ b/data/core.telegram.org/type/string.html @@ -0,0 +1,126 @@ + + + + + string + + + + + + + + + + + + + +
+ +
+
+
+ +

string

+ +

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

+

Further details on basic types»

+

Related pages

+

bytes

+

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

+

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

+

Binary Data Serialization

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/upload.CdnFile b/data/core.telegram.org/type/upload.CdnFile new file mode 100644 index 0000000000..0c1b0cbfdf --- /dev/null +++ b/data/core.telegram.org/type/upload.CdnFile @@ -0,0 +1,167 @@ + + + + + upload.CdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.CdnFile

+ +

Represents the download status of a CDN file

+

+ +
+
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
+upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
+
+---functions---
+
+upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
upload.cdnFileReuploadNeededThe file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.
upload.cdnFileRepresent a chunk of a CDN file.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getCdnFileDownload a CDN file.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/core.telegram.org/type/upload.File b/data/core.telegram.org/type/upload.File new file mode 100644 index 0000000000..8a195440cf --- /dev/null +++ b/data/core.telegram.org/type/upload.File @@ -0,0 +1,167 @@ + + + + + upload.File + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.File

+ +

Contains info on file.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+---functions---
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
upload.fileFile content.
upload.fileCdnRedirectThe file must be downloaded from a CDN DC.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
upload.getFileReturns content of a whole file or its part.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end/voice-calls.html b/data/corefork.telegram.org/api/end-to-end/voice-calls.html new file mode 100644 index 0000000000..2743024d71 --- /dev/null +++ b/data/corefork.telegram.org/api/end-to-end/voice-calls.html @@ -0,0 +1,178 @@ + + + + + End-to-End Encrypted Voice Calls + + + + + + + + + + + + + +
+ +
+
+
+ +

End-to-End Encrypted Voice Calls

+ +
+

This document describes encryption in voice calls as implemented in Telegram apps with versions < 7.0. See this document for details on encryption used in voice and video calls in app versions released on August 14, 2020 and later.

+
+
Related articles
+

+ +

Establishing voice calls

+

Before a voice call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document details the generation of the encryption key. Other negotiations will be eventually documented elsewhere.

+

Key Generation

+

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

+

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

+
    +
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • +
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • +
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • +
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • +
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • +
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • +
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • +
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • +
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • +
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • +
+

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

+

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

+

Encryption of voice data

+

Both parties A (the Caller) and B (the Callee) transform the voice information into a sequence of small chunks or packets, not more than 1 kilobyte each. This information is to be encrypted using the shared key key generated during the initial exchange, and sent to the other party, either directly (P2P) or through Telegram's relay servers (so-called reflectors). This document describes only the encryption process for each chunk, leaving out voice encoding and the network-dependent parts.

+

Encapsulation of low-level voice data

+

The low-level data chunk raw_data:string, obtained from voice encoder, is first encapsulated into one of the two constructors for the DecryptedDataBlock type, similar to DecryptedMessage used in secret chats:

+
decryptedDataBlock#dbf948c1 random_id:long random_bytes:string flags:# voice_call_id:flags.2?int128 in_seq_no:flags.4?int out_seq_no:flags.4?int recent_received_mask:flags.5?int proto:flags.3?int extra:flags.1?string raw_data:flags.0?string = DecryptedDataBlock;
+simpleDataBlock#cc0d0e76 random_id:long random_bytes:string raw_data:string = DecryptedDataBlock;
+

Here out_seq_no is the chunk's sequence number among all sent by this party (starting from one), in_seq_no -- the highest known out_seq_no from the received packets. The parameter recent_received_mask is a 32-bit mask, used to track delivery of the last 32 packets sent by the other party. The bit i is set if a packet with out_seq_no equal to in_seq_no-i has been received.

+

The higher 8 bits in flags are reserved for use by the lower-level protocol (the one which generates and interprets raw_data), and will never be used for future extensions of decryptedDataBlock.

+

The parameters voice_call_id and proto are mandatory until the other side confirms reception of at least one packet by sending a packet with a non-zero in_seq_no. After that, they become optional, and the simpleDataBlock constructor can be used if the lower level protocol wants to.

+

The parameter voice_call_id is computed from the key key and equals the lower 128 bits of its SHA-256.

+

The random_bytes string should contain at least 7 bytes of random data. The field random_id also contains 8 random bytes, which can be used as a unique packet identifier if necessary.

+

MTProto encryption

+

Once the data is encapsulated in DecryptedDataBlock, it is TL-serialized and encrypted with MTProto, using key instead of auth_key; the parameter x is to be set to 0 for messages from A to B, and to 8 for messages in the opposite direction. Encrypted data are prepended by the 128-bit msg_key (usual for MTProto); before that, either the 128-bit voice_call_id (if P2P is used) or the peer_tag (if reflectors are used) is prepended. The resulting data packet is sent by UDP either directly to the other party (if P2P is possible) or to the Telegram relay servers (reflectors).

+

Key Verification

+

To verify the key, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

+

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

+
    +
  • A->B : (generates a and) sends g_a := g^a
  • +
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • +
  • A : computes key (g_b)^a
  • +
+

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

+
    +
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • +
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • +
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • +
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • +
+

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

+

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

+

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

+
+

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html new file mode 100644 index 0000000000..6282ab0f8c --- /dev/null +++ b/data/corefork.telegram.org/api/files.html @@ -0,0 +1,568 @@ + + + + + Uploading and Downloading Files + + + + + + + + + + + + + +
+ +
+
+
+ +

Uploading and Downloading Files

+ +
+ +

When working with the API, it is sometimes necessary to send a relatively large file to the server. For example, when sending a message with a photo/video attachment or when setting the current user’s profile picture.

+

Uploading files

+

There are a number of API methods to save files. The schema of the types and methods used is presented below:

+
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
+inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;
+
+
+inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
+inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
+
+inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+
+inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
+
+
+---functions---
+
+messages.sendMedia#e25ff8e0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
+messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
+
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;    
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
+

Before transmitting the contents of the file itself, the file has to be assigned a unique 64-bit client identifier: file_id.

+

The file’s binary content is then split into parts. All parts must have the same size ( part_size ) and the following conditions must be met:

+
    +
  • part_size % 1024 = 0 (divisible by 1KB)
  • +
  • 524288 % part_size = 0 (512KB must be evenly divisible by part_size)
  • +
+

The last part does not have to satisfy these conditions, provided its size is less than part_size.

+

Each part should have a sequence number, file_part, with a value ranging from 0 to 2,999.

+

After the file has been partitioned you need to choose a method for saving it on the server. Use upload.saveBigFilePart in case the full size of the file is more than 10 MB and upload.saveFilePart for smaller files.

+

Each call saves a portion of the data in a temporary location on the server to be used later. The storage life of each portion of data is between several minutes and several hours (depending on how busy the storage area is). After this time, the file part will become unavailable. To increase the time efficiency of a file save operation, we recommend using a call queue, so X pieces of the file are being saved at any given moment in time. Each successful operation to save a part invokes the method call to save the next part. The value of X can be tuned to achieve maximum performance.

+

When using one of the methods mentioned above to save file parts, one of the following data input errors may be returned:

+
    +
  • FILE_PARTS_INVALID - Invalid number of parts. The value is not between 1..3000
  • +
  • FILE_PART_INVALID: The file part number is invalid. The value is not between 0 and 2,999.
  • +
  • FILE_PART_TOO_BIG: The size limit (512 KB) for the content of the file part has been exceeded
  • +
  • FILE_PART_EMPTY: The file part sent is empty
  • +
  • FILE_PART_SIZE_INVALID - 512KB cannot be evenly divided by part_size
  • +
  • FILE_PART_SIZE_CHANGED - The part size is different from the size of one of the previous parts in the same file
  • +
+

While the parts are being uploaded, an MD5 hash of the file contents can also be computed to be used later as the md5_checksum parameter in the inputFile constructor (since it is checked only by the server, for encrypted secret chat files it must be generated from the encrypted file). +After the entire file is successfully saved, the final method may be called and passed the generated inputFile object. In case the upload.saveBigFilePart method is used, the inputFileBig constructor must be passed, in other cases use inputFile.

+ +

The file save operation may return one of the following data input errors:

+
    +
  • FILE_PARTS_INVALID: The number of file parts is invalid The value is not between 1 and 3,000.
  • +
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage. Try repeating the method call to resave the part.
  • +
  • MD5_CHECKSUM_INVALID: The file’s checksum did not match the md5_checksum parameter
  • +
+

Albums, grouped media

+
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
+
+inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
+
+---functions---
+
+messages.sendMultiMedia#f803138f flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+

Telegram allows grouping photos into albums and generic files (audio, docuemnts) into media groups.

+

To do this, messages.sendMultiMedia is used, wrapping each InputMedia constructor (uploaded or pre-existing, maximum 10 per media group) into an inputSingleMedia constructor, optionally providing a custom per-file caption in message.

+

For photo albums, clients should display an album caption only if exactly one photo in the group has a caption, otherwise no album caption should be displayed, and only when viewing in detail a specific photo of the group the caption should be shown.
+Other grouped media can display a caption under each file.

+

Re-using pre-uploaded files

+
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+---functions---
+
+messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
+

For some types of documents like GIFs, messages.getDocumentByHash can be used to search for the document on Telegram servers. +The SHA256 hash of the file is computed, and it is passed along with the file's mime type and size to the method: if the file type is correct and the file is found, a document is returned.

+

Uploading profile or chat pictures

+
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+
+photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
+
+inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
+
+inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
+
+inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
+inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
+
+---functions---
+
+photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
+photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
+
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
+
+channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
+

User profile pictures can be uploaded using the photos.uploadProfilePhoto method: the actual profile picture has to be uploaded as for normal files.
+photos.uploadProfilePhoto can also be used to reupload previously uploaded profile pictures.

+

Animated profile pictures

+

Animated profile pictures are also supported, by populating the video constructor: square MPEG4 videos up to 1080x1080 are supported, 800x800 is the recommended resolution.
+The video_start_ts is a floating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.

+

Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (legacy groups) or channels.editPhoto (channels, supergroups).
+Use the inputChatPhoto to reuse previously uploaded profile pictures.

+

Downloading files

+

There are methods available to download files which have been successfully uploaded. The schema of the types and methods used is presented below:

+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
+upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
+
+storage.fileUnknown#aa963b05 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;
+
+---functions---
+
+upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
+

Any file can be downloaded by calling upload.getFile. +The data for the input parameter of the InputFileLocation type is generated as follows:

+
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
+inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+inputTakeoutFileLocation#29be5899 = InputFileLocation;
+inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
+inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;
+
+inputStickerSetEmpty#ffb62b95 = InputStickerSet;
+inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
+inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
+inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
+inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+inputPeerSelf#7da07ec9 = InputPeer;
+inputPeerChat#35a95cb9 chat_id:long = InputPeer;
+inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
+inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
+
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+
+chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
+userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
+
    +
  • +

    For photos, inputPhotoFileLocation is used:

    +
      +
    • id, file_reference and access_hash taken from the photo constructor
    • +
    • thumb_size taken from the type field of the desired PhotoSize of the photo
    • +
    +
  • +
  • +

    For profile pictures of users, channels, supergroups and groups, inputPeerPhotoFileLocation has to be used:

    +
      +
    • peer is the identifier of the peer whose photo we want to download
    • +
    • big is used to choose whether to download the full-resolution picture, or just the thumbnail
    • +
    • photo_id is extracted from the chatPhoto or userProfilePhoto of the desired profile photo
    • +
    +
  • +
  • +

    For documents, inputDocumentFileLocation is used:

    +
      +
    • id, file_reference and access_hash taken from the document constructor
    • +
    • If downloading the thumbnail of a document, thumb_size should be taken from the type field of the desired PhotoSize of the photo; otherwise, provide an empty string.
    • +
    +
  • +
  • +

    For previews of sticker sets, inputStickerSetThumb is used (note: to download stickers and previews of stickers use the document method described above for documents):

    + +
  • +
  • +

    For encrypted secret chat and telegram passport documents, respectively inputEncryptedFileLocation and inputSecureFileLocation have to be used, with parameters extracted from encryptedFile and secureFile (passport docs).

    +
  • +
  • +

    For livestream chunks, inputGroupCallStream is used:

    +
      +
    • call contains the related group call ID+access hash, taken from the groupCall constructor.
    • +
    • time_ms specifies the timestamp to fetch
    • +
    • scale specifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
    • +
    • video_channel specifies the video channel to fetch
    • +
    • video_quality specifies the selected video quality (0 = lowest, 1 = medium, 2 = best)
    • +
    +
  • +
  • +

    For old deprecated photos, if the client has cached some old fileLocations with the deprecated secret identifier, inputFileLocation or inputPhotoLegacyFileLocation is used (this is mainly used for backwards compatiblity with bot API file IDs, all user clients must use the modern inputPhotoFileLocation file IDs):

    +
      +
    • All fields are taken from the previously cached fileLocation except for file_reference, access_hash and id, which are taken from the photo constructor (the last two fields are used only if available, in which case inputPhotoLegacyFileLocation is used instead of inputFileLocation).
    • +
    +
  • +
+

The size of each file in bytes is available, which makes it possible to download the file in parts using the parameters offset and limit, similar to the way files are uploaded.

+

If precise flag is not specified, then

+
    +
  • The parameter offset must be divisible by 4 KB.
  • +
  • The parameter limit must be divisible by 4 KB.
  • +
  • 1048576 (1 MB) must be divisible by limit.
  • +
+

If precise is specified, then

+
    +
  • The parameter offset must be divisible by 1 KB.
  • +
  • The parameter limit must be divisible by 1 KB.
  • +
  • limit must not exceed 1048576 (1 MB).
  • +
+

In any case the requested part should be within one 1 MB chunk from the beginning of the file, i. e.

+
    +
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024).
  • +
+

The file download operation may return a FILE_REFERENCE_EXPIRED error (or another error starting with FILE_REFERENCE_): in this case, the file_reference field of the input location must be refreshed. +The file download operation may return an upload.fileCdnRedirect constructor: in this case, these instructions must be followed for downloading CDN files. +The file download operation may also return one of the following data input errors:

+
    +
  • FILE_ID_INVALID: The file address is invalid
  • +
  • OFFSET_INVALID: The offset value is invalid
  • +
  • LIMIT_INVALID: The limit value is invalid
  • +
  • FILE_MIGRATE_X: The file is in the datacenter No. X
  • +
+

Verifying downloaded chunks

+
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
+
+---functions---
+
+upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;
+

In order to confirm the integrity of the downloaded file, clients are recommended to verify hashes for each downloaded part, as for CDN DCs. +upload.getFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

+

Before saving each portion of the data received from the DC into the file, the client can confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getFileHashes method to obtain the missing hash.

+

Handling audio, video and vector previews

+

Schema:

+
photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
+photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
+
+videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
+
+document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+
+photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
+

Telegram attaches a vector of thumbnails with reduced resolution to all uploaded media.
+The server also generates a trimmed and scaled down video preview for videos, GIFs and animated profile pictures.

+

Image thumbnail types

+

Each photo preview has a specific type, indicating the resolution and image transform that was applied server-side.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeImage filterSize
sbox100x100
mbox320x320
xbox800x800
ybox1280x1280
wbox2560x2560
acrop160x160
bcrop320x320
ccrop640x640
dcrop1280x1280
+

Special types:

+ + + + + + + + + + + + + + + + + +
TypeImage filter
istrip
joutline
+

Stripped thumbnails

+
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+

A photoStrippedSize (with type i) is an extremely low-res thumbnail, embedded directly inside media location objects.
+It should be shown to the user in chat message previews, or while still downloading the most appropriately sized photoSize through the media DCs as described above.

+

The stripped bytes payload should be inflated to a JPG payload as seen here ».

+

Vector thumbnails

+
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
+

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation. +Animated sticker outlines will have a j type photoPathSize thumbnail.

+

This specific vector thumbnail consists in an SVG path, specially encoded to save space.
+This path will be the outline of the animated sticker, and should be shown to the user while downloading the actual sticker.

+

As for stripped sizes, the payload should be inflated using the following algorithm:

+
encoded := photoPathSize.bytes
+
+lookup := "AACAAAAHAAALMAAAQASTAVAAAZaacaaaahaaalmaaaqastava.az0123456789-,"
+
+path := "M"
+
+len := strlen(encoded)
+for (i = 0; i < len; i++) {
+  num := ord(encoded[i])
+  if (num >= 128 + 64) {
+    path += lookup[num - 128 - 64]
+  } else {
+    if (num >= 128) {
+      path += ','
+    } else if (num >= 64) {
+      path += '-'
+    }
+    path += itoa(num & 63)
+  }
+}
+path += "z"
+

path will contain the actual SVG path that can be directly inserted in the d attribute of an svg <path> element:

+
<?xml version="1.0" encoding="utf-8"?>
+<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
+   viewBox="0 0 512 512" xml:space="preserve">
+<path d="{$path}"/>
+</svg>
+

Video types

+
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
+

A videoSize constructor is typically used for animated profile pictures and video previews.

+ + + + + + + + + + + + + + + + + + + + +
TypeDescriptionFormat
uAnimated profile pictureMPEG4
vVideo previewMPEG4
+

Downloading webfiles

+

Remote HTTP files sent by inline bots in response to inline queries and in other places are represented by WebDocument constructors. +When forwarding such remote HTTP files, they should be sent using external InputMedia constructors. +Remote HTTP files can only be downloaded directly by the client if contained in a webDocumentNoProxy constructor: in this case, the file is deemed safe to download (this is the case for HTTPS files from certain trusted domains).

+

However, if the remote file is contained in a webDocument, to avoid leaking sensitive information the file must be downloaded through telegram's servers. +This can be done in a manner similar to normal files, with the difference that upload.getWebFile must be used, instead.

+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+
+storage.fileUnknown#aa963b05 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;
+
+ ---functions---
+
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
+

The InputWebFileLocation constructor is generated as follows.

+
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
+inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
+
+webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
+
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
+
+geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
+
    +
  • inputWebFileLocation is simply generated by taking the url and access_hash fields of the webDocument constructor.
  • +
  • inputWebFileGeoPointLocation is used to download a server-generated image with the map preview from a geoPoint.
      +
    • geo_point is generated from the lat, long accuracy_radius parameters of the geoPoint
    • +
    • access_hash is the access hash of the geoPoint
    • +
    • w - Map width in pixels before applying scale; 16-1024
    • +
    • h - Map height in pixels before applying scale; 16-1024
    • +
    • zoom - Map zoom level; 13-20
    • +
    • scale - Map scale; 1-3
    • +
    +
  • +
+

General Considerations

+

It is recommended that large queries (upload.getFile, upload.saveFilePart, upload.getWebFile) be handled through a separate session and a separate connection, in which no methods other than these should be executed. If this is done, then data transfer will cause less interference with getting updates and other method calls.

+

Related articles

+

Handling file references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/import.html b/data/corefork.telegram.org/api/import.html new file mode 100644 index 0000000000..bb6e294831 --- /dev/null +++ b/data/corefork.telegram.org/api/import.html @@ -0,0 +1,173 @@ + + + + + Imported messages + + + + + + + + + + + + + +
+ +
+
+
+ +

Imported messages

+ +
+ +

Telegram allows importing messages and media from foreign chat apps.

+
+

Note: This article is intended for MTProto API developers. If you're looking for a way to move history from other chat apps into Telegram, check out the related Telegram blog post.

+
+

1. Validate the chat export file

+
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
+
+---functions---
+
+messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
+

The import process begins by calling messages.checkHistoryImport, passing to import_head up to 100 lines of the chat export file, starting from the beginning of the file.

+

The returned constructor contains information about the exported chat, including its title or type. +If the pm flag is set, the chat export file was generated from a private chat. +If the group flag is set, the chat export file was generated from a group chat. +If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

+

2. Choosing a destination Telegram chat

+
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
+
+---functions---
+
+messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
+

Using messages.checkHistoryImportPeer, check whether chat history exported from another chat app can be imported into a specific Telegram peer, chosen by the user.
+Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

+

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user in a confirmation prompt.
+Upon final user confirmation, the import process is initialized.

+

3. Initialize the import

+
messages.historyImport#1662af0b id:long = messages.HistoryImport;
+
+---functions---
+
+messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
+

Use messages.initHistoryImport to initialize the import process, passing the following parameters:

+
    +
  • peer - The Telegram chat where the history should be imported.
  • +
  • file - The chat export file.
  • +
  • media_count - The number of media files associated with the export, to be uploaded in the next step.
  • +
+

4. Uploading media

+
---functions---
+
+messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
+

Use messages.uploadImportedMedia to upload media files eventually associated with the chat export.
+import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport in the previous step.

+

5. Finalize the import

+
message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+---functions---
+
+messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
+

Finally, invoke messages.startHistoryImport to complete the history import process, importing all messages into the chat.
+As usual, import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport.

+

Imported messages will show in the chat history as messages containing a fwd_from messageFwdHeader constructor with the imported flag, and should be appropriately marked in the UI as messages imported from a foreign chat app.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/poll.html b/data/corefork.telegram.org/api/poll.html new file mode 100644 index 0000000000..0e3dfaee29 --- /dev/null +++ b/data/corefork.telegram.org/api/poll.html @@ -0,0 +1,199 @@ + + + + + Poll + + + + + + + + + + + + + +
+ +
+
+
+ +

Poll

+ +
+ +

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

+

Sending a poll

+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
+
+---functions---
+
+messages.sendMedia#e25ff8e0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;
+

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

+
    +
  • +

    poll is the actual poll constructor, containing:

    +
      +
    • question - The poll title, aka the poll's title
    • +
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • +
    • closed - Whether the poll is closed
    • +
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • +
    • multiple_choice - Whether multiple options can be chosen as answer
    • +
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • +
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • +
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      +These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • +
    +
  • +
  • +

    correct_answers - For quizes, option ID of the only correct answer

    +
  • +
  • +

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    +
  • +
  • +

    solution_entities - Styled text message entities for the solution explanation

    +
  • +
+

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

+

Voting in polls

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
+
+messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
+

When receiving a message with a messageMediaPoll, users can vote in it using messages.sendVote, specifying the chosen option identifiers.

+

The method will return an updateMessagePoll, containing an updated pollResults constructor, with the chosen flag set on the options we chose, and the correct flag set on the correct answers.

+

Getting poll votes

+
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
+
+pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
+
+updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
+
+---functions---
+
+messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
+

Regularly, if new users have voted in polls available to the user, they will receive an updateMessagePoll, with updated pollResults.

+

The same constructor can also be fetched manually using messages.getPollResults.

+

Getting poll voters in non-anonymous polls

+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
+messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
+messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
+
+messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList; 
+
+updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
+
+---functions---
+
+messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
+

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
+Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/rights.html b/data/corefork.telegram.org/api/rights.html new file mode 100644 index 0000000000..603681a672 --- /dev/null +++ b/data/corefork.telegram.org/api/rights.html @@ -0,0 +1,133 @@ + + + + + Admin, banned, default rights + + + + + + + + + + + + + +
+ +
+
+
+ +

Admin, banned, default rights

+ +
+ +

Channels and supergroups allow setting granular permissions both for admins and specific users. +Channels, supergroups and legacy groups also allow setting global granular permissions for users.

+

They can be modified as follows:

+

Admin rights

+

channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup. +Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.

+

Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).

+

Banned rights

+

channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things. +Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser: however, setting global granular permissions with legacy groups is supported.

+

Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.

+

Default rights

+

messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel, supergroup or legacy group, to restrict them from doing certain things.

+

Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/threads.html b/data/corefork.telegram.org/api/threads.html new file mode 100644 index 0000000000..153f04f039 --- /dev/null +++ b/data/corefork.telegram.org/api/threads.html @@ -0,0 +1,182 @@ + + + + + Threads + + + + + + + + + + + + + +
+ +
+
+
+ +

Threads

+ +
+ +

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Message threads

+

Schema:

+
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+
+message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+---functions---
+
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
+

Threads are usually automatically created when replying to any message in a group.
+For example, all replies to a message with ID 420 are associated to thread with ID 420, unique to this group; this thread ID is contained in the reply_to_top_id field of reply_to messageReplyHeader, along with an eventual reply_to_msg_id, for replies to messages within a thread.
+Replies to messages in a thread are part of the same thread, and do not spawn new threads.

+

When receiving a message from a group that is also the top of a thread (the message with ID 420), the replies optional field will contain a messageReplies constructor, containing the message ID and PTS of the latest reply in the thread, and the message ID of the latest read thread reply, along with the total number of replies in the thread.

+

Replies to a thread can also be manually fetched using messages.search, providing to top_msg_id the thread ID.

+

Channel comments

+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
+

The same messageReplies constructor seen above will also be contained in channel posts, this time containing information about the comment section of a specific channel post.
+The comment section of a channel post is simply the message thread of the automatically forwarded channel message in the linked discussion supergroup; the ID of the linked discussion supergroup will be contained in the messageReplies.channel_id field.

+

For channel posts, the recent_repliers field will also contain information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.

+

@replies

+
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
+
+messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
+
+message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+
+updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
+updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
+
+---functions---
+
+contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
+
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
+

Since a user can comment in channel posts without joining the actual discussion supergroup, there must be a way for them to receive notifications about replies in comment sections.
+For this reason, a special @replies username is provided. +Its ID for main and testing endpoints can be seen in the tdlib sources.

+

When someone replies to one of our messages in the comment section of a channel post, and the user is not subscribed to the discussion group, the client will receive two updates:

+
    +
  • An updateNewChannelMessage from the discussion group itself, structured just like any other update coming from a subscribed group, with:
      +
    • id set to the ID of the reply
    • +
    • from_id set to the peer that replied to us
    • +
    • peer_id set to the peer of the discussion group
    • +
    • reply_to.reply_to_msg_id set to the ID of our message
    • +
    • reply_to.reply_to_top_id set to the thread ID.
    • +
    +
  • +
  • An updateNewMessage
      +
    • id set to the common ID sequence for users
    • +
    • from_id set to the peer of @replies
    • +
    • peer_id set to our own peer
    • +
    • fwd_from.saved_from_msg_id set to the ID of the reply
    • +
    • fwd_from.from_id set to the the peer that replied to us
    • +
    • reply_to.reply_to_peer_id set to the peer of the discussion group
    • +
    • reply_to.reply_to_msg_id set to the ID of our message
    • +
    • reply_to.reply_to_top_id set to the thread ID
    • +
    +
  • +
+

Clients should display messages coming from @replies as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/api/url-authorization.html b/data/corefork.telegram.org/api/url-authorization.html new file mode 100644 index 0000000000..365eb87458 --- /dev/null +++ b/data/corefork.telegram.org/api/url-authorization.html @@ -0,0 +1,160 @@ + + + + + Seamless Telegram Login + + + + + + + + + + + + + +
+ +
+
+
+ +

Seamless Telegram Login

+ +
+ +

Bots or Telegram websites may ask users to login to a certain website via Telegram when clicking on certain links or URL buttons in inline keyboards.

+

Bot URL authorization

+

When the user clicks on keyboardButtonUrlAuth, messages.requestUrlAuth should be called, providing the button_id of the button and the ID and peer of the container message. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The bot parameter will contain info about the bot which will be used for user authorization (example: DiscussBot).
  • +
  • The request_write_access will be set if the bot would like to send messages to the user.
  • +
+

The info should be shown in a prompt:

+
+ TITLE +
+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open, which will include a query string with the requested info and a hash that must be verified upon receival by the service.

+

urlAuthResultDefault could also be returned, instead, in which case the url of the keyboardButtonUrlAuth must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Link URL authorization

+

Telegram supports automatic authorization on certain websites upon opening an HTTP URL in-app, upon clicking a link in a message or clicking on a keyboardButtonUrl.

+

Automatic authorization

+

Clients should automatically authenticate users when opening official Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

Upon clicking a link, the URL must be modified by appending the autologin_token from the client configuration object » to the query string, like so:

+

Original URL: https://somedomain.telegram.org/path?query=string#fragment=value
+Modified URL: https://somedomain.telegram.org/path?query=string&autologin_token=$autologin_token#fragment=value

+

Make sure that the used autologin_token is no more than 10000 seconds old, if it is older it must be refetched before use as described in the client configuration section ».

+

Manual authorization

+

Clients should show a confirmation prompt similar to the one used for bots, to authenticate users when opening certain Telegram websites, listed in the url_auth_domains key of the client configuration object ».

+

messages.requestUrlAuth should be called, providing only the original url. +The returned urlAuthResultRequest object will contain more details about the authorization request:

+
    +
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • +
  • The request_write_access will be set if the website would like to send messages to the user.
  • +
+

The info should be shown in a prompt.

+

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). +The result will be a urlAuthResultAccepted with the final URL to open.

+

urlAuthResultDefault could also be returned, instead, in which case the original URL must be opened, instead. +The same must be done if the user opens the link while refusing the authorization request.

+

Related articles

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/bots/samples/hellobot.html b/data/corefork.telegram.org/bots/samples/hellobot.html new file mode 100644 index 0000000000..5ad7bd1cf8 --- /dev/null +++ b/data/corefork.telegram.org/bots/samples/hellobot.html @@ -0,0 +1,287 @@ + + + + + Hellobot + + + + + + + + + + + + + +
+ +
+
+
+ +

Hellobot

+ +
+

This sample PHP bot demonstrates the basics of the Telegram Bot API.
If you have questions, try our FAQ or check out this page for more examples.

+
+

+ +
<?php
+
+define('BOT_TOKEN', '12345678:replace-me-with-real-token');
+define('API_URL', 'https://api.telegram.org/bot'.BOT_TOKEN.'/');
+
+function apiRequestWebhook($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  $parameters["method"] = $method;
+
+  $payload = json_encode($parameters);
+  header('Content-Type: application/json');
+  header('Content-Length: '.strlen($payload));
+  echo $payload;
+
+  return true;
+}
+
+function exec_curl_request($handle) {
+  $response = curl_exec($handle);
+
+  if ($response === false) {
+    $errno = curl_errno($handle);
+    $error = curl_error($handle);
+    error_log("Curl returned error $errno: $error\n");
+    curl_close($handle);
+    return false;
+  }
+
+  $http_code = intval(curl_getinfo($handle, CURLINFO_HTTP_CODE));
+  curl_close($handle);
+
+  if ($http_code >= 500) {
+    // do not wat to DDOS server if something goes wrong
+    sleep(10);
+    return false;
+  } else if ($http_code != 200) {
+    $response = json_decode($response, true);
+    error_log("Request has failed with error {$response['error_code']}: {$response['description']}\n");
+    if ($http_code == 401) {
+      throw new Exception('Invalid access token provided');
+    }
+    return false;
+  } else {
+    $response = json_decode($response, true);
+    if (isset($response['description'])) {
+      error_log("Request was successful: {$response['description']}\n");
+    }
+    $response = $response['result'];
+  }
+
+  return $response;
+}
+
+function apiRequest($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  foreach ($parameters as $key => &$val) {
+    // encoding to JSON array parameters, for example reply_markup
+    if (!is_numeric($val) && !is_string($val)) {
+      $val = json_encode($val);
+    }
+  }
+  $url = API_URL.$method.'?'.http_build_query($parameters);
+
+  $handle = curl_init($url);
+  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
+  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
+  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
+
+  return exec_curl_request($handle);
+}
+
+function apiRequestJson($method, $parameters) {
+  if (!is_string($method)) {
+    error_log("Method name must be a string\n");
+    return false;
+  }
+
+  if (!$parameters) {
+    $parameters = array();
+  } else if (!is_array($parameters)) {
+    error_log("Parameters must be an array\n");
+    return false;
+  }
+
+  $parameters["method"] = $method;
+
+  $handle = curl_init(API_URL);
+  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
+  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
+  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
+  curl_setopt($handle, CURLOPT_POST, true);
+  curl_setopt($handle, CURLOPT_POSTFIELDS, json_encode($parameters));
+  curl_setopt($handle, CURLOPT_HTTPHEADER, array("Content-Type: application/json"));
+
+  return exec_curl_request($handle);
+}
+
+function processMessage($message) {
+  // process incoming message
+  $message_id = $message['message_id'];
+  $chat_id = $message['chat']['id'];
+  if (isset($message['text'])) {
+    // incoming text message
+    $text = $message['text'];
+
+    if (strpos($text, "/start") === 0) {
+      apiRequestJson("sendMessage", array('chat_id' => $chat_id, "text" => 'Hello', 'reply_markup' => array(
+        'keyboard' => array(array('Hello', 'Hi')),
+        'one_time_keyboard' => true,
+        'resize_keyboard' => true)));
+    } else if ($text === "Hello" || $text === "Hi") {
+      apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'Nice to meet you'));
+    } else if (strpos($text, "/stop") === 0) {
+      // stop now
+    } else {
+      apiRequestWebhook("sendMessage", array('chat_id' => $chat_id, "reply_to_message_id" => $message_id, "text" => 'Cool'));
+    }
+  } else {
+    apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'I understand only text messages'));
+  }
+}
+
+
+define('WEBHOOK_URL', 'https://my-site.example.com/secret-path-for-webhooks/');
+
+if (php_sapi_name() == 'cli') {
+  // if run from console, set or delete webhook
+  apiRequest('setWebhook', array('url' => isset($argv[1]) && $argv[1] == 'delete' ? '' : WEBHOOK_URL));
+  exit;
+}
+
+
+$content = file_get_contents("php://input");
+$update = json_decode($content, true);
+
+if (!$update) {
+  // receive wrong update, must not happen
+  exit;
+}
+
+if (isset($update["message"])) {
+  processMessage($update["message"]);
+}
+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/bots/webhooks.html b/data/corefork.telegram.org/bots/webhooks.html new file mode 100644 index 0000000000..1aa78ec5c3 --- /dev/null +++ b/data/corefork.telegram.org/bots/webhooks.html @@ -0,0 +1,827 @@ + + + + + Marvin's Marvellous Guide to All Things Webhook + + + + + + + + + + + + + +
+ +
+
+
+ +

Marvin's Marvellous Guide to All Things Webhook

+ +
+ +

We currently support two ways of processing bot updates, getUpdates and setWebhook. getUpdates is a pull mechanism, setwebhook is push. Although the concept of a webhook is fairly simple, the setup of the individual components has proven to be tricky for many. This guide provides some extra information for those of you brave enough to venture into the art of the webhook.

+

There are some advantages of using a webhook over getUpdates. As soon as an update arrives, we’ll kindly deliver it to your bot for processing.

+

This:

+
1. Avoids your bot having to ask for updates frequently.
+2. Avoids the need for some kind of polling mechanism in your code.
+

Other advantages may include saving some potential CPU cycles and an increase in response time, these things however depend heavily on the usage pattern of your bot.

+

Setting a webhook means you supplying Telegram with a location in the form of a URL, on which your bot listens for updates. We need to be able to connect and post updates to that URL.

+

To ensure that we can do that, there are some basic requirements:

+

The short version

+

You'll need a server that:

+
    +
  • Supports IPv4, IPv6 is currently not supported for webhooks.
  • +
  • Accepts incoming POSTs from subnets 149.154.160.0/20 and 91.108.4.0/22 on port 443, 80, 88, or 8443.
  • +
  • Is able to handle TLS1.2(+) HTTPS-traffic.
  • +
  • Provides a supported, verified or self-signed certificate.
  • +
  • Uses a CN or SAN that matches the domain you’ve supplied on setup.
  • +
  • Supplies all intermediate certificates to complete a verification chain.
  • +
+

That’s almost all there’s to it.
If you decide to limit traffic to our specific range of addresses, keep an eye on this document whenever you seem to run into trouble. Our IP-range might change in the future.

+

The longer version

+
    +
  • A domain name

    +

    Setting a webhook needs a URL for us to post to. For that you'll need a server with a domain name. If you don't have one, you'll need to obtain one first. Telegram currently doesn't offer hosting or domain name services. There are quite a few VPS/Web hosting providers around the internet, feel free to pick one to your liking.
    If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    How do I get a server with a domain name?

    +
  • +
  • An open port

    +

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    +
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
    +Whenever something stops working in the future, please check this document again as 
    +the range might expand or change.
    +

    How do I check for open ports or limit access to my bot?

    +
  • +
  • Always SSL/TLS

    +

    A webhook requires SSL/TLS encryption, no matter which port is used. It's not possible to use a plain-text HTTP webhook. You shouldn't want to either, for the sake of your bot and users.
    SSL/TLS, why do I have to handle this for a webhook?

    +
  • +
  • Not all SSL/TLS is equal

    +

    We support any SSL/TLS version TLS1.2 and up for your webhook. This means that SSLV2/3/TLS1.0/TSL1.1 are NOT supported, due to security issues associated with those older versions.
    How do I check that I’m handling the right version?

    +
  • +
  • SSL needs a certificate

    +

    The common name (CN) of your certificate (self-signed or verified) has to match the domain name where your bot is hosted. You may also use a subject alternative name (SAN), that matches the domain for your webhook. Server Name Indication (SNI)-routing is supported. If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    A certificate, where do I get one, and how?

    +
  • +
  • Verified or self-signed

    +

    A certificate can either be verified or self-signed. Setting a webhook with a self-signed certificate differs a little from setting a webhook with a verified certificate. Ensure you're using the correct setup for the type of certificate you've chosen for your webhook.
    How do I set a webhook for either type?

    +
  • +
  • Supported certificates

    +

    Not all verified certificates are supported. Certificates are based on a network of trust and come in a chain. Trusting your verified certificate means we have to trust the provider of that certificate, the Certificate Authority (and hence its root certificate). Before you pick a certificate provider, Check this list to make sure that we actually trust their root certificate.
    What if my root certificate isn’t on that list?

    +
  • +
  • An Untrusted root

    +

    Ok, so you already had a certificate installed and just discovered it’s not on our list.
    Start by ignoring it, and just try to set it. We occasionally add extra root certificates to keep up with popular demand, so the list isn't always exhaustive. Unlucky after all? We'll allow you to supply an unsupported root certificate when setting the webhook. This method is nearly identical to setting a self-signed certificate webhook. Instead of your self-signed certificate you'll be sending us the root certificate as inputFile.
    Setting a verified webhook with an untrusted root

    +
  • +
  • Intermediate certificates

    +

    Some verified certificates require an intermediate certificate. In this construction the provider of your verified certificate has used their root certificate to sign an intermediate certificate. This intermediate certificate is then used to sign your verified certificate. You'll need to provide the intermediate certificate for us to be able to verify the chain of trust. CA's that use this type of chain supply an intermediate certificate.
    Supplying an intermediate certificate

    +
  • +
  • More information

    +

    Since we know webhooks can be a tad overwhelming, we’re working on a little digital assistant that’ll try and help you with the most common problems, it's not nearly perfect, but you may try using @CanOfWormsBot to check if your chain of certificates is installed correctly before contacting support.

    +
  • +
  • Testing your bot

    +

    We took the liberty of adding a set of example updates. They come in handy when testing your bot, no matter which method of getting updates you might be using.

    +
  • +
  • Don't panic.

    +

    If by now you're looking for your fishing gear because we've mentioned ports and hooks or you're about to Google what kind of bait URL and TLS exactly are, this guide might not be completely for you. You’re quite likely still a brilliant bot programmer, don’t worry. Perhaps this whole webhook thing is just new to you, not all is lost. If you currently have a working getUpdates situation, it's a good idea to pick up this guide again on a rainy Sunday afternoon and take your time to read up on some subjects around the internet. This guide can only contain a finite amount of information after all.

    +
  • +
+

The verbose version

+
How do I get a server with a domain name?
+

If you use a webhook, we have to deliver requests to your bot to a server we can reach. So yes, you need a server we can connect to. It can be anywhere in the galaxy, if you ensure we can reach the server by domain name (or at least via IP for a self-signed certificate), it will work just fine.

+

There are quite a few ways to get this done, as a novice however it's likely that you're not directly jumping at the chance of crafting this from scratch. Actually, as a novice, we recommend you don't. It's likely to be a complex and long ride.

+

If you got stuck here, make a choice:

+
    +
  • You use getUpdates at the moment and it works, keep it that way. Especially if you're running your bot from a nice machine that does well. There is nothing wrong with using getUpdates.

    +
  • +
  • Go with a hosted service and let a bunch of professionals worry about things like registering a domain, setting up DNS, a web server, securing it and so on.

    +
  • +
+
If you're going with a hosted service, make sure to look for a hosting provider that 
+not only supports your code’s needs, for example: support for your PHP version,
+but one that also handles SSL and allows you to create/deploy certificates.
+
    +
  • Go crazy, dive on the internet and start reading. Once you’re confident that you’ve got all the basic theories down, find yourself a nice hosted VPS or roll your own machine at home and get back to us here.
  • +
+
How do I check for open ports or limit access to my bot?
+

So you have the hosting thing down and all is good so far, however, when you enter the address of your bot in your browser it seems unreachable.

+

Explaining every firewall or web server solution in detail isn't possible for us, which we hope you understand. If you’re running a hosted solution, you’re more likely to have a nice UI where you configure these settings. Head to your configuration panel and check all of them. If you’re on a Linux based VPS with shell access, we have some tips for you:

+
    +
  • Make sure your bot process is indeed configured to listen on the port you're using.
    netstat –ln | grep portnumber
    Shows you if your bot is actually listening for incoming requests on the port you expect.
    sudo lsof -i | grep process name
    Is a simple way to check if that’s actually being listened on by the process your bot is using.
  • +
+
    +
  • Make sure it’s listening correctly.
    Your bot has to listen on the address you’ve exposed to the outside (your public IP), it can also listen on all addresses (*: or 0.0.0.0).
    The netstat and lsof-commands mentioned above assist in checking this. If nothing shows up, it is time to check your configuration and fix it. Set the correct IP, make sure it’s listening on a supported port and fire away! Just use a Web Browser to check if you’re reachable. The problem can be in the configuration of your bot, your web server virtual host configuration, or the servers binding configuration.
  • +
+
    +
  • If you still can’t reach your address, check your firewall.
    sudo iptables –L
    OR
    sudo ufw status verbose (Ubuntu)
    Gives you some insight in the current firewall settings.

    +
  • +
  • If it looks like you’re blocking incoming traffic, let’s fix that.
    sudo iptables –A INPUT –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow portnumber/tcp
    Allows incoming traffic on all interfaces to the specified tcp port.
    sudo iptables –A INPUT –i interfacename –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp
    Allows incoming traffic to a specific interface and a specific port from everywhere.
    sudo ifconfig
    Helps you find the interface with the public address you’re going to use.

    +
  • +
+
If you use iptables, make sure to actually SAVE after changing the configuration.
+On a Debian based system the iptables-persistent package is be a good option.
+RHEL/CentOS offers a service iptables save -command.
+A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.
+
    +
  • If you’re just looking for some hints on how to limit incoming traffic:
    sudo iptables –A INPUT –i interfacename –p tcp –m iprange –src-range 149.154.167.197-149.154.167.233 –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp from 149.154.167.192/26
    Allows incoming traffic to a specific interface and a specific port from a specific range of addresses. (ufw is using a subnet mask in the example, ranging from 192-255)
  • +
+

That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

+
SSL/TLS, what is it and why do I have to handle this for a webhook?
+

You’re already familiar with it in some form or another. Whenever you see that (nicely green) lock in your browser bar, you know it’s reasonably safe to assume that you’ve landed on the site you actually wanted to visit. If you see the green lock, that's SSL/TLS in action. If you want to learn more about how SSL/TLS works in general, it's best to search the internet.

+

The main difference between getUpdates and a webhook is the way the connection takes place. getUpdates means you'll connect to our server, a webhook means we'll be connecting to your server instead. Connecting to your server has to be done secure, we have to know for sure it's you we're talking to after all. This means you'll have to handle all that server side encryption stuff, virtually presenting us with a green lock. If you use a web server for us to post to, you need to support SSL/TLS handling on the port/virtual host of your choice. An online search for “YOURWEBSERVER enable HTTPS” will help you.

+

Not using a regular web server? Have a look at our example page, most examples there include code for handling SSL/TLS in a webhook setup.

+
How do I check that I’m handling the right version?
+

You just read up on the whole SSL/TLS stuff, figured out that it’s not all that bad to setup and we add some more requirements. Here are some tips to check if you’re indeed supporting at least TLS1.2.

+
    +
  • Several online services exist that allow you to check your certificate installation,
    They give you an overview of your supported TLS versions/Cipher suites and other details. Search online for Symantec crypto report or Qualys ssl. Both supply tools to verify your setup.

    +
  • +
  • Checking locally can also be done, in several ways, here are three options,

    +
      +
    • Go simple:
      Using Chrome as a browser? Open up the URL to your bot and inspect the certificate details. If you’re supporting TLS Chrome tells you so in the security overview tab. Other browsers are likely able to give you similar basic information.

      +
    • +
    • Using curl:
      curl --tlsv1.2 -v -k https://yourbotdomain:yourbotport/
      You can add --tlsv1.2 to force curl into using TLS1.2 when trying to connect. -k is optional and used to check against a self-signed certificate. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using.

      +
    • +
    • Using OpenSSL
      openssl s_client -tls1_2 -connect yourbotdomain:yourbotport -servername yourbotdomain
      You can add -tls1_2 to force OpenSSL into using TLS1.2 when trying to connect. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using. Note that https:// isn’t used for OpenSSL. -servername is optional, and included here for some shared hosters, which use SNI to route traffic to the correct domain. When SNI is used you’ll notice that your server appears to be returning a certificate for a different domain than your own. Adding -servername yourbotdomain ensures that SNI negotiation is done, and the correct certificate is returned.

      +
    • +
    +
  • +
  • Some additional configuration pointers

    +
      +
    • Forcing TLS in your virtual host on Apache:
      SSLProtocol -all +TLSv1.2
    • +
    • Forcing TLS in your virtual host on Nginx:
      ssl_protocols TLSv1.2;
    • +
    • Force TLS for your Java virtual machine through system properties:
      -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2
    • +
    • Enabling ssl debug for your JVM:
      -Djavax.net.debug=ssl,handshake,record
    • +
    +
  • +
  • Other tools that may help in debugging issues:

    +
      +
    • Wireshark: excellent packet capturing
    • +
    • Tcpdump: equally excellent and doesn’t need a GUI
    • +
    • Charles: web debugging proxy
    • +
    • Fiddler: web debugging proxy
    • +
    +
  • +
+
A certificate, where do I get one and how?
+

You need a certificate, pick on of these types;

+
    +
  • A verified, supported certificate
  • +
  • A self-signed certificate

    +
  • +
  • A verified, supported certificate
    +

    Using a verified certificate means you already have, or will obtain, a certificate backed by a trusted certificate authority (CA). There are many ways to acquire a verified certificate, paid or free. Two popular examples of free suppliers are StartSSL and Let’s Encrypt. You’re welcome to pick another. Just make sure first the supplier is likely to be supported.
    Check this list before selecting a CA.
    Once you’ve picked a CA and validated your identity with them, you can craft your certificate. This frequently starts by generating a CSR (Certificate Signing Request). Generating a CSR is done either through your host machine, or online via the tools provided by the CA.

    +
  • +
  • Here is an example (PEM format output).

    +
      +
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -keyout yourprivatekey.key -out yoursigningrequest.csr
    • +
    +
  • +
+
----
+Generating a 2048 bit RSA private keywriting new private key to yourprivatekey.key
+Enter PEM pass phrase: enter a password for your key here 
+Verifying - Enter PEM pass phrase: confirm the entered password
+-----
+You are about to be asked to enter information that will be incorporated
+into your certificate request.
+What you are about to enter is what is called a Distinguished Name or a DN.
+There are quite a few fields but you can leave some blank
+For some fields there will be a default value,If you enter '.',
+the field will be left blank.-----
+Country Name (2 letter code) [AU]:
+State or Province Name (full name) [Some-State]:
+Locality Name (eg, city) []:
+Organization Name (eg, company) [Internet Widgits Pty Ltd]:
+Organizational Unit Name (eg, section) []:
+Common Name (e.g. server FQDN or YOUR name) []: yourbotdomainname
+Email Address []:
+Please enter the following 'extra' attributes
+to be sent with your certificate request
+A challenge password []:
+An optional company name []:
+---
+
    +
  • Another example:

    +
      +
    • Using Java keytool:
      keytool -genkey -alias yourbotdomainname -keyalg RSA -keystore yourkeystore.jks -keysize 2048
    • +
    +
  • +
+
---
+Enter keystore password:  
+Re-enter new password: 
+What is your first and last name?  [Unknown]: yourbotdomainname
+What is the name of your organizational unit?  [Unknown]:  
+What is the name of your organization?  [Unknown]:  
+What is the name of your City or Locality?  [Unknown]:  
+What is the name of your State or Province?  [Unknown]:  
+What is the two-letter country code for this unit?  [Unknown]:  
+Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?  
+[no]:  yes
+Enter key password for yourbotdomainname   
+(RETURN if same as keystore password): 
+---
+

This generates the initial keystore, from which you can then create a CSR like this:

+

keytool -certreq -alias yourbotdomainname -keystore yourkeystore.jks -file yourbotdomainname.csr

+
---
+Enter keystore password:
+---
+

To validate your certificate the Common Name (CN) has to match your webhook domain. Example, if you’re using https://www.example.com/example.php as a webhook address, the certificate CN has to be www.example.com.
So you need an exact match of the FQDN you’re setting for the webhook

+

There is an exception, if you’re using a SAN (Subject Alternative Name) the webhook address can either match the CN of your certificate, OR one of the SANs provided in the certificate. In most cases you’ll be using the CN.

+

Create your CSR and supply the contents of the file to your CA. Most CA’s are kind enough to give you an example command of the input format they expect.

+

cat yoursigningrequest.csr or cat yourbotdomainname.csr
Lets you have a look at the CSR we just generated:

+
+ +
+ +

That doesn’t seem to informative, but we can deduce that the file is in PEM format (ASCII base64 encoded) and contains a certificate signing request. Luckily it is possible to look at the human readable contents of the CSR. Use the following commands to double check if all fields are set correctly.

+
    +
  • Using OpenSSL
    openssl req -text -noout -verify -in yoursigningrequest.csr

    +
  • +
  • Using Java keytool
    keytool -printcertreq -v -file yourbotdomainname.csr

    +
  • +
+

Verify your CSR and supply it to your CA to get a certificate. We’ll use StartSSL as an example here. StartSSL allows you to set up to 5 names (SAN), Their intermediate certificate is also needed for a webhook to work, which makes for a nice complete example.

+

Go to the certificates wizard, enter the required hostname(s) for your SSL certificate (this is the CN you’ve also set in the CSR and an optional SAN).

+
+ +
+ +

In the example above we’ve chosen to set a CN (test.telegram.org), but also a SAN (sanexample.telegram.org) The CN given has to match the CN used for generating the CSR.
Set your CN (and optional SAN) and copy the contents of the yoursigningrequest.csr file.

+
+ +
+ +

Paste the contents, submit and you’re done.

+
+ +
+ +

Now you can download the created certificate directly. In the example used above you’ll receive a zip file with several PEM certificates. The root, intermediate and yourdomain certificate.
You need the intermediate and yourdomain to set a webhook with a StartSSL certificate.

+

You can inspect the set of certificates you’ve just downloaded.

+
    +
  • Here are some example commands:

    +
      +
    • Using OpenSSL:
      openssl x509 -in yourdomain.crt -text -noout

      +
    • +
    • Using Java keytool:
      keytool -printcert -v -yourdomain.crt

      +
    • +
    • Using Windows:
      StartSSL supplies certificates in PEM format with a .crt extension, on Windows you can view the contents of them with a quick double click. Extract the files or open the “Otherserver.zip” and double click each of the certificates for inspection. The details tab supplies you with extra information.
      Make sure you have a correct CN in the Subject-field of the yourdomain-certificate. If you're using a SAN, make sure that it is listed in the Subject Alternative Name-field.

      +
    • +
    +
  • +
+
+ +
+ +

With your fresh certificates at hand, you can now continue setting your webhook.

+
    +
  • A self-signed certificate
    +

    Using a self-signed certificate means you’ll forfeit on the chain of trust backed by a CA. Instead you are the CA. For this to work, a slight difference in setup is required. Because Telegram will have no chain of trust to verify your certificate, you have to use the generated public certificate as an input file when setting the webhook. Keep in mind that the certificate file has to be uploaded as multipart/form data in PEM encoded (ASCII BASE64) format.

    +
  • +
  • First let’s generate some certificates:

    +
      +
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"
      You’ll end up with 2 files, a private key and the public certificate file. Use YOURPUBLIC.PEM as input file for setting the webhook.

      +
    • +
    • Using Java keytool:
      keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

      +
      What is your first and last name?
      +[test.telegram.org]:
      +What is the name of your organizational unit?
      +[Unknown]:  
      +What is the name of your organization?
      +[Unknown]:  
      +What is the name of your City or Locality?
      +[Unknown]:  
      +What is the name of your State or Province?
      +[Unknown]:  
      +What is the two-letter country code for this unit?
      +[Unknown]:  
      +Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
      +[no]: yes
      +

      Once done you’ll need 2 more commands to export the public certificate file from the generated store (you’ll be using the store for your JVM and the PEM for setting the webhook)

      +
    • +
    • Convert the JKS to pkcs12 (intermediate step for conversion to PEM):
      keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

      +
    • +
    • Convert PKCS12 to PEM (requires OpenSSL)
      openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem -nokeys

      +
    • +
    • Using Windows:
      Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.
      certreq -new TEMPLATE.txt RequestFileOut generates a CSR.

      +
    • +
    • TEMPLATE.txt example file:

      +
      [NewRequest]
      +; At least one value must be set in this section
      +Subject = "CN=DOMAIN.EXAMPLE"
      +KeyLength = 2048
      +KeyAlgorithm = RSA
      +HashAlgorithm = sha256
      +;MachineKeySet = true
      +RequestType = Cert
      +UseExistingKeySet=false ;generates a new private key (for export)
      +Exportable = true ;makes the private key exportable with the PFX
      +
    • +
    +
  • +
+

A self-signed certificate is generated and installed, to use the certificate for a self-signed webhook you'll have to export it in PEM format.

+
    +
  • Windows continued:

    +
      +
    • You can have a look at the certificates in your store with:
      certutil -store -user my

      +
    • +
    • To export the installed certificate in DER format (intermediate step for conversion to PEM):
      certutil -user -store -split my SERIALNUMBER YOURDER.der

      +
    • +
    • Now you can convert the certificate to PEM:
      certutil -encode YOURDER.der YOURPEM.pem
      Remember that only the public certificate is needed as input for the self-signed webhook certificate parameter.
      certmgr.msc can also be used as a GUI to export the public part of self-signed certificate to PEM.

      +
    • +
    +
  • +
+

After following the above you'll end up with a nice self-signed certificate. You’ll still have to set the webhook, and handle SSL correctly.

+
How do I set a webhook for either type?
+

The setWebhook method is needed for both types. For a verified certificate with a trusted root CA, it’s enough to use the setWebhook method with just the URL parameter.

+
    +
  • A curl example for a verified certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

For a self-signed certificate an extra parameter is needed, certificate, with the public certificate in PEM format as data.

+
    +
  • A curl example for a self-signed certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" -F "certificate=@<YOURCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

The -F means we’re using the multipart/form-data-type to supply the certificate, the type of the certificate parameter is inputFile. Make sure that you’re supplying the correct type.

+

Both parameters for the setWebhook method are classed as optional. Calling the method with an empty URL parameter can be used to clear a previously set webhook.

+
    +
  • A curl example to clear a previous webhook :
    curl -F "url=" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • +
+

Keep in mind that the URL parameter starts with https:// when setting a webhook. By default that means we’re knocking at your door on port 443. If you want to use another port (80,88 or 8443), you’ll have to specify the port in the URL parameter.

+
    +
  • Example:
    url=https://<YOURDOMAIN.EXAMPLE>:88/<WEBHOOKLOCATION>
  • +
+
Setting a verified webhook with an untrusted root
+

If you already have a verified certificate and our servers don’t trust your root CA, we have an alternative way for you to set a webhook. Instead of using the setWebhook method without the certificate parameter, you can use the self-signed method. Your CA's root certificate has to be used as an inputFile for the certificate parameter.

+
    +
  • A curl example to supply an untrusted root certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>" -F "certificate=@<YOURCAROOTCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
    Before you can do this, you need the root certificate of your certificate’s CA. Most CA’s supply their root certificates in several different formats (PEM/DER/etc.). Visit your CA’s website, and download the Root certificate indicated for your verified certificate.
  • +
+

You can use these commands to quickly convert a DER formatted root certificate to PEM:

+
    +
  • Using OpenSSL:
    openssl x509 -inform der -in root.cer -out root.pem

    +
  • +
  • Using Java keytool:
    keytool -import -alias Root -keystore YOURKEYSTORE.JKS -trustcacerts -file ROOTCERT.CER
    The root certificate needs to be imported in your keystore first:
    keytool -exportcert -alias Root -file <YOURROOTPEMFILE.PEM> -rfc -keystore YOURKEYSTORE.JKS

    +
  • +
+

Once done, set your webhook with the root-pem-file and you’ll be good to go. If you need more pointers, have a look at the self-signed part of this guide.

+
Supplying an intermediate certificate
+

Once you’ve crafted your certificate, your CA might present you with a nice bundle. Most bundles contain a root certificate, your public certificate and sometimes an intermediate certificate. StartSSL is one of many CA’s that’ll supply such an intermediate beast. This certificate has to be supplied in the chain of certificates you’re presenting to us when we connect to your server. If an intermediate was used to sign your certificate but isn’t supplied to our servers, we won’t be able to verify the chain of trust and your webhook will not work.

+

If your webhook isn’t working and you’re wondering if the chain is complete:

+
    +
  • Check with your certificate provider if you need an intermediate certificate.
  • +
  • Verify your certificate chain.
    Search online for Symantec crypto report or Qualys ssl. 
    +Both supply tools to verify your setup.
    +
  • +
+

Here’s an example of a complete chain, note that in this case 2 intermediate certificates have been supplied.

+
+ +
+ +

Even though your browser might not complain when visiting your page, an incomplete chain will not work for your webhook. If your chain is incomplete we have some tips to add them to your current setup:

+
    +
  • Apache:
    Add the intermediate certificate to the end of the file configured in the SSLCertificateFile directive of your virtual host configuration. If you’re using an older version than Apache 2.4.8, you may use the SSLCertificateChainFile directive instead.

    +
  • +
  • Nginx:
    Add the intermediate certificate to the end of the file configured in the ssl_certificate_key directive of your virtual host configuration.

    +
  • +
  • A quick command for doing this correctly:
    cat your_domain_name.pem intermediate.pem >> bundle.pem
    Make sure the order is correct, expect failure otherwise.

    +
  • +
  • Java keytool:
    keytool -import -trustcacerts -alias intermediate -file intermediate.pem -keystore YOURKEYSTORE.jks

    +
  • +
+

The end result of all this is a complete certificate chain, backed by either a root certificate we trust or, in the case of an untrusted root, a root certificate you're supplying to us. Make sure to verify your setup again after adding the intermediate, once done, you're good to go!

+
Testing your bot with updates
+
    +
  • Update examples
    A set of example updates, which comes in handy for testing your bot.

    +
      +
    • Message with text using curl:

      +
      curl --tlsv1.2 -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test",
      +     "username":"Test"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test",
      +     "username":"Test"
      +  },
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +

      --tlsv1.2 will force using TLS1.2.

      +
    • +
    • Message with text using Postman:

      +
      + +
      +
    • +
    +
  • +
  • More examples in curl:

    +
      +
    • Message with text:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "type": "private",
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Forwarded message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "type": "private",
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "forward_from": {
      +     "last_name":"Forward Lastname",
      +     "id": 222222,
      +     "first_name":"Forward Firstname"
      +  },
      +  "forward_date":1441645550,
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Forwarded channel message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "forward_from": {
      +     "id": -10000000000,
      +     "type": "channel",
      +     "title": "Test channel"
      +  },
      +  "forward_date":1441645550,
      +  "text":"/start"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with a reply:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"/start",
      +  "reply_to_message":{
      +      "date":1441645000,
      +      "chat":{
      +          "last_name":"Reply Lastname",
      +          "type": "private",
      +          "id":1111112,
      +          "first_name":"Reply Firstname",
      +          "username":"Testusername"
      +      },
      +      "message_id":1334,
      +      "text":"Original"
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Edited message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"edited_message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"Edited text",
      +  "edit_date": 1441646600
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with entities:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "text":"Bold and italics",
      +  "entities": [
      +      {
      +          "type": "italic",
      +          "offset": 9,
      +          "length": 7
      +      },
      +      {
      +          "type": "bold",
      +          "offset": 0,
      +          "length": 4
      +      }
      +      ]
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with audio:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "audio": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "duration": 243,
      +      "mime_type": "audio/mpeg",
      +      "file_size": 3897500,
      +      "title": "Test music file"
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Voice message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "voice": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "duration": 5,
      +      "mime_type": "audio/ogg",
      +      "file_size": 23000
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Message with a document:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"message":{
      +  "date":1441645532,
      +  "chat":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "message_id":1365,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "document": {
      +      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      +      "file_name": "Testfile.pdf",
      +      "mime_type": "application/pdf",
      +      "file_size": 536392
      +  }
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"inline_query":{
      +  "id": 134567890097,
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "query": "inline query",
      +  "offset": ""
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Chosen inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"chosen_inline_result":{
      +  "result_id": "12",
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "query": "inline query",
      +  "inline_message_id": "1234csdbsk4839"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +
    • +
    • Callback query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      +"update_id":10000,
      +"callback_query":{
      +  "id": "4382bfdwdsb323b2d9",
      +  "from":{
      +     "last_name":"Test Lastname",
      +     "type": "private",
      +     "id":1111111,
      +     "first_name":"Test Firstname",
      +     "username":"Testusername"
      +  },
      +  "data": "Data from button callback",
      +  "inline_message_id": "1234csdbsk4839"
      +}
      +}' "https://YOUR.BOT.URL:YOURPORT/"
      +That's all we have for now!
    • +
    +
  • +
+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/constructor/account.resetPasswordFailedWait b/data/corefork.telegram.org/constructor/account.resetPasswordFailedWait new file mode 100644 index 0000000000..e9ad24616b --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.resetPasswordFailedWait @@ -0,0 +1,147 @@ + + + + + account.resetPasswordFailedWait + + + + + + + + + + + + + +
+ +
+
+
+ +

account.resetPasswordFailedWait

+ +

You recently requested a password reset that was canceled, please wait until the specified date before requesting another reset.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
retry_dateintWait until this date before requesting another reset.
+

Type

+

account.ResetPasswordResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/account.themesNotModified b/data/corefork.telegram.org/constructor/account.themesNotModified new file mode 100644 index 0000000000..e48df3d48b --- /dev/null +++ b/data/corefork.telegram.org/constructor/account.themesNotModified @@ -0,0 +1,132 @@ + + + + + account.themesNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

account.themesNotModified

+ +

No new themes were installed

+

+ +
+
account.themesNotModified#f41eb622 = account.Themes;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

account.Themes

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired b/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired new file mode 100644 index 0000000000..dac20857a9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired @@ -0,0 +1,155 @@ + + + + + auth.authorizationSignUpRequired + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.authorizationSignUpRequired

+ +

An account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up

+

+ +
+
auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
terms_of_serviceflags.0?help.TermsOfServiceTelegram's terms of service: the user must read and accept the terms of service before signing up to telegram
+

Type

+

auth.Authorization

+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeCall b/data/corefork.telegram.org/constructor/auth.codeTypeCall new file mode 100644 index 0000000000..0e4c665575 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.codeTypeCall @@ -0,0 +1,132 @@ + + + + + auth.codeTypeCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeCall

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeCall#741cd3e3 = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeSms b/data/corefork.telegram.org/constructor/auth.codeTypeSms new file mode 100644 index 0000000000..2c604a3ea5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/auth.codeTypeSms @@ -0,0 +1,132 @@ + + + + + auth.codeTypeSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.codeTypeSms

+ +

Type of verification code that will be sent next if you call the resendCode method: SMS code

+

+ +
+
auth.codeTypeSms#72a3158c = auth.CodeType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

auth.CodeType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeArctic.html b/data/corefork.telegram.org/constructor/baseThemeArctic.html new file mode 100644 index 0000000000..965d7643dc --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeArctic.html @@ -0,0 +1,132 @@ + + + + + baseThemeArctic + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeArctic

+ +

Arctic theme

+

+ +
+
baseThemeArctic#5b11125a = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/baseThemeClassic.html b/data/corefork.telegram.org/constructor/baseThemeClassic.html new file mode 100644 index 0000000000..c6575294a1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/baseThemeClassic.html @@ -0,0 +1,132 @@ + + + + + baseThemeClassic + + + + + + + + + + + + + +
+ +
+
+
+ +

baseThemeClassic

+ +

Classic theme

+

+ +
+
baseThemeClassic#c3a12462 = BaseTheme;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BaseTheme

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/boolTrue.html b/data/corefork.telegram.org/constructor/boolTrue.html new file mode 100644 index 0000000000..f066d89ff4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/boolTrue.html @@ -0,0 +1,132 @@ + + + + + boolTrue + + + + + + + + + + + + + +
+ +
+
+
+ +

boolTrue

+ +

The constructor can be interpreted as a booleantrue value.

+

+ +
+
boolTrue#997275b5 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botCommandScopeDefault.html b/data/corefork.telegram.org/constructor/botCommandScopeDefault.html new file mode 100644 index 0000000000..8c414c9684 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botCommandScopeDefault.html @@ -0,0 +1,132 @@ + + + + + botCommandScopeDefault + + + + + + + + + + + + + +
+ +
+
+
+ +

botCommandScopeDefault

+ +

The commands will be valid in all dialogs

+

+ +
+
botCommandScopeDefault#2f6cb2ab = BotCommandScope;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

BotCommandScope

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/botInlineResult.html b/data/corefork.telegram.org/constructor/botInlineResult.html new file mode 100644 index 0000000000..f148304c86 --- /dev/null +++ b/data/corefork.telegram.org/constructor/botInlineResult.html @@ -0,0 +1,189 @@ + + + + + botInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

botInlineResult

+ +

Generic result

+

+ +
+
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of article or webpage
thumbflags.4?WebDocumentThumbnail for the result
contentflags.5?WebDocumentContent of the result
send_messageBotInlineMessageMessage to send
+

Type

+

BotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEvent.html b/data/corefork.telegram.org/constructor/channelAdminLogEvent.html new file mode 100644 index 0000000000..e99e3bfc68 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEvent.html @@ -0,0 +1,162 @@ + + + + + channelAdminLogEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEvent

+ +

Admin log event

+

+ +
+
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongEvent ID
dateintDate
user_idlongUser ID
actionChannelAdminLogEventActionAction
+

Type

+

ChannelAdminLogEvent

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html new file mode 100644 index 0000000000..0218a8de7c --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html @@ -0,0 +1,152 @@ + + + + + channelAdminLogEventActionChangeLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionChangeLocation

+ +

The geogroup location was changed

+

+ +
+
channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
prev_valueChannelLocationPrevious location
new_valueChannelLocationNew location
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html new file mode 100644 index 0000000000..a19200ce5c --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionDiscardGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionDiscardGroupCall

+ +

A group call was terminated

+

+ +
+
channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call that was terminated
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html new file mode 100644 index 0000000000..7b194bdbce --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html @@ -0,0 +1,147 @@ + + + + + channelAdminLogEventActionStartGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionStartGroupCall

+ +

A group call was started

+

+ +
+
channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallGroup call
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html new file mode 100644 index 0000000000..8d6d1e269a --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleNoForwards.html @@ -0,0 +1,162 @@ + + + + + channelAdminLogEventActionToggleNoForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

channelAdminLogEventActionToggleNoForwards

+ +

+ +
+
channelAdminLogEventActionToggleNoForwards#cb2ac766 new_value:Bool = ChannelAdminLogEventAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
new_valueBool 
+

Type

+

ChannelAdminLogEventAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantAdmin.html b/data/corefork.telegram.org/constructor/channelParticipantAdmin.html new file mode 100644 index 0000000000..2c6230a10a --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantAdmin.html @@ -0,0 +1,190 @@ + + + + + channelParticipantAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantAdmin

+ +

Admin

+

+ +
+
channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_editflags.0?trueCan this admin promote other admins with the same permissions?
selfflags.1?trueIs this the current user
user_idlongAdmin user ID
inviter_idflags.1?longUser that invited the admin to the channel/group
promoted_bylongUser that promoted the user to admin
dateintWhen did the user join
admin_rightsChatAdminRightsAdmin rights
rankflags.2?stringThe role (rank) of the admin in the group: just an arbitrary string, admin by default
+

Type

+

ChannelParticipant

+

Related pages

+

Admin, banned, default rights

+

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html b/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html new file mode 100644 index 0000000000..34da486eca --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsAdmins + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsAdmins

+ +

Fetch only admin participants

+

+ +
+
channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsRecent.html b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html new file mode 100644 index 0000000000..91160c33af --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsRecent + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsRecent

+ +

Fetch only recent participants

+

+ +
+
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsSearch.html b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html new file mode 100644 index 0000000000..7cbe515197 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html @@ -0,0 +1,147 @@ + + + + + channelParticipantsSearch + + + + + + + + + + + + + +
+ +
+
+
+ +

channelParticipantsSearch

+ +

Query participants by name

+

+ +
+
channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
qstringSearch query
+

Type

+

ChannelParticipantsFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatAdminRights.html b/data/corefork.telegram.org/constructor/chatAdminRights.html new file mode 100644 index 0000000000..c0ce01ae7d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatAdminRights.html @@ -0,0 +1,205 @@ + + + + + chatAdminRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatAdminRights

+ +

Represents the rights of an admin in a channel/supergroup.

+

+ +
+
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
change_infoflags.0?trueIf set, allows the admin to modify the description of the channel/supergroup
post_messagesflags.1?trueIf set, allows the admin to post messages in the channel
edit_messagesflags.2?trueIf set, allows the admin to also edit messages from other admins in the channel
delete_messagesflags.3?trueIf set, allows the admin to also delete messages from other admins in the channel
ban_usersflags.4?trueIf set, allows the admin to ban users from the channel/supergroup
invite_usersflags.5?trueIf set, allows the admin to invite users in the channel/supergroup
pin_messagesflags.7?trueIf set, allows the admin to pin messages in the channel/supergroup
add_adminsflags.9?trueIf set, allows the admin to add other admins with the same (or more limited) permissions in the channel/supergroup
anonymousflags.10?trueWhether this admin is anonymous
manage_callflags.11?trueIf set, allows the admin to change group call/livestream settings
otherflags.12?trueSet this flag if none of the other flags are set, but you stil want the user to be an admin.
+

Type

+

ChatAdminRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatBannedRights.html b/data/corefork.telegram.org/constructor/chatBannedRights.html new file mode 100644 index 0000000000..bffb28280c --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatBannedRights.html @@ -0,0 +1,215 @@ + + + + + chatBannedRights + + + + + + + + + + + + + +
+ +
+
+
+ +

chatBannedRights

+ +

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

+

+ +
+
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send polls in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
+

Type

+

ChatBannedRights

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatInvitePeek.html b/data/corefork.telegram.org/constructor/chatInvitePeek.html new file mode 100644 index 0000000000..cb47897a6d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatInvitePeek.html @@ -0,0 +1,152 @@ + + + + + chatInvitePeek + + + + + + + + + + + + + +
+ +
+
+
+ +

chatInvitePeek

+ +

A chat invitation that also allows peeking into the group to read messages without joining it.

+

+ +
+
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
+

Type

+

ChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/chatOnlines.html b/data/corefork.telegram.org/constructor/chatOnlines.html new file mode 100644 index 0000000000..d28d7d472d --- /dev/null +++ b/data/corefork.telegram.org/constructor/chatOnlines.html @@ -0,0 +1,147 @@ + + + + + chatOnlines + + + + + + + + + + + + + +
+ +
+
+
+ +

chatOnlines

+ +

Number of online users in a chat

+

+ +
+
chatOnlines#f041e250 onlines:int = ChatOnlines;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
onlinesintNumber of online users
+

Type

+

ChatOnlines

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/codeSettings.html b/data/corefork.telegram.org/constructor/codeSettings.html new file mode 100644 index 0000000000..094bca3fa1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/codeSettings.html @@ -0,0 +1,176 @@ + + + + + codeSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

codeSettings

+ +

Settings used by telegram servers for sending the confirm code.

+

Example implementations: telegram for android, tdlib.

+

+ +
+
codeSettings#8a6469c2 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true allow_missed_call:flags.5?true logout_tokens:flags.6?Vector<bytes> = CodeSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
allow_flashcallflags.0?trueWhether to allow phone verification via phone calls.
current_numberflags.1?truePass true if the phone number is used on the current device. Ignored if allow_flashcall is not set.
allow_app_hashflags.4?trueIf a token that will be included in eventually sent SMSs is required: required in newer versions of android, to use the android SMS receiver APIs
allow_missed_callflags.5?true 
logout_tokensflags.6?Vector<bytes> 
+

Type

+

CodeSettings

+

Related pages

+

User Authorization

+

How to register a user's phone to start using the API.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contactStatus.html b/data/corefork.telegram.org/constructor/contactStatus.html new file mode 100644 index 0000000000..9e2080e57a --- /dev/null +++ b/data/corefork.telegram.org/constructor/contactStatus.html @@ -0,0 +1,152 @@ + + + + + contactStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

contactStatus

+ +

Contact status: online / offline.

+

+ +
+
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
statusUserStatusOnline status
+

Type

+

ContactStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.blockedSlice b/data/corefork.telegram.org/constructor/contacts.blockedSlice new file mode 100644 index 0000000000..79e90bad9d --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.blockedSlice @@ -0,0 +1,162 @@ + + + + + contacts.blockedSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.blockedSlice

+ +

Incomplete list of blocked users.

+

+ +
+
contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of elements in the list
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
+

Type

+

contacts.Blocked

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/contacts.contacts b/data/corefork.telegram.org/constructor/contacts.contacts new file mode 100644 index 0000000000..c3dbb9fab5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/contacts.contacts @@ -0,0 +1,157 @@ + + + + + contacts.contacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.contacts

+ +

The current user's contact list and info on users.

+

+ +
+
contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
contactsVector<Contact>Contact list
saved_countintNumber of contacts that were saved successfully
usersVector<User>User list
+

Type

+

contacts.Contacts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html new file mode 100644 index 0000000000..046928c11b --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionAcceptKey.html @@ -0,0 +1,160 @@ + + + + + decryptedMessageActionAcceptKey + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionAcceptKey

+ +

Accept new key

+

+ +
+
===20===
+decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
exchange_idlongExchange ID
g_bbytesB parameter, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
+

Type

+

DecryptedMessageAction

+

Related pages

+

Perfect Forward Secrecy

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html b/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html new file mode 100644 index 0000000000..237737768e --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html @@ -0,0 +1,155 @@ + + + + + decryptedMessageActionResend + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageActionResend

+ +

Request for the other party in a Secret Chat to automatically resend a contiguous range of previously sent messages, as explained in Sequence number is Secret Chats.

+

+ +
+
===17===
+decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
start_seq_nointout_seq_no of the first message to be resent, with correct parity
end_seq_nointout_seq_no of the last message to be resent, with same parity.
+

Type

+

DecryptedMessageAction

+

Related pages

+

Sequence numbers in Secret Chats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html new file mode 100644 index 0000000000..969750f202 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html @@ -0,0 +1,153 @@ + + + + + decryptedMessageMediaGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaGeoPoint

+ +

GeoPont attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html new file mode 100644 index 0000000000..11474e72d9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html @@ -0,0 +1,191 @@ + + + + + decryptedMessageMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaPhoto

+ +

Photo attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesContent of thumbnail file (JPEGfile, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
wintPhoto width
hintPhoto height
sizeintSize of the photo in bytes
keybytesKey to decrypt an attached file with a full version
ivbytesInitialization vector
captionstringCaption
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html new file mode 100644 index 0000000000..8ada4afd73 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html @@ -0,0 +1,207 @@ + + + + + decryptedMessageMediaVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaVideo

+ +

Video attached to an encrypted message.

+

+ +
+
===8===
+decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===17===
+decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
+
+===45===
+decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
thumbbytesContent of thumbnail file (JPEG file, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
durationintDuration of video in seconds
mime_typestringMIME-type of the video file
Parameter added in Layer 17.
wintImage width
hintImage height
sizeintFile size
keybytesKey to decrypt the attached video file
ivbytesInitialization vector
captionstringCaption
+

Type

+

DecryptedMessageMedia

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html new file mode 100644 index 0000000000..224789f8e8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html @@ -0,0 +1,148 @@ + + + + + decryptedMessageMediaWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageMediaWebPage

+ +

Webpage preview

+

+ +
+
===45===
+decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL of webpage
+

Type

+

DecryptedMessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/decryptedMessageService.html b/data/corefork.telegram.org/constructor/decryptedMessageService.html new file mode 100644 index 0000000000..bc3f98120f --- /dev/null +++ b/data/corefork.telegram.org/constructor/decryptedMessageService.html @@ -0,0 +1,156 @@ + + + + + decryptedMessageService + + + + + + + + + + + + + +
+ +
+
+
+ +

decryptedMessageService

+ +

Contents of an encrypted service message.

+

+ +
+
===8===
+decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
+
+===17===
+decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
random_idlongRandom message ID, assigned by the message author.
Must be equal to the ID passed to the sending method.
actionDecryptedMessageActionAction relevant to the service message
+

Type

+

DecryptedMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialog.html b/data/corefork.telegram.org/constructor/dialog.html new file mode 100644 index 0000000000..27eac357c4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialog.html @@ -0,0 +1,219 @@ + + + + + dialog + + + + + + + + + + + + + +
+ +
+
+
+ +

dialog

+ +

Chat

+

+ +
+
dialog#a8edd0f5 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int unread_reactions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs the dialog pinned
unread_markflags.3?trueWhether the chat was manually marked as unread
peerPeerThe chat
top_messageintThe latest message ID
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintNumber of unread messages
unread_mentions_countintNumber of unread mentions
unread_reactions_countint 
notify_settingsPeerNotifySettingsNotification settings
ptsflags.0?intPTS
draftflags.1?DraftMessageMessage draft
folder_idflags.4?intPeer folder ID, for more info click here
+

Type

+

Dialog

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialogFilterSuggested.html b/data/corefork.telegram.org/constructor/dialogFilterSuggested.html new file mode 100644 index 0000000000..00845e2375 --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogFilterSuggested.html @@ -0,0 +1,155 @@ + + + + + dialogFilterSuggested + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogFilterSuggested

+ +

Suggested folders

+

+ +
+
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
+

Type

+

DialogFilterSuggested

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/dialogPeerFolder.html b/data/corefork.telegram.org/constructor/dialogPeerFolder.html new file mode 100644 index 0000000000..15318e8ddf --- /dev/null +++ b/data/corefork.telegram.org/constructor/dialogPeerFolder.html @@ -0,0 +1,150 @@ + + + + + dialogPeerFolder + + + + + + + + + + + + + +
+ +
+
+
+ +

dialogPeerFolder

+ +

Peer folder

+

+ +
+
dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_idintPeer folder ID, for more info click here
+

Type

+

DialogPeer

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/document.html b/data/corefork.telegram.org/constructor/document.html new file mode 100644 index 0000000000..a9b825ede8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/document.html @@ -0,0 +1,200 @@ + + + + + document + + + + + + + + + + + + + +
+ +
+
+
+ +

document

+ +

Document

+

+ +
+
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongDocument ID
access_hashlongCheck sum, dependant on document ID
file_referencebytesFile reference
dateintCreation date
mime_typestringMIME type
sizeintSize
thumbsflags.0?Vector<PhotoSize>Thumbnails
video_thumbsflags.1?Vector<VideoSize>Video thumbnails
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes
+

Type

+

Document

+

Related pages

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeAudio.html b/data/corefork.telegram.org/constructor/documentAttributeAudio.html new file mode 100644 index 0000000000..d3dd51b2a1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeAudio.html @@ -0,0 +1,172 @@ + + + + + documentAttributeAudio + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeAudio

+ +

Represents an audio file

+

+ +
+
documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
voiceflags.10?trueWhether this is a voice message
durationintDuration in seconds
titleflags.0?stringName of song
performerflags.1?stringPerformer
waveformflags.2?bytesWaveform
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeFilename.html b/data/corefork.telegram.org/constructor/documentAttributeFilename.html new file mode 100644 index 0000000000..5f30e98f2b --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeFilename.html @@ -0,0 +1,147 @@ + + + + + documentAttributeFilename + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeFilename

+ +

A simple document with a file name

+

+ +
+
documentAttributeFilename#15590068 file_name:string = DocumentAttribute;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
file_namestringThe file name
+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html b/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html new file mode 100644 index 0000000000..8f0801708a --- /dev/null +++ b/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html @@ -0,0 +1,132 @@ + + + + + documentAttributeHasStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

documentAttributeHasStickers

+ +

Whether the current document has stickers attached

+

+ +
+
documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

DocumentAttribute

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/emojiLanguage.html b/data/corefork.telegram.org/constructor/emojiLanguage.html new file mode 100644 index 0000000000..c7d437cbcf --- /dev/null +++ b/data/corefork.telegram.org/constructor/emojiLanguage.html @@ -0,0 +1,147 @@ + + + + + emojiLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

emojiLanguage

+ +

Emoji language

+

+ +
+
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Type

+

EmojiLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/encryptedChatWaiting.html b/data/corefork.telegram.org/constructor/encryptedChatWaiting.html new file mode 100644 index 0000000000..96a384456a --- /dev/null +++ b/data/corefork.telegram.org/constructor/encryptedChatWaiting.html @@ -0,0 +1,167 @@ + + + + + encryptedChatWaiting + + + + + + + + + + + + + +
+ +
+
+
+ +

encryptedChatWaiting

+ +

Chat waiting for approval of second participant.

+

+ +
+
encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idintChat ID
access_hashlongChecking sum depending on user ID
dateintDate of chat creation
admin_idlongChat creator ID
participant_idlongID of second chat participant
+

Type

+

EncryptedChat

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/fileLocationUnavailable.html b/data/corefork.telegram.org/constructor/fileLocationUnavailable.html new file mode 100644 index 0000000000..6b36910c9e --- /dev/null +++ b/data/corefork.telegram.org/constructor/fileLocationUnavailable.html @@ -0,0 +1,179 @@ + + + + + fileLocationUnavailable + + + + + + + + + + + + + +
+ +
+
+
+ +

fileLocationUnavailable

+ +

File is currently unavailable.

+

+ +
+
Constructor schema is available as of layer 98. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
+

Type

+

FileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/game.html b/data/corefork.telegram.org/constructor/game.html new file mode 100644 index 0000000000..1a7751407b --- /dev/null +++ b/data/corefork.telegram.org/constructor/game.html @@ -0,0 +1,182 @@ + + + + + game + + + + + + + + + + + + + +
+ +
+
+
+ +

game

+ +

Indicates an already sent game

+

+ +
+
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idlongID of the game
access_hashlongAccess hash of the game
short_namestringShort name for the game
titlestringTitle of the game
descriptionstringGame description
photoPhotoGame preview
documentflags.0?DocumentOptional attached document
+

Type

+

Game

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/groupCall.html b/data/corefork.telegram.org/constructor/groupCall.html new file mode 100644 index 0000000000..4678ea435d --- /dev/null +++ b/data/corefork.telegram.org/constructor/groupCall.html @@ -0,0 +1,235 @@ + + + + + groupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

groupCall

+ +

Info about a group call or livestream

+

+ +
+
groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
join_mutedflags.1?trueWhether the user should be muted upon joining the call
can_change_join_mutedflags.2?trueWhether the current user can change the value of the join_muted flag using phone.toggleGroupCallSettings
join_date_ascflags.6?trueSpecifies the ordering to use when locally sorting by date and displaying in the UI group call participants.
schedule_start_subscribedflags.8?trueWhether we subscribed to the scheduled call
can_start_videoflags.9?trueWhether you can start streaming video into the call
record_video_activeflags.11?trueWhether the group call is currently being recorded
rtmp_streamflags.12?true 
idlongGroup call ID
access_hashlongGroup call access hash
participants_countintParticipant count
titleflags.3?stringGroup call title
stream_dc_idflags.4?intDC ID to be used for livestream chunks
record_start_dateflags.5?intWhen was the recording started
schedule_dateflags.7?intWhen is the call scheduled to start
unmuted_video_countflags.10?intNumber of people currently streaming video into the call
unmuted_video_limitintMaximum number of people allowed to stream video into the call
versionintVersion
+

Type

+

GroupCall

+

Related pages

+

phone.toggleGroupCallSettings

+

Change group call settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.appUpdate b/data/corefork.telegram.org/constructor/help.appUpdate new file mode 100644 index 0000000000..05cfb4253b --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.appUpdate @@ -0,0 +1,190 @@ + + + + + help.appUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.appUpdate

+ +

An update is available for the application.

+

+ +
+
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
can_not_skipflags.0?trueUnskippable, the new info must be shown to the user (with a popup or something else)
idintUpdate ID
versionstringNew version name
textstringText description of the update
entitiesVector<MessageEntity>Message entities for styled text
documentflags.1?DocumentApplication binary
urlflags.2?stringApplication download URL
stickerflags.3?DocumentAssociated sticker
+

Type

+

help.AppUpdate

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.countriesList b/data/corefork.telegram.org/constructor/help.countriesList new file mode 100644 index 0000000000..b719eb5bc8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.countriesList @@ -0,0 +1,155 @@ + + + + + help.countriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countriesList

+ +

Name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
hashintHash for pagination, for more info click here
+

Type

+

help.CountriesList

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.countriesListNotModified b/data/corefork.telegram.org/constructor/help.countriesListNotModified new file mode 100644 index 0000000000..8c737cf307 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.countriesListNotModified @@ -0,0 +1,132 @@ + + + + + help.countriesListNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

help.countriesListNotModified

+ +

The country list has not changed

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.CountriesList

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty b/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty new file mode 100644 index 0000000000..5120ea1cfc --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty @@ -0,0 +1,132 @@ + + + + + help.deepLinkInfoEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

help.deepLinkInfoEmpty

+ +

Deep link info empty

+

+ +
+
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.DeepLinkInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.noAppUpdate b/data/corefork.telegram.org/constructor/help.noAppUpdate new file mode 100644 index 0000000000..844ecd3f9d --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.noAppUpdate @@ -0,0 +1,132 @@ + + + + + help.noAppUpdate + + + + + + + + + + + + + +
+ +
+
+
+ +

help.noAppUpdate

+ +

No updates are available for the application.

+

+ +
+
help.noAppUpdate#c45a6536 = help.AppUpdate;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

help.AppUpdate

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.passportConfig b/data/corefork.telegram.org/constructor/help.passportConfig new file mode 100644 index 0000000000..26ed916575 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.passportConfig @@ -0,0 +1,156 @@ + + + + + help.passportConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

help.passportConfig

+ +

Telegram passport configuration

+

+ +
+
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
+

Type

+

help.PassportConfig

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.support b/data/corefork.telegram.org/constructor/help.support new file mode 100644 index 0000000000..41c9a204f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.support @@ -0,0 +1,152 @@ + + + + + help.support + + + + + + + + + + + + + +
+ +
+
+
+ +

help.support

+ +

Info on support user.

+

+ +
+
help.support#17c6b5f6 phone_number:string user:User = help.Support;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
userUserUser
+

Type

+

help.Support

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/help.supportName b/data/corefork.telegram.org/constructor/help.supportName new file mode 100644 index 0000000000..a0a97ad4a4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/help.supportName @@ -0,0 +1,147 @@ + + + + + help.supportName + + + + + + + + + + + + + +
+ +
+
+
+ +

help.supportName

+ +

Localized name for telegram support

+

+ +
+
help.supportName#8c05f1c9 name:string = help.SupportName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
namestringLocalized name
+

Type

+

help.SupportName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html new file mode 100644 index 0000000000..d38c8e6e99 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html @@ -0,0 +1,135 @@ + + + + + inlineQueryPeerTypeMegagroup + + + + + + + + + + + + + +
+ +
+
+
+ +

inlineQueryPeerTypeMegagroup

+ +

The inline query was sent in a supergroup

+

+ +
+
inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InlineQueryPeerType

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html new file mode 100644 index 0000000000..3d1d72c259 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html @@ -0,0 +1,172 @@ + + + + + inputBotInlineMessageMediaContact + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineMessageMediaContact

+ +

A contact

+

+ +
+
inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
+

Type

+

InputBotInlineMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResult.html b/data/corefork.telegram.org/constructor/inputBotInlineResult.html new file mode 100644 index 0000000000..aab98bb892 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputBotInlineResult.html @@ -0,0 +1,189 @@ + + + + + inputBotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

inputBotInlineResult

+ +

An inline bot result

+

+ +
+
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idstringID of result
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of result
thumbflags.4?InputWebDocumentThumbnail for result
contentflags.5?InputWebDocumentResult contents
send_messageInputBotInlineMessageMessage to send when the result is selected
+

Type

+

InputBotInlineResult

+

Related pages

+

Telegram Bot API

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChannelEmpty.html b/data/corefork.telegram.org/constructor/inputChannelEmpty.html new file mode 100644 index 0000000000..be130f7318 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChannelEmpty.html @@ -0,0 +1,132 @@ + + + + + inputChannelEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChannelEmpty

+ +

Represents the absence of a channel

+

+ +
+
inputChannelEmpty#ee8c1e86 = InputChannel;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputChannel

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html b/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html new file mode 100644 index 0000000000..8f06f3165a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html @@ -0,0 +1,165 @@ + + + + + inputChatUploadedPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputChatUploadedPhoto

+ +

New photo to be set as group profile photo.

+

+ +
+
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts using the method upload.saveFilePart
videoflags.1?InputFileSquare video for animated profile picture
video_start_tsflags.2?doubleTimestamp that should be shown as static preview to the user (seconds)
+

Type

+

InputChatPhoto

+

Related pages

+

upload.saveFilePart

+

Saves a part of file for futher sending to one of the methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html new file mode 100644 index 0000000000..fa012ff084 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html @@ -0,0 +1,132 @@ + + + + + inputCheckPasswordEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputCheckPasswordEmpty

+ +

There is no password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputCheckPasswordSRP

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDocument.html b/data/corefork.telegram.org/constructor/inputDocument.html new file mode 100644 index 0000000000..64cd70594b --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDocument.html @@ -0,0 +1,162 @@ + + + + + inputDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocument

+ +

Defines a video for subsequent interaction.

+

+ +
+
inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
+

Type

+

InputDocument

+

Related pages

+

document

+

Document

+

File references

+

How to handle file references.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDocumentEmpty.html b/data/corefork.telegram.org/constructor/inputDocumentEmpty.html new file mode 100644 index 0000000000..3c7e171472 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputDocumentEmpty.html @@ -0,0 +1,132 @@ + + + + + inputDocumentEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputDocumentEmpty

+ +

Empty constructor.

+

+ +
+
inputDocumentEmpty#72f0eaae = InputDocument;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputDocument

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGroupCall.html b/data/corefork.telegram.org/constructor/inputGroupCall.html new file mode 100644 index 0000000000..5963607e09 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGroupCall.html @@ -0,0 +1,152 @@ + + + + + inputGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGroupCall

+ +

Points to a specific group call

+

+ +
+
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
+

Type

+

InputGroupCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputGroupCallStream.html b/data/corefork.telegram.org/constructor/inputGroupCallStream.html new file mode 100644 index 0000000000..80ce048039 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputGroupCallStream.html @@ -0,0 +1,172 @@ + + + + + inputGroupCallStream + + + + + + + + + + + + + +
+ +
+
+
+ +

inputGroupCallStream

+ +

Chunk of a livestream

+

+ +
+
inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallLivestream info
time_mslongTimestamp in milliseconds
scaleintSpecifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
video_channelflags.0?intSelected video channel
video_qualityflags.0?intSelected video quality (0 = lowest, 1 = medium, 2 = best)
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html b/data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html new file mode 100644 index 0000000000..63b978464d --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputKeyboardButtonUserProfile.html @@ -0,0 +1,173 @@ + + + + + inputKeyboardButtonUserProfile + + + + + + + + + + + + + +
+ +
+
+
+ +

inputKeyboardButtonUserProfile

+ +

+ +
+
inputKeyboardButtonUserProfile#e988037b text:string user_id:InputUser = KeyboardButton;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstring 
user_idInputUser 
+

Type

+

KeyboardButton

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMediaPhoto.html b/data/corefork.telegram.org/constructor/inputMediaPhoto.html new file mode 100644 index 0000000000..15a7f7ee7a --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMediaPhoto.html @@ -0,0 +1,157 @@ + + + + + inputMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMediaPhoto

+ +

Forwarded photo

+

+ +
+
inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idInputPhotoPhoto to be forwarded
ttl_secondsflags.0?intTime to live in seconds of self-destructing photo
+

Type

+

InputMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessageReplyTo.html b/data/corefork.telegram.org/constructor/inputMessageReplyTo.html new file mode 100644 index 0000000000..3f9adf6457 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessageReplyTo.html @@ -0,0 +1,147 @@ + + + + + inputMessageReplyTo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessageReplyTo

+ +

Message to which the specified message replies to

+

+ +
+
inputMessageReplyTo#bad88395 id:int = InputMessage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idintID of the message that replies to the message we need
+

Type

+

InputMessage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html b/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html new file mode 100644 index 0000000000..189d4a4ab3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterChatPhotos + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterChatPhotos

+ +

Return only chat photo changes

+

+ +
+
inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html b/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html new file mode 100644 index 0000000000..3805114aeb --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterEmpty

+ +

Filter is absent.

+

+ +
+
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html new file mode 100644 index 0000000000..bc2d2521c8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterGeo

+ +

Return only messages containing geolocations

+

+ +
+
inputMessagesFilterGeo#e7026d0d = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html new file mode 100644 index 0000000000..8f96bf4389 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html @@ -0,0 +1,132 @@ + + + + + inputMessagesFilterVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

inputMessagesFilterVideo

+ +

Filter for messages containing videos.

+

+ +
+
inputMessagesFilterVideo#9fc00e65 = MessagesFilter;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

MessagesFilter

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html new file mode 100644 index 0000000000..364cacf63f --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html @@ -0,0 +1,147 @@ + + + + + inputPaymentCredentialsGooglePay + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPaymentCredentialsGooglePay

+ +

Google Pay payment credentials

+

+ +
+
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
payment_tokenDataJSONPayment token
+

Type

+

InputPaymentCredentials

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html b/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html new file mode 100644 index 0000000000..72c339bbf3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html @@ -0,0 +1,162 @@ + + + + + inputPeerPhotoFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPeerPhotoFileLocation

+ +

Location of profile photo of channel/group/supergroup/user

+

+ +
+
inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
bigflags.0?trueWhether to download the high-quality version of the picture
peerInputPeerThe peer whose profile picture should be downloaded
photo_idlongPhoto ID
+

Type

+

InputFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html new file mode 100644 index 0000000000..2db1d3c107 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyPhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyPhoneCall

+ +

Whether the user will accept phone calls

+

+ +
+
inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html new file mode 100644 index 0000000000..38f4eb03f5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html @@ -0,0 +1,132 @@ + + + + + inputPrivacyKeyPhoneNumber + + + + + + + + + + + + + +
+ +
+
+
+ +

inputPrivacyKeyPhoneNumber

+ +

Whether people will be able to see the user's phone number

+

+ +
+
inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputPrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonPornography.html b/data/corefork.telegram.org/constructor/inputReportReasonPornography.html new file mode 100644 index 0000000000..72c387af86 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonPornography.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonPornography + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonPornography

+ +

Report for pornography

+

+ +
+
inputReportReasonPornography#2e59d922 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputReportReasonSpam.html b/data/corefork.telegram.org/constructor/inputReportReasonSpam.html new file mode 100644 index 0000000000..fca4b732b3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputReportReasonSpam.html @@ -0,0 +1,132 @@ + + + + + inputReportReasonSpam + + + + + + + + + + + + + +
+ +
+
+
+ +

inputReportReasonSpam

+ +

Report for spam

+

+ +
+
inputReportReasonSpam#58dbcab8 = ReportReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

ReportReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html b/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html new file mode 100644 index 0000000000..283d3c2f10 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html @@ -0,0 +1,169 @@ + + + + + inputSecureFileUploaded + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureFileUploaded

+ +

Uploaded secure file, for more info see the passport docs »

+

+ +
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongSecure file ID
partsintSecure file part count
md5_checksumstringMD5 hash of encrypted uploaded file, to be checked server-side
file_hashbytesFile hash
secretbytesSecret
+

Type

+

InputSecureFile

+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputSecureValue.html b/data/corefork.telegram.org/constructor/inputSecureValue.html new file mode 100644 index 0000000000..7bf44bb781 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputSecureValue.html @@ -0,0 +1,190 @@ + + + + + inputSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

inputSecureValue

+ +

Secure value, for more info see the passport docs »

+

+ +
+
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
+

Type

+

InputSecureValue

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetID.html b/data/corefork.telegram.org/constructor/inputStickerSetID.html new file mode 100644 index 0000000000..d75f235911 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetID.html @@ -0,0 +1,152 @@ + + + + + inputStickerSetID + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetID

+ +

Stickerset by ID

+

+ +
+
inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongID
access_hashlongAccess hash
+

Type

+

InputStickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputStickerSetThumb.html b/data/corefork.telegram.org/constructor/inputStickerSetThumb.html new file mode 100644 index 0000000000..ac05115fd4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputStickerSetThumb.html @@ -0,0 +1,155 @@ + + + + + inputStickerSetThumb + + + + + + + + + + + + + +
+ +
+
+
+ +

inputStickerSetThumb

+ +

Location of stickerset thumbnail (see files)

+

+ +
+
inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
stickersetInputStickerSetSticker set
thumb_versionintThumbnail version
+

Type

+

InputFileLocation

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputUserSelf.html b/data/corefork.telegram.org/constructor/inputUserSelf.html new file mode 100644 index 0000000000..57b26e9cc8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputUserSelf.html @@ -0,0 +1,132 @@ + + + + + inputUserSelf + + + + + + + + + + + + + +
+ +
+
+
+ +

inputUserSelf

+ +

Defines the current user.

+

+ +
+
inputUserSelf#f7c1b13f = InputUser;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

InputUser

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html b/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html new file mode 100644 index 0000000000..bfe3cf58f2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html @@ -0,0 +1,172 @@ + + + + + inputWebFileGeoPointLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWebFileGeoPointLocation

+ +

Geolocation

+

+ +
+
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
geo_pointInputGeoPointGeolocation
access_hashlongAccess hash
wintMap width in pixels before applying scale; 16-1024
hintMap height in pixels before applying scale; 16-1024
zoomintMap zoom level; 13-20
scaleintMap scale; 1-3
+

Type

+

InputWebFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/inputWebFileLocation.html b/data/corefork.telegram.org/constructor/inputWebFileLocation.html new file mode 100644 index 0000000000..cbb8e48d34 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputWebFileLocation.html @@ -0,0 +1,152 @@ + + + + + inputWebFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

inputWebFileLocation

+ +

Location of a remote HTTP(s) file

+

+ +
+
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringHTTP URL of file
access_hashlongAccess hash
+

Type

+

InputWebFileLocation

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/jsonArray.html b/data/corefork.telegram.org/constructor/jsonArray.html new file mode 100644 index 0000000000..091d98fcce --- /dev/null +++ b/data/corefork.telegram.org/constructor/jsonArray.html @@ -0,0 +1,147 @@ + + + + + jsonArray + + + + + + + + + + + + + +
+ +
+
+
+ +

jsonArray

+ +

JSON array

+

+ +
+
jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
valueVector<JSONValue>JSON values
+

Type

+

JSONValue

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/message.html b/data/corefork.telegram.org/constructor/message.html new file mode 100644 index 0000000000..fcae72fd1f --- /dev/null +++ b/data/corefork.telegram.org/constructor/message.html @@ -0,0 +1,312 @@ + + + + + message + + + + + + + + + + + + + +
+ +
+
+
+ +

message

+ +

A message

+

+ +
+
message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueIs this an outgoing message
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether there are unread media attachments in this message
silentflags.13?trueWhether this is a silent message (no notification triggered)
postflags.14?trueWhether this is a channel post
from_scheduledflags.18?trueWhether this is a scheduled message
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
edit_hideflags.21?trueWhether the message should be shown as not modified to the user, even if an edit date is present
pinnedflags.24?trueWhether this message is pinned
noforwardsflags.26?true 
idintID of the message
from_idflags.8?PeerID of the sender of the message
peer_idPeerPeer ID, the chat where this message was sent
fwd_fromflags.2?MessageFwdHeaderInfo about forwarded messages
via_bot_idflags.11?longID of the inline bot that generated the message
reply_toflags.3?MessageReplyHeaderReply information
dateintDate of the message
messagestringThe message
mediaflags.9?MessageMediaMedia attachment
reply_markupflags.6?ReplyMarkupReply markup (bot/inline keyboards)
entitiesflags.7?Vector<MessageEntity>Message entities for styled text
viewsflags.10?intView count for channel posts
forwardsflags.10?intForward counter
repliesflags.23?MessageRepliesInfo about post comments (for channels) or message replies (for groups)
edit_dateflags.15?intLast edit date of this message
post_authorflags.16?stringName of the author of this message for channel posts (with signatures enabled)
grouped_idflags.17?longMultiple media messages sent using messages.sendMultiMedia with the same grouped ID indicate an album or media group
reactionsflags.20?MessageReactions 
restriction_reasonflags.22?Vector<RestrictionReason>Contains the reason why access to this message must be restricted.
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Message

+

Related pages

+

Mentions

+

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

+

Scheduled messages

+

Telegram allows scheduling messages

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

Styled text with message entities

+

How to create styled text with message entities

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

messages.sendMultiMedia

+

Send an album or grouped media

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionCustomAction.html b/data/corefork.telegram.org/constructor/messageActionCustomAction.html new file mode 100644 index 0000000000..b42c1dcff1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionCustomAction.html @@ -0,0 +1,147 @@ + + + + + messageActionCustomAction + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionCustomAction

+ +

Custom action (most likely not supported by the current layer, an upgrade might be needed)

+

+ +
+
messageActionCustomAction#fae69f56 message:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
messagestringAction message
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionGameScore.html b/data/corefork.telegram.org/constructor/messageActionGameScore.html new file mode 100644 index 0000000000..509833f06d --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionGameScore.html @@ -0,0 +1,152 @@ + + + + + messageActionGameScore + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionGameScore

+ +

Someone scored in a game

+

+ +
+
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
game_idlongGame ID
scoreintScore
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html b/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html new file mode 100644 index 0000000000..c540c2dcbf --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html @@ -0,0 +1,152 @@ + + + + + messageActionInviteToGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionInviteToGroupCall

+ +

A set of users was invited to the group call

+

+ +
+
messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
usersVector<long>The invited users
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html b/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html new file mode 100644 index 0000000000..05bbbd1193 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html @@ -0,0 +1,147 @@ + + + + + messageActionSetChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

messageActionSetChatTheme

+ +

The chat theme was changed

+

+ +
+
messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
emoticonstringThe emoji that identifies a chat theme
+

Type

+

MessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityBlockquote.html b/data/corefork.telegram.org/constructor/messageEntityBlockquote.html new file mode 100644 index 0000000000..f25a193958 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityBlockquote.html @@ -0,0 +1,152 @@ + + + + + messageEntityBlockquote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBlockquote

+ +

Message entity representing a block quote.

+

+ +
+
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityBotCommand.html b/data/corefork.telegram.org/constructor/messageEntityBotCommand.html new file mode 100644 index 0000000000..6f5f34d79b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityBotCommand.html @@ -0,0 +1,152 @@ + + + + + messageEntityBotCommand + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityBotCommand

+ +

Message entity representing a bot /command

+

+ +
+
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityItalic.html b/data/corefork.telegram.org/constructor/messageEntityItalic.html new file mode 100644 index 0000000000..953abc20c5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityItalic.html @@ -0,0 +1,152 @@ + + + + + messageEntityItalic + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityItalic

+ +

Message entity representing italic text.

+

+ +
+
messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityStrike.html b/data/corefork.telegram.org/constructor/messageEntityStrike.html new file mode 100644 index 0000000000..a4879d3178 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityStrike.html @@ -0,0 +1,152 @@ + + + + + messageEntityStrike + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityStrike

+ +

Message entity representing strikethrough text.

+

+ +
+
messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityUnderline.html b/data/corefork.telegram.org/constructor/messageEntityUnderline.html new file mode 100644 index 0000000000..717f79dafe --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityUnderline.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnderline

+ +

Message entity representing underlined text.

+

+ +
+
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageEntityUnknown.html b/data/corefork.telegram.org/constructor/messageEntityUnknown.html new file mode 100644 index 0000000000..832b36a72f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageEntityUnknown.html @@ -0,0 +1,152 @@ + + + + + messageEntityUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

messageEntityUnknown

+ +

Unknown message entity

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
+

Type

+

MessageEntity

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageInteractionCounters.html b/data/corefork.telegram.org/constructor/messageInteractionCounters.html new file mode 100644 index 0000000000..24569b82b1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageInteractionCounters.html @@ -0,0 +1,157 @@ + + + + + messageInteractionCounters + + + + + + + + + + + + + +
+ +
+
+
+ +

messageInteractionCounters

+ +

Message interaction counters

+

+ +
+
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idintMessage ID
viewsintViews
forwardsintNumber of times this message was forwarded
+

Type

+

MessageInteractionCounters

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaDocument.html b/data/corefork.telegram.org/constructor/messageMediaDocument.html new file mode 100644 index 0000000000..7006a9a08a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaDocument.html @@ -0,0 +1,157 @@ + + + + + messageMediaDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaDocument

+ +

Document (video, audio, voice, sticker, any media type except photo)

+

+ +
+
messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
documentflags.0?DocumentAttached document
ttl_secondsflags.2?intTime to live of self-destructing document
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaGame.html b/data/corefork.telegram.org/constructor/messageMediaGame.html new file mode 100644 index 0000000000..e6826ee81a --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaGame.html @@ -0,0 +1,147 @@ + + + + + messageMediaGame + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGame

+ +

Telegram game

+

+ +
+
messageMediaGame#fdb19008 game:Game = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
gameGameGame
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaGeo.html b/data/corefork.telegram.org/constructor/messageMediaGeo.html new file mode 100644 index 0000000000..e74f8053db --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaGeo.html @@ -0,0 +1,147 @@ + + + + + messageMediaGeo + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaGeo

+ +

Attached map.

+

+ +
+
messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
geoGeoPointGeoPoint
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageMediaPhoto.html b/data/corefork.telegram.org/constructor/messageMediaPhoto.html new file mode 100644 index 0000000000..34082f6f99 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageMediaPhoto.html @@ -0,0 +1,157 @@ + + + + + messageMediaPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messageMediaPhoto

+ +

Attached photo.

+

+ +
+
messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
photoflags.0?PhotoPhoto
ttl_secondsflags.2?intTime to live in seconds of self-destructing photo
+

Type

+

MessageMedia

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageRange.html b/data/corefork.telegram.org/constructor/messageRange.html new file mode 100644 index 0000000000..92ed7ee853 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageRange.html @@ -0,0 +1,152 @@ + + + + + messageRange + + + + + + + + + + + + + +
+ +
+
+
+ +

messageRange

+ +

Indicates a range of chat messages

+

+ +
+
messageRange#ae30253 min_id:int max_id:int = MessageRange;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
min_idintStart of range (message ID)
max_idintEnd of range (message ID)
+

Type

+

MessageRange

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageReplies.html b/data/corefork.telegram.org/constructor/messageReplies.html new file mode 100644 index 0000000000..9af23fc961 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageReplies.html @@ -0,0 +1,189 @@ + + + + + messageReplies + + + + + + + + + + + + + +
+ +
+
+
+ +

messageReplies

+ +

Info about the comment section of a channel post, or a simple message thread

+

+ +
+
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
commentsflags.0?trueWhether this constructor contains information about the comment section of a channel post, or a simple message thread
repliesintContains the total number of replies in this thread or comment section.
replies_ptsintPTS of the message that started this thread.
recent_repliersflags.1?Vector<Peer>For channel post comments, contains information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.
channel_idflags.0?longFor channel post comments, contains the ID of the associated discussion supergroup
max_idflags.2?intID of the latest message in this thread or comment section.
read_max_idflags.3?intContains the ID of the latest read message in this thread or comment section.
+

Type

+

MessageReplies

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageService.html b/data/corefork.telegram.org/constructor/messageService.html new file mode 100644 index 0000000000..cd5703d77e --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageService.html @@ -0,0 +1,212 @@ + + + + + messageService + + + + + + + + + + + + + +
+ +
+
+
+ +

messageService

+ +

Indicates a service message

+

+ +
+
messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether the message contains unread media
silentflags.13?trueWhether the message is silent
postflags.14?trueWhether it's a channel post
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
idintMessage ID
from_idflags.8?PeerID of the sender of this message
peer_idPeerSender of service message
reply_toflags.3?MessageReplyHeaderReply (thread) information
dateintMessage date
actionMessageActionEvent connected with the service message
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageUserVote.html b/data/corefork.telegram.org/constructor/messageUserVote.html new file mode 100644 index 0000000000..1b61c472ff --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageUserVote.html @@ -0,0 +1,157 @@ + + + + + messageUserVote + + + + + + + + + + + + + +
+ +
+
+
+ +

messageUserVote

+ +

How a user voted in a poll

+

+ +
+
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser ID
optionbytesThe option chosen by the user
dateintWhen did the user cast the vote
+

Type

+

MessageUserVote

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messageViews.html b/data/corefork.telegram.org/constructor/messageViews.html new file mode 100644 index 0000000000..52706c2ae1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messageViews.html @@ -0,0 +1,165 @@ + + + + + messageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messageViews

+ +

View, forward counter + info about replies of a specific message

+

+ +
+
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
viewsflags.0?intViewcount of message
forwardsflags.1?intForward count of message
repliesflags.2?MessageRepliesReply and thread information of message
+

Type

+

MessageViews

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.affectedFoundMessages b/data/corefork.telegram.org/constructor/messages.affectedFoundMessages new file mode 100644 index 0000000000..dea499bc7f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.affectedFoundMessages @@ -0,0 +1,165 @@ + + + + + messages.affectedFoundMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedFoundMessages

+ +

Messages found and affected by changes

+

+ +
+
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
offsetintIf bigger than zero, the request must be repeated to remove more messages
messagesVector<int>Affected message IDs
+

Type

+

messages.AffectedFoundMessages

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.affectedHistory b/data/corefork.telegram.org/constructor/messages.affectedHistory new file mode 100644 index 0000000000..2c0bbb68ca --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.affectedHistory @@ -0,0 +1,157 @@ + + + + + messages.affectedHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.affectedHistory

+ +

Affected part of communication history with the user or in a chat.

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
ptsintNumber of events occured in a text box
pts_countintNumber of affected events
offsetintIf a parameter contains positive value, it is necessary to repeat the method call using the given value; during the proceeding of all the history the value itself shall gradually decrease
+

Type

+

messages.AffectedHistory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.allStickersNotModified b/data/corefork.telegram.org/constructor/messages.allStickersNotModified new file mode 100644 index 0000000000..9de6798689 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.allStickersNotModified @@ -0,0 +1,132 @@ + + + + + messages.allStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.allStickersNotModified

+ +

Info about all installed stickers hasn't changed

+

+ +
+
messages.allStickersNotModified#e86602c3 = messages.AllStickers;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.AllStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.archivedStickers b/data/corefork.telegram.org/constructor/messages.archivedStickers new file mode 100644 index 0000000000..082d3d70fc --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.archivedStickers @@ -0,0 +1,152 @@ + + + + + messages.archivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.archivedStickers

+ +

Archived stickersets

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of archived stickers
setsVector<StickerSetCovered>Archived stickersets
+

Type

+

messages.ArchivedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.availableReactionsNotModified b/data/corefork.telegram.org/constructor/messages.availableReactionsNotModified new file mode 100644 index 0000000000..7ba65c9b47 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.availableReactionsNotModified @@ -0,0 +1,137 @@ + + + + + messages.availableReactionsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.availableReactionsNotModified

+ +

+ +
+
messages.availableReactionsNotModified#9f071957 = messages.AvailableReactions;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.AvailableReactions

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.botCallbackAnswer b/data/corefork.telegram.org/constructor/messages.botCallbackAnswer new file mode 100644 index 0000000000..b9ab7e8065 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.botCallbackAnswer @@ -0,0 +1,177 @@ + + + + + messages.botCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.botCallbackAnswer

+ +

Callback answer sent by the bot in response to a button press

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether an alert should be shown to the user instead of a toast notification
has_urlflags.3?trueWhether an URL is present
native_uiflags.4?trueWhether to show games in WebView or in native UI.
messageflags.0?stringAlert to show
urlflags.2?stringURL to open
cache_timeintFor how long should this answer be cached
+

Type

+

messages.BotCallbackAnswer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.botResults b/data/corefork.telegram.org/constructor/messages.botResults new file mode 100644 index 0000000000..a55ead271c --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.botResults @@ -0,0 +1,182 @@ + + + + + messages.botResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.botResults

+ +

Result of a query to an inline bot

+

+ +
+
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueWhether the result is a picture gallery
query_idlongQuery ID
next_offsetflags.1?stringThe next offset to use when navigating through results
switch_pmflags.2?InlineBotSwitchPMWhether the bot requested the user to message him in private
resultsVector<BotInlineResult>The results
cache_timeintCaching validity of the results
usersVector<User>Users mentioned in the results
+

Type

+

messages.BotResults

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites b/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites new file mode 100644 index 0000000000..a7b1573da6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites @@ -0,0 +1,152 @@ + + + + + messages.chatAdminsWithInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatAdminsWithInvites

+ +

Info about chat invites generated by admins.

+

+ +
+
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
adminsVector<ChatAdminWithInvites>Info about chat invites generated by admins.
usersVector<User>Mentioned users
+

Type

+

messages.ChatAdminsWithInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.chatFull b/data/corefork.telegram.org/constructor/messages.chatFull new file mode 100644 index 0000000000..23999c990b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.chatFull @@ -0,0 +1,157 @@ + + + + + messages.chatFull + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.chatFull

+ +

Extended info on chat and auxiliary data.

+

+ +
+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
full_chatChatFullExtended info on a chat
chatsVector<Chat>List containing basic info on chat
usersVector<User>List of users mentioned above
+

Type

+

messages.ChatFull

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.dialogsNotModified b/data/corefork.telegram.org/constructor/messages.dialogsNotModified new file mode 100644 index 0000000000..3ab5ce9f90 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.dialogsNotModified @@ -0,0 +1,147 @@ + + + + + messages.dialogsNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.dialogsNotModified

+ +

Dialogs haven't changed

+

+ +
+
messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of dialogs found server-side by the query
+

Type

+

messages.Dialogs

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.discussionMessage b/data/corefork.telegram.org/constructor/messages.discussionMessage new file mode 100644 index 0000000000..4032d07ff4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.discussionMessage @@ -0,0 +1,185 @@ + + + + + messages.discussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discussionMessage

+ +

Information about a message thread

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
messagesVector<Message>Discussion messages
max_idflags.0?intMessage ID of latest reply in this thread
read_inbox_max_idflags.1?intMessage ID of latest read incoming message in this thread
read_outbox_max_idflags.2?intMessage ID of latest read outgoing message in this thread
unread_countintNumber of unread messages
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
+

Type

+

messages.DiscussionMessage

+

Related pages

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced b/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced new file mode 100644 index 0000000000..1254cb147b --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced @@ -0,0 +1,157 @@ + + + + + messages.exportedChatInviteReplaced + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInviteReplaced

+ +

The specified chat invite was replaced with another one

+

+ +
+
messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
inviteExportedChatInviteThe replaced chat invite
new_inviteExportedChatInviteThe invite that replaces the previous invite
usersVector<User>Mentioned users
+

Type

+

messages.ExportedChatInvite

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInvites b/data/corefork.telegram.org/constructor/messages.exportedChatInvites new file mode 100644 index 0000000000..19b8187639 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.exportedChatInvites @@ -0,0 +1,157 @@ + + + + + messages.exportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.exportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
countintNumber of invites exported by the admin
invitesVector<ExportedChatInvite>Exported invites
usersVector<User>Info about the admin
+

Type

+

messages.ExportedChatInvites

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified b/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified new file mode 100644 index 0000000000..e7b243cc91 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified @@ -0,0 +1,147 @@ + + + + + messages.featuredStickersNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.featuredStickersNotModified

+ +

Featured stickers haven't changed

+

+ +
+
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
countintTotal number of featured stickers
+

Type

+

messages.FeaturedStickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.historyImport b/data/corefork.telegram.org/constructor/messages.historyImport new file mode 100644 index 0000000000..ed9d38806f --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.historyImport @@ -0,0 +1,150 @@ + + + + + messages.historyImport + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.historyImport

+ +

ID of a specific chat import session, click here for more info ».

+

+ +
+
messages.historyImport#1662af0b id:long = messages.HistoryImport;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongHistory import ID
+

Type

+

messages.HistoryImport

+

Related pages

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.inactiveChats b/data/corefork.telegram.org/constructor/messages.inactiveChats new file mode 100644 index 0000000000..d2884cd8e3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.inactiveChats @@ -0,0 +1,157 @@ + + + + + messages.inactiveChats + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.inactiveChats

+ +

Inactive chat list

+

+ +
+
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
datesVector<int>When was the chat last active
chatsVector<Chat>Chat list
usersVector<User>Users mentioned in the chat list
+

Type

+

messages.InactiveChats

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messages b/data/corefork.telegram.org/constructor/messages.messages new file mode 100644 index 0000000000..03b55922b8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messages @@ -0,0 +1,157 @@ + + + + + messages.messages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messages

+ +

Full list of messages with auxilary data.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.messagesSlice b/data/corefork.telegram.org/constructor/messages.messagesSlice new file mode 100644 index 0000000000..5d939264e0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.messagesSlice @@ -0,0 +1,185 @@ + + + + + messages.messagesSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.messagesSlice

+ +

Incomplete list of messages and auxiliary data.

+

+ +
+
messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, indicates that the results may be inexact
countintTotal number of messages in the list
next_rateflags.0?intRate to use in the offset_rate parameter in the next call to messages.searchGlobal
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in messages
usersVector<User>List of users mentioned in messages and chats
+

Type

+

messages.Messages

+

Related pages

+

messages.searchGlobal

+

Search for messages and peers globally

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.savedGifs b/data/corefork.telegram.org/constructor/messages.savedGifs new file mode 100644 index 0000000000..59149952ec --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.savedGifs @@ -0,0 +1,155 @@ + + + + + messages.savedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.savedGifs

+ +

Saved gifs

+

+ +
+
messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
gifsVector<Document>List of saved gifs
+

Type

+

messages.SavedGifs

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.sponsoredMessages b/data/corefork.telegram.org/constructor/messages.sponsoredMessages new file mode 100644 index 0000000000..661ec152cc --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.sponsoredMessages @@ -0,0 +1,157 @@ + + + + + messages.sponsoredMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sponsoredMessages

+ +

A set of sponsored messages associated to a channel

+

+ +
+
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messagesVector<SponsoredMessage>Sponsored messages
chatsVector<Chat>Chats mentioned in the sponsored messages
usersVector<User>Users mentioned in the sponsored messages
+

Type

+

messages.SponsoredMessages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.stickerSetNotModified b/data/corefork.telegram.org/constructor/messages.stickerSetNotModified new file mode 100644 index 0000000000..44446a1920 --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.stickerSetNotModified @@ -0,0 +1,137 @@ + + + + + messages.stickerSetNotModified + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.stickerSetNotModified

+ +

+ +
+
messages.stickerSetNotModified#d3f924eb = messages.StickerSet;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

messages.StickerSet

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/messages.votesList b/data/corefork.telegram.org/constructor/messages.votesList new file mode 100644 index 0000000000..a5eaa4274e --- /dev/null +++ b/data/corefork.telegram.org/constructor/messages.votesList @@ -0,0 +1,170 @@ + + + + + messages.votesList + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.votesList

+ +

How users voted in a poll

+

+ +
+
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
countintTotal number of votes for all options (or only for the chosen option, if provided to messages.getPollVotes)
votesVector<MessageUserVote>Vote info for each user
usersVector<User>Info about users that voted in the poll
next_offsetflags.0?stringOffset to use with the next messages.getPollVotes request, empty string if no more results are available.
+

Type

+

messages.VotesList

+

Related pages

+

messages.getPollVotes

+

Get poll results for non-anonymous polls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/notifyPeer.html b/data/corefork.telegram.org/constructor/notifyPeer.html new file mode 100644 index 0000000000..569fa22500 --- /dev/null +++ b/data/corefork.telegram.org/constructor/notifyPeer.html @@ -0,0 +1,147 @@ + + + + + notifyPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

notifyPeer

+ +

Notifications generated by a certain user or group.

+

+ +
+
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerPeeruser or group
+

Type

+

NotifyPeer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockCover.html b/data/corefork.telegram.org/constructor/pageBlockCover.html new file mode 100644 index 0000000000..b440f32ba3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockCover.html @@ -0,0 +1,147 @@ + + + + + pageBlockCover + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockCover

+ +

A page cover

+

+ +
+
pageBlockCover#39f23300 cover:PageBlock = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
coverPageBlockCover
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockDivider.html b/data/corefork.telegram.org/constructor/pageBlockDivider.html new file mode 100644 index 0000000000..b1c5bec0a8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockDivider.html @@ -0,0 +1,132 @@ + + + + + pageBlockDivider + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockDivider

+ +

An empty block separating a page

+

+ +
+
pageBlockDivider#db20b188 = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockList.html b/data/corefork.telegram.org/constructor/pageBlockList.html new file mode 100644 index 0000000000..33f89d9971 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockList.html @@ -0,0 +1,147 @@ + + + + + pageBlockList + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockList

+ +

Unordered list of IV blocks

+

+ +
+
pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
itemsVector<PageListItem>List of blocks in an IV page
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockPullquote.html b/data/corefork.telegram.org/constructor/pageBlockPullquote.html new file mode 100644 index 0000000000..d8e1cf0599 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockPullquote.html @@ -0,0 +1,152 @@ + + + + + pageBlockPullquote + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockPullquote

+ +

Pullquote

+

+ +
+
pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
captionRichTextCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockSubtitle.html b/data/corefork.telegram.org/constructor/pageBlockSubtitle.html new file mode 100644 index 0000000000..2de5daffd4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockSubtitle.html @@ -0,0 +1,147 @@ + + + + + pageBlockSubtitle + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockSubtitle

+ +

Subtitle

+

+ +
+
pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockTable.html b/data/corefork.telegram.org/constructor/pageBlockTable.html new file mode 100644 index 0000000000..6d5c1aaf37 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockTable.html @@ -0,0 +1,167 @@ + + + + + pageBlockTable + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockTable

+ +

Table

+

+ +
+
pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
borderedflags.0?trueDoes the table have a visible border?
stripedflags.1?trueIs the table striped?
titleRichTextTitle
rowsVector<PageTableRow>Table rows
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockUnsupported.html b/data/corefork.telegram.org/constructor/pageBlockUnsupported.html new file mode 100644 index 0000000000..d5bd8ff5a5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockUnsupported.html @@ -0,0 +1,132 @@ + + + + + pageBlockUnsupported + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockUnsupported

+ +

Unsupported IV element

+

+ +
+
pageBlockUnsupported#13567e8a = PageBlock;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockVideo.html b/data/corefork.telegram.org/constructor/pageBlockVideo.html new file mode 100644 index 0000000000..62e96aa40c --- /dev/null +++ b/data/corefork.telegram.org/constructor/pageBlockVideo.html @@ -0,0 +1,167 @@ + + + + + pageBlockVideo + + + + + + + + + + + + + +
+ +
+
+
+ +

pageBlockVideo

+ +

Video

+

+ +
+
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
+

Type

+

PageBlock

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/paymentCharge.html b/data/corefork.telegram.org/constructor/paymentCharge.html new file mode 100644 index 0000000000..4363457435 --- /dev/null +++ b/data/corefork.telegram.org/constructor/paymentCharge.html @@ -0,0 +1,152 @@ + + + + + paymentCharge + + + + + + + + + + + + + +
+ +
+
+
+ +

paymentCharge

+ +

Payment identifier

+

+ +
+
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idstringTelegram payment identifier
provider_charge_idstringProvider payment identifier
+

Type

+

PaymentCharge

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded b/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded new file mode 100644 index 0000000000..d5b81908d6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded @@ -0,0 +1,147 @@ + + + + + payments.paymentVerificationNeeded + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.paymentVerificationNeeded

+ +

Payment was not successful, additional verification is needed

+

+ +
+
payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL for additional payment credentials verification
+

Type

+

payments.PaymentResult

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerChannel.html b/data/corefork.telegram.org/constructor/peerChannel.html new file mode 100644 index 0000000000..593dca34fe --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerChannel.html @@ -0,0 +1,147 @@ + + + + + peerChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

peerChannel

+ +

Channel/supergroup

+

+ +
+
peerChannel#a2a5371e channel_id:long = Peer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
+

Type

+

Peer

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerNotifySettings.html b/data/corefork.telegram.org/constructor/peerNotifySettings.html new file mode 100644 index 0000000000..c202284e63 --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerNotifySettings.html @@ -0,0 +1,182 @@ + + + + + peerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

peerNotifySettings

+ +

Notification settings.

+

+ +
+
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolDisplay text in notifications
silentflags.1?BoolMute peer?
mute_untilflags.2?intMute all notifications until this date
soundflags.3?stringAudio file name for notifications
+

Type

+

PeerNotifySettings

+

Event flags (events_mask)

+ + + + + + + + + + + + + +
0x00000001Profile photo update notification
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/peerSettings.html b/data/corefork.telegram.org/constructor/peerSettings.html new file mode 100644 index 0000000000..c4b351bdf5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/peerSettings.html @@ -0,0 +1,212 @@ + + + + + peerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

peerSettings

+ +

Peer settings

+

+ +
+
peerSettings#a518110d flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true request_chat_broadcast:flags.10?true geo_distance:flags.6?int request_chat_title:flags.9?string request_chat_date:flags.9?int = PeerSettings;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
report_spamflags.0?trueWhether we can still report the user for spam
add_contactflags.1?trueWhether we can add the user as contact
block_contactflags.2?trueWhether we can block the user
share_contactflags.3?trueWhether we can share the user's contact
need_contacts_exceptionflags.4?trueWhether a special exception for contacts is needed
report_geoflags.5?trueWhether we can report a geogroup is irrelevant for this location
autoarchivedflags.7?trueWhether this peer was automatically archived according to privacy settings
invite_membersflags.8?trueWhether we can invite members to a group or channel
request_chat_broadcastflags.10?true 
geo_distanceflags.6?intDistance in meters between us and this peer
request_chat_titleflags.9?string 
request_chat_dateflags.9?int 
+

Type

+

PeerSettings

+

Related pages

+

globalPrivacySettings

+

Global privacy settings

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phone.phoneCall b/data/corefork.telegram.org/constructor/phone.phoneCall new file mode 100644 index 0000000000..d45b9a382c --- /dev/null +++ b/data/corefork.telegram.org/constructor/phone.phoneCall @@ -0,0 +1,152 @@ + + + + + phone.phoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.phoneCall

+ +

A VoIP phone call

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_callPhoneCallThe VoIP phone call
usersVector<User>VoIP phone call participants
+

Type

+

phone.PhoneCall

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html new file mode 100644 index 0000000000..8c84251a66 --- /dev/null +++ b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html @@ -0,0 +1,132 @@ + + + + + phoneCallDiscardReasonHangup + + + + + + + + + + + + + +
+ +
+
+
+ +

phoneCallDiscardReasonHangup

+ +

The phone call was ended normally

+

+ +
+
phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PhoneCallDiscardReason

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoCachedSize.html b/data/corefork.telegram.org/constructor/photoCachedSize.html new file mode 100644 index 0000000000..4b64ee6e8d --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoCachedSize.html @@ -0,0 +1,167 @@ + + + + + photoCachedSize + + + + + + + + + + + + + +
+ +
+
+
+ +

photoCachedSize

+ +

Description of an image and its content.

+

+ +
+
photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
bytesbytesBinary data, file content
+

Type

+

PhotoSize

+

Thumbnail type and its sizes

+

See here.

+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photoSizeEmpty.html b/data/corefork.telegram.org/constructor/photoSizeEmpty.html new file mode 100644 index 0000000000..35abc8148f --- /dev/null +++ b/data/corefork.telegram.org/constructor/photoSizeEmpty.html @@ -0,0 +1,150 @@ + + + + + photoSizeEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

photoSizeEmpty

+ +

Empty constructor. Image with this thumbnail is unavailable.

+

+ +
+
photoSizeEmpty#e17e23c type:string = PhotoSize;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typestringThumbnail type (see. photoSize)
+

Type

+

PhotoSize

+

Related pages

+

photoSize

+

Image description.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/photos.photos b/data/corefork.telegram.org/constructor/photos.photos new file mode 100644 index 0000000000..ac5a0d4ffe --- /dev/null +++ b/data/corefork.telegram.org/constructor/photos.photos @@ -0,0 +1,152 @@ + + + + + photos.photos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.photos

+ +

Full list of photos with auxiliary data.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
+

Type

+

photos.Photos

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/pollAnswer.html b/data/corefork.telegram.org/constructor/pollAnswer.html new file mode 100644 index 0000000000..63025921ce --- /dev/null +++ b/data/corefork.telegram.org/constructor/pollAnswer.html @@ -0,0 +1,155 @@ + + + + + pollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

pollAnswer

+ +

A possible answer of a poll

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
+

Type

+

PollAnswer

+

Related pages

+

messages.sendVote

+

Vote in a poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html b/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html new file mode 100644 index 0000000000..45c212d6f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html @@ -0,0 +1,132 @@ + + + + + privacyKeyChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyChatInvite

+ +

Whether the user can be invited to chats

+

+ +
+
privacyKeyChatInvite#500e6dfa = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html b/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html new file mode 100644 index 0000000000..fb45419330 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html @@ -0,0 +1,132 @@ + + + + + privacyKeyPhoneP2P + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyKeyPhoneP2P

+ +

Whether P2P connections in phone calls are allowed

+

+ +
+
privacyKeyPhoneP2P#39491cc8 = PrivacyKey;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

PrivacyKey

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html b/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html new file mode 100644 index 0000000000..d67e987d70 --- /dev/null +++ b/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html @@ -0,0 +1,147 @@ + + + + + privacyValueDisallowUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

privacyValueDisallowUsers

+ +

Disallow only certain users

+

+ +
+
privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<long>Disallowed users
+

Type

+

PrivacyRule

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html b/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html new file mode 100644 index 0000000000..1d078b50bf --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlChatInvite

+ +

Recent t.me invite link to a chat

+

+ +
+
recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
chat_inviteChatInviteChat invitation
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html b/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html new file mode 100644 index 0000000000..15075a6940 --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlStickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlStickerSet

+ +

Recent t.me stickerset installation URL

+

+ +
+
recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringt.me URL
setStickerSetCoveredStickerset
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html b/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html new file mode 100644 index 0000000000..1b6f4ce231 --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html @@ -0,0 +1,147 @@ + + + + + recentMeUrlUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUnknown

+ +

Unknown t.me url

+

+ +
+
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/recentMeUrlUser.html b/data/corefork.telegram.org/constructor/recentMeUrlUser.html new file mode 100644 index 0000000000..604cfca243 --- /dev/null +++ b/data/corefork.telegram.org/constructor/recentMeUrlUser.html @@ -0,0 +1,152 @@ + + + + + recentMeUrlUser + + + + + + + + + + + + + +
+ +
+
+
+ +

recentMeUrlUser

+ +

Recent t.me link to a user

+

+ +
+
recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL
user_idlongUser ID
+

Type

+

RecentMeUrl

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html b/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html new file mode 100644 index 0000000000..25c5c2a1b3 --- /dev/null +++ b/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html @@ -0,0 +1,172 @@ + + + + + replyKeyboardMarkup + + + + + + + + + + + + + +
+ +
+
+
+ +

replyKeyboardMarkup

+ +

Bot keyboard

+

+ +
+
replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
resizeflags.0?trueRequests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). If not set, the custom keyboard is always of the same height as the app's standard keyboard.
single_useflags.1?trueRequests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again.
selectiveflags.2?trueUse this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
rowsVector<KeyboardButtonRow>Button row
placeholderflags.3?stringThe placeholder to be shown in the input field when the keyboard is active; 1-64 characters.
+

Type

+

ReplyMarkup

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/searchResultPosition.html b/data/corefork.telegram.org/constructor/searchResultPosition.html new file mode 100644 index 0000000000..3e5d9761c4 --- /dev/null +++ b/data/corefork.telegram.org/constructor/searchResultPosition.html @@ -0,0 +1,184 @@ + + + + + searchResultPosition + + + + + + + + + + + + + +
+ +
+
+
+ +

searchResultPosition

+ +

+ +
+
searchResultPosition#7f648b67 msg_id:int date:int offset:int = SearchResultsPosition;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idint 
dateint 
offsetint 
+

Type

+

SearchResultsPosition

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/searchResultsCalendarPeriod.html b/data/corefork.telegram.org/constructor/searchResultsCalendarPeriod.html new file mode 100644 index 0000000000..f3d7b39cfd --- /dev/null +++ b/data/corefork.telegram.org/constructor/searchResultsCalendarPeriod.html @@ -0,0 +1,195 @@ + + + + + searchResultsCalendarPeriod + + + + + + + + + + + + + +
+ +
+
+
+ +

searchResultsCalendarPeriod

+ +

+ +
+
searchResultsCalendarPeriod#c9b0539f date:int min_msg_id:int max_msg_id:int count:int = SearchResultsCalendarPeriod;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
dateint 
min_msg_idint 
max_msg_idint 
countint 
+

Type

+

SearchResultsCalendarPeriod

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureData.html b/data/corefork.telegram.org/constructor/secureData.html new file mode 100644 index 0000000000..b3b875408b --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureData.html @@ -0,0 +1,160 @@ + + + + + secureData + + + + + + + + + + + + + +
+ +
+
+
+ +

secureData

+ +

Secure passport data, for more info see the passport docs »

+

+ +
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
databytesData
data_hashbytesData hash
secretbytesSecret
+

Type

+

SecureData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureFileEmpty.html b/data/corefork.telegram.org/constructor/secureFileEmpty.html new file mode 100644 index 0000000000..c0cfd18b5c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureFileEmpty.html @@ -0,0 +1,132 @@ + + + + + secureFileEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

secureFileEmpty

+ +

Empty constructor

+

+ +
+
secureFileEmpty#64199744 = SecureFile;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureFile

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html new file mode 100644 index 0000000000..51e3bb8a17 --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html @@ -0,0 +1,132 @@ + + + + + securePasswordKdfAlgoUnknown + + + + + + + + + + + + + +
+ +
+
+
+ +

securePasswordKdfAlgoUnknown

+ +

Unknown KDF algo (most likely the client has to be updated)

+

+ +
+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecurePasswordKdfAlgo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/securePlainPhone.html b/data/corefork.telegram.org/constructor/securePlainPhone.html new file mode 100644 index 0000000000..cab5dd85eb --- /dev/null +++ b/data/corefork.telegram.org/constructor/securePlainPhone.html @@ -0,0 +1,150 @@ + + + + + securePlainPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

securePlainPhone

+ +

Phone number to use in telegram passport: it must be verified, first ».

+

+ +
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonestringPhone number
+

Type

+

SecurePlainData

+

Related pages

+

Telegram Passport Manual

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html b/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html new file mode 100644 index 0000000000..4c29ba89d5 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html @@ -0,0 +1,147 @@ + + + + + secureRequiredTypeOneOf + + + + + + + + + + + + + +
+ +
+
+
+ +

secureRequiredTypeOneOf

+ +

One of

+

+ +
+
secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
typesVector<SecureRequiredType>Secure required value types
+

Type

+

SecureRequiredType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFiles.html b/data/corefork.telegram.org/constructor/secureValueErrorFiles.html new file mode 100644 index 0000000000..6caf089d75 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorFiles.html @@ -0,0 +1,168 @@ + + + + + secureValueErrorFiles + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFiles

+ +

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

+

+ +
+
secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>File hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeUtilityBill

+

Utility bill

+

secureValueTypeBankStatement

+

Bank statement

+

secureValueTypeRentalAgreement

+

Rental agreement

+

secureValueTypePassportRegistration

+

Internal registration passport

+

secureValueTypeTemporaryRegistration

+

Temporary registration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html b/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html new file mode 100644 index 0000000000..888550f63a --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html @@ -0,0 +1,166 @@ + + + + + secureValueErrorFrontSide + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorFrontSide

+ +

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

+

+ +
+
secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypePassport

+

Passport

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+

secureValueTypeInternalPassport

+

Internal passport

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html b/data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html new file mode 100644 index 0000000000..edb6a50bc8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html @@ -0,0 +1,162 @@ + + + + + secureValueErrorReverseSide + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueErrorReverseSide

+ +

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

+

+ +
+
secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeDriverLicense, secureValueTypeIdentityCard
file_hashbytesFile hash
textstringError message
+

Type

+

SecureValueError

+

Related pages

+

secureValueTypeDriverLicense

+

Driver's license

+

secureValueTypeIdentityCard

+

Identity card

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html b/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html new file mode 100644 index 0000000000..0d88f6837a --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeBankStatement + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeBankStatement

+ +

Bank statement

+

+ +
+
secureValueTypeBankStatement#89137c0d = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html b/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html new file mode 100644 index 0000000000..98305b3095 --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html @@ -0,0 +1,132 @@ + + + + + secureValueTypePersonalDetails + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypePersonalDetails

+ +

Personal details

+

+ +
+
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html new file mode 100644 index 0000000000..b5deaa7a0c --- /dev/null +++ b/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html @@ -0,0 +1,132 @@ + + + + + secureValueTypeTemporaryRegistration + + + + + + + + + + + + + +
+ +
+
+
+ +

secureValueTypeTemporaryRegistration

+ +

Temporary registration

+

+ +
+
secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SecureValueType

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html b/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html new file mode 100644 index 0000000000..1cd23f46ba --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageGeoLocationAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageGeoLocationAction

+ +

User is selecting a location to share.

+

+ +
+
sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageTypingAction.html b/data/corefork.telegram.org/constructor/sendMessageTypingAction.html new file mode 100644 index 0000000000..47e38445de --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageTypingAction.html @@ -0,0 +1,132 @@ + + + + + sendMessageTypingAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageTypingAction

+ +

User is typing.

+

+ +
+
sendMessageTypingAction#16bf744e = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html new file mode 100644 index 0000000000..0729359f3e --- /dev/null +++ b/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html @@ -0,0 +1,147 @@ + + + + + sendMessageUploadDocumentAction + + + + + + + + + + + + + +
+ +
+
+
+ +

sendMessageUploadDocumentAction

+ +

User is uploading a file.

+

+ +
+
sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
progressintProgress percentage
+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html b/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html new file mode 100644 index 0000000000..d98f7a1604 --- /dev/null +++ b/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html @@ -0,0 +1,132 @@ + + + + + speakingInGroupCallAction + + + + + + + + + + + + + +
+ +
+
+
+ +

speakingInGroupCallAction

+ +

User is currently speaking in the group call

+

+ +
+
speakingInGroupCallAction#d92c2285 = SendMessageAction;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

SendMessageAction

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stats.broadcastStats b/data/corefork.telegram.org/constructor/stats.broadcastStats new file mode 100644 index 0000000000..0c4527026b --- /dev/null +++ b/data/corefork.telegram.org/constructor/stats.broadcastStats @@ -0,0 +1,220 @@ + + + + + stats.broadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.broadcastStats

+ +

Channel statistics.

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
+

Type

+

stats.BroadcastStats

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsGraphAsync.html b/data/corefork.telegram.org/constructor/statsGraphAsync.html new file mode 100644 index 0000000000..c572f53904 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsGraphAsync.html @@ -0,0 +1,152 @@ + + + + + statsGraphAsync + + + + + + + + + + + + + +
+ +
+
+
+ +

statsGraphAsync

+ +

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenstringToken to use for fetching the async graph
+

Type

+

StatsGraph

+

Related pages

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

stats.loadAsyncGraph

+

Load channel statistics graph asynchronously

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/statsURL.html b/data/corefork.telegram.org/constructor/statsURL.html new file mode 100644 index 0000000000..625eb78842 --- /dev/null +++ b/data/corefork.telegram.org/constructor/statsURL.html @@ -0,0 +1,147 @@ + + + + + statsURL + + + + + + + + + + + + + +
+ +
+
+
+ +

statsURL

+ +

URL with chat statistics

+

+ +
+
statsURL#47a971e0 url:string = StatsURL;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
urlstringChat statistics
+

Type

+

StatsURL

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickerSetCovered.html b/data/corefork.telegram.org/constructor/stickerSetCovered.html new file mode 100644 index 0000000000..4de12252d1 --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickerSetCovered.html @@ -0,0 +1,152 @@ + + + + + stickerSetCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSetCovered

+ +

Stickerset, with a specific sticker as preview

+

+ +
+
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetStickerset
coverDocumentPreview
+

Type

+

StickerSetCovered

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html b/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html new file mode 100644 index 0000000000..f8247c766e --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html @@ -0,0 +1,152 @@ + + + + + stickerSetMultiCovered + + + + + + + + + + + + + +
+ +
+
+
+ +

stickerSetMultiCovered

+ +

Stickerset, with a specific stickers as preview

+

+ +
+
stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
setStickerSetStickerset
coversVector<Document>Preview stickers
+

Type

+

StickerSetCovered

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/stickers.suggestedShortName b/data/corefork.telegram.org/constructor/stickers.suggestedShortName new file mode 100644 index 0000000000..3e4e9e2b3b --- /dev/null +++ b/data/corefork.telegram.org/constructor/stickers.suggestedShortName @@ -0,0 +1,147 @@ + + + + + stickers.suggestedShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.suggestedShortName

+ +

A suggested short name for a stickerpack

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
short_namestringSuggested short name
+

Type

+

stickers.SuggestedShortName

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textAnchor.html b/data/corefork.telegram.org/constructor/textAnchor.html new file mode 100644 index 0000000000..4642cc9d10 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textAnchor.html @@ -0,0 +1,152 @@ + + + + + textAnchor + + + + + + + + + + + + + +
+ +
+
+
+ +

textAnchor

+ +

Text linking to another section of the page

+

+ +
+
textAnchor#35553762 text:RichText name:string = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
namestringSection name
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textItalic.html b/data/corefork.telegram.org/constructor/textItalic.html new file mode 100644 index 0000000000..e9cb30ac53 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textItalic.html @@ -0,0 +1,147 @@ + + + + + textItalic + + + + + + + + + + + + + +
+ +
+
+
+ +

textItalic

+ +

Italic text

+

+ +
+
textItalic#d912a59c text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textUnderline.html b/data/corefork.telegram.org/constructor/textUnderline.html new file mode 100644 index 0000000000..71ba552750 --- /dev/null +++ b/data/corefork.telegram.org/constructor/textUnderline.html @@ -0,0 +1,147 @@ + + + + + textUnderline + + + + + + + + + + + + + +
+ +
+
+
+ +

textUnderline

+ +

Underlined text

+

+ +
+
textUnderline#c12622c4 text:RichText = RichText;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/textUrl.html b/data/corefork.telegram.org/constructor/textUrl.html new file mode 100644 index 0000000000..88b44dcf3f --- /dev/null +++ b/data/corefork.telegram.org/constructor/textUrl.html @@ -0,0 +1,157 @@ + + + + + textUrl + + + + + + + + + + + + + +
+ +
+
+
+ +

textUrl

+ +

Link

+

+ +
+
textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
textRichTextText of link
urlstringWebpage HTTP URL
webpage_idlongIf a preview was already generated for the page, the page ID
+

Type

+

RichText

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html new file mode 100644 index 0000000000..6b0c909888 --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html @@ -0,0 +1,132 @@ + + + + + topPeerCategoryForwardUsers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryForwardUsers

+ +

Users to which the users often forwards messages to

+

+ +
+
topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

TopPeerCategory

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html b/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html new file mode 100644 index 0000000000..f4dd22ec97 --- /dev/null +++ b/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html @@ -0,0 +1,157 @@ + + + + + topPeerCategoryPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

topPeerCategoryPeers

+ +

Top peer category

+

+ +
+
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
categoryTopPeerCategoryTop peer category of peers
countintCount of peers
peersVector<TopPeer>Peers
+

Type

+

TopPeerCategoryPeers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/true.html b/data/corefork.telegram.org/constructor/true.html new file mode 100644 index 0000000000..815dd56189 --- /dev/null +++ b/data/corefork.telegram.org/constructor/true.html @@ -0,0 +1,134 @@ + + + + + true + + + + + + + + + + + + + +
+ +
+
+
+ +

true

+ +

See predefined identifiers.

+

+ +
+
true#3fedd339 = True;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

True

+

Related pages

+

TL-formal

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html b/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html new file mode 100644 index 0000000000..789bd0bd72 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotChatInviteRequester.html @@ -0,0 +1,211 @@ + + + + + updateBotChatInviteRequester + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotChatInviteRequester

+ +

+ +
+
updateBotChatInviteRequester#11dfa986 peer:Peer date:int user_id:long about:string invite:ExportedChatInvite qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeer 
dateint 
user_idlong 
aboutstring 
inviteExportedChatInvite 
qtsint 
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateBotShippingQuery.html b/data/corefork.telegram.org/constructor/updateBotShippingQuery.html new file mode 100644 index 0000000000..14b06a612f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateBotShippingQuery.html @@ -0,0 +1,162 @@ + + + + + updateBotShippingQuery + + + + + + + + + + + + + +
+ +
+
+
+ +

updateBotShippingQuery

+ +

This object contains information about an incoming shipping query.

+

+ +
+
updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
shipping_addressPostAddressUser specified shipping address
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelMessageViews.html b/data/corefork.telegram.org/constructor/updateChannelMessageViews.html new file mode 100644 index 0000000000..3e6b9fb346 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelMessageViews.html @@ -0,0 +1,157 @@ + + + + + updateChannelMessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelMessageViews

+ +

The view counter of a message in a channel has changed

+

+ +
+
updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
idintID of the message
viewsintNew view counter
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelParticipant.html b/data/corefork.telegram.org/constructor/updateChannelParticipant.html new file mode 100644 index 0000000000..8108436803 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelParticipant.html @@ -0,0 +1,192 @@ + + + + + updateChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelParticipant

+ +

A participant has left, joined, was banned or admined in a channel or supergroup.

+

+ +
+
updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
dateintDate of the event
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChannelParticipantPrevious participant status
new_participantflags.1?ChannelParticipantNew participant status
inviteflags.2?ExportedChatInviteChat invite used to join the channel/supergroup
qtsintNew qts value, see updates » for more info.
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChannelWebPage.html b/data/corefork.telegram.org/constructor/updateChannelWebPage.html new file mode 100644 index 0000000000..4909eeb55e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChannelWebPage.html @@ -0,0 +1,167 @@ + + + + + updateChannelWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChannelWebPage

+ +

A webpage preview of a link in a channel/supergroup message was generated

+

+ +
+
updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel/supergroup ID
webpageWebPageGenerated webpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateChatParticipants.html b/data/corefork.telegram.org/constructor/updateChatParticipants.html new file mode 100644 index 0000000000..a9a8baf24e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateChatParticipants.html @@ -0,0 +1,147 @@ + + + + + updateChatParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

updateChatParticipants

+ +

Composition of chat participants changed.

+

+ +
+
updateChatParticipants#7761198 participants:ChatParticipants = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
participantsChatParticipantsUpdated chat participants
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateContactsReset.html b/data/corefork.telegram.org/constructor/updateContactsReset.html new file mode 100644 index 0000000000..f964e2a181 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateContactsReset.html @@ -0,0 +1,132 @@ + + + + + updateContactsReset + + + + + + + + + + + + + +
+ +
+
+
+ +

updateContactsReset

+ +

All contacts were deleted

+

+ +
+
updateContactsReset#7084a7be = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDcOptions.html b/data/corefork.telegram.org/constructor/updateDcOptions.html new file mode 100644 index 0000000000..76dec82b14 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDcOptions.html @@ -0,0 +1,147 @@ + + + + + updateDcOptions + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDcOptions

+ +

Changes in the data center configuration options.

+

+ +
+
updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
dc_optionsVector<DcOption>New connection options
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html new file mode 100644 index 0000000000..e263fd3ab7 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html @@ -0,0 +1,167 @@ + + + + + updateDeleteChannelMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDeleteChannelMessages

+ +

Some messages in a supergroup/channel were deleted

+

+ +
+
updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channel_idlongChannel ID
messagesVector<int>IDs of messages that were deleted
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogFilter.html b/data/corefork.telegram.org/constructor/updateDialogFilter.html new file mode 100644 index 0000000000..5b3e02d5f9 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogFilter.html @@ -0,0 +1,160 @@ + + + + + updateDialogFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilter

+ +

A new folder was added

+

+ +
+
updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html b/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html new file mode 100644 index 0000000000..da8c62cdcd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html @@ -0,0 +1,150 @@ + + + + + updateDialogFilterOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

updateDialogFilterOrder

+ +

New folder order

+

+ +
+
updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
orderVector<int>Ordered folder IDs
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateFavedStickers.html b/data/corefork.telegram.org/constructor/updateFavedStickers.html new file mode 100644 index 0000000000..f708009921 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateFavedStickers.html @@ -0,0 +1,135 @@ + + + + + updateFavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

updateFavedStickers

+ +

The list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list

+

+ +
+
updateFavedStickers#e511996d = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+

Related pages

+

messages.getFavedStickers

+

Get faved stickers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateLoginToken.html b/data/corefork.telegram.org/constructor/updateLoginToken.html new file mode 100644 index 0000000000..ae92191ab6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateLoginToken.html @@ -0,0 +1,132 @@ + + + + + updateLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

updateLoginToken

+ +

A login token (for login via QR code) was accepted.

+

+ +
+
updateLoginToken#564fe691 = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateMessagePoll.html b/data/corefork.telegram.org/constructor/updateMessagePoll.html new file mode 100644 index 0000000000..660320a94e --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateMessagePoll.html @@ -0,0 +1,162 @@ + + + + + updateMessagePoll + + + + + + + + + + + + + +
+ +
+
+
+ +

updateMessagePoll

+ +

The results of a poll have changed

+

+ +
+
updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
poll_idlongPoll ID
pollflags.0?PollIf the server knows the client hasn't cached this poll yet, the poll itself
resultsPollResultsNew poll results
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html new file mode 100644 index 0000000000..cfdcbbe951 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html @@ -0,0 +1,162 @@ + + + + + updateNewChannelMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNewChannelMessage

+ +

A new message was sent in a channel/supergroup

+

+ +
+
updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
messageMessageNew message
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateNotifySettings.html b/data/corefork.telegram.org/constructor/updateNotifySettings.html new file mode 100644 index 0000000000..5bee6b9c75 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateNotifySettings.html @@ -0,0 +1,152 @@ + + + + + updateNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

updateNotifySettings

+ +

Changes in notification settings.

+

+ +
+
updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerNotifyPeerNofication source
notify_settingsPeerNotifySettingsNew notification settings
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePendingJoinRequests.html b/data/corefork.telegram.org/constructor/updatePendingJoinRequests.html new file mode 100644 index 0000000000..33daa5a1de --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePendingJoinRequests.html @@ -0,0 +1,184 @@ + + + + + updatePendingJoinRequests + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePendingJoinRequests

+ +

+ +
+
updatePendingJoinRequests#7063c3db peer:Peer requests_pending:int recent_requesters:Vector<long> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerPeer 
requests_pendingint 
recent_requestersVector<long> 
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html new file mode 100644 index 0000000000..4387a7c622 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html @@ -0,0 +1,152 @@ + + + + + updatePhoneCallSignalingData + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePhoneCallSignalingData

+ +

Incoming phone call signaling payload

+

+ +
+
updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_call_idlongPhone call ID
databytesSignaling payload
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updatePinnedMessages.html b/data/corefork.telegram.org/constructor/updatePinnedMessages.html new file mode 100644 index 0000000000..219633fcc8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updatePinnedMessages.html @@ -0,0 +1,175 @@ + + + + + updatePinnedMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

updatePinnedMessages

+ +

Some messages were pinned in a chat

+

+ +
+
updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
peerPeerPeer
messagesVector<int>Message IDs
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html b/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html new file mode 100644 index 0000000000..4e49ec227b --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html @@ -0,0 +1,182 @@ + + + + + updateReadHistoryInbox + + + + + + + + + + + + + +
+ +
+
+
+ +

updateReadHistoryInbox

+ +

Incoming messages were read

+

+ +
+
updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
peerPeerPeer
max_idintMaximum ID of messages read
still_unread_countintNumber of messages that are still unread
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateSavedGifs.html b/data/corefork.telegram.org/constructor/updateSavedGifs.html new file mode 100644 index 0000000000..1a9441de9c --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateSavedGifs.html @@ -0,0 +1,132 @@ + + + + + updateSavedGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

updateSavedGifs

+ +

The saved gif list has changed, the client should refetch it using messages.getSavedGifs

+

+ +
+
updateSavedGifs#9375341e = Update;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateShortChatMessage.html b/data/corefork.telegram.org/constructor/updateShortChatMessage.html new file mode 100644 index 0000000000..ef215c660a --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateShortChatMessage.html @@ -0,0 +1,232 @@ + + + + + updateShortChatMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateShortChatMessage

+ +

Shortened constructor containing info on one new incoming text message from a chat

+

+ +
+
updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether the message contains some unread mentions
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintID of the message
from_idlongID of the sender of the message
chat_idlongID of the chat where the message was sent
messagestringMessage
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply (thread) information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once updateShortChatMessage.date+updateShortChatMessage.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
+

Type

+

Updates

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+

Styled text with message entities

+

How to create styled text with message entities

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html b/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html new file mode 100644 index 0000000000..7fc2c166ec --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html @@ -0,0 +1,157 @@ + + + + + updateStickerSetsOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

updateStickerSetsOrder

+ +

The order of stickersets was changed

+

+ +
+
updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether the updated stickers are mask stickers
orderVector<long>New sticker order by sticker ID
+

Type

+

Update

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserName.html b/data/corefork.telegram.org/constructor/updateUserName.html new file mode 100644 index 0000000000..778275d4c8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserName.html @@ -0,0 +1,167 @@ + + + + + updateUserName + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserName

+ +

Changes the user's first name, last name and username.

+

+ +
+
updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser identifier
first_namestringNew first name. Corresponds to the new value of real_first_name field of the userFull constructor.
last_namestringNew last name. Corresponds to the new value of real_last_name field of the userFull constructor.
usernamestringNew username.
Parameter added in Layer 18.
+

Type

+

Update

+

Related pages

+

userFull

+

Extended user info

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateUserTyping.html b/data/corefork.telegram.org/constructor/updateUserTyping.html new file mode 100644 index 0000000000..caf916f79f --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateUserTyping.html @@ -0,0 +1,155 @@ + + + + + updateUserTyping + + + + + + + + + + + + + +
+ +
+
+
+ +

updateUserTyping

+ +

The user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

+

+ +
+
updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idlongUser id
actionSendMessageActionAction type
Param added in Layer 17.
+

Type

+

Update

+

Related pages

+

Layers

+

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updateWebPage.html b/data/corefork.telegram.org/constructor/updateWebPage.html new file mode 100644 index 0000000000..7c4fccbaa0 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updateWebPage.html @@ -0,0 +1,160 @@ + + + + + updateWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

updateWebPage

+ +

An instant view webpage preview was generated

+

+ +
+
updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
webpageWebPageWebpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
+

Type

+

Update

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.differenceSlice b/data/corefork.telegram.org/constructor/updates.differenceSlice new file mode 100644 index 0000000000..153b8761f6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.differenceSlice @@ -0,0 +1,175 @@ + + + + + updates.differenceSlice + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceSlice

+ +

Incomplete list of occurred events.

+

+ +
+
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/updates.differenceTooLong b/data/corefork.telegram.org/constructor/updates.differenceTooLong new file mode 100644 index 0000000000..e72286ccdd --- /dev/null +++ b/data/corefork.telegram.org/constructor/updates.differenceTooLong @@ -0,0 +1,150 @@ + + + + + updates.differenceTooLong + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.differenceTooLong

+ +

The difference is too long, and the specified state must be used to refetch updates.

+

+ +
+
updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
ptsintThe new state to use.
+

Type

+

updates.Difference

+

Related pages

+

Working with Updates

+

How to subscribe to updates and handle them properly.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.cdnFile b/data/corefork.telegram.org/constructor/upload.cdnFile new file mode 100644 index 0000000000..50e7b2a73d --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.cdnFile @@ -0,0 +1,149 @@ + + + + + upload.cdnFile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.cdnFile

+ +

Represent a chunk of a CDN file.

+

+ +
+
upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
bytesbytesThe data
+

Type

+

upload.CdnFile

+

Related pages

+

Encrypted CDNs for Speed and Security

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/upload.file b/data/corefork.telegram.org/constructor/upload.file new file mode 100644 index 0000000000..a3fe7bcae2 --- /dev/null +++ b/data/corefork.telegram.org/constructor/upload.file @@ -0,0 +1,157 @@ + + + + + upload.file + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.file

+ +

File content.

+

+ +
+
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typestorage.FileTypeFile type
mtimeintModification type
bytesbytesBinary data, file content
+

Type

+

upload.File

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/urlAuthResultRequest.html b/data/corefork.telegram.org/constructor/urlAuthResultRequest.html new file mode 100644 index 0000000000..a7c222616c --- /dev/null +++ b/data/corefork.telegram.org/constructor/urlAuthResultRequest.html @@ -0,0 +1,165 @@ + + + + + urlAuthResultRequest + + + + + + + + + + + + + +
+ +
+
+
+ +

urlAuthResultRequest

+ +

Details about the authorization request, for more info click here »

+

+ +
+
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueWhether the bot would like to send messages to the user
botUserUsername of a bot, which will be used for user authorization. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
domainstringThe domain name of the website on which the user will log in.
+

Type

+

UrlAuthResult

+

Related pages

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userEmpty.html b/data/corefork.telegram.org/constructor/userEmpty.html new file mode 100644 index 0000000000..c4c7b13752 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userEmpty.html @@ -0,0 +1,147 @@ + + + + + userEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

userEmpty

+ +

Empty constructor, non-existent user.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongUser identifier or 0
+

Type

+

User

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/userStatusLastWeek.html b/data/corefork.telegram.org/constructor/userStatusLastWeek.html new file mode 100644 index 0000000000..6f1ae2e946 --- /dev/null +++ b/data/corefork.telegram.org/constructor/userStatusLastWeek.html @@ -0,0 +1,132 @@ + + + + + userStatusLastWeek + + + + + + + + + + + + + +
+ +
+
+
+ +

userStatusLastWeek

+ +

Online status: last seen last week

+

+ +
+
userStatusLastWeek#7bf09fc = UserStatus;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

UserStatus

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/vector.html b/data/corefork.telegram.org/constructor/vector.html new file mode 100644 index 0000000000..0a2519e1aa --- /dev/null +++ b/data/corefork.telegram.org/constructor/vector.html @@ -0,0 +1,134 @@ + + + + + vector + + + + + + + + + + + + + +
+ +
+
+
+ +

vector

+ +

A universal vector constructor.

+

+ +
+
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

+

Parameters

+

This constructor does not require any parameters.

+

Type

+

Vector t

+

Params additional

+

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/wallPaper.html b/data/corefork.telegram.org/constructor/wallPaper.html new file mode 100644 index 0000000000..b8bf00b776 --- /dev/null +++ b/data/corefork.telegram.org/constructor/wallPaper.html @@ -0,0 +1,192 @@ + + + + + wallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaper

+ +

Wallpaper settings.

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongIdentifier
flags#Flags, see TL conditional fields
creatorflags.0?trueCreator of the wallpaper
defaultflags.1?trueWhether this is the default wallpaper
patternflags.3?truePattern
darkflags.4?trueDark mode
access_hashlongAccess hash
slugstringUnique wallpaper ID
documentDocumentThe actual wallpaper
settingsflags.2?WallPaperSettingsWallpaper settings
+

Type

+

WallPaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/wallPaperNoFile.html b/data/corefork.telegram.org/constructor/wallPaperNoFile.html new file mode 100644 index 0000000000..f4c50fc753 --- /dev/null +++ b/data/corefork.telegram.org/constructor/wallPaperNoFile.html @@ -0,0 +1,171 @@ + + + + + wallPaperNoFile + + + + + + + + + + + + + +
+ +
+
+
+ +

wallPaperNoFile

+ +

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
+Also used for some default wallpapers which contain only colours.

+

+ +
+
wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idlongWallpaper ID
flags#Flags, see TL conditional fields
defaultflags.1?trueWhether this is the default wallpaper
darkflags.4?trueDark mode
settingsflags.2?WallPaperSettingsWallpaper settings
+

Type

+

WallPaper

+

Related pages

+

account.saveWallPaper

+

Install/uninstall wallpaper

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/constructor/webPageEmpty.html b/data/corefork.telegram.org/constructor/webPageEmpty.html new file mode 100644 index 0000000000..662fad3eb6 --- /dev/null +++ b/data/corefork.telegram.org/constructor/webPageEmpty.html @@ -0,0 +1,147 @@ + + + + + webPageEmpty + + + + + + + + + + + + + +
+ +
+
+
+ +

webPageEmpty

+ +

No preview is available for the webpage

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idlongPreview ID
+

Type

+

WebPage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/getProxyConfig.html b/data/corefork.telegram.org/getProxyConfig.html new file mode 100644 index 0000000000..7238f2dd28 --- /dev/null +++ b/data/corefork.telegram.org/getProxyConfig.html @@ -0,0 +1,24 @@ +# force_probability 10 10 +default 2; +proxy_for 1 149.154.X.X:8888; +proxy_for -1 149.154.X.X:8888; +proxy_for 2 149.154.X.X:8888; +proxy_for -2 149.154.X.X:8888; +proxy_for 3 149.154.X.X:8888; +proxy_for -3 149.154.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for 4 91.108.X.X:8888; +proxy_for -4 149.154.X.X:8888; +proxy_for -4 149.154.X.X:8888; +proxy_for 5 91.108.X.X:8888; +proxy_for 5 91.108.X.X:8888; +proxy_for -5 91.108.X.X:8888; +proxy_for -5 91.108.X.X:8888; diff --git a/data/corefork.telegram.org/method/account.changePhone b/data/corefork.telegram.org/method/account.changePhone new file mode 100644 index 0000000000..8851f189e5 --- /dev/null +++ b/data/corefork.telegram.org/method/account.changePhone @@ -0,0 +1,195 @@ + + + + + account.changePhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.changePhone

+ +

Change the phone number of the current account

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringNew phone number
phone_code_hashstringPhone code hash received when calling account.sendChangePhoneCode
phone_codestringPhone code received when calling account.sendChangePhoneCode
+

Result

+

User

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_CODE_EXPIREDThe phone code you provided has expired.
406PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
+

Related pages

+

account.sendChangePhoneCode

+

Verify a new phone number to associate to the current account

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.confirmPhone b/data/corefork.telegram.org/method/account.confirmPhone new file mode 100644 index 0000000000..d1e48ffedf --- /dev/null +++ b/data/corefork.telegram.org/method/account.confirmPhone @@ -0,0 +1,180 @@ + + + + + account.confirmPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

account.confirmPhone

+ +

Confirm a phone number to cancel account deletion, for more info click here »

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_code_hashstringPhone code hash, for more info click here »
phone_codestringSMS code, for more info click here »
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CODE_HASH_INVALIDCode hash invalid.
400PHONE_CODE_EMPTYphone_code is missing.
+

Related pages

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getContactSignUpNotification b/data/corefork.telegram.org/method/account.getContactSignUpNotification new file mode 100644 index 0000000000..9de8f4bde0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getContactSignUpNotification @@ -0,0 +1,135 @@ + + + + + account.getContactSignUpNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getContactSignUpNotification

+ +

Whether the user will receive notifications when contacts sign up

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.getContactSignUpNotification#9f07c728 = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getContentSettings b/data/corefork.telegram.org/method/account.getContentSettings new file mode 100644 index 0000000000..9213a4314a --- /dev/null +++ b/data/corefork.telegram.org/method/account.getContentSettings @@ -0,0 +1,134 @@ + + + + + account.getContentSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getContentSettings

+ +

Get sensitive content settings

+

+ +
+
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
+---functions---
+account.getContentSettings#8b9b4dae = account.ContentSettings;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

account.ContentSettings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getMultiWallPapers b/data/corefork.telegram.org/method/account.getMultiWallPapers new file mode 100644 index 0000000000..9281752e0b --- /dev/null +++ b/data/corefork.telegram.org/method/account.getMultiWallPapers @@ -0,0 +1,148 @@ + + + + + account.getMultiWallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getMultiWallPapers

+ +

Get info about multiple wallpapers

+

+ +
+
---functions---
+account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
wallpapersVector<InputWallPaper>Wallpapers to fetch info about
+

Result

+

Vector<WallPaper>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.getTmpPassword b/data/corefork.telegram.org/method/account.getTmpPassword new file mode 100644 index 0000000000..7c90d0dbc0 --- /dev/null +++ b/data/corefork.telegram.org/method/account.getTmpPassword @@ -0,0 +1,176 @@ + + + + + account.getTmpPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

account.getTmpPassword

+ +

Get temporary payment password

+

+ +
+
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
+---functions---
+account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPSRP password parameters
periodintTime during which the temporary password will be valid, in seconds; should be between 60 and 86400
+

Result

+

account.TmpPassword

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400TMP_PASSWORD_DISABLEDThe temporary password is disabled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.installTheme b/data/corefork.telegram.org/method/account.installTheme new file mode 100644 index 0000000000..2bb51e2c0a --- /dev/null +++ b/data/corefork.telegram.org/method/account.installTheme @@ -0,0 +1,170 @@ + + + + + account.installTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

account.installTheme

+ +

Install a theme

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.installTheme#c727bb3b flags:# dark:flags.0?true theme:flags.1?InputTheme format:flags.2?string base_theme:flags.3?BaseTheme = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to install the dark version
themeflags.1?InputThemeTheme to install
formatflags.2?stringTheme format, a string that identifies the theming engines supported by the client
base_themeflags.3?BaseTheme 
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.registerDevice b/data/corefork.telegram.org/method/account.registerDevice new file mode 100644 index 0000000000..760b110d43 --- /dev/null +++ b/data/corefork.telegram.org/method/account.registerDevice @@ -0,0 +1,217 @@ + + + + + account.registerDevice + + + + + + + + + + + + + +
+ +
+
+
+ +

account.registerDevice

+ +

Register device to receive PUSH notifications

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_mutedflags.0?trueAvoid receiving (silent and invisible background) notifications. Useful to save battery.
token_typeintDevice token type.
Possible values:
1 - APNS (device token for apple push)
2 - FCM (firebase token for google firebase)
3 - MPNS (channel URI for microsoft push)
4 - Simple push (endpoint for firefox's simple push API)
5 - Ubuntu phone (token for ubuntu push)
6 - Blackberry (token for blackberry push)
7 - Unused
8 - WNS (windows push)
9 - APNS VoIP (token for apple push VoIP)
10 - Web push (web push, see below)
11 - MPNS VoIP (token for microsoft push VoIP)
12 - Tizen (token for tizen push)

For 10 web push, the token must be a JSON-encoded object containing the keys described in PUSH updates
tokenstringDevice token
app_sandboxBoolIf (boolTrue) is transmitted, a sandbox-certificate will be used during transmission.
secretbytesFor FCM and APNS VoIP, optional encryption key used to encrypt push notifications
other_uidsVector<long>List of user identifiers of other users currently using the client
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
400WEBPUSH_AUTH_INVALIDThe specified web push authentication secret is invalid.
400WEBPUSH_KEY_INVALIDThe specified web push elliptic curve Diffie-Hellman public key is invalid.
400WEBPUSH_TOKEN_INVALIDThe specified web push token is invalid.
+

Related pages

+

Handling PUSH-notifications

+

How to subscribe to and handle PUSH notifications

+

boolTrue

+

The constructor can be interpreted as a booleantrue value.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.reportPeer b/data/corefork.telegram.org/method/account.reportPeer new file mode 100644 index 0000000000..4fb189e8fc --- /dev/null +++ b/data/corefork.telegram.org/method/account.reportPeer @@ -0,0 +1,182 @@ + + + + + account.reportPeer + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportPeer

+ +

Report a peer for violation of telegram's Terms of Service

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer to report
reasonReportReasonThe reason why this peer is being reported
messagestringComment for report moderation
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.reportProfilePhoto b/data/corefork.telegram.org/method/account.reportProfilePhoto new file mode 100644 index 0000000000..95ef750d1a --- /dev/null +++ b/data/corefork.telegram.org/method/account.reportProfilePhoto @@ -0,0 +1,165 @@ + + + + + account.reportProfilePhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

account.reportProfilePhoto

+ +

Report a profile photo of a dialog

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe dialog
photo_idInputPhotoDialog photo ID
reasonReportReasonReport reason
messagestringComment for report moderation
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.saveWallPaper b/data/corefork.telegram.org/method/account.saveWallPaper new file mode 100644 index 0000000000..c26a614835 --- /dev/null +++ b/data/corefork.telegram.org/method/account.saveWallPaper @@ -0,0 +1,177 @@ + + + + + account.saveWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.saveWallPaper

+ +

Install/uninstall wallpaper

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
wallpaperInputWallPaperWallpaper to save
unsaveBoolUninstall wallpaper?
settingsWallPaperSettingsWallpaper settings
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.setAuthorizationTTL b/data/corefork.telegram.org/method/account.setAuthorizationTTL new file mode 100644 index 0000000000..c1e4bc1472 --- /dev/null +++ b/data/corefork.telegram.org/method/account.setAuthorizationTTL @@ -0,0 +1,195 @@ + + + + + account.setAuthorizationTTL + + + + + + + + + + + + + +
+ +
+
+
+ +

account.setAuthorizationTTL

+ +

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.setAuthorizationTTL#bf899aa0 authorization_ttl_days:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
authorization_ttl_daysint 
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.updateProfile b/data/corefork.telegram.org/method/account.updateProfile new file mode 100644 index 0000000000..bb056bdd9b --- /dev/null +++ b/data/corefork.telegram.org/method/account.updateProfile @@ -0,0 +1,187 @@ + + + + + account.updateProfile + + + + + + + + + + + + + +
+ +
+
+
+ +

account.updateProfile

+ +

Updates user profile.

+

+ +
+
userEmpty#d3bc4b7a id:long = User;
+user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
+---functions---
+account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
first_nameflags.0?stringNew user first name
last_nameflags.1?stringNew user last name
aboutflags.2?stringNew bio
+

Result

+

Returns User object containing the updated current user profile.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ABOUT_TOO_LONGAbout string too long.
400FIRSTNAME_INVALIDThe first name is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/account.uploadWallPaper b/data/corefork.telegram.org/method/account.uploadWallPaper new file mode 100644 index 0000000000..2abbce23bb --- /dev/null +++ b/data/corefork.telegram.org/method/account.uploadWallPaper @@ -0,0 +1,182 @@ + + + + + account.uploadWallPaper + + + + + + + + + + + + + +
+ +
+
+
+ +

account.uploadWallPaper

+ +

Create and upload a new wallpaper

+

+ +
+
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
+wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
+---functions---
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
fileInputFileThe JPG/PNG wallpaper
mime_typestringMIME type of uploaded wallpaper
settingsWallPaperSettingsWallpaper settings
+

Result

+

WallPaper

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400WALLPAPER_FILE_INVALIDThe specified wallpaper file is invalid.
400WALLPAPER_MIME_INVALIDThe specified wallpaper MIME type is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.acceptLoginToken b/data/corefork.telegram.org/method/auth.acceptLoginToken new file mode 100644 index 0000000000..ee51424851 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.acceptLoginToken @@ -0,0 +1,176 @@ + + + + + auth.acceptLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.acceptLoginToken

+ +

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.

+

+ +
+
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
+---functions---
+auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
tokenbytesLogin token embedded in QR code, for more info, see login via QR code.
+

Result

+

Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_TOKEN_EXPIREDThe authorization token has expired.
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.bindTempAuthKey b/data/corefork.telegram.org/method/auth.bindTempAuthKey new file mode 100644 index 0000000000..ef7f0a0843 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.bindTempAuthKey @@ -0,0 +1,252 @@ + + + + + auth.bindTempAuthKey + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.bindTempAuthKey

+ +

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.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
perm_auth_key_idlongPermanent auth_key_id to bind to
noncelongRandom long from Binding message contents
expires_atintUnix timestamp to invalidate temporary key, see Binding message contents
encrypted_messagebytesSee Generating encrypted_message
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ENCRYPTED_MESSAGE_INVALIDEncrypted message invalid.
400TEMP_AUTH_KEY_ALREADY_BOUNDThe passed temporary key is already bound to another perm_auth_key_id.
400TEMP_AUTH_KEY_EMPTYNo temporary auth key provided.
+

Generating encrypted_message

+

The client begins by creating a special binding message:

+

Binding message contents

+
bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
noncelongRandom long
temp_auth_key_idlongTemporary auth_key_id
perm_auth_key_idlongPermanent auth_key_id to bind to
temp_session_idlongSession id, which will be used to invoke auth.bindTempAuthKey method
expires_atintUnix timestamp to invalidate temporary key
+

Encrypting the binding message

+

This binding message is encrypted in the usual way, but with MTProto v1 using the perm_auth_key. In other words, one has to prepend random:int128 (it replaces the customary session_id:long and salt:long that are irrelevant in this case), then append the same msg_id that will be used for the request, a seqno equal to zero, and the correct msg_len (40 bytes in this case); after that, one computes the msg_key:int128 as SHA1 of the resulting string, appends padding necessary for a 16-byte alignment, encrypts the resulting string using the key derived from perm_auth_key and msg_key, and prepends perm_auth_key_id and msg_key to the encrypted data as usual.

+

Binding

+

Once encrypted_message is ready, an auth.bindTempAuthKey request is sent to the server using temp_auth_key and temp_session_id. Don't forget to rewrite client info using initConnection when the binding is completed.

+

Bots can use this method

+

Related pages

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

long

+

A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

+

More on basic types »

+

int

+

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

+

More on basic types »

+

Mobile Protocol: Detailed Description

+

Calling API Methods

+

Additional options for calling methods.

+

initConnection

+

Initialize connection

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.cancelCode b/data/corefork.telegram.org/method/auth.cancelCode new file mode 100644 index 0000000000..aafc881185 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.cancelCode @@ -0,0 +1,180 @@ + + + + + auth.cancelCode + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.cancelCode

+ +

Cancel the login verification code

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash from auth.sendCode
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired.
406PHONE_NUMBER_INVALIDThe phone number is invalid.
+

Related pages

+

auth.sendCode

+

Send the verification code for login

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.checkPassword b/data/corefork.telegram.org/method/auth.checkPassword new file mode 100644 index 0000000000..606aaef51d --- /dev/null +++ b/data/corefork.telegram.org/method/auth.checkPassword @@ -0,0 +1,180 @@ + + + + + auth.checkPassword + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.checkPassword

+ +

Try logging to an account protected by a 2FA password.

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
passwordInputCheckPasswordSRPThe account's password (see SRP)
+

Result

+

auth.Authorization

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.exportLoginToken b/data/corefork.telegram.org/method/auth.exportLoginToken new file mode 100644 index 0000000000..2d4102d075 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.exportLoginToken @@ -0,0 +1,183 @@ + + + + + auth.exportLoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.exportLoginToken

+ +

Generate a login token, for login via QR code.
+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.

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+---functions---
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
except_idsVector<long>List of already logged-in user IDs, to prevent logging in twice with the same user
+

Result

+

auth.LoginToken

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
+

Related pages

+

Login via QR code

+

QR code login flow

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.importBotAuthorization b/data/corefork.telegram.org/method/auth.importBotAuthorization new file mode 100644 index 0000000000..c60788916f --- /dev/null +++ b/data/corefork.telegram.org/method/auth.importBotAuthorization @@ -0,0 +1,200 @@ + + + + + auth.importBotAuthorization + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.importBotAuthorization

+ +

Login as a bot

+

+ +
+
auth.authorization#33fb7bb8 flags:# setup_password_required:flags.1?true otherwise_relogin_days:flags.1?int tmp_sessions:flags.0?int user:User = auth.Authorization;
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+---functions---
+auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flagsintReserved for future use
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
bot_auth_tokenstringBot token (see bots)
+

Result

+

Returns an auth.Authorization object with information on the new authorization.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ACCESS_TOKEN_EXPIREDAccess token expired.
400ACCESS_TOKEN_INVALIDAccess token invalid.
400API_ID_INVALIDAPI ID invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
+

Bots can use this method

+

Related pages

+

Bots: An introduction for developers

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.requestPasswordRecovery b/data/corefork.telegram.org/method/auth.requestPasswordRecovery new file mode 100644 index 0000000000..26e13dcdd3 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.requestPasswordRecovery @@ -0,0 +1,159 @@ + + + + + auth.requestPasswordRecovery + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.requestPasswordRecovery

+ +

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

+

+ +
+
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
+---functions---
+auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

auth.PasswordRecovery

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PASSWORD_EMPTYThe provided password is empty.
400PASSWORD_RECOVERY_NANo email was set, can't recover password via email.
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.sendCall b/data/corefork.telegram.org/method/auth.sendCall new file mode 100644 index 0000000000..ffc1255c55 --- /dev/null +++ b/data/corefork.telegram.org/method/auth.sendCall @@ -0,0 +1,175 @@ + + + + + auth.sendCall + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendCall

+ +

Makes a voice call to the passed phone number. A robot will repeat the confirmation code from a previously sent SMS message.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
+

Result

+

Bool

+

Query example

+
(auth.sendCall "79991234567" "2dc02d2cda9e615c84")
+=
+(boolTrue)
+
+03c51564 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 64e1a61b
+=
+997275b5
+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/auth.sendSms b/data/corefork.telegram.org/method/auth.sendSms new file mode 100644 index 0000000000..1d5b0a244c --- /dev/null +++ b/data/corefork.telegram.org/method/auth.sendSms @@ -0,0 +1,167 @@ + + + + + auth.sendSms + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.sendSms

+ +

Forces sending an SMS message to the specified phone number. Use this method if auth.sentAppCode was returned as a response to auth.sendCode, but the user can't reach the device with Telegram.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
phone_numberstringPhone number in international format
phone_code_hashstringSMS-message ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/bots.sendCustomRequest b/data/corefork.telegram.org/method/bots.sendCustomRequest new file mode 100644 index 0000000000..e2723cbac1 --- /dev/null +++ b/data/corefork.telegram.org/method/bots.sendCustomRequest @@ -0,0 +1,177 @@ + + + + + bots.sendCustomRequest + + + + + + + + + + + + + +
+ +
+
+
+ +

bots.sendCustomRequest

+ +

Sends a custom request; for bots only

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+---functions---
+bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
custom_methodstringThe method name
paramsDataJSONJSON-serialized method parameters
+

Result

+

DataJSON

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
403USER_BOT_INVALIDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel new file mode 100644 index 0000000000..f4a70c6d63 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.createChannel @@ -0,0 +1,232 @@ + + + + + channels.createChannel + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.createChannel

+ +

Create a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.0?trueWhether to create a channel
megagroupflags.1?trueWhether to create a supergroup
for_importflags.3?trueWhether the supergroup is being created to import messages from a foreign chat service using messages.initHistoryImport
titlestringChannel title
aboutstringChannel description
geo_pointflags.2?InputGeoPointGeogroup location
addressflags.2?stringGeogroup address
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHThe user has reached the limit of public geogroups.
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_TITLE_EMPTYNo chat title provided.
406USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

messages.initHistoryImport

+

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.deleteUserHistory b/data/corefork.telegram.org/method/channels.deleteUserHistory new file mode 100644 index 0000000000..d67890cceb --- /dev/null +++ b/data/corefork.telegram.org/method/channels.deleteUserHistory @@ -0,0 +1,197 @@ + + + + + channels.deleteUserHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.deleteUserHistory

+ +

Delete all messages sent by a certain user in a supergroup

+

+ +
+
 Method schema is available as of layer 135. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserUser whose messages should be deleted
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editAdmin b/data/corefork.telegram.org/method/channels.editAdmin new file mode 100644 index 0000000000..a9f7c1e676 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editAdmin @@ -0,0 +1,301 @@ + + + + + channels.editAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editAdmin

+ +

Modify the admin rights of a user in a supergroup/channel.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelThe supergroup/channel.
user_idInputUserThe ID of the user whose admin rights should be modified
admin_rightsChatAdminRightsThe admin rights
rankstringIndicates the role (rank) of the admin in the group: just an arbitrary string
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ADMINS_TOO_MUCHThere are too many admins.
400ADMIN_RANK_EMOJI_NOT_ALLOWEDAn admin rank cannot contain emojis.
400ADMIN_RANK_INVALIDThe specified admin rank is invalid.
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_CHANNELS_NABots can't edit admin privileges.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHAT_ADMIN_INVITE_REQUIREDYou do not have the rights to do this.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
406FRESH_CHANGE_ADMINS_FORBIDDENYou were just elected admin, you can't add or modify other admins yet.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
403RIGHT_FORBIDDENYour admin rights do not allow you to do this.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BLOCKEDUser blocked.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_ID_INVALIDThe provided user ID is invalid.
403USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.editTitle b/data/corefork.telegram.org/method/channels.editTitle new file mode 100644 index 0000000000..2393ac3825 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.editTitle @@ -0,0 +1,206 @@ + + + + + channels.editTitle + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.editTitle

+ +

Edit the name of a channel/supergroup

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+channels.editTitle#566decd0 channel:InputChannel title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel/supergroup
titlestringNew name
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
+

Bots can use this method

+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.exportMessageLink b/data/corefork.telegram.org/method/channels.exportMessageLink new file mode 100644 index 0000000000..c21366c9f8 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.exportMessageLink @@ -0,0 +1,204 @@ + + + + + channels.exportMessageLink + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.exportMessageLink

+ +

Get link and embed info of a message in a channel/supergroup

+

+ +
+
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
+---functions---
+channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
groupedflags.0?trueWhether to include other grouped media (for albums)
threadflags.1?trueWhether to also include a thread ID, if available, inside of the link
channelInputChannelChannel
idintMessage ID
+

Result

+

ExportedMessageLink

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels new file mode 100644 index 0000000000..2236c0cd1a --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels @@ -0,0 +1,191 @@ + + + + + channels.getAdminedPublicChannels + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getAdminedPublicChannels

+ +

Get channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
by_locationflags.0?trueGet geogroups
check_limitflags.1?trueIf set and the user has reached the limit of owned public channels/supergroups/geogroups, instead of returning the channel list one of the specified errors will be returned.
Useful to check if a new public channel can indeed be created, even before asking the user to enter a channel username to use in channels.checkUsername/channels.updateUsername.
+

Result

+

messages.Chats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHThe user has reached the limit of public geogroups.
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

channels.checkUsername

+

Check if a username is free and can be assigned to a channel/supergroup

+

channels.updateUsername

+

Change the username of a supergroup/channel

+

config

+

Current configuration

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion new file mode 100644 index 0000000000..74cd048bb5 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion @@ -0,0 +1,144 @@ + + + + + channels.getGroupsForDiscussion + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getGroupsForDiscussion

+ +

Get all groups that can be used as discussion groups.

+

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
+To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.

+

+ +
+
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
+---functions---
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

messages.Chats

+

Related pages

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

channels.togglePreHistoryHidden

+

Hide/unhide message history for new channel/supergroup users

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/channels.getParticipants b/data/corefork.telegram.org/method/channels.getParticipants new file mode 100644 index 0000000000..3001413b72 --- /dev/null +++ b/data/corefork.telegram.org/method/channels.getParticipants @@ -0,0 +1,203 @@ + + + + + channels.getParticipants + + + + + + + + + + + + + +
+ +
+
+
+ +

channels.getParticipants

+ +

Get the participants of a supergroup/channel

+

+ +
+
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
+channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
+---functions---
+channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelChannel
filterChannelParticipantsFilterWhich participant types to fetch
offsetintOffset
limitintLimit
hashlongHash
+

Result

+

channels.ChannelParticipants

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
+

Bots can use this method

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.acceptContact b/data/corefork.telegram.org/method/contacts.acceptContact new file mode 100644 index 0000000000..9f23bb3d52 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.acceptContact @@ -0,0 +1,190 @@ + + + + + contacts.acceptContact + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.acceptContact

+ +

If the peer settings of a new user allow us to add him as contact, add that user as contact

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.acceptContact#f831a20f id:InputUser = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserThe user to add as contact
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONTACT_ADD_MISSINGContact to add is missing.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_REQ_MISSINGMissing contact request.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

peerSettings

+

Peer settings

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.addContact b/data/corefork.telegram.org/method/contacts.addContact new file mode 100644 index 0000000000..470888fec2 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.addContact @@ -0,0 +1,217 @@ + + + + + contacts.addContact + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.addContact

+ +

Add an existing telegram user as contact.

+

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
add_phone_privacy_exceptionflags.0?trueAllow the other user to see our phone number?
idInputUserTelegram ID of the other user
first_namestringFirst name
last_namestringLast name
phonestringUser's phone number
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_NAME_EMPTYContact name empty.
400MSG_ID_INVALIDInvalid message ID provided.
+

Related pages

+

contacts.importContacts

+

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 to add Telegram contacts without actually using their phone number.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.block b/data/corefork.telegram.org/method/contacts.block new file mode 100644 index 0000000000..64bf66ac93 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.block @@ -0,0 +1,182 @@ + + + + + contacts.block + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.block

+ +

Adds the user to the blacklist.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.block#68cc1411 id:InputPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputPeerUser ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.deleteByPhones b/data/corefork.telegram.org/method/contacts.deleteByPhones new file mode 100644 index 0000000000..751cdb1ded --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.deleteByPhones @@ -0,0 +1,150 @@ + + + + + contacts.deleteByPhones + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.deleteByPhones

+ +

Delete contacts by phone number

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
phonesVector<string>Phone numbers
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getContactIDs b/data/corefork.telegram.org/method/contacts.getContactIDs new file mode 100644 index 0000000000..08cd92f4b5 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getContactIDs @@ -0,0 +1,151 @@ + + + + + contacts.getContactIDs + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContactIDs

+ +

Get contact by telegram IDs

+

+ +
+
---functions---
+contacts.getContactIDs#7adc669d hash:long = Vector<int>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongHash for pagination, for more info click here
+

Result

+

Vector<int>

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getContacts b/data/corefork.telegram.org/method/contacts.getContacts new file mode 100644 index 0000000000..ad0e755eff --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getContacts @@ -0,0 +1,155 @@ + + + + + contacts.getContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getContacts

+ +

Returns the current user's contact list.

+

+ +
+
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
+contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
+---functions---
+contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashlongIf there already is a full contact list on the client, a hash of a the list of contact IDs in ascending order may be passed in this parameter. If the contact set was not changed, (contacts.contactsNotModified) will be returned.
+

Result

+

contacts.Contacts

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

contacts.contactsNotModified

+

Contact list on the server is the same as the list on the client.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getStatuses b/data/corefork.telegram.org/method/contacts.getStatuses new file mode 100644 index 0000000000..2a9e85a427 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getStatuses @@ -0,0 +1,133 @@ + + + + + contacts.getStatuses + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getStatuses

+ +

Returns the list of contact statuses.

+

+ +
+
---functions---
+contacts.getStatuses#c4a353ee = Vector<ContactStatus>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<ContactStatus>

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.getTopPeers b/data/corefork.telegram.org/method/contacts.getTopPeers new file mode 100644 index 0000000000..3e9a29b762 --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.getTopPeers @@ -0,0 +1,226 @@ + + + + + contacts.getTopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.getTopPeers

+ +

Get most used peers

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+---functions---
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
correspondentsflags.0?trueUsers we've chatted most frequently with
bots_pmflags.1?trueMost used bots
bots_inlineflags.2?trueMost used inline bots
phone_callsflags.3?trueMost frequently called users
forward_usersflags.4?trueUsers to which the users often forwards messages to
forward_chatsflags.5?trueChats to which the users often forwards messages to
groupsflags.10?trueOften-opened groups and supergroups
channelsflags.15?trueMost frequently visited channels
offsetintOffset for pagination
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
+

Result

+

contacts.TopPeers

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TYPES_EMPTYNo top peer type was provided.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/contacts.resolveUsername b/data/corefork.telegram.org/method/contacts.resolveUsername new file mode 100644 index 0000000000..8cdd9f311d --- /dev/null +++ b/data/corefork.telegram.org/method/contacts.resolveUsername @@ -0,0 +1,177 @@ + + + + + contacts.resolveUsername + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.resolveUsername

+ +

Resolve a @username to get peer info

+

+ +
+
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
+---functions---
+contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
usernamestring@username to resolve
+

Result

+

contacts.ResolvedPeer

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CONNECTION_LAYER_INVALIDLayer invalid.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_OCCUPIEDThe provided username is not occupied.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/folders.editPeerFolders b/data/corefork.telegram.org/method/folders.editPeerFolders new file mode 100644 index 0000000000..454868ecb9 --- /dev/null +++ b/data/corefork.telegram.org/method/folders.editPeerFolders @@ -0,0 +1,180 @@ + + + + + folders.editPeerFolders + + + + + + + + + + + + + +
+ +
+
+
+ +

folders.editPeerFolders

+ +

Edit peers in peer folder

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
folder_peersVector<InputFolderPeer>New peer list
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400FOLDER_ID_INVALIDInvalid folder ID.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.dismissSuggestion b/data/corefork.telegram.org/method/help.dismissSuggestion new file mode 100644 index 0000000000..cfa8e37182 --- /dev/null +++ b/data/corefork.telegram.org/method/help.dismissSuggestion @@ -0,0 +1,160 @@ + + + + + help.dismissSuggestion + + + + + + + + + + + + + +
+ +
+
+
+ +

help.dismissSuggestion

+ +

Dismiss a suggestion, see here for more info ».

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerIn the case of pending suggestions in channels, the channel ID.
suggestionstringSuggestion, see here for more info ».
+

Result

+

Bool

+

Related pages

+

channelFull

+

Full info about a channel/supergroup

+

Client configuration

+

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getDeepLinkInfo b/data/corefork.telegram.org/method/help.getDeepLinkInfo new file mode 100644 index 0000000000..6b5c226bca --- /dev/null +++ b/data/corefork.telegram.org/method/help.getDeepLinkInfo @@ -0,0 +1,150 @@ + + + + + help.getDeepLinkInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getDeepLinkInfo

+ +

Get info about a t.me link

+

+ +
+
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
+help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+---functions---
+help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
pathstringPath in t.me/path
+

Result

+

help.DeepLinkInfo

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getNearestDc b/data/corefork.telegram.org/method/help.getNearestDc new file mode 100644 index 0000000000..5bf959f42c --- /dev/null +++ b/data/corefork.telegram.org/method/help.getNearestDc @@ -0,0 +1,134 @@ + + + + + help.getNearestDc + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getNearestDc

+ +

Returns info on data centre nearest to the user.

+

+ +
+
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
+---functions---
+help.getNearestDc#1fb33026 = NearestDc;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

NearestDc

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/help.getProxyData b/data/corefork.telegram.org/method/help.getProxyData new file mode 100644 index 0000000000..9cc87ab252 --- /dev/null +++ b/data/corefork.telegram.org/method/help.getProxyData @@ -0,0 +1,132 @@ + + + + + help.getProxyData + + + + + + + + + + + + + +
+ +
+
+
+ +

help.getProxyData

+ +

Get promotion info of the currently-used MTProxy

+

+ +
+
 Method schema is available as of layer 113. Switch »

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

help.ProxyData

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/initConnection.html b/data/corefork.telegram.org/method/initConnection.html new file mode 100644 index 0000000000..9af87099f6 --- /dev/null +++ b/data/corefork.telegram.org/method/initConnection.html @@ -0,0 +1,216 @@ + + + + + initConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

initConnection

+ +

Initialize connection

+

+ +
+
---functions---
+initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
api_idintApplication identifier (see. App configuration)
device_modelstringDevice model
system_versionstringOperation system version
app_versionstringApplication version
system_lang_codestringCode for the language used on the device's OS, ISO 639-1 standard
lang_packstringLanguage pack to use
lang_codestringCode for the language used on the client, ISO 639-1 standard
proxyflags.0?InputClientProxyInfo about an MTProto proxy
paramsflags.1?JSONValueAdditional initConnection parameters.
For now, only the tz_offset field is supported, for specifying timezone offset in seconds.
query!XThe query itself
+

Result

+

X

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CONNECTION_LAYER_INVALIDLayer invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeAfterMsgs.html b/data/corefork.telegram.org/method/invokeAfterMsgs.html new file mode 100644 index 0000000000..12d1580407 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeAfterMsgs.html @@ -0,0 +1,154 @@ + + + + + invokeAfterMsgs + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeAfterMsgs

+ +

Invokes a query after a successfull completion of previous queries

+

+ +
+
---functions---
+invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
msg_idsVector<long>List of messages on which a current query depends
query!XThe query itself
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeWithLayer.html b/data/corefork.telegram.org/method/invokeWithLayer.html new file mode 100644 index 0000000000..801055bed6 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeWithLayer.html @@ -0,0 +1,194 @@ + + + + + invokeWithLayer + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithLayer

+ +

Invoke the specified query using the specified API layer

+

+ +
+
---functions---
+invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
layerintThe layer to use
query!XThe query
+

Result

+

X

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400INVITE_HASH_EXPIREDThe invite link has expired.
+

Bots can use this method

+

Related pages

+

Calling API Methods

+

Additional options for calling methods.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/invokeWithMessagesRange.html b/data/corefork.telegram.org/method/invokeWithMessagesRange.html new file mode 100644 index 0000000000..a7b17a0189 --- /dev/null +++ b/data/corefork.telegram.org/method/invokeWithMessagesRange.html @@ -0,0 +1,154 @@ + + + + + invokeWithMessagesRange + + + + + + + + + + + + + +
+ +
+
+
+ +

invokeWithMessagesRange

+ +

Invoke with the given message range

+

+ +
+
---functions---
+invokeWithMessagesRange#365275f2 {X:Type} range:MessageRange query:!X = X;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
rangeMessageRangeMessage range
query!XQuery
+

Result

+

X

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getLanguage b/data/corefork.telegram.org/method/langpack.getLanguage new file mode 100644 index 0000000000..fbb7886d27 --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getLanguage @@ -0,0 +1,154 @@ + + + + + langpack.getLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLanguage

+ +

Get information about a language in a localization pack

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+---functions---
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
+

Result

+

LangPackLanguage

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getLanguages b/data/corefork.telegram.org/method/langpack.getLanguages new file mode 100644 index 0000000000..e5786fe847 --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getLanguages @@ -0,0 +1,165 @@ + + + + + langpack.getLanguages + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getLanguages

+ +

Get information about all languages in a localization pack

+

+ +
+
---functions---
+langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack
+

Result

+

Vector<LangPackLanguage>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/langpack.getStrings b/data/corefork.telegram.org/method/langpack.getStrings new file mode 100644 index 0000000000..ebd86f8ffa --- /dev/null +++ b/data/corefork.telegram.org/method/langpack.getStrings @@ -0,0 +1,175 @@ + + + + + langpack.getStrings + + + + + + + + + + + + + +
+ +
+
+
+ +

langpack.getStrings

+ +

Get strings from a language pack

+

+ +
+
---functions---
+langpack.getStrings#efea3803 lang_pack:string lang_code:string keys:Vector<string> = Vector<LangPackString>;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
keysVector<string>Strings to get
+

Result

+

Vector<LangPackString>

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.clearAllDrafts b/data/corefork.telegram.org/method/messages.clearAllDrafts new file mode 100644 index 0000000000..c5a0386099 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.clearAllDrafts @@ -0,0 +1,138 @@ + + + + + messages.clearAllDrafts + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.clearAllDrafts

+ +

Clear all drafts.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.clearAllDrafts#7e58ee9c = Bool;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Bool

+

Related pages

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.createChat b/data/corefork.telegram.org/method/messages.createChat new file mode 100644 index 0000000000..1b5ef7f8b6 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.createChat @@ -0,0 +1,202 @@ + + + + + messages.createChat + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.createChat

+ +

Creates a new chat.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
usersVector<InputUser>List of user IDs to be invited
titlestringChat name
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
500CHAT_ID_GENERATE_FAILEDFailure while generating the chat ID.
400CHAT_INVALIDInvalid chat.
400CHAT_TITLE_EMPTYNo chat title provided.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USERS_TOO_FEWNot enough users (to create a chat, for example).
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.deleteMessages b/data/corefork.telegram.org/method/messages.deleteMessages new file mode 100644 index 0000000000..cf47a052c4 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.deleteMessages @@ -0,0 +1,182 @@ + + + + + messages.deleteMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.deleteMessages

+ +

Deletes messages by their identifiers.

+

+ +
+
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
+---functions---
+messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to delete messages for all participants of the chat
idVector<int>Message ID list
+

Result

+

The method returns the list of successfully deleted messages in Vector<int>.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.discardEncryption b/data/corefork.telegram.org/method/messages.discardEncryption new file mode 100644 index 0000000000..618c8c68b3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.discardEncryption @@ -0,0 +1,187 @@ + + + + + messages.discardEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.discardEncryption

+ +

Cancels a request for creation and/or delete info on secret chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
delete_historyflags.0?trueWhether to delete the entire chat history for the other user as well
chat_idintSecret chat ID
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_EMPTYThe provided chat ID is empty.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatAdmin b/data/corefork.telegram.org/method/messages.editChatAdmin new file mode 100644 index 0000000000..642b52aa3e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatAdmin @@ -0,0 +1,195 @@ + + + + + messages.editChatAdmin + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatAdmin

+ +

Make a user admin in a legacy group.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongThe ID of the group
user_idInputUserThe user to make admin
is_adminBoolWhether to make him admin
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editChatPhoto b/data/corefork.telegram.org/method/messages.editChatPhoto new file mode 100644 index 0000000000..5fb4b4f20e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editChatPhoto @@ -0,0 +1,203 @@ + + + + + messages.editChatPhoto + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editChatPhoto

+ +

Changes chat photo and sends a service message on it

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
chat_idlongChat ID
photoInputChatPhotoPhoto to be set
+

Result

+

Returns a messages.StatedMessage object containing a service message sent during an action.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.editExportedChatInvite b/data/corefork.telegram.org/method/messages.editExportedChatInvite new file mode 100644 index 0000000000..c413c7b4b5 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.editExportedChatInvite @@ -0,0 +1,208 @@ + + + + + messages.editExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.editExportedChatInvite

+ +

Edit an exported chat invite

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+---functions---
+messages.editExportedChatInvite#bdca2f75 flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int request_needed:flags.3?Bool title:flags.4?string = messages.ExportedChatInvite;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.2?trueWhether to revoke the chat invite
peerInputPeerChat
linkstringInvite link
expire_dateflags.0?intNew expiration date
usage_limitflags.1?intMaximum number of users that can join using this link
request_neededflags.3?Bool 
titleflags.4?string 
+

Result

+

messages.ExportedChatInvite

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
403EDIT_BOT_INVITE_FORBIDDEN 
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.forwardMessage b/data/corefork.telegram.org/method/messages.forwardMessage new file mode 100644 index 0000000000..22d984f418 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.forwardMessage @@ -0,0 +1,177 @@ + + + + + messages.forwardMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessage

+ +

Forwards single messages.

+

{schema}

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerUser or chat where a message will be forwarded
idintForwarded message ID
random_idlongUnique client message ID required to prevent message resending
+

Result

+

messages.StatedMessage

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
400YOU_BLOCKED_USERYou blocked this user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.forwardMessages b/data/corefork.telegram.org/method/messages.forwardMessages new file mode 100644 index 0000000000..38a0c3fe2e --- /dev/null +++ b/data/corefork.telegram.org/method/messages.forwardMessages @@ -0,0 +1,388 @@ + + + + + messages.forwardMessages + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.forwardMessages

+ +

Forwards messages by their IDs.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.forwardMessages#cc30290b flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true noforwards:flags.14?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send messages silently (no notification will be triggered on the destination clients)
backgroundflags.6?trueWhether to send the message in background
with_my_scoreflags.8?trueWhen forwarding games, whether to include your score in the game
drop_authorflags.11?trueWhether to forward messages without quoting the original author
drop_media_captionsflags.12?trueWhether to strip captions from media
noforwardsflags.14?true 
from_peerInputPeerSource of messages
idVector<int>IDs of messages
random_idVector<long>Random ID to prevent resending of messages
to_peerInputPeerDestination peer
schedule_dateflags.10?intScheduled message date for scheduled messages
send_asflags.13?InputPeer 
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
406CHAT_FORWARDS_RESTRICTEDYou can't forward messages from a protected chat.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400GROUPED_MEDIA_INVALIDInvalid grouped media.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400QUIZ_ANSWER_MISSING 
500RANDOM_ID_DUPLICATEYou provided a random ID that was already used.
400RANDOM_ID_INVALIDA provided random ID is invalid.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SEND_AS_PEER_INVALIDYou can't send messages as the specified peer.
420SLOWMODE_WAIT_%dSlowmode is enabled in this chat: wait %d seconds before sending another message to this chat.
400SLOWMODE_MULTI_MSGS_DISABLEDSlowmode is enabled, you cannot forward multiple messages to this group.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
403USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getArchivedStickers b/data/corefork.telegram.org/method/messages.getArchivedStickers new file mode 100644 index 0000000000..3ec1016eb7 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getArchivedStickers @@ -0,0 +1,167 @@ + + + + + messages.getArchivedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getArchivedStickers

+ +

Get all archived stickers

+

+ +
+
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
+---functions---
+messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueGet mask stickers
offset_idlongOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.ArchivedStickers

+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getAvailableReactions b/data/corefork.telegram.org/method/messages.getAvailableReactions new file mode 100644 index 0000000000..fa93254446 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getAvailableReactions @@ -0,0 +1,168 @@ + + + + + messages.getAvailableReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getAvailableReactions

+ +

+ +
+
messages.availableReactionsNotModified#9f071957 = messages.AvailableReactions;
+messages.availableReactions#768e3aad hash:int reactions:Vector<AvailableReaction> = messages.AvailableReactions;
+---functions---
+messages.getAvailableReactions#18dea0ac hash:int = messages.AvailableReactions;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
hashint 
+

Result

+

messages.AvailableReactions

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDhConfig b/data/corefork.telegram.org/method/messages.getDhConfig new file mode 100644 index 0000000000..011b820259 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDhConfig @@ -0,0 +1,175 @@ + + + + + messages.getDhConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDhConfig

+ +

Returns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.

+

+ +
+
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
+messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
+---functions---
+messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
versionintValue of the version parameter from messages.dhConfig, avialable at the client
random_lengthintLength of the required random sequence
+

Result

+

messages.DhConfig

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400RANDOM_LENGTH_INVALIDRandom length invalid.
+

Related pages

+

messages.dhConfig

+

New set of configuring parameters.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getDialogFilters b/data/corefork.telegram.org/method/messages.getDialogFilters new file mode 100644 index 0000000000..cc262f566d --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getDialogFilters @@ -0,0 +1,136 @@ + + + + + messages.getDialogFilters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getDialogFilters

+ +

Get folders

+

+ +
+
---functions---
+messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

Vector<DialogFilter>

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywords b/data/corefork.telegram.org/method/messages.getEmojiKeywords new file mode 100644 index 0000000000..54c35573b3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getEmojiKeywords @@ -0,0 +1,149 @@ + + + + + messages.getEmojiKeywords + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywords

+ +

Get localized emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+---functions---
+messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
+

Result

+

EmojiKeywordsDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference b/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference new file mode 100644 index 0000000000..38fc7adcb0 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference @@ -0,0 +1,154 @@ + + + + + messages.getEmojiKeywordsDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getEmojiKeywordsDifference

+ +

Get changed emoji keywords

+

+ +
+
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
+---functions---
+messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious emoji keyword localization version
+

Result

+

EmojiKeywordsDifference

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getHistory b/data/corefork.telegram.org/method/messages.getHistory new file mode 100644 index 0000000000..0ca63ecbb4 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getHistory @@ -0,0 +1,227 @@ + + + + + messages.getHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getHistory

+ +

Gets back the conversation history with one interlocutor / within a chat

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerTarget peer
offset_idintOnly return messages starting from the specified message ID
offset_dateintOnly return messages sent before the specified date
add_offsetintNumber of list elements to be skipped, negative values are also accepted.
limitintNumber of results to return
max_idintIf a positive value was transferred, the method will return only messages with IDs less than max_id
min_idintIf a positive value was transferred, the method will return only messages with IDs more than min_id
hashlongResult hash
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getInlineGameHighScores b/data/corefork.telegram.org/method/messages.getInlineGameHighScores new file mode 100644 index 0000000000..0a5909de87 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getInlineGameHighScores @@ -0,0 +1,177 @@ + + + + + messages.getInlineGameHighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getInlineGameHighScores

+ +

Get highscores of a game sent using an inline bot

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+---functions---
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
idInputBotInlineMessageIDID of inline message
user_idInputUserGet high scores of a certain user
+

Result

+

messages.HighScores

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getMessagesViews b/data/corefork.telegram.org/method/messages.getMessagesViews new file mode 100644 index 0000000000..d846de198f --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getMessagesViews @@ -0,0 +1,199 @@ + + + + + messages.getMessagesViews + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getMessagesViews

+ +

Get and increase the view counter of a message sent or forwarded from a channel

+

+ +
+
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
+---functions---
+messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer where the message was found
idVector<int>ID of message
incrementBoolWhether to mark the message as viewed and increment the view counter
+

Result

+

Vector<int>

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getScheduledHistory b/data/corefork.telegram.org/method/messages.getScheduledHistory new file mode 100644 index 0000000000..45d8596408 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getScheduledHistory @@ -0,0 +1,182 @@ + + + + + messages.getScheduledHistory + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getScheduledHistory

+ +

Get scheduled messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerPeer
hashlongHash for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getSearchResultsPositions b/data/corefork.telegram.org/method/messages.getSearchResultsPositions new file mode 100644 index 0000000000..35758e3a95 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getSearchResultsPositions @@ -0,0 +1,198 @@ + + + + + messages.getSearchResultsPositions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getSearchResultsPositions

+ +

+ +
+
messages.searchResultsPositions#53b22baf count:int positions:Vector<SearchResultsPosition> = messages.SearchResultsPositions;
+---functions---
+messages.getSearchResultsPositions#6e9583a3 peer:InputPeer filter:MessagesFilter offset_id:int limit:int = messages.SearchResultsPositions;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeer 
filterMessagesFilter 
offset_idint 
limitint 
+

Result

+

messages.SearchResultsPositions

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.getWebPage b/data/corefork.telegram.org/method/messages.getWebPage new file mode 100644 index 0000000000..627a58a74a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.getWebPage @@ -0,0 +1,177 @@ + + + + + messages.getWebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.getWebPage

+ +

Get instant view page

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+---functions---
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
urlstringURL of IV page to fetch
hashintHash for pagination, for more info click here
+

Result

+

WebPage

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400WC_CONVERT_URL_INVALIDWC convert URL invalid.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.markDialogUnread b/data/corefork.telegram.org/method/messages.markDialogUnread new file mode 100644 index 0000000000..da62daa992 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.markDialogUnread @@ -0,0 +1,177 @@ + + + + + messages.markDialogUnread + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.markDialogUnread

+ +

Manually mark dialog as unread

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueMark as unread/read
peerInputDialogPeerDialog
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readMentions b/data/corefork.telegram.org/method/messages.readMentions new file mode 100644 index 0000000000..29727316c7 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readMentions @@ -0,0 +1,181 @@ + + + + + messages.readMentions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readMentions

+ +

Mark mentions as read

+

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerDialog
+

Result

+

messages.AffectedHistory

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.readReactions b/data/corefork.telegram.org/method/messages.readReactions new file mode 100644 index 0000000000..c78b934815 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.readReactions @@ -0,0 +1,167 @@ + + + + + messages.readReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.readReactions

+ +

+ +
+
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
+---functions---
+messages.readReactions#82e251d7 peer:InputPeer = messages.AffectedHistory;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeer 
+

Result

+

messages.AffectedHistory

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.requestEncryption b/data/corefork.telegram.org/method/messages.requestEncryption new file mode 100644 index 0000000000..15d5b17905 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.requestEncryption @@ -0,0 +1,185 @@ + + + + + messages.requestEncryption + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.requestEncryption

+ +

Sends a request to start a secret chat to the user.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+---functions---
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
user_idInputUserUser ID
random_idintUnique client request ID required to prevent resending. This also doubles as the chat ID.
g_abytesA = g ^ a mod p, see Wikipedia
+

Result

+

EncryptedChat

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400DH_G_A_INVALIDg_a invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.saveDraft b/data/corefork.telegram.org/method/messages.saveDraft new file mode 100644 index 0000000000..d508cf317a --- /dev/null +++ b/data/corefork.telegram.org/method/messages.saveDraft @@ -0,0 +1,202 @@ + + + + + messages.saveDraft + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveDraft

+ +

Save a message draft associated to a chat.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable generation of the webpage preview
reply_to_msg_idflags.0?intMessage ID the message should reply to
peerInputPeerDestination of the message that should be sent
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Message drafts

+

How to handle message drafts

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.saveRecentSticker b/data/corefork.telegram.org/method/messages.saveRecentSticker new file mode 100644 index 0000000000..23596b01cb --- /dev/null +++ b/data/corefork.telegram.org/method/messages.saveRecentSticker @@ -0,0 +1,182 @@ + + + + + messages.saveRecentSticker + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.saveRecentSticker

+ +

Add/remove sticker from recent stickers list

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueWhether to add/remove stickers recently attached to photo or video files
idInputDocumentSticker
unsaveBoolWhether to save or unsave the sticker
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.search b/data/corefork.telegram.org/method/messages.search new file mode 100644 index 0000000000..e4e02e2f83 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.search @@ -0,0 +1,291 @@ + + + + + messages.search + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.search

+ +

Gets back found messages

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerUser or chat, histories with which are searched, or (inputPeerEmpty) constructor for global search
qstringText search request
from_idflags.0?InputPeerOnly return messages sent by the specified user ID
top_msg_idflags.1?intThread ID
filterMessagesFilterFilter to return only specified message types
min_dateintIf a positive value was transferred, only messages with a sending date bigger than the transferred one will be returned
max_dateintIf a positive value was transferred, only messages with a sending date smaller than the transferred one will be returned
offset_idintOnly return messages starting from the specified message ID
add_offsetintAdditional offset
limitintNumber of results to return
max_idintMaximum message ID to return
min_idintMinimum message ID to return
hashlongHash
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400FROM_PEER_INVALIDThe specified from_id is invalid.
400INPUT_FILTER_INVALIDThe specified filter is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PEER_ID_NOT_SUPPORTEDThe provided peer ID is not supported.
400SEARCH_QUERY_EMPTYThe search query is empty.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Related pages

+

inputPeerEmpty

+

An empty constructor, no user or chat is defined.

+

Threads

+

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.searchGifs b/data/corefork.telegram.org/method/messages.searchGifs new file mode 100644 index 0000000000..606fad0099 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.searchGifs @@ -0,0 +1,177 @@ + + + + + messages.searchGifs + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGifs

+ +

Search for GIFs

+

+ +
+
 Method schema is available as of layer 114. Switch »

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
qstringText query
offsetintOffset for pagination »
+

Result

+

messages.FoundGifs

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.searchGlobal b/data/corefork.telegram.org/method/messages.searchGlobal new file mode 100644 index 0000000000..61fce793af --- /dev/null +++ b/data/corefork.telegram.org/method/messages.searchGlobal @@ -0,0 +1,226 @@ + + + + + messages.searchGlobal + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.searchGlobal

+ +

Search for messages and peers globally

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
qstringQuery
filterMessagesFilterGlobal search filter
min_dateintIf a positive value was specified, the method will return only messages with date bigger than min_date
max_dateintIf a positive value was transferred, the method will return only messages with date smaller than max_date
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintOffsets for pagination, for more info click here
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400SEARCH_QUERY_EMPTYThe search query is empty.
+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+

messages.messagesSlice

+

Incomplete list of messages and auxiliary data.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendMedia b/data/corefork.telegram.org/method/messages.sendMedia new file mode 100644 index 0000000000..be87747d93 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendMedia @@ -0,0 +1,543 @@ + + + + + messages.sendMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendMedia

+ +

Send a media

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendMedia#e25ff8e0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true noforwards:flags.14?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueSend message silently (no notification should be triggered)
backgroundflags.6?trueSend message in background
clear_draftflags.7?trueClear the draft
noforwardsflags.14?true 
peerInputPeerDestination
reply_to_msg_idflags.0?intMessage ID to which this message should reply to
mediaInputMediaAttached media
messagestringCaption
random_idlongRandom ID to avoid resending the same message
reply_markupflags.2?ReplyMarkupReply markup for bot keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
send_asflags.13?InputPeer 
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400BOT_PAYMENTS_DISABLEDPlease enable bot payments in botfather before calling this method.
400BOT_POLLS_DISABLED 
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_FORWARDS_RESTRICTEDYou can't forward messages from a protected chat.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CURRENCY_TOTAL_AMOUNT_INVALIDThe total amount of all prices is invalid.
400EMOTICON_INVALIDThe specified emoji is invalid.
400EXTERNAL_URL_INVALIDExternal URL invalid.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_LENGTH_INVALIDThe length of a file part is invalid.
400FILE_REFERENCE_EMPTYAn empty file reference was specified.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in the documentation.
400GAME_BOT_INVALIDBots can't send another bot's game.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PAYMENT_PROVIDER_INVALIDThe specified payment provider is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400POLL_ANSWERS_INVALIDInvalid poll answers were provided.
400POLL_ANSWER_INVALIDOne of the poll answers is not acceptable.
400POLL_OPTION_DUPLICATEDuplicate poll options provided.
400POLL_OPTION_INVALIDInvalid poll option provided.
400POLL_QUESTION_INVALIDOne of the poll questions is not acceptable.
400QUIZ_CORRECT_ANSWERS_EMPTYNo correct quiz answer was specified.
400QUIZ_CORRECT_ANSWERS_TOO_MUCHYou specified too many correct answers in a quiz, quizes can only have one right answer!
400QUIZ_CORRECT_ANSWER_INVALIDAn invalid value was provided to the correct_answers field.
400QUIZ_MULTIPLE_INVALIDQuizes can't have the multiple_choice flag set!
500RANDOM_ID_DUPLICATEYou provided a random ID that was already used.
400REPLY_MARKUP_BUY_EMPTYReply markup for buy button empty.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SEND_AS_PEER_INVALIDYou can't send messages as the specified peer.
420SLOWMODE_WAIT_%dSlowmode is enabled in this chat: wait %d seconds before sending another message to this chat.
400TTL_MEDIA_INVALIDInvalid media Time To Live was provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
403USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400VIDEO_CONTENT_TYPE_INVALIDThe video's content type is invalid.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
+

Bots can use this method

+

Related pages

+

Styled text with message entities

+

How to create styled text with message entities

+

Scheduled messages

+

Telegram allows scheduling messages

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendScreenshotNotification b/data/corefork.telegram.org/method/messages.sendScreenshotNotification new file mode 100644 index 0000000000..8cef019573 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendScreenshotNotification @@ -0,0 +1,187 @@ + + + + + messages.sendScreenshotNotification + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendScreenshotNotification

+ +

Notify the other user in a private chat that a screenshot of the chat was taken

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerOther user
reply_to_msg_idintID of message that was screenshotted, can be 0
random_idlongRandom ID to avoid message resending
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
400YOU_BLOCKED_USERYou blocked this user.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.sendVote b/data/corefork.telegram.org/method/messages.sendVote new file mode 100644 index 0000000000..f7995b79c3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.sendVote @@ -0,0 +1,220 @@ + + + + + messages.sendVote + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.sendVote

+ +

Vote in a poll

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe chat where the poll was sent
msg_idintThe message ID of the poll
optionsVector<bytes>The options that were chosen
+

Result

+

Updates

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_POLL_CLOSEDPoll closed.
400OPTIONS_TOO_MUCHToo many options provided.
400OPTION_INVALIDInvalid option selected.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REVOTE_NOT_ALLOWEDYou cannot change your vote.
+

Related pages

+

poll

+

Poll

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setChatAvailableReactions b/data/corefork.telegram.org/method/messages.setChatAvailableReactions new file mode 100644 index 0000000000..a269519c6b --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setChatAvailableReactions @@ -0,0 +1,184 @@ + + + + + messages.setChatAvailableReactions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setChatAvailableReactions

+ +

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+messages.setChatAvailableReactions#14050ea6 peer:InputPeer available_reactions:Vector<string> = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeer 
available_reactionsVector<string> 
+

Result

+

Updates

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.setInlineBotResults b/data/corefork.telegram.org/method/messages.setInlineBotResults new file mode 100644 index 0000000000..707b6ccae3 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.setInlineBotResults @@ -0,0 +1,363 @@ + + + + + messages.setInlineBotResults + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.setInlineBotResults

+ +

Answer an inline query, for bots only

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueSet this flag if the results are composed of media files
privateflags.1?trueSet this flag if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
query_idlongUnique identifier for the answered query
resultsVector<InputBotInlineResult>Vector of results for the inline query
cache_timeintThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
next_offsetflags.2?stringPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don‘t support pagination. Offset length can’t exceed 64 bytes.
switch_pmflags.3?InlineBotSwitchPMIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with a certain parameter.
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400ARTICLE_TITLE_EMPTYThe title of the article is empty.
400AUDIO_CONTENT_URL_EMPTYThe remote URL specified in the content field is empty.
400AUDIO_TITLE_EMPTYAn empty audio title was provided.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400DOCUMENT_INVALIDThe specified document is invalid.
400FILE_CONTENT_TYPE_INVALIDFile content-type is invalid.
400FILE_TITLE_EMPTYAn empty file title was specified.
400GIF_CONTENT_TYPE_INVALIDGIF content-type invalid.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400NEXT_OFFSET_INVALIDThe specified offset is longer than 64 bytes.
400PHOTO_CONTENT_TYPE_INVALIDPhoto mime-type invalid.
400PHOTO_CONTENT_URL_EMPTYPhoto URL invalid.
400PHOTO_INVALIDPhoto invalid.
400PHOTO_THUMB_URL_EMPTYPhoto thumbnail URL is empty.
400QUERY_ID_INVALIDThe query ID is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400RESULTS_TOO_MUCHToo many results were provided.
400RESULT_ID_DUPLICATEYou provided a duplicate result ID.
400RESULT_TYPE_INVALIDResult type invalid.
400SEND_MESSAGE_MEDIA_INVALIDInvalid media provided.
400SEND_MESSAGE_TYPE_INVALIDThe message type is invalid.
400START_PARAM_INVALIDStart parameter invalid.
400STICKER_DOCUMENT_INVALIDThe specified sticker document is invalid.
400URL_INVALIDInvalid URL provided.
403USER_BOT_INVALIDThis method can only be called by a bot.
400VIDEO_TITLE_EMPTYThe specified video title is empty.
400WEBDOCUMENT_INVALIDInvalid webdocument URL provided.
400WEBDOCUMENT_MIME_INVALIDInvalid webdocument mime type provided.
400WEBDOCUMENT_SIZE_TOO_BIGWebdocument is too big!
400WEBDOCUMENT_URL_INVALIDThe specified webdocument URL is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.toggleStickerSets b/data/corefork.telegram.org/method/messages.toggleStickerSets new file mode 100644 index 0000000000..ecbb629ad8 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.toggleStickerSets @@ -0,0 +1,170 @@ + + + + + messages.toggleStickerSets + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.toggleStickerSets

+ +

Apply changes to multiple stickersets

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
uninstallflags.0?trueUninstall the specified stickersets
archiveflags.1?trueArchive the specified stickersets
unarchiveflags.2?trueUnarchive the specified stickersets
stickersetsVector<InputStickerSet>Stickersets to act upon
+

Result

+

Bool

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.translateText b/data/corefork.telegram.org/method/messages.translateText new file mode 100644 index 0000000000..a4a1518371 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.translateText @@ -0,0 +1,199 @@ + + + + + messages.translateText + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.translateText

+ +

+ +
+
messages.translateNoResult#67ca4737 = messages.TranslatedText;
+messages.translateResultText#a214f7d0 text:string = messages.TranslatedText;
+---functions---
+messages.translateText#24ce6dee flags:# peer:flags.0?InputPeer msg_id:flags.0?int text:flags.1?string from_lang:flags.2?string to_lang:string = messages.TranslatedText;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerflags.0?InputPeer 
msg_idflags.0?int 
textflags.1?string 
from_langflags.2?string 
to_langstring 
+

Result

+

messages.TranslatedText

+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder b/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder new file mode 100644 index 0000000000..2e8ff2b873 --- /dev/null +++ b/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder @@ -0,0 +1,153 @@ + + + + + messages.updateDialogFiltersOrder + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.updateDialogFiltersOrder

+ +

Reorder folders

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
orderVector<int>New folder order
+

Result

+

Bool

+

Related pages

+

Folders

+

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.getPaymentForm b/data/corefork.telegram.org/method/payments.getPaymentForm new file mode 100644 index 0000000000..12db09b988 --- /dev/null +++ b/data/corefork.telegram.org/method/payments.getPaymentForm @@ -0,0 +1,181 @@ + + + + + payments.getPaymentForm + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getPaymentForm

+ +

Get a payment form

+

+ +
+
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
+---functions---
+payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of payment form
theme_paramsflags.0?DataJSONA JSON object with the following keys, containing color theme information (integers, RGB24) to pass to the payment provider, to apply in eventual verification pages:
bg_color - Background color
text_color - Text color
hint_color - Hint text color
link_color - Link color
button_color - Button color
button_text_color - Button text color
+

Result

+

payments.PaymentForm

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/payments.getPaymentReceipt b/data/corefork.telegram.org/method/payments.getPaymentReceipt new file mode 100644 index 0000000000..572da4986e --- /dev/null +++ b/data/corefork.telegram.org/method/payments.getPaymentReceipt @@ -0,0 +1,171 @@ + + + + + payments.getPaymentReceipt + + + + + + + + + + + + + +
+ +
+
+
+ +

payments.getPaymentReceipt

+ +

Get payment receipt

+

+ +
+
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
+---functions---
+payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPeerThe peer where the payment receipt was sent
msg_idintMessage ID of receipt
+

Result

+

payments.PaymentReceipt

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.confirmCall b/data/corefork.telegram.org/method/phone.confirmCall new file mode 100644 index 0000000000..2438b77914 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.confirmCall @@ -0,0 +1,188 @@ + + + + + phone.confirmCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.confirmCall

+ +

Complete phone call E2E encryption key exchange »

+

+ +
+
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
+---functions---
+phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
peerInputPhoneCallThe phone call
g_abytesParameter for E2E encryption key exchange »
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolPhone call settings
+

Result

+

phone.PhoneCall

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+

Related pages

+

End-to-End Encrypted Voice Calls

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.getCallConfig b/data/corefork.telegram.org/method/phone.getCallConfig new file mode 100644 index 0000000000..8d619db3a6 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.getCallConfig @@ -0,0 +1,134 @@ + + + + + phone.getCallConfig + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getCallConfig

+ +

Get phone call configuration to be passed to libtgvoip's shared config

+

+ +
+
dataJSON#7d748d04 data:string = DataJSON;
+---functions---
+phone.getCallConfig#55451fa9 = DataJSON;

+

Parameters

+

This constructor does not require any parameters.

+

Result

+

DataJSON

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.getGroupCall b/data/corefork.telegram.org/method/phone.getGroupCall new file mode 100644 index 0000000000..0391c31494 --- /dev/null +++ b/data/corefork.telegram.org/method/phone.getGroupCall @@ -0,0 +1,174 @@ + + + + + phone.getGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.getGroupCall

+ +

Get info about a group call

+

+ +
+
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
+---functions---
+phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
limitintMaximum number of results to return, see pagination
+

Result

+

phone.GroupCall

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400GROUPCALL_INVALID 
+

Related pages

+

Pagination in the API

+

How to fetch results from large lists of objects.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.leaveGroupCall b/data/corefork.telegram.org/method/phone.leaveGroupCall new file mode 100644 index 0000000000..3d786beb5f --- /dev/null +++ b/data/corefork.telegram.org/method/phone.leaveGroupCall @@ -0,0 +1,160 @@ + + + + + phone.leaveGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.leaveGroupCall

+ +

Leave a group call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe group call
sourceintYour source ID
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.setCallRating b/data/corefork.telegram.org/method/phone.setCallRating new file mode 100644 index 0000000000..01b86c94de --- /dev/null +++ b/data/corefork.telegram.org/method/phone.setCallRating @@ -0,0 +1,192 @@ + + + + + phone.setCallRating + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.setCallRating

+ +

Rate a call

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
user_initiativeflags.0?trueWhether the user decided on their own initiative to rate the call
peerInputPhoneCallThe call to rate
ratingintRating in 1-5 stars
commentstringAn additional comment
+

Result

+

Updates with info about the rating message sent to the official VoIP bot

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.startScheduledGroupCall b/data/corefork.telegram.org/method/phone.startScheduledGroupCall new file mode 100644 index 0000000000..501564308a --- /dev/null +++ b/data/corefork.telegram.org/method/phone.startScheduledGroupCall @@ -0,0 +1,155 @@ + + + + + phone.startScheduledGroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.startScheduledGroupCall

+ +

Start a scheduled group call.

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
callInputGroupCallThe scheduled group call
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallRecord b/data/corefork.telegram.org/method/phone.toggleGroupCallRecord new file mode 100644 index 0000000000..9f1c56782f --- /dev/null +++ b/data/corefork.telegram.org/method/phone.toggleGroupCallRecord @@ -0,0 +1,180 @@ + + + + + phone.toggleGroupCallRecord + + + + + + + + + + + + + +
+ +
+
+
+ +

phone.toggleGroupCallRecord

+ +

Start or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).

+

+ +
+
updatesTooLong#e317af7e = Updates;
+updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+updateShort#78d4dec1 update:Update date:int = Updates;
+updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
+---functions---
+phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
startflags.0?trueWhether to start or stop recording
videoflags.2?trueWhether to also record video streams
callInputGroupCallThe group call or livestream
titleflags.1?stringRecording title
video_portraitflags.2?BoolIf video stream recording is enabled, whether to record in portrait or landscape mode
+

Result

+

Updates

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stats.getMegagroupStats b/data/corefork.telegram.org/method/stats.getMegagroupStats new file mode 100644 index 0000000000..614c4f8164 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.getMegagroupStats @@ -0,0 +1,191 @@ + + + + + stats.getMegagroupStats + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getMegagroupStats

+ +

Get supergroup statistics

+

+ +
+
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
+---functions---
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelSupergroup ID
+

Result

+

stats.MegagroupStats

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stats.getMessagePublicForwards b/data/corefork.telegram.org/method/stats.getMessagePublicForwards new file mode 100644 index 0000000000..b1fe7c1e74 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.getMessagePublicForwards @@ -0,0 +1,212 @@ + + + + + stats.getMessagePublicForwards + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.getMessagePublicForwards

+ +

Obtains a list of messages, indicating to which other public channels was a channel message forwarded.
+Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.

+

+ +
+
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
+messages.messagesNotModified#74535f21 count:int = messages.Messages;
+---functions---
+stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
channelInputChannelSource channel
msg_idintSource message ID
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
+

Result

+

messages.Messages

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
+

Related pages

+

messages.messagesSlice

+

Incomplete list of messages and auxiliary data.

+

Pagination in the API

+

How to fetch results from large lists of objects.

+

message

+

A message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stats.loadAsyncGraph b/data/corefork.telegram.org/method/stats.loadAsyncGraph new file mode 100644 index 0000000000..f22663b066 --- /dev/null +++ b/data/corefork.telegram.org/method/stats.loadAsyncGraph @@ -0,0 +1,193 @@ + + + + + stats.loadAsyncGraph + + + + + + + + + + + + + +
+ +
+
+
+ +

stats.loadAsyncGraph

+ +

Load channel statistics graph asynchronously

+

+ +
+
statsGraphAsync#4a27eb2d token:string = StatsGraph;
+statsGraphError#bedc9822 error:string = StatsGraph;
+statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
+---functions---
+stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
flags#Flags, see TL conditional fields
tokenstringGraph token from statsGraphAsync constructor
xflags.0?longZoom value, if required
+

Result

+

StatsGraph

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400GRAPH_EXPIRED_RELOADThis graph has expired, please obtain a new graph token.
400GRAPH_INVALID_RELOADInvalid graph token provided, please reload the stats and provide the updated token.
400GRAPH_OUTDATED_RELOADThe graph is outdated, please get a new async token using stats.getBroadcastStats.
+

Related pages

+

statsGraphAsync

+

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/stickers.suggestShortName b/data/corefork.telegram.org/method/stickers.suggestShortName new file mode 100644 index 0000000000..6f0a3d3177 --- /dev/null +++ b/data/corefork.telegram.org/method/stickers.suggestShortName @@ -0,0 +1,166 @@ + + + + + stickers.suggestShortName + + + + + + + + + + + + + +
+ +
+
+
+ +

stickers.suggestShortName

+ +

Suggests a short name for a given stickerpack name

+

+ +
+
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+---functions---
+stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
titlestringSticker pack name
+

Result

+

stickers.SuggestedShortName

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400TITLE_INVALIDThe specified stickerpack title is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.getWebFile b/data/corefork.telegram.org/method/upload.getWebFile new file mode 100644 index 0000000000..2d89947e10 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.getWebFile @@ -0,0 +1,176 @@ + + + + + upload.getWebfile + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.getWebfile

+ +

Returns content of an HTTP file or a part, by proxying the request through telegram.

+

+ +
+
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
+---functions---
+upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
locationInputWebFileLocationThe file to download
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
+

Result

+

upload.WebFile

+

Possible errors

+ + + + + + + + + + + + + + + +
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/upload.saveBigFilePart b/data/corefork.telegram.org/method/upload.saveBigFilePart new file mode 100644 index 0000000000..bca0225981 --- /dev/null +++ b/data/corefork.telegram.org/method/upload.saveBigFilePart @@ -0,0 +1,208 @@ + + + + + upload.saveBigFilePart + + + + + + + + + + + + + +
+ +
+
+
+ +

upload.saveBigFilePart

+ +

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

+

+ +
+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;

+

Parameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
file_idlongRandom file id, created by the client
file_partintPart sequence number
file_total_partsintTotal number of parts
bytesbytesBinary data, part contents
+

Result

+

Bool

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
400FILE_PART_SIZE_CHANGEDProvided file part size has changed.
400FILE_PART_SIZE_INVALIDThe provided file part size is invalid.
400FILE_PART_TOO_BIGThe uploaded file part is too big.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/method/users.getFullUser b/data/corefork.telegram.org/method/users.getFullUser new file mode 100644 index 0000000000..e795a3a644 --- /dev/null +++ b/data/corefork.telegram.org/method/users.getFullUser @@ -0,0 +1,177 @@ + + + + + users.getFullUser + + + + + + + + + + + + + +
+ +
+
+
+ +

users.getFullUser

+ +

Returns extended user info by ID.

+

+ +
+
users.userFull#3b6d152e full_user:UserFull chats:Vector<Chat> users:Vector<User> = users.UserFull;
+---functions---
+users.getFullUser#b60f5918 id:InputUser = users.UserFull;

+

Parameters

+ + + + + + + + + + + + + + + +
NameTypeDescription
idInputUserUser ID
+

Result

+

Returns a UserFull object containing user info.

+

Possible errors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
+

Bots can use this method

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-combinators.html b/data/corefork.telegram.org/mtproto/TL-combinators.html new file mode 100644 index 0000000000..4d6c7dc85c --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-combinators.html @@ -0,0 +1,251 @@ + + + + + Formal description of TL combinators + + + + + + + + + + + + + +
+ +
+
+
+ +

Formal description of TL combinators

+ +

Formal declaration of TL combinators

+

Main article: Formal description of TL. See also TL Language.

+

Combinators in TL are declared as follows:

+
+

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
+full-combinator-id ::= lc-ident-full | _
+combinator-id ::= lc-ident-ns | _
+opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
+args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
+args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
+args ::= [ ! ] type-term
+multiplicity ::= nat-term
+var-ident-opt ::= var-ident | _
+conditional-arg-def ::= var-ident [ . nat-const ] ?
+result-type ::= boxed-type-ident { subexpr }
+result-type ::= boxed-type-ident < subexpr { , subexpr } >

+
+

We shall clarify what all this means.

+
    +
  • +

    A combinator identifier is either an identifier starting with a lowercase Latin letter (lc-ident), or a namespace identifier (also lc-ident) followed by a period and another lc-ident. Therefore, cons and lists.get are valid combinator identifiers.

    +
  • +
  • +

    A combinator has a name, also known as a number (not to be confused with the designation) -- a 32-bit number that unambiguously determines it. It is either calculated automatically (see below) or it is explicitly assigned in the declaration. To do this, a hash mark (#) and exactly 8 hexadecimal digits -- the combinator’s name -- are added to the identifier of the combinator being defined.

    +
  • +
  • +

    A combinator’s declaration begins with its identifier, to which its name (separated by a hash mark) may have been added.

    +
  • +
  • +

    After the combinator identifier comes the main part of the declaration, which consists of declarations of fields (or variables), including an indication of their types.

    +
  • +
  • +

    First come declarations of optional fields (of which there may be several or none at all). Then there are the declarations of the required fields (there may not be any of these either).

    +
  • +
  • +

    Any identifier that begins with an uppercase or lowercase letter and which does not contain references to a namespace can be a field (variable) identifier. Using uc-ident for identifiers of variable types and lc-indent for other variables is good practice.

    +
  • +
  • +

    Next a combinator declaration contains the equals sign (=) and the result type (it may be composite or appearing for the first time). The result type may be polymorphic and/or dependent; any fields of the defined constructor’s fields of type Type or # may be returned (as subexpressions).

    +
  • +
  • +

    A combinator declaration is terminated with a semicolon.

    +
  • +
+

In what follows, a constructor’s fields, variables, and arguments mean the same thing.

+

Optional field declarations

+
    +
  • +

    These have the form { field_1 ... field_k : type-expr }, where field_i is a variable (field) identifier that is unique within the scope of the combinator declaration, and type-expr is a type shared by all of the fields.

    +
  • +
  • +

    If k>1, this entry is functionally equivalent to { field_1 : type-expr } ... { field_k : type-expr }.

    +
  • +
  • +

    All optional fields must be explicitly named (using _ instead of field_i is not allowed).

    +
  • +
  • +

    Moreover, at present the names of all optional fields must share the combinator’s result type (possibly more than once) and themselves be of type # (i,e., nat) or Type. Therefore, if the exact result type is known, it is possible to determine the values of all of the combinator’s implicit parameters (possibly obtaining a contradiction of the form 2=3 in doing so, which means that the combinator is not allowed in the context).

    +
  • +
+

Required field declarations

+
    +
  • +

    These may have the form ( field_1 ... field_k : type-expr ), similar to an optional field declaration, but with parentheses. This entry is equivalent to ( field_1 : type-expr ) ... ( field_k : type-expr ), where the fields are defined one at a time.

    +
  • +
  • +

    The underscore sign (_) can be used as names of one or more fields (field_i), indicating that the field is anonymous (the exact name is unimportant).

    +
  • +
  • +

    One field may be declared without outer parentheses, like this: field_id : type-expr. Here, however, if type-expr is a complex type, parentheses may be necessary around type-expr (this is reflected in BNF).

    +
  • +
  • +

    Furthermore, one anonymous field may be declared using a type-expr entry, functionally equivalent to _ : type-expr.

    +
  • +
  • +

    Required field declarations follow one after another, separated by spaces (by any number of whitespace symbols, to be more precise).

    +
  • +
  • +

    The declared field’s type (type-expr) may use the declared combinator’s previously defined variables (fields) as subexpressions (i.e. parameter values). For example:

    +

    nil {X:Type} = List X; +cons {X:Type} hd:X tl:(list X) = List X; +typed_list (X:Type) (l : list X) = TypedList;

    +
  • +
+

Repetitions

+
    +
  • +

    These may only exist among required parameters. They have the form [ field-id : ] [ multiplicity * ] [ args ], where args has the same format as the combinator’s declaration of (several) required fields, except that all of the enclosing combinator’s previously declared fields may be used in the argument types.

    +
  • +
  • +

    The name of a field of an enclosing combinator that receives a repetition as a value may be specified (field-id), or bypassed, which is equivalent to using the underscore sign as a field-id.

    +
  • +
  • +

    The multiplicity field is an expression of the type # (nat), which can be a real constant, the name of a preceding field of type #, or an expression in the form ( c + v ), where c is a real constant and v is the name of a field of type #. The sense of the multiplicity field is to provide the length of the (repetition) vector, each element of which consists of values of the types enumerated in args.

    +
  • +
  • +

    The multiplicity field may be bypassed. In this case, the last preceding parameter of type # from the enclosing combinator is used (it must be).

    +
  • +
  • +

    Functionally, the repetition field-id : multiplicity * [ args ] is equivalent to the declaration of the single field ( field-id : %Tuple %AuxType multiplicity ), where aux_type is an auxiliary type with a new name defined as aux_type *args* = AuxType. If any of the enclosing type’s fields are used within args, they are added to the auxiliary constructor aux_type and to its AuxType result type as the first (optional) parameters.

    +
  • +
  • +

    If args consists of one anonymous field of type some-type, then some-type can be used directly instead of %AuxType.

    +
  • +
  • +

    If during implementation the repetitions are rewritten as indicated above, it is logical to use instead of aux_type and AuxType, some identifiers that contain the name of the outer combinator being defined and the repetition’s index number inside its definition.

    +
  • +
+

Example:

+
matrix {m n : #} a : m* [ n* [ double ] ] = Matrix m n;
+

is functionally equivalent to

+
aux_type {n : #} (_ : %Tuple double n) = AuxType n;
+matrix {m : #} {n : #} (a : %Tuple %(AuxType n) m) = Matrix m n;
+

Moreover, the built-in types Tuple and Vector could be defined as:

+
tnil {X : Type} = Tuple X 0;
+tcons {X : Type} {n : #} hd:X tl:%(Tuple X n) = Tuple X (S n);
+vector {X : Type} (n : #) (v : %(Tuple X n)) = Vector X;
+

Actually, the following equivalent entry is considered the definition of Vector (i.e. it is specifically this entry that is used to compute the name of the vector constructor and its partial applications):

+
vector {t : Type} # [ t ] = Vector t;
+

If we expand it using Tuple, we obtain the previous definition exactly.

+

Conditional fields

+

The construction

+
+

args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
+conditional-arg-def ::= var-ident [ . nat-const ] ?

+
+

permits assigning fields which are only present if the value of a preceding mandatory or optional field of type # is not null (or if its chosen bit is not zero if the special binary bit-selection operator . is applied). +Example:

+
+

user {fields:#} id:int first_name:(fields.0?string) last_name:(fields.1?string) friends:(fields.2?%(Vector int)) = User fields;
+get_users req_fields:# ids:%(Vector int) = Vector %(User req_fields)

+
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-types.html b/data/corefork.telegram.org/mtproto/TL-types.html new file mode 100644 index 0000000000..28c1e276c4 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-types.html @@ -0,0 +1,124 @@ + + + + + Type serialization + + + + + + + + + + + + + +
+ +
+
+
+ +

Type serialization

+ +

See Polymorphism in TL and TL Language.

+

It remains to describe how types, e.g. values of type Type, are transmitted (serialized). In general, there is nothing unexpected going on here: we have type constructors of various arities (for example, List is an arity-1 constructor, but IntList is a 0-arity constructor); and if we know that a 32-bit “name” is assigned to each type constructor, there are no further questions -- values of type Type are serialized exactly like values of any other recursive type with a defined set of constructors of differing arity.

+

How can a 32-bit “name” be assigned to a type (a type constructor, to be more exact) such as List or IntList? +It is proposed to use the sum of the names of all of its constructors, plus the CRC32 of the string with the designation of the type's name and all of its parameters such as “IntList = Type” or “List X:Type = Type”. This way, the List constructor’s “name” is the sum of the CRC32s of the three strings "List X:Type = Type", "cons X:Type hd:X tl:List X = List X", and "nil X:Type = List X". +For “bare” types (which, formally speaking, are subtypes of the corresponding “boxed” type), the situation is somewhat more complicated; the logical negation of the corresponding constructor’s name is used. For built-in bareand boxed types (for example, int and Int), a pseudo-declaration is used (for example, int ? = Int").

+
    +
  • This description is somewhat outdated and may be updated in the future. Specifically, how to treat the ! modifier has not been explained.*
  • +
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/mtproto-transports.html b/data/corefork.telegram.org/mtproto/mtproto-transports.html new file mode 100644 index 0000000000..56c94a6bbb --- /dev/null +++ b/data/corefork.telegram.org/mtproto/mtproto-transports.html @@ -0,0 +1,294 @@ + + + + + MTProto transports + + + + + + + + + + + + + +
+ +
+
+
+ +

MTProto transports

+ +
+ +

Here's a list of MTProto transport protocols (see the ISO/OSI recap for a full explanation):

+ +

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header. +Additionally, the following transport features can be used:

+ +

Example implementations for these protocols can be seen in tdlib and MadelineProto.

+

Abridged

+

The lightest protocol available.

+
    +
  • Overhead: Very small
  • +
  • Minimum envelope length: 1 byte
  • +
  • Maximum envelope length: 4 bytes
  • +
+

Payload structure:

+
+-+----...----+
+|l|  payload  |
++-+----...----+
+OR
+
++-+---+----...----+
+|h|len|  payload  +
++-+---+----...----+
+

Before sending anything into the underlying socket (see transports), the client must first send 0xef as the first byte (the server will not send 0xef as the first byte in the first reply).
+Then, payloads are wrapped in the following envelope:

+
    +
  • Length: payload length, divided by four, and encoded as a single byte, only if the resulting packet length is a value between 0x01..0x7e.
  • +
  • Payload: the MTProto payload
  • +
+

If the packet length divided by four is bigger than or equal to 127 (>= 0x7f), the following envelope must be used, instead:

+
    +
  • Header: A single byte of value 0x7f
  • +
  • Length: payload length, divided by four, and encoded as 3 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
+

Intermediate

+

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used.

+
    +
  • Overhead: small
  • +
  • Minimum envelope length: 4 bytes
  • +
  • Maximum envelope length: 4 bytes
  • +
+

Payload structure:

+
+----+----...----+
++len.+  payload  +
++----+----...----+
+

Before sending anything into the underlying socket (see transports), the client must first send 0xeeeeeeee as the first int (four bytes, the server will not send 0xeeeeeeee as the first int in the first reply).
+Then, payloads are wrapped in the following envelope:

+
    +
  • Length: payload length encoded as 4 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
+

Padded intermediate

+

Padded version of the intermediate protocol, to use with obfuscation enabled to bypass ISP blocks.

+
    +
  • Overhead: small-medium
  • +
  • Minimum envelope length: random
  • +
  • Maximum envelope length: random
  • +
+

Before sending anything into the underlying socket (see transports), the client must first send 0xdddddddd as the first int (four bytes, the server will not send 0xdddddddd as the first int in the first reply).
+Then, payloads are wrapped in the following envelope:

+
+----+----...----+----...----+
+|tlen|  payload  |  padding  |
++----+----...----+----...----+
+

Envelope description:

+
    +
  • Total length: payload+padding length encoded as 4 length bytes (little endian)
  • +
  • Payload: the MTProto payload
  • +
  • Padding: A random padding string of length 0-15
  • +
+

Full

+

The basic MTProto transport protocol

+
    +
  • Overhead: medium
  • +
  • Minimum envelope length: 12 bytes (length+seqno+crc)
  • +
  • Maximum envelope length: 12 bytes (length+seqno+crc)
  • +
+

Payload structure:

+
+----+----+----...----+----+
+|len.|seq.|  payload  |crc.|
++----+----+----...----+----+
+

Envelope description:

+
    +
  • Length: length+seqno+payload+crc length encoded as 4 length bytes (little endian, the length of the length field must be included, too)
  • +
  • Seqno: the TCP sequence number for this TCP connection (different from the MTProto sequence number): the first packet sent is numbered 0, the next one 1, etc.
  • +
  • payload: MTProto payload
  • +
  • crc: 4 CRC32 bytes computed using length, sequence number, and payload together.
  • +
+

Transport features

+

Additionally, the following transport features can be used:

+

Quick ack

+

These MTProto transport protocols have support for quick acknowledgment. +In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. +They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

+

Transport errors

+

In the event of a transport error (missing auth key, transport flood, etc.), the server may send a packet with a signed little-endian number of 4 bytes, whose absolute value contains the error code (the error itself is actually negative).

+

For example, error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

+

Error 404 (auth key not found) is returned when the specified auth key ID cannot be found by the DC.

+

Error 429 (transport flood) is returned when too many transport connections are established to the same IP in a too short lapse of time, or if any of the container/service message limits are reached.

+

Error 444 (invalid DC) is returned while creating an auth key, connecting to an MTProxy or in other contexts if an invalid DC ID is specified.

+

Transport obfuscation

+

Transport obfuscation is required to use the websocket transports.

+

Transport obfuscation to prevent ISP blocks is implemented using the following protocol, situated under the MTProto transport in the ISO/OSI stack, see the recap; this means that the payload is first wrapped in the MTProto transport envelope (all transports are supported), and then obfuscated:

+

Prior to establishing the connection (and eventually sending the protocol header of a specific MTProto transport), a 64-byte (512-bit) random initialization payload is generated. +During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).
+In particular, the first four bytes must not be equal to 0xdddddddd (padded intermediate), 0xeeeeeeee (intermediate), POST, GET, HEAD, or any of the HTTP methods that are accepted by the MTProto servers.
+The first byte must also not be equal to 0xef (abridged). +Bytes 4-8 must also not be equal to 0x00000000, since that would indicate use of the full transport with the initial TCP sequence number (0).

+

The protocol identifier, if present, must be inserted in the initialization payload at byte offset 56: if its length is less than 4, it must be padded using the protocol identifier itself, to make its length 4 (0xef => 0xefefefef): the standalone protocol identifier must be not be sent aftwerwards.

+

This protocol is also (but not exclusively) used when connecting to MTProxies: only in this case, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset 60. +The encoding simply consist of the DC ID in two-byte signed little-endian form; 10000 has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we're connecting to is a media (not CDN) DC.

+

Next, a secondary initialization payload is generated by reversing the primary initialization payload.

+

Two keys are extracted from both initialization payloads, using bytes at offsets 8-40: the key extracted from the primary payload is used as encryption key, the key extracted from the secondary payload is used as decryption key.

+

Two IVs are extracted from both initialization payloads, using bytes at offsets 40-56: the IV extracted from the primary payload is used as encryption IV, the IV extracted from the secondary payload is used as decryption IV.

+

Only if using MTProxy, the secret is used to provide connection with the MTProxy server. +The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.

+

Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it's 0xdd, to indicate that the padded intermediate protocol should be used 0xdddddddd; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).

+

The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it's the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.

+

The obtained encryption and decryption key/IV pairs must then be used with AES-256-CTR to encrypt and decrypt all outgoing and incoming payloads.

+

The first thing that must be encrypted using the encryption key is the initialization payload itself. +Then bytes 56-64 of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (only for MTProxies).

+

The final initialization payload must then be sent in the socket as first 64 bytes after the TCP handshake.

+

Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated padded intermediate transport. +Warning: do not use the specified proxy secret in any MTProxy exposed on the internet.

+
protocol := 0xdddddddd
+dc := 0xfcff
+
+while 1:
+    init := (56 random bytes) + protocol + dc + (2 random bytes)
+
+    if init[0] == 0xef:
+      continue
+
+    first_int := substr(init, 0, 4)
+    if first_int == 0x44414548 || first_int == 0x54534f50 || first_int == 0x20544547 || first_int == 0x4954504f || first_int == 0x02010316 || first_int == 0xdddddddd || first_int == 0xeeeeeeee:
+      continue
+
+    second_int := substr(init, 0, 4)
+    if second_int == 0x00000000:
+      continue
+
+    break
+
+initRev := strrev(init)
+
+encryptKey := substr(init, 8, 32)
+encryptIV := substr(init, 40, 16)
+
+decryptKey := substr(initRev, 8, 32)
+decryptIV := substr(initRev, 40, 16)
+
+secret := substr(0xdd99999999999999999999999999999999, 1, 16)
+
+encryptKey = SHA256(encryptKey + secret)
+decryptKey = SHA256(decryptKey + secret)
+
+encryptedInit := CTR(encryptKey, encryptIV, init)
+
+finalInit := substr(init, 0, 56) + substr(encryptedInit, 56, 8)
+
+write(finalInit)
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/samples-auth_key.html b/data/corefork.telegram.org/mtproto/samples-auth_key.html new file mode 100644 index 0000000000..54ce6ab2ee --- /dev/null +++ b/data/corefork.telegram.org/mtproto/samples-auth_key.html @@ -0,0 +1,748 @@ + + + + + samples-auth_key + + + + + + + + + + + + + +
+ +
+
+
+ +

samples-auth_key

+ +

In the examples below, the transport headers are omitted:

+
+

For example, for an abridged version of the transport the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01-0x7e = data length divided by 4; or 0x7f followed by 3 bytes (little endian) divided by 4) followed by the data themselves. In this case, server responses have the same form (although the server does not send 0xefas the first byte).

+
+

Detailed documentation on creating authorization keys is available here ».

+

1. Request for (p,q) Authorization

+
req_pq#60469778 nonce:int128 = ResPQ
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac42770964aExact unixtime * 2^32
message_length16, 420Message body length
%(req_pq)20, 460469778req_pq constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCRandom number
+

The header is 20 bytes long, the message body is 20 bytes long, and the entire message is 40 bytes in length.

+
0000 | 00 00 00 00 00 00 00 00 4A 96 70 27 C4 7A E5 51
+0010 | 14 00 00 00 78 97 46 60 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC
+

2. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 C8 83 1E C9 7A E5 51
+0010 | 40 00 00 00 63 24 16 05 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 08 17 ED 48 94 1A 08 F9
+0040 | 81 00 00 00 15 C4 B5 1C 01 00 00 00 21 6B E8 6C
+0050 | 02 2B B4 C3
+
Response decomposition using the following formula:
+
resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ 
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57AC91E83C801Server message ID
message_length16, 464Message body length
%(resPQ)20, 405162463resPQ constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Server-generated random number
pq56, 1217ED48941A08F981Single-byte prefix denoting length, an 8-byte string, and three bytes of padding
%(Vector long)68, 41cb5c415Vector long constructor number from TL schema
count72, 41Number of elements in key fingerprint list
fingerprints[]76, 8c3b42b026ce86b2164 lower-order bits of SHA1 (server_public_key)
+

The server_public_key public key has been selected whose fingerprint corresponds to the only one received from the server: c3b42b026ce86b21.

+

3. Pq = 17ED48941A08F981 decomposed into 2 prime cofactors:

+
p = 494C553B
+q = 53911073
+

4. encrypted_data Generation

+
p_q_inner_data#83c95aec pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 = P_Q_inner_data
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(p_q_inner_data)0, 483c95aecp_q_inner_data constructor number from TL schema
pq4, 1217ED48941A08F981Single-byte prefix denoting length, 8-byte string, and three bytes of padding
p16, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q24, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
nonce32, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce48, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce64, 32311C85DB234AA2640AFC4A76A735CF5B 1F0FD68BD17FA181E1229AD867CC024DClient-generated random number
+

The serialization of P_Q_inner_data produces some string data. This is followed by encrypted_data:

+
SHA1 (data) = DB761C27718A2305044F71F2AD951629D78B2449
+RSA (data_with_hash, server_public_key) = 7BB0100A523161904D9C69FA04BC60DECFC5DD74B99995C768EB60D8716E2109BAF2D4601DAB6B09610DC11067BB89021E09471FCFA52DBD0F23204AD8CA8B012BF40A112F44695AB6C266955386114EF5211E6372227ADBD34995D3E0E5FF02EC63A43F9926878962F7C570E6A6E78BF8366AF917A5272675C46064BE62E3E202EFA8B1ADFB1C32A898C2987BE27B5F31D57C9BB963ABCB734B16F652CEDB4293CBB7C878A3A3FFAC9DBEA9DF7C67BC9E9508E111C78FC46E057F5C65ADE381D91FEE430A6B576A99BDF8551FDB1BE2B57069B1A45730618F27427E8A04720B4971EF4A9215983D68F2830C3EAA6E40385562F970D38A05C9F1246DC33438E6
+

The length of the final string was 256 bytes.

+
Request to Start Diffie-Hellman Key Exchange
+
req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac917717a27Exact unixtime * 2^32
message_length16, 4320Message body length
%(req_DH_params)20, 4d712e4bereq_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
p56, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q64, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
public_key_fingerprint72, 8c3b42b026ce86b21Fingerprint of public key used
encrypted_data80, 260See aboveSee “Generation of encrypted_data"
+
0000 | 00 00 00 00 00 00 00 00 27 7A 71 17 C9 7A E5 51
+0010 | 40 01 00 00 BE E4 12 D7 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 04 49 4C 55 3B 00 00 00
+0040 | 04 53 91 10 73 00 00 00 21 6B E8 6C 02 2B B4 C3
+0050 | FE 00 01 00 7B B0 10 0A 52 31 61 90 4D 9C 69 FA
+0060 | 04 BC 60 DE CF C5 DD 74 B9 99 95 C7 68 EB 60 D8
+0070 | 71 6E 21 09 BA F2 D4 60 1D AB 6B 09 61 0D C1 10
+0080 | 67 BB 89 02 1E 09 47 1F CF A5 2D BD 0F 23 20 4A
+0090 | D8 CA 8B 01 2B F4 0A 11 2F 44 69 5A B6 C2 66 95
+00A0 | 53 86 11 4E F5 21 1E 63 72 22 7A DB D3 49 95 D3
+00B0 | E0 E5 FF 02 EC 63 A4 3F 99 26 87 89 62 F7 C5 70
+00C0 | E6 A6 E7 8B F8 36 6A F9 17 A5 27 26 75 C4 60 64
+00D0 | BE 62 E3 E2 02 EF A8 B1 AD FB 1C 32 A8 98 C2 98
+00E0 | 7B E2 7B 5F 31 D5 7C 9B B9 63 AB CB 73 4B 16 F6
+00F0 | 52 CE DB 42 93 CB B7 C8 78 A3 A3 FF AC 9D BE A9
+0100 | DF 7C 67 BC 9E 95 08 E1 11 C7 8F C4 6E 05 7F 5C
+0110 | 65 AD E3 81 D9 1F EE 43 0A 6B 57 6A 99 BD F8 55
+0120 | 1F DB 1B E2 B5 70 69 B1 A4 57 30 61 8F 27 42 7E
+0130 | 8A 04 72 0B 49 71 EF 4A 92 15 98 3D 68 F2 83 0C
+0140 | 3E AA 6E 40 38 55 62 F9 70 D3 8A 05 C9 F1 24 6D
+0150 | C3 34 38 E6
+

5. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 54 43 36 CB 7A E5 51
+0010 | 78 02 00 00 5C 07 E8 D0 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 FE 50 02 00 28 A9 2F E2
+0040 | 01 73 B3 47 A8 BB 32 4B 5F AB 26 67 C9 A8 BB CE
+0050 | 64 68 D5 B5 09 A4 CB DD C1 86 24 0A C9 12 CF 70
+0060 | 06 AF 89 26 DE 60 6A 2E 74 C0 49 3C AA 57 74 1E
+0070 | 6C 82 45 1F 54 D3 E0 68 F5 CC C4 9B 44 44 12 4B
+0080 | 96 66 FF B4 05 AA B5 64 A3 D0 1E 67 F6 E9 12 86
+0090 | 7C 8D 20 D9 88 27 07 DC 33 0B 17 B4 E0 DD 57 CB
+00A0 | 53 BF AA FA 9E F5 BE 76 AE 6C 1B 9B 6C 51 E2 D6
+00B0 | 50 2A 47 C8 83 09 5C 46 C8 1E 3B E2 5F 62 42 7B
+00C0 | 58 54 88 BB 3B F2 39 21 3B F4 8E B8 FE 34 C9 A0
+00D0 | 26 CC 84 13 93 40 43 97 4D B0 35 56 63 30 38 39
+00E0 | 2C EC B5 1F 94 82 4E 14 0B 98 63 77 30 A4 BE 79
+00F0 | A8 F9 DA FA 39 BA E8 1E 10 95 84 9E A4 C8 34 67
+0100 | C9 2A 3A 17 D9 97 81 7C 8A 7A C6 1C 3F F4 14 DA
+0110 | 37 B7 D6 6E 94 9C 0A EC 85 8F 04 82 24 21 0F CC
+0120 | 61 F1 1C 3A 91 0B 43 1C CB D1 04 CC CC 8D C6 D2
+0130 | 9D 4A 5D 13 3B E6 39 A4 C3 2B BF F1 53 E6 3A CA
+0140 | 3A C5 2F 2E 47 09 B8 AE 01 84 4B 14 2C 1E E8 9D
+0150 | 07 5D 64 F6 9A 39 9F EB 04 E6 56 FE 36 75 A6 F8
+0160 | F4 12 07 8F 3D 0B 58 DA 15 31 1C 1A 9F 8E 53 B3
+0170 | CD 6B B5 57 2C 29 49 04 B7 26 D0 BE 33 7E 2E 21
+0180 | 97 7D A2 6D D6 E3 32 70 25 1C 2C A2 9D FC C7 02
+0190 | 27 F0 75 5F 84 CF DA 9A C4 B8 DD 5F 84 F1 D1 EB
+01A0 | 36 BA 45 CD DC 70 44 4D 8C 21 3E 4B D8 F6 3B 8A
+01B0 | B9 5A 2D 0B 41 80 DC 91 28 3D C0 63 AC FB 92 D6
+01C0 | A4 E4 07 CD E7 C8 C6 96 89 F7 7A 00 74 41 D4 A6
+01D0 | A8 38 4B 66 65 02 D9 B7 7F C6 8B 5B 43 CC 60 7E
+01E0 | 60 A1 46 22 3E 11 0F CB 43 BC 3C 94 2E F9 81 93
+01F0 | 0C DC 4A 1D 31 0C 0B 64 D5 E5 5D 30 8D 86 32 51
+0200 | AB 90 50 2C 3E 46 CC 59 9E 88 6A 92 7C DA 96 3B
+0210 | 9E B1 6C E6 26 03 B6 85 29 EE 98 F9 F5 20 64 19
+0220 | E0 3F B4 58 EC 4B D9 45 4A A8 F6 BA 77 75 73 CC
+0230 | 54 B3 28 89 5B 1D F2 5E AD 9F B4 CD 51 98 EE 02
+0240 | 2B 2B 81 F3 88 D2 81 D5 E5 BC 58 01 07 CA 01 A5
+0250 | 06 65 C3 2B 55 27 15 F3 35 FD 76 26 4F AD 00 DD
+0260 | D5 AE 45 B9 48 32 AC 79 CE 7C 51 1D 19 4B C4 2B
+0270 | 70 EF A8 50 BB 15 C2 01 2C 52 15 CA BF E9 7C E6
+0280 | 6B 8D 87 34 D0 EE 75 9A 63 8A F0 13
+
Response decomposition using the following formula:
+
server_DH_params_fail#79cb045d nonce:int128 server_nonce:int128 new_nonce_hash:int128 = Server_DH_Params;
+server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57ACB36435401Exact unixtime * 2^32
message_length16, 4632Message body length
%(server_DH_params_ok)20, 4d0e8075cserver_DH_params_ok constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_answer56, 596See belowSee “Decomposition of encrypted_answer"
+
Conversion of encrypted_answer into answer:
+
encrypted_answer = 28A92FE20173B347A8BB324B5FAB2667C9A8BBCE6468D5B509A4CBDDC186240AC912CF7006AF8926DE606A2E74C0493CAA57741E6C82451F54D3E068F5CCC49B4444124B9666FFB405AAB564A3D01E67F6E912867C8D20D9882707DC330B17B4E0DD57CB53BFAAFA9EF5BE76AE6C1B9B6C51E2D6502A47C883095C46C81E3BE25F62427B585488BB3BF239213BF48EB8FE34C9A026CC8413934043974DB03556633038392CECB51F94824E140B98637730A4BE79A8F9DAFA39BAE81E1095849EA4C83467C92A3A17D997817C8A7AC61C3FF414DA37B7D66E949C0AEC858F048224210FCC61F11C3A910B431CCBD104CCCC8DC6D29D4A5D133BE639A4C32BBFF153E63ACA3AC52F2E4709B8AE01844B142C1EE89D075D64F69A399FEB04E656FE3675A6F8F412078F3D0B58DA15311C1A9F8E53B3CD6BB5572C294904B726D0BE337E2E21977DA26DD6E33270251C2CA29DFCC70227F0755F84CFDA9AC4B8DD5F84F1D1EB36BA45CDDC70444D8C213E4BD8F63B8AB95A2D0B4180DC91283DC063ACFB92D6A4E407CDE7C8C69689F77A007441D4A6A8384B666502D9B77FC68B5B43CC607E60A146223E110FCB43BC3C942EF981930CDC4A1D310C0B64D5E55D308D863251AB90502C3E46CC599E886A927CDA963B9EB16CE62603B68529EE98F9F5206419E03FB458EC4BD9454AA8F6BA777573CC54B328895B1DF25EAD9FB4CD5198EE022B2B81F388D281D5E5BC580107CA01A50665C32B552715F335FD76264FAD00DDD5AE45B94832AC79CE7C511D194BC42B70EFA850BB15C2012C5215CABFE97CE66B8D8734D0EE759A638AF013
+tmp_aes_key = F011280887C7BB01DF0FC4E17830E0B91FBB8BE4B2267CB985AE25F33B527253
+tmp_aes_iv = 3212D579EE35452ED23E0D0C92841AA7D31B2E9BDEF2151E80D15860311C85DB
+answer = BA0D89B53E0549828CCA27E966B301A48FECE2FCA5CF4D33F4A11EA877BA4AA57390733002000000FE000100C71CAEB9C6B1C9048E6C522F70F13F73980D40238E3E21C14934D037563D930F48198A0AA7C14058229493D22530F4DBFA336F6E0AC925139543AED44CCE7C3720FD51F69458705AC68CD4FE6B6B13ABDC9746512969328454F18FAF8C595F642477FE96BB2A941D5BCD1D4AC8CC49880708FA9B378E3C4F3A9060BEE67CF9A4A4A695811051907E162753B56B0F6B410DBA74D8A84B2A14B3144E0EF1284754FD17ED950D5965B4B9DD46582DB1178D169C6BC465B0D6FF9CA3928FEF5B9AE4E418FC15E83EBEA0F87FA9FF5EED70050DED2849F47BF959D956850CE929851F0D8115F635B105EE2E4E15D04B2454BF6F4FADF034B10403119CD8E3B92FCC5BFE000100262AABA621CC4DF587DC94CF8252258C0B9337DFB47545A49CDD5C9B8EAE7236C6CADC40B24E88590F1CC2CC762EBF1CF11DCC0B393CAAD6CEE4EE5848001C73ACBB1D127E4CB93072AA3D1C8151B6FB6AA6124B7CD782EAF981BDCFCE9D7A00E423BD9D194E8AF78EF6501F415522E44522281C79D906DDB79C72E9C63D83FB2A940FF779DFB5F2FD786FB4AD71C9F08CF48758E534E9815F634F1E3A80A5E1C2AF210C5AB762755AD4B2126DFA61A77FA9DA967D65DFD0AFB5CDF26C4D4E1A88B180F4E0D0B45BA1484F95CB2712B50BF3F5968D9D55C99C0FB9FB67BFF56D7D4481B634514FBA3488C4CDA2FC0659990E8E868B28632875A9AA703BCDCE8FCB7AE551
+
Server_DH_inner_data decomposition using the following formula:
+
server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(server_DH_inner_data)0, 4b5890dbaserver_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
g36, 42Value received from server in Step 2
dh_prime40, 260C71CAEB9C6B1C9048E6C522F70F13F73 980D40238E3E21C14934D037563D930F 48198A0AA7C14058229493D22530F4DB FA336F6E0AC925139543AED44CCE7C37 20FD51F69458705AC68CD4FE6B6B13AB DC9746512969328454F18FAF8C595F64 2477FE96BB2A941D5BCD1D4AC8CC4988 0708FA9B378E3C4F3A9060BEE67CF9A4 A4A695811051907E162753B56B0F6B41 0DBA74D8A84B2A14B3144E0EF1284754 FD17ED950D5965B4B9DD46582DB1178D 169C6BC465B0D6FF9CA3928FEF5B9AE4 E418FC15E83EBEA0F87FA9FF5EED7005 0DED2849F47BF959D956850CE929851F 0D8115F635B105EE2E4E15D04B2454BF 6F4FADF034B10403119CD8E3B92FCC5B
g_a300, 260262AABA621CC4DF587DC94CF8252258C 0B9337DFB47545A49CDD5C9B8EAE7236 C6CADC40B24E88590F1CC2CC762EBF1C F11DCC0B393CAAD6CEE4EE5848001C73 ACBB1D127E4CB93072AA3D1C8151B6FB 6AA6124B7CD782EAF981BDCFCE9D7A00 E423BD9D194E8AF78EF6501F415522E4 4522281C79D906DDB79C72E9C63D83FB 2A940FF779DFB5F2FD786FB4AD71C9F0 8CF48758E534E9815F634F1E3A80A5E1 C2AF210C5AB762755AD4B2126DFA61A7 7FA9DA967D65DFD0AFB5CDF26C4D4E1A 88B180F4E0D0B45BA1484F95CB2712B5 0BF3F5968D9D55C99C0FB9FB67BFF56D 7D4481B634514FBA3488C4CDA2FC0659 990E8E868B28632875A9AA703BCDCE8F
server_time560, 41373993675Server time
+

6. Random number b is computed:

+
b = 6F620AFA575C9233EB4C014110A7BCAF49464F798A18A0981FEA1E05E8DA67D9681E0FD6DF0EDF0272AE3492451A84502F2EFC0DA18741A5FB80BD82296919A70FAA6D07CBBBCA2037EA7D3E327B61D585ED3373EE0553A91CBD29B01FA9A89D479CA53D57BDE3A76FBD922A923A0A38B922C1D0701F53FF52D7EA9217080163A64901E766EB6A0F20BC391B64B9D1DD2CD13A7D0C946A3A7DF8CEC9E2236446F646C42CFE2B60A2A8D776E56C8D7519B08B88ED0970E10D12A8C9E355D765F2B7BBB7B4CA9360083435523CB0D57D2B106FD14F94B4EEE79D8AC131CA56AD389C84FE279716F8124A543337FB9EA3D988EC5FA63D90A4BA3970E7A39E5C0DE5
+
Generation of encrypted_data
+
client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(client_DH_inner_data)0, 46643b654client_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
retry_id36, 80First attempt
g_b44, 26073700E7BFC7AEEC828EB8E0DCC04D09A 0DD56A1B4B35F72F0B55FCE7DB7EBB72 D7C33C5D4AA59E1C74D09B01AE536B31 8CFED436AFDB15FE9EB4C70D7F0CB14E 46DBBDE9053A64304361EB358A9BB32E 9D5C2843FE87248B89C3F066A7D5876D 61657ACC52B0D81CD683B2A0FA93E8AD AB20377877F3BC3369BBF57B10F5B589 E65A9C27490F30A0C70FFCFD3453F5B3 79C1B9727A573CFFDCA8D23C721B135B 92E529B1CDD2F7ABD4F34DAC4BE1EEAF 60993DDE8ED45890E4F47C26F2C0B2E0 37BB502739C8824F2A99E2B1E7E41658 3417CC79A8807A4BDAC6A5E9805D4F61 86C37D66F6988C9F9C752896F3D34D25 529263FAF2670A09B2A59CE35264511Fg^b mod dh_prime
+

The serialization of Client_DH_Inner_Data produces some string data. This is followed by encrypted_data:

+
data_with_hash := SHA1(data) + data + (0-15 random bytes); such that the length be divisible by 16;
+AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv) = 928A4957D0463B525C1CC48AABAA030A256BE5C746792C84CA4C5A0DF60AC799048D98A38A8480EDCF082214DFC79DCB9EE34E206513E2B3BC1504CFE6C9ADA46BF9A03CA74F192EAF8C278454ADABC795A566615462D31817382984039505F71CB33A41E2527A4B1AC05107872FED8E3ABCEE1518AE965B0ED3AED7F67479155BDA8E4C286B64CDF123EC748CF289B1DB02D1907B562DF462D8582BA6F0A3022DC2D3504D69D1BA48B677E3A830BFAFD67584C8AA24E1344A8904E305F9587C92EF964F0083F50F61EAB4A393EAA33C9270294AEDC7732891D4EA1599F52311D74469D2112F4EDF3F342E93C8E87E812DC3989BAECFE6740A46077524C75093F5A5405736DE8937BB6E42C9A0DCF22CA53227D462BCCC2CFE94B6FE86AB7FBFA395021F66661AF7C0024CA2986CA03F3476905407D1EA9C010B763258DB1AA2CC7826D91334EFC1FDC665B67FE45ED0
+

The length of the final string was 336 bytes.

+
Request
+
set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57acd2aa32c6dExact unixtime * 2^32
message_length16, 4376Message body length
%(set_client_DH_params)20, 4f5045f1fset_client_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_data56, 340See aboveSee “Generation of encrypted_data"
+
0000 | 00 00 00 00 00 00 00 00 6D 2C A3 2A CD 7A E5 51
+0010 | 78 01 00 00 1F 5F 04 F5 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 FE 50 01 00 92 8A 49 57
+0040 | D0 46 3B 52 5C 1C C4 8A AB AA 03 0A 25 6B E5 C7
+0050 | 46 79 2C 84 CA 4C 5A 0D F6 0A C7 99 04 8D 98 A3
+0060 | 8A 84 80 ED CF 08 22 14 DF C7 9D CB 9E E3 4E 20
+0070 | 65 13 E2 B3 BC 15 04 CF E6 C9 AD A4 6B F9 A0 3C
+0080 | A7 4F 19 2E AF 8C 27 84 54 AD AB C7 95 A5 66 61
+0090 | 54 62 D3 18 17 38 29 84 03 95 05 F7 1C B3 3A 41
+00A0 | E2 52 7A 4B 1A C0 51 07 87 2F ED 8E 3A BC EE 15
+00B0 | 18 AE 96 5B 0E D3 AE D7 F6 74 79 15 5B DA 8E 4C
+00C0 | 28 6B 64 CD F1 23 EC 74 8C F2 89 B1 DB 02 D1 90
+00D0 | 7B 56 2D F4 62 D8 58 2B A6 F0 A3 02 2D C2 D3 50
+00E0 | 4D 69 D1 BA 48 B6 77 E3 A8 30 BF AF D6 75 84 C8
+00F0 | AA 24 E1 34 4A 89 04 E3 05 F9 58 7C 92 EF 96 4F
+0100 | 00 83 F5 0F 61 EA B4 A3 93 EA A3 3C 92 70 29 4A
+0110 | ED C7 73 28 91 D4 EA 15 99 F5 23 11 D7 44 69 D2
+0120 | 11 2F 4E DF 3F 34 2E 93 C8 E8 7E 81 2D C3 98 9B
+0130 | AE CF E6 74 0A 46 07 75 24 C7 50 93 F5 A5 40 57
+0140 | 36 DE 89 37 BB 6E 42 C9 A0 DC F2 2C A5 32 27 D4
+0150 | 62 BC CC 2C FE 94 B6 FE 86 AB 7F BF A3 95 02 1F
+0160 | 66 66 1A F7 C0 02 4C A2 98 6C A0 3F 34 76 90 54
+0170 | 07 D1 EA 9C 01 0B 76 32 58 DB 1A A2 CC 78 26 D9
+0180 | 13 34 EF C1 FD C6 65 B6 7F E4 5E D0
+

7. Computing auth_key using formula g^{ab} mod dh_prime:

+
auth_key = AB96E207C631300986F30EF97DF55E179E63C112675F0CE502EE76D74BBEE6CBD1E95772818881E9F2FF54BD52C258787474F6A7BEA61EABE49D1D01D55F64FC07BC31685716EC8FB46FEACF9502E42CFD6B9F45A08E90AA5C2B5933AC767CBE1CD50D8E64F89727CA4A1A5D32C0DB80A9FCDBDDD4F8D5A1E774198F1A4299F927C484FEEC395F29647E43C3243986F93609E23538C21871DF50E00070B3B6A8FA9BC15628E8B43FF977409A61CEEC5A21CF7DFB5A4CC28F5257BC30CD8F2FB92FBF21E28924065F50E0BBD5E11A420300E2C136B80E9826C6C5609B5371B7850AA628323B6422F3A94F6DFDE4C3DC1EA60F7E11EE63122B3F39CBD1A8430157
+

8. The server verifies that auth_key_hash is unique.

+

The key is unique.

+

9. A response from the server has been received with the following content:

+
0000 | 00 00 00 00 00 00 00 00 01 30 AA C5 CE 7A E5 51
+0010 | 34 00 00 00 34 F7 CB 3B 3E 05 49 82 8C CA 27 E9
+0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
+0030 | 77 BA 4A A5 73 90 73 30 CC EB C0 21 72 66 E1 ED
+0040 | EC 7F B0 A0 EE D6 C2 20
+

Set_client_DH_params_answer decomposition using the following formula:

+
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
+dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
+dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterOffset, Length in bytesValueDescription
%(dh_gen_ok)0, 43bcbf734dh_gen_ok constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce_hash136, 16CCEBC0217266E1EDEC7FB0A0EED6C220
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/mtproto/security_guidelines.html b/data/corefork.telegram.org/mtproto/security_guidelines.html new file mode 100644 index 0000000000..a4627d6170 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/security_guidelines.html @@ -0,0 +1,177 @@ + + + + + Security Guidelines for Client Developers + + + + + + + + + + + + + +
+ +
+
+
+ +

Security Guidelines for Client Developers

+ +
+ +

See also:

+

+ +

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply.

+
+

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. +MTProto v.1.0 is deprecated and is currently being phased out.

+
+

Diffie-Hellman key exchange

+

We use DH key exchange in two cases:

+ +

In both cases, there are some verifications to be done whenever DH is used:

+

Validation of DH parameters

+

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

+

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

+

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

+
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
+

g_a and g_b validation

+

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

+

Checking SHA1 hash values during key generation

+

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

+
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
+

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

+

Checking nonce, server_nonce and new_nonce fields

+

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

+

Using secure pseudorandom number generator to create DH secret parameters a and b

+

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

+

MTProto Encrypted Messages

+

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

+

Checking SHA256 hash value of msg_key

+

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA256 of the plaintext obtained as the result of decryption (including the final 12...1024 padding bytes), prepended with 32 bytes taken from the auth_key, as explained in MTProto 2.0 Description.

+

If an error is encountered before this check could be performed, the client must perform the msg_key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

+

Checking message length

+

The client must check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference (i.e. the length of the random padding) lies in the range from 12 to 1024 bytes.

+

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

+

Checking session_id

+

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

+

Checking msg_id

+

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

+

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

+

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

+

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

+

Behavior in case of mismatch

+

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

+

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

+

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

+
+

The previous version of security recommendations relevant for MTProto 1.0 clients is available here.

+
+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/mtproto/serialize.html b/data/corefork.telegram.org/mtproto/serialize.html new file mode 100644 index 0000000000..e2028a2386 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/serialize.html @@ -0,0 +1,240 @@ + + + + + Binary Data Serialization + + + + + + + + + + + + + +
+ +
+
+
+ +

Binary Data Serialization

+ +

MTProto operation requires that elementary and composite data types as well as queries to which such data types are passed as arguments or by which they are returned, be transmitted in binary format (i. e. serialized) . +The TL language is used to describe the data types to be serialized.

+

General Definitions

+

For our purposes, we can identify a type with the set of its (serialized) values understood as strings (finite sequences) of 32-bit numbers (transmitted in little endian order).

+

Therefore:

+
    +
  • Alphabet (A), in this case, is a set of 32-bit numbers (normally, signed, i. e. between -2^31 and 2^31 - 1).
  • +
  • Value, in this case, is the same as a string in Alphabet A, i. e. a finite (possibly, empty) sequence of 32-bit numbers. The set of all such sequences is designated as A*.
  • +
  • Type, for our purposes, is the same as the set of legal values of a type, i. e. some set T which is a subset of A* and is a prefix code (i. e. no element of T may be a prefix for any other element). Therefore, any sequence from A* can contain no more than one prefix that is a member of T.
  • +
  • Value of Type T is any sequence (value) which is a member of T as a subset of A*.
  • +
  • Compatible Types are the types T and T’ not intersecting as subsets of A*, such that the union of T and T' is a prefix code.
  • +
  • Coordinated System of Types is a finite or infinite set of types T_1, ..., T_n, ..., such that any two types from this set are compatible.
  • +
  • Data Type is the same as type in the sense of the definition above.
  • +
  • Functional Type is a type describing a function; it is not a type in the sense of the definition above. Initially, we ignore the existence of functional types and describe only the data types; however, in reality, functional types will later be implemented in some extension of this system using the so-called temporary combinators.
  • +
+

Combinators, Constructors, Composite Data Types

+
    +
  • +

    Combinator is a function that takes arguments of certain types and returns a value of some other type. We normally look at combinators whose argument and result types are data types (rather than functional types).

    +
  • +
  • +

    Arity (of combinator) is a non-negative integer, the number of combinator arguments.

    +
  • +
  • +

    Combinator identifier is an identifier beginning with a lowercase Roman letter that uniquely identifies a combinator.

    +
  • +
  • +

    Combinator number or combinator name is a 32-bit number (i.e., an element of A) that uniquely identifies a combinator. Most often, it is CRC32 of the string containing the combinator description without the final semicolon, and with one space between contiguous lexemes. This always falls in the range from 0x01000000 to 0xffffff00. The highest 256 values are reserved for the so-called temporal-logic combinators used to transmit functions. We frequently denote as combinator the combinator name with single quotes: ‘combinator’.

    +
  • +
  • +

    Combinator description is a string of format combinator_name type_arg_1 ... type_arg_N = type_res; where N stands for the arity of the combinator, type_arg_i is the type of the i-th argument (or rather, a string with the combinator name), and type_res is the combinator value type.

    +
  • +
  • +

    Constructor is a combinator that cannot be computed (reduced). This is used to represent composite data types. For example, combinator ‘int_tree’ with description int_tree IntTree int IntTree = IntTree, alongside combinator empty_tree = IntTree, may be used to define a composite data type called “IntTree” that takes on values in the form of binary trees with integers as nodes.

    +
  • +
  • +

    Function (functional combinator) is a combinator which may be computed (reduced) on condition that the requisite number of arguments of requisite types are provided. The result of the computation is an expression consisting of constructors and base type values only.

    +
  • +
  • +

    Normal form is an expression consisting only of constructors and base type values; that which is normally the result of computing a function.

    +
  • +
  • +

    Type identifier is an identifier that normally starts with a capital letter in Roman script and uniquely identifies the type.

    +
  • +
  • +

    Type number or type name is a 32-bit number that uniquely identifies a type; it normally is the sum of the CRC32 values of the descriptions of the type constructors.

    +
  • +
  • +

    Description of (composite) Type T is a collection of the descriptions of all constructors that take on Type T values. This is normally written as text with each string containing the description of a single constructor. Here is a description of Type ‘IntTree’, for example:

    +

    int_tree IntTree int IntTree = IntTree; +empty_tree = IntTree;

    +
  • +
  • +

    Polymorphic type is a type whose description contains parameters (type variables) in lieu of actual types; approximately, what would be a template in C++. Here is a description of Type List alpha where List is a polymorphic type of arity 1 (i. e., dependent on a single argument), and alpha is a type variable which appears as the constructor’s optional parameter (in curly braces):

    +

    cons {alpha:Type} alpha (List alpha) = List alpha; +nil {alpha:Type} = List alpha;

    +
  • +
  • +

    Value of (composite) Type T is any sequence from A* in the format constr_num arg1 ... argN, where constr_num is the index number of some Constructor C which takes on values of Type T, and arg_i is a value of Type T_i which is the type of the i-th argument to Constructor C. For example, let Combinator int_tree have the index number 17, whereas Combinator empty_tree has the index number 239. Then, the value of Type IntTree is, for example, 17 17 239 1 239 2 239 which is more conveniently written as 'int_tree' 'int_tree' 'empty_tree' 1 'empty_tree' 2 ‘empty_tree’. From the standpoint of a high-level language, this is int_tree (int_tree (empty_tree) 1 (empty_tree)) 2 (empty_tree): IntTree.

    +
  • +
  • +

    Schema is a collection of all the (composite) data type descriptions. This is used to define some agreed-to system of types.

    +
  • +
+

Boxed and Bare Types

+
    +
  • Boxed type is a type any value of which starts with the constructor number. Since every constructor has a uniquely determined value type, the first number in any boxed type value uniquely defines its type. This guarantees that the various boxed types in totality make up a coordinated system of types. A boxed type identifier is always capitalized.
  • +
  • Bare type is a type whose values do not contain a constructor number, which is implied instead. A bare type identifier always coincides with the name of the implied constructor (and therefore, begins with a lowercase letter) which may be padded at the front by the percentage sign (%). In addition, if X is a boxed type with no more than a single constructor, then %X refers to the corresponding bare type. The values of a bare type are identical with the set of number sequences obtained by dropping the first number (i. e., the external constructor index number) from the set of values of the corresponding boxed type (which is the result type of the selected constructor), starting with the selected constructor index number. For example, 3 4 is a value of the int_couple bare type, defined using int_couple int int = IntCouple. The corresponding boxed type is IntCouple; if 404 is the constructor index number for int_couple, then 404 3 4 is the value for the IntCouple boxed type which corresponds to the value of the bare type int_couple (also known as %int_couple and %IntCouple; the latter form is conceptually preferable but longer).
  • +
+

Conceptually, only boxed types should be used everywhere. However, for speed and compactness, bare types have to be used (for instance, an array of 10,000 bare int values is 40,000 bytes long, whereas boxed Int values take up twice as much space; therefore, when transmitting a large array of integer identifiers, say, it is more efficient to use the Vector int type rather than Vector Int). In addition, all base types (int, long, double, string) are bare.

+

If a boxed type is polymorphic of type arity r, this is also true of any derived bare type. In other words, if one were to define intCouple {alpha:Type} int alpha = IntCouple alpha, then, thereafter, intCouple as an identifier would also be a polymorphic type of arity 1 in combinator (and consequently, in constructor and type) descriptions. The notations intCouple X, %(IntCouple X), and %IntCouple X are equivalent.

+

Base Types

+

Base types exist both as bare (int, long, double, string) and as boxed (Int, Long, Double, String) versions. Their constructor identifiers coincide with the names of the relevant bare types. Their pseudodescriptions have the following appearance:

+
int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+

Consequently, the int constructor index number, for example, is the CRC32 of the string "int ? = Int".

+

The values of bare type int are exactly all the single-element sequences, i. e. numbers between -2^31 and 2^31-1 represent themselves in this case. Values of type long are two-element sequences that are 64-bit signed numbers (little endian again). Values of type double, again, are two-element sequences containing 64-bit real numbers in a standard double format. And finally, the values of type string look differently depending on the length L of the string being serialized:

+
    +
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit numbers.
  • +
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • +
+

Object Pseudotype

+

The Object pseudotype is a “type” which can take on values that belong to any boxed type in the schema. This helps quickly define such types as list of random items without using polymorphic types. It is best not to abuse this capability since it results in the use of dynamic typing. Nonetheless, it is hard to imagine the data structures that we know from PHP and JSON without using the Object pseudotype.

+

It is recommended to use TypedObject instead whenever possible:

+
object X:Type value:X = TypedObject;
+

Built-In Composite Types: Vectors and Associative Arrays

+

The Vector t polymorphic pseudotype is a “type” whose value is a sequence of values of any type t, either boxed or bare.

+
vector {t:Type} # [ t ] = Vector t;
+

Serialization always uses the same constructor “vector” (const 0x1cb5c415 = crc32("vector t:Type # [ t ] = Vector t”) that is not dependent on the specific value of the variable of type t. The value of the Vector t type is the index number of the relevant constructor number followed by N, the number of elements in the vector, and then by N values of type t. The value of the optional parameter t is not involved in the serialization since it is derived from the result type (always known prior to deserialization).

+

Polymorphic pseudotypes IntHash t and StrHash t are associative arrays mapping integer and string keys to values of type t. They are, in fact, vectors containing bare 2-tuples (int, t) or (string, t):

+
coupleInt {t:Type} int t = CoupleInt t;
+intHash {t:Type} (vector %(CoupleInt t)) = IntHash t;
+coupleStr {t:Type} string t = CoupleStr t;
+strHash {t:Type} (vector %(CoupleStr t)) = StrHash t;
+

The percentage sign, in this case, means that a bare type that corresponds to the boxed type in parentheses is taken; the boxed type in question must have no more than a single constructor, whatever the values of the parameters.

+

The keys may be sorted or be in some other order (as in PHP arrays). For associative arrays with sorted keys, the IntSortedHash or StrSortedHash alias is used:

+
intSortedHash {t:Type} (intHash t) = IntSortedHash t;
+strSortedHash {t:Type} (strHash t) = StrSortedHash t;
+

Polymorphic Type Constructors

+

The constructor of a polymorphic type does not depend on the specific types to which the polymorphic type is applied. When it is computed, optional parameters (normally containing type variables and placed in curly braces) cease to be optional (the curly braces are removed), and, in addition to that, all parenthesis are also removed. Therefore,

+
vector {t:Type} # [ t ] = Vector t;
+

corresponds to the constructor number crc32("vector t:Type # [ t ] = Vector t") = 0x1cb5c415. During (de)serialization, the specific values of the optional variable t are derived from the result type (i. e. the object being serialized or deserialized) that is always known, and are never serialized explicitly.

+

Previously, it had to be known which specific variable types each polymorphic type will apply to. To accomplish this, the type system used strings of the form

+
polymorphic_type_name type_1 ... type_N;
+

For example,

+
Vector int;
+Vector string;
+Vector Object;
+

Now they are ignored.

+

See also polymorphism in TL.

+

In this case, the Object pseudotype permits using Vector Object to store lists of anything (the values of any boxed types). Since bare types are efficient when short, in practice it is unlikely that cases more complex than the ones cited above will be required.

+

Field Names

+

Let us say that we need to represent users as triplets containing one integer (user ID) and two strings (first and last names). The requisite data structure is the triplet int, string, string which may be declared as follows:

+
user int string string = User;
+

On the other hand, a group may be described by a similar triplet consisting of a group ID, its name, and description:

+
group int string string = Group;
+

For the difference between User and Group to be clear, it is convenient to assign names to some or all of the fields:

+
user id:int first_name:string last_name:string = User;
+group id:int title:string description:string = Group;
+

If the User type needs to be extended at a later time by having records with some additional field added to it, it could be accomplished as follows:

+
userv2 id:int unread_messages:int first_name:string last_name:string in_groups:vector int = User;
+

Aside from other things, this approach helps define correct mappings between fields that belong to different constructors of the same type, convert between them as well as convert type values into an associative array with string keys (field names, if defined, are natural choices for such keys).

+

TL Language

+

See TL Language

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/passport/encryption.html b/data/corefork.telegram.org/passport/encryption.html new file mode 100644 index 0000000000..8aed498b38 --- /dev/null +++ b/data/corefork.telegram.org/passport/encryption.html @@ -0,0 +1,606 @@ + + + + + Telegram Passport Encryption Details + + + + + + + + + + + + + +
+ +
+
+
+ +

Telegram Passport Encryption Details

+ +
+ +

Telegram Passport data is stored encrypted End-to-End which means that the Telegram server does not have access to the data and only functions as a storage for encrypted data it can't decipher. Encryption and decryption are handled exclusively by the Telegram clients, which are open source.

+

Overview

+

To encrypt each particular element of Telegram Passport, the client generates a random secret. The secret is a 32-byte number with the modulo 255 sum of bytes equal to 239. This secret is in turn encrypted with the passport_secret that is generated when the user creates their Telegram Passport. passport_secret is encrypted with the user's password and is stored encrypted in the Telegram Cloud.

+

Passport Secret

+

The passport secret is one of the secret parameters used to encrypt the data uploaded by the user to the Telegram Cloud.

+

When first setting up Telegram Passport it must be created, encrypted and uploaded as described in Passport Secret Encryption.

+

When using Telegram Passport normally, it must be downloaded and decrypted for use as described in Passport Secret Decryption.

+

The passport secret must also be downloaded, re-encrypted and re-uploaded as described in Passport Secret Encryption if a new, more secure encryption algorithm is defined in a newer version of Telegram or the 2FA password is updated.

+

Passport Secret Encryption

+

First of all, server-side passport parameters are fetched, schema:

+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+
+---functions---
+
+account.getPassword#548a30f5 = account.Password;
+

When Telegram Passport is first used, the client generates a passport_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239), using a part of server-generated random secure_random from account.password as an additional source of entropy for OpenSSL (when re-encrypting the passport_secret with a more secure algorithm or after a 2FA password change, the previous passport_secret is used, instead). +Then passport_secret is then encrypted using the user's password and hashed using the schema and parameters specified in the new_algo field of account.password.

+

The server should always return a securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 constructor in the new_algo field. +If securePasswordKdfAlgoUnknown is returned, the remotely stored secret is encrypted using a new algorithm, not supported by the current client: the user should update their app.

+

The other constructors may be used only when decrypting old passport parameters generated by a legacy client; in this case, the passport secret should be re-encrypted and updated using new_algo.

+ +

Subsequently, the client receives the encrypted passport_secret from the server and decrypts it after the user enters their password ».

+

In case the password is changed or a more secure algorithm is introduced in an update of the API, the client re-encrypts the passport_secret using the new password. +If the password is disabled, all Telegram Passport data is lost.

+

Passport Secret Decryption

+

Schema:

+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
+
+secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
+
+account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+---functions---
+
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
+

The client requests the user's 2FA password and generates the SRP paramaters to be passed to account.getPasswordSettings.

+

If the password is correct, an account.passwordSettings constructor with secureSecretSettings is returned.

+

encrypted_passport_secret, passport_secret_fingerprint parameters are extracted from the secureSecretSettings constructor:

+
encrypted_passport_secret = secureSecretSettings.secure_secret
+passport_secret_fingerprint = secureSecretSettings.secure_id
+

The combined passport_secret_salt is extracted from the SecurePasswordKdfAlgo.

+
passport_secret_salt = SecurePasswordKdfAlgo.salt
+

Similar to passport secret encryption, the following process is used to decrypt and verify the encrypted_passport_secret:

+
    +
  • +

    The user's 2FA plaintext password is hashed using the specified algorithm.

    + +
  • +
  • +

    The secret_key and iv parameters are extracted from the generated password_hash

    +
    secret_key = slice( password_hash, 0, 32 )
    +iv = slice( password_hash, 32, 16 )
    +
  • +
  • +

    The encrypted_passport_secret is decrypted using AES256-CBC with the key secret_key and iv:

    +
    passport_secret = AES256_CBC_DEC(encrypted_passport_secret, secret_key, iv)
    +
  • +
  • +

    The passport_secret is verified by generating and checking the fingerprint:

    +
    my_passport_secret_fingerprint = long( slice( SHA256( passport_secret ), 0, 8 ) )
    +

    The client must verify that passport_secret_fingerprint is indeed equal to my_passport_secret_fingerprint.

    +
  • +
+

The passport_secret can now be used to decrypt encrypted passport data stored on telegram servers:

+

Data and File Encryption

+

Encryption

+

To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The the data is encrypted according to the following scheme:

+ +

Packing

+
SecureData
+
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
    +
  • data is an encrypted and padded (see Encryption) JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on the chosen type. +Data must be in JSON format and not TL, as it has to be passed directly to the service using E2E encryption, without the bot API middleman to convert TL objects.
  • +
  • data_hash is the data_hash
  • +
  • secret is the encrypted_data_secret
  • +
+

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
+
InputSecureFile
+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+---functions---
+
+upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
+

Files (JPG format, max. 10MB) are encrypted and padded (see Encryption), and then uploaded chunk by chunk as described in files », except that instead of generating an inputFile, an inputSecureFile should be generated, instead.

+
    +
  • As for secret chat files, the md5_checksum is to be set to the MD5 hash of the encrypted file, for a server-side integrity check.
  • +
  • The file_hash field should be set to the data_hash of the data.
  • +
  • The secret field is the encrypted_data_secret.
  • +
+
SecurePlainData
+
securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+---functions---
+
+account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
+account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
+account.verifyEmail#ecba39db email:string code:string = Bool;
+
+auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
+auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
+

The email/phone is passed in plaintext using the respective SecurePlainData constructor. +To verify a phone number or email and use it in Telegram Passport, use the appropriate methods:

+ +

The flow is similar to the one used for logging in:

+
    +
  • Send email/phone code using the appropriate account.sendVerify*Code method
  • +
  • Pass the received code to the appropriate account.verify* method
  • +
  • Only for phone code verification, you can also resend/cancel the phone code using auth.resendCode/auth.cancelCode, as for logging in.
  • +
+

For more info, see the authorization docs.

+

When to use each constructor.

+
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
+inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
+
+secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
+secureValueTypePassport#3dac6a00 = SecureValueType;
+secureValueTypeDriverLicense#6e425c4 = SecureValueType;
+secureValueTypeIdentityCard#a0d0744b = SecureValueType;
+secureValueTypeInternalPassport#99a48f23 = SecureValueType;
+secureValueTypeAddress#cbe31e26 = SecureValueType;
+secureValueTypeUtilityBill#fc36954e = SecureValueType;
+secureValueTypeBankStatement#89137c0d = SecureValueType;
+secureValueTypeRentalAgreement#8b883488 = SecureValueType;
+secureValueTypePassportRegistration#99e3806a = SecureValueType;
+secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
+secureValueTypePhone#b320aadb = SecureValueType;
+secureValueTypeEmail#8e3ca7ee = SecureValueType;
+
+securePlainPhone#7d6099dd phone:string = SecurePlainData;
+securePlainEmail#21ec5a5f email:string = SecurePlainData;
+
+secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
+
+inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
+

The schema for the inputSecureValue constructor defines the constructor to use for each field.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
+

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
+

Fetching and deleting stored passport data

+
---functions---
+
+account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
+account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
+account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
+

The above methods can be used to fetch or remove encrypted Telegram Passport files stored in the Telegram Cloud by document type.

+

Passport Credentials

+

When a service requests data, it passes a nonce to the client. The nonce is a cryptographically secure unique identifier which allows the service to identify a request when receiving data as well as confirm the integrity of the data. The Telegram server doesn't have access to this nonce.

+

Once the user authorizes the Telegram Passport data transfer, the client forms the credentials (Credentials JSON object). Credentials contain the data_hash and data_secret from each element of Telegram Passport to which the user has allowed access. In addition to this, the credentials will always contain the nonce that the client received from the service at the initiation of the request.

+

Credentials are then passed to the service through the Bot API in encrypted form. To encrypt the credentials, the client generates a credentials_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). Then the credentials are encrypted according to the following scheme:

+
    +
  • +

    Credentials are padded to a length which is divisible by 16 bytes. To achieve this, 32 to 255 bytes are added at the beginning, where the first byte always holds the number of added bytes and the rest are random.

    +
  • +
  • +

    A hash of the padded credentials credentials_hash is calculated:

    +
    credentials_hash = SHA256( credentials )
    +
  • +
  • +

    The encryption key credentials_key is calculated:

    +
    credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    +credentials_key = slice( credentials_secret_hash, 0, 32 )
    +iv = slice( credentials_secret_hash, 32, 16 )
    +
  • +
  • +

    Credentials are encrypted using AES256-CBC with the key credentials_key and iv.

    +
    encrypted_credentials = AES256-CBC-ENC(credentials, credentials_key, iv)
    +
  • +
  • +

    credentials_secret is encrypted with the public RSA-key of the service with OPENSSL_PKCS1_OAEP_PADDING.

    +
    encrypted_credentials_secret = RSA-ENC(credentials_secret, key, OPENSSL_PKCS1_OAEP_PADDING)
    +
  • +
  • +

    The encrypted credentials are passed to the service via the MTProto API together with the encrypred credentials_secret and credentials_hash. Along with the credentials, the service receives from the Telegram Cloud the data it requested in encrypted form. See Submitting the Passport Form and PassportData:

    +
    secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
    +
  • +
  • +

    data is the encrypted_credentials

    +
  • +
  • +

    hash is the credentials_hash

    +
  • +
  • +

    secret is the encrypted_credentials_secret

    +
  • +
+

Then the service decrypts the data as described here.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/passport/example.html b/data/corefork.telegram.org/passport/example.html new file mode 100644 index 0000000000..fbfa48d49e --- /dev/null +++ b/data/corefork.telegram.org/passport/example.html @@ -0,0 +1,585 @@ + + + + + Example + + + + + + + + + + + + + + + +
+ +
+
+
+
+

Example

+ +

If you'd like to test Telegram Passport, use this page to request data. If you'd like to check out a real-life implementation, please see this blog post for examples of services that have integrated Telegram Passport.

+

Request Telegram Passport Data

+

+

+
+
+
+ + +
+
+
+
+ +
+ +
+ +
+
+ +
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ + +
+
+
+
+ +
+ +
+ +
+ +
+
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ +
+
+ + +
+
+
+
+ +
+ +
+ +
+
+ +
+
+ +
+
+ + +
+
+
+ +

+
+
+

Note that the passport demo bot will only store data for 1 hour and then discard it. After logging in here, you can use the logout button on this page to reset your session.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/corefork.telegram.org/passport/sdk-android.html b/data/corefork.telegram.org/passport/sdk-android.html new file mode 100644 index 0000000000..9784921198 --- /dev/null +++ b/data/corefork.telegram.org/passport/sdk-android.html @@ -0,0 +1,180 @@ + + + + + Android SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Android SDK

+ +
+ +

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Installing from Maven

+

Telegram Passport SDK is available from the Maven repository. +Add this line to the dependencies section in your build.gradle:

+
compile 'org.telegram:passport:1.1'
+

and sync your project.

+

Adding as a module

+

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

+

In settings.gradle, add ':telegrampassport' to includes:

+
include ':app', ':telegrampassport'
+

In the build.gradle file for your app, add this line to the dependencies section:

+
compile ':telegrampassport'
+

and sync your project.

+

Usage

+

Adding the button

+

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

+
TelegramLoginButton telegramButton;
+// ...
+telegramButton=new TelegramLoginButton(this);
+// Optionally you can change the roundness of the button corners
+// to better fit your design.
+telegramButton.setCornerRoundness(1f);
+viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
+

Or from XML:

+
 <org.telegram.passport.TelegramLoginButton
+             android:layout_width="wrap_content"
+             android:layout_height="wrap_content"
+             app:cornerRoundness="0.5"/>
+

Requesting authorization

+

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

+
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
+// ...
+telegramButton.setOnClickListener(new View.OnClickListener(){
+@Override
+public void onClick(View view){
+    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
+    req.botID=/* your bot ID here */;
+    req.publicKey=/* your bot public key here */;
+    req.nonce=/* a unique nonce to pass to the bot server */;
+    // Request either a passport or an ID card with selfie, a driver license, personal details with
+    // name as it appears in the documents, address with any address document, and a phone number.
+    // You could also pass a raw JSON object here if that's what works better for you
+    // (for example, if you already get it from your server in the correct format).
+    req.scope=new PassportScope(
+        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
+        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
+        PassportScope.DRIVER_LICENSE,
+        PassportScope.ADDRESS,
+        PassportScope.ADDRESS_DOCUMENT,
+        PassportScope.PHONE_NUMBER
+    );
+    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
+}});
+

If you need more control over the process, the TelegramPassport class contains several more methods:

+
    +
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • +
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • +
+

Handling the result

+

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/passport/sdk-javascript.html b/data/corefork.telegram.org/passport/sdk-javascript.html new file mode 100644 index 0000000000..4a9ea10099 --- /dev/null +++ b/data/corefork.telegram.org/passport/sdk-javascript.html @@ -0,0 +1,258 @@ + + + + + Javascript SDK + + + + + + + + + + + + + +
+ +
+
+
+ +

Javascript SDK

+ +
+ +

The Javascript SDK helps you easily integrate Telegram Passport requests into your website. Check out our GitHub repository to see samples using this SDK.

+

Installation

+

Download and include the Javascript SDK in the head section of your page:

+
<script src="telegram-passport.js"></script>
+

Usage

+

Simply call Telegram.Passport.createAuthButton to create the default Telegram Passport button:

+
<div id="telegram_passport_auth"></div>
+<script>
+  Telegram.Passport.createAuthButton('telegram_passport_auth', {
+    bot_id:       123456, // place id of your bot here
+    scope:        {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
+    public_key:   '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
+    nonce:        'ab2df83746a87d2f3bd6...', // place nonce here
+    callback_url: 'https://example.com/callback/' // place callback url here
+  });
+</script>
+
+

Note that if you use a Content-Security-Policy (CSP) header with the frame-src/child-src directive you should allow tg: source to prevent errors in some browsers (e.g. Firefox)

+
+

createAuthButton

+ + + + + + + + + + + + + + + + + + + + + + + +
ParametersTypeRequired
elementString or DOMNodeYes
auth_paramsAuthParameters or FunctionYes
optionsAuthButtonOptionsOptional
+

AuthParameters

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
bot_idIntegerUnique identifier for the bot
scopePassportScopeA JSON-serialized object describing the data you want to request
public_keyStringPublic key of your bot
nonceStringBot-specified nonce
callback_urlStringOptional. URL to which the user will be redirected.
+

AuthButtonOptions

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
textStringOptional. Text on the button. Defaults to "Log In With Telegram".
radiusIntegerOptional. Radius of the button and tooltip in px. Defaults to 23.
tooltip_textStringOptional. Text on the tooltip. Defaults to "Please install Telegram to use this option.".
tooltip_positionStringOptional. Tooltip position. One of "top", "bottom", "left", "right". Defaults to "bottom".
tooltip_forceBooleanOptional. Always show a tooltip. Defaults to false.
+

You can also create your custom button. Do not forget about the tooltip. You should add an onclick listener to the button which calls the Telegram.Passport.auth(auth_params, tooltip_toggle); method:

+
<button id="telegram_passport_auth">Log In With Telegram</button>
+<script>
+  var auth_button = document.getElementById('telegram_passport_auth');
+  var auth_params = {
+    bot_id:        XXXXXX, // place id of your bot here
+    scope:         {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
+    public_key:    '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
+    nonce:         'ab2df83746a87d2f3bd6...', // place nonce here
+    callback_url:  'https://example.com/callback/' // place callback url here
+  };
+  auth_button.addEventListener('click', function() {
+    Telegram.Passport.auth(auth_params, function(show) {
+      if (show) {
+        // some code to show tooltip
+      } else {
+        // some code to hide tooltip
+      }
+    });
+  }, false);
+</script>
+

Receiving information

+

When the user confirms your request by pressing the 'Authorize' button, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=success and the Bot API will send the bot an Update with the field passport_data which contains encrypted Telegram Passport data.

+

If the user cancels your request, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=cancel.

+

If an error occurs during the request, the user will be redirected to the URL specified in the callback_url with the parameter tg_passport=error. The parameter error will contain one of the following values: BOT_INVALID, PUBLIC_KEY_REQUIRED, PUBLIC_KEY_INVALID, SCOPE_EMPTY, NONCE_EMPTY.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/corefork.telegram.org/schema/json.html b/data/corefork.telegram.org/schema/json.html new file mode 100644 index 0000000000..aba9f00ebe --- /dev/null +++ b/data/corefork.telegram.org/schema/json.html @@ -0,0 +1 @@ +{"constructors":[{"id":"-1132882121","predicate":"boolFalse","params":[],"type":"Bool"},{"id":"-1720552011","predicate":"boolTrue","params":[],"type":"Bool"},{"id":"1072550713","predicate":"true","params":[],"type":"True"},{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"-994444869","predicate":"error","params":[{"name":"code","type":"int"},{"name":"text","type":"string"}],"type":"Error"},{"id":"1450380236","predicate":"null","params":[],"type":"Null"},{"id":"2134579434","predicate":"inputPeerEmpty","params":[],"type":"InputPeer"},{"id":"2107670217","predicate":"inputPeerSelf","params":[],"type":"InputPeer"},{"id":"900291769","predicate":"inputPeerChat","params":[{"name":"chat_id","type":"long"}],"type":"InputPeer"},{"id":"-1182234929","predicate":"inputUserEmpty","params":[],"type":"InputUser"},{"id":"-138301121","predicate":"inputUserSelf","params":[],"type":"InputUser"},{"id":"-208488460","predicate":"inputPhoneContact","params":[{"name":"client_id","type":"long"},{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"InputContact"},{"id":"-181407105","predicate":"inputFile","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"},{"name":"md5_checksum","type":"string"}],"type":"InputFile"},{"id":"-1771768449","predicate":"inputMediaEmpty","params":[],"type":"InputMedia"},{"id":"505969924","predicate":"inputMediaUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"-1279654347","predicate":"inputMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputPhoto"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-104578748","predicate":"inputMediaGeoPoint","params":[{"name":"geo_point","type":"InputGeoPoint"}],"type":"InputMedia"},{"id":"-122978821","predicate":"inputMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"}],"type":"InputMedia"},{"id":"480546647","predicate":"inputChatPhotoEmpty","params":[],"type":"InputChatPhoto"},{"id":"-968723890","predicate":"inputChatUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"InputChatPhoto"},{"id":"-1991004873","predicate":"inputChatPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputChatPhoto"},{"id":"-457104426","predicate":"inputGeoPointEmpty","params":[],"type":"InputGeoPoint"},{"id":"1210199983","predicate":"inputGeoPoint","params":[{"name":"flags","type":"#"},{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"InputGeoPoint"},{"id":"483901197","predicate":"inputPhotoEmpty","params":[],"type":"InputPhoto"},{"id":"1001634122","predicate":"inputPhoto","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputPhoto"},{"id":"-539317279","predicate":"inputFileLocation","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputFileLocation"},{"id":"1498486562","predicate":"peerUser","params":[{"name":"user_id","type":"long"}],"type":"Peer"},{"id":"918946202","predicate":"peerChat","params":[{"name":"chat_id","type":"long"}],"type":"Peer"},{"id":"-1432995067","predicate":"storage.fileUnknown","params":[],"type":"storage.FileType"},{"id":"1086091090","predicate":"storage.filePartial","params":[],"type":"storage.FileType"},{"id":"8322574","predicate":"storage.fileJpeg","params":[],"type":"storage.FileType"},{"id":"-891180321","predicate":"storage.fileGif","params":[],"type":"storage.FileType"},{"id":"172975040","predicate":"storage.filePng","params":[],"type":"storage.FileType"},{"id":"-1373745011","predicate":"storage.filePdf","params":[],"type":"storage.FileType"},{"id":"1384777335","predicate":"storage.fileMp3","params":[],"type":"storage.FileType"},{"id":"1258941372","predicate":"storage.fileMov","params":[],"type":"storage.FileType"},{"id":"-1278304028","predicate":"storage.fileMp4","params":[],"type":"storage.FileType"},{"id":"276907596","predicate":"storage.fileWebp","params":[],"type":"storage.FileType"},{"id":"-742634630","predicate":"userEmpty","params":[{"name":"id","type":"long"}],"type":"User"},{"id":"1326562017","predicate":"userProfilePhotoEmpty","params":[],"type":"UserProfilePhoto"},{"id":"-2100168954","predicate":"userProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"UserProfilePhoto"},{"id":"164646985","predicate":"userStatusEmpty","params":[],"type":"UserStatus"},{"id":"-306628279","predicate":"userStatusOnline","params":[{"name":"expires","type":"int"}],"type":"UserStatus"},{"id":"9203775","predicate":"userStatusOffline","params":[{"name":"was_online","type":"int"}],"type":"UserStatus"},{"id":"693512293","predicate":"chatEmpty","params":[{"name":"id","type":"long"}],"type":"Chat"},{"id":"1103884886","predicate":"chat","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"kicked","type":"flags.1?true"},{"name":"left","type":"flags.2?true"},{"name":"deactivated","type":"flags.5?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"noforwards","type":"flags.25?true"},{"name":"id","type":"long"},{"name":"title","type":"string"},{"name":"photo","type":"ChatPhoto"},{"name":"participants_count","type":"int"},{"name":"date","type":"int"},{"name":"version","type":"int"},{"name":"migrated_to","type":"flags.6?InputChannel"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"}],"type":"Chat"},{"id":"1704108455","predicate":"chatForbidden","params":[{"name":"id","type":"long"},{"name":"title","type":"string"}],"type":"Chat"},{"id":"-779165146","predicate":"chatFull","params":[{"name":"flags","type":"#"},{"name":"can_set_username","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants","type":"ChatParticipants"},{"name":"chat_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.13?ExportedChatInvite"},{"name":"bot_info","type":"flags.3?Vector"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"call","type":"flags.12?InputGroupCall"},{"name":"ttl_period","type":"flags.14?int"},{"name":"groupcall_default_join_as","type":"flags.15?Peer"},{"name":"theme_emoticon","type":"flags.16?string"},{"name":"requests_pending","type":"flags.17?int"},{"name":"recent_requesters","type":"flags.17?Vector"},{"name":"available_reactions","type":"flags.18?Vector"}],"type":"ChatFull"},{"id":"-1070776313","predicate":"chatParticipant","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-2023500831","predicate":"chatParticipantsForbidden","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"self_participant","type":"flags.0?ChatParticipant"}],"type":"ChatParticipants"},{"id":"1018991608","predicate":"chatParticipants","params":[{"name":"chat_id","type":"long"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"ChatParticipants"},{"id":"935395612","predicate":"chatPhotoEmpty","params":[],"type":"ChatPhoto"},{"id":"476978193","predicate":"chatPhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"ChatPhoto"},{"id":"-1868117372","predicate":"messageEmpty","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"peer_id","type":"flags.0?Peer"}],"type":"Message"},{"id":"940666592","predicate":"message","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"from_scheduled","type":"flags.18?true"},{"name":"legacy","type":"flags.19?true"},{"name":"edit_hide","type":"flags.21?true"},{"name":"pinned","type":"flags.24?true"},{"name":"noforwards","type":"flags.26?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"reply_markup","type":"flags.6?ReplyMarkup"},{"name":"entities","type":"flags.7?Vector"},{"name":"views","type":"flags.10?int"},{"name":"forwards","type":"flags.10?int"},{"name":"replies","type":"flags.23?MessageReplies"},{"name":"edit_date","type":"flags.15?int"},{"name":"post_author","type":"flags.16?string"},{"name":"grouped_id","type":"flags.17?long"},{"name":"reactions","type":"flags.20?MessageReactions"},{"name":"restriction_reason","type":"flags.22?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"721967202","predicate":"messageService","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"legacy","type":"flags.19?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"action","type":"MessageAction"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"1038967584","predicate":"messageMediaEmpty","params":[],"type":"MessageMedia"},{"id":"1766936791","predicate":"messageMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"photo","type":"flags.0?Photo"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1457575028","predicate":"messageMediaGeo","params":[{"name":"geo","type":"GeoPoint"}],"type":"MessageMedia"},{"id":"1882335561","predicate":"messageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"user_id","type":"long"}],"type":"MessageMedia"},{"id":"-1618676578","predicate":"messageMediaUnsupported","params":[],"type":"MessageMedia"},{"id":"-1230047312","predicate":"messageActionEmpty","params":[],"type":"MessageAction"},{"id":"-1119368275","predicate":"messageActionChatCreate","params":[{"name":"title","type":"string"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1247687078","predicate":"messageActionChatEditTitle","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"2144015272","predicate":"messageActionChatEditPhoto","params":[{"name":"photo","type":"Photo"}],"type":"MessageAction"},{"id":"-1780220945","predicate":"messageActionChatDeletePhoto","params":[],"type":"MessageAction"},{"id":"365886720","predicate":"messageActionChatAddUser","params":[{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1539362612","predicate":"messageActionChatDeleteUser","params":[{"name":"user_id","type":"long"}],"type":"MessageAction"},{"id":"-1460809483","predicate":"dialog","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"unread_mark","type":"flags.3?true"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"unread_mentions_count","type":"int"},{"name":"unread_reactions_count","type":"int"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"pts","type":"flags.0?int"},{"name":"draft","type":"flags.1?DraftMessage"},{"name":"folder_id","type":"flags.4?int"}],"type":"Dialog"},{"id":"590459437","predicate":"photoEmpty","params":[{"name":"id","type":"long"}],"type":"Photo"},{"id":"-82216347","predicate":"photo","params":[{"name":"flags","type":"#"},{"name":"has_stickers","type":"flags.0?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"sizes","type":"Vector"},{"name":"video_sizes","type":"flags.1?Vector"},{"name":"dc_id","type":"int"}],"type":"Photo"},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize"},{"id":"1976012384","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize"},{"id":"35527382","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"286776671","predicate":"geoPointEmpty","params":[],"type":"GeoPoint"},{"id":"-1297942941","predicate":"geoPoint","params":[{"name":"flags","type":"#"},{"name":"long","type":"double"},{"name":"lat","type":"double"},{"name":"access_hash","type":"long"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"GeoPoint"},{"id":"1577067778","predicate":"auth.sentCode","params":[{"name":"flags","type":"#"},{"name":"type","type":"auth.SentCodeType"},{"name":"phone_code_hash","type":"string"},{"name":"next_type","type":"flags.1?auth.CodeType"},{"name":"timeout","type":"flags.2?int"}],"type":"auth.SentCode"},{"id":"872119224","predicate":"auth.authorization","params":[{"name":"flags","type":"#"},{"name":"setup_password_required","type":"flags.1?true"},{"name":"otherwise_relogin_days","type":"flags.1?int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"user","type":"User"}],"type":"auth.Authorization"},{"id":"-1271602504","predicate":"auth.exportedAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.ExportedAuthorization"},{"id":"-1195615476","predicate":"inputNotifyPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputNotifyPeer"},{"id":"423314455","predicate":"inputNotifyUsers","params":[],"type":"InputNotifyPeer"},{"id":"1251338318","predicate":"inputNotifyChats","params":[],"type":"InputNotifyPeer"},{"id":"-1673717362","predicate":"inputPeerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"InputPeerNotifySettings"},{"id":"-1353671392","predicate":"peerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"PeerNotifySettings"},{"id":"-1525149427","predicate":"peerSettings","params":[{"name":"flags","type":"#"},{"name":"report_spam","type":"flags.0?true"},{"name":"add_contact","type":"flags.1?true"},{"name":"block_contact","type":"flags.2?true"},{"name":"share_contact","type":"flags.3?true"},{"name":"need_contacts_exception","type":"flags.4?true"},{"name":"report_geo","type":"flags.5?true"},{"name":"autoarchived","type":"flags.7?true"},{"name":"invite_members","type":"flags.8?true"},{"name":"request_chat_broadcast","type":"flags.10?true"},{"name":"geo_distance","type":"flags.6?int"},{"name":"request_chat_title","type":"flags.9?string"},{"name":"request_chat_date","type":"flags.9?int"}],"type":"PeerSettings"},{"id":"-1539849235","predicate":"wallPaper","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"pattern","type":"flags.3?true"},{"name":"dark","type":"flags.4?true"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"document","type":"Document"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"1490799288","predicate":"inputReportReasonSpam","params":[],"type":"ReportReason"},{"id":"505595789","predicate":"inputReportReasonViolence","params":[],"type":"ReportReason"},{"id":"777640226","predicate":"inputReportReasonPornography","params":[],"type":"ReportReason"},{"id":"-1376497949","predicate":"inputReportReasonChildAbuse","params":[],"type":"ReportReason"},{"id":"-1041980751","predicate":"inputReportReasonOther","params":[],"type":"ReportReason"},{"id":"-818518751","predicate":"userFull","params":[{"name":"flags","type":"#"},{"name":"blocked","type":"flags.0?true"},{"name":"phone_calls_available","type":"flags.4?true"},{"name":"phone_calls_private","type":"flags.5?true"},{"name":"can_pin_message","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.12?true"},{"name":"video_calls_available","type":"flags.13?true"},{"name":"id","type":"long"},{"name":"about","type":"flags.1?string"},{"name":"settings","type":"PeerSettings"},{"name":"profile_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"bot_info","type":"flags.3?BotInfo"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"common_chats_count","type":"int"},{"name":"folder_id","type":"flags.11?int"},{"name":"ttl_period","type":"flags.14?int"},{"name":"theme_emoticon","type":"flags.15?string"},{"name":"private_forward_name","type":"flags.16?string"}],"type":"UserFull"},{"id":"341499403","predicate":"contact","params":[{"name":"user_id","type":"long"},{"name":"mutual","type":"Bool"}],"type":"Contact"},{"id":"-1052885936","predicate":"importedContact","params":[{"name":"user_id","type":"long"},{"name":"client_id","type":"long"}],"type":"ImportedContact"},{"id":"383348795","predicate":"contactStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"ContactStatus"},{"id":"-1219778094","predicate":"contacts.contactsNotModified","params":[],"type":"contacts.Contacts"},{"id":"-353862078","predicate":"contacts.contacts","params":[{"name":"contacts","type":"Vector"},{"name":"saved_count","type":"int"},{"name":"users","type":"Vector"}],"type":"contacts.Contacts"},{"id":"2010127419","predicate":"contacts.importedContacts","params":[{"name":"imported","type":"Vector"},{"name":"popular_invites","type":"Vector"},{"name":"retry_contacts","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"182326673","predicate":"contacts.blocked","params":[{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"-513392236","predicate":"contacts.blockedSlice","params":[{"name":"count","type":"int"},{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"364538944","predicate":"messages.dialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"1910543603","predicate":"messages.dialogsSlice","params":[{"name":"count","type":"int"},{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"-1938715001","predicate":"messages.messages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"978610270","predicate":"messages.messagesSlice","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"count","type":"int"},{"name":"next_rate","type":"flags.0?int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"1694474197","predicate":"messages.chats","params":[{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-438840932","predicate":"messages.chatFull","params":[{"name":"full_chat","type":"ChatFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatFull"},{"id":"-1269012015","predicate":"messages.affectedHistory","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"}],"type":"messages.AffectedHistory"},{"id":"1474492012","predicate":"inputMessagesFilterEmpty","params":[],"type":"MessagesFilter"},{"id":"-1777752804","predicate":"inputMessagesFilterPhotos","params":[],"type":"MessagesFilter"},{"id":"-1614803355","predicate":"inputMessagesFilterVideo","params":[],"type":"MessagesFilter"},{"id":"1458172132","predicate":"inputMessagesFilterPhotoVideo","params":[],"type":"MessagesFilter"},{"id":"-1629621880","predicate":"inputMessagesFilterDocument","params":[],"type":"MessagesFilter"},{"id":"2129714567","predicate":"inputMessagesFilterUrl","params":[],"type":"MessagesFilter"},{"id":"-3644025","predicate":"inputMessagesFilterGif","params":[],"type":"MessagesFilter"},{"id":"522914557","predicate":"updateNewMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1318109142","predicate":"updateMessageID","params":[{"name":"id","type":"int"},{"name":"random_id","type":"long"}],"type":"Update"},{"id":"-1576161051","predicate":"updateDeleteMessages","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1071741569","predicate":"updateUserTyping","params":[{"name":"user_id","type":"long"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-2092401936","predicate":"updateChatUserTyping","params":[{"name":"chat_id","type":"long"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"125178264","predicate":"updateChatParticipants","params":[{"name":"participants","type":"ChatParticipants"}],"type":"Update"},{"id":"-440534818","predicate":"updateUserStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"Update"},{"id":"-1007549728","predicate":"updateUserName","params":[{"name":"user_id","type":"long"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"username","type":"string"}],"type":"Update"},{"id":"-232290676","predicate":"updateUserPhoto","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"photo","type":"UserProfilePhoto"},{"name":"previous","type":"Bool"}],"type":"Update"},{"id":"-1519637954","predicate":"updates.state","params":[{"name":"pts","type":"int"},{"name":"qts","type":"int"},{"name":"date","type":"int"},{"name":"seq","type":"int"},{"name":"unread_count","type":"int"}],"type":"updates.State"},{"id":"1567990072","predicate":"updates.differenceEmpty","params":[{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"updates.Difference"},{"id":"16030880","predicate":"updates.difference","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-1459938943","predicate":"updates.differenceSlice","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"intermediate_state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-484987010","predicate":"updatesTooLong","params":[],"type":"Updates"},{"id":"826001400","predicate":"updateShortMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"user_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"1299050149","predicate":"updateShortChatMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"from_id","type":"long"},{"name":"chat_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"2027216577","predicate":"updateShort","params":[{"name":"update","type":"Update"},{"name":"date","type":"int"}],"type":"Updates"},{"id":"1918567619","predicate":"updatesCombined","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq_start","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"1957577280","predicate":"updates","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"-1916114267","predicate":"photos.photos","params":[{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"352657236","predicate":"photos.photosSlice","params":[{"name":"count","type":"int"},{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"539045032","predicate":"photos.photo","params":[{"name":"photo","type":"Photo"},{"name":"users","type":"Vector"}],"type":"photos.Photo"},{"id":"157948117","predicate":"upload.file","params":[{"name":"type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.File"},{"id":"414687501","predicate":"dcOption","params":[{"name":"flags","type":"#"},{"name":"ipv6","type":"flags.0?true"},{"name":"media_only","type":"flags.1?true"},{"name":"tcpo_only","type":"flags.2?true"},{"name":"cdn","type":"flags.3?true"},{"name":"static","type":"flags.4?true"},{"name":"id","type":"int"},{"name":"ip_address","type":"string"},{"name":"port","type":"int"},{"name":"secret","type":"flags.10?bytes"}],"type":"DcOption"},{"id":"856375399","predicate":"config","params":[{"name":"flags","type":"#"},{"name":"phonecalls_enabled","type":"flags.1?true"},{"name":"default_p2p_contacts","type":"flags.3?true"},{"name":"preload_featured_stickers","type":"flags.4?true"},{"name":"ignore_phone_entities","type":"flags.5?true"},{"name":"revoke_pm_inbox","type":"flags.6?true"},{"name":"blocked_mode","type":"flags.8?true"},{"name":"pfs_enabled","type":"flags.13?true"},{"name":"date","type":"int"},{"name":"expires","type":"int"},{"name":"test_mode","type":"Bool"},{"name":"this_dc","type":"int"},{"name":"dc_options","type":"Vector"},{"name":"dc_txt_domain_name","type":"string"},{"name":"chat_size_max","type":"int"},{"name":"megagroup_size_max","type":"int"},{"name":"forwarded_count_max","type":"int"},{"name":"online_update_period_ms","type":"int"},{"name":"offline_blur_timeout_ms","type":"int"},{"name":"offline_idle_timeout_ms","type":"int"},{"name":"online_cloud_timeout_ms","type":"int"},{"name":"notify_cloud_delay_ms","type":"int"},{"name":"notify_default_delay_ms","type":"int"},{"name":"push_chat_period_ms","type":"int"},{"name":"push_chat_limit","type":"int"},{"name":"saved_gifs_limit","type":"int"},{"name":"edit_time_limit","type":"int"},{"name":"revoke_time_limit","type":"int"},{"name":"revoke_pm_time_limit","type":"int"},{"name":"rating_e_decay","type":"int"},{"name":"stickers_recent_limit","type":"int"},{"name":"stickers_faved_limit","type":"int"},{"name":"channels_read_media_period","type":"int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"pinned_dialogs_count_max","type":"int"},{"name":"pinned_infolder_count_max","type":"int"},{"name":"call_receive_timeout_ms","type":"int"},{"name":"call_ring_timeout_ms","type":"int"},{"name":"call_connect_timeout_ms","type":"int"},{"name":"call_packet_timeout_ms","type":"int"},{"name":"me_url_prefix","type":"string"},{"name":"autoupdate_url_prefix","type":"flags.7?string"},{"name":"gif_search_username","type":"flags.9?string"},{"name":"venue_search_username","type":"flags.10?string"},{"name":"img_search_username","type":"flags.11?string"},{"name":"static_maps_provider","type":"flags.12?string"},{"name":"caption_length_max","type":"int"},{"name":"message_length_max","type":"int"},{"name":"webfile_dc_id","type":"int"},{"name":"suggested_lang_code","type":"flags.2?string"},{"name":"lang_pack_version","type":"flags.2?int"},{"name":"base_lang_pack_version","type":"flags.2?int"}],"type":"Config"},{"id":"-1910892683","predicate":"nearestDc","params":[{"name":"country","type":"string"},{"name":"this_dc","type":"int"},{"name":"nearest_dc","type":"int"}],"type":"NearestDc"},{"id":"-860107216","predicate":"help.appUpdate","params":[{"name":"flags","type":"#"},{"name":"can_not_skip","type":"flags.0?true"},{"name":"id","type":"int"},{"name":"version","type":"string"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"document","type":"flags.1?Document"},{"name":"url","type":"flags.2?string"},{"name":"sticker","type":"flags.3?Document"}],"type":"help.AppUpdate"},{"id":"-1000708810","predicate":"help.noAppUpdate","params":[],"type":"help.AppUpdate"},{"id":"415997816","predicate":"help.inviteText","params":[{"name":"message","type":"string"}],"type":"help.InviteText"},{"id":"314359194","predicate":"updateNewEncryptedMessage","params":[{"name":"message","type":"EncryptedMessage"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"386986326","predicate":"updateEncryptedChatTyping","params":[{"name":"chat_id","type":"int"}],"type":"Update"},{"id":"-1264392051","predicate":"updateEncryption","params":[{"name":"chat","type":"EncryptedChat"},{"name":"date","type":"int"}],"type":"Update"},{"id":"956179895","predicate":"updateEncryptedMessagesRead","params":[{"name":"chat_id","type":"int"},{"name":"max_date","type":"int"},{"name":"date","type":"int"}],"type":"Update"},{"id":"-1417756512","predicate":"encryptedChatEmpty","params":[{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"1722964307","predicate":"encryptedChatWaiting","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"}],"type":"EncryptedChat"},{"id":"1223809356","predicate":"encryptedChatRequested","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1643173063","predicate":"encryptedChat","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"505183301","predicate":"encryptedChatDiscarded","params":[{"name":"flags","type":"#"},{"name":"history_deleted","type":"flags.0?true"},{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"-247351839","predicate":"inputEncryptedChat","params":[{"name":"chat_id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedChat"},{"id":"-1038136962","predicate":"encryptedFileEmpty","params":[],"type":"EncryptedFile"},{"id":"1248893260","predicate":"encryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"EncryptedFile"},{"id":"406307684","predicate":"inputEncryptedFileEmpty","params":[],"type":"InputEncryptedFile"},{"id":"1690108678","predicate":"inputEncryptedFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1511503333","predicate":"inputEncryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedFile"},{"id":"-182231723","predicate":"inputEncryptedFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"-317144808","predicate":"encryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"},{"name":"file","type":"EncryptedFile"}],"type":"EncryptedMessage"},{"id":"594758406","predicate":"encryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"}],"type":"EncryptedMessage"},{"id":"-1058912715","predicate":"messages.dhConfigNotModified","params":[{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"740433629","predicate":"messages.dhConfig","params":[{"name":"g","type":"int"},{"name":"p","type":"bytes"},{"name":"version","type":"int"},{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"1443858741","predicate":"messages.sentEncryptedMessage","params":[{"name":"date","type":"int"}],"type":"messages.SentEncryptedMessage"},{"id":"-1802240206","predicate":"messages.sentEncryptedFile","params":[{"name":"date","type":"int"},{"name":"file","type":"EncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"-95482955","predicate":"inputFileBig","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"}],"type":"InputFile"},{"id":"767652808","predicate":"inputEncryptedFileBigUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1037718609","predicate":"updateChatParticipantAdd","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-483443337","predicate":"updateChatParticipantDelete","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-1906403213","predicate":"updateDcOptions","params":[{"name":"dc_options","type":"Vector"}],"type":"Update"},{"id":"1530447553","predicate":"inputMediaUploadedDocument","params":[{"name":"flags","type":"#"},{"name":"nosound_video","type":"flags.3?true"},{"name":"force_file","type":"flags.4?true"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.2?InputFile"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"860303448","predicate":"inputMediaDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputDocument"},{"name":"ttl_seconds","type":"flags.0?int"},{"name":"query","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-1666158377","predicate":"messageMediaDocument","params":[{"name":"flags","type":"#"},{"name":"document","type":"flags.0?Document"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1928391342","predicate":"inputDocumentEmpty","params":[],"type":"InputDocument"},{"id":"448771445","predicate":"inputDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputDocument"},{"id":"-1160743548","predicate":"inputDocumentFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"922273905","predicate":"documentEmpty","params":[{"name":"id","type":"long"}],"type":"Document"},{"id":"512177195","predicate":"document","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumbs","type":"flags.0?Vector"},{"name":"video_thumbs","type":"flags.1?Vector"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"Document"},{"id":"398898678","predicate":"help.support","params":[{"name":"phone_number","type":"string"},{"name":"user","type":"User"}],"type":"help.Support"},{"id":"-1613493288","predicate":"notifyPeer","params":[{"name":"peer","type":"Peer"}],"type":"NotifyPeer"},{"id":"-1261946036","predicate":"notifyUsers","params":[],"type":"NotifyPeer"},{"id":"-1073230141","predicate":"notifyChats","params":[],"type":"NotifyPeer"},{"id":"-1094555409","predicate":"updateNotifySettings","params":[{"name":"peer","type":"NotifyPeer"},{"name":"notify_settings","type":"PeerNotifySettings"}],"type":"Update"},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction"},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction"},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction"},{"id":"-378127636","predicate":"sendMessageUploadVideoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction"},{"id":"-212740181","predicate":"sendMessageUploadAudioAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-774682074","predicate":"sendMessageUploadPhotoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-1441998364","predicate":"sendMessageUploadDocumentAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction"},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction"},{"id":"-1290580579","predicate":"contacts.found","params":[{"name":"my_results","type":"Vector"},{"name":"results","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Found"},{"id":"-337352679","predicate":"updateServiceNotification","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"inbox_date","type":"flags.1?int"},{"name":"type","type":"string"},{"name":"message","type":"string"},{"name":"media","type":"MessageMedia"},{"name":"entities","type":"Vector"}],"type":"Update"},{"id":"-496024847","predicate":"userStatusRecently","params":[],"type":"UserStatus"},{"id":"129960444","predicate":"userStatusLastWeek","params":[],"type":"UserStatus"},{"id":"2011940674","predicate":"userStatusLastMonth","params":[],"type":"UserStatus"},{"id":"-298113238","predicate":"updatePrivacy","params":[{"name":"key","type":"PrivacyKey"},{"name":"rules","type":"Vector"}],"type":"Update"},{"id":"1335282456","predicate":"inputPrivacyKeyStatusTimestamp","params":[],"type":"InputPrivacyKey"},{"id":"-1137792208","predicate":"privacyKeyStatusTimestamp","params":[],"type":"PrivacyKey"},{"id":"218751099","predicate":"inputPrivacyValueAllowContacts","params":[],"type":"InputPrivacyRule"},{"id":"407582158","predicate":"inputPrivacyValueAllowAll","params":[],"type":"InputPrivacyRule"},{"id":"320652927","predicate":"inputPrivacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"195371015","predicate":"inputPrivacyValueDisallowContacts","params":[],"type":"InputPrivacyRule"},{"id":"-697604407","predicate":"inputPrivacyValueDisallowAll","params":[],"type":"InputPrivacyRule"},{"id":"-1877932953","predicate":"inputPrivacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-123988","predicate":"privacyValueAllowContacts","params":[],"type":"PrivacyRule"},{"id":"1698855810","predicate":"privacyValueAllowAll","params":[],"type":"PrivacyRule"},{"id":"-1198497870","predicate":"privacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"-125240806","predicate":"privacyValueDisallowContacts","params":[],"type":"PrivacyRule"},{"id":"-1955338397","predicate":"privacyValueDisallowAll","params":[],"type":"PrivacyRule"},{"id":"-463335103","predicate":"privacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"1352683077","predicate":"account.privacyRules","params":[{"name":"rules","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"-1194283041","predicate":"accountDaysTTL","params":[{"name":"days","type":"int"}],"type":"AccountDaysTTL"},{"id":"88680979","predicate":"updateUserPhone","params":[{"name":"user_id","type":"long"},{"name":"phone","type":"string"}],"type":"Update"},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute"},{"id":"1662637586","predicate":"documentAttributeSticker","params":[{"name":"flags","type":"#"},{"name":"mask","type":"flags.1?true"},{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"DocumentAttribute"},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"round_message","type":"flags.0?true"},{"name":"supports_streaming","type":"flags.1?true"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"voice","type":"flags.10?true"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute"},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute"},{"id":"-244016606","predicate":"messages.stickersNotModified","params":[],"type":"messages.Stickers"},{"id":"816245886","predicate":"messages.stickers","params":[{"name":"hash","type":"long"},{"name":"stickers","type":"Vector"}],"type":"messages.Stickers"},{"id":"313694676","predicate":"stickerPack","params":[{"name":"emoticon","type":"string"},{"name":"documents","type":"Vector"}],"type":"StickerPack"},{"id":"-395967805","predicate":"messages.allStickersNotModified","params":[],"type":"messages.AllStickers"},{"id":"-843329861","predicate":"messages.allStickers","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.AllStickers"},{"id":"-1667805217","predicate":"updateReadHistoryInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"791617983","predicate":"updateReadHistoryOutbox","params":[{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-2066640507","predicate":"messages.affectedMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"messages.AffectedMessages"},{"id":"2139689491","predicate":"updateWebPage","params":[{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-350980120","predicate":"webPageEmpty","params":[{"name":"id","type":"long"}],"type":"WebPage"},{"id":"-981018084","predicate":"webPagePending","params":[{"name":"id","type":"long"},{"name":"date","type":"int"}],"type":"WebPage"},{"id":"-392411726","predicate":"webPage","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"url","type":"string"},{"name":"display_url","type":"string"},{"name":"hash","type":"int"},{"name":"type","type":"flags.0?string"},{"name":"site_name","type":"flags.1?string"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"photo","type":"flags.4?Photo"},{"name":"embed_url","type":"flags.5?string"},{"name":"embed_type","type":"flags.5?string"},{"name":"embed_width","type":"flags.6?int"},{"name":"embed_height","type":"flags.6?int"},{"name":"duration","type":"flags.7?int"},{"name":"author","type":"flags.8?string"},{"name":"document","type":"flags.9?Document"},{"name":"cached_page","type":"flags.10?Page"},{"name":"attributes","type":"flags.12?Vector"}],"type":"WebPage"},{"id":"-1557277184","predicate":"messageMediaWebPage","params":[{"name":"webpage","type":"WebPage"}],"type":"MessageMedia"},{"id":"-1392388579","predicate":"authorization","params":[{"name":"flags","type":"#"},{"name":"current","type":"flags.0?true"},{"name":"official_app","type":"flags.1?true"},{"name":"password_pending","type":"flags.2?true"},{"name":"encrypted_requests_disabled","type":"flags.3?true"},{"name":"call_requests_disabled","type":"flags.4?true"},{"name":"hash","type":"long"},{"name":"device_model","type":"string"},{"name":"platform","type":"string"},{"name":"system_version","type":"string"},{"name":"api_id","type":"int"},{"name":"app_name","type":"string"},{"name":"app_version","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"country","type":"string"},{"name":"region","type":"string"}],"type":"Authorization"},{"id":"1275039392","predicate":"account.authorizations","params":[{"name":"authorization_ttl_days","type":"int"},{"name":"authorizations","type":"Vector"}],"type":"account.Authorizations"},{"id":"408623183","predicate":"account.password","params":[{"name":"flags","type":"#"},{"name":"has_recovery","type":"flags.0?true"},{"name":"has_secure_values","type":"flags.1?true"},{"name":"has_password","type":"flags.2?true"},{"name":"current_algo","type":"flags.2?PasswordKdfAlgo"},{"name":"srp_B","type":"flags.2?bytes"},{"name":"srp_id","type":"flags.2?long"},{"name":"hint","type":"flags.3?string"},{"name":"email_unconfirmed_pattern","type":"flags.4?string"},{"name":"new_algo","type":"PasswordKdfAlgo"},{"name":"new_secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_random","type":"bytes"},{"name":"pending_reset_date","type":"flags.5?int"}],"type":"account.Password"},{"id":"-1705233435","predicate":"account.passwordSettings","params":[{"name":"flags","type":"#"},{"name":"email","type":"flags.0?string"},{"name":"secure_settings","type":"flags.1?SecureSecretSettings"}],"type":"account.PasswordSettings"},{"id":"-1036572727","predicate":"account.passwordInputSettings","params":[{"name":"flags","type":"#"},{"name":"new_algo","type":"flags.0?PasswordKdfAlgo"},{"name":"new_password_hash","type":"flags.0?bytes"},{"name":"hint","type":"flags.0?string"},{"name":"email","type":"flags.1?string"},{"name":"new_secure_settings","type":"flags.2?SecureSecretSettings"}],"type":"account.PasswordInputSettings"},{"id":"326715557","predicate":"auth.passwordRecovery","params":[{"name":"email_pattern","type":"string"}],"type":"auth.PasswordRecovery"},{"id":"-1052959727","predicate":"inputMediaVenue","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"InputMedia"},{"id":"784356159","predicate":"messageMediaVenue","params":[{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"MessageMedia"},{"id":"-1551583367","predicate":"receivedNotifyMessage","params":[{"name":"id","type":"int"},{"name":"flags","type":"int"}],"type":"ReceivedNotifyMessage"},{"id":"179611673","predicate":"chatInviteExported","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.0?true"},{"name":"permanent","type":"flags.5?true"},{"name":"request_needed","type":"flags.6?true"},{"name":"link","type":"string"},{"name":"admin_id","type":"long"},{"name":"date","type":"int"},{"name":"start_date","type":"flags.4?int"},{"name":"expire_date","type":"flags.1?int"},{"name":"usage_limit","type":"flags.2?int"},{"name":"usage","type":"flags.3?int"},{"name":"requested","type":"flags.7?int"},{"name":"title","type":"flags.8?string"}],"type":"ExportedChatInvite"},{"id":"1516793212","predicate":"chatInviteAlready","params":[{"name":"chat","type":"Chat"}],"type":"ChatInvite"},{"id":"806110401","predicate":"chatInvite","params":[{"name":"flags","type":"#"},{"name":"channel","type":"flags.0?true"},{"name":"broadcast","type":"flags.1?true"},{"name":"public","type":"flags.2?true"},{"name":"megagroup","type":"flags.3?true"},{"name":"request_needed","type":"flags.6?true"},{"name":"title","type":"string"},{"name":"about","type":"flags.5?string"},{"name":"photo","type":"Photo"},{"name":"participants_count","type":"int"},{"name":"participants","type":"flags.4?Vector"}],"type":"ChatInvite"},{"id":"51520707","predicate":"messageActionChatJoinedByLink","params":[{"name":"inviter_id","type":"long"}],"type":"MessageAction"},{"id":"1757493555","predicate":"updateReadMessagesContents","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet"},{"id":"-1645763991","predicate":"inputStickerSetID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputStickerSet"},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet"},{"id":"-673242758","predicate":"stickerSet","params":[{"name":"flags","type":"#"},{"name":"archived","type":"flags.1?true"},{"name":"official","type":"flags.2?true"},{"name":"masks","type":"flags.3?true"},{"name":"animated","type":"flags.5?true"},{"name":"videos","type":"flags.6?true"},{"name":"installed_date","type":"flags.0?int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumbs","type":"flags.4?Vector"},{"name":"thumb_dc_id","type":"flags.4?int"},{"name":"thumb_version","type":"flags.4?int"},{"name":"count","type":"int"},{"name":"hash","type":"int"}],"type":"StickerSet"},{"id":"-1240849242","predicate":"messages.stickerSet","params":[{"name":"set","type":"StickerSet"},{"name":"packs","type":"Vector"},{"name":"documents","type":"Vector"}],"type":"messages.StickerSet"},{"id":"1073147056","predicate":"user","params":[{"name":"flags","type":"#"},{"name":"self","type":"flags.10?true"},{"name":"contact","type":"flags.11?true"},{"name":"mutual_contact","type":"flags.12?true"},{"name":"deleted","type":"flags.13?true"},{"name":"bot","type":"flags.14?true"},{"name":"bot_chat_history","type":"flags.15?true"},{"name":"bot_nochats","type":"flags.16?true"},{"name":"verified","type":"flags.17?true"},{"name":"restricted","type":"flags.18?true"},{"name":"min","type":"flags.20?true"},{"name":"bot_inline_geo","type":"flags.21?true"},{"name":"support","type":"flags.23?true"},{"name":"scam","type":"flags.24?true"},{"name":"apply_min_photo","type":"flags.25?true"},{"name":"fake","type":"flags.26?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.0?long"},{"name":"first_name","type":"flags.1?string"},{"name":"last_name","type":"flags.2?string"},{"name":"username","type":"flags.3?string"},{"name":"phone","type":"flags.4?string"},{"name":"photo","type":"flags.5?UserProfilePhoto"},{"name":"status","type":"flags.6?UserStatus"},{"name":"bot_info_version","type":"flags.14?int"},{"name":"restriction_reason","type":"flags.18?Vector"},{"name":"bot_inline_placeholder","type":"flags.19?string"},{"name":"lang_code","type":"flags.22?string"}],"type":"User"},{"id":"-1032140601","predicate":"botCommand","params":[{"name":"command","type":"string"},{"name":"description","type":"string"}],"type":"BotCommand"},{"id":"460632885","predicate":"botInfo","params":[{"name":"user_id","type":"long"},{"name":"description","type":"string"},{"name":"commands","type":"Vector"}],"type":"BotInfo"},{"id":"-1560655744","predicate":"keyboardButton","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"2002815875","predicate":"keyboardButtonRow","params":[{"name":"buttons","type":"Vector"}],"type":"KeyboardButtonRow"},{"id":"-1606526075","predicate":"replyKeyboardHide","params":[{"name":"flags","type":"#"},{"name":"selective","type":"flags.2?true"}],"type":"ReplyMarkup"},{"id":"-2035021048","predicate":"replyKeyboardForceReply","params":[{"name":"flags","type":"#"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-2049074735","predicate":"replyKeyboardMarkup","params":[{"name":"flags","type":"#"},{"name":"resize","type":"flags.0?true"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"rows","type":"Vector"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-571955892","predicate":"inputPeerUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-233744186","predicate":"inputUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputUser"},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity"},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity"},{"id":"-1877614335","predicate":"updateShortSentMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"-292807034","predicate":"inputChannelEmpty","params":[],"type":"InputChannel"},{"id":"-212145112","predicate":"inputChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputChannel"},{"id":"-1566230754","predicate":"peerChannel","params":[{"name":"channel_id","type":"long"}],"type":"Peer"},{"id":"666680316","predicate":"inputPeerChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-2107528095","predicate":"channel","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"left","type":"flags.2?true"},{"name":"broadcast","type":"flags.5?true"},{"name":"verified","type":"flags.7?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"restricted","type":"flags.9?true"},{"name":"signatures","type":"flags.11?true"},{"name":"min","type":"flags.12?true"},{"name":"scam","type":"flags.19?true"},{"name":"has_link","type":"flags.20?true"},{"name":"has_geo","type":"flags.21?true"},{"name":"slowmode_enabled","type":"flags.22?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"fake","type":"flags.25?true"},{"name":"gigagroup","type":"flags.26?true"},{"name":"noforwards","type":"flags.27?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.13?long"},{"name":"title","type":"string"},{"name":"username","type":"flags.6?string"},{"name":"photo","type":"ChatPhoto"},{"name":"date","type":"int"},{"name":"restriction_reason","type":"flags.9?Vector"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"banned_rights","type":"flags.15?ChatBannedRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"},{"name":"participants_count","type":"flags.17?int"}],"type":"Chat"},{"id":"399807445","predicate":"channelForbidden","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.5?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"until_date","type":"flags.16?int"}],"type":"Chat"},{"id":"2131196633","predicate":"contacts.resolvedPeer","params":[{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ResolvedPeer"},{"id":"-516145888","predicate":"channelFull","params":[{"name":"flags","type":"#"},{"name":"can_view_participants","type":"flags.3?true"},{"name":"can_set_username","type":"flags.6?true"},{"name":"can_set_stickers","type":"flags.7?true"},{"name":"hidden_prehistory","type":"flags.10?true"},{"name":"can_set_location","type":"flags.16?true"},{"name":"has_scheduled","type":"flags.19?true"},{"name":"can_view_stats","type":"flags.20?true"},{"name":"blocked","type":"flags.22?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants_count","type":"flags.0?int"},{"name":"admins_count","type":"flags.1?int"},{"name":"kicked_count","type":"flags.2?int"},{"name":"banned_count","type":"flags.2?int"},{"name":"online_count","type":"flags.13?int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"chat_photo","type":"Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.23?ExportedChatInvite"},{"name":"bot_info","type":"Vector"},{"name":"migrated_from_chat_id","type":"flags.4?long"},{"name":"migrated_from_max_id","type":"flags.4?int"},{"name":"pinned_msg_id","type":"flags.5?int"},{"name":"stickerset","type":"flags.8?StickerSet"},{"name":"available_min_id","type":"flags.9?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"linked_chat_id","type":"flags.14?long"},{"name":"location","type":"flags.15?ChannelLocation"},{"name":"slowmode_seconds","type":"flags.17?int"},{"name":"slowmode_next_send_date","type":"flags.18?int"},{"name":"stats_dc","type":"flags.12?int"},{"name":"pts","type":"int"},{"name":"call","type":"flags.21?InputGroupCall"},{"name":"ttl_period","type":"flags.24?int"},{"name":"pending_suggestions","type":"flags.25?Vector"},{"name":"groupcall_default_join_as","type":"flags.26?Peer"},{"name":"theme_emoticon","type":"flags.27?string"},{"name":"requests_pending","type":"flags.28?int"},{"name":"recent_requesters","type":"flags.28?Vector"},{"name":"default_send_as","type":"flags.29?Peer"},{"name":"available_reactions","type":"flags.30?Vector"}],"type":"ChatFull"},{"id":"182649427","predicate":"messageRange","params":[{"name":"min_id","type":"int"},{"name":"max_id","type":"int"}],"type":"MessageRange"},{"id":"1682413576","predicate":"messages.channelMessages","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"pts","type":"int"},{"name":"count","type":"int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"-1781355374","predicate":"messageActionChannelCreate","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"277713951","predicate":"updateChannelTooLong","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"pts","type":"flags.0?int"}],"type":"Update"},{"id":"1666927625","predicate":"updateChannel","params":[{"name":"channel_id","type":"long"}],"type":"Update"},{"id":"1656358105","predicate":"updateNewChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1842450928","predicate":"updateReadChannelInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"}],"type":"Update"},{"id":"-1020437742","predicate":"updateDeleteChannelMessages","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-232346616","predicate":"updateChannelMessageViews","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"views","type":"int"}],"type":"Update"},{"id":"1041346555","predicate":"updates.channelDifferenceEmpty","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"}],"type":"updates.ChannelDifference"},{"id":"-1531132162","predicate":"updates.channelDifferenceTooLong","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"timeout","type":"flags.1?int"},{"name":"dialog","type":"Dialog"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"543450958","predicate":"updates.channelDifference","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"},{"name":"new_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"-1798033689","predicate":"channelMessagesFilterEmpty","params":[],"type":"ChannelMessagesFilter"},{"id":"-847783593","predicate":"channelMessagesFilter","params":[{"name":"flags","type":"#"},{"name":"exclude_new_messages","type":"flags.1?true"},{"name":"ranges","type":"Vector"}],"type":"ChannelMessagesFilter"},{"id":"-1072953408","predicate":"channelParticipant","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"900251559","predicate":"channelParticipantSelf","params":[{"name":"flags","type":"#"},{"name":"via_request","type":"flags.0?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"803602899","predicate":"channelParticipantCreator","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.0?string"}],"type":"ChannelParticipant"},{"id":"-566281095","predicate":"channelParticipantsRecent","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1268741783","predicate":"channelParticipantsAdmins","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1548400251","predicate":"channelParticipantsKicked","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-1699676497","predicate":"channels.channelParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipants"},{"id":"-541588713","predicate":"channels.channelParticipant","params":[{"name":"participant","type":"ChannelParticipant"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipant"},{"id":"-462696732","predicate":"chatParticipantCreator","params":[{"name":"user_id","type":"long"}],"type":"ChatParticipant"},{"id":"-1600962725","predicate":"chatParticipantAdmin","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-674602590","predicate":"updateChatParticipantAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"is_admin","type":"Bool"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-519864430","predicate":"messageActionChatMigrateTo","params":[{"name":"channel_id","type":"long"}],"type":"MessageAction"},{"id":"-365344535","predicate":"messageActionChannelMigrateFrom","params":[{"name":"title","type":"string"},{"name":"chat_id","type":"long"}],"type":"MessageAction"},{"id":"-1328445861","predicate":"channelParticipantsBots","params":[],"type":"ChannelParticipantsFilter"},{"id":"2013922064","predicate":"help.termsOfService","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"id","type":"DataJSON"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"min_age_confirm","type":"flags.1?int"}],"type":"help.TermsOfService"},{"id":"1753886890","predicate":"updateNewStickerSet","params":[{"name":"stickerset","type":"messages.StickerSet"}],"type":"Update"},{"id":"196268545","predicate":"updateStickerSetsOrder","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Update"},{"id":"1135492588","predicate":"updateStickerSets","params":[],"type":"Update"},{"id":"-402498398","predicate":"messages.savedGifsNotModified","params":[],"type":"messages.SavedGifs"},{"id":"-2069878259","predicate":"messages.savedGifs","params":[{"name":"hash","type":"long"},{"name":"gifs","type":"Vector"}],"type":"messages.SavedGifs"},{"id":"-1821035490","predicate":"updateSavedGifs","params":[],"type":"Update"},{"id":"864077702","predicate":"inputBotInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1036876423","predicate":"inputBotInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-2000710887","predicate":"inputBotInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?InputWebDocument"},{"name":"content","type":"flags.5?InputWebDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1984755728","predicate":"botInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1937807902","predicate":"botInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"295067450","predicate":"botInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?WebDocument"},{"name":"content","type":"flags.5?WebDocument"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1803769784","predicate":"messages.botResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"query_id","type":"long"},{"name":"next_offset","type":"flags.1?string"},{"name":"switch_pm","type":"flags.2?InlineBotSwitchPM"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"users","type":"Vector"}],"type":"messages.BotResults"},{"id":"1232025500","predicate":"updateBotInlineQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"peer_type","type":"flags.1?InlineQueryPeerType"},{"name":"offset","type":"string"}],"type":"Update"},{"id":"317794823","predicate":"updateBotInlineSend","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"id","type":"string"},{"name":"msg_id","type":"flags.1?InputBotInlineMessageID"}],"type":"Update"},{"id":"1358283666","predicate":"inputMessagesFilterVoice","params":[],"type":"MessagesFilter"},{"id":"928101534","predicate":"inputMessagesFilterMusic","params":[],"type":"MessagesFilter"},{"id":"-1107622874","predicate":"inputPrivacyKeyChatInvite","params":[],"type":"InputPrivacyKey"},{"id":"1343122938","predicate":"privacyKeyChatInvite","params":[],"type":"PrivacyKey"},{"id":"1571494644","predicate":"exportedMessageLink","params":[{"name":"link","type":"string"},{"name":"html","type":"string"}],"type":"ExportedMessageLink"},{"id":"1601666510","predicate":"messageFwdHeader","params":[{"name":"flags","type":"#"},{"name":"imported","type":"flags.7?true"},{"name":"from_id","type":"flags.0?Peer"},{"name":"from_name","type":"flags.5?string"},{"name":"date","type":"int"},{"name":"channel_post","type":"flags.2?int"},{"name":"post_author","type":"flags.3?string"},{"name":"saved_from_peer","type":"flags.4?Peer"},{"name":"saved_from_msg_id","type":"flags.4?int"},{"name":"psa_type","type":"flags.6?string"}],"type":"MessageFwdHeader"},{"id":"457133559","predicate":"updateEditChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1799538451","predicate":"messageActionPinMessage","params":[],"type":"MessageAction"},{"id":"1923290508","predicate":"auth.codeTypeSms","params":[],"type":"auth.CodeType"},{"id":"1948046307","predicate":"auth.codeTypeCall","params":[],"type":"auth.CodeType"},{"id":"577556219","predicate":"auth.codeTypeFlashCall","params":[],"type":"auth.CodeType"},{"id":"1035688326","predicate":"auth.sentCodeTypeApp","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1073693790","predicate":"auth.sentCodeTypeSms","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"1398007207","predicate":"auth.sentCodeTypeCall","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1425815847","predicate":"auth.sentCodeTypeFlashCall","params":[{"name":"pattern","type":"string"}],"type":"auth.SentCodeType"},{"id":"629866245","predicate":"keyboardButtonUrl","params":[{"name":"text","type":"string"},{"name":"url","type":"string"}],"type":"KeyboardButton"},{"id":"901503851","predicate":"keyboardButtonCallback","params":[{"name":"flags","type":"#"},{"name":"requires_password","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"data","type":"bytes"}],"type":"KeyboardButton"},{"id":"-1318425559","predicate":"keyboardButtonRequestPhone","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-59151553","predicate":"keyboardButtonRequestGeoLocation","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"90744648","predicate":"keyboardButtonSwitchInline","params":[{"name":"flags","type":"#"},{"name":"same_peer","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"query","type":"string"}],"type":"KeyboardButton"},{"id":"1218642516","predicate":"replyInlineMarkup","params":[{"name":"rows","type":"Vector"}],"type":"ReplyMarkup"},{"id":"911761060","predicate":"messages.botCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"has_url","type":"flags.3?true"},{"name":"native_ui","type":"flags.4?true"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"messages.BotCallbackAnswer"},{"id":"-1177566067","predicate":"updateBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"649453030","predicate":"messages.messageEditData","params":[{"name":"flags","type":"#"},{"name":"caption","type":"flags.0?true"}],"type":"messages.MessageEditData"},{"id":"-469536605","predicate":"updateEditMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1768777083","predicate":"inputBotInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1098628881","predicate":"inputBotInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-1494368259","predicate":"inputBotInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"85477117","predicate":"botInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1970903652","predicate":"botInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"416402882","predicate":"botInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1462213465","predicate":"inputBotInlineResultPhoto","params":[{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"InputPhoto"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"-459324","predicate":"inputBotInlineResultDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"document","type":"InputDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"400266251","predicate":"botInlineMediaResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"flags.0?Photo"},{"name":"document","type":"flags.1?Document"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1995686519","predicate":"inputBotInlineMessageID","params":[{"name":"dc_id","type":"int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"1763610706","predicate":"updateInlineBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"msg_id","type":"InputBotInlineMessageID"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"1008755359","predicate":"inlineBotSwitchPM","params":[{"name":"text","type":"string"},{"name":"start_param","type":"string"}],"type":"InlineBotSwitchPM"},{"id":"863093588","predicate":"messages.peerDialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"messages.PeerDialogs"},{"id":"-305282981","predicate":"topPeer","params":[{"name":"peer","type":"Peer"},{"name":"rating","type":"double"}],"type":"TopPeer"},{"id":"-1419371685","predicate":"topPeerCategoryBotsPM","params":[],"type":"TopPeerCategory"},{"id":"344356834","predicate":"topPeerCategoryBotsInline","params":[],"type":"TopPeerCategory"},{"id":"104314861","predicate":"topPeerCategoryCorrespondents","params":[],"type":"TopPeerCategory"},{"id":"-1122524854","predicate":"topPeerCategoryGroups","params":[],"type":"TopPeerCategory"},{"id":"371037736","predicate":"topPeerCategoryChannels","params":[],"type":"TopPeerCategory"},{"id":"-75283823","predicate":"topPeerCategoryPeers","params":[{"name":"category","type":"TopPeerCategory"},{"name":"count","type":"int"},{"name":"peers","type":"Vector"}],"type":"TopPeerCategoryPeers"},{"id":"-567906571","predicate":"contacts.topPeersNotModified","params":[],"type":"contacts.TopPeers"},{"id":"1891070632","predicate":"contacts.topPeers","params":[{"name":"categories","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.TopPeers"},{"id":"-595914432","predicate":"messageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"long"}],"type":"MessageEntity"},{"id":"546203849","predicate":"inputMessageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"MessageEntity"},{"id":"975236280","predicate":"inputMessagesFilterChatPhotos","params":[],"type":"MessagesFilter"},{"id":"-1218471511","predicate":"updateReadChannelOutbox","params":[{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"}],"type":"Update"},{"id":"-299124375","predicate":"updateDraftMessage","params":[{"name":"peer","type":"Peer"},{"name":"draft","type":"DraftMessage"}],"type":"Update"},{"id":"453805082","predicate":"draftMessageEmpty","params":[{"name":"flags","type":"#"},{"name":"date","type":"flags.0?int"}],"type":"DraftMessage"},{"id":"-40996577","predicate":"draftMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"},{"name":"date","type":"int"}],"type":"DraftMessage"},{"id":"-1615153660","predicate":"messageActionHistoryClear","params":[],"type":"MessageAction"},{"id":"-958657434","predicate":"messages.featuredStickersNotModified","params":[{"name":"count","type":"int"}],"type":"messages.FeaturedStickers"},{"id":"-2067782896","predicate":"messages.featuredStickers","params":[{"name":"hash","type":"long"},{"name":"count","type":"int"},{"name":"sets","type":"Vector"},{"name":"unread","type":"Vector"}],"type":"messages.FeaturedStickers"},{"id":"1461528386","predicate":"updateReadFeaturedStickers","params":[],"type":"Update"},{"id":"186120336","predicate":"messages.recentStickersNotModified","params":[],"type":"messages.RecentStickers"},{"id":"-1999405994","predicate":"messages.recentStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"},{"name":"dates","type":"Vector"}],"type":"messages.RecentStickers"},{"id":"-1706939360","predicate":"updateRecentStickers","params":[],"type":"Update"},{"id":"1338747336","predicate":"messages.archivedStickers","params":[{"name":"count","type":"int"},{"name":"sets","type":"Vector"}],"type":"messages.ArchivedStickers"},{"id":"946083368","predicate":"messages.stickerSetInstallResultSuccess","params":[],"type":"messages.StickerSetInstallResult"},{"id":"904138920","predicate":"messages.stickerSetInstallResultArchive","params":[{"name":"sets","type":"Vector"}],"type":"messages.StickerSetInstallResult"},{"id":"1678812626","predicate":"stickerSetCovered","params":[{"name":"set","type":"StickerSet"},{"name":"cover","type":"Document"}],"type":"StickerSetCovered"},{"id":"-1574314746","predicate":"updateConfig","params":[],"type":"Update"},{"id":"861169551","predicate":"updatePtsChanged","params":[],"type":"Update"},{"id":"-440664550","predicate":"inputMediaPhotoExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-78455655","predicate":"inputMediaDocumentExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"872932635","predicate":"stickerSetMultiCovered","params":[{"name":"set","type":"StickerSet"},{"name":"covers","type":"Vector"}],"type":"StickerSetCovered"},{"id":"-1361650766","predicate":"maskCoords","params":[{"name":"n","type":"int"},{"name":"x","type":"double"},{"name":"y","type":"double"},{"name":"zoom","type":"double"}],"type":"MaskCoords"},{"id":"-1744710921","predicate":"documentAttributeHasStickers","params":[],"type":"DocumentAttribute"},{"id":"1251549527","predicate":"inputStickeredMediaPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputStickeredMedia"},{"id":"70813275","predicate":"inputStickeredMediaDocument","params":[{"name":"id","type":"InputDocument"}],"type":"InputStickeredMedia"},{"id":"-1107729093","predicate":"game","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"short_name","type":"string"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"Photo"},{"name":"document","type":"flags.0?Document"}],"type":"Game"},{"id":"1336154098","predicate":"inputBotInlineResultGame","params":[{"name":"id","type":"string"},{"name":"short_name","type":"string"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1262639204","predicate":"inputBotInlineMessageGame","params":[{"name":"flags","type":"#"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-38694904","predicate":"messageMediaGame","params":[{"name":"game","type":"Game"}],"type":"MessageMedia"},{"id":"-750828557","predicate":"inputMediaGame","params":[{"name":"id","type":"InputGame"}],"type":"InputMedia"},{"id":"53231223","predicate":"inputGameID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGame"},{"id":"-1020139510","predicate":"inputGameShortName","params":[{"name":"bot_id","type":"InputUser"},{"name":"short_name","type":"string"}],"type":"InputGame"},{"id":"1358175439","predicate":"keyboardButtonGame","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-1834538890","predicate":"messageActionGameScore","params":[{"name":"game_id","type":"long"},{"name":"score","type":"int"}],"type":"MessageAction"},{"id":"1940093419","predicate":"highScore","params":[{"name":"pos","type":"int"},{"name":"user_id","type":"long"},{"name":"score","type":"int"}],"type":"HighScore"},{"id":"-1707344487","predicate":"messages.highScores","params":[{"name":"scores","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.HighScores"},{"id":"1258196845","predicate":"updates.differenceTooLong","params":[{"name":"pts","type":"int"}],"type":"updates.Difference"},{"id":"791390623","predicate":"updateChannelWebPage","params":[{"name":"channel_id","type":"long"},{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1663561404","predicate":"messages.chatsSlice","params":[{"name":"count","type":"int"},{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-599948721","predicate":"textEmpty","params":[],"type":"RichText"},{"id":"1950782688","predicate":"textPlain","params":[{"name":"text","type":"string"}],"type":"RichText"},{"id":"1730456516","predicate":"textBold","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-653089380","predicate":"textItalic","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1054465340","predicate":"textUnderline","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1678197867","predicate":"textStrike","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1816074681","predicate":"textFixed","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1009288385","predicate":"textUrl","params":[{"name":"text","type":"RichText"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"}],"type":"RichText"},{"id":"-564523562","predicate":"textEmail","params":[{"name":"text","type":"RichText"},{"name":"email","type":"string"}],"type":"RichText"},{"id":"2120376535","predicate":"textConcat","params":[{"name":"texts","type":"Vector"}],"type":"RichText"},{"id":"324435594","predicate":"pageBlockUnsupported","params":[],"type":"PageBlock"},{"id":"1890305021","predicate":"pageBlockTitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1879401953","predicate":"pageBlockSubtitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1162877472","predicate":"pageBlockAuthorDate","params":[{"name":"author","type":"RichText"},{"name":"published_date","type":"int"}],"type":"PageBlock"},{"id":"-1076861716","predicate":"pageBlockHeader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-248793375","predicate":"pageBlockSubheader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"1182402406","predicate":"pageBlockParagraph","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1066346178","predicate":"pageBlockPreformatted","params":[{"name":"text","type":"RichText"},{"name":"language","type":"string"}],"type":"PageBlock"},{"id":"1216809369","predicate":"pageBlockFooter","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-618614392","predicate":"pageBlockDivider","params":[],"type":"PageBlock"},{"id":"-837994576","predicate":"pageBlockAnchor","params":[{"name":"name","type":"string"}],"type":"PageBlock"},{"id":"-454524911","predicate":"pageBlockList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"641563686","predicate":"pageBlockBlockquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"1329878739","predicate":"pageBlockPullquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"391759200","predicate":"pageBlockPhoto","params":[{"name":"flags","type":"#"},{"name":"photo_id","type":"long"},{"name":"caption","type":"PageCaption"},{"name":"url","type":"flags.0?string"},{"name":"webpage_id","type":"flags.0?long"}],"type":"PageBlock"},{"id":"2089805750","predicate":"pageBlockVideo","params":[{"name":"flags","type":"#"},{"name":"autoplay","type":"flags.0?true"},{"name":"loop","type":"flags.1?true"},{"name":"video_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"972174080","predicate":"pageBlockCover","params":[{"name":"cover","type":"PageBlock"}],"type":"PageBlock"},{"id":"-1468953147","predicate":"pageBlockEmbed","params":[{"name":"flags","type":"#"},{"name":"full_width","type":"flags.0?true"},{"name":"allow_scrolling","type":"flags.3?true"},{"name":"url","type":"flags.1?string"},{"name":"html","type":"flags.2?string"},{"name":"poster_photo_id","type":"flags.4?long"},{"name":"w","type":"flags.5?int"},{"name":"h","type":"flags.5?int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-229005301","predicate":"pageBlockEmbedPost","params":[{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"author_photo_id","type":"long"},{"name":"author","type":"string"},{"name":"date","type":"int"},{"name":"blocks","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1705048653","predicate":"pageBlockCollage","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"52401552","predicate":"pageBlockSlideshow","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1930545681","predicate":"webPageNotModified","params":[{"name":"flags","type":"#"},{"name":"cached_page_views","type":"flags.0?int"}],"type":"WebPage"},{"id":"-88417185","predicate":"inputPrivacyKeyPhoneCall","params":[],"type":"InputPrivacyKey"},{"id":"1030105979","predicate":"privacyKeyPhoneCall","params":[],"type":"PrivacyKey"},{"id":"-580219064","predicate":"sendMessageGamePlayAction","params":[],"type":"SendMessageAction"},{"id":"-2048646399","predicate":"phoneCallDiscardReasonMissed","params":[],"type":"PhoneCallDiscardReason"},{"id":"-527056480","predicate":"phoneCallDiscardReasonDisconnect","params":[],"type":"PhoneCallDiscardReason"},{"id":"1471006352","predicate":"phoneCallDiscardReasonHangup","params":[],"type":"PhoneCallDiscardReason"},{"id":"-84416311","predicate":"phoneCallDiscardReasonBusy","params":[],"type":"PhoneCallDiscardReason"},{"id":"1852826908","predicate":"updateDialogPinned","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-99664734","predicate":"updatePinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.1?int"},{"name":"order","type":"flags.0?Vector"}],"type":"Update"},{"id":"2104790276","predicate":"dataJSON","params":[{"name":"data","type":"string"}],"type":"DataJSON"},{"id":"-2095595325","predicate":"updateBotWebhookJSON","params":[{"name":"data","type":"DataJSON"}],"type":"Update"},{"id":"-1684914010","predicate":"updateBotWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"},{"name":"timeout","type":"int"}],"type":"Update"},{"id":"-886477832","predicate":"labeledPrice","params":[{"name":"label","type":"string"},{"name":"amount","type":"long"}],"type":"LabeledPrice"},{"id":"215516896","predicate":"invoice","params":[{"name":"flags","type":"#"},{"name":"test","type":"flags.0?true"},{"name":"name_requested","type":"flags.1?true"},{"name":"phone_requested","type":"flags.2?true"},{"name":"email_requested","type":"flags.3?true"},{"name":"shipping_address_requested","type":"flags.4?true"},{"name":"flexible","type":"flags.5?true"},{"name":"phone_to_provider","type":"flags.6?true"},{"name":"email_to_provider","type":"flags.7?true"},{"name":"currency","type":"string"},{"name":"prices","type":"Vector"},{"name":"max_tip_amount","type":"flags.8?long"},{"name":"suggested_tip_amounts","type":"flags.8?Vector"}],"type":"Invoice"},{"id":"-646342540","predicate":"inputMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"start_param","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-368917890","predicate":"paymentCharge","params":[{"name":"id","type":"string"},{"name":"provider_charge_id","type":"string"}],"type":"PaymentCharge"},{"id":"-1892568281","predicate":"messageActionPaymentSentMe","params":[{"name":"flags","type":"#"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"charge","type":"PaymentCharge"}],"type":"MessageAction"},{"id":"-2074799289","predicate":"messageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"receipt_msg_id","type":"flags.2?int"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"start_param","type":"string"}],"type":"MessageMedia"},{"id":"512535275","predicate":"postAddress","params":[{"name":"street_line1","type":"string"},{"name":"street_line2","type":"string"},{"name":"city","type":"string"},{"name":"state","type":"string"},{"name":"country_iso2","type":"string"},{"name":"post_code","type":"string"}],"type":"PostAddress"},{"id":"-1868808300","predicate":"paymentRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"name","type":"flags.0?string"},{"name":"phone","type":"flags.1?string"},{"name":"email","type":"flags.2?string"},{"name":"shipping_address","type":"flags.3?PostAddress"}],"type":"PaymentRequestedInfo"},{"id":"-1344716869","predicate":"keyboardButtonBuy","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1080663248","predicate":"messageActionPaymentSent","params":[{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"MessageAction"},{"id":"-842892769","predicate":"paymentSavedCredentialsCard","params":[{"name":"id","type":"string"},{"name":"title","type":"string"}],"type":"PaymentSavedCredentials"},{"id":"475467473","predicate":"webDocument","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"-1678949555","predicate":"inputWebDocument","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"InputWebDocument"},{"id":"-1036396922","predicate":"inputWebFileLocation","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"}],"type":"InputWebFileLocation"},{"id":"568808380","predicate":"upload.webFile","params":[{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"file_type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.WebFile"},{"id":"378828315","predicate":"payments.paymentForm","params":[{"name":"flags","type":"#"},{"name":"can_save_credentials","type":"flags.2?true"},{"name":"password_missing","type":"flags.3?true"},{"name":"form_id","type":"long"},{"name":"bot_id","type":"long"},{"name":"invoice","type":"Invoice"},{"name":"provider_id","type":"long"},{"name":"url","type":"string"},{"name":"native_provider","type":"flags.4?string"},{"name":"native_params","type":"flags.4?DataJSON"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"},{"name":"saved_credentials","type":"flags.1?PaymentSavedCredentials"},{"name":"users","type":"Vector"}],"type":"payments.PaymentForm"},{"id":"-784000893","predicate":"payments.validatedRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"id","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"payments.ValidatedRequestedInfo"},{"id":"1314881805","predicate":"payments.paymentResult","params":[{"name":"updates","type":"Updates"}],"type":"payments.PaymentResult"},{"id":"1891958275","predicate":"payments.paymentReceipt","params":[{"name":"flags","type":"#"},{"name":"date","type":"int"},{"name":"bot_id","type":"long"},{"name":"provider_id","type":"long"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.2?WebDocument"},{"name":"invoice","type":"Invoice"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping","type":"flags.1?ShippingOption"},{"name":"tip_amount","type":"flags.3?long"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"credentials_title","type":"string"},{"name":"users","type":"Vector"}],"type":"payments.PaymentReceipt"},{"id":"-74456004","predicate":"payments.savedInfo","params":[{"name":"flags","type":"#"},{"name":"has_saved_credentials","type":"flags.1?true"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"}],"type":"payments.SavedInfo"},{"id":"-1056001329","predicate":"inputPaymentCredentialsSaved","params":[{"name":"id","type":"string"},{"name":"tmp_password","type":"bytes"}],"type":"InputPaymentCredentials"},{"id":"873977640","predicate":"inputPaymentCredentials","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-614138572","predicate":"account.tmpPassword","params":[{"name":"tmp_password","type":"bytes"},{"name":"valid_until","type":"int"}],"type":"account.TmpPassword"},{"id":"-1239335713","predicate":"shippingOption","params":[{"name":"id","type":"string"},{"name":"title","type":"string"},{"name":"prices","type":"Vector"}],"type":"ShippingOption"},{"id":"-1246823043","predicate":"updateBotShippingQuery","params":[{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"shipping_address","type":"PostAddress"}],"type":"Update"},{"id":"-1934976362","predicate":"updateBotPrecheckoutQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"Update"},{"id":"-6249322","predicate":"inputStickerSetItem","params":[{"name":"flags","type":"#"},{"name":"document","type":"InputDocument"},{"name":"emoji","type":"string"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"InputStickerSetItem"},{"id":"-1425052898","predicate":"updatePhoneCall","params":[{"name":"phone_call","type":"PhoneCall"}],"type":"Update"},{"id":"506920429","predicate":"inputPhoneCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPhoneCall"},{"id":"1399245077","predicate":"phoneCallEmpty","params":[{"name":"id","type":"long"}],"type":"PhoneCall"},{"id":"-987599081","predicate":"phoneCallWaiting","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"receive_date","type":"flags.0?int"}],"type":"PhoneCall"},{"id":"347139340","predicate":"phoneCallRequested","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"912311057","predicate":"phoneCallAccepted","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"-1770029977","predicate":"phoneCall","params":[{"name":"flags","type":"#"},{"name":"p2p_allowed","type":"flags.5?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"connections","type":"Vector"},{"name":"start_date","type":"int"}],"type":"PhoneCall"},{"id":"1355435489","predicate":"phoneCallDiscarded","params":[{"name":"flags","type":"#"},{"name":"need_rating","type":"flags.2?true"},{"name":"need_debug","type":"flags.3?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"PhoneCall"},{"id":"-1655957568","predicate":"phoneConnection","params":[{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"peer_tag","type":"bytes"}],"type":"PhoneConnection"},{"id":"-58224696","predicate":"phoneCallProtocol","params":[{"name":"flags","type":"#"},{"name":"udp_p2p","type":"flags.0?true"},{"name":"udp_reflector","type":"flags.1?true"},{"name":"min_layer","type":"int"},{"name":"max_layer","type":"int"},{"name":"library_versions","type":"Vector"}],"type":"PhoneCallProtocol"},{"id":"-326966976","predicate":"phone.phoneCall","params":[{"name":"phone_call","type":"PhoneCall"},{"name":"users","type":"Vector"}],"type":"phone.PhoneCall"},{"id":"-2134272152","predicate":"inputMessagesFilterPhoneCalls","params":[{"name":"flags","type":"#"},{"name":"missed","type":"flags.0?true"}],"type":"MessagesFilter"},{"id":"-2132731265","predicate":"messageActionPhoneCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.2?true"},{"name":"call_id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"MessageAction"},{"id":"2054952868","predicate":"inputMessagesFilterRoundVoice","params":[],"type":"MessagesFilter"},{"id":"-1253451181","predicate":"inputMessagesFilterRoundVideo","params":[],"type":"MessagesFilter"},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction"},{"id":"608050278","predicate":"sendMessageUploadRoundAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-242427324","predicate":"upload.fileCdnRedirect","params":[{"name":"dc_id","type":"int"},{"name":"file_token","type":"bytes"},{"name":"encryption_key","type":"bytes"},{"name":"encryption_iv","type":"bytes"},{"name":"file_hashes","type":"Vector"}],"type":"upload.File"},{"id":"-290921362","predicate":"upload.cdnFileReuploadNeeded","params":[{"name":"request_token","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-1449145777","predicate":"upload.cdnFile","params":[{"name":"bytes","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-914167110","predicate":"cdnPublicKey","params":[{"name":"dc_id","type":"int"},{"name":"public_key","type":"string"}],"type":"CdnPublicKey"},{"id":"1462101002","predicate":"cdnConfig","params":[{"name":"public_keys","type":"Vector"}],"type":"CdnConfig"},{"id":"-283684427","predicate":"pageBlockChannel","params":[{"name":"channel","type":"Chat"}],"type":"PageBlock"},{"id":"-892239370","predicate":"langPackString","params":[{"name":"key","type":"string"},{"name":"value","type":"string"}],"type":"LangPackString"},{"id":"1816636575","predicate":"langPackStringPluralized","params":[{"name":"flags","type":"#"},{"name":"key","type":"string"},{"name":"zero_value","type":"flags.0?string"},{"name":"one_value","type":"flags.1?string"},{"name":"two_value","type":"flags.2?string"},{"name":"few_value","type":"flags.3?string"},{"name":"many_value","type":"flags.4?string"},{"name":"other_value","type":"string"}],"type":"LangPackString"},{"id":"695856818","predicate":"langPackStringDeleted","params":[{"name":"key","type":"string"}],"type":"LangPackString"},{"id":"-209337866","predicate":"langPackDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"strings","type":"Vector"}],"type":"LangPackDifference"},{"id":"-288727837","predicate":"langPackLanguage","params":[{"name":"flags","type":"#"},{"name":"official","type":"flags.0?true"},{"name":"rtl","type":"flags.2?true"},{"name":"beta","type":"flags.3?true"},{"name":"name","type":"string"},{"name":"native_name","type":"string"},{"name":"lang_code","type":"string"},{"name":"base_lang_code","type":"flags.1?string"},{"name":"plural_code","type":"string"},{"name":"strings_count","type":"int"},{"name":"translated_count","type":"int"},{"name":"translations_url","type":"string"}],"type":"LangPackLanguage"},{"id":"1180041828","predicate":"updateLangPackTooLong","params":[{"name":"lang_code","type":"string"}],"type":"Update"},{"id":"1442983757","predicate":"updateLangPack","params":[{"name":"difference","type":"LangPackDifference"}],"type":"Update"},{"id":"885242707","predicate":"channelParticipantAdmin","params":[{"name":"flags","type":"#"},{"name":"can_edit","type":"flags.0?true"},{"name":"self","type":"flags.1?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"flags.1?long"},{"name":"promoted_by","type":"long"},{"name":"date","type":"int"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.2?string"}],"type":"ChannelParticipant"},{"id":"1844969806","predicate":"channelParticipantBanned","params":[{"name":"flags","type":"#"},{"name":"left","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"kicked_by","type":"long"},{"name":"date","type":"int"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"ChannelParticipant"},{"id":"338142689","predicate":"channelParticipantsBanned","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"106343499","predicate":"channelParticipantsSearch","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-421545947","predicate":"channelAdminLogEventActionChangeTitle","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1427671598","predicate":"channelAdminLogEventActionChangeAbout","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1783299128","predicate":"channelAdminLogEventActionChangeUsername","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1129042607","predicate":"channelAdminLogEventActionChangePhoto","params":[{"name":"prev_photo","type":"Photo"},{"name":"new_photo","type":"Photo"}],"type":"ChannelAdminLogEventAction"},{"id":"460916654","predicate":"channelAdminLogEventActionToggleInvites","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"648939889","predicate":"channelAdminLogEventActionToggleSignatures","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-370660328","predicate":"channelAdminLogEventActionUpdatePinned","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1889215493","predicate":"channelAdminLogEventActionEditMessage","params":[{"name":"prev_message","type":"Message"},{"name":"new_message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1121994683","predicate":"channelAdminLogEventActionDeleteMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"405815507","predicate":"channelAdminLogEventActionParticipantJoin","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-124291086","predicate":"channelAdminLogEventActionParticipantLeave","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-484690728","predicate":"channelAdminLogEventActionParticipantInvite","params":[{"name":"participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-422036098","predicate":"channelAdminLogEventActionParticipantToggleBan","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-714643696","predicate":"channelAdminLogEventActionParticipantToggleAdmin","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"531458253","predicate":"channelAdminLogEvent","params":[{"name":"id","type":"long"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"action","type":"ChannelAdminLogEventAction"}],"type":"ChannelAdminLogEvent"},{"id":"-309659827","predicate":"channels.adminLogResults","params":[{"name":"events","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.AdminLogResults"},{"id":"-368018716","predicate":"channelAdminLogEventsFilter","params":[{"name":"flags","type":"#"},{"name":"join","type":"flags.0?true"},{"name":"leave","type":"flags.1?true"},{"name":"invite","type":"flags.2?true"},{"name":"ban","type":"flags.3?true"},{"name":"unban","type":"flags.4?true"},{"name":"kick","type":"flags.5?true"},{"name":"unkick","type":"flags.6?true"},{"name":"promote","type":"flags.7?true"},{"name":"demote","type":"flags.8?true"},{"name":"info","type":"flags.9?true"},{"name":"settings","type":"flags.10?true"},{"name":"pinned","type":"flags.11?true"},{"name":"edit","type":"flags.12?true"},{"name":"delete","type":"flags.13?true"},{"name":"group_call","type":"flags.14?true"},{"name":"invites","type":"flags.15?true"},{"name":"send","type":"flags.16?true"}],"type":"ChannelAdminLogEventsFilter"},{"id":"511092620","predicate":"topPeerCategoryPhoneCalls","params":[],"type":"TopPeerCategory"},{"id":"-2143067670","predicate":"pageBlockAudio","params":[{"name":"audio_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1558266229","predicate":"popularContact","params":[{"name":"client_id","type":"long"},{"name":"importers","type":"int"}],"type":"PopularContact"},{"id":"1200788123","predicate":"messageActionScreenshotTaken","params":[],"type":"MessageAction"},{"id":"-1634752813","predicate":"messages.favedStickersNotModified","params":[],"type":"messages.FavedStickers"},{"id":"750063767","predicate":"messages.favedStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"}],"type":"messages.FavedStickers"},{"id":"-451831443","predicate":"updateFavedStickers","params":[],"type":"Update"},{"id":"1153291573","predicate":"updateChannelReadMessagesContents","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-1040652646","predicate":"inputMessagesFilterMyMentions","params":[],"type":"MessagesFilter"},{"id":"1887741886","predicate":"updateContactsReset","params":[],"type":"Update"},{"id":"-1312568665","predicate":"channelAdminLogEventActionChangeStickerSet","params":[{"name":"prev_stickerset","type":"InputStickerSet"},{"name":"new_stickerset","type":"InputStickerSet"}],"type":"ChannelAdminLogEventAction"},{"id":"-85549226","predicate":"messageActionCustomAction","params":[{"name":"message","type":"string"}],"type":"MessageAction"},{"id":"178373535","predicate":"inputPaymentCredentialsApplePay","params":[{"name":"payment_data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-419271411","predicate":"inputMessagesFilterGeo","params":[],"type":"MessagesFilter"},{"id":"-530392189","predicate":"inputMessagesFilterContacts","params":[],"type":"MessagesFilter"},{"id":"-1304443240","predicate":"updateChannelAvailableMessages","params":[{"name":"channel_id","type":"long"},{"name":"available_min_id","type":"int"}],"type":"Update"},{"id":"1599903217","predicate":"channelAdminLogEventActionTogglePreHistoryHidden","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1759532989","predicate":"inputMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"stopped","type":"flags.0?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.2?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"}],"type":"InputMedia"},{"id":"-1186937242","predicate":"messageMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"int"},{"name":"proximity_notification_radius","type":"flags.1?int"}],"type":"MessageMedia"},{"id":"1189204285","predicate":"recentMeUrlUnknown","params":[{"name":"url","type":"string"}],"type":"RecentMeUrl"},{"id":"-1188296222","predicate":"recentMeUrlUser","params":[{"name":"url","type":"string"},{"name":"user_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-1294306862","predicate":"recentMeUrlChat","params":[{"name":"url","type":"string"},{"name":"chat_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-347535331","predicate":"recentMeUrlChatInvite","params":[{"name":"url","type":"string"},{"name":"chat_invite","type":"ChatInvite"}],"type":"RecentMeUrl"},{"id":"-1140172836","predicate":"recentMeUrlStickerSet","params":[{"name":"url","type":"string"},{"name":"set","type":"StickerSetCovered"}],"type":"RecentMeUrl"},{"id":"235081943","predicate":"help.recentMeUrls","params":[{"name":"urls","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"help.RecentMeUrls"},{"id":"-266911767","predicate":"channels.channelParticipantsNotModified","params":[],"type":"channels.ChannelParticipants"},{"id":"1951620897","predicate":"messages.messagesNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Messages"},{"id":"482797855","predicate":"inputSingleMedia","params":[{"name":"flags","type":"#"},{"name":"media","type":"InputMedia"},{"name":"random_id","type":"long"},{"name":"message","type":"string"},{"name":"entities","type":"flags.0?Vector"}],"type":"InputSingleMedia"},{"id":"-1493633966","predicate":"webAuthorization","params":[{"name":"hash","type":"long"},{"name":"bot_id","type":"long"},{"name":"domain","type":"string"},{"name":"browser","type":"string"},{"name":"platform","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"region","type":"string"}],"type":"WebAuthorization"},{"id":"-313079300","predicate":"account.webAuthorizations","params":[{"name":"authorizations","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.WebAuthorizations"},{"id":"-1502174430","predicate":"inputMessageID","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-1160215659","predicate":"inputMessageReplyTo","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-2037963464","predicate":"inputMessagePinned","params":[],"type":"InputMessage"},{"id":"-1687559349","predicate":"messageEntityPhone","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1280209983","predicate":"messageEntityCashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1410748418","predicate":"messageActionBotAllowed","params":[{"name":"domain","type":"string"}],"type":"MessageAction"},{"id":"-55902537","predicate":"inputDialogPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputDialogPeer"},{"id":"-445792507","predicate":"dialogPeer","params":[{"name":"peer","type":"Peer"}],"type":"DialogPeer"},{"id":"223655517","predicate":"messages.foundStickerSetsNotModified","params":[],"type":"messages.FoundStickerSets"},{"id":"-1963942446","predicate":"messages.foundStickerSets","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.FoundStickerSets"},{"id":"1648543603","predicate":"fileHash","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"bytes"}],"type":"FileHash"},{"id":"-104284986","predicate":"webDocumentNoProxy","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"1968737087","predicate":"inputClientProxy","params":[{"name":"address","type":"string"},{"name":"port","type":"int"}],"type":"InputClientProxy"},{"id":"-483352705","predicate":"help.termsOfServiceUpdateEmpty","params":[{"name":"expires","type":"int"}],"type":"help.TermsOfServiceUpdate"},{"id":"686618977","predicate":"help.termsOfServiceUpdate","params":[{"name":"expires","type":"int"},{"name":"terms_of_service","type":"help.TermsOfService"}],"type":"help.TermsOfServiceUpdate"},{"id":"859091184","predicate":"inputSecureFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"InputSecureFile"},{"id":"1399317950","predicate":"inputSecureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputSecureFile"},{"id":"-876089816","predicate":"inputSecureFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"1679398724","predicate":"secureFileEmpty","params":[],"type":"SecureFile"},{"id":"-534283678","predicate":"secureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"date","type":"int"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureFile"},{"id":"-1964327229","predicate":"secureData","params":[{"name":"data","type":"bytes"},{"name":"data_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureData"},{"id":"2103482845","predicate":"securePlainPhone","params":[{"name":"phone","type":"string"}],"type":"SecurePlainData"},{"id":"569137759","predicate":"securePlainEmail","params":[{"name":"email","type":"string"}],"type":"SecurePlainData"},{"id":"-1658158621","predicate":"secureValueTypePersonalDetails","params":[],"type":"SecureValueType"},{"id":"1034709504","predicate":"secureValueTypePassport","params":[],"type":"SecureValueType"},{"id":"115615172","predicate":"secureValueTypeDriverLicense","params":[],"type":"SecureValueType"},{"id":"-1596951477","predicate":"secureValueTypeIdentityCard","params":[],"type":"SecureValueType"},{"id":"-1717268701","predicate":"secureValueTypeInternalPassport","params":[],"type":"SecureValueType"},{"id":"-874308058","predicate":"secureValueTypeAddress","params":[],"type":"SecureValueType"},{"id":"-63531698","predicate":"secureValueTypeUtilityBill","params":[],"type":"SecureValueType"},{"id":"-1995211763","predicate":"secureValueTypeBankStatement","params":[],"type":"SecureValueType"},{"id":"-1954007928","predicate":"secureValueTypeRentalAgreement","params":[],"type":"SecureValueType"},{"id":"-1713143702","predicate":"secureValueTypePassportRegistration","params":[],"type":"SecureValueType"},{"id":"-368907213","predicate":"secureValueTypeTemporaryRegistration","params":[],"type":"SecureValueType"},{"id":"-1289704741","predicate":"secureValueTypePhone","params":[],"type":"SecureValueType"},{"id":"-1908627474","predicate":"secureValueTypeEmail","params":[],"type":"SecureValueType"},{"id":"411017418","predicate":"secureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?SecureFile"},{"name":"reverse_side","type":"flags.2?SecureFile"},{"name":"selfie","type":"flags.3?SecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"},{"name":"hash","type":"bytes"}],"type":"SecureValue"},{"id":"-618540889","predicate":"inputSecureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?InputSecureFile"},{"name":"reverse_side","type":"flags.2?InputSecureFile"},{"name":"selfie","type":"flags.3?InputSecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"}],"type":"InputSecureValue"},{"id":"-316748368","predicate":"secureValueHash","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"}],"type":"SecureValueHash"},{"id":"-391902247","predicate":"secureValueErrorData","params":[{"name":"type","type":"SecureValueType"},{"name":"data_hash","type":"bytes"},{"name":"field","type":"string"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"12467706","predicate":"secureValueErrorFrontSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2037765467","predicate":"secureValueErrorReverseSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-449327402","predicate":"secureValueErrorSelfie","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"2054162547","predicate":"secureValueErrorFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"1717706985","predicate":"secureValueErrorFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"871426631","predicate":"secureCredentialsEncrypted","params":[{"name":"data","type":"bytes"},{"name":"hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureCredentialsEncrypted"},{"id":"-1389486888","predicate":"account.authorizationForm","params":[{"name":"flags","type":"#"},{"name":"required_types","type":"Vector"},{"name":"values","type":"Vector"},{"name":"errors","type":"Vector"},{"name":"users","type":"Vector"},{"name":"privacy_policy_url","type":"flags.0?string"}],"type":"account.AuthorizationForm"},{"id":"-2128640689","predicate":"account.sentEmailCode","params":[{"name":"email_pattern","type":"string"},{"name":"length","type":"int"}],"type":"account.SentEmailCode"},{"id":"455635795","predicate":"messageActionSecureValuesSentMe","params":[{"name":"values","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"MessageAction"},{"id":"-648257196","predicate":"messageActionSecureValuesSent","params":[{"name":"types","type":"Vector"}],"type":"MessageAction"},{"id":"1722786150","predicate":"help.deepLinkInfoEmpty","params":[],"type":"help.DeepLinkInfo"},{"id":"1783556146","predicate":"help.deepLinkInfo","params":[{"name":"flags","type":"#"},{"name":"update_app","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"help.DeepLinkInfo"},{"id":"289586518","predicate":"savedPhoneContact","params":[{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"date","type":"int"}],"type":"SavedContact"},{"id":"1304052993","predicate":"account.takeout","params":[{"name":"id","type":"long"}],"type":"account.Takeout"},{"id":"700340377","predicate":"inputTakeoutFileLocation","params":[],"type":"InputFileLocation"},{"id":"-513517117","predicate":"updateDialogUnreadMark","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-253500010","predicate":"messages.dialogsNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Dialogs"},{"id":"-1625153079","predicate":"inputWebFileGeoPointLocation","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"access_hash","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"zoom","type":"int"},{"name":"scale","type":"int"}],"type":"InputWebFileLocation"},{"id":"-1255369827","predicate":"contacts.topPeersDisabled","params":[],"type":"contacts.TopPeers"},{"id":"-1685456582","predicate":"inputReportReasonCopyright","params":[],"type":"ReportReason"},{"id":"-732254058","predicate":"passwordKdfAlgoUnknown","params":[],"type":"PasswordKdfAlgo"},{"id":"4883767","predicate":"securePasswordKdfAlgoUnknown","params":[],"type":"SecurePasswordKdfAlgo"},{"id":"-1141711456","predicate":"securePasswordKdfAlgoPBKDF2HMACSHA512iter100000","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"-2042159726","predicate":"securePasswordKdfAlgoSHA512","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"354925740","predicate":"secureSecretSettings","params":[{"name":"secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_secret","type":"bytes"},{"name":"secure_secret_id","type":"long"}],"type":"SecureSecretSettings"},{"id":"982592842","predicate":"passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow","params":[{"name":"salt1","type":"bytes"},{"name":"salt2","type":"bytes"},{"name":"g","type":"int"},{"name":"p","type":"bytes"}],"type":"PasswordKdfAlgo"},{"id":"-1736378792","predicate":"inputCheckPasswordEmpty","params":[],"type":"InputCheckPasswordSRP"},{"id":"-763367294","predicate":"inputCheckPasswordSRP","params":[{"name":"srp_id","type":"long"},{"name":"A","type":"bytes"},{"name":"M1","type":"bytes"}],"type":"InputCheckPasswordSRP"},{"id":"-2036501105","predicate":"secureValueError","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-1592506512","predicate":"secureValueErrorTranslationFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"878931416","predicate":"secureValueErrorTranslationFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2103600678","predicate":"secureRequiredType","params":[{"name":"flags","type":"#"},{"name":"native_names","type":"flags.0?true"},{"name":"selfie_required","type":"flags.1?true"},{"name":"translation_required","type":"flags.2?true"},{"name":"type","type":"SecureValueType"}],"type":"SecureRequiredType"},{"id":"41187252","predicate":"secureRequiredTypeOneOf","params":[{"name":"types","type":"Vector"}],"type":"SecureRequiredType"},{"id":"-1078332329","predicate":"help.passportConfigNotModified","params":[],"type":"help.PassportConfig"},{"id":"-1600596305","predicate":"help.passportConfig","params":[{"name":"hash","type":"int"},{"name":"countries_langs","type":"DataJSON"}],"type":"help.PassportConfig"},{"id":"488313413","predicate":"inputAppEvent","params":[{"name":"time","type":"double"},{"name":"type","type":"string"},{"name":"peer","type":"long"},{"name":"data","type":"JSONValue"}],"type":"InputAppEvent"},{"id":"-1059185703","predicate":"jsonObjectValue","params":[{"name":"key","type":"string"},{"name":"value","type":"JSONValue"}],"type":"JSONObjectValue"},{"id":"1064139624","predicate":"jsonNull","params":[],"type":"JSONValue"},{"id":"-952869270","predicate":"jsonBool","params":[{"name":"value","type":"Bool"}],"type":"JSONValue"},{"id":"736157604","predicate":"jsonNumber","params":[{"name":"value","type":"double"}],"type":"JSONValue"},{"id":"-1222740358","predicate":"jsonString","params":[{"name":"value","type":"string"}],"type":"JSONValue"},{"id":"-146520221","predicate":"jsonArray","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1715350371","predicate":"jsonObject","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1311015810","predicate":"inputNotifyBroadcasts","params":[],"type":"InputNotifyPeer"},{"id":"-703403793","predicate":"notifyBroadcasts","params":[],"type":"NotifyPeer"},{"id":"-311786236","predicate":"textSubscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-939827711","predicate":"textSuperscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"55281185","predicate":"textMarked","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"483104362","predicate":"textPhone","params":[{"name":"text","type":"RichText"},{"name":"phone","type":"string"}],"type":"RichText"},{"id":"136105807","predicate":"textImage","params":[{"name":"document_id","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"RichText"},{"id":"504660880","predicate":"pageBlockKicker","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"878078826","predicate":"pageTableCell","params":[{"name":"flags","type":"#"},{"name":"header","type":"flags.0?true"},{"name":"align_center","type":"flags.3?true"},{"name":"align_right","type":"flags.4?true"},{"name":"valign_middle","type":"flags.5?true"},{"name":"valign_bottom","type":"flags.6?true"},{"name":"text","type":"flags.7?RichText"},{"name":"colspan","type":"flags.1?int"},{"name":"rowspan","type":"flags.2?int"}],"type":"PageTableCell"},{"id":"-524237339","predicate":"pageTableRow","params":[{"name":"cells","type":"Vector"}],"type":"PageTableRow"},{"id":"-1085412734","predicate":"pageBlockTable","params":[{"name":"flags","type":"#"},{"name":"bordered","type":"flags.0?true"},{"name":"striped","type":"flags.1?true"},{"name":"title","type":"RichText"},{"name":"rows","type":"Vector"}],"type":"PageBlock"},{"id":"1869903447","predicate":"pageCaption","params":[{"name":"text","type":"RichText"},{"name":"credit","type":"RichText"}],"type":"PageCaption"},{"id":"-1188055347","predicate":"pageListItemText","params":[{"name":"text","type":"RichText"}],"type":"PageListItem"},{"id":"635466748","predicate":"pageListItemBlocks","params":[{"name":"blocks","type":"Vector"}],"type":"PageListItem"},{"id":"1577484359","predicate":"pageListOrderedItemText","params":[{"name":"num","type":"string"},{"name":"text","type":"RichText"}],"type":"PageListOrderedItem"},{"id":"-1730311882","predicate":"pageListOrderedItemBlocks","params":[{"name":"num","type":"string"},{"name":"blocks","type":"Vector"}],"type":"PageListOrderedItem"},{"id":"-1702174239","predicate":"pageBlockOrderedList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"1987480557","predicate":"pageBlockDetails","params":[{"name":"flags","type":"#"},{"name":"open","type":"flags.0?true"},{"name":"blocks","type":"Vector"},{"name":"title","type":"RichText"}],"type":"PageBlock"},{"id":"-1282352120","predicate":"pageRelatedArticle","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"title","type":"flags.0?string"},{"name":"description","type":"flags.1?string"},{"name":"photo_id","type":"flags.2?long"},{"name":"author","type":"flags.3?string"},{"name":"published_date","type":"flags.4?int"}],"type":"PageRelatedArticle"},{"id":"370236054","predicate":"pageBlockRelatedArticles","params":[{"name":"title","type":"RichText"},{"name":"articles","type":"Vector"}],"type":"PageBlock"},{"id":"-1538310410","predicate":"pageBlockMap","params":[{"name":"geo","type":"GeoPoint"},{"name":"zoom","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-1738178803","predicate":"page","params":[{"name":"flags","type":"#"},{"name":"part","type":"flags.0?true"},{"name":"rtl","type":"flags.1?true"},{"name":"v2","type":"flags.2?true"},{"name":"url","type":"string"},{"name":"blocks","type":"Vector"},{"name":"photos","type":"Vector"},{"name":"documents","type":"Vector"},{"name":"views","type":"flags.3?int"}],"type":"Page"},{"id":"-610373422","predicate":"inputPrivacyKeyPhoneP2P","params":[],"type":"InputPrivacyKey"},{"id":"961092808","predicate":"privacyKeyPhoneP2P","params":[],"type":"PrivacyKey"},{"id":"894777186","predicate":"textAnchor","params":[{"name":"text","type":"RichText"},{"name":"name","type":"string"}],"type":"RichText"},{"id":"-1945767479","predicate":"help.supportName","params":[{"name":"name","type":"string"}],"type":"help.SupportName"},{"id":"-206688531","predicate":"help.userInfoEmpty","params":[],"type":"help.UserInfo"},{"id":"32192344","predicate":"help.userInfo","params":[{"name":"message","type":"string"},{"name":"entities","type":"Vector"},{"name":"author","type":"string"},{"name":"date","type":"int"}],"type":"help.UserInfo"},{"id":"-202219658","predicate":"messageActionContactSignUp","params":[],"type":"MessageAction"},{"id":"-1398708869","predicate":"updateMessagePoll","params":[{"name":"flags","type":"#"},{"name":"poll_id","type":"long"},{"name":"poll","type":"flags.0?Poll"},{"name":"results","type":"PollResults"}],"type":"Update"},{"id":"1823064809","predicate":"pollAnswer","params":[{"name":"text","type":"string"},{"name":"option","type":"bytes"}],"type":"PollAnswer"},{"id":"-2032041631","predicate":"poll","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"closed","type":"flags.0?true"},{"name":"public_voters","type":"flags.1?true"},{"name":"multiple_choice","type":"flags.2?true"},{"name":"quiz","type":"flags.3?true"},{"name":"question","type":"string"},{"name":"answers","type":"Vector"},{"name":"close_period","type":"flags.4?int"},{"name":"close_date","type":"flags.5?int"}],"type":"Poll"},{"id":"997055186","predicate":"pollAnswerVoters","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"correct","type":"flags.1?true"},{"name":"option","type":"bytes"},{"name":"voters","type":"int"}],"type":"PollAnswerVoters"},{"id":"-591909213","predicate":"pollResults","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"results","type":"flags.1?Vector"},{"name":"total_voters","type":"flags.2?int"},{"name":"recent_voters","type":"flags.3?Vector"},{"name":"solution","type":"flags.4?string"},{"name":"solution_entities","type":"flags.4?Vector"}],"type":"PollResults"},{"id":"261416433","predicate":"inputMediaPoll","params":[{"name":"flags","type":"#"},{"name":"poll","type":"Poll"},{"name":"correct_answers","type":"flags.0?Vector"},{"name":"solution","type":"flags.1?string"},{"name":"solution_entities","type":"flags.1?Vector"}],"type":"InputMedia"},{"id":"1272375192","predicate":"messageMediaPoll","params":[{"name":"poll","type":"Poll"},{"name":"results","type":"PollResults"}],"type":"MessageMedia"},{"id":"-264117680","predicate":"chatOnlines","params":[{"name":"onlines","type":"int"}],"type":"ChatOnlines"},{"id":"1202287072","predicate":"statsURL","params":[{"name":"url","type":"string"}],"type":"StatsURL"},{"id":"-525288402","predicate":"photoStrippedSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"1605510357","predicate":"chatAdminRights","params":[{"name":"flags","type":"#"},{"name":"change_info","type":"flags.0?true"},{"name":"post_messages","type":"flags.1?true"},{"name":"edit_messages","type":"flags.2?true"},{"name":"delete_messages","type":"flags.3?true"},{"name":"ban_users","type":"flags.4?true"},{"name":"invite_users","type":"flags.5?true"},{"name":"pin_messages","type":"flags.7?true"},{"name":"add_admins","type":"flags.9?true"},{"name":"anonymous","type":"flags.10?true"},{"name":"manage_call","type":"flags.11?true"},{"name":"other","type":"flags.12?true"}],"type":"ChatAdminRights"},{"id":"-1626209256","predicate":"chatBannedRights","params":[{"name":"flags","type":"#"},{"name":"view_messages","type":"flags.0?true"},{"name":"send_messages","type":"flags.1?true"},{"name":"send_media","type":"flags.2?true"},{"name":"send_stickers","type":"flags.3?true"},{"name":"send_gifs","type":"flags.4?true"},{"name":"send_games","type":"flags.5?true"},{"name":"send_inline","type":"flags.6?true"},{"name":"embed_links","type":"flags.7?true"},{"name":"send_polls","type":"flags.8?true"},{"name":"change_info","type":"flags.10?true"},{"name":"invite_users","type":"flags.15?true"},{"name":"pin_messages","type":"flags.17?true"},{"name":"until_date","type":"int"}],"type":"ChatBannedRights"},{"id":"1421875280","predicate":"updateChatDefaultBannedRights","params":[{"name":"peer","type":"Peer"},{"name":"default_banned_rights","type":"ChatBannedRights"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-433014407","predicate":"inputWallPaper","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputWallPaper"},{"id":"1913199744","predicate":"inputWallPaperSlug","params":[{"name":"slug","type":"string"}],"type":"InputWallPaper"},{"id":"-1150621555","predicate":"channelParticipantsContacts","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"771095562","predicate":"channelAdminLogEventActionDefaultBannedRights","params":[{"name":"prev_banned_rights","type":"ChatBannedRights"},{"name":"new_banned_rights","type":"ChatBannedRights"}],"type":"ChannelAdminLogEventAction"},{"id":"-1895328189","predicate":"channelAdminLogEventActionStopPoll","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"471437699","predicate":"account.wallPapersNotModified","params":[],"type":"account.WallPapers"},{"id":"-842824308","predicate":"account.wallPapers","params":[{"name":"hash","type":"long"},{"name":"wallpapers","type":"Vector"}],"type":"account.WallPapers"},{"id":"-1973130814","predicate":"codeSettings","params":[{"name":"flags","type":"#"},{"name":"allow_flashcall","type":"flags.0?true"},{"name":"current_number","type":"flags.1?true"},{"name":"allow_app_hash","type":"flags.4?true"},{"name":"allow_missed_call","type":"flags.5?true"},{"name":"logout_tokens","type":"flags.6?Vector"}],"type":"CodeSettings"},{"id":"499236004","predicate":"wallPaperSettings","params":[{"name":"flags","type":"#"},{"name":"blur","type":"flags.1?true"},{"name":"motion","type":"flags.2?true"},{"name":"background_color","type":"flags.0?int"},{"name":"second_background_color","type":"flags.4?int"},{"name":"third_background_color","type":"flags.5?int"},{"name":"fourth_background_color","type":"flags.6?int"},{"name":"intensity","type":"flags.3?int"},{"name":"rotation","type":"flags.4?int"}],"type":"WallPaperSettings"},{"id":"-532532493","predicate":"autoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"disabled","type":"flags.0?true"},{"name":"video_preload_large","type":"flags.1?true"},{"name":"audio_preload_next","type":"flags.2?true"},{"name":"phonecalls_less_data","type":"flags.3?true"},{"name":"photo_size_max","type":"int"},{"name":"video_size_max","type":"int"},{"name":"file_size_max","type":"int"},{"name":"video_upload_maxbitrate","type":"int"}],"type":"AutoDownloadSettings"},{"id":"1674235686","predicate":"account.autoDownloadSettings","params":[{"name":"low","type":"AutoDownloadSettings"},{"name":"medium","type":"AutoDownloadSettings"},{"name":"high","type":"AutoDownloadSettings"}],"type":"account.AutoDownloadSettings"},{"id":"-709641735","predicate":"emojiKeyword","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"594408994","predicate":"emojiKeywordDeleted","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"1556570557","predicate":"emojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"keywords","type":"Vector"}],"type":"EmojiKeywordsDifference"},{"id":"-1519029347","predicate":"emojiURL","params":[{"name":"url","type":"string"}],"type":"EmojiURL"},{"id":"-1275374751","predicate":"emojiLanguage","params":[{"name":"lang_code","type":"string"}],"type":"EmojiLanguage"},{"id":"-1529000952","predicate":"inputPrivacyKeyForwards","params":[],"type":"InputPrivacyKey"},{"id":"1777096355","predicate":"privacyKeyForwards","params":[],"type":"PrivacyKey"},{"id":"1461304012","predicate":"inputPrivacyKeyProfilePhoto","params":[],"type":"InputPrivacyKey"},{"id":"-1777000467","predicate":"privacyKeyProfilePhoto","params":[],"type":"PrivacyKey"},{"id":"1075322878","predicate":"inputPhotoFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"-667654413","predicate":"inputPhotoLegacyFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"InputFileLocation"},{"id":"925204121","predicate":"inputPeerPhotoFileLocation","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"long"}],"type":"InputFileLocation"},{"id":"-1652231205","predicate":"inputStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb_version","type":"int"}],"type":"InputFileLocation"},{"id":"-11252123","predicate":"folder","params":[{"name":"flags","type":"#"},{"name":"autofill_new_broadcasts","type":"flags.0?true"},{"name":"autofill_public_groups","type":"flags.1?true"},{"name":"autofill_new_correspondents","type":"flags.2?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"photo","type":"flags.3?ChatPhoto"}],"type":"Folder"},{"id":"1908216652","predicate":"dialogFolder","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"folder","type":"Folder"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"unread_muted_peers_count","type":"int"},{"name":"unread_unmuted_peers_count","type":"int"},{"name":"unread_muted_messages_count","type":"int"},{"name":"unread_unmuted_messages_count","type":"int"}],"type":"Dialog"},{"id":"1684014375","predicate":"inputDialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"InputDialogPeer"},{"id":"1363483106","predicate":"dialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"DialogPeer"},{"id":"-70073706","predicate":"inputFolderPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"folder_id","type":"int"}],"type":"InputFolderPeer"},{"id":"-373643672","predicate":"folderPeer","params":[{"name":"peer","type":"Peer"},{"name":"folder_id","type":"int"}],"type":"FolderPeer"},{"id":"422972864","predicate":"updateFolderPeers","params":[{"name":"folder_peers","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"497305826","predicate":"inputUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputUser"},{"id":"1536380829","predicate":"inputChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputChannel"},{"id":"-1468331492","predicate":"inputPeerUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputPeer"},{"id":"-1121318848","predicate":"inputPeerChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputPeer"},{"id":"55761658","predicate":"inputPrivacyKeyPhoneNumber","params":[],"type":"InputPrivacyKey"},{"id":"-778378131","predicate":"privacyKeyPhoneNumber","params":[],"type":"PrivacyKey"},{"id":"-1472172887","predicate":"topPeerCategoryForwardUsers","params":[],"type":"TopPeerCategory"},{"id":"-68239120","predicate":"topPeerCategoryForwardChats","params":[],"type":"TopPeerCategory"},{"id":"84703944","predicate":"channelAdminLogEventActionChangeLinkedChat","params":[{"name":"prev_value","type":"long"},{"name":"new_value","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-398136321","predicate":"messages.searchCounter","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"filter","type":"MessagesFilter"},{"name":"count","type":"int"}],"type":"messages.SearchCounter"},{"id":"280464681","predicate":"keyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.0?string"},{"name":"url","type":"string"},{"name":"button_id","type":"int"}],"type":"KeyboardButton"},{"id":"-802258988","predicate":"inputKeyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.1?string"},{"name":"url","type":"string"},{"name":"bot","type":"InputUser"}],"type":"KeyboardButton"},{"id":"-1831650802","predicate":"urlAuthResultRequest","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"bot","type":"User"},{"name":"domain","type":"string"}],"type":"UrlAuthResult"},{"id":"-1886646706","predicate":"urlAuthResultAccepted","params":[{"name":"url","type":"string"}],"type":"UrlAuthResult"},{"id":"-1445536993","predicate":"urlAuthResultDefault","params":[],"type":"UrlAuthResult"},{"id":"-2079962673","predicate":"inputPrivacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-380694650","predicate":"inputPrivacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"1796427406","predicate":"privacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"1103656293","predicate":"privacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"-1672577397","predicate":"messageEntityUnderline","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1090087980","predicate":"messageEntityStrike","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"34469328","predicate":"messageEntityBlockquote","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1786671974","predicate":"updatePeerSettings","params":[{"name":"peer","type":"Peer"},{"name":"settings","type":"PeerSettings"}],"type":"Update"},{"id":"-1078612597","predicate":"channelLocationEmpty","params":[],"type":"ChannelLocation"},{"id":"547062491","predicate":"channelLocation","params":[{"name":"geo_point","type":"GeoPoint"},{"name":"address","type":"string"}],"type":"ChannelLocation"},{"id":"-901375139","predicate":"peerLocated","params":[{"name":"peer","type":"Peer"},{"name":"expires","type":"int"},{"name":"distance","type":"int"}],"type":"PeerLocated"},{"id":"-1263546448","predicate":"updatePeerLocated","params":[{"name":"peers","type":"Vector"}],"type":"Update"},{"id":"241923758","predicate":"channelAdminLogEventActionChangeLocation","params":[{"name":"prev_value","type":"ChannelLocation"},{"name":"new_value","type":"ChannelLocation"}],"type":"ChannelAdminLogEventAction"},{"id":"-606798099","predicate":"inputReportReasonGeoIrrelevant","params":[],"type":"ReportReason"},{"id":"1401984889","predicate":"channelAdminLogEventActionToggleSlowMode","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"1148485274","predicate":"auth.authorizationSignUpRequired","params":[{"name":"flags","type":"#"},{"name":"terms_of_service","type":"flags.0?help.TermsOfService"}],"type":"auth.Authorization"},{"id":"-666824391","predicate":"payments.paymentVerificationNeeded","params":[{"name":"url","type":"string"}],"type":"payments.PaymentResult"},{"id":"42402760","predicate":"inputStickerSetAnimatedEmoji","params":[],"type":"InputStickerSet"},{"id":"967122427","predicate":"updateNewScheduledMessage","params":[{"name":"message","type":"Message"}],"type":"Update"},{"id":"-1870238482","predicate":"updateDeleteScheduledMessages","params":[{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-797791052","predicate":"restrictionReason","params":[{"name":"platform","type":"string"},{"name":"reason","type":"string"},{"name":"text","type":"string"}],"type":"RestrictionReason"},{"id":"1012306921","predicate":"inputTheme","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputTheme"},{"id":"-175567375","predicate":"inputThemeSlug","params":[{"name":"slug","type":"string"}],"type":"InputTheme"},{"id":"-1609668650","predicate":"theme","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"for_chat","type":"flags.5?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?Document"},{"name":"settings","type":"flags.3?Vector"},{"name":"emoticon","type":"flags.6?string"},{"name":"installs_count","type":"flags.4?int"}],"type":"Theme"},{"id":"-199313886","predicate":"account.themesNotModified","params":[],"type":"account.Themes"},{"id":"-1707242387","predicate":"account.themes","params":[{"name":"hash","type":"long"},{"name":"themes","type":"Vector"}],"type":"account.Themes"},{"id":"-2112423005","predicate":"updateTheme","params":[{"name":"theme","type":"Theme"}],"type":"Update"},{"id":"-786326563","predicate":"inputPrivacyKeyAddedByPhone","params":[],"type":"InputPrivacyKey"},{"id":"1124062251","predicate":"privacyKeyAddedByPhone","params":[],"type":"PrivacyKey"},{"id":"-2027964103","predicate":"updateGeoLiveViewed","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"}],"type":"Update"},{"id":"1448076945","predicate":"updateLoginToken","params":[],"type":"Update"},{"id":"1654593920","predicate":"auth.loginToken","params":[{"name":"expires","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"110008598","predicate":"auth.loginTokenMigrateTo","params":[{"name":"dc_id","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"957176926","predicate":"auth.loginTokenSuccess","params":[{"name":"authorization","type":"auth.Authorization"}],"type":"auth.LoginToken"},{"id":"1474462241","predicate":"account.contentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"},{"name":"sensitive_can_change","type":"flags.1?true"}],"type":"account.ContentSettings"},{"id":"-1456996667","predicate":"messages.inactiveChats","params":[{"name":"dates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.InactiveChats"},{"id":"-1012849566","predicate":"baseThemeClassic","params":[],"type":"BaseTheme"},{"id":"-69724536","predicate":"baseThemeDay","params":[],"type":"BaseTheme"},{"id":"-1212997976","predicate":"baseThemeNight","params":[],"type":"BaseTheme"},{"id":"1834973166","predicate":"baseThemeTinted","params":[],"type":"BaseTheme"},{"id":"1527845466","predicate":"baseThemeArctic","params":[],"type":"BaseTheme"},{"id":"-1770371538","predicate":"inputWallPaperNoFile","params":[{"name":"id","type":"long"}],"type":"InputWallPaper"},{"id":"-528465642","predicate":"wallPaperNoFile","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"default","type":"flags.1?true"},{"name":"dark","type":"flags.4?true"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"-1881255857","predicate":"inputThemeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?InputWallPaper"},{"name":"wallpaper_settings","type":"flags.1?WallPaperSettings"}],"type":"InputThemeSettings"},{"id":"-94849324","predicate":"themeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?WallPaper"}],"type":"ThemeSettings"},{"id":"1421174295","predicate":"webPageAttributeTheme","params":[{"name":"flags","type":"#"},{"name":"documents","type":"flags.0?Vector"},{"name":"settings","type":"flags.1?ThemeSettings"}],"type":"WebPageAttribute"},{"id":"274961865","predicate":"updateMessagePollVote","params":[{"name":"poll_id","type":"long"},{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"886196148","predicate":"messageUserVote","params":[{"name":"user_id","type":"long"},{"name":"option","type":"bytes"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"1017491692","predicate":"messageUserVoteInputOption","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"-1973033641","predicate":"messageUserVoteMultiple","params":[{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"136574537","predicate":"messages.votesList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"votes","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.VotesList"},{"id":"-1144565411","predicate":"keyboardButtonRequestPoll","params":[{"name":"flags","type":"#"},{"name":"quiz","type":"flags.0?Bool"},{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1981704948","predicate":"messageEntityBankCard","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-177732982","predicate":"bankCardOpenUrl","params":[{"name":"url","type":"string"},{"name":"name","type":"string"}],"type":"BankCardOpenUrl"},{"id":"1042605427","predicate":"payments.bankCardData","params":[{"name":"title","type":"string"},{"name":"open_urls","type":"Vector"}],"type":"payments.BankCardData"},{"id":"-118740917","predicate":"peerSelfLocated","params":[{"name":"expires","type":"int"}],"type":"PeerLocated"},{"id":"1949890536","predicate":"dialogFilter","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"non_contacts","type":"flags.1?true"},{"name":"groups","type":"flags.2?true"},{"name":"broadcasts","type":"flags.3?true"},{"name":"bots","type":"flags.4?true"},{"name":"exclude_muted","type":"flags.11?true"},{"name":"exclude_read","type":"flags.12?true"},{"name":"exclude_archived","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"emoticon","type":"flags.25?string"},{"name":"pinned_peers","type":"Vector"},{"name":"include_peers","type":"Vector"},{"name":"exclude_peers","type":"Vector"}],"type":"DialogFilter"},{"id":"2004110666","predicate":"dialogFilterSuggested","params":[{"name":"filter","type":"DialogFilter"},{"name":"description","type":"string"}],"type":"DialogFilterSuggested"},{"id":"654302845","predicate":"updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Update"},{"id":"-1512627963","predicate":"updateDialogFilterOrder","params":[{"name":"order","type":"Vector"}],"type":"Update"},{"id":"889491791","predicate":"updateDialogFilters","params":[],"type":"Update"},{"id":"-1237848657","predicate":"statsDateRangeDays","params":[{"name":"min_date","type":"int"},{"name":"max_date","type":"int"}],"type":"StatsDateRangeDays"},{"id":"-884757282","predicate":"statsAbsValueAndPrev","params":[{"name":"current","type":"double"},{"name":"previous","type":"double"}],"type":"StatsAbsValueAndPrev"},{"id":"-875679776","predicate":"statsPercentValue","params":[{"name":"part","type":"double"},{"name":"total","type":"double"}],"type":"StatsPercentValue"},{"id":"1244130093","predicate":"statsGraphAsync","params":[{"name":"token","type":"string"}],"type":"StatsGraph"},{"id":"-1092839390","predicate":"statsGraphError","params":[{"name":"error","type":"string"}],"type":"StatsGraph"},{"id":"-1901828938","predicate":"statsGraph","params":[{"name":"flags","type":"#"},{"name":"json","type":"DataJSON"},{"name":"zoom_token","type":"flags.0?string"}],"type":"StatsGraph"},{"id":"-1387279939","predicate":"messageInteractionCounters","params":[{"name":"msg_id","type":"int"},{"name":"views","type":"int"},{"name":"forwards","type":"int"}],"type":"MessageInteractionCounters"},{"id":"-1107852396","predicate":"stats.broadcastStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"followers","type":"StatsAbsValueAndPrev"},{"name":"views_per_post","type":"StatsAbsValueAndPrev"},{"name":"shares_per_post","type":"StatsAbsValueAndPrev"},{"name":"enabled_notifications","type":"StatsPercentValue"},{"name":"growth_graph","type":"StatsGraph"},{"name":"followers_graph","type":"StatsGraph"},{"name":"mute_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"interactions_graph","type":"StatsGraph"},{"name":"iv_interactions_graph","type":"StatsGraph"},{"name":"views_by_source_graph","type":"StatsGraph"},{"name":"new_followers_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"recent_message_interactions","type":"Vector"}],"type":"stats.BroadcastStats"},{"id":"-428884101","predicate":"inputMediaDice","params":[{"name":"emoticon","type":"string"}],"type":"InputMedia"},{"id":"1065280907","predicate":"messageMediaDice","params":[{"name":"value","type":"int"},{"name":"emoticon","type":"string"}],"type":"MessageMedia"},{"id":"-427863538","predicate":"inputStickerSetDice","params":[{"name":"emoticon","type":"string"}],"type":"InputStickerSet"},{"id":"-1728664459","predicate":"help.promoDataEmpty","params":[{"name":"expires","type":"int"}],"type":"help.PromoData"},{"id":"-1942390465","predicate":"help.promoData","params":[{"name":"flags","type":"#"},{"name":"proxy","type":"flags.0?true"},{"name":"expires","type":"int"},{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"psa_type","type":"flags.1?string"},{"name":"psa_message","type":"flags.2?string"}],"type":"help.PromoData"},{"id":"-567037804","predicate":"videoSize","params":[{"name":"flags","type":"#"},{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"video_start_ts","type":"flags.0?double"}],"type":"VideoSize"},{"id":"643940105","predicate":"updatePhoneCallSignalingData","params":[{"name":"phone_call_id","type":"long"},{"name":"data","type":"bytes"}],"type":"Update"},{"id":"1634294960","predicate":"chatInvitePeek","params":[{"name":"chat","type":"Chat"},{"name":"expires","type":"int"}],"type":"ChatInvite"},{"id":"-1660637285","predicate":"statsGroupTopPoster","params":[{"name":"user_id","type":"long"},{"name":"messages","type":"int"},{"name":"avg_chars","type":"int"}],"type":"StatsGroupTopPoster"},{"id":"-682079097","predicate":"statsGroupTopAdmin","params":[{"name":"user_id","type":"long"},{"name":"deleted","type":"int"},{"name":"kicked","type":"int"},{"name":"banned","type":"int"}],"type":"StatsGroupTopAdmin"},{"id":"1398765469","predicate":"statsGroupTopInviter","params":[{"name":"user_id","type":"long"},{"name":"invitations","type":"int"}],"type":"StatsGroupTopInviter"},{"id":"-276825834","predicate":"stats.megagroupStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"members","type":"StatsAbsValueAndPrev"},{"name":"messages","type":"StatsAbsValueAndPrev"},{"name":"viewers","type":"StatsAbsValueAndPrev"},{"name":"posters","type":"StatsAbsValueAndPrev"},{"name":"growth_graph","type":"StatsGraph"},{"name":"members_graph","type":"StatsGraph"},{"name":"new_members_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"messages_graph","type":"StatsGraph"},{"name":"actions_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"weekdays_graph","type":"StatsGraph"},{"name":"top_posters","type":"Vector"},{"name":"top_admins","type":"Vector"},{"name":"top_inviters","type":"Vector"},{"name":"users","type":"Vector"}],"type":"stats.MegagroupStats"},{"id":"-1096616924","predicate":"globalPrivacySettings","params":[{"name":"flags","type":"#"},{"name":"archive_and_mute_new_noncontact_peers","type":"flags.0?Bool"}],"type":"GlobalPrivacySettings"},{"id":"1667228533","predicate":"phoneConnectionWebrtc","params":[{"name":"flags","type":"#"},{"name":"turn","type":"flags.0?true"},{"name":"stun","type":"flags.1?true"},{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"username","type":"string"},{"name":"password","type":"string"}],"type":"PhoneConnection"},{"id":"1107543535","predicate":"help.countryCode","params":[{"name":"flags","type":"#"},{"name":"country_code","type":"string"},{"name":"prefixes","type":"flags.0?Vector"},{"name":"patterns","type":"flags.1?Vector"}],"type":"help.CountryCode"},{"id":"-1014526429","predicate":"help.country","params":[{"name":"flags","type":"#"},{"name":"hidden","type":"flags.0?true"},{"name":"iso2","type":"string"},{"name":"default_name","type":"string"},{"name":"name","type":"flags.1?string"},{"name":"country_codes","type":"Vector"}],"type":"help.Country"},{"id":"-1815339214","predicate":"help.countriesListNotModified","params":[],"type":"help.CountriesList"},{"id":"-2016381538","predicate":"help.countriesList","params":[{"name":"countries","type":"Vector"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"1163625789","predicate":"messageViews","params":[{"name":"flags","type":"#"},{"name":"views","type":"flags.0?int"},{"name":"forwards","type":"flags.1?int"},{"name":"replies","type":"flags.2?MessageReplies"}],"type":"MessageViews"},{"id":"-761649164","predicate":"updateChannelMessageForwards","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"forwards","type":"int"}],"type":"Update"},{"id":"-96535659","predicate":"photoSizeProgressive","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"sizes","type":"Vector"}],"type":"PhotoSize"},{"id":"-1228606141","predicate":"messages.messageViews","params":[{"name":"views","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.MessageViews"},{"id":"-693004986","predicate":"updateReadChannelDiscussionInbox","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"},{"name":"broadcast_id","type":"flags.0?long"},{"name":"broadcast_post","type":"flags.0?int"}],"type":"Update"},{"id":"1767677564","predicate":"updateReadChannelDiscussionOutbox","params":[{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Update"},{"id":"-1506535550","predicate":"messages.discussionMessage","params":[{"name":"flags","type":"#"},{"name":"messages","type":"Vector"},{"name":"max_id","type":"flags.0?int"},{"name":"read_inbox_max_id","type":"flags.1?int"},{"name":"read_outbox_max_id","type":"flags.2?int"},{"name":"unread_count","type":"int"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.DiscussionMessage"},{"id":"-1495959709","predicate":"messageReplyHeader","params":[{"name":"flags","type":"#"},{"name":"reply_to_msg_id","type":"int"},{"name":"reply_to_peer_id","type":"flags.0?Peer"},{"name":"reply_to_top_id","type":"flags.1?int"}],"type":"MessageReplyHeader"},{"id":"-2083123262","predicate":"messageReplies","params":[{"name":"flags","type":"#"},{"name":"comments","type":"flags.0?true"},{"name":"replies","type":"int"},{"name":"replies_pts","type":"int"},{"name":"recent_repliers","type":"flags.1?Vector"},{"name":"channel_id","type":"flags.0?long"},{"name":"max_id","type":"flags.2?int"},{"name":"read_max_id","type":"flags.3?int"}],"type":"MessageReplies"},{"id":"610945826","predicate":"updatePeerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"blocked","type":"Bool"}],"type":"Update"},{"id":"-386039788","predicate":"peerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"date","type":"int"}],"type":"PeerBlocked"},{"id":"-1937192669","predicate":"updateChannelUserTyping","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-1392895362","predicate":"inputMessageCallbackQuery","params":[{"name":"id","type":"int"},{"name":"query_id","type":"long"}],"type":"InputMessage"},{"id":"453242886","predicate":"channelParticipantLeft","params":[{"name":"peer","type":"Peer"}],"type":"ChannelParticipant"},{"id":"-531931925","predicate":"channelParticipantsMentions","params":[{"name":"flags","type":"#"},{"name":"q","type":"flags.0?string"},{"name":"top_msg_id","type":"flags.1?int"}],"type":"ChannelParticipantsFilter"},{"id":"-309990731","predicate":"updatePinnedMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1538885128","predicate":"updatePinnedChannelMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"464520273","predicate":"inputMessagesFilterPinned","params":[],"type":"MessagesFilter"},{"id":"-1986399595","predicate":"stats.messageStats","params":[{"name":"views_graph","type":"StatsGraph"}],"type":"stats.MessageStats"},{"id":"-1730095465","predicate":"messageActionGeoProximityReached","params":[{"name":"from_id","type":"Peer"},{"name":"to_id","type":"Peer"},{"name":"distance","type":"int"}],"type":"MessageAction"},{"id":"-668906175","predicate":"photoPathSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"-651419003","predicate":"speakingInGroupCallAction","params":[],"type":"SendMessageAction"},{"id":"2004925620","predicate":"groupCallDiscarded","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"duration","type":"int"}],"type":"GroupCall"},{"id":"-711498484","predicate":"groupCall","params":[{"name":"flags","type":"#"},{"name":"join_muted","type":"flags.1?true"},{"name":"can_change_join_muted","type":"flags.2?true"},{"name":"join_date_asc","type":"flags.6?true"},{"name":"schedule_start_subscribed","type":"flags.8?true"},{"name":"can_start_video","type":"flags.9?true"},{"name":"record_video_active","type":"flags.11?true"},{"name":"rtmp_stream","type":"flags.12?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"participants_count","type":"int"},{"name":"title","type":"flags.3?string"},{"name":"stream_dc_id","type":"flags.4?int"},{"name":"record_start_date","type":"flags.5?int"},{"name":"schedule_date","type":"flags.7?int"},{"name":"unmuted_video_count","type":"flags.10?int"},{"name":"unmuted_video_limit","type":"int"},{"name":"version","type":"int"}],"type":"GroupCall"},{"id":"-659913713","predicate":"inputGroupCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGroupCall"},{"id":"2047704898","predicate":"messageActionGroupCall","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"duration","type":"flags.0?int"}],"type":"MessageAction"},{"id":"1345295095","predicate":"messageActionInviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-341428482","predicate":"groupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"left","type":"flags.1?true"},{"name":"can_self_unmute","type":"flags.2?true"},{"name":"just_joined","type":"flags.4?true"},{"name":"versioned","type":"flags.5?true"},{"name":"min","type":"flags.8?true"},{"name":"muted_by_you","type":"flags.9?true"},{"name":"volume_by_admin","type":"flags.10?true"},{"name":"self","type":"flags.12?true"},{"name":"video_joined","type":"flags.15?true"},{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"active_date","type":"flags.3?int"},{"name":"source","type":"int"},{"name":"volume","type":"flags.7?int"},{"name":"about","type":"flags.11?string"},{"name":"raise_hand_rating","type":"flags.13?long"},{"name":"video","type":"flags.6?GroupCallParticipantVideo"},{"name":"presentation","type":"flags.14?GroupCallParticipantVideo"}],"type":"GroupCallParticipant"},{"id":"-124097970","predicate":"updateChat","params":[{"name":"chat_id","type":"long"}],"type":"Update"},{"id":"-219423922","predicate":"updateGroupCallParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"Update"},{"id":"347227392","predicate":"updateGroupCall","params":[{"name":"chat_id","type":"long"},{"name":"call","type":"GroupCall"}],"type":"Update"},{"id":"-1636664659","predicate":"phone.groupCall","params":[{"name":"call","type":"GroupCall"},{"name":"participants","type":"Vector"},{"name":"participants_next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.GroupCall"},{"id":"-193506890","predicate":"phone.groupParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"version","type":"int"}],"type":"phone.GroupParticipants"},{"id":"813821341","predicate":"inlineQueryPeerTypeSameBotPM","params":[],"type":"InlineQueryPeerType"},{"id":"-2093215828","predicate":"inlineQueryPeerTypePM","params":[],"type":"InlineQueryPeerType"},{"id":"-681130742","predicate":"inlineQueryPeerTypeChat","params":[],"type":"InlineQueryPeerType"},{"id":"1589952067","predicate":"inlineQueryPeerTypeMegagroup","params":[],"type":"InlineQueryPeerType"},{"id":"1664413338","predicate":"inlineQueryPeerTypeBroadcast","params":[],"type":"InlineQueryPeerType"},{"id":"589338437","predicate":"channelAdminLogEventActionStartGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-610299584","predicate":"channelAdminLogEventActionDiscardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-115071790","predicate":"channelAdminLogEventActionParticipantMute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-431740480","predicate":"channelAdminLogEventActionParticipantUnmute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1456906823","predicate":"channelAdminLogEventActionToggleGroupCallSetting","params":[{"name":"join_muted","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1966921727","predicate":"inputPaymentCredentialsGooglePay","params":[{"name":"payment_token","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"375566091","predicate":"messages.historyImport","params":[{"name":"id","type":"long"}],"type":"messages.HistoryImport"},{"id":"-606432698","predicate":"sendMessageHistoryImportAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"1578088377","predicate":"messages.historyImportParsed","params":[{"name":"flags","type":"#"},{"name":"pm","type":"flags.0?true"},{"name":"group","type":"flags.1?true"},{"name":"title","type":"flags.2?string"}],"type":"messages.HistoryImportParsed"},{"id":"-170010905","predicate":"inputReportReasonFake","params":[],"type":"ReportReason"},{"id":"-275956116","predicate":"messages.affectedFoundMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"},{"name":"messages","type":"Vector"}],"type":"messages.AffectedFoundMessages"},{"id":"-1441072131","predicate":"messageActionSetMessagesTTL","params":[{"name":"period","type":"int"}],"type":"MessageAction"},{"id":"-1147422299","predicate":"updatePeerHistoryTTL","params":[{"name":"flags","type":"#"},{"name":"peer","type":"Peer"},{"name":"ttl_period","type":"flags.0?int"}],"type":"Update"},{"id":"-796432838","predicate":"updateChatParticipant","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChatParticipant"},{"name":"new_participant","type":"flags.1?ChatParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1738720581","predicate":"updateChannelParticipant","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChannelParticipant"},{"name":"new_participant","type":"flags.1?ChannelParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-997782967","predicate":"updateBotStopped","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"stopped","type":"Bool"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1940201511","predicate":"chatInviteImporter","params":[{"name":"flags","type":"#"},{"name":"requested","type":"flags.0?true"},{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"about","type":"flags.2?string"},{"name":"approved_by","type":"flags.1?long"}],"type":"ChatInviteImporter"},{"id":"-1111085620","predicate":"messages.exportedChatInvites","params":[{"name":"count","type":"int"},{"name":"invites","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvites"},{"id":"410107472","predicate":"messages.exportedChatInvite","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"572915951","predicate":"messages.exportedChatInviteReplaced","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"-2118733814","predicate":"messages.chatInviteImporters","params":[{"name":"count","type":"int"},{"name":"importers","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatInviteImporters"},{"id":"-219353309","predicate":"chatAdminWithInvites","params":[{"name":"admin_id","type":"long"},{"name":"invites_count","type":"int"},{"name":"revoked_invites_count","type":"int"}],"type":"ChatAdminWithInvites"},{"id":"-1231326505","predicate":"messages.chatAdminsWithInvites","params":[{"name":"admins","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatAdminsWithInvites"},{"id":"1557846647","predicate":"channelAdminLogEventActionParticipantJoinByInvite","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1515256996","predicate":"channelAdminLogEventActionExportedInviteDelete","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1091179342","predicate":"channelAdminLogEventActionExportedInviteRevoke","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"-384910503","predicate":"channelAdminLogEventActionExportedInviteEdit","params":[{"name":"prev_invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1048537159","predicate":"channelAdminLogEventActionParticipantVolume","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1855199800","predicate":"channelAdminLogEventActionChangeHistoryTTL","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"-1571952873","predicate":"messages.checkedHistoryImportPeer","params":[{"name":"confirm_text","type":"string"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"93890858","predicate":"inputGroupCallStream","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"time_ms","type":"long"},{"name":"scale","type":"int"},{"name":"video_channel","type":"flags.0?int"},{"name":"video_quality","type":"flags.0?int"}],"type":"InputFileLocation"},{"id":"-1343921601","predicate":"phone.joinAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.JoinAsPeers"},{"id":"541839704","predicate":"phone.exportedGroupCallInvite","params":[{"name":"link","type":"string"}],"type":"phone.ExportedGroupCallInvite"},{"id":"-672693723","predicate":"inputBotInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"894081801","predicate":"botInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1281329567","predicate":"messageActionGroupCallScheduled","params":[{"name":"call","type":"InputGroupCall"},{"name":"schedule_date","type":"int"}],"type":"MessageAction"},{"id":"-592373577","predicate":"groupCallParticipantVideoSourceGroup","params":[{"name":"semantics","type":"string"},{"name":"sources","type":"Vector"}],"type":"GroupCallParticipantVideoSourceGroup"},{"id":"1735736008","predicate":"groupCallParticipantVideo","params":[{"name":"flags","type":"#"},{"name":"paused","type":"flags.0?true"},{"name":"endpoint","type":"string"},{"name":"source_groups","type":"Vector"},{"name":"audio_source","type":"flags.1?int"}],"type":"GroupCallParticipantVideo"},{"id":"192428418","predicate":"updateGroupCallConnection","params":[{"name":"flags","type":"#"},{"name":"presentation","type":"flags.0?true"},{"name":"params","type":"DataJSON"}],"type":"Update"},{"id":"-2046910401","predicate":"stickers.suggestedShortName","params":[{"name":"short_name","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"795652779","predicate":"botCommandScopeDefault","params":[],"type":"BotCommandScope"},{"id":"1011811544","predicate":"botCommandScopeUsers","params":[],"type":"BotCommandScope"},{"id":"1877059713","predicate":"botCommandScopeChats","params":[],"type":"BotCommandScope"},{"id":"-1180016534","predicate":"botCommandScopeChatAdmins","params":[],"type":"BotCommandScope"},{"id":"-610432643","predicate":"botCommandScopePeer","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"1071145937","predicate":"botCommandScopePeerAdmins","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"169026035","predicate":"botCommandScopePeerUser","params":[{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"BotCommandScope"},{"id":"-478701471","predicate":"account.resetPasswordFailedWait","params":[{"name":"retry_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-370148227","predicate":"account.resetPasswordRequestedWait","params":[{"name":"until_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-383330754","predicate":"account.resetPasswordOk","params":[],"type":"account.ResetPasswordResult"},{"id":"1299263278","predicate":"updateBotCommands","params":[{"name":"peer","type":"Peer"},{"name":"bot_id","type":"long"},{"name":"commands","type":"Vector"}],"type":"Update"},{"id":"-1434950843","predicate":"messageActionSetChatTheme","params":[{"name":"emoticon","type":"string"}],"type":"MessageAction"},{"id":"-1336228175","predicate":"sendMessageChooseStickerAction","params":[],"type":"SendMessageAction"},{"id":"981691896","predicate":"sponsoredMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"bytes"},{"name":"from_id","type":"flags.3?Peer"},{"name":"chat_invite","type":"flags.4?ChatInvite"},{"name":"chat_invite_hash","type":"flags.4?string"},{"name":"channel_post","type":"flags.2?int"},{"name":"start_param","type":"flags.0?string"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"SponsoredMessage"},{"id":"1705297877","predicate":"messages.sponsoredMessages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SponsoredMessages"},{"id":"215889721","predicate":"inputStickerSetAnimatedEmojiAnimations","params":[],"type":"InputStickerSet"},{"id":"630664139","predicate":"sendMessageEmojiInteraction","params":[{"name":"emoticon","type":"string"},{"name":"msg_id","type":"int"},{"name":"interaction","type":"DataJSON"}],"type":"SendMessageAction"},{"id":"-1234857938","predicate":"sendMessageEmojiInteractionSeen","params":[{"name":"emoticon","type":"string"}],"type":"SendMessageAction"},{"id":"-1227287081","predicate":"inputBotInlineMessageID64","params":[{"name":"dc_id","type":"int"},{"name":"owner_id","type":"long"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"-911191137","predicate":"searchResultsCalendarPeriod","params":[{"name":"date","type":"int"},{"name":"min_msg_id","type":"int"},{"name":"max_msg_id","type":"int"},{"name":"count","type":"int"}],"type":"SearchResultsCalendarPeriod"},{"id":"343859772","predicate":"messages.searchResultsCalendar","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.0?true"},{"name":"count","type":"int"},{"name":"min_date","type":"int"},{"name":"min_msg_id","type":"int"},{"name":"offset_id_offset","type":"flags.1?int"},{"name":"periods","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SearchResultsCalendar"},{"id":"2137295719","predicate":"searchResultPosition","params":[{"name":"msg_id","type":"int"},{"name":"date","type":"int"},{"name":"offset","type":"int"}],"type":"SearchResultsPosition"},{"id":"1404185519","predicate":"messages.searchResultsPositions","params":[{"name":"count","type":"int"},{"name":"positions","type":"Vector"}],"type":"messages.SearchResultsPositions"},{"id":"-339958837","predicate":"messageActionChatJoinedByRequest","params":[],"type":"MessageAction"},{"id":"1885586395","predicate":"updatePendingJoinRequests","params":[{"name":"peer","type":"Peer"},{"name":"requests_pending","type":"int"},{"name":"recent_requesters","type":"Vector"}],"type":"Update"},{"id":"299870598","predicate":"updateBotChatInviteRequester","params":[{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"about","type":"string"},{"name":"invite","type":"ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1347021750","predicate":"channelAdminLogEventActionParticipantJoinByRequest","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"approved_by","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-376962181","predicate":"inputKeyboardButtonUserProfile","params":[{"name":"text","type":"string"},{"name":"user_id","type":"InputUser"}],"type":"KeyboardButton"},{"id":"814112961","predicate":"keyboardButtonUserProfile","params":[{"name":"text","type":"string"},{"name":"user_id","type":"long"}],"type":"KeyboardButton"},{"id":"-2091463255","predicate":"channels.sendAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.SendAsPeers"},{"id":"-886388890","predicate":"channelAdminLogEventActionToggleNoForwards","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-738646805","predicate":"messages.stickerSetNotModified","params":[],"type":"messages.StickerSet"},{"id":"997004590","predicate":"users.userFull","params":[{"name":"full_user","type":"UserFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"users.UserFull"},{"id":"1753266509","predicate":"messages.peerSettings","params":[{"name":"settings","type":"PeerSettings"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.PeerSettings"},{"id":"663693416","predicate":"channelAdminLogEventActionSendMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"-702884114","predicate":"auth.codeTypeMissedCall","params":[],"type":"auth.CodeType"},{"id":"-2113903484","predicate":"auth.sentCodeTypeMissedCall","params":[{"name":"prefix","type":"string"},{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1012759713","predicate":"auth.loggedOut","params":[{"name":"flags","type":"#"},{"name":"future_auth_token","type":"flags.0?bytes"}],"type":"auth.LoggedOut"},{"id":"357013699","predicate":"updateMessageReactions","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"reactions","type":"MessageReactions"}],"type":"Update"},{"id":"1873957073","predicate":"reactionCount","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"reaction","type":"string"},{"name":"count","type":"int"}],"type":"ReactionCount"},{"id":"1328256121","predicate":"messageReactions","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"can_see_list","type":"flags.2?true"},{"name":"results","type":"Vector"},{"name":"recent_reactions","type":"flags.1?Vector"}],"type":"MessageReactions"},{"id":"834488621","predicate":"messages.messageReactionsList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"reactions","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.MessageReactionsList"},{"id":"-1065882623","predicate":"availableReaction","params":[{"name":"flags","type":"#"},{"name":"inactive","type":"flags.0?true"},{"name":"reaction","type":"string"},{"name":"title","type":"string"},{"name":"static_icon","type":"Document"},{"name":"appear_animation","type":"Document"},{"name":"select_animation","type":"Document"},{"name":"activate_animation","type":"Document"},{"name":"effect_animation","type":"Document"},{"name":"around_animation","type":"flags.1?Document"},{"name":"center_icon","type":"flags.1?Document"}],"type":"AvailableReaction"},{"id":"-1626924713","predicate":"messages.availableReactionsNotModified","params":[],"type":"messages.AvailableReactions"},{"id":"1989032621","predicate":"messages.availableReactions","params":[{"name":"hash","type":"int"},{"name":"reactions","type":"Vector"}],"type":"messages.AvailableReactions"},{"id":"852137487","predicate":"messageEntitySpoiler","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1661470870","predicate":"channelAdminLogEventActionChangeAvailableReactions","params":[{"name":"prev_value","type":"Vector"},{"name":"new_value","type":"Vector"}],"type":"ChannelAdminLogEventAction"},{"id":"1741309751","predicate":"messages.translateNoResult","params":[],"type":"messages.TranslatedText"},{"id":"-1575684144","predicate":"messages.translateResultText","params":[{"name":"text","type":"string"}],"type":"messages.TranslatedText"},{"id":"1370914559","predicate":"messagePeerReaction","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"unread","type":"flags.1?true"},{"name":"peer_id","type":"Peer"},{"name":"reaction","type":"string"}],"type":"MessagePeerReaction"}],"methods":[{"id":"-878758099","method":"invokeAfterMsg","params":[{"name":"msg_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"1036301552","method":"invokeAfterMsgs","params":[{"name":"msg_ids","type":"Vector"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1502141361","method":"auth.sendCode","params":[{"name":"phone_number","type":"string"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"-2131827673","method":"auth.signUp","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"auth.Authorization"},{"id":"-1126886015","method":"auth.signIn","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"auth.Authorization"},{"id":"1047706137","method":"auth.logOut","params":[],"type":"auth.LoggedOut"},{"id":"-1616179942","method":"auth.resetAuthorizations","params":[],"type":"Bool"},{"id":"-440401971","method":"auth.exportAuthorization","params":[{"name":"dc_id","type":"int"}],"type":"auth.ExportedAuthorization"},{"id":"-1518699091","method":"auth.importAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.Authorization"},{"id":"-841733627","method":"auth.bindTempAuthKey","params":[{"name":"perm_auth_key_id","type":"long"},{"name":"nonce","type":"long"},{"name":"expires_at","type":"int"},{"name":"encrypted_message","type":"bytes"}],"type":"Bool"},{"id":"-326762118","method":"account.registerDevice","params":[{"name":"flags","type":"#"},{"name":"no_muted","type":"flags.0?true"},{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"app_sandbox","type":"Bool"},{"name":"secret","type":"bytes"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"1779249670","method":"account.unregisterDevice","params":[{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"-2067899501","method":"account.updateNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"},{"name":"settings","type":"InputPeerNotifySettings"}],"type":"Bool"},{"id":"313765169","method":"account.getNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"}],"type":"PeerNotifySettings"},{"id":"-612493497","method":"account.resetNotifySettings","params":[],"type":"Bool"},{"id":"2018596725","method":"account.updateProfile","params":[{"name":"flags","type":"#"},{"name":"first_name","type":"flags.0?string"},{"name":"last_name","type":"flags.1?string"},{"name":"about","type":"flags.2?string"}],"type":"User"},{"id":"1713919532","method":"account.updateStatus","params":[{"name":"offline","type":"Bool"}],"type":"Bool"},{"id":"127302966","method":"account.getWallPapers","params":[{"name":"hash","type":"long"}],"type":"account.WallPapers"},{"id":"-977650298","method":"account.reportPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"227648840","method":"users.getUsers","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1240508136","method":"users.getFullUser","params":[{"name":"id","type":"InputUser"}],"type":"users.UserFull"},{"id":"2061264541","method":"contacts.getContactIDs","params":[{"name":"hash","type":"long"}],"type":"Vector"},{"id":"-995929106","method":"contacts.getStatuses","params":[],"type":"Vector"},{"id":"1574346258","method":"contacts.getContacts","params":[{"name":"hash","type":"long"}],"type":"contacts.Contacts"},{"id":"746589157","method":"contacts.importContacts","params":[{"name":"contacts","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"157945344","method":"contacts.deleteContacts","params":[{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"269745566","method":"contacts.deleteByPhones","params":[{"name":"phones","type":"Vector"}],"type":"Bool"},{"id":"1758204945","method":"contacts.block","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-1096393392","method":"contacts.unblock","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-176409329","method":"contacts.getBlocked","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"contacts.Blocked"},{"id":"1673946374","method":"messages.getMessages","params":[{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1594569905","method":"messages.getDialogs","params":[{"name":"flags","type":"#"},{"name":"exclude_pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"offset_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Dialogs"},{"id":"1143203525","method":"messages.getHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1593989278","method":"messages.search","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"q","type":"string"},{"name":"from_id","type":"flags.0?InputPeer"},{"name":"top_msg_id","type":"flags.1?int"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"238054714","method":"messages.readHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedMessages"},{"id":"-1332768214","method":"messages.deleteHistory","params":[{"name":"flags","type":"#"},{"name":"just_clear","type":"flags.0?true"},{"name":"revoke","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"},{"name":"min_date","type":"flags.2?int"},{"name":"max_date","type":"flags.3?int"}],"type":"messages.AffectedHistory"},{"id":"-443640366","method":"messages.deleteMessages","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"94983360","method":"messages.receivedMessages","params":[{"name":"max_id","type":"int"}],"type":"Vector"},{"id":"1486110434","method":"messages.setTyping","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"action","type":"SendMessageAction"}],"type":"Bool"},{"id":"228423076","method":"messages.sendMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-497026848","method":"messages.sendMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"media","type":"InputMedia"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-869258997","method":"messages.forwardMessages","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"with_my_score","type":"flags.8?true"},{"name":"drop_author","type":"flags.11?true"},{"name":"drop_media_captions","type":"flags.12?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"from_peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"random_id","type":"Vector"},{"name":"to_peer","type":"InputPeer"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-820669733","method":"messages.reportSpam","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-270948702","method":"messages.getPeerSettings","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.PeerSettings"},{"id":"-1991005362","method":"messages.report","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"1240027791","method":"messages.getChats","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"-1364194508","method":"messages.getFullChat","params":[{"name":"chat_id","type":"long"}],"type":"messages.ChatFull"},{"id":"1937260541","method":"messages.editChatTitle","params":[{"name":"chat_id","type":"long"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"903730804","method":"messages.editChatPhoto","params":[{"name":"chat_id","type":"long"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"-230206493","method":"messages.addChatUser","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"fwd_limit","type":"int"}],"type":"Updates"},{"id":"-1575461717","method":"messages.deleteChatUser","params":[{"name":"flags","type":"#"},{"name":"revoke_history","type":"flags.0?true"},{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"164303470","method":"messages.createChat","params":[{"name":"users","type":"Vector"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-304838614","method":"updates.getState","params":[],"type":"updates.State"},{"id":"630429265","method":"updates.getDifference","params":[{"name":"flags","type":"#"},{"name":"pts","type":"int"},{"name":"pts_total_limit","type":"flags.0?int"},{"name":"date","type":"int"},{"name":"qts","type":"int"}],"type":"updates.Difference"},{"id":"1926525996","method":"photos.updateProfilePhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"photos.Photo"},{"id":"-1980559511","method":"photos.uploadProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"photos.Photo"},{"id":"-2016444625","method":"photos.deletePhotos","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1291540959","method":"upload.saveFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1319462148","method":"upload.getFile","params":[{"name":"flags","type":"#"},{"name":"precise","type":"flags.0?true"},{"name":"cdn_supported","type":"flags.1?true"},{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.File"},{"id":"-990308245","method":"help.getConfig","params":[],"type":"Config"},{"id":"531836966","method":"help.getNearestDc","params":[],"type":"NearestDc"},{"id":"1378703997","method":"help.getAppUpdate","params":[{"name":"source","type":"string"}],"type":"help.AppUpdate"},{"id":"1295590211","method":"help.getInviteText","params":[],"type":"help.InviteText"},{"id":"-1848823128","method":"photos.getUserPhotos","params":[{"name":"user_id","type":"InputUser"},{"name":"offset","type":"int"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"photos.Photos"},{"id":"651135312","method":"messages.getDhConfig","params":[{"name":"version","type":"int"},{"name":"random_length","type":"int"}],"type":"messages.DhConfig"},{"id":"-162681021","method":"messages.requestEncryption","params":[{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1035731989","method":"messages.acceptEncryption","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"-208425312","method":"messages.discardEncryption","params":[{"name":"flags","type":"#"},{"name":"delete_history","type":"flags.0?true"},{"name":"chat_id","type":"int"}],"type":"Bool"},{"id":"2031374829","method":"messages.setEncryptedTyping","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"typing","type":"Bool"}],"type":"Bool"},{"id":"2135648522","method":"messages.readEncryptedHistory","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"max_date","type":"int"}],"type":"Bool"},{"id":"1157265941","method":"messages.sendEncrypted","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1431914525","method":"messages.sendEncryptedFile","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"},{"name":"file","type":"InputEncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"852769188","method":"messages.sendEncryptedService","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1436924774","method":"messages.receivedQueue","params":[{"name":"max_qts","type":"int"}],"type":"Vector"},{"id":"1259113487","method":"messages.reportEncryptedSpam","params":[{"name":"peer","type":"InputEncryptedChat"}],"type":"Bool"},{"id":"-562337987","method":"upload.saveBigFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"file_total_parts","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1043505495","method":"initConnection","params":[{"name":"flags","type":"#"},{"name":"api_id","type":"int"},{"name":"device_model","type":"string"},{"name":"system_version","type":"string"},{"name":"app_version","type":"string"},{"name":"system_lang_code","type":"string"},{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"proxy","type":"flags.0?InputClientProxy"},{"name":"params","type":"flags.1?JSONValue"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1663104819","method":"help.getSupport","params":[],"type":"help.Support"},{"id":"916930423","method":"messages.readMessageContents","params":[{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"655677548","method":"account.checkUsername","params":[{"name":"username","type":"string"}],"type":"Bool"},{"id":"1040964988","method":"account.updateUsername","params":[{"name":"username","type":"string"}],"type":"User"},{"id":"301470424","method":"contacts.search","params":[{"name":"q","type":"string"},{"name":"limit","type":"int"}],"type":"contacts.Found"},{"id":"-623130288","method":"account.getPrivacy","params":[{"name":"key","type":"InputPrivacyKey"}],"type":"account.PrivacyRules"},{"id":"-906486552","method":"account.setPrivacy","params":[{"name":"key","type":"InputPrivacyKey"},{"name":"rules","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"1099779595","method":"account.deleteAccount","params":[{"name":"reason","type":"string"}],"type":"Bool"},{"id":"150761757","method":"account.getAccountTTL","params":[],"type":"AccountDaysTTL"},{"id":"608323678","method":"account.setAccountTTL","params":[{"name":"ttl","type":"AccountDaysTTL"}],"type":"Bool"},{"id":"-627372787","method":"invokeWithLayer","params":[{"name":"layer","type":"int"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-113456221","method":"contacts.resolveUsername","params":[{"name":"username","type":"string"}],"type":"contacts.ResolvedPeer"},{"id":"-2108208411","method":"account.sendChangePhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1891839707","method":"account.changePhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"User"},{"id":"-710552671","method":"messages.getStickers","params":[{"name":"emoticon","type":"string"},{"name":"hash","type":"long"}],"type":"messages.Stickers"},{"id":"-1197432408","method":"messages.getAllStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"954152242","method":"account.updateDeviceLocked","params":[{"name":"period","type":"int"}],"type":"Bool"},{"id":"1738800940","method":"auth.importBotAuthorization","params":[{"name":"flags","type":"int"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"bot_auth_token","type":"string"}],"type":"auth.Authorization"},{"id":"-1956073268","method":"messages.getWebPagePreview","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"MessageMedia"},{"id":"-484392616","method":"account.getAuthorizations","params":[],"type":"account.Authorizations"},{"id":"-545786948","method":"account.resetAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1418342645","method":"account.getPassword","params":[],"type":"account.Password"},{"id":"-1663767815","method":"account.getPasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"account.PasswordSettings"},{"id":"-1516564433","method":"account.updatePasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"new_settings","type":"account.PasswordInputSettings"}],"type":"Bool"},{"id":"-779399914","method":"auth.checkPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"auth.Authorization"},{"id":"-661144474","method":"auth.requestPasswordRecovery","params":[],"type":"auth.PasswordRecovery"},{"id":"923364464","method":"auth.recoverPassword","params":[{"name":"flags","type":"#"},{"name":"code","type":"string"},{"name":"new_settings","type":"flags.0?account.PasswordInputSettings"}],"type":"auth.Authorization"},{"id":"-1080796745","method":"invokeWithoutUpdates","params":[{"name":"query","type":"!X"}],"type":"X"},{"id":"-1607670315","method":"messages.exportChatInvite","params":[{"name":"flags","type":"#"},{"name":"legacy_revoke_permanent","type":"flags.2?true"},{"name":"request_needed","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"},{"name":"title","type":"flags.4?string"}],"type":"ExportedChatInvite"},{"id":"1051570619","method":"messages.checkChatInvite","params":[{"name":"hash","type":"string"}],"type":"ChatInvite"},{"id":"1817183516","method":"messages.importChatInvite","params":[{"name":"hash","type":"string"}],"type":"Updates"},{"id":"-928977804","method":"messages.getStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"hash","type":"int"}],"type":"messages.StickerSet"},{"id":"-946871200","method":"messages.installStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"archived","type":"Bool"}],"type":"messages.StickerSetInstallResult"},{"id":"-110209570","method":"messages.uninstallStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"-421563528","method":"messages.startBot","params":[{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"long"},{"name":"start_param","type":"string"}],"type":"Updates"},{"id":"-1877938321","method":"help.getAppChangelog","params":[{"name":"prev_app_version","type":"string"}],"type":"Updates"},{"id":"1468322785","method":"messages.getMessagesViews","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"increment","type":"Bool"}],"type":"messages.MessageViews"},{"id":"-871347913","method":"channels.readHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"-2067661490","method":"channels.deleteMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"-196443371","method":"channels.reportSpam","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1383294429","method":"channels.getMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"2010044880","method":"channels.getParticipants","params":[{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelParticipantsFilter"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"channels.ChannelParticipants"},{"id":"-1599378234","method":"channels.getParticipant","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"channels.ChannelParticipant"},{"id":"176122811","method":"channels.getChannels","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"141781513","method":"channels.getFullChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.ChatFull"},{"id":"1029681423","method":"channels.createChannel","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.0?true"},{"name":"megagroup","type":"flags.1?true"},{"name":"for_import","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"about","type":"string"},{"name":"geo_point","type":"flags.2?InputGeoPoint"},{"name":"address","type":"flags.2?string"}],"type":"Updates"},{"id":"-751007486","method":"channels.editAdmin","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"string"}],"type":"Updates"},{"id":"1450044624","method":"channels.editTitle","params":[{"name":"channel","type":"InputChannel"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-248621111","method":"channels.editPhoto","params":[{"name":"channel","type":"InputChannel"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"283557164","method":"channels.checkUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"890549214","method":"channels.updateUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"615851205","method":"channels.joinChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"-130635115","method":"channels.leaveChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"429865580","method":"channels.inviteToChannel","params":[{"name":"channel","type":"InputChannel"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"-1072619549","method":"channels.deleteChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"51854712","method":"updates.getChannelDifference","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelMessagesFilter"},{"name":"pts","type":"int"},{"name":"limit","type":"int"}],"type":"updates.ChannelDifference"},{"id":"-1470377534","method":"messages.editChatAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"is_admin","type":"Bool"}],"type":"Bool"},{"id":"-1568189671","method":"messages.migrateChat","params":[{"name":"chat_id","type":"long"}],"type":"Updates"},{"id":"1271290010","method":"messages.searchGlobal","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"q","type":"string"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"2016638777","method":"messages.reorderStickerSets","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"864953444","method":"messages.getDocumentByHash","params":[{"name":"sha256","type":"bytes"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1559270965","method":"messages.getSavedGifs","params":[{"name":"hash","type":"long"}],"type":"messages.SavedGifs"},{"id":"846868683","method":"messages.saveGif","params":[{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"1364105629","method":"messages.getInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"geo_point","type":"flags.0?InputGeoPoint"},{"name":"query","type":"string"},{"name":"offset","type":"string"}],"type":"messages.BotResults"},{"id":"-346119674","method":"messages.setInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"private","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"next_offset","type":"flags.2?string"},{"name":"switch_pm","type":"flags.3?InlineBotSwitchPM"}],"type":"Bool"},{"id":"2057376407","method":"messages.sendInlineBotResult","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"hide_via","type":"flags.11?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"random_id","type":"long"},{"name":"query_id","type":"long"},{"name":"id","type":"string"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"-432034325","method":"channels.exportMessageLink","params":[{"name":"flags","type":"#"},{"name":"grouped","type":"flags.0?true"},{"name":"thread","type":"flags.1?true"},{"name":"channel","type":"InputChannel"},{"name":"id","type":"int"}],"type":"ExportedMessageLink"},{"id":"527021574","method":"channels.toggleSignatures","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"1056025023","method":"auth.resendCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"auth.SentCode"},{"id":"520357240","method":"auth.cancelCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"Bool"},{"id":"-39416522","method":"messages.getMessageEditData","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"messages.MessageEditData"},{"id":"1224152952","method":"messages.editMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.15?int"}],"type":"Updates"},{"id":"-2091549254","method":"messages.editInlineBotMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"-1824339449","method":"messages.getBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"game","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"data","type":"flags.0?bytes"},{"name":"password","type":"flags.2?InputCheckPasswordSRP"}],"type":"messages.BotCallbackAnswer"},{"id":"-712043766","method":"messages.setBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"Bool"},{"id":"-1758168906","method":"contacts.getTopPeers","params":[{"name":"flags","type":"#"},{"name":"correspondents","type":"flags.0?true"},{"name":"bots_pm","type":"flags.1?true"},{"name":"bots_inline","type":"flags.2?true"},{"name":"phone_calls","type":"flags.3?true"},{"name":"forward_users","type":"flags.4?true"},{"name":"forward_chats","type":"flags.5?true"},{"name":"groups","type":"flags.10?true"},{"name":"channels","type":"flags.15?true"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"contacts.TopPeers"},{"id":"451113900","method":"contacts.resetTopPeerRating","params":[{"name":"category","type":"TopPeerCategory"},{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-462373635","method":"messages.getPeerDialogs","params":[{"name":"peers","type":"Vector"}],"type":"messages.PeerDialogs"},{"id":"-1137057461","method":"messages.saveDraft","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"peer","type":"InputPeer"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"1782549861","method":"messages.getAllDrafts","params":[],"type":"Updates"},{"id":"1685588756","method":"messages.getFeaturedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"1527873830","method":"messages.readFeaturedStickers","params":[{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1649852357","method":"messages.getRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"hash","type":"long"}],"type":"messages.RecentStickers"},{"id":"958863608","method":"messages.saveRecentSticker","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-1986437075","method":"messages.clearRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"}],"type":"Bool"},{"id":"1475442322","method":"messages.getArchivedStickers","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"offset_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.ArchivedStickers"},{"id":"457157256","method":"account.sendConfirmPhoneCode","params":[{"name":"hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1596029123","method":"account.confirmPhone","params":[{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"-122669393","method":"channels.getAdminedPublicChannels","params":[{"name":"flags","type":"#"},{"name":"by_location","type":"flags.0?true"},{"name":"check_limit","type":"flags.1?true"}],"type":"messages.Chats"},{"id":"1678738104","method":"messages.getMaskStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"-866424884","method":"messages.getAttachedStickers","params":[{"name":"media","type":"InputStickeredMedia"}],"type":"Vector"},{"id":"-1907842680","method":"auth.dropTempAuthKeys","params":[{"name":"except_auth_keys","type":"Vector"}],"type":"Bool"},{"id":"-1896289088","method":"messages.setGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Updates"},{"id":"363700068","method":"messages.setInlineGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Bool"},{"id":"-400399203","method":"messages.getGameHighScores","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"258170395","method":"messages.getInlineGameHighScores","params":[{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"-468934396","method":"messages.getCommonChats","params":[{"name":"user_id","type":"InputUser"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.Chats"},{"id":"-2023787330","method":"messages.getAllChats","params":[{"name":"except_ids","type":"Vector"}],"type":"messages.Chats"},{"id":"-333262899","method":"help.setBotUpdatesStatus","params":[{"name":"pending_updates_count","type":"int"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"852135825","method":"messages.getWebPage","params":[{"name":"url","type":"string"},{"name":"hash","type":"int"}],"type":"WebPage"},{"id":"-1489903017","method":"messages.toggleDialogPin","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"991616823","method":"messages.reorderPinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"folder_id","type":"int"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-692498958","method":"messages.getPinnedDialogs","params":[{"name":"folder_id","type":"int"}],"type":"messages.PeerDialogs"},{"id":"-1440257555","method":"bots.sendCustomRequest","params":[{"name":"custom_method","type":"string"},{"name":"params","type":"DataJSON"}],"type":"DataJSON"},{"id":"-434028723","method":"bots.answerWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"}],"type":"Bool"},{"id":"619086221","method":"upload.getWebFile","params":[{"name":"location","type":"InputWebFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.WebFile"},{"id":"-1976353651","method":"payments.getPaymentForm","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"theme_params","type":"flags.0?DataJSON"}],"type":"payments.PaymentForm"},{"id":"611897804","method":"payments.getPaymentReceipt","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"payments.PaymentReceipt"},{"id":"-619695760","method":"payments.validateRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"info","type":"PaymentRequestedInfo"}],"type":"payments.ValidatedRequestedInfo"},{"id":"818134173","method":"payments.sendPaymentForm","params":[{"name":"flags","type":"#"},{"name":"form_id","type":"long"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"requested_info_id","type":"flags.0?string"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"credentials","type":"InputPaymentCredentials"},{"name":"tip_amount","type":"flags.2?long"}],"type":"payments.PaymentResult"},{"id":"1151208273","method":"account.getTmpPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"period","type":"int"}],"type":"account.TmpPassword"},{"id":"578650699","method":"payments.getSavedInfo","params":[],"type":"payments.SavedInfo"},{"id":"-667062079","method":"payments.clearSavedInfo","params":[{"name":"flags","type":"#"},{"name":"credentials","type":"flags.0?true"},{"name":"info","type":"flags.1?true"}],"type":"Bool"},{"id":"-436833542","method":"messages.setBotShippingResults","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"Bool"},{"id":"163765653","method":"messages.setBotPrecheckoutResults","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"}],"type":"Bool"},{"id":"-1876841625","method":"stickers.createStickerSet","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"animated","type":"flags.1?true"},{"name":"videos","type":"flags.4?true"},{"name":"user_id","type":"InputUser"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumb","type":"flags.2?InputDocument"},{"name":"stickers","type":"Vector"},{"name":"software","type":"flags.3?string"}],"type":"messages.StickerSet"},{"id":"-143257775","method":"stickers.removeStickerFromSet","params":[{"name":"sticker","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"-4795190","method":"stickers.changeStickerPosition","params":[{"name":"sticker","type":"InputDocument"},{"name":"position","type":"int"}],"type":"messages.StickerSet"},{"id":"-2041315650","method":"stickers.addStickerToSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"sticker","type":"InputStickerSetItem"}],"type":"messages.StickerSet"},{"id":"1369162417","method":"messages.uploadMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"1430593449","method":"phone.getCallConfig","params":[],"type":"DataJSON"},{"id":"1124046573","method":"phone.requestCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"1003664544","method":"phone.acceptCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"788404002","method":"phone.confirmCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_a","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"399855457","method":"phone.receivedCall","params":[{"name":"peer","type":"InputPhoneCall"}],"type":"Bool"},{"id":"-1295269440","method":"phone.discardCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"duration","type":"int"},{"name":"reason","type":"PhoneCallDiscardReason"},{"name":"connection_id","type":"long"}],"type":"Updates"},{"id":"1508562471","method":"phone.setCallRating","params":[{"name":"flags","type":"#"},{"name":"user_initiative","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"rating","type":"int"},{"name":"comment","type":"string"}],"type":"Updates"},{"id":"662363518","method":"phone.saveCallDebug","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"debug","type":"DataJSON"}],"type":"Bool"},{"id":"536919235","method":"upload.getCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.CdnFile"},{"id":"-1691921240","method":"upload.reuploadCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"request_token","type":"bytes"}],"type":"Vector"},{"id":"1375900482","method":"help.getCdnConfig","params":[],"type":"CdnConfig"},{"id":"-219008246","method":"langpack.getLangPack","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackDifference"},{"id":"-269862909","method":"langpack.getStrings","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"keys","type":"Vector"}],"type":"Vector"},{"id":"-845657435","method":"langpack.getDifference","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"LangPackDifference"},{"id":"1120311183","method":"langpack.getLanguages","params":[{"name":"lang_pack","type":"string"}],"type":"Vector"},{"id":"-1763259007","method":"channels.editBanned","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"870184064","method":"channels.getAdminLog","params":[{"name":"flags","type":"#"},{"name":"channel","type":"InputChannel"},{"name":"q","type":"string"},{"name":"events_filter","type":"flags.0?ChannelAdminLogEventsFilter"},{"name":"admins","type":"flags.1?Vector"},{"name":"max_id","type":"long"},{"name":"min_id","type":"long"},{"name":"limit","type":"int"}],"type":"channels.AdminLogResults"},{"id":"1302676017","method":"upload.getCdnFileHashes","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"-914493408","method":"messages.sendScreenshotNotification","params":[{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"int"},{"name":"random_id","type":"long"}],"type":"Updates"},{"id":"-359881479","method":"channels.setStickers","params":[{"name":"channel","type":"InputChannel"},{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"82946729","method":"messages.getFavedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FavedStickers"},{"id":"-1174420133","method":"messages.faveSticker","params":[{"name":"id","type":"InputDocument"},{"name":"unfave","type":"Bool"}],"type":"Bool"},{"id":"-357180360","method":"channels.readMessageContents","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-2020263951","method":"contacts.resetSaved","params":[],"type":"Bool"},{"id":"1180140658","method":"messages.getUnreadMentions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-1355375294","method":"channels.deleteHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"1036054804","method":"help.getRecentMeUrls","params":[{"name":"referer","type":"string"}],"type":"help.RecentMeUrls"},{"id":"-356796084","method":"channels.togglePreHistoryHidden","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"251759059","method":"messages.readMentions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1881817312","method":"messages.getRecentLocations","params":[{"name":"peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-134016113","method":"messages.sendMultiMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"noforwards","type":"flags.14?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"multi_media","type":"Vector"},{"name":"schedule_date","type":"flags.10?int"},{"name":"send_as","type":"flags.13?InputPeer"}],"type":"Updates"},{"id":"1347929239","method":"messages.uploadEncryptedFile","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"file","type":"InputEncryptedFile"}],"type":"EncryptedFile"},{"id":"405695855","method":"account.getWebAuthorizations","params":[],"type":"account.WebAuthorizations"},{"id":"755087855","method":"account.resetWebAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1747789204","method":"account.resetWebAuthorizations","params":[],"type":"Bool"},{"id":"896555914","method":"messages.searchStickerSets","params":[{"name":"flags","type":"#"},{"name":"exclude_featured","type":"flags.0?true"},{"name":"q","type":"string"},{"name":"hash","type":"long"}],"type":"messages.FoundStickerSets"},{"id":"-956147407","method":"upload.getFileHashes","params":[{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"749019089","method":"help.getTermsOfServiceUpdate","params":[],"type":"help.TermsOfServiceUpdate"},{"id":"-294455398","method":"help.acceptTermsOfService","params":[{"name":"id","type":"DataJSON"}],"type":"Bool"},{"id":"-1299661699","method":"account.getAllSecureValues","params":[],"type":"Vector"},{"id":"1936088002","method":"account.getSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Vector"},{"id":"-1986010339","method":"account.saveSecureValue","params":[{"name":"value","type":"InputSecureValue"},{"name":"secure_secret_id","type":"long"}],"type":"SecureValue"},{"id":"-1199522741","method":"account.deleteSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Bool"},{"id":"-1865902923","method":"users.setSecureValueErrors","params":[{"name":"id","type":"InputUser"},{"name":"errors","type":"Vector"}],"type":"Bool"},{"id":"-1456907910","method":"account.getAuthorizationForm","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"}],"type":"account.AuthorizationForm"},{"id":"-202552205","method":"account.acceptAuthorization","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"},{"name":"value_hashes","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"Bool"},{"id":"-1516022023","method":"account.sendVerifyPhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1305716726","method":"account.verifyPhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"1880182943","method":"account.sendVerifyEmailCode","params":[{"name":"email","type":"string"}],"type":"account.SentEmailCode"},{"id":"-323339813","method":"account.verifyEmail","params":[{"name":"email","type":"string"},{"name":"code","type":"string"}],"type":"Bool"},{"id":"1072547679","method":"help.getDeepLinkInfo","params":[{"name":"path","type":"string"}],"type":"help.DeepLinkInfo"},{"id":"-2098076769","method":"contacts.getSaved","params":[],"type":"Vector"},{"id":"-2092831552","method":"channels.getLeftChannels","params":[{"name":"offset","type":"int"}],"type":"messages.Chats"},{"id":"-262453244","method":"account.initTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"message_users","type":"flags.1?true"},{"name":"message_chats","type":"flags.2?true"},{"name":"message_megagroups","type":"flags.3?true"},{"name":"message_channels","type":"flags.4?true"},{"name":"files","type":"flags.5?true"},{"name":"file_max_size","type":"flags.5?int"}],"type":"account.Takeout"},{"id":"489050862","method":"account.finishTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.0?true"}],"type":"Bool"},{"id":"486505992","method":"messages.getSplitRanges","params":[],"type":"Vector"},{"id":"911373810","method":"invokeWithMessagesRange","params":[{"name":"range","type":"MessageRange"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1398145746","method":"invokeWithTakeout","params":[{"name":"takeout_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1031349873","method":"messages.markDialogUnread","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"585256482","method":"messages.getDialogUnreadMarks","params":[],"type":"Vector"},{"id":"-2062238246","method":"contacts.toggleTopPeers","params":[{"name":"enabled","type":"Bool"}],"type":"Bool"},{"id":"2119757468","method":"messages.clearAllDrafts","params":[],"type":"Bool"},{"id":"-1735311088","method":"help.getAppConfig","params":[],"type":"JSONValue"},{"id":"1862465352","method":"help.saveAppLog","params":[{"name":"events","type":"Vector"}],"type":"Bool"},{"id":"-966677240","method":"help.getPassportConfig","params":[{"name":"hash","type":"int"}],"type":"help.PassportConfig"},{"id":"1784243458","method":"langpack.getLanguage","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackLanguage"},{"id":"-760547348","method":"messages.updatePinnedMessage","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"unpin","type":"flags.1?true"},{"name":"pm_oneside","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"Updates"},{"id":"-1881204448","method":"account.confirmPasswordEmail","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"2055154197","method":"account.resendPasswordEmail","params":[],"type":"Bool"},{"id":"-1043606090","method":"account.cancelPasswordEmail","params":[],"type":"Bool"},{"id":"-748624084","method":"help.getSupportName","params":[],"type":"help.SupportName"},{"id":"59377875","method":"help.getUserInfo","params":[{"name":"user_id","type":"InputUser"}],"type":"help.UserInfo"},{"id":"1723407216","method":"help.editUserInfo","params":[{"name":"user_id","type":"InputUser"},{"name":"message","type":"string"},{"name":"entities","type":"Vector"}],"type":"help.UserInfo"},{"id":"-1626880216","method":"account.getContactSignUpNotification","params":[],"type":"Bool"},{"id":"-806076575","method":"account.setContactSignUpNotification","params":[{"name":"silent","type":"Bool"}],"type":"Bool"},{"id":"1398240377","method":"account.getNotifyExceptions","params":[{"name":"flags","type":"#"},{"name":"compare_sound","type":"flags.1?true"},{"name":"peer","type":"flags.0?InputNotifyPeer"}],"type":"Updates"},{"id":"283795844","method":"messages.sendVote","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"options","type":"Vector"}],"type":"Updates"},{"id":"1941660731","method":"messages.getPollResults","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1848369232","method":"messages.getOnlines","params":[{"name":"peer","type":"InputPeer"}],"type":"ChatOnlines"},{"id":"-554301545","method":"messages.editChatAbout","params":[{"name":"peer","type":"InputPeer"},{"name":"about","type":"string"}],"type":"Bool"},{"id":"-1517917375","method":"messages.editChatDefaultBannedRights","params":[{"name":"peer","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"-57811990","method":"account.getWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"}],"type":"WallPaper"},{"id":"-578472351","method":"account.uploadWallPaper","params":[{"name":"file","type":"InputFile"},{"name":"mime_type","type":"string"},{"name":"settings","type":"WallPaperSettings"}],"type":"WallPaper"},{"id":"1817860919","method":"account.saveWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"unsave","type":"Bool"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-18000023","method":"account.installWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-1153722364","method":"account.resetWallPapers","params":[],"type":"Bool"},{"id":"1457130303","method":"account.getAutoDownloadSettings","params":[],"type":"account.AutoDownloadSettings"},{"id":"1995661875","method":"account.saveAutoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"low","type":"flags.0?true"},{"name":"high","type":"flags.1?true"},{"name":"settings","type":"AutoDownloadSettings"}],"type":"Bool"},{"id":"899735650","method":"messages.getEmojiKeywords","params":[{"name":"lang_code","type":"string"}],"type":"EmojiKeywordsDifference"},{"id":"352892591","method":"messages.getEmojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"EmojiKeywordsDifference"},{"id":"1318675378","method":"messages.getEmojiKeywordsLanguages","params":[{"name":"lang_codes","type":"Vector"}],"type":"Vector"},{"id":"-709817306","method":"messages.getEmojiURL","params":[{"name":"lang_code","type":"string"}],"type":"EmojiURL"},{"id":"1749536939","method":"folders.editPeerFolders","params":[{"name":"folder_peers","type":"Vector"}],"type":"Updates"},{"id":"472471681","method":"folders.deleteFolder","params":[{"name":"folder_id","type":"int"}],"type":"Updates"},{"id":"1932455680","method":"messages.getSearchCounters","params":[{"name":"peer","type":"InputPeer"},{"name":"filters","type":"Vector"}],"type":"Vector"},{"id":"-170208392","method":"channels.getGroupsForDiscussion","params":[],"type":"messages.Chats"},{"id":"1079520178","method":"channels.setDiscussionGroup","params":[{"name":"broadcast","type":"InputChannel"},{"name":"group","type":"InputChannel"}],"type":"Bool"},{"id":"428848198","method":"messages.requestUrlAuth","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"-1322487515","method":"messages.acceptUrlAuth","params":[{"name":"flags","type":"#"},{"name":"write_allowed","type":"flags.0?true"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"1336717624","method":"messages.hidePeerSettingsBar","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-386636848","method":"contacts.addContact","params":[{"name":"flags","type":"#"},{"name":"add_phone_privacy_exception","type":"flags.0?true"},{"name":"id","type":"InputUser"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"phone","type":"string"}],"type":"Updates"},{"id":"-130964977","method":"contacts.acceptContact","params":[{"name":"id","type":"InputUser"}],"type":"Updates"},{"id":"-1892102881","method":"channels.editCreator","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"password","type":"InputCheckPasswordSRP"}],"type":"Updates"},{"id":"-750207932","method":"contacts.getLocated","params":[{"name":"flags","type":"#"},{"name":"background","type":"flags.1?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"self_expires","type":"flags.0?int"}],"type":"Updates"},{"id":"1491484525","method":"channels.editLocation","params":[{"name":"channel","type":"InputChannel"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"address","type":"string"}],"type":"Bool"},{"id":"-304832784","method":"channels.toggleSlowMode","params":[{"name":"channel","type":"InputChannel"},{"name":"seconds","type":"int"}],"type":"Updates"},{"id":"-183077365","method":"messages.getScheduledHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1111817116","method":"messages.getScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1120369398","method":"messages.sendScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"1504586518","method":"messages.deleteScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"473805619","method":"account.uploadTheme","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.0?InputFile"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1697530880","method":"account.createTheme","params":[{"name":"flags","type":"#"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?Vector"}],"type":"Theme"},{"id":"737414348","method":"account.updateTheme","params":[{"name":"flags","type":"#"},{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"slug","type":"flags.0?string"},{"name":"title","type":"flags.1?string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?Vector"}],"type":"Theme"},{"id":"-229175188","method":"account.saveTheme","params":[{"name":"theme","type":"InputTheme"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-953697477","method":"account.installTheme","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"theme","type":"flags.1?InputTheme"},{"name":"format","type":"flags.2?string"},{"name":"base_theme","type":"flags.3?BaseTheme"}],"type":"Bool"},{"id":"-1919060949","method":"account.getTheme","params":[{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"document_id","type":"long"}],"type":"Theme"},{"id":"1913054296","method":"account.getThemes","params":[{"name":"format","type":"string"},{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-1210022402","method":"auth.exportLoginToken","params":[{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"except_ids","type":"Vector"}],"type":"auth.LoginToken"},{"id":"-1783866140","method":"auth.importLoginToken","params":[{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"-392909491","method":"auth.acceptLoginToken","params":[{"name":"token","type":"bytes"}],"type":"Authorization"},{"id":"-1250643605","method":"account.setContentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"}],"type":"Bool"},{"id":"-1952756306","method":"account.getContentSettings","params":[],"type":"account.ContentSettings"},{"id":"300429806","method":"channels.getInactiveChannels","params":[],"type":"messages.InactiveChats"},{"id":"1705865692","method":"account.getMultiWallPapers","params":[{"name":"wallpapers","type":"Vector"}],"type":"Vector"},{"id":"-1200736242","method":"messages.getPollVotes","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"option","type":"flags.0?bytes"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.VotesList"},{"id":"-1257951254","method":"messages.toggleStickerSets","params":[{"name":"flags","type":"#"},{"name":"uninstall","type":"flags.0?true"},{"name":"archive","type":"flags.1?true"},{"name":"unarchive","type":"flags.2?true"},{"name":"stickersets","type":"Vector"}],"type":"Bool"},{"id":"779736953","method":"payments.getBankCardData","params":[{"name":"number","type":"string"}],"type":"payments.BankCardData"},{"id":"-241247891","method":"messages.getDialogFilters","params":[],"type":"Vector"},{"id":"-1566780372","method":"messages.getSuggestedDialogFilters","params":[],"type":"Vector"},{"id":"450142282","method":"messages.updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Bool"},{"id":"-983318044","method":"messages.updateDialogFiltersOrder","params":[{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-1421720550","method":"stats.getBroadcastStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.BroadcastStats"},{"id":"1646092192","method":"stats.loadAsyncGraph","params":[{"name":"flags","type":"#"},{"name":"token","type":"string"},{"name":"x","type":"flags.0?long"}],"type":"StatsGraph"},{"id":"-1707717072","method":"stickers.setStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"85399130","method":"bots.setBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"},{"name":"commands","type":"Vector"}],"type":"Bool"},{"id":"2127598753","method":"messages.getOldFeaturedStickers","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"-1063816159","method":"help.getPromoData","params":[],"type":"help.PromoData"},{"id":"505748629","method":"help.hidePromoData","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-8744061","method":"phone.sendSignalingData","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"data","type":"bytes"}],"type":"Bool"},{"id":"-589330937","method":"stats.getMegagroupStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.MegagroupStats"},{"id":"-349483786","method":"account.getGlobalPrivacySettings","params":[],"type":"GlobalPrivacySettings"},{"id":"517647042","method":"account.setGlobalPrivacySettings","params":[{"name":"settings","type":"GlobalPrivacySettings"}],"type":"GlobalPrivacySettings"},{"id":"-183649631","method":"help.dismissSuggestion","params":[{"name":"peer","type":"InputPeer"},{"name":"suggestion","type":"string"}],"type":"Bool"},{"id":"1935116200","method":"help.getCountriesList","params":[{"name":"lang_code","type":"string"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"584962828","method":"messages.getReplies","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"1147761405","method":"messages.getDiscussionMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"messages.DiscussionMessage"},{"id":"-147740172","method":"messages.readDiscussion","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Bool"},{"id":"698914348","method":"contacts.blockFromReplies","params":[{"name":"flags","type":"#"},{"name":"delete_message","type":"flags.0?true"},{"name":"delete_history","type":"flags.1?true"},{"name":"report_spam","type":"flags.2?true"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1445996571","method":"stats.getMessagePublicForwards","params":[{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"-1226791947","method":"stats.getMessageStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"}],"type":"stats.MessageStats"},{"id":"-265962357","method":"messages.unpinAllMessages","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1221445336","method":"phone.createGroupCall","params":[{"name":"flags","type":"#"},{"name":"rtmp_stream","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"schedule_date","type":"flags.1?int"}],"type":"Updates"},{"id":"-1322057861","method":"phone.joinGroupCall","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"video_stopped","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_as","type":"InputPeer"},{"name":"invite_hash","type":"flags.1?string"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"1342404601","method":"phone.leaveGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"source","type":"int"}],"type":"Updates"},{"id":"2067345760","method":"phone.inviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"2054648117","method":"phone.discardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1958458429","method":"phone.toggleGroupCallSettings","params":[{"name":"flags","type":"#"},{"name":"reset_invite_hash","type":"flags.1?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_muted","type":"flags.0?Bool"}],"type":"Updates"},{"id":"68699611","method":"phone.getGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"limit","type":"int"}],"type":"phone.GroupCall"},{"id":"-984033109","method":"phone.getGroupParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"ids","type":"Vector"},{"name":"sources","type":"Vector"},{"name":"offset","type":"string"},{"name":"limit","type":"int"}],"type":"phone.GroupParticipants"},{"id":"-1248003721","method":"phone.checkGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"sources","type":"Vector"}],"type":"Vector"},{"id":"1540419152","method":"messages.deleteChat","params":[{"name":"chat_id","type":"long"}],"type":"Bool"},{"id":"-104078327","method":"messages.deletePhoneCallHistory","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"}],"type":"messages.AffectedFoundMessages"},{"id":"1140726259","method":"messages.checkHistoryImport","params":[{"name":"import_head","type":"string"}],"type":"messages.HistoryImportParsed"},{"id":"873008187","method":"messages.initHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"file","type":"InputFile"},{"name":"media_count","type":"int"}],"type":"messages.HistoryImport"},{"id":"713433234","method":"messages.uploadImportedMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"},{"name":"file_name","type":"string"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"-1271008444","method":"messages.startHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"}],"type":"Bool"},{"id":"-1565154314","method":"messages.getExportedChatInvites","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"},{"name":"offset_date","type":"flags.2?int"},{"name":"offset_link","type":"flags.2?string"},{"name":"limit","type":"int"}],"type":"messages.ExportedChatInvites"},{"id":"1937010524","method":"messages.getExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"messages.ExportedChatInvite"},{"id":"-1110823051","method":"messages.editExportedChatInvite","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"},{"name":"request_needed","type":"flags.3?Bool"},{"name":"title","type":"flags.4?string"}],"type":"messages.ExportedChatInvite"},{"id":"1452833749","method":"messages.deleteRevokedExportedChatInvites","params":[{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"}],"type":"Bool"},{"id":"-731601877","method":"messages.deleteExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"Bool"},{"id":"958457583","method":"messages.getAdminsWithInvites","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.ChatAdminsWithInvites"},{"id":"-553329330","method":"messages.getChatInviteImporters","params":[{"name":"flags","type":"#"},{"name":"requested","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"flags.1?string"},{"name":"q","type":"flags.2?string"},{"name":"offset_date","type":"int"},{"name":"offset_user","type":"InputUser"},{"name":"limit","type":"int"}],"type":"messages.ChatInviteImporters"},{"id":"-1207017500","method":"messages.setHistoryTTL","params":[{"name":"peer","type":"InputPeer"},{"name":"period","type":"int"}],"type":"Updates"},{"id":"-91437323","method":"account.reportProfilePhoto","params":[{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"InputPhoto"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"187239529","method":"channels.convertToGigagroup","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"1573261059","method":"messages.checkHistoryImportPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"-248985848","method":"phone.toggleGroupCallRecord","params":[{"name":"flags","type":"#"},{"name":"start","type":"flags.0?true"},{"name":"video","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"title","type":"flags.1?string"},{"name":"video_portrait","type":"flags.2?Bool"}],"type":"Updates"},{"id":"-1524155713","method":"phone.editGroupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"participant","type":"InputPeer"},{"name":"muted","type":"flags.0?Bool"},{"name":"volume","type":"flags.1?int"},{"name":"raise_hand","type":"flags.2?Bool"},{"name":"video_stopped","type":"flags.3?Bool"},{"name":"video_paused","type":"flags.4?Bool"},{"name":"presentation_paused","type":"flags.5?Bool"}],"type":"Updates"},{"id":"480685066","method":"phone.editGroupCallTitle","params":[{"name":"call","type":"InputGroupCall"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-277077702","method":"phone.getGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"}],"type":"phone.JoinAsPeers"},{"id":"-425040769","method":"phone.exportGroupCallInvite","params":[{"name":"flags","type":"#"},{"name":"can_self_unmute","type":"flags.0?true"},{"name":"call","type":"InputGroupCall"}],"type":"phone.ExportedGroupCallInvite"},{"id":"563885286","method":"phone.toggleGroupCallStartSubscription","params":[{"name":"call","type":"InputGroupCall"},{"name":"subscribed","type":"Bool"}],"type":"Updates"},{"id":"1451287362","method":"phone.startScheduledGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1465786252","method":"phone.saveDefaultGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"},{"name":"join_as","type":"InputPeer"}],"type":"Bool"},{"id":"-873829436","method":"phone.joinGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"475058500","method":"phone.leaveGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"676017721","method":"stickers.checkShortName","params":[{"name":"short_name","type":"string"}],"type":"Bool"},{"id":"1303364867","method":"stickers.suggestShortName","params":[{"name":"title","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"1032708345","method":"bots.resetBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Bool"},{"id":"-481554986","method":"bots.getBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Vector"},{"id":"-1828139493","method":"account.resetPassword","params":[],"type":"account.ResetPasswordResult"},{"id":"1284770294","method":"account.declinePasswordReset","params":[],"type":"Bool"},{"id":"221691769","method":"auth.checkRecoveryPassword","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"-700916087","method":"account.getChatThemes","params":[{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-432283329","method":"messages.setChatTheme","params":[{"name":"peer","type":"InputPeer"},{"name":"emoticon","type":"string"}],"type":"Updates"},{"id":"-1095836780","method":"channels.viewSponsoredMessage","params":[{"name":"channel","type":"InputChannel"},{"name":"random_id","type":"bytes"}],"type":"Bool"},{"id":"-333377601","method":"channels.getSponsoredMessages","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.SponsoredMessages"},{"id":"745510839","method":"messages.getMessageReadParticipants","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Vector"},{"id":"1240514025","method":"messages.getSearchResultsCalendar","params":[{"name":"peer","type":"InputPeer"},{"name":"filter","type":"MessagesFilter"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"}],"type":"messages.SearchResultsCalendar"},{"id":"1855292323","method":"messages.getSearchResultsPositions","params":[{"name":"peer","type":"InputPeer"},{"name":"filter","type":"MessagesFilter"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.SearchResultsPositions"},{"id":"2145904661","method":"messages.hideChatJoinRequest","params":[{"name":"flags","type":"#"},{"name":"approved","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"-528091926","method":"messages.hideAllChatJoinRequests","params":[{"name":"flags","type":"#"},{"name":"approved","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"flags.1?string"}],"type":"Updates"},{"id":"-1323389022","method":"messages.toggleNoForwards","params":[{"name":"peer","type":"InputPeer"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"-855777386","method":"messages.saveDefaultSendAs","params":[{"name":"peer","type":"InputPeer"},{"name":"send_as","type":"InputPeer"}],"type":"Bool"},{"id":"231174382","method":"channels.getSendAs","params":[{"name":"peer","type":"InputPeer"}],"type":"channels.SendAsPeers"},{"id":"-1081501024","method":"account.setAuthorizationTTL","params":[{"name":"authorization_ttl_days","type":"int"}],"type":"Bool"},{"id":"1089766498","method":"account.changeAuthorizationSettings","params":[{"name":"flags","type":"#"},{"name":"hash","type":"long"},{"name":"encrypted_requests_disabled","type":"flags.0?Bool"},{"name":"call_requests_disabled","type":"flags.1?Bool"}],"type":"Bool"},{"id":"913655003","method":"channels.deleteParticipantHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"627641572","method":"messages.sendReaction","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"reaction","type":"flags.0?string"}],"type":"Updates"},{"id":"-1950707482","method":"messages.getMessagesReactions","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"-521245833","method":"messages.getMessageReactionsList","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"reaction","type":"flags.0?string"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.MessageReactionsList"},{"id":"335875750","method":"messages.setChatAvailableReactions","params":[{"name":"peer","type":"InputPeer"},{"name":"available_reactions","type":"Vector"}],"type":"Updates"},{"id":"417243308","method":"messages.getAvailableReactions","params":[{"name":"hash","type":"int"}],"type":"messages.AvailableReactions"},{"id":"-647969580","method":"messages.setDefaultReaction","params":[{"name":"reaction","type":"string"}],"type":"Bool"},{"id":"617508334","method":"messages.translateText","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.0?InputPeer"},{"name":"msg_id","type":"flags.0?int"},{"name":"text","type":"flags.1?string"},{"name":"from_lang","type":"flags.2?string"},{"name":"to_lang","type":"string"}],"type":"messages.TranslatedText"},{"id":"-396644838","method":"messages.getUnreadReactions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-2099097129","method":"messages.readReactions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"}]} \ No newline at end of file diff --git a/data/corefork.telegram.org/type/BotInlineMessage.html b/data/corefork.telegram.org/type/BotInlineMessage.html new file mode 100644 index 0000000000..f4ea00a705 --- /dev/null +++ b/data/corefork.telegram.org/type/BotInlineMessage.html @@ -0,0 +1,168 @@ + + + + + BotInlineMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

BotInlineMessage

+ +

Inline message

+

+ +
+
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
+botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
botInlineMessageMediaAutoSend whatever media is attached to the botInlineMediaResult
botInlineMessageTextSend a simple text message
botInlineMessageMediaGeoSend a geolocation
botInlineMessageMediaVenueSend a venue
botInlineMessageMediaContactSend a contact
botInlineMessageMediaInvoiceSend an invoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEvent.html b/data/corefork.telegram.org/type/ChannelAdminLogEvent.html new file mode 100644 index 0000000000..ea8cf07dff --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelAdminLogEvent.html @@ -0,0 +1,143 @@ + + + + + ChannelAdminLogEvent + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelAdminLogEvent

+ +

An event in a channel admin log

+

+ +
+
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
channelAdminLogEventAdmin log event
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelLocation.html b/data/corefork.telegram.org/type/ChannelLocation.html new file mode 100644 index 0000000000..c966b75734 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelLocation.html @@ -0,0 +1,148 @@ + + + + + ChannelLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelLocation

+ +

Geographical location of supergroup (geogroups)

+

+ +
+
channelLocationEmpty#bfb5ad8b = ChannelLocation;
+channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channelLocationEmptyNo location (normal supergroup)
channelLocationGeographical location of supergroup (geogroups)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelMessagesFilter.html b/data/corefork.telegram.org/type/ChannelMessagesFilter.html new file mode 100644 index 0000000000..901f70b731 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelMessagesFilter.html @@ -0,0 +1,148 @@ + + + + + ChannelMessagesFilter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelMessagesFilter

+ +

Filter for fetching only certain types of channel messages

+

+ +
+
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
+channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
channelMessagesFilterEmptyNo filter
channelMessagesFilterFilter for getting only certain types of channel messages
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChannelParticipant.html b/data/corefork.telegram.org/type/ChannelParticipant.html new file mode 100644 index 0000000000..cac59fdde8 --- /dev/null +++ b/data/corefork.telegram.org/type/ChannelParticipant.html @@ -0,0 +1,168 @@ + + + + + ChannelParticipant + + + + + + + + + + + + + +
+ +
+
+
+ +

ChannelParticipant

+ +

Channel participant

+

+ +
+
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
+channelParticipantSelf#35a8bfa7 flags:# via_request:flags.0?true user_id:long inviter_id:long date:int = ChannelParticipant;
+channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
+channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
+channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
+channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
channelParticipantChannel/supergroup participant
channelParticipantSelfMyself
channelParticipantCreatorChannel/supergroup creator
channelParticipantAdminAdmin
channelParticipantBannedBanned/kicked user
channelParticipantLeftA participant that left the channel/supergroup
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Chat.html b/data/corefork.telegram.org/type/Chat.html new file mode 100644 index 0000000000..379b4fd8c5 --- /dev/null +++ b/data/corefork.telegram.org/type/Chat.html @@ -0,0 +1,163 @@ + + + + + Chat + + + + + + + + + + + + + +
+ +
+
+
+ +

Chat

+ +

Object defines a group.

+

+ +
+
chatEmpty#29562865 id:long = Chat;
+chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
+chatForbidden#6592a1a7 id:long title:string = Chat;
+channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
+channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
chatEmptyEmpty constructor, group doesn't exist
chatInfo about a group
chatForbiddenA group to which the user has no access. E.g., because the user was kicked from the group.
channelChannel/supergroup info
channelForbiddenIndicates a channel/supergroup we can't access because we were banned, or for some other reason.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatAdminRights.html b/data/corefork.telegram.org/type/ChatAdminRights.html new file mode 100644 index 0000000000..c3f792e9dc --- /dev/null +++ b/data/corefork.telegram.org/type/ChatAdminRights.html @@ -0,0 +1,146 @@ + + + + + ChatAdminRights + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatAdminRights

+ +

Represents the rights of an admin in a channel/supergroup.

+

+ +
+
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatAdminRightsRepresents the rights of an admin in a channel/supergroup.
+

Related pages

+

Channels

+

How to handle channels, supergroups, groups, and what's the difference between them.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatInviteImporter.html b/data/corefork.telegram.org/type/ChatInviteImporter.html new file mode 100644 index 0000000000..2d8f4b413e --- /dev/null +++ b/data/corefork.telegram.org/type/ChatInviteImporter.html @@ -0,0 +1,143 @@ + + + + + ChatInviteImporter + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatInviteImporter

+ +

When and which user joined the chat using a chat invite

+

+ +
+
chatInviteImporter#8c5adfd9 flags:# requested:flags.0?true user_id:long date:int about:flags.2?string approved_by:flags.1?long = ChatInviteImporter;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
chatInviteImporterWhen and which user joined the chat using a chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ChatTheme.html b/data/corefork.telegram.org/type/ChatTheme.html new file mode 100644 index 0000000000..50291e9445 --- /dev/null +++ b/data/corefork.telegram.org/type/ChatTheme.html @@ -0,0 +1,128 @@ + + + + + ChatTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

ChatTheme

+ +

A chat theme

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Config.html b/data/corefork.telegram.org/type/Config.html new file mode 100644 index 0000000000..a4663d6648 --- /dev/null +++ b/data/corefork.telegram.org/type/Config.html @@ -0,0 +1,162 @@ + + + + + Config + + + + + + + + + + + + + +
+ +
+
+
+ +

Config

+ +

Object contains info on API configuring parameters.

+

+ +
+
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
+
+---functions---
+
+help.getConfig#c4f9186b = Config;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
configCurrent configuration
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getConfigReturns current configuration, icluding data center configuration.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Contact.html b/data/corefork.telegram.org/type/Contact.html new file mode 100644 index 0000000000..51edfe5820 --- /dev/null +++ b/data/corefork.telegram.org/type/Contact.html @@ -0,0 +1,143 @@ + + + + + Contact + + + + + + + + + + + + + +
+ +
+
+
+ +

Contact

+ +

A contact of the current user.

+

+ +
+
contact#145ade0b user_id:long mutual:Bool = Contact;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contactA contact of the current user that is registered in the system.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ContactStatus.html b/data/corefork.telegram.org/type/ContactStatus.html new file mode 100644 index 0000000000..f4289fcd13 --- /dev/null +++ b/data/corefork.telegram.org/type/ContactStatus.html @@ -0,0 +1,143 @@ + + + + + ContactStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

ContactStatus

+ +

Contact status: online / offline.

+

+ +
+
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contactStatusContact status: online / offline.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EncryptedChat.html b/data/corefork.telegram.org/type/EncryptedChat.html new file mode 100644 index 0000000000..6de4f92c10 --- /dev/null +++ b/data/corefork.telegram.org/type/EncryptedChat.html @@ -0,0 +1,187 @@ + + + + + EncryptedChat + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedChat

+ +

Object contains info on an encrypted chat.

+

+ +
+
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
+encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
+encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
+encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
+encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
+
+---functions---
+
+messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
+messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedChatEmptyEmpty constructor.
encryptedChatWaitingChat waiting for approval of second participant.
encryptedChatRequestedRequest to create an encrypted chat.
encryptedChatEncrypted chat
encryptedChatDiscardedDiscarded or deleted chat.
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.acceptEncryptionConfirms creation of a secret chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/EncryptedMessage.html b/data/corefork.telegram.org/type/EncryptedMessage.html new file mode 100644 index 0000000000..8f34aa77ce --- /dev/null +++ b/data/corefork.telegram.org/type/EncryptedMessage.html @@ -0,0 +1,148 @@ + + + + + EncryptedMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

EncryptedMessage

+ +

Object contains encrypted message.

+

+ +
+
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
+encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
encryptedMessageEncrypted message.
encryptedMessageServiceEncrypted service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/GroupCall.html b/data/corefork.telegram.org/type/GroupCall.html new file mode 100644 index 0000000000..0ad0da18eb --- /dev/null +++ b/data/corefork.telegram.org/type/GroupCall.html @@ -0,0 +1,148 @@ + + + + + GroupCall + + + + + + + + + + + + + +
+ +
+
+
+ +

GroupCall

+ +

A group call

+

+ +
+
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
+groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true rtmp_stream:flags.12?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
groupCallDiscardedAn ended group call
groupCallInfo about a group call or livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputBotInlineResult.html b/data/corefork.telegram.org/type/InputBotInlineResult.html new file mode 100644 index 0000000000..e03c4c89ab --- /dev/null +++ b/data/corefork.telegram.org/type/InputBotInlineResult.html @@ -0,0 +1,158 @@ + + + + + InputBotInlineResult + + + + + + + + + + + + + +
+ +
+
+
+ +

InputBotInlineResult

+ +

Inline bot result

+

+ +
+
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
+inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputBotInlineResultAn inline bot result
inputBotInlineResultPhotoPhoto
inputBotInlineResultDocumentDocument (media of any type except for photos)
inputBotInlineResultGameGame
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputCheckPasswordSRP.html b/data/corefork.telegram.org/type/InputCheckPasswordSRP.html new file mode 100644 index 0000000000..f2a6fd24cf --- /dev/null +++ b/data/corefork.telegram.org/type/InputCheckPasswordSRP.html @@ -0,0 +1,151 @@ + + + + + InputCheckPasswordSRP + + + + + + + + + + + + + +
+ +
+
+
+ +

InputCheckPasswordSRP

+ +

Constructors for checking the validity of a 2FA SRP password

+

+ +
+
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
+inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputCheckPasswordEmptyThere is no password
inputCheckPasswordSRPConstructor for checking the validity of a 2FA SRP password (see SRP)
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputFileLocation.html b/data/corefork.telegram.org/type/InputFileLocation.html new file mode 100644 index 0000000000..7801cd22fc --- /dev/null +++ b/data/corefork.telegram.org/type/InputFileLocation.html @@ -0,0 +1,188 @@ + + + + + InputFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

InputFileLocation

+ +

Defines the location of a file for download.

+

+ +
+
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
+inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
+inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
+inputTakeoutFileLocation#29be5899 = InputFileLocation;
+inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
+inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
+inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
+inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
+inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
inputFileLocationDEPRECATED location of a photo
inputEncryptedFileLocationLocation of encrypted secret chat file.
inputDocumentFileLocationDocument location (video, voice, audio, basically every type except photo)
inputSecureFileLocationLocation of encrypted telegram passport file.
inputTakeoutFileLocationEmpty constructor for takeout
inputPhotoFileLocationUse this object to download a photo with upload.getFile method
inputPhotoLegacyFileLocationLegacy file location
inputPeerPhotoFileLocationLocation of profile photo of channel/group/supergroup/user
inputStickerSetThumbLocation of stickerset thumbnail (see files)
inputGroupCallStreamChunk of a livestream
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputGeoPoint.html b/data/corefork.telegram.org/type/InputGeoPoint.html new file mode 100644 index 0000000000..25dbb13485 --- /dev/null +++ b/data/corefork.telegram.org/type/InputGeoPoint.html @@ -0,0 +1,148 @@ + + + + + InputGeoPoint + + + + + + + + + + + + + +
+ +
+
+
+ +

InputGeoPoint

+ +

Defines a GeoPoint.

+

+ +
+
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
+inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputGeoPointEmptyEmpty GeoPoint constructor.
inputGeoPointDefines a GeoPoint by its coordinates.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputPeerNotifySettings.html b/data/corefork.telegram.org/type/InputPeerNotifySettings.html new file mode 100644 index 0000000000..6be11a8be9 --- /dev/null +++ b/data/corefork.telegram.org/type/InputPeerNotifySettings.html @@ -0,0 +1,143 @@ + + + + + InputPeerNotifySettings + + + + + + + + + + + + + +
+ +
+
+
+ +

InputPeerNotifySettings

+ +

Notifications settings.

+

+ +
+
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputPeerNotifySettingsNotification settings.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputSecureValue.html b/data/corefork.telegram.org/type/InputSecureValue.html new file mode 100644 index 0000000000..ae48e299cd --- /dev/null +++ b/data/corefork.telegram.org/type/InputSecureValue.html @@ -0,0 +1,145 @@ + + + + + InputSecureValue + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSecureValue

+ +

Secure value, for more info see the passport docs »

+

+ +
+
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputSecureValueSecure value, for more info see the passport docs »
+

Related pages

+

Telegram Passport Encryption Details

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputSingleMedia.html b/data/corefork.telegram.org/type/InputSingleMedia.html new file mode 100644 index 0000000000..e67e43c65c --- /dev/null +++ b/data/corefork.telegram.org/type/InputSingleMedia.html @@ -0,0 +1,148 @@ + + + + + InputSingleMedia + + + + + + + + + + + + + +
+ +
+
+
+ +

InputSingleMedia

+ +

A single media in an album or grouped media sent with messages.sendMultiMedia.

+

+ +
+
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputSingleMediaA single media in an album or grouped media sent with messages.sendMultiMedia.
+

Related pages

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

messages.sendMultiMedia

+

Send an album or grouped media

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputStickerSetItem.html b/data/corefork.telegram.org/type/InputStickerSetItem.html new file mode 100644 index 0000000000..7f1403bb69 --- /dev/null +++ b/data/corefork.telegram.org/type/InputStickerSetItem.html @@ -0,0 +1,143 @@ + + + + + InputStickerSetItem + + + + + + + + + + + + + +
+ +
+
+
+ +

InputStickerSetItem

+ +

Sticker

+

+ +
+
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputStickerSetItemSticker in a stickerset
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputTheme.html b/data/corefork.telegram.org/type/InputTheme.html new file mode 100644 index 0000000000..446de96479 --- /dev/null +++ b/data/corefork.telegram.org/type/InputTheme.html @@ -0,0 +1,148 @@ + + + + + InputTheme + + + + + + + + + + + + + +
+ +
+
+
+ +

InputTheme

+ +

Cloud theme

+

+ +
+
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
+inputThemeSlug#f5890df1 slug:string = InputTheme;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputThemeTheme
inputThemeSlugTheme by theme ID
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputWebDocument.html b/data/corefork.telegram.org/type/InputWebDocument.html new file mode 100644 index 0000000000..bf5510e59d --- /dev/null +++ b/data/corefork.telegram.org/type/InputWebDocument.html @@ -0,0 +1,143 @@ + + + + + InputWebDocument + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWebDocument

+ +

Specifies a document that will have to be downloaded from the URL by the telegram servers

+

+ +
+
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
inputWebDocumentThe document
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/InputWebFileLocation.html b/data/corefork.telegram.org/type/InputWebFileLocation.html new file mode 100644 index 0000000000..7e5f504cd2 --- /dev/null +++ b/data/corefork.telegram.org/type/InputWebFileLocation.html @@ -0,0 +1,148 @@ + + + + + InputWebFileLocation + + + + + + + + + + + + + +
+ +
+
+
+ +

InputWebFileLocation

+ +

Location of remote file

+

+ +
+
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
+inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
inputWebFileLocationLocation of a remote HTTP(s) file
inputWebFileGeoPointLocationGeolocation
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Invoice.html b/data/corefork.telegram.org/type/Invoice.html new file mode 100644 index 0000000000..6aaae7acce --- /dev/null +++ b/data/corefork.telegram.org/type/Invoice.html @@ -0,0 +1,143 @@ + + + + + Invoice + + + + + + + + + + + + + +
+ +
+
+
+ +

Invoice

+ +

Invoice

+

+ +
+
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
invoiceInvoice
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/LabeledPrice.html b/data/corefork.telegram.org/type/LabeledPrice.html new file mode 100644 index 0000000000..adbae6bd2f --- /dev/null +++ b/data/corefork.telegram.org/type/LabeledPrice.html @@ -0,0 +1,143 @@ + + + + + LabeledPrice + + + + + + + + + + + + + +
+ +
+
+
+ +

LabeledPrice

+ +

Labeled pricetag

+

+ +
+
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
labeledPriceThis object represents a portion of the price for goods or services.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/LangPackLanguage.html b/data/corefork.telegram.org/type/LangPackLanguage.html new file mode 100644 index 0000000000..683ff0d16b --- /dev/null +++ b/data/corefork.telegram.org/type/LangPackLanguage.html @@ -0,0 +1,162 @@ + + + + + LangPackLanguage + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackLanguage

+ +

Language pack language

+

+ +
+
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
+
+---functions---
+
+langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
langPackLanguageIdentifies a localization pack
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
langpack.getLanguageGet information about a language in a localization pack
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/LangPackString.html b/data/corefork.telegram.org/type/LangPackString.html new file mode 100644 index 0000000000..872f6b3649 --- /dev/null +++ b/data/corefork.telegram.org/type/LangPackString.html @@ -0,0 +1,153 @@ + + + + + LangPackString + + + + + + + + + + + + + +
+ +
+
+
+ +

LangPackString

+ +

Language pack string

+

+ +
+
langPackString#cad181f6 key:string value:string = LangPackString;
+langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
+langPackStringDeleted#2979eeb2 key:string = LangPackString;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
langPackStringTranslated localization string
langPackStringPluralizedA language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
langPackStringDeletedDeleted localization string
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/Message.html b/data/corefork.telegram.org/type/Message.html new file mode 100644 index 0000000000..090e1edae2 --- /dev/null +++ b/data/corefork.telegram.org/type/Message.html @@ -0,0 +1,153 @@ + + + + + Message + + + + + + + + + + + + + +
+ +
+
+
+ +

Message

+ +

Object describing a message.

+

+ +
+
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
+message#38116ee0 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
+messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageEmptyEmpty constructor, non-existent message.
messageA message
messageServiceIndicates a service message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageEntity.html b/data/corefork.telegram.org/type/MessageEntity.html new file mode 100644 index 0000000000..d959b509fa --- /dev/null +++ b/data/corefork.telegram.org/type/MessageEntity.html @@ -0,0 +1,238 @@ + + + + + MessageEntity + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageEntity

+ +

Message entities, representing styled text in a message

+

+ +
+
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
+messageEntityMention#fa04579d offset:int length:int = MessageEntity;
+messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
+messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
+messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
+messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
+messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
+messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
+messageEntityCode#28a20571 offset:int length:int = MessageEntity;
+messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
+messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
+messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
+inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
+messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
+messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
+messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
+messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
+messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
+messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;
+messageEntitySpoiler#32ca960f offset:int length:int = MessageEntity;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
messageEntityUnknownUnknown message entity
messageEntityMentionMessage entity mentioning the current user
messageEntityHashtag#hashtag message entity
messageEntityBotCommandMessage entity representing a bot /command
messageEntityUrlMessage entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
messageEntityEmailMessage entity representing an email@example.com.
messageEntityBoldMessage entity representing bold text.
messageEntityItalicMessage entity representing italic text.
messageEntityCodeMessage entity representing a codeblock.
messageEntityPreMessage entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.
messageEntityTextUrlMessage entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
messageEntityMentionNameMessage entity representing a user mention: for creating a mention use inputMessageEntityMentionName.
inputMessageEntityMentionNameMessage entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.
messageEntityPhoneMessage entity representing a phone number.
messageEntityCashtagMessage entity representing a $cashtag.
messageEntityUnderlineMessage entity representing underlined text.
messageEntityStrikeMessage entity representing strikethrough text.
messageEntityBlockquoteMessage entity representing a block quote.
messageEntityBankCardIndicates a credit card number
messageEntitySpoiler 
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageReplyHeader.html b/data/corefork.telegram.org/type/MessageReplyHeader.html new file mode 100644 index 0000000000..e3947b829a --- /dev/null +++ b/data/corefork.telegram.org/type/MessageReplyHeader.html @@ -0,0 +1,143 @@ + + + + + MessageReplyHeader + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageReplyHeader

+ +

Reply information

+

+ +
+
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageReplyHeaderMessage thread information
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/MessageViews.html b/data/corefork.telegram.org/type/MessageViews.html new file mode 100644 index 0000000000..eef0efcab3 --- /dev/null +++ b/data/corefork.telegram.org/type/MessageViews.html @@ -0,0 +1,143 @@ + + + + + MessageViews + + + + + + + + + + + + + +
+ +
+
+
+ +

MessageViews

+ +

View, forward counter + info about replies of a specific message

+

+ +
+
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messageViewsView, forward counter + info about replies of a specific message
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageCaption.html b/data/corefork.telegram.org/type/PageCaption.html new file mode 100644 index 0000000000..22f4d9ae1d --- /dev/null +++ b/data/corefork.telegram.org/type/PageCaption.html @@ -0,0 +1,143 @@ + + + + + PageCaption + + + + + + + + + + + + + +
+ +
+
+
+ +

PageCaption

+ +

Page caption

+

+ +
+
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageCaptionPage caption
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageListItem.html b/data/corefork.telegram.org/type/PageListItem.html new file mode 100644 index 0000000000..d287317c02 --- /dev/null +++ b/data/corefork.telegram.org/type/PageListItem.html @@ -0,0 +1,148 @@ + + + + + PageListItem + + + + + + + + + + + + + +
+ +
+
+
+ +

PageListItem

+ +

Item in block list

+

+ +
+
pageListItemText#b92fb6cd text:RichText = PageListItem;
+pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
pageListItemTextList item
pageListItemBlocksList item
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PageRelatedArticle.html b/data/corefork.telegram.org/type/PageRelatedArticle.html new file mode 100644 index 0000000000..2bfc6715d0 --- /dev/null +++ b/data/corefork.telegram.org/type/PageRelatedArticle.html @@ -0,0 +1,143 @@ + + + + + PageRelatedArticle + + + + + + + + + + + + + +
+ +
+
+
+ +

PageRelatedArticle

+ +

Related articles

+

+ +
+
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pageRelatedArticleRelated article
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PaymentRequestedInfo.html b/data/corefork.telegram.org/type/PaymentRequestedInfo.html new file mode 100644 index 0000000000..07429a2328 --- /dev/null +++ b/data/corefork.telegram.org/type/PaymentRequestedInfo.html @@ -0,0 +1,143 @@ + + + + + PaymentRequestedInfo + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentRequestedInfo

+ +

Requested payment info

+

+ +
+
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentRequestedInfoOrder info provided by the user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PaymentSavedCredentials.html b/data/corefork.telegram.org/type/PaymentSavedCredentials.html new file mode 100644 index 0000000000..0a81b5a8ce --- /dev/null +++ b/data/corefork.telegram.org/type/PaymentSavedCredentials.html @@ -0,0 +1,143 @@ + + + + + PaymentSavedCredentials + + + + + + + + + + + + + +
+ +
+
+
+ +

PaymentSavedCredentials

+ +

Saved payment credentials

+

+ +
+
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
paymentSavedCredentialsCardSaved credit card
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhoneCall.html b/data/corefork.telegram.org/type/PhoneCall.html new file mode 100644 index 0000000000..9760135ea3 --- /dev/null +++ b/data/corefork.telegram.org/type/PhoneCall.html @@ -0,0 +1,168 @@ + + + + + PhoneCall + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneCall

+ +

Phone call

+

+ +
+
phoneCallEmpty#5366c915 id:long = PhoneCall;
+phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
+phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
+phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
+phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneCallEmptyEmpty constructor
phoneCallWaitingIncoming phone call
phoneCallRequestedRequested phone call
phoneCallAcceptedAn accepted phone call
phoneCallPhone call
phoneCallDiscardedIndicates a discarded phone call
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhoneConnection.html b/data/corefork.telegram.org/type/PhoneConnection.html new file mode 100644 index 0000000000..91be252fad --- /dev/null +++ b/data/corefork.telegram.org/type/PhoneConnection.html @@ -0,0 +1,148 @@ + + + + + PhoneConnection + + + + + + + + + + + + + +
+ +
+
+
+ +

PhoneConnection

+ +

Phone call connection

+

+ +
+
phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;
+phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
phoneConnectionIdentifies an endpoint that can be used to connect to the other user in a phone call
phoneConnectionWebrtcWebRTC connection parameters
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PhotoSize.html b/data/corefork.telegram.org/type/PhotoSize.html new file mode 100644 index 0000000000..7a00981558 --- /dev/null +++ b/data/corefork.telegram.org/type/PhotoSize.html @@ -0,0 +1,168 @@ + + + + + PhotoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

PhotoSize

+ +

Location of a certain size of a picture

+

+ +
+
photoSizeEmpty#e17e23c type:string = PhotoSize;
+photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
+photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
+photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
+photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
+photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
photoSizeEmptyEmpty constructor. Image with this thumbnail is unavailable.
photoSizeImage description.
photoCachedSizeDescription of an image and its content.
photoStrippedSizeJust the image's content
photoSizeProgressiveProgressively encoded photosize
photoPathSizeMessages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PollAnswer.html b/data/corefork.telegram.org/type/PollAnswer.html new file mode 100644 index 0000000000..a8dc6d588f --- /dev/null +++ b/data/corefork.telegram.org/type/PollAnswer.html @@ -0,0 +1,146 @@ + + + + + PollAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

PollAnswer

+ +

Indicates a possible answer to a poll.

+

+ +
+
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
pollAnswerA possible answer of a poll
+

Related pages

+

Poll

+

Indicates a poll message

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/PostAddress.html b/data/corefork.telegram.org/type/PostAddress.html new file mode 100644 index 0000000000..e8ac09253b --- /dev/null +++ b/data/corefork.telegram.org/type/PostAddress.html @@ -0,0 +1,143 @@ + + + + + PostAddress + + + + + + + + + + + + + +
+ +
+
+
+ +

PostAddress

+ +

Shipping address

+

+ +
+
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
postAddressShipping address
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ReactionCount.html b/data/corefork.telegram.org/type/ReactionCount.html new file mode 100644 index 0000000000..346be39808 --- /dev/null +++ b/data/corefork.telegram.org/type/ReactionCount.html @@ -0,0 +1,143 @@ + + + + + ReactionCount + + + + + + + + + + + + + +
+ +
+
+
+ +

ReactionCount

+ +

Number of users that reacted with a certain emoji

+

+ +
+
reactionCount#6fb250d1 flags:# chosen:flags.0?true reaction:string count:int = ReactionCount;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
reactionCountReactions
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/ReceivedNotifyMessage.html b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html new file mode 100644 index 0000000000..87298150d0 --- /dev/null +++ b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html @@ -0,0 +1,143 @@ + + + + + ReceivedNotifyMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

ReceivedNotifyMessage

+ +

Confirmation of message receipt

+

+ +
+
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html b/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html new file mode 100644 index 0000000000..ec1e8dc569 --- /dev/null +++ b/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html @@ -0,0 +1,155 @@ + + + + + SecurePasswordKdfAlgo + + + + + + + + + + + + + +
+ +
+
+
+ +

SecurePasswordKdfAlgo

+ +

KDF algorithm to use for computing telegram passport hash

+

+ +
+
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
+securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
securePasswordKdfAlgoUnknownUnknown KDF algo (most likely the client has to be updated)
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000PBKDF2 with SHA512 and 100000 iterations KDF algo
securePasswordKdfAlgoSHA512SHA512 KDF algo
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/SendMessageAction.html b/data/corefork.telegram.org/type/SendMessageAction.html new file mode 100644 index 0000000000..5a620c2871 --- /dev/null +++ b/data/corefork.telegram.org/type/SendMessageAction.html @@ -0,0 +1,228 @@ + + + + + SendMessageAction + + + + + + + + + + + + + +
+ +
+
+
+ +

SendMessageAction

+ +

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

+

+ +
+
sendMessageTypingAction#16bf744e = SendMessageAction;
+sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
+sendMessageRecordVideoAction#a187d66f = SendMessageAction;
+sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
+sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
+sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
+sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
+sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
+sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
+sendMessageChooseContactAction#628cbc6f = SendMessageAction;
+sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
+sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
+sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
+speakingInGroupCallAction#d92c2285 = SendMessageAction;
+sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
+sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
sendMessageTypingActionUser is typing.
sendMessageCancelActionInvalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.
sendMessageRecordVideoActionUser is recording a video.
sendMessageUploadVideoActionUser is uploading a video.
sendMessageRecordAudioActionUser is recording a voice message.
sendMessageUploadAudioActionUser is uploading a voice message.
sendMessageUploadPhotoActionUser is uploading a photo.
sendMessageUploadDocumentActionUser is uploading a file.
sendMessageGeoLocationActionUser is selecting a location to share.
sendMessageChooseContactActionUser is selecting a contact to share.
sendMessageGamePlayActionUser is playing a game
sendMessageRecordRoundActionUser is recording a round video to share
sendMessageUploadRoundActionUser is uploading a round video
speakingInGroupCallActionUser is currently speaking in the group call
sendMessageHistoryImportActionChat history is being imported
sendMessageChooseStickerActionUser is choosing a sticker
sendMessageEmojiInteractionUser has clicked on an animated emoji, triggering a reaction
sendMessageEmojiInteractionSeenUser has seen the reaction generated by another user
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html b/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html new file mode 100644 index 0000000000..7363b8a423 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html @@ -0,0 +1,143 @@ + + + + + StatsAbsValueAndPrev + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsAbsValueAndPrev

+ +

Channel statistics value pair

+

+ +
+
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsAbsValueAndPrevStatistics value couple; initial and final value for period of time currently in consideration
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StatsPercentValue.html b/data/corefork.telegram.org/type/StatsPercentValue.html new file mode 100644 index 0000000000..41df1b93b7 --- /dev/null +++ b/data/corefork.telegram.org/type/StatsPercentValue.html @@ -0,0 +1,143 @@ + + + + + StatsPercentValue + + + + + + + + + + + + + +
+ +
+
+
+ +

StatsPercentValue

+ +

Channel statistics percentage

+

+ +
+
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
statsPercentValueChannel statistics percentage
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/StickerSet.html b/data/corefork.telegram.org/type/StickerSet.html new file mode 100644 index 0000000000..1120971d10 --- /dev/null +++ b/data/corefork.telegram.org/type/StickerSet.html @@ -0,0 +1,143 @@ + + + + + StickerSet + + + + + + + + + + + + + +
+ +
+
+
+ +

StickerSet

+ +

Represents a stickerset (stickerpack)

+

+ +
+
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stickerSetRepresents a stickerset (stickerpack)
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/TopPeerCategoryPeers.html b/data/corefork.telegram.org/type/TopPeerCategoryPeers.html new file mode 100644 index 0000000000..ad4d486e6d --- /dev/null +++ b/data/corefork.telegram.org/type/TopPeerCategoryPeers.html @@ -0,0 +1,143 @@ + + + + + TopPeerCategoryPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

TopPeerCategoryPeers

+ +

Top peers by top peer category

+

+ +
+
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
topPeerCategoryPeersTop peer category
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/UserStatus.html b/data/corefork.telegram.org/type/UserStatus.html new file mode 100644 index 0000000000..b9452b8f86 --- /dev/null +++ b/data/corefork.telegram.org/type/UserStatus.html @@ -0,0 +1,168 @@ + + + + + UserStatus + + + + + + + + + + + + + +
+ +
+
+
+ +

UserStatus

+ +

User online status

+

+ +
+
userStatusEmpty#9d05049 = UserStatus;
+userStatusOnline#edb93949 expires:int = UserStatus;
+userStatusOffline#8c703f was_online:int = UserStatus;
+userStatusRecently#e26f42f1 = UserStatus;
+userStatusLastWeek#7bf09fc = UserStatus;
+userStatusLastMonth#77ebc742 = UserStatus;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
userStatusEmptyUser status has not been set yet.
userStatusOnlineOnline status of the user.
userStatusOfflineThe user's offline status.
userStatusRecentlyOnline status: last seen recently
userStatusLastWeekOnline status: last seen last week
userStatusLastMonthOnline status: last seen last month
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/VideoSize.html b/data/corefork.telegram.org/type/VideoSize.html new file mode 100644 index 0000000000..add9560a2b --- /dev/null +++ b/data/corefork.telegram.org/type/VideoSize.html @@ -0,0 +1,143 @@ + + + + + VideoSize + + + + + + + + + + + + + +
+ +
+
+
+ +

VideoSize

+ +

Represents an animated video thumbnail

+

+ +
+
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
videoSizeAnimated profile picture in MPEG4 format
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/WallPaperSettings.html b/data/corefork.telegram.org/type/WallPaperSettings.html new file mode 100644 index 0000000000..1bd10a7560 --- /dev/null +++ b/data/corefork.telegram.org/type/WallPaperSettings.html @@ -0,0 +1,143 @@ + + + + + WallPaperSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

WallPaperSettings

+ +

Wallpaper settings

+

+ +
+
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
wallPaperSettingsWallpaper settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/WebPage.html b/data/corefork.telegram.org/type/WebPage.html new file mode 100644 index 0000000000..b0209e0231 --- /dev/null +++ b/data/corefork.telegram.org/type/WebPage.html @@ -0,0 +1,177 @@ + + + + + WebPage + + + + + + + + + + + + + +
+ +
+
+
+ +

WebPage

+ +

Instant View webpage preview

+

+ +
+
webPageEmpty#eb1477e8 id:long = WebPage;
+webPagePending#c586da1c id:long date:int = WebPage;
+webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
+webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
+
+---functions---
+
+messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
webPageEmptyNo preview is available for the webpage
webPagePendingA preview of the webpage is currently being generated
webPageWebpage preview
webPageNotModifiedThe preview of the webpage hasn't changed
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getWebPageGet instant view page
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.ChatThemes b/data/corefork.telegram.org/type/account.ChatThemes new file mode 100644 index 0000000000..253aa2b11d --- /dev/null +++ b/data/corefork.telegram.org/type/account.ChatThemes @@ -0,0 +1,128 @@ + + + + + account.ChatThemes + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ChatThemes

+ +

Available chat themes

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.Password b/data/corefork.telegram.org/type/account.Password new file mode 100644 index 0000000000..5cfee67bc3 --- /dev/null +++ b/data/corefork.telegram.org/type/account.Password @@ -0,0 +1,162 @@ + + + + + account.Password + + + + + + + + + + + + + +
+ +
+
+
+ +

account.Password

+ +

Configuration for two-factor authorization

+

+ +
+
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
+
+---functions---
+
+account.getPassword#548a30f5 = account.Password;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordConfiguration for two-factor authorization
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getPasswordObtain configuration for two-factor authorization with password
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.PasswordInputSettings b/data/corefork.telegram.org/type/account.PasswordInputSettings new file mode 100644 index 0000000000..e205cbfdf5 --- /dev/null +++ b/data/corefork.telegram.org/type/account.PasswordInputSettings @@ -0,0 +1,146 @@ + + + + + account.PasswordInputSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.PasswordInputSettings

+ +

Constructor for setting up a new 2FA SRP password

+

+ +
+
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordInputSettingsSettings for setting up a new password
+

Related pages

+

Two-factor authentication

+

How to login to a user's account if they have enabled 2FA, how to change password.

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.PasswordSettings b/data/corefork.telegram.org/type/account.PasswordSettings new file mode 100644 index 0000000000..70e659f242 --- /dev/null +++ b/data/corefork.telegram.org/type/account.PasswordSettings @@ -0,0 +1,164 @@ + + + + + account.PasswordSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

account.PasswordSettings

+ +

Private info associated to the password info (recovery email, telegram passport info & so on)

+

+ +
+
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
+---functions---
+
+account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
account.passwordSettingsPrivate info associated to the password info (recovery email, telegram passport info & so on)
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
+

Related pages

+

Telegram Passport Manual

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.ResetPasswordResult b/data/corefork.telegram.org/type/account.ResetPasswordResult new file mode 100644 index 0000000000..4ac3bd2e29 --- /dev/null +++ b/data/corefork.telegram.org/type/account.ResetPasswordResult @@ -0,0 +1,175 @@ + + + + + account.ResetPasswordResult + + + + + + + + + + + + + +
+ +
+
+
+ +

account.ResetPasswordResult

+ +

Result of an account.resetPassword request.

+

+ +
+
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
+account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
+account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
+
+---functions---
+
+account.resetPassword#9308ce1b = account.ResetPasswordResult;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
account.resetPasswordFailedWaitYou requested a password reset too many times, please wait until the specified date before retrying the reset.
account.resetPasswordRequestedWaitYou already requested a password reset, please wait until the specified date before retrying the reset.
account.resetPasswordOkThe 2FA password was reset successfully.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.resetPasswordInitiate a 2FA password reset
+

Related pages

+

account.resetPassword

+

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/account.WallPapers b/data/corefork.telegram.org/type/account.WallPapers new file mode 100644 index 0000000000..6e6b098ffa --- /dev/null +++ b/data/corefork.telegram.org/type/account.WallPapers @@ -0,0 +1,167 @@ + + + + + Account.WallPapers + + + + + + + + + + + + + +
+ +
+
+
+ +

Account.WallPapers

+ +

Wallpapers

+

+ +
+
account.wallPapersNotModified#1c199183 = account.WallPapers;
+account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+
+---functions---
+
+account.getWallPapers#7967d36 hash:long = account.WallPapers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
account.wallPapersNotModifiedNo new wallpapers were found
account.wallPapersInstalled wallpapers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
account.getWallPapersReturns a list of available wallpapers.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.CheckedPhone b/data/corefork.telegram.org/type/auth.CheckedPhone new file mode 100644 index 0000000000..248d3127cf --- /dev/null +++ b/data/corefork.telegram.org/type/auth.CheckedPhone @@ -0,0 +1,128 @@ + + + + + Auth.CheckedPhone + + + + + + + + + + + + + +
+ +
+
+
+ +

Auth.CheckedPhone

+ +

Checked phone

+

+ +
+

+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/auth.LoginToken b/data/corefork.telegram.org/type/auth.LoginToken new file mode 100644 index 0000000000..e8e54f3aad --- /dev/null +++ b/data/corefork.telegram.org/type/auth.LoginToken @@ -0,0 +1,177 @@ + + + + + auth.LoginToken + + + + + + + + + + + + + +
+ +
+
+
+ +

auth.LoginToken

+ +

Login token (for QR code login)

+

+ +
+
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
+auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
+auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
+
+---functions---
+
+auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
+auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
auth.loginTokenLogin token (for QR code login)
auth.loginTokenMigrateToRepeat the query to the specified DC
auth.loginTokenSuccessLogin via token (QR code) succeded!
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
auth.exportLoginTokenExport login token (for login via QR code)
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.ImportedContacts b/data/corefork.telegram.org/type/contacts.ImportedContacts new file mode 100644 index 0000000000..d73467e889 --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.ImportedContacts @@ -0,0 +1,162 @@ + + + + + contacts.ImportedContacts + + + + + + + + + + + + + +
+ +
+
+
+ +

contacts.ImportedContacts

+ +

Object contains info on succesfully imported contacts.

+

+ +
+
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
+
+---functions---
+
+contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
contacts.importedContactsInfo on succesfully imported contacts.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/contacts.TopPeers b/data/corefork.telegram.org/type/contacts.TopPeers new file mode 100644 index 0000000000..c631697e5d --- /dev/null +++ b/data/corefork.telegram.org/type/contacts.TopPeers @@ -0,0 +1,172 @@ + + + + + Contacts.TopPeers + + + + + + + + + + + + + +
+ +
+
+
+ +

Contacts.TopPeers

+ +

Top peers

+

+ +
+
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
+contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
+contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
+
+---functions---
+
+contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
contacts.topPeersNotModifiedTop peer info hasn't changed
contacts.topPeersTop peers
contacts.topPeersDisabledTop peers disabled
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
contacts.getTopPeersGet most used peers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.CountriesList b/data/corefork.telegram.org/type/help.CountriesList new file mode 100644 index 0000000000..9adf6d57ac --- /dev/null +++ b/data/corefork.telegram.org/type/help.CountriesList @@ -0,0 +1,167 @@ + + + + + help.CountriesList + + + + + + + + + + + + + +
+ +
+
+
+ +

help.CountriesList

+ +

Name, ISO code, localized name and phone codes/patterns of all available countries

+

+ +
+
help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
+
+---functions---
+
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
help.countriesListNotModifiedThe country list has not changed
help.countriesListName, ISO code, localized name and phone codes/patterns of all available countries
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/help.Country b/data/corefork.telegram.org/type/help.Country new file mode 100644 index 0000000000..18f11b76ed --- /dev/null +++ b/data/corefork.telegram.org/type/help.Country @@ -0,0 +1,143 @@ + + + + + help.Country + + + + + + + + + + + + + +
+ +
+
+
+ +

help.Country

+ +

Name, ISO code, localized name and phone codes/patterns of a specific country

+

+ +
+
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
help.countryName, ISO code, localized name and phone codes/patterns of a specific country
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.BotCallbackAnswer b/data/corefork.telegram.org/type/messages.BotCallbackAnswer new file mode 100644 index 0000000000..464a1f94d1 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.BotCallbackAnswer @@ -0,0 +1,162 @@ + + + + + Messages.BotCallbackAnswer + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.BotCallbackAnswer

+ +

Callback answer of bot

+

+ +
+
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
+
+---functions---
+
+messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.botCallbackAnswerCallback answer sent by the bot in response to a button press
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ChatInviteImporters b/data/corefork.telegram.org/type/messages.ChatInviteImporters new file mode 100644 index 0000000000..19789ed16c --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ChatInviteImporters @@ -0,0 +1,162 @@ + + + + + messages.ChatInviteImporters + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ChatInviteImporters

+ +

List of users that imported a chat invitation link.

+

+ +
+
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
+
+---functions---
+
+messages.getChatInviteImporters#df04dd4e flags:# requested:flags.0?true peer:InputPeer link:flags.1?string q:flags.2?string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.chatInviteImportersInfo about the users that joined the chat using a specific chat invite
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.DiscussionMessage b/data/corefork.telegram.org/type/messages.DiscussionMessage new file mode 100644 index 0000000000..e6530fe9a1 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.DiscussionMessage @@ -0,0 +1,162 @@ + + + + + messages.DiscussionMessage + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.DiscussionMessage

+ +

Info about a message thread

+

+ +
+
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
+
+---functions---
+
+messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.discussionMessageInformation about a message thread
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ExportedChatInvite b/data/corefork.telegram.org/type/messages.ExportedChatInvite new file mode 100644 index 0000000000..c68920b356 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ExportedChatInvite @@ -0,0 +1,172 @@ + + + + + messages.ExportedChatInvite + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvite

+ +

Contains info about a chat invite, and eventually a pointer to the newest chat invite.

+

+ +
+
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
+
+---functions---
+
+messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
+messages.editExportedChatInvite#bdca2f75 flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int request_needed:flags.3?Bool title:flags.4?string = messages.ExportedChatInvite;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInviteInfo about a chat invite
messages.exportedChatInviteReplacedThe specified chat invite was replaced with another one
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.ExportedChatInvites b/data/corefork.telegram.org/type/messages.ExportedChatInvites new file mode 100644 index 0000000000..732dc8ed5d --- /dev/null +++ b/data/corefork.telegram.org/type/messages.ExportedChatInvites @@ -0,0 +1,162 @@ + + + + + messages.ExportedChatInvites + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.ExportedChatInvites

+ +

Info about chat invites exported by a certain admin.

+

+ +
+
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
+
+---functions---
+
+messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.exportedChatInvitesInfo about chat invites exported by a certain admin.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.FavedStickers b/data/corefork.telegram.org/type/messages.FavedStickers new file mode 100644 index 0000000000..af56e5d7ca --- /dev/null +++ b/data/corefork.telegram.org/type/messages.FavedStickers @@ -0,0 +1,167 @@ + + + + + Messages.FavedStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.FavedStickers

+ +

Favorited stickers

+

+ +
+
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
+messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
+
+---functions---
+
+messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getFavedStickersGet faved stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.HighScores b/data/corefork.telegram.org/type/messages.HighScores new file mode 100644 index 0000000000..cdcd991cfb --- /dev/null +++ b/data/corefork.telegram.org/type/messages.HighScores @@ -0,0 +1,167 @@ + + + + + Messages.HighScores + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.HighScores

+ +

High scores (in games)

+

+ +
+
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
+
+---functions---
+
+messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
+messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.highScoresHighscores in a game
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.PeerDialogs b/data/corefork.telegram.org/type/messages.PeerDialogs new file mode 100644 index 0000000000..e1a1cf7e95 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.PeerDialogs @@ -0,0 +1,167 @@ + + + + + Messages.PeerDialogs + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.PeerDialogs

+ +

List of dialogs

+

+ +
+
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
+
+---functions---
+
+messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
+messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
+

Methods

+ + + + + + + + + + + + + + + + + +
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.PeerSettings b/data/corefork.telegram.org/type/messages.PeerSettings new file mode 100644 index 0000000000..ef376e9949 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.PeerSettings @@ -0,0 +1,179 @@ + + + + + messages.PeerSettings + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.PeerSettings

+ +

+ +
+
messages.peerSettings#6880b94d settings:PeerSettings chats:Vector<Chat> users:Vector<User> = messages.PeerSettings;
+
+---functions---
+
+messages.getPeerSettings#efd9a6a2 peer:InputPeer = messages.PeerSettings;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.peerSettings 
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getPeerSettingsGet peer settings
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.RecentStickers b/data/corefork.telegram.org/type/messages.RecentStickers new file mode 100644 index 0000000000..7b2dc810a1 --- /dev/null +++ b/data/corefork.telegram.org/type/messages.RecentStickers @@ -0,0 +1,167 @@ + + + + + Messages.RecentStickers + + + + + + + + + + + + + +
+ +
+
+
+ +

Messages.RecentStickers

+ +

Recent stickers

+

+ +
+
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
+messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
+
+---functions---
+
+messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
messages.recentStickersNotModifiedNo new recent sticker was found
messages.recentStickersRecently used stickers
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getRecentStickersGet recent stickers
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SearchResultsCalendar b/data/corefork.telegram.org/type/messages.SearchResultsCalendar new file mode 100644 index 0000000000..e8034627ff --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SearchResultsCalendar @@ -0,0 +1,177 @@ + + + + + messages.SearchResultsCalendar + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SearchResultsCalendar

+ +

+ +
+
messages.searchResultsCalendar#147ee23c flags:# inexact:flags.0?true count:int min_date:int min_msg_id:int offset_id_offset:flags.1?int periods:Vector<SearchResultsCalendarPeriod> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.SearchResultsCalendar;
+
+---functions---
+
+messages.getSearchResultsCalendar#49f0bde9 peer:InputPeer filter:MessagesFilter offset_id:int offset_date:int = messages.SearchResultsCalendar;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.searchResultsCalendar 
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getSearchResultsCalendar 
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/messages.SearchResultsPositions b/data/corefork.telegram.org/type/messages.SearchResultsPositions new file mode 100644 index 0000000000..70177cacea --- /dev/null +++ b/data/corefork.telegram.org/type/messages.SearchResultsPositions @@ -0,0 +1,177 @@ + + + + + messages.SearchResultsPositions + + + + + + + + + + + + + +
+ +
+
+
+ +

messages.SearchResultsPositions

+ +

+ +
+
messages.searchResultsPositions#53b22baf count:int positions:Vector<SearchResultsPosition> = messages.SearchResultsPositions;
+
+---functions---
+
+messages.getSearchResultsPositions#6e9583a3 peer:InputPeer filter:MessagesFilter offset_id:int limit:int = messages.SearchResultsPositions;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
messages.searchResultsPositions 
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
messages.getSearchResultsPositions 
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/photos.Photos b/data/corefork.telegram.org/type/photos.Photos new file mode 100644 index 0000000000..21a5033b8e --- /dev/null +++ b/data/corefork.telegram.org/type/photos.Photos @@ -0,0 +1,167 @@ + + + + + photos.Photos + + + + + + + + + + + + + +
+ +
+
+
+ +

photos.Photos

+ +

Object contains list of photos with auxiliary data.

+

+ +
+
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
+photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
+
+---functions---
+
+photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

+

Constructors

+ + + + + + + + + + + + + + + + + +
ConstructorDescription
photos.photosFull list of photos with auxiliary data.
photos.photosSliceIncomplete list of photos with auxiliary data.
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
photos.getUserPhotosReturns the list of user photos.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/stats.BroadcastStats b/data/corefork.telegram.org/type/stats.BroadcastStats new file mode 100644 index 0000000000..36a606ba04 --- /dev/null +++ b/data/corefork.telegram.org/type/stats.BroadcastStats @@ -0,0 +1,162 @@ + + + + + Stats.BroadcastStats + + + + + + + + + + + + + +
+ +
+
+
+ +

Stats.BroadcastStats

+ +

Channel statistics

+

+ +
+
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
+
+---functions---
+
+stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
stats.broadcastStatsChannel statistics
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
stats.getBroadcastStatsGet channel statistics
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/storage.FileType b/data/corefork.telegram.org/type/storage.FileType new file mode 100644 index 0000000000..d0bb3d3fd0 --- /dev/null +++ b/data/corefork.telegram.org/type/storage.FileType @@ -0,0 +1,188 @@ + + + + + storage.FileType + + + + + + + + + + + + + +
+ +
+
+
+ +

storage.FileType

+ +

Object describes the file type.

+

+ +
+
storage.fileUnknown#aa963b05 = storage.FileType;
+storage.filePartial#40bc6f52 = storage.FileType;
+storage.fileJpeg#7efe0e = storage.FileType;
+storage.fileGif#cae1aadf = storage.FileType;
+storage.filePng#a4f63c0 = storage.FileType;
+storage.filePdf#ae1e508d = storage.FileType;
+storage.fileMp3#528a0677 = storage.FileType;
+storage.fileMov#4b09ebbc = storage.FileType;
+storage.fileMp4#b3cea0e4 = storage.FileType;
+storage.fileWebp#1081464c = storage.FileType;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
storage.fileUnknownUnknown type.
storage.filePartialPart of a bigger file.
storage.fileJpegJPEG image. MIME type: image/jpeg.
storage.fileGifGIF image. MIME type: image/gif.
storage.filePngPNG image. MIME type: image/png.
storage.filePdfPDF document image. MIME type: application/pdf.
storage.fileMp3Mp3 audio. MIME type: audio/mpeg.
storage.fileMovQuicktime video. MIME type: video/quicktime.
storage.fileMp4MPEG-4 video. MIME type: video/mp4.
storage.fileWebpWEBP image. MIME type: image/webp.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/updates.ChannelDifference b/data/corefork.telegram.org/type/updates.ChannelDifference new file mode 100644 index 0000000000..74581b25a7 --- /dev/null +++ b/data/corefork.telegram.org/type/updates.ChannelDifference @@ -0,0 +1,172 @@ + + + + + updates.ChannelDifference + + + + + + + + + + + + + +
+ +
+
+
+ +

updates.ChannelDifference

+ +

Contains the difference (new messages) between our local channel state and the remote state

+

+ +
+
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
+updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
+
+---functions---
+
+updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

+

Constructors

+ + + + + + + + + + + + + + + + + + + + + +
ConstructorDescription
updates.channelDifferenceEmptyThere are no new updates
updates.channelDifferenceTooLongThe 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. 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. It looks much smoother 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 and getMessages 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.
updates.channelDifferenceThe new updates
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/type/users.UserFull b/data/corefork.telegram.org/type/users.UserFull new file mode 100644 index 0000000000..4bf4523052 --- /dev/null +++ b/data/corefork.telegram.org/type/users.UserFull @@ -0,0 +1,179 @@ + + + + + users.UserFull + + + + + + + + + + + + + +
+ +
+
+
+ +

users.UserFull

+ +

+ +
+
users.userFull#3b6d152e full_user:UserFull chats:Vector<Chat> users:Vector<User> = users.UserFull;
+
+---functions---
+
+users.getFullUser#b60f5918 id:InputUser = users.UserFull;

+

Constructors

+ + + + + + + + + + + + + +
ConstructorDescription
users.userFull 
+

Methods

+ + + + + + + + + + + + + +
MethodDescription
users.getFullUserReturns extended user info by ID.
+ +
+ +
+
+ +
+ + + + + + diff --git a/data/corefork.telegram.org/widgets/post.html b/data/corefork.telegram.org/widgets/post.html new file mode 100644 index 0000000000..383e14184f --- /dev/null +++ b/data/corefork.telegram.org/widgets/post.html @@ -0,0 +1,240 @@ + + + + + Post Widget + + + + + + + + + + + + + + + +
+ +
+
+
+ +

Post Widget

+ +

You can embed messages from public groups and channels anywhere. Here’s what an embed of a Telegram message looks like when included on a web page:

+

+ +

+
+ +

To get the HTML-code for embedding a message, just open its t.me link (e.g., t.me/durov/43) in a web browser and click < > EMBED:

+
+ +
+ +

Configure widget

+

You can choose more options using the form below.

+

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+
+ +
+ +
+ + + +
+
+ +
+ +
+
+ + + + + + + +
+ + +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+
+ +
+ +
+
+ +
+ + + + + + + + + + diff --git a/data/corefork.telegram.org/widgets/share.html b/data/corefork.telegram.org/widgets/share.html new file mode 100644 index 0000000000..18ec61fb75 --- /dev/null +++ b/data/corefork.telegram.org/widgets/share.html @@ -0,0 +1,250 @@ + + + + + Sharing Button + + + + + + + + + + + + + + +
+ +
+
+
+ +

Sharing Button

+ +

A Telegram Sharing Button is an easy way to let users forward content from your website or app to their friends, Channels or Saved Messages on Telegram.

+
+ TITLE +
+ +

When a user presses the button, Telegram asks them to choose a chat, group or channel where your link will be shared. You can also add some text that describes the link – the user will be able to edit it before sending the message.

+
+ TITLE +
+ +
+

Check out posts on the Telegram Blog for working examples of sharing buttons.

+
+

Adding Telegram sharing buttons to your website

+

Widget Constructor

+

Use this constructor to get embeddable code for your website.

+


+ +

+
+ +
+
+ +
+ +
+
+
+ +
+ +
+
+ +
+
+
+
+ +
+ +
+ + +
+
+ +
+ +
+ + +
+
+ +
+ +
+ +
+
+ +
+
+
+
+
+

+

Custom buttons

+

Feel free to create your own custom UI for the button. The only thing you need to make it work is to point the user to this URL on click:

+
https://t.me/share/url?url={url}&text={text}
+

where {url} is the URL the user will be sharing and {text} is an optional description that will be included with the link. Both values should be URL-encoded.

+

Here is a sample code for PHP:

+
/**
+ * @param string $url Absolute URL to share, e.g. "https://example.com/path/to/article?with=params"
+ * @param string $text Optional comment to share URL with, e.g. "Check out this article!"
+ * @return string Button HTML markup, feel free to modify to your taste
+ */
+function telegramForwardButton($url, $text = '') {
+  $share_url = 'https://t.me/share/url?url='.rawurlencode($url).'&text='.rawurlencode($text);
+  return "<a href=\"{$share_url}\">Share</a>";
+}
+

You are welcome to use the Telegram Logos in your custom button design.

+

Integrations and libraries

+ +

If you have a library, plugin or integration script for Telegram sharing buttons, please contact @BotSupport and we'll add you to this list.

+
+ +
+ +
+
+ +
+ + + + + + + + + diff --git a/data/desktop.telegram.org.html b/data/desktop.telegram.org.html new file mode 100644 index 0000000000..b2c6845e01 --- /dev/null +++ b/data/desktop.telegram.org.html @@ -0,0 +1,76 @@ + + + + + Telegram Desktop + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + diff --git a/data/desktop.telegram.org/changelog.html b/data/desktop.telegram.org/changelog.html new file mode 100644 index 0000000000..ca9619d1c0 --- /dev/null +++ b/data/desktop.telegram.org/changelog.html @@ -0,0 +1,211 @@ + + + + + Version history + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +

Version history

+ +

v 3.5.2 (08.02.22)

+
    +
  • Fix a freeze in audio playback on Linux.
  • +
  • Fix a crash in screen sharing initialization on Linux.
  • +
+

v 3.5.1 (04.02.22)

+
    +
  • Keep the screen on while watching a video or participating in a video chat.
  • +
  • Save experimental settings between relaunches.
  • +
  • Bug fixes and other minor improvements.
  • +
+

v 3.5 (31.01.22)

+
    +
  • Use a new type of detailed stickers with smooth animations.
  • +
  • Create new sets by sending .webm videos to @stickers.
  • +
  • Bring your custom animated stickers from other apps.
  • +
  • See smaller, compact animations when reacting to messages.
  • +
  • See real-time animations in chat when a user reacts to your message.
  • +
  • React with additional emoji expressing love, appreciation, anger or surprise.
  • +
  • Tap the new button in chats to jump to your messages that have unseen reactions.
  • +
  • Watch the animations for unseen reactions play when you hit the button.
  • +
  • The app will warn you before closing if you are uploading photos or files to a chat.
  • +
  • Enjoy better screencast quality in video chats.
  • +
+

v 3.4.8 19.01.22

+
    +
  • Beautifully animated reactions.
  • +
  • Support for snap layouts on Windows 11.
  • +
  • Bug fixes and two bowls of miso soup.
  • +
+

v 3.4 31.12.21

+
    +
  • Hover over any message to show the reaction button.
  • +
  • Click the button for a quick 👍 reaction – or hover over it for the full range of emoji.
  • +
  • Group and Channel admins can enable reactions in their chat via '…' menu > Manage > Reactions.
  • +
  • Select text when typing and choose 'Formatting > Spoiler' in the context menu to hide some or all of the contents of a message.
  • +
  • Click on the spoiler animation in chat to reveal its hidden text.
  • +
  • Spoiler formatting hides text in chat, as well as in the chat list and notifications.
  • +
+

v 3.3 07.12.21

+
    +
  • Content creators can restrict the ability to save media and forward messages from their groups and channels.
  • +
  • Clear messages in one-on-one chats from a specific day or date range.
  • +
  • Comment as one of your channels in public groups and channel comments.
  • +
  • When you request to join a community and its admin or bot-admin contacts you with a message, you will see which chat they are from at the top of the chat.
  • +
  • Bot-admins can now ask users to complete tasks before they are allowed to join - like accepting community rules, passing a test, or making a donation to the content creators.
  • +
+

v 3.2 03.11.21

+
    +
  • Create special invite links that require admins to approve users before they become members.
  • +
  • Admins can view the applicants' profiles and bios by tapping the Join Requests bar at the top of the chat.
  • +
  • Add internal labels to your chat's Invite Links to keep them organized.
  • +
  • More Interactive Emoji - 👻, 👎, 🤮, 😂, 💸 or 🎃
  • +
+

v 3.1 19.09.21

+
    +
  • Some animated emoji now have extra effects.
  • +
  • Send 🎆, 🎉. 🎈. 👍. 💩 or ❤️ to any private chat, then click on the animated emoji to launch the effect.
  • +
  • If your chat partner also has the chat open, you will both see the effects.
  • +
  • See the “Watching” status when your chat partner is enjoying emoji effects with you.
  • +
  • More interactive emoji coming soon.
  • +
  • Right click one of your outgoing messages in small groups to see who recently viewed it.
  • +
  • To protect privacy, read receipts are only stored for 7 days after the message was sent.
  • +
  • Record video and audio from live broadcasts in your group or channel.
  • +
  • Admins can start recording from the '…' menu.
  • +
  • Choose between recording in portrait or landscape orientation.
  • +
  • Finished recordings are sent to the admin's Saved Messages and can be easily shared.
  • +
+

v 3.0 31.08.21

+
    +
  • Broadcast video and share your screen to an unlimited number of viewers.
  • +
  • To begin, click on the Live Stream button in the title bar of a community where you are an admin.
  • +
  • Click on the “Forward Message” label above the input field to change how messages will be sent.
  • +
  • Hide or show the original sender's name.
  • +
  • Remove or keep captions from media messages.
  • +
  • See how many unread comments there are when opening a channel's comments.
  • +
+

Beta version

+

If you would like to get all updates faster and be the first to test new features, you are welcome to use Telegram Desktop's beta version updates.

+

The stable version is updated less frequently, but is tested better than the beta version.

+

Here are the beta version links for different platforms:

+

Windows x64 Setup
Windows x64 Portable
Windows Setup
Windows Portable
Mac OS X 10.12+ Setup
Linux 64 bit

+

Just install it on top of your current Telegram Desktop and there you go.

+

Old system versions

+

The up-to-date versions of Telegram Desktop support Windows 7 and later, macOS 10.12 and later and 64 bit Linux. But there are old versions available:

+

v2.4.4 Setup for OS X 10.10 and 10.11
v2.4.4 for Linux 32 bit
v1.8.15 Setup for Windows XP / Vista
v1.8.15 Portable for Windows XP / Vista
v1.8.15 Setup for OS X 10.6 and 10.7
v1.8.15 Setup for OS X 10.8 and 10.9

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/instantview.telegram.org.html b/data/instantview.telegram.org.html new file mode 100644 index 0000000000..a280c7fd58 --- /dev/null +++ b/data/instantview.telegram.org.html @@ -0,0 +1,293 @@ + + + + + Instant View + + + + + + + + + + + +
+ +
+
+
+
+
+ +
+
+
+
+
+
+
+
+ +
+
+
+
+

Instant Views Explained

+ +
+ +
+ +
+ +

Instant View allows Telegram users to view articles from around the Web in a consistent way, with zero loading time. When you get a link to an article via Telegram, simply tap the Instant View button, and the page will open instantly.

+

With Instant View, Telegram users can enjoy articles from any mass media or blogs in a uniform and easily readable way. Instant View pages support text and media of any type and work great even if the original website was not optimized for mobile devices.

+

On top of this, Instant View pages are extremely lightweight and are cached on the Telegram servers, so they load instantly on pretty much any connection — hence the name. No more waiting for clunky websites to load, now you can get the good stuff right away!

+

And the best part is that webmasters don't need to change anything on their websites for Instant Views to work.

+
+
+ +

Instant View Button

+
+
+ +

Instant View Page

+
+ +

How does this work?

+

When you share a link via Telegram and a link preview is generated, our Instant View bot also checks if it has an Instant View Template for that website. Templates are sets of instructions we call rules that teach the IV bot to build instant view pages for particular domains or URLs.

+

If a template exists for the link, the bot uses it to find the relevant content on the page (headings, text, media, embedded elements), remove clutter, and create a slim and beautiful Instant View page.

+

Anyone can use our Instant View Editor to create templates. Once a template for a URL is approved by our team, all Telegram users will get the option to view the page in the Instant View format whenever they see a link to it on Telegram.

+

If you publish your content on Telegram yourself, you don‘t even need to wait for us to approve your template. You can just send specially formatted links to your subscribers, and they’ll get Instant View pages built using your template right away.

+

Read More About Publishing Templates »

+

Join buttons

+

Another added bonus if you have a channel is that you can direct users to join your channel from the Instant View pages built from your articles.

+
+ +

Join Button

+ +

For this to work, the template must contain a channel property that holds a link to your channel. More in the docs »

+

Instant View Editor

+

Telegram's Instant View Editor allows you to create and test templates for any domain. To begin, just go to My Templates, type a target URL for your Instant View template into the box, and hit ‘enter’. This will open the editor. The source page will be displayed on the left.

+
+

Tip: Use the Developer Tools in your browser (e.g. Inspect mode in Chrome) to study the HTML markup of the page.

+
+
+
+
+ +

The middle section of the page is where you create your template for the chosen domain name or URL. Templates consist of simple instructions to our IV bot we call rules. You can later study the syntax in detail here. Once you've saved your rules for the page (cmd + S or ctrl + S in the Rules window), the window on the right will display the Instant View page that the IV bot would create based on the current instructions.

+
+

Note the status line at the bottom of the page — it displays the result of the last operation. This is also where you'll find the output of the @debug function:

+
+
+ +
+ +

Sample templates

+

If you'd like an example, you can check out the exact same templates that we're currently using to generate Instant View pages for posts on Medium, Telegra.ph, and the Telegram Blog. We've added many comments to these templates, so they literally speak for themselves.

+

Feel free to experiment with them and see what changes. Don‘t worry, your changes won’t be applied to the actual Instant View pages that regular Telegram users can see.

+

Templates tutorial

+

When creating an Instant View template, you have four main objectives:

+
    +
  • Instant View pages must only be generated for pages that need them.
  • +
  • All essential content from the source page must be represented.
  • +
  • All unnecessary elements must be eliminated from the Instant View page.
  • +
  • Your template must work well with any of the pages it covers.
  • +
+

Accordingly, one of the ways to create a template is to follow these steps:

+

Step 1. Aim your template

+

Instant View pages work best with relatively static articles. On the other hand, the main page of a news site that contains ever-changing lists of links to new articles would hardly benefit from the IV treatment.

+

For the first step, you will likely use conditions to clearly define which parts of the target website will and will not be covered by your template.

+

Step 2. Grab the essentials

+

Now it's time to do some real business. An Instant View page requires at least two properties to be created: a title and a body. Take a close look at the target article and make sure that all important elements are carried over to the IV page in a format supported by the Telegram apps.

+

At this stage, you may need to use functions to transform some elements before they are transferred. By the time you're done, your IV page should show the entire text of the article, along with all the headings and subheadings, quotes, cover and other photos, videos, and other kinds of embedded content from the source page.

+

Step 3. Remove the rest

+

Salvage the remaining useful bits, then use the @remove function to drop the rest. By now you should have a clean and slim IV page that displays the pure content and none of the fluff.

+

Step 4. Refine your template

+

At this stage, we advise you to leave the familiar confines of the page you were using for testing and check out different pages from your target website. See if any pages that don't deserve IVs are getting them — and whether IV pages are missing for any that do deserve them.

+

Also, check whether pages with irregular elements are processed correctly. Pay special attention to ensure that various types of media, embedded content, quotes, and separators are all displayed nicely. Check 5-10 different links and make the relevant adjustments.

+
+

See also: Our Perfect Template Checklist »

+
+

Naturally, this is just a brief outline of what you could do — Instant View pages offer limitless possibilities.

+

Tracking changes

+

Once you're satisfied with your template's generated IV pages, press the Track Changes button. If modified template rules are subsequently applied, they can now be checked across all applicable IV pages within the system.

+
+ +

Track Changes

+
+ +

After Track Changes is enabled, editing your template will not immediately check for changes across all pages. Instead, when you're happy with the currently generated IV page, and no warnings are shown, click Mark as Checked to see if your changes broke anything on the other IV pages impacted by your template.

+
+ +

Pages Modified

+ +

If any changes are detected, the status line will display the difference and the result:

+
+ +

Changes Detected

+ + +
+

Take care that your changes don‘t break pages that already had good IV pages. There’s a handy indicator at the top of the page that shows the status of the pages relevant for your template. As long as it's green, everything's fine.

+
+

Publishing templates

+

If the Instant View page has been processed successfully, you'll see a View in Telegram button in the top right corner – you can use it to view the resulting page in-app.

+

For your own audience

+

Note that if you send the resulting t.me/iv?url=...&rhash=... link to other Telegram users, they will see an Instant View page built using your template (the rhash parameter in the link determines which template is used to create the page). This means that, as a website owner, you can create a template for your page and publish t.me/iv?url=... links with the corresponding rhash to your Telegram channel — and your subscribers will be able to view your articles in the Instant View format right away.

+

For all Telegram users

+

If you'd like your template to become truly public and seen by all users, regardless of the link they get, the template will need to be approved by the Telegram team.

+
+
+

And that‘s it, you’re now ready to move on to the full instant view documentation.
Don't forget that you can also check out our annotated sample templates.

+
+
+ +
+
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/auth.html b/data/instantview.telegram.org/auth.html new file mode 100644 index 0000000000..6ca9cdff2b --- /dev/null +++ b/data/instantview.telegram.org/auth.html @@ -0,0 +1,294 @@ + + + + + Instant View + + + + + + + + + + + +
+ +
+
+
+
+
+ +
+
+
+
+
+
+
+
+ +
+
+
+
+

Instant Views Explained

+ +
+ +
+ +
+ +

Instant View allows Telegram users to view articles from around the Web in a consistent way, with zero loading time. When you get a link to an article via Telegram, simply tap the Instant View button, and the page will open instantly.

+

With Instant View, Telegram users can enjoy articles from any mass media or blogs in a uniform and easily readable way. Instant View pages support text and media of any type and work great even if the original website was not optimized for mobile devices.

+

On top of this, Instant View pages are extremely lightweight and are cached on the Telegram servers, so they load instantly on pretty much any connection — hence the name. No more waiting for clunky websites to load, now you can get the good stuff right away!

+

And the best part is that webmasters don't need to change anything on their websites for Instant Views to work.

+
+
+ +

Instant View Button

+
+
+ +

Instant View Page

+
+ +

How does this work?

+

When you share a link via Telegram and a link preview is generated, our Instant View bot also checks if it has an Instant View Template for that website. Templates are sets of instructions we call rules that teach the IV bot to build instant view pages for particular domains or URLs.

+

If a template exists for the link, the bot uses it to find the relevant content on the page (headings, text, media, embedded elements), remove clutter, and create a slim and beautiful Instant View page.

+

Anyone can use our Instant View Editor to create templates. Once a template for a URL is approved by our team, all Telegram users will get the option to view the page in the Instant View format whenever they see a link to it on Telegram.

+

If you publish your content on Telegram yourself, you don‘t even need to wait for us to approve your template. You can just send specially formatted links to your subscribers, and they’ll get Instant View pages built using your template right away.

+

Read More About Publishing Templates »

+

Join buttons

+

Another added bonus if you have a channel is that you can direct users to join your channel from the Instant View pages built from your articles.

+
+ +

Join Button

+ +

For this to work, the template must contain a channel property that holds a link to your channel. More in the docs »

+

Instant View Editor

+

Telegram's Instant View Editor allows you to create and test templates for any domain. To begin, just go to My Templates, type a target URL for your Instant View template into the box, and hit ‘enter’. This will open the editor. The source page will be displayed on the left.

+
+

Tip: Use the Developer Tools in your browser (e.g. Inspect mode in Chrome) to study the HTML markup of the page.

+
+
+
+
+ +

The middle section of the page is where you create your template for the chosen domain name or URL. Templates consist of simple instructions to our IV bot we call rules. You can later study the syntax in detail here. Once you've saved your rules for the page (cmd + S or ctrl + S in the Rules window), the window on the right will display the Instant View page that the IV bot would create based on the current instructions.

+
+

Note the status line at the bottom of the page — it displays the result of the last operation. This is also where you'll find the output of the @debug function:

+
+
+ +
+ +

Sample templates

+

If you'd like an example, you can check out the exact same templates that we're currently using to generate Instant View pages for posts on Medium, Telegra.ph, and the Telegram Blog. We've added many comments to these templates, so they literally speak for themselves.

+

Feel free to experiment with them and see what changes. Don‘t worry, your changes won’t be applied to the actual Instant View pages that regular Telegram users can see.

+

Templates tutorial

+

When creating an Instant View template, you have four main objectives:

+
    +
  • Instant View pages must only be generated for pages that need them.
  • +
  • All essential content from the source page must be represented.
  • +
  • All unnecessary elements must be eliminated from the Instant View page.
  • +
  • Your template must work well with any of the pages it covers.
  • +
+

Accordingly, one of the ways to create a template is to follow these steps:

+

Step 1. Aim your template

+

Instant View pages work best with relatively static articles. On the other hand, the main page of a news site that contains ever-changing lists of links to new articles would hardly benefit from the IV treatment.

+

For the first step, you will likely use conditions to clearly define which parts of the target website will and will not be covered by your template.

+

Step 2. Grab the essentials

+

Now it's time to do some real business. An Instant View page requires at least two properties to be created: a title and a body. Take a close look at the target article and make sure that all important elements are carried over to the IV page in a format supported by the Telegram apps.

+

At this stage, you may need to use functions to transform some elements before they are transferred. By the time you're done, your IV page should show the entire text of the article, along with all the headings and subheadings, quotes, cover and other photos, videos, and other kinds of embedded content from the source page.

+

Step 3. Remove the rest

+

Salvage the remaining useful bits, then use the @remove function to drop the rest. By now you should have a clean and slim IV page that displays the pure content and none of the fluff.

+

Step 4. Refine your template

+

At this stage, we advise you to leave the familiar confines of the page you were using for testing and check out different pages from your target website. See if any pages that don't deserve IVs are getting them — and whether IV pages are missing for any that do deserve them.

+

Also, check whether pages with irregular elements are processed correctly. Pay special attention to ensure that various types of media, embedded content, quotes, and separators are all displayed nicely. Check 5-10 different links and make the relevant adjustments.

+
+

See also: Our Perfect Template Checklist »

+
+

Naturally, this is just a brief outline of what you could do — Instant View pages offer limitless possibilities.

+

Tracking changes

+

Once you're satisfied with your template's generated IV pages, press the Track Changes button. If modified template rules are subsequently applied, they can now be checked across all applicable IV pages within the system.

+
+ +

Track Changes

+
+ +

After Track Changes is enabled, editing your template will not immediately check for changes across all pages. Instead, when you're happy with the currently generated IV page, and no warnings are shown, click Mark as Checked to see if your changes broke anything on the other IV pages impacted by your template.

+
+ +

Pages Modified

+ +

If any changes are detected, the status line will display the difference and the result:

+
+ +

Changes Detected

+ + +
+

Take care that your changes don‘t break pages that already had good IV pages. There’s a handy indicator at the top of the page that shows the status of the pages relevant for your template. As long as it's green, everything's fine.

+
+

Publishing templates

+

If the Instant View page has been processed successfully, you'll see a View in Telegram button in the top right corner – you can use it to view the resulting page in-app.

+

For your own audience

+

Note that if you send the resulting t.me/iv?url=...&rhash=... link to other Telegram users, they will see an Instant View page built using your template (the rhash parameter in the link determines which template is used to create the page). This means that, as a website owner, you can create a template for your page and publish t.me/iv?url=... links with the corresponding rhash to your Telegram channel — and your subscribers will be able to view your articles in the Instant View format right away.

+

For all Telegram users

+

If you'd like your template to become truly public and seen by all users, regardless of the link they get, the template will need to be approved by the Telegram team.

+
+
+

And that‘s it, you’re now ready to move on to the full instant view documentation.
Don't forget that you can also check out our annotated sample templates.

+
+
+ +
+
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/checklist.html b/data/instantview.telegram.org/checklist.html new file mode 100644 index 0000000000..3c2c26d823 --- /dev/null +++ b/data/instantview.telegram.org/checklist.html @@ -0,0 +1,624 @@ + + + + + Checklist – Instant View + + + + + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+
+

A Guide to Good Templates

+ +
+ +
+ +
+ +

This page lists general rules and detailed clarifications for creating good Instant View templates for news articles.

+

For more info on templates, see our Introduction and Sample Templates.

+

General Rules

+

Instant View templates must meet these five basic requirements:

+

1. IVs must only be generated for pages that need them

+

Instant View pages work best with relatively static articles. Dynamic pages (such as the main page of a news site) that are constantly refreshed with new links and media don't need IV.

+

Templates should only generate IV pages for articles and should not affect service areas of websites, as well as any other sections unsuitable for IV. IV pages should not be generated for articles that have content which is not supported in IV since this would result in unacceptable loss of information (e.g., IV pages don't support dynamic maps — if you generate an IV page for a wiki article with a dynamic map, the IV version will be missing a key element).

+

2. All essential content must be preserved

+

IV pages should show the entire text of the article, along with all its formatting, media, and embedded content. This includes headings, subheadings, quotes, captions, photos, videos, links, etc.

+

3. Unnecessary elements must be removed

+

IV pages should display only the source’s content – removing all interface elements, advertisments and irrelevant embedded material.

+

4. Template must process all the pages it covers

+

Pages with irregular elements should be processed correctly. All media, embeds, quotes and separators should be properly displayed.

+

5. No extraneous info may be added

+

Any attempt to add content that is not present on the original page will cause your template to be rejected.

+

You may include the username of websites’ official channels in Instant View templates. The username is assigned to the channel property, and to be considered official, the channel must be labeled as such by the company or person who published it (on its website or social media).

+
+

More detailed criteria and clarifications are available below.

+
+
+

Submitting Templates

+

You can submit your template for review as soon as it covers a sufficient number of articles. Make sure you've enabled Track Changes for at least 10-15 different pages on the target website and that all IV pages are generated correctly.

+

When ready, simply tap Submit Template next to a template in the My Templates section:

+
+ +

Submitting a template from My Templates

+ +

Finding Issues

+

Anyone can check how well Instant View templates process articles on their respective websites, and may submit feedback using the Report Issue button.

+

Click to select and highlight incorrectly parsed blocks in the source page or in the Instant View result and provide a detailed explanation of what is wrong (check the criteria below for ideas). The author of the template will be able to see all issues, fix and resubmit their work.

+
+

Perfect Templates

+

To make it easier to report issues in Instant View templates, we’ve compiled this list of characteristics that make a perfect template. Please use the list below as a reference when looking for issues in templates.

+

1. IV Targets: Must Generate

+

Templates must generate Instant View pages for all relevant pages on the target website.

+

1.1. Pages with static article-like content

+
    +
  • News articles
  • +
  • Blog posts
  • +
  • Guides
  • +
  • Wiki entries
  • +
  • Documentation
  • +
  • Etc.
  • +
+
+

Tip: It may be a good idea to identify a common feature of all the IV-positive pages and add rules so that the template only applies to them. Note that these pages only need IV pages if their essential content is supported in the IV format — otherwise, see 2.3.

+
+

2. IV Targets: Must NOT Generate

+

Templates must not generate Instant View content for pages of the following types:

+

2.1. Pages with dynamic content

+
    +
  • Dynamically updated lists of articles
  • +
  • Catalogs
  • +
  • Forum threads
  • +
  • Search pages and search results
  • +
  • Etc.
  • +
+
+

Tip: IV pages are cached. As articles get older, their cached IV pages update less frequently. Any pages that update content in real time would subsequently display outdated IV pages to users — which is unacceptable.

+
+

2.2. Pages that require significant interaction

+
    +
  • Service areas of websites, such as Contact pages with forms
  • +
  • Store areas of websites, such as pages where users can buy products
  • +
  • Etc.
  • +
+
+

Tip: While it's possible to modify interactive components of a page into simple links, the IV format was primarily designed to allow Telegram users to enjoy web content in a quick and uniform way. Interacting with websites, buying things, writing reviews, etc. are outside of the current scope for IVs.

+
+

2.3. Pages featuring content not supported by the IV format

+
    +
  • Pages with unsupported embedded content that can't be displayed
  • +
  • Any other unsupported content
  • +
+
+

Tip: The rule is simple. If an essential part of an article is not available in the Instant View format, an IV page must not be generated. In most cases, this will happen automatically but template creators can further protect their templates from data loss by marking any unsupported essential content using the @unsupported function. See this section for advice on handling unsupported videos.

+
+

2.4. Inaccessible pages

+
    +
  • Pages that are fully or partially behind a paywall.
  • +
  • Pages that are only accessible after logging in, etc.
  • +
+

3. Essential Content

+

All essential content must be presented on the Instant View page.

+

3.1. General properties

+
    +
  • The title must be shown on the IV page (may need to include the kicker).
  • +
  • The subtitle must be shown on the IV page if a subtitle exists in the source.
  • +
  • The date of publication must be shown on the IV page if the date of publication is mentioned anywhere in the source (including meta tags).
  • +
+

These properties are also essential, but not always present or supported in IV:

+
    +
  • Author name can be shown on the IV page if an author is specified in the source.
  • +
  • Author name on the IV page can link to the author URL if an author URL is specified in the source.
  • +
  • The main image can be shown as a cover on the IV page if a suitable image exists in the source.
  • +
  • NEW Right-To-Left pages (Arabic, Persian, Hebrew, etc.) must have the dir="rtl" attribute set.
  • +
+
+

Important: See our Clarifications below for tips on how to best process cover images, date and time, author names and URLs, and other tricky elements.

+
+

3.2. Link preview

+
    +
  • The link preview must include a photo if a suitable image or document exist in the source.
  • +
  • If the page has a cover but the metadata contains no image or contains the generic site logo, you must use the cover as the photo.
  • +
  • The link preview requires a description.
  • +
  • If a short description exists in the source, it must be used for the link preview (OpenGraph descriptions, lead sections, etc.).
  • +
  • If the description in the metadata (routinely) doesn’t describe the contents of the article, your template must create a description using the subtitle or lead section, first paragraph, etc.
  • +
  • The site_name property must include the name that users see on the main page of the website (examples here).
  • +
  • It is advisable to generate proper link previews even for pages that do not generate an IV.
  • +
+
+

Note: Telegram apps will show site_name in the header of the IV. It must match the name that users see on the main page of the website (see examples) and it must not contain any additional data. For this reason metadata should not be used blindly. If the main page doesn’t display a site name, use the name they use on social networks (Telegram channels have priority).

+
+

3.3. Supported elements

+
    +
  • All important media (images, videos, slideshows, and other content that is relevant to the article) that exists in the source must be formatted accordingly.
  • +
  • Media captions must be included with the corresponding media, provided they exist in the source and can be reliably identified.
  • +
  • Credits in quotes and media captions must be formatted correctly.
  • +
  • Dividers must be converted to simplified dividers on the IV page if dividers exist in the source.
  • +
  • Anchor links must work properly on IV page if anchor links exist in the source.
  • +
+
+

Tip: Check that pages featuring unsupported content do not generate IV pages. In most cases, this will happen automatically, but it is a good idea to confirm this before submitting your template. Mark any unsupported essential content using the @unsupported function. See this section for advice on handling unsupported videos.

+
+

4. Content to be Removed

+

Anything that is not essential to the article in question should be removed from the Instant View page, including:

+
    +
  • Main navigation bars and menus (essential navigation may be adjusted to simple links)
  • +
  • Top bars
  • +
  • Side bars (can potentially be adjusted and appended to bottom of IV page)
  • +
  • Footers
  • +
  • Unsupported widgets (check supported embeds)
  • +
  • Advertisements
  • +
  • Banners
  • +
  • Social media links and buttons, including “Share” and “Like”
  • +
  • Other buttons (if it is essential, it must be simplified into a link)
  • +
  • Etc.
  • +
+

5. Extraneous Content

+

The resulting IV page may not contain any content not present in the original.

+
    +
  • No signatures or information about the template's author
  • +
  • No extra links or ads of any kind
  • +
  • Etc.
  • +
+
+

Tip: You may display the official Telegram channel of the website that published the article at the top of the IV page (by using the channel property). To be considered official, the channel must be labelled as such somewhere on the source website (doesn't have to be on the same page as the original article).

+
+

6. Clarifications

+
+

Below are some clarifications for the trickier aspects of creating perfect Instant View templates.

+
+

GENERAL PROPERTIES

+

6.1.1 Author name

+

Author name is required only if it is presented in the source article in a consistent, clear and identifiable way (in an html block with particular properties), especially if there's a name of an actual person.

+

In less obvious cases, what the user sees when viewing the original article in a browser has priority over invisible meta-information. Names of actual people are always preferable over entity names like 'team' or the name of the website.

+

You may omit the author in cases where no name can be seen by a regular user opening the original article in the browser. You may omit the name when there's no identifiable person, only the website's 'team', 'editors', 'website name' etc.

+

Absent author names for articles in which no author can be easily identified by a regular viewing user are not considered an issue.

+

6.1.2 Date and time

+

The date of publication is obligatory for news publications. It must be obtained by any means possible, including meta tags, etc. If the date is specified correctly, time is optional.

+

If conflicting dates are stored in multiple places on the source page, preference should be given to the time that is visible to an ordinary user who views the page in a browser.

+

The IV editor's 'Preview' section will always show the date/time in UTC format, while the 'Original' section may use a different time zone. It is possible for a perfect template to display a date/time that looks different than the original.

+

Support for time zones is optional, unless the time zone is reliably identifiable from the source, in which case it’s obligatory.

+
+

Tip: If given 'date published' and 'date last edited', use 'date published' for articles. For wiki-like entries 'date last edited' must be used.

+
+

6.1.3 Subtitle

+

A subtitle is a subordinate title of a published work or article giving additional information about its content. If this is present in the original article, a subtitle is required. Here's an example of a subtitle:

+
+ +

A Subtitle

+
+ +

Few publications actually use subtitles. More commonly, short summary sentences are shown below the title (and are called standfirst in the UK). These summary sentences are usually short and are not part of the article's text. It is advisable but not required to represent them as subtitle elements. Here's an example:

+
+ +

A Summary

+ +

6.1.4 Lead paragraph

+

Many publications use a slightly different style for their lead paragraphs. Unlike subtitles and summaries, the lead paragraph is part of the article's text. Even if the lead uses a different style from the rest of the text, it is less desirable to present it as a subtitle — but this is not a critical issue.

+

If the lead paragraph uses a different style, it is recommended to use bold or italic text.

+
+ +

A summary, then lead in bold

+ +

In the example above, the lead paragraph is highlighted in bold: “TAXI giant Uber has reportedly fired over 20 workers following an internal investigation into sexual harassment allegations.”

+

The article then continues: “The company told staff of the layoffs on Tuesday and related claims by law firm Perkins Coie, a person close with the case told Bloomberg.” It would be acceptable to present the “TAXI giant Uber…” paragraph as bold, or italic, or plain text.

+
+

Tip: Generally, it is advisable to avoid setting too much text as the subtitle. If the website publishes summaries that take an entire paragraph or even multiple paragraphs, it's better to use italic/bold text instead of the subtitle element to represent this content in IV.

+
+

6.1.5 Kicker

+

Kickers are separately formatted parts of the title supported in IV 2.0 with the kicker property. The kicker property must be set if a kicker is present and its text is actually a part of the title/story (see 'UBER SEX CLAIMS' on the screenshot above).

+

If the kicker represents a regular section or category into which the article falls, (e.g. 'CRIME: Seventy suitcases stolen from Heathrow airport'), it should be omitted. Missing section/category kickers are not considered an issue.

+

IMAGES AND MEDIA

+

6.2.1 Image quality

+

When several image resolutions are available and can be extracted reliably, the IV page should use better quality images (within reason). The optimal resolution range is 1280px-2560px, using larger images is pointless. Note that images that are too large (>5 MB) will fail to load. We recommend updating your template to IV 2.1 to automatically extract optimal images from the srcset attribute.

+

If for some reason it is only technically possible to obtain low-resolution versions of images (lower than 320px) for a page, but its original web version has high-resolution images, the page should not generate an IV.

+
+

Note: For the Icon type, we highly recommend setting the correct size using the width/height attributes so that they appear the same way in IV as they do in the text. Otherwise, you risk grabbing the 3x version of an emoji and displaying it as a full-blown image.

+
+

See also: Infographics

+

6.2.2 Cover images

+

It is obligatory to use a cover image:

+
    +
  • If the image is present on the page and described in the source as “featured-img”, “cover”, “lead_img”, “main_image”, etc.
  • +
  • When the article has a cover on the source website (above the title or subtitle).
  • +
+

In other cases, cover images are optional:

+
    +
  • We recommend setting a cover If there's a suitable image directly below the title/subtitle.
  • +
  • While it is possible to use GIFs and videos as cover, in most cases, it's better to leave these elements in the body of the article.
  • +
+

Sometimes, a cover is less desirable:

+
    +
  • In single-image, single-video, or single-GIF articles with no significant text.
  • +
  • When text on the cover image repeats the title.
  • +
  • Images from meta-tags are not recommended: they might be suitable, but are usually designed with sharing widgets in mind and don’t work well in the IV environment.
  • +
+

A cover must not be set if:

+
    +
  • The chosen image is clearly inappropriate for the cover.
  • +
  • The chosen image appears several paragraphs into the article and it is possible to reliably identify this.
  • +
  • The cover image is duplicated in the article.
  • +
  • Several images appear in the article one after another. In this case, the template should not break the sequence by extracting one of them as a cover (example).
  • +
+
+

Tip: Cover images can also have captions in IV, don't lose them.

+
+

6.2.3 Galleries and slideshows

+

Slideshows are required only if the source article shows several photos or other media as a slideshow or gallery. If this is the case, do the following:
- Present all images in the IV as a gallery, if possible.
- If that's not possible, keep a link to the full gallery.
- If none of the above are possible, generate no IV for the page.

+

If the source has several ordinary images/videos/GIFs following each other in the source, you may also convert them into a slideshow, but this is purely optional. This makes more sense in cases when images serve as additional content (e.g., a long text about a new car which is followed by ten images of the car).

+

We will not accept issue reports based on presence or absence of slideshows for ordinary images following each other in the source article.

+

EXCEPTION! Slideshows must not be used when:

+
    +
  • The slideshow fetches unrelated images (e.g. an illustration and a disclaimer).
  • +
  • The article consists entirely of a slideshow (and its caption/description) and there's no other content.
  • +
  • The article uses images/videos/GIFs with captions as the main medium (e.g.: travel blogs that show many photos with captions, step-by-step crafting guides, cooking recipes, etc.).
  • +
+

In the cases above, use images with captions (or even plain paragraph text) following one another.

+
+

Tip: Remember that captions should be preserved for all images in the source. If you lose captions for images you've put into a slideshow, it's a valid issue. IV Slideshows support both a caption for the entire slideshows and different captions for each individual element.

+
+

6.2.4 Captions

+

Any captions present in the source article must be preserved. This includes captions for the cover image and captions for all individual elements of slideshows.

+
+ +

All Captions Preserved

+
+ +

If the image has no caption, but has meaningful text in the alt attribute, you may use that text as the caption. This is optional, we will not accept issue reports about alt-text missing from captions.

+
+

Tip: Please don't include meaningless alt-text as captions (e.g., the PlayStation blog always puts the name of the corresponding game in the alt attribute of all screenshots – there's no need to reproduce that on the IV page.)

+
+

6.2.5 Media credits

+

IV 2.0 supports a dedicated <cite> tag for credits in media captions. Credits in captions must be preserved and placed inside the appropriate tag, provided it is possible to reliably identify them.

+

6.2.6 Infographics

+

Tall infographic images are currently unreadable in Telegram apps. If there’s a reliable way to identify them (e.g., consistently used attributes or a specific section on the website that only contains infographics) the IV must add an image link to the full version of the image. If there is no reliable way to identify such images and they are not consistently featured on the website, it is acceptable to leave infographics as ordinary photos.

+

LINKS

+

6.3.1 Image links

+

In IV 2.0, <img> tags support the attribute href to make the image clickable. It must be used to preserve the link behind the image if it leads to some different page or content.

+

Image links are required only if they are meaningful. If the link opens the same image in a higher resolution, it must be removed. Exception: Infographics.

+

6.3.2 Related Articles and other “More” links

+

IV 2.0 supports a dedicated type for RelatedArticles. Related articles are relatively static individual links or blocks of articles which are thematically related to the current one. They don't have to be located on the same domain.

+

It is obligatory to format “Related articles” links using the new <related> tag and/or remove other “More” links, provided all these links can be extracted from the article without endangering essential information.

+

We designed the RelatedArticles block to deliver a better IV-reading experience to users. The IV engine automatically checks whether articles in the <related> block have an IV, you don't need to worry about this.

+
+

If pages have no IV, they will not be displayed. If this results in an empty block, it will not be displayed.

+
+

There are cases when you must not use RelatedArticles:

+

1. Keep but don’t format as Related

+
    +
  • Links that can’t be safely and reliably extracted from the article text.
  • +
  • Links that are part of essential content for the article (without which the article makes no sense).
  • +
  • Navigational links to the other parts of multipart articles.
  • +
+
+

Never put essential links into <related>, they will be lost if the page they are leading to doesn’t have an IV.

+
+

2. Remove

+
    +
  • “More” blocks that show different links each time the page is reloaded.
  • +
  • (Consistently) random unrelated articles.
  • +
  • Dynamic lists of "Latest articles from this category”, “More articles by this author”, “Featured articles”, etc.
  • +
  • Lists of categories (links to dynamic lists).
  • +
  • External links leading to “Partner sites” (e.g., You won't believe what this game does to people!).
  • +
+

6.3.2.1. Formatting Related Articles

+

It is sufficient to put links into <related>. You only need the <a> – the IV engine will handle the rest (title, description, etc.). Your IV may only have one block of related articles at the end of the page. If the source has several blocks, merge them together or choose which one to keep.

+

Headers
Only one header may be present for the block of related articles at the end of the page. We will not accept reports about missing headers on Related blocks (unless the header contains critical information).

+

Note that if a header for a related article is not reliably extractable from the body, you must not use <related> for that link. (Otherwise, if the link gets no IV, the text will have a hanging header).

+

“Inline” blocks
You may leave “inline” related links in the middle the article. If you do, these <related> blocks must not have headers (unless the header contains critical information).

+

6.3.3 Channel links

+

You may display the official channel of the website that published the article on the IV page by using the channel property:

+
+ +

Official Channel Link

+
+ +

This channel link is optional. We will not accept issue reports based on the absence or presence of a channel link, with one exception:

+

If the channel property is set, the channel it is pointing to must be the official channel. To be considered official, the channel must be labelled as such somewhere on the source website (doesn't have to be on the same page as the original article).

+

6.3.4 Source links

+

Some articles include a link to their source. This link could be inserted at the end of the article in the format via <a href="https://example.org">Website Name</a>. A word with a similar meaning could be used instead of 'via' for websites in other languages.

+

6.3.5 Author links

+

Author links are optional. If there's a clearly identifiable author and they have a page on the target website, use that one. In more ambiguous cases, use what the regular viewing user can see in the original article or omit the link altogether.

+
+

Tip: IV only supports one author URL per article. If there are several in the article, it's permissible to choose one or omit them altogether.

+
+

6.3.6 Social media links

+

Sharing buttons and other interface-based links must be removed as per Rule 4.

+

Many articles include something like “check out our Facebook page” at the end of the text. Such links must be removed if they are placed in a reliably identifiable container.

+

6.3.7 Multi-page articles

+

To parse several pages into one IV, update your template to IV 2.1 (which skips canonical redirects by default) and use the inline function. Make sure to check in-app to see if your solution is working. The IV should open correctly when users share a link to any part of the article.

+

If pages can’t be safely assembled into one IV, navigation must be preserved. Please confirm that navigation is working and all further pages open correctly. If navigation can’t be preserved, the article must not generate an IV.

+

Never format links to the other parts of an article as related. This may break navigation if one part of the article fails to generate IV (since related articles without IVs are omitted in the block).

+

UNSUPPORTED CONTENT

+

Pages that display unsupported content (e.g. an interactive map widget) must not generate IVs.

+

Important: We will accept issue reports requesting to generate IVs for pages with content previously deemed unsupported if you include a link to a template that fully supports the content in question. This does not apply to supporting content from popular widgets that are likely to get official support in the future, see the list below.

+

6.4.1 Complex tables

+

IV 2.0 includes support for Tables. IVs can now be generated for articles with simple tables. However, complex tables may not render through existing means, and must be tagged as @unsupported.

+

Important: We will accept issue reports requesting to generate IVs for pages with content previously deemed unsupported if you include a link to a template that fully supports the content in question.

+

6.4.2 Video/Audio from unsupported players

+
    +
  • If the unsupported widget has an iFrame version, make it into an <iframe>. If you do that, the IV page will not be generated due to unsupported content, but things will work out of the box if and when we support that widget.
  • +
  • If it is not possible to represent the widget as an iFrame, but it is possible to get a direct link to the video/audio, use that link to generate a <video> or <audio> with the correct src attribute.
  • +
  • Otherwise, mark the object with the @unsupported function.
  • +
+
+

If an article that is otherwise supported includes a video or an audio track that would cause it to become unsupported, it is acceptable to include a link to the video instead of unsupporting the article. If there’s no other content on the page, it must not generate an IV.

+
+

6.4.3 Auxiliary widgets

+

Some pages include unsupported widgets that are not essential for the understanding of the article. A local news site may show a weather forecast widget on their pages. A business newspaper may show a stock price ticker for the companies covered in the article. Some websites include “And what would you do?” polls at the end of some of their articles to increase user engagement.

+

Such non-essential widgets may be omitted in IV. Warning: Make sure that this dynamic auxiliary data doesn't get added to the static IV page.

+

6.4.4 Popular Widgets

+

Telegram is likely to support the following popular widgets in the future:

+
    +
  • Reddit
  • +
  • Spotify
  • +
  • Getty images
  • +
  • Imgur
  • +
  • Coub
  • +
  • Soundbank
  • +
  • JW Player
  • +
  • Twitter Timeline
  • +
  • Infogram
  • +
  • VK Post
  • +
  • WordPress Embed Post
  • +
  • Yandex.music
  • +
+

Supporting content from these widgets is optional since it will eventually become available through official means.

+

OTHER

+

6.5.1 Subdomains

+

Subdomains that present content in a similar way to the higher-level domain must be supported.

+

If a subdomain looks like a separate website, supporting it is optional. We will accept issue reports if a template generates broken IV pages for any subdomain.

+
+

Note: We will add the necessary redirects so that Telegram apps will show IVs for articles on the main domain when users share links to the mobile version. It is not necessary to support pages from the mobile version.

+
+

6.5.2 Service areas

+

Non-article pages are strictly optional, unless there’s interactive content – in which case they must not generate IVs. This includes Terms of Service, Privacy Policies, About sections, Contacts sections and special “Print” versions of articles.

+

6.5.3 Single-media pages

+

Support for pages that only contain a single media item (photo, GIF, video, etc.) is required if:

+
    +
  • The pages are routinely accessible to users through the main navigation of the website and include other data like title, date, etc.
  • +
  • Such pages are the main medium for the domain in question (e.g. Pikabu.ru)
  • +
+

If the single-media page contains unsupported media, it must not generate an IV. See 6.4.2 Unsupported Video and Audio content.

+

In all other cases, supporting single-media pages is optional.

+

6.5.4 Ancient lore

+

Support for news articles from 2015 and earlier is optional. We won’t accept issue reports on news articles posted before 2016 if the template correctly handles articles published recently.

+

6.5.5 Quotes

+

Quotes must be formatted to match their appearance in the source article, provided it is possible to identify them (and their type) in a reliable way. Line breaks in quotes must be preserved.

+

Quotes support <cite> tags. If a quote includes an author, it must be formatted accordingly (provided the author can be reliably identified in the source).

+
+

7. Checklist Changelog

+

We will be updating this document with further clarifications as new issues arise.

+

Mar 20 2019

+
+

Don’t miss the IV 2.1 update.

+
+

Checklist 2.2:

+

Expanded clarifications

+
    +
  • 3.2, Link Preview: site_name must include the name that users see on the main page of the website; cover photo must be used in preview if metadata is empty or contains site logo; template must generate proper description if metadata is unsuitable
  • +
  • 3.3, Supported Elements: Credits must be supported in media captions and quotes
  • +
  • 6.1.2, Date and Time: Time is optional if the date is set correctly; time zones are optional, unless reliably identifiable in the source
  • +
  • 6.2.1, Image Quality: for issues to be accepted, the difference in image quality must be significant; higher resolution images must be reliably extractable; note
  • +
  • 6.3.1, Image links: Must be preserved if they are meaningful
  • +
  • 6.3.2, Related articles: Details on when RelatedArticles must not be used; Formatting guidelines
  • +
  • 6.4, Unsupported content: Optional to extract content from popular widgets which are scheduled for official Telegram support, even if another template does this
  • +
  • 6.4.2, Unsupported Video/Audio: Possible to include a link to an audio/video instead of unsupporting an otherwise fine article
  • +
  • 6.5.1, Subdomains: Added a note on mobile versions
  • +
+

Added NEW clarifications

+ +
+

Feb 6 2019

+

Checklist 2.1

+
    +
  • Related Articles (6.3.2). Considerably expanded guidelines. Now obligatory to put related links into the new “Related articles” block, provided they are reliably identifiable in the source. Other links should be removed, see full details.
  • +
  • Cover Images (6.2.2). Added conditions when covers are obligatory.
  • +
  • Galleries and Slideshows (6.2.3). Added detailed explanations on gallery usage.
  • +
+
+

Feb 2 2019

+

Checklist 2.0: Changes for the Second Instant View Contest

+

The Clarifications section has been rewritten to better organize the lore we've accumulated during and after the previous contest. These clarifications have been updated:

+
    +
  • Tables are supported (if they are not too complex).
  • +
  • Nested lists (and lists inside tables) are supported.
  • +
  • RTL-support has been introduced and is obligatory for RTL pages.
  • +
  • Related Articles got a dedicated element (UPDATED 6.02, see guidelines!).
  • +
  • Image links are supported.
  • +
  • Added guidelines on image quality.
  • +
  • Updated guidelines for cover images
  • +
  • The new Icon type requires careful handling.
  • +
  • Media credits can be formatted properly (if separable from caption).
  • +
  • Kickers in titles got a dedicated element for certain cases.
  • +
  • Added guidelines for supporting subdomains.
  • +
  • Updated guidelines for social media links
  • +
  • Updated the guidelines for site_name in link previews.
  • +
+

Don't forget to check out what's new in IV 2.0 to know what your templates are now able to support.

+
+ +
+
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/docs.html b/data/instantview.telegram.org/docs.html new file mode 100644 index 0000000000..51203e87be --- /dev/null +++ b/data/instantview.telegram.org/docs.html @@ -0,0 +1,1527 @@ + + + + + Instant View Manual + + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+
+

Instant Views and Where to Find Them

+ +
+ +

This document describes Telegram's Instant View format in stupefying detail. If this is your first time hearing about Instant View, please check out our Introduction and Sample Templates before you dive in.

+

If you're comfortable with the idea of Instant View templates, let's look at what makes them tick. To begin with, this is our in-house artist's idea of how Instant View pages are generated:

+
+ +
+ +

It turns out, he is not entirely wrong. This is how Instant View pages are really generated:

+
    +
  1. Whenever Telegram needs to display a link preview for a URL, it also checks whether an Instant View template exists for that domain.
  2. +
  3. If a template exists, our Instant View Bot obtains the page using the URL (it only processes pages that have the MIME-type text/html).
  4. +
  5. The bot then applies rules from the template that determine the positioning of the key elements on the source page (using XPath 1.0 expressions) and modifies the page content to fit the Instant View format.
  6. +
  7. The edited page is used to create a new Instant View page that will be displayed to the user.
  8. +
+

This document will explore the Instant View Format, the Types of Rules your template can utilize, as well as some useful XPath constructs, conditions, and functions that may help you build better templates.

+

This manual was intended to be used as a reference, so you don't have to read the entire thing to get started. Our sample templates make for a much better entry point. You can check back here whenever something is not clear.

+

Recent changes

+

September 10, 2020

+
    +
  • Added the new ~allowed_origin option
  • +
  • Added the new @load function
  • +
  • The @inline function now supports the silent parameter which ignores errors while fetching a page
  • +
+

March 20, 2019

+

Version 2.1

+
    +
  • Supported the srcset attribute in Image and Icon types. The IV engine will automatically take the highest image resolution available (but not higher than 2560px).
  • +
  • The @match function now returns only nodes which content was matched by regular expression
  • +
  • The @replace function now returns only nodes which content was replaced by regular expression
  • +
  • The @inline function no longer follows canonical redirect links while fetching a page
  • +
+

Also in this update:

+ +

December 10, 2018

+

Instant View 2.0 expands the platform with support for right-to-left languages, new page blocks, useful functions and much more. We recommend using the latest version in your templates. To do this, add the following rule at the beginning of the template:

+
~version: "2.0"
+

Below is a list of changes in version 2.0:

+

New properties:

+
    +
  • kicker
  • +
  • site_name
  • +
+

New types:

+
    +
  • Map
  • +
  • Table
  • +
  • Details
  • +
  • RelatedArticles
  • +
  • Marked
  • +
  • Subscript
  • +
  • Superscript
  • +
  • Icon
  • +
  • PhoneLink
  • +
  • Reference
  • +
+

New types of rules:

+ +

New functions:

+ +

Other features and improvements:

+
    +
  • Xpath query results can be appended into variables using + (see more)
  • +
  • New XPath function ends-with
  • +
  • Lists can contain block elements such as paragraph, nested lists, tables and so on
  • +
  • Support for attribution in media captions (<cite> tag)
  • +
  • Support for image links (href attribute for the Image type)
  • +
  • Unsupported elements (such as an image inside the blockquote) now generate an error instead of moving up
  • +
  • Improved @simplify function for better processing RichText (e.g. saves line breaks formed by block elements)
  • +
+

Instant View Format

+

An Instant View page is an object with the following properties:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParameterTypeDescription
title RequiredRichTextPage title
subtitleRichTextPage subtitle
kicker RichTextKicker
authorStringAuthor name
author_urlUrlAuthor link
published_dateUnixtimeDate published
descriptionStringA short description (used in link preview)
image_urlUrlLink preview photo (used in link preview)
document_urlUrlLink preview document (used in link preview)
site_name StringName of website (used in link preview)
channelStringThe username of the article author's (or the originating website's) channel on Telegram in the format @username
coverMedia (Image/Video/Embed/Map)Page cover
body RequiredArticlePage content
+

RTL support

+

The platform supports right-to-left languages. If <html> tag or tag referenced by body property has the attribute dir="rtl", the page will be marked as RTL. In case this attribute is not set, you can set it manually to display the page in Instant View as RTL using the following rule:

+
  @set_attr(dir, "rtl"): $body   # if body is already defined
+  @set_attr(dir, "rtl"): /html   # alternative way
+

Supported types

+

The IV page object can hold the following types:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
TypeAllowed childrenDescriptionHTML counterpart
ArticleHeader
Subheader
Paragraph
Preformatted
Divider
Anchor
List
Blockquote
Pullquote
Media
Image
Video
Audio
Embed
Slideshow
Table
Details
Footer
RelatedArticles
Page content<article>
HeaderRichTextMajor headingWe use the top-level of the <h1><h4> headings found on the source page
SubheaderRichTextMinor headingWe use the remaining headings <h1><h4> as well as <h5><h6> headings
ParagraphRichTextA paragraph<p>
PreformattedRichTextPreformatted text<pre> with the optional attribute data-language*
AnchorAnchor<anchor> with the attribute name that contains the anchor name
DividerA separator<hr>
ListListItemA list<ul> for a bullet list, <ol> for a numbered list
ListItemversion 1.0:
RichText

version 2.0:
Header
Subheader
Paragraph
Preformatted
Divider
Anchor
List
Blockquote
Pullquote
Media
Image
Video
Audio
Embed
Slideshow
Table
Details
A list item<li>
BlockquoteRichText
QuoteCaption
A block quote<blockquote>
PullquoteRichText
QuoteCaption
A pull quote<aside>
QuoteCaptionRichTextCaption of a quote<cite>
MediaImage
Video
Audio
Embed
Map
MediaCaption
Media content<figure>
ImageAn image<img> with the attribute src and the optional attribute href to make the image clickable. Allowed formats: GIF, JPG, PNG (GIF would be converted into Video type by IV)
As of version 2.1, supports the attribute srcset (srcset has higher priority than src, the same as in a browser; IV gets the highest available resolution under 2560px).
VideoA video<video> with the attribute src, or containing the tag <source type="video/mp4"> with the attribute src
AudioAn audio<audio> with the attribute src, or containing the tag <source> with the attribute src and the attribute type (possible types: audio/ogg, audio/mpeg, audio/mp4)
EmbedAn embedded element<iframe> with the attribute src. List of supported embeds
Map A map<img> or <iframe> with the attribute src referring to Google or Yandex maps
SlideshowMedia (Image/Video)
Image
Video
MediaCaption
A slideshow<slideshow>
MediaCaptionRichTextMedia caption<figcaption>
As of IV 2.0, can contain an additional tag <cite> with attribution (author, creator or source of the media)
Table TableCaption
TableRow
A table<table>
TableCaption RichTextA table caption<caption>
TableRow TableCellA table row<tr> with the optional attributes align, valign, can be wrapped with <thead> or <tbody> or <tfoot> with the optional attributes align, valign
TableCell RichTextA table cell<td> for a standard cell, <th> for a header cell, with the optional attributes align, valign, colspan, rowspan
Details 
(version 2.0+)
DetailsHeader
Header
Subheader
Paragraph
Preformatted
Divider
Anchor
List
Blockquote
Pullquote
Media
Image
Video
Audio
Embed
Slideshow
Table
Details
A collapsible block<details> with the optional attribute open to be opened by default
DetailsHeader 
(version 2.0+)
RichTextA visible heading for the collapsible block<summary>
RelatedArticles Header
Link
Related articles<related> containing one of <h1><h6> tag as header of the block and <a> tags with the attribute href containing a URL of related article. Note: Only articles that have an IV will appear in this block on the IV page.
FooterRichTextThe footer<footer>
RichTextBold
Italic
Underline
Strike
Fixed
Marked
Subscript
Superscript
Icon
Link
EmailLink
PhoneLink
LineBreak
Anchor
Reference
String
Formatted textText elements and supported tags
BoldRichTextBold text<b> or <strong>
ItalicRichTextItalic text<i> or <em>
UnderlineRichTextUnderlined text<u> or <ins>
StrikeRichTextStrikethrough text<s> or <del> or <strike>
FixedRichTextMonospace text<code> or <kbd> or <samp> or <tt>
Marked RichTextMarked text<mark>
Subscript RichTextSubscript text<sub>
Superscript RichTextSuperscript text<sup>
Icon A small image inside the text<pic> with the attribute src, width, height. Can contain the attribute optional if the image is not important and may be ignored. Allowed formats: JPG, PNG.
As of version 2.1, supports the attribute srcset (srcset has higher priority than src, the same as in a browser).
LinkRichTextA link<a> with the attribute href containing a URL
EmailLinkRichTextA link to an email address<a> with the attribute href containing a mailto: link
PhoneLink RichTextA link to a phone number<a> with the attribute href containing a tel: link
Reference RichTextA reference<reference> with the attribute name that contains the reference name
LineBreakLine break<br>
+
Note on code languages
+

Telegram apps currently do not support code highlighting, but they will in the future. For this reason, it is advisable to include the code language attribute (data-language) for large <pre> blocks if it is supplied in the source.

+
+

Types of Rules

+

Instant View rules are instructions that tell our IV bot where to find the meta-elements on the source page and how it should modify the content of the page when an Instant View page is created.

+

Each new line in a template describes a new rule. When the bot renders a page into the Instant View format, it applies rules from the relevant template one after another and ignores any empty lines. You can leave comments by starting a line with #, all following text on that line will be ignored unless enclosed in quote marks. You can use the \ symbol to carry a rule over to the next string, like this:

+
# Comment 
+# You can break up \
+  a long rule into \
+  multiple strings
+

Most rules are based on XPath 1.0 expressions used to locate the required nodes on the source page.

+

A block of rules may have a name. In this case, it can be reused in other rules.

+

We support the following types of rules:

+

Conditions

+

Conditions offer unlimited flexibility for your templates. Rules of this type begin with the symbols ? or ! and use the following format:

+
?condition:  xpath_query   # condition example
+!condition:  regexp        # parameter on the right depends on the type of the condition
+?condition                 # some conditions don't have parameters
+

Groups of conditions that immediately follow one another are interpreted as a block. ?-rules follow the OR logic when joined, while !-rules follow the AND logic. This means that for the bot to apply each block, all !-conditions in the block and at least one of the ?-conditions within it must be met. This also means that each block must have at least one ?-condition.

+

Blocks of conditions split your rule set into groups. Groups of rules that do not have any conditions are always applied. All other groups are only applied if their conditions are met.

+

Examples

+
# If a rule is placed here, it will be applied
+# Same with the one here
+
+?false               # This condition is always false
+# The rule placed here will never be applied, because the condition is not met
+# Very useful indeed
+
+?exists: //article   # This condition is true if the page has an article tag
+# On these lines, a new group of rules is located, and it will be applied if
+# there's an article tag on the page, despite the ?false condition above
+
+?exists: //article
+?exists: //div[@id="article"]
+!exists: //meta[@property="og:title"]
+# The rules below this block will be applied if an <article> tag or a
+# <div id="article"> can be found, this tag must also be present: <meta property="og:title">
+

+ +
+

Check out the Supported Conditions to see what works out of the box »

+
+

Properties

+

Properties are the building blocks for your IV page. Check the Instant View Format for a list of properties that can be used when creating IV pages (you can also define custom properties, but they will not be used anywhere on the resulting IV page). Use this format to fill properties:

+
property: xpath_query
+property: "Some string"
+property: null
+

Properties store the first node that matches the XPath expression xpath_query. By default, if a property already has a value, it will not be overwritten. You can change this behavior by adding ! to the property name – in this case a new non-empty value can be assigned. If you add !! to the property name, even an empty new value can be assigned to the property.

+

You can also assign a string to the property instead of the xpath_query. In this case, the property will contain a text element with the specified text. It is also possible to assign null to discard the property's value (will only work with !!).

+

Examples

+
title:   //article//h1      # Looking for the 'title' in the article heading
+title:   //h1               # If not found, checking for any headings at all
+title:   //head/title       # If no luck either, trying the <title> tag
+?path: /blog/.*             # On pages in the /blog/ section 
+title!:  //div[@id="title"] # we prefer to use <div id="title">, if present
+?path: /news/.*             # On pages in the /news/ section
+title!!: //h3               # title is always in an h3 tag
+
+author:   //article/@author  # Get author name from the author attribute
+?exists:  //article[has-class("anonymous")]    
+author!!: null               # Don't display author for anonymous posts
+
+

Reminder: The title and body properties are required for an IV page to be created.

+
+

Variables

+

Variables are useful for storing and manipulating nodes before assigning them to properties for the final IV page. Variable names begin with the $ symbol. Use this format to initialize them:

+
$variable: xpath_query
+$variable: "Some text"
+$variable: null
+

Variables store a list of nodes that match the Xpath expression xpath_query. If a variable is assigned for the second time, its previous value is overwritten. You can change this behavior by adding ? to the variable name. You can also append a list of nodes to the previous one by adding + to the variable name.

+

You can also assign a string to the variable instead of the xpath_query. In this case, the variable will contain a list with one text element that has the specified text. It is also possible to assign null to discard the variable's value.

+

Examples

+
$images:  //img
+$images:  //img[@src]     # the previous value will be overwritten
+$images?: //article//img  # a new value will only be assigned if the variable is empty
+$medias:  //img
+$medias+: //video         # now $medias contains all img and video tags
+

Options

+

Options affect how the page is processed by the bot. Options begin with the ~ symbol. Use this format to set them:

+
~option: "value"
+~option: true
+

Options can be set with values in JSON format.

+

Examples

+
~version: "2.1"
+

+ +
+

Check out Supported Options to see what else works out of the box.

+
+

Functions

+

Functions are extremely flexible, but you'll probably mostly use them to strip unnecessary nodes from the page and to replace certain elements with others. Function names begin with the @ symbol, you can use the following format:

+
@function:                 xpath_query   # a function without parameters
+@function(param):          xpath_query   # additional parameters are placed in paretheses
+@function(p1 p2):          xpath_query   # a function with two parameters
+@function(p1, "param #2"): xpath_query   # parameters can be separated by commas
+                                         # and enclosed in quote marks when needed
+@function:                 "Some text"   # use string instead of xpath_query if needed
+

The main argument of a function is a list of nodes that match the Xpath expression xpath_query. You can also use a string as the main argument instead of an xpath_query. In this case, the main argument passed to the function will be a list with one text element that has the specified text.

+

Examples

+
@remove:            //header               # removes all <header> tags found on the page
+@replace_tag(<h1>): //div[@class="header"] # replaces all <div class="header"> tags with <h1>
+<h1>:               //div[@class="header"] # an alias for @replace_tag(<h1>)
+

+ +

Note: You may find the @debug function particularly useful when creating XPath expressions.

+
+

Check out Supported Functions to see what else works out of the box.

+
+

Block Functions

+

Block functions manipulate blocks of rules. Block function names also begin with the @ symbol, you can use the following format:

+
@function(xpath_query) {   # opening bracket should be at the end of the line
+  $variable: xpath_query   # some other rules here
+  @function: $@            #   inside the block function
+}                          # closing bracket should be on a separate line
+

A block function can contain another block function so they can be nested. Block function can not contain conditions.

+
+

Please note that block functions that execute a block of rules several times (map, repeat, while, while_not) have a limit on the total number of iterations for the entire template.

+
+

Examples

+
@if( //article ) {    # if <article> exists
+  @append(<p>): $$    #   append paragraph into it
+}
+

+ +
+

Check out Supported Block Functions to see what else works out of the box.

+
+

Include

+
+

Note: This is a service rule, it will not work in your templates. It was included in this reference to give you a better understanding of how the system works. You can see an example of this rule at work in the Processing Pages section.

+
+

Rules of this type begin with the + symbol and use the following format:

+
+ rules
+

This rule inserts a block of rules with the specified name. In most cases, the name corresponds to the domain to which the rules apply.

+

Examples

+
+ core.telegram.org # inserting the block of rules that is used for core.telegram.org
+?not_exists: $body
++ telegram.org      # inserting the block of rules that is used for telegram.org
+

Special variables $$ and $@

+

The special variables work within a group of rules.

+
    +
  • The $$ variable always contains the result of the most recent XPath query.
  • +
  • The $@ variable holds the return of the most recently run function.
  • +
+

These variables come in handy when you're creating chains of rules. If a rule is missing xpath_query, the statement is considered to be equal to $$.

+

Examples

+
# Put a picture into a <figure> tag, then set it as the cover
+@wrap(<figure>): //img[@id="cover"]
+cover:           $@
+
+# Insert a divider before each div.divider that's no longer required
+@before(<hr>):   //div[has-class("divider")]
+@remove          # this is the same as @remove: $$
+

Extended XPath

+

For your convenience, you can use the following constructs in your XPath expressions.

+

Context

+

Regular XPath queries search for nodes in the context of the entire document. To specify the context for a particular expression, you can use variables in the format $context. If a matching variable exists, the query will be made relative to each variable node. If it doesn't and a matching property exists, the query will be made relative to the property node. If no matching variables or properties exist, the query return an empty list.

+

Examples

+
$headers:      //h1              # all <h1> tags on the page
+article:       //article         # the first <article> tag on the page
+$art_headers:  $article//h1      # all <h1> tags inside article
+$header_links: $art_headers//a   # all <a> tags inside each $art_headers node
+

Zeroing in on nodes

+

The result of an XPath query is always a list of matching nodes. If you'd like to narrow the list down to a single node, you can use the following syntax: (xpath_query)[n], where n is the number of the desired node. Numbering starts at 1, you can get the last node by using the last() function. This syntax can only be applied to the entire expression.

+

Examples

+
$headers:    //h1                    # all <h1> tags on the page
+$header2:    (//h1)[2]               # the second <h1> tag on the page
+$header2:    ($headers)[2]           # same
+$last_link:  ($header2//a)[last()]   # the last link inside $header2
+

has-class

+

You will often need to locate nodes that have a certain class. To do this, you can use the has-class("class") function that serves as an alias for the expression contains(concat(" ", normalize-space(@class), " "), " class ").

+

Examples

+
# Transform all div.header elements into h1
+<h1>: //div[contains(concat(" ", normalize-space(@class), " "), " header ")]
+# same idea, but much shorter
+<h1>: //div[has-class("header")]
+

ends-with

+

XPath has a starts-with function that checks whether the first string starts with the second string but does not have ends-with. In IV you can use the ends-with("haystack","needle") function that serves as an alias for the expression (substring("haystack", string-length("haystack") - string-length("needle") + 1) = "needle").

+

Examples

+
# Select all JPG images
+@debug: //img[(substring(@src, string-length(@src) - string-length(".jpg") + 1) = ".jpg")]
+# the same, but much shorter
+@debug: //img[ends-with(@src, ".jpg")]
+

prev-sibling

+

An axis that selects the previous sibling of the current node. Serves as an alias for the expression preceding-sibling::*[1]/self.

+

Examples

+
# Transform all div nodes, that immediately follow img nodes into figcaption
+<figcaption>: //div[./preceding-sibling::*[1]/self::img]
+# the same
+<figcaption>: //div[./prev-sibling::img]
+

next-sibling

+

An axis that selects the next sibling of the current node. Serves as an alias for the expression following-sibling::*[1]/self

+

Examples

+
# Join paragraphs following each other into one, separating them with a line break
+@combine(<br>): //p/following-sibling::*[1]/self::p
+# the same, but shorter
+@combine(<br>): //p/next-sibling::p
+

Supported conditions

+

Below are conditions supported in Instant View rules.

+

domain

+
domain: regexp
+

Checks whether the domain of the current page matches a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for *.subdomain.example.com URLs
+?domain: .+\.subdomain\.example\.com
+

domain_not

+
domain_not: regexp
+

Checks whether the domain of the current page does not match a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for *.subdomain.example.com URLs with an exception for dev.subdomain.example.com
+?domain:     .+\.subdomain\.example\.com
+!domain_not: dev\.subdomain\.example\.com
+

path

+
path: regexp
+

Checks whether the path to the current page matches a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for example.com/news/* links
+?path: /news/.+   # no need to escape the slash
+

path_not

+
path_not: regexp
+

Checks whether the path to the current page does not match a regular expression. The check is case-insensitive, so the actual expression used will look like this: /^regexp$/i.

+

Examples

+
# Rule for example.com/news/* links with an exception for example.com/news/recent
+?path:     /news/.+
+!path_not: /news/recent
+

exists

+
exists: xpath_query
+

Checks whether target nodes exist on the current page.

+

Examples

+
# Apply rule only to pages with an <article> tag
+?exists: //article
+

not_exists

+
not_exists: xpath_query
+

Checks whether target nodes do not exist on the current page.

+

Examples

+
# Apply rule only to pages with an <article> tag, that do not include any quotes.
+?exists:     //article
+!not_exists: //article//blockquote
+

true

+
true
+

A condition that is always true.

+

Examples

+
?path:    /blog/.+
+# Rules for the blog section go here
+?true
+# Rules that go here will be applied to all pages
+

false

+
false
+

A condition that is always false.

+

Examples

+
?path:    /news/.+
+# Rules for the news section go here
+?false
+# Rules that go here will never be applied
+

Supported options

+

Below are options supported in Instant View rules.

+

version

+
~version: "2.1"
+

Sets the version of IV used in the template. The behavior of some IV functions may change according to the version provided (see the manual of corresponding function).
The value must be one of "1.0", "2.0" or "2.1". We recommend using the latest version, 2.1.

+

Examples

+
~version: "2.1"
+# Now you can use new features from IV 2.1
+
+

Please note that version should be set at the beginning of the template before any other rules.

+
+

allowed_origin NEW

+
~allowed_origin: "https://example.com"
+~allowed_origin: ["https://example.com", "https://subdomain.example.com"]
+

Sets the origin (or the list of origins) from which content can be loaded using the @load and @inline functions.
The value should be String or Array of String.

+

Examples

+
~allowed_origin: "https://api.example.com"
+# Now you can load content from https://api.example.com regardless of the origin of current page
+@load: "https://api.example.com/get/article"
+

Supported functions

+

The general format for a function is the following:

+
@function: xpath_query
+

Each function accepts the list of nodes returned by the XPath statement as the main parameter. You may omit xpath_query, in which case $$, the result of the previous XPath query, will be passed into the function. The function then processes each element in the list and returns a list of transformed nodes which are stored in the $@ variable.

+

Below is a list of functions that are supported in Instant View rules.

+

debug

+
@debug: xpath_query
+

Logs the elements passed into the function, these elements will be displayed in the status line at the bottom of the screen in the Instant View Editor. Returns the elements passed. Consider combining with $$ and $@.

+

Example

+
@debug: //article//a     # displays all links from the page in the log
+@debug                   # displays all links again
+

+ +

Look for debug output at the bottom of your Editor:

+
+ +
+ + +

remove

+
@remove: xpath_query
+

Removes target nodes from the page, returns an empty list.

+

Examples

+
@remove: //div[has-class("related")] # remove article div.related
+@debug                               # empty list
+

append

+
@append("Some text"): xpath_query
+@append(@attr):       xpath_query
+@append(<tag>):       xpath_query
+@append(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, to the end of each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em></div>
+@append(<p>): //div
+# <div class="a"><em>1</em><p></p></div>
+

prepend

+
@prepend("Some text"): xpath_query
+@prepend(@attr):       xpath_query
+@prepend(<tag>):       xpath_query
+@prepend(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, to the beginning of each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em></div>
+@prepend(<p>, data-class, @class): //div
+# <div class="a"><p data-class="a"></p><em>1</em></div>
+

after

+
@after("Some text"): xpath_query
+@after(@attr):       xpath_query
+@after(<tag>):       xpath_query
+@after(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, after each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em><em>2</em></div>
+@after("!"): //div/em
+# <div class="a"><em>1</em>!<em>2</em>!</div>
+

before

+
@before("Some text"): xpath_query
+@before(@attr):       xpath_query
+@before(<tag>):       xpath_query
+@before(<tag>, attr, value[, attr, value[, ...]]): xpath_query
+

Inserts content, specified by the parameter, before each target node.

+
    +
  • If the first parameter is in angle brackets, a new <tag> node will be created. The following two parameters then specify the name and value of an attribute for that node. If value has the format @attr, the value of the attribute attr in the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.
  • +
  • If the first parameter has the format @attr, a new text element with value of the attribute attr of the targeted node will be created.
  • +
  • Otherwise, a text element with the text specified in the first parameter will be created.
  • +
+

Returns a list of the newly created nodes.

+

Examples

+
# <div class="a"><em>1</em></div>
+@before("@"): //div/em
+# <div class="a">@<em>1</em></div>
+

append_to

+
@append_to(xpath_query): xpath_query
+@append_to($var):        xpath_query
+

Inserts each target node to the end of the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:             //div
+# <div class="a"><em></em></div><p>Text</p>
+@append_to($div): //p
+# <div class="a"><em></em><p>Text</p></div>
+

prepend_to

+
@prepend_to(xpath_query): xpath_query
+@prepend_to($var):        xpath_query
+

Inserts each target node to the beginning of the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:              //div
+# <div class="a"><em></em></div><p>Text</p>
+@prepend_to($div): //p
+# <div class="a"><p>Text</p><em></em></div>
+

after_el

+
@after_el(xpath_query): xpath_query
+@after_el($var):        xpath_query
+

Inserts each target node after the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:                        //div
+# <div class="a"><p>Text</p><em></em></div>
+@after_el("./../self::div"): //p
+# <div class="a"><em></em></div><p>Text</p>
+

before_el

+
@before_el(xpath_query): xpath_query
+@before_el($var):        xpath_query
+

Inserts each target node before the base node.

+

The first parameter specifies the base node. You can pass an XPath expression that begins with ., in this case the query will be executed relative to the relevant node. The first relevant node will be used as the base node. You can also pass a variable name. If such a variable exists, the first relevant node will be used as the base node. If the variable doesn't exist or is empty, the property with a matching name will be used as the base node.

+

Returns a list of target nodes.

+

Examples

+
$div:                        //div
+# <div class="a"><p>Text</p><em></em></div>
+@before_el("./../self::div"): //p
+# <p>Text</p><div class="a"><em></em></div>
+

replace_tag

+
@replace_tag(<tag>):     xpath_query
+<tag>:                   xpath_query
+

Changes the name of the tag. The new name for the tag should be passed as the first parameter. Returns target nodes.

+

Examples

+
# <div class="list unordered"><div class="item"></div><div class="item"></div></div>
+@replace_tag(<li>): //div[has-class("item")]
+<ul>:               //div[has-class("list")]
+# <ul class="list unordered"><li class="item"></li><li class="item"></li></ul>
+

wrap

+
@wrap(<tag>): xpath_query
+

Wrap each target node in the <tag> tag. Returns a list of the new <tag> elements.

+

Examples

+
# <em>1</em><em>2</em>
+@wrap(<b>): //em
+# <b><em>1</em></b><b><em>2</em></b>
+@wrap(<u>)
+# <b><u><em>1</em></u></b><b><u><em>2</em></u></b>
+@wrap(<p>): $@
+# <b><p><u><em>1</em></u></p></b><b><p><u><em>2</em></u></p></b>
+

wrap_inner

+
@wrap_inner(<tag>): xpath_query
+

Wrap an HTML structure around the content of each target node in the <tag> tag. Returns a list of new <tag> elements.

+

Examples

+
# <p>H<sub>2</sub>0</p>
+@wrap_inner(<b>): //p
+# <p><b>H<sub>2</sub>0</b></p>
+

clone

+
@clone: xpath_query
+

Creates a copy of each target node. Returns a list of the newly created nodes.

+

Examples

+
# <p class="text">Paragraph</p>
+@clone: //p
+# <p class="text">Paragraph</p><p class="text">Paragraph</p>
+

detach

+
@detach: xpath_query
+

Separates the target node from the rest in the parent tag. Creates a copy of the parent tag and wraps the target node into this new instance. Returns a list of parent tags that contain target nodes.

+

Examples

+
# <a href="#1">
+#   <b>1</b>
+#   <p>Link #1</p>
+# </a>
+# <a href="#2">
+#   <b>2</b>
+#   <p>Link #2</p>
+# </a>
+
+@detach: //a/b
+
+# <a href="#1">
+#   <b>1</b>
+# </a>
+# <a href="#1">
+#   <p>Link #1</p>
+# </a>
+# <a href="#2">
+#   <b>2</b>
+# </a>
+# <a href="#2">
+#   <p>Link #2</p>
+# </a>
+
+@after(<br>): $@
+
+# <a href="#1">
+#   <b>1</b>
+# </a><br>
+# <a href="#1">
+#   <p>Link #1</p>
+# </a>
+# <a href="#2">
+#   <b>2</b>
+# </a><br>
+# <a href="#2">
+#   <p>Link #2</p>
+# </a>
+

split_parent

+
@split_parent: xpath_query
+

Splits the parent tag by the target node. Places preceding siblings wrapped into parent element before the target node. Places following siblings wrapped into parent element placed after target node.

+

Returns a list of target nodes.

+

Examples

+
# <p class="text">
+#   <b>First</b> line
+#   <figure><img src="photo.jpg"></figure>
+#   <i>Second</i> line
+# </p>
+@split_parent: //p/figure
+# <p class="text">
+#   <b>First</b> line
+# </p>
+# <figure><img src="photo.jpg"></figure>
+# <p class="text">
+#   <i>Second</i> line
+# </p>
+

pre

+
@pre: xpath_query
+

Specifies that the text inside the target node is already formatted. Returns a list of matching nodes.

+

Examples

+
# <p>     Some          text  , </p>
+# <p>  Some  another      text  </p>
+@pre: (//p)[1]
+# Result in the Instant View page:
+#      Some          text  , 
+# Some another text
+

set_attr

+
@set_attr(attr, value):       xpath_query
+@set_attr(attr, @attr):       xpath_query
+@set_attr(attr, "Some text"): xpath_query
+@set_attr(attr, "Some text", @from-attr, ...): xpath_query
+

Sets an attribute in each matching node. The name of the attribute is passed in the first parameter. The value of the attribute is the rest of the parameters concatenated.

+

If value has the format @attr, the value of the attribute attr of the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.

+

Returns a list of attribute nodes.

+

Examples

+
# <p class="a"></p>
+@set_attr(data-class, @class)
+# <p class="a" data-class="a"></p>
+@set_attr(id, @class, "_", ./@data-class)
+# <p class="a" data-class="a" id="a_a"></p>
+

set_attrs

+
@set_attrs(attr, value): xpath_query
+@set_attrs(attr, value[, attr, value[, ...]]): xpath_query
+

Sets multiple attributes for each of the target nodes. Each two parameters specify the name and value for the new attributes.

+

If value has the format @attr, the value of the attribute attr of the target node will be used as the value. value can be an XPath expression that begins with ., in this case the query will be executed relative to the relevant node, and the text value of the returned elements will be used as the attribute's value. Otherwise, value will be used as the attribute's value.

+

Returns a list of the matching nodes.

+

Examples

+
# <p class="a"></p>
+@set_attrs(data-class, @class, id, "a_a"): //p
+# <p class="a" data-class="a" id="a_a"></p>
+

match

+
@match(regexp):                         xpath_query
+@match(regexp, match_index):            xpath_query
+@match(regexp, match_index, modifiers): xpath_query
+

Performs a search based on a regular expression. Replaces the content of the target node with the search result. The second parameter specifies the number of the captured parenthesized subpattern. If this is not specified, the text that matched the full pattern will be used. You can specify modifiers for the regular expression using the optional parameter (ims modifiers are supported).

+

Returns a list of target nodes. As of IV 2.1, returns a list of target nodes the content of which matched the regular expression.

+

Examples

+
# <p class="plainText">Hello, world!</p>
+@match("[a-z]+!"): //p
+# <p class="plainText">world!</p>
+@match("([a-z]+)!", 1): //p/text()
+# <p class="plainText">world</p>
+@match("..t", 0, "i"): //p/@class
+# <p class="inT">Bye, world!</p>
+
+# <ul><li>a1</li><li>a</li><li>21b</li><li>.</li></ul>
+@match("[0-9]+"): //ul/li
+# <ul><li>1</li><li></li><li>21</li><li></li></ul>
+@debug: $@
+# Debug 2 nodes:
+#   [0]: <li>1</li>
+#   [1]: <li>21</li>
+

replace

+
@replace(regexp, replacement):            xpath_query
+@replace(regexp, replacement, modifiers): xpath_query
+

Performs a search and replace operation using the regular expression. You can specify modifiers for the regular expression using the optional parameter (ims modifiers are supported).

+

Returns a list of target nodes. As of IV 2.1, returns a list of target nodes the content of which was replaced by the regular expression.

+

Examples

+
# <p class="text">Hello, world!</p>
+@replace("Hello", "Goodbye"): //p/text()
+# <p class="text">Goodbye, world!</p>
+@replace(".t$", "mp"): //p/@class
+# <p class="temp">Goodbye, world!</p>
+@replace("goodb", "B", "i"): //p/text()
+# <p class="temp">Bye, world!</p>
+
+# <ul><li>a1</li><li>a</li><li>21b</li><li>.</li></ul>
+@replace("[0-9]+", "($0)"): //ul/li
+# <ul><li>a(1)</li><li>a</li><li>(21)b</li><li>.</li></ul>
+@debug: $@
+# Debug 2 nodes:
+#   [0]: <li>a(1)</li>
+#   [1]: <li>(21)b</li>
+

urlencode

+
@urlencode: xpath_query
+

Encodes the content of the target node as per RFC 3986. Returns target nodes.

+

Examples

+
# <a href="https://telegram.org">link</a>
+$a: //a
+@urlencode: $a/@href
+# <a href="https%3A%2F%2Ftelegram.org">link</a>
+@set_attr(href, "/?url=", @href): $a
+# <a href="/?url=https%3A%2F%2Ftelegram.org">link</a>
+

urldecode

+
@urldecode: xpath_query
+

Decodes the content of the target node as per RFC 3986. Returns target nodes.

+

Examples

+
# <a href="/?url=https%3A%2F%2Ftelegram.org">link</a>
+$a: //a
+@match("^/\?url=(.+)$", 1): $a/@href
+# <a href="https%3A%2F%2Ftelegram.org">link</a>
+@urldecode
+# <a href="https://telegram.org">link</a>
+

htmlencode

+
@htmlencode: xpath_query
+

Convert special characters in the target node to HTML entities. Returns the target nodes.

+

Examples

+
# <p>&lt;b&gt;Some text&lt;\b&gt;</p>
+@htmlencode: //p
+# <p>&amp;lt;b&amp;gt;Some text&amp;lt;\b&amp;gt;</p>
+

htmldecode

+
@htmldecode: xpath_query
+

Convert special HTML entities in the target node back to characters. Returns the target nodes.

+

Examples

+
# <p>&amp;lt;b&amp;gt;Some text&amp;lt;\b&amp;gt;</p>
+@htmldecode: //p
+# <p>&lt;b&gt;Some text&lt;\b&gt;</p>
+

style_to_attrs

+
@style_to_attrs(css_prop, attr): xpath_query
+@style_to_attrs(css_prop, attr[, css_prop, attr[, ...]]): xpath_query
+

Gets a value of a CSS property from the style attribute and sets it into an attribute for each of the target nodes. Each two parameters specify the name for the new attribute and the name of CSS property. Returns a list of matching nodes.

+

Examples

+
# <img style="width: 20px; height: 20px">
+@style_to_attrs(width, data-width, height, data-height): //img
+# <img style="width: 20px; height: 20px" data-width="20" data-height="20">
+

background_to_image

+
@background_to_image: xpath_query
+

Transforms the target node with a background picture into an <img> tag with an src attribute. The target node must contain a style attribute with the background. Returns a list of transformed nodes.

+

Examples

+
# <div class="bg_image" style="background-image:url(image.jpg)"></div>
+@background_to_image: //div[has-class("bg_image")]
+# <img src="image.jpg">
+

json_to_xml

+
@json_to_xml: xpath_query
+

Transforms the content of the target node to the XML format. The contents must be in valid JSON format. The resulting XML tree will be inserted into the document. Returns the root element of the XML tree.

+

Examples

+
# <div data-var='{"a":1,"b":[1,2],"c":{"p":"Hello!"}}'></div>
+@json_to_xml: //div/@data-var
+@debug: $@
+# <xml><a>1</a><b><item>1</item><item>2</item></b><c><p>Hello!</p></c></xml>
+

html_to_dom

+
@html_to_dom: xpath_query
+

Parse the content of the target node in HTML format and insert it into the document. Returns the root element of the inserted HTML tree.

+

Examples

+
# <div data-content="&lt;b&gt;Some text&lt;\b&gt;"></div>
+@html_to_dom: //div/@data-content
+@debug: $@
+# <dom><b>Some text</b></dom>
+

combine

+
@combine:                        xpath_query
+@combine(" - "):                 xpath_query
+@combine(<tag>):                 xpath_query
+@combine(<tag>[, " - "[, ...]]): xpath_query
+

Combines each target node with its preceding node if such a node exists. You can use parameters to specify nodes to be inserted above the target node. If the parameter is in angular brackets, a new <tag> node will be created. Otherwise a text element with the text specified by the parameter will be used.

+

Returns a list of nodes, preceding the target nodes.

+

Examples

+
# <pre>1 2 3</pre>
+# <pre> 4 5 </pre>
+# <pre>6 7 8</pre>
+@combine:             //pre/following-sibling::*[1]/self::pre
+# <pre>1 2 3 4 5 6 7 8</pre>
+
+# <p>first</p>
+# <p>second</p>
+@combine(<br>, <br>): //p/following-sibling::*[1]/self::p
+# <p>first<br><br>second</p>
+
+# <h1>Title</h1>
+# <strong>Subtitle</strong>
+@combine(<br>, "\n"): //h1/following-sibling::*[1]/self::strong
+# <h1>Title<br>
+# Subtitle</h1>
+

datetime

+
@datetime(-2): xpath_query
+@datetime(-2, "en-US", "yyyy-MM-dd"): xpath_query
+

Transforms the date and time from the text of the target node into a unixtime timestamp. The parameter specifies the timezone of the original date and time.

+

You can also pass a locale and a pattern to parse the date and time in more complicated cases. If a non-gregorian calendar is used, this needs to be specified in the locale. For example, "fa-IR@calendar=persian". Available patterns are documented here.

+

On success, returns a text element with the unixtime timestamp. Otherwise, returns the target element.

+

Examples

+
# <div id="date">1 January 2017, 15:04</div>
+@datetime(-2):  //div[@id="date"]
+published_date: $@   # the property published_date will hold a unixtime timestamp
+
+# <time>دوشنبه, ۲۳ اسفند ۱۳۹۵</time>
+@datetime(0, "fa-IR@calendar=persian", "EEEE, dd MMMM yyyy"): //time
+published_date: $@   # the property published_date will hold a unixtime timestamp
+

simplify

+
+

Note: This is a service function. There is no reason for you to use it in your templates. It was included in this reference to give you a better understanding of how the system works (see the ..after block).

+
+
@simplify: xpath_query
+

Processes the target nodes according to the Instant View format. Returns the target nodes.

+

Examples

+
# <p><span><b>S</b>ome</span> <em>important</em> text!</p>
+@simplify: //p
+# <p><b>S</b>ome <em>important</em> text!</p>
+

inline

+
@inline:         xpath_query
+@inline(silent): xpath_query
+

If the target element is an <iframe> with the attribute src, the content of the iframe will be loaded. The target element will be replaced with the content of the iframe.

+

If the target node is an HTML-comment, a <comment> element with the content of the comment will be created. The comment will be replaced by the newly created node.

+

You can use silent parameter to ignore errors while processing this function. You will still see an error in the debug console, but the rules that come after will continue to execute.

+

Returns a list of replaced nodes.

+
+

Note: The @inline function adheres to the same-origin policy. This means that the target and the inlined pages should have the same origin. You can specify additional allowed origins using the option ~allowed_origin

+
+

Examples

+
# <p><iframe src="/subpage.html"></iframe></p>
+# /subpage.html:
+#   <html><body><p>Hello!</p></body></html>
+@inline: //p/iframe
+# <p><html><body><p>Hello!</p></body></html></p>
+@debug
+# <html><body><p>Hello!</p></body></html>
+
+# <p><!--<b>Hello!</b>, world!--></p>
+@inline: //p/comment()
+# <p><comment><b>Hello!</b>, world!</comment></p>
+@debug
+# <comment><b>Hello!</b>, world!</comment>
+

load NEW

+
@load:         "https://example.com"
+@load(silent): xpath_query
+

Loads the content of the URL. The URL can be specified as a string or be the content of the target node.

+

You can use silent parameter to ignore errors while processing this function. You will still see an error in the debug console, but the rules that come after will continue to execute.

+

Returns the newly created node with loaded content.

+
+

Note: The @load function adheres to the same-origin policy. This means that the target and the loaded pages should have the same origin. You can specify additional allowed origins using the option ~allowed_origin

+
+

Examples

+
@append(<iframe> src "/subpage.html"): /html/body
+$iframe: $@
+@remove
+@inline: $iframe
+# the same, but much shorter
+@load: "/subpage.html"
+
+@load(silent): //meta[@property="api:url"]/@content
+# trying to load content from api:url
+@if ( $@ ) {
+  # Do something with content
+}
+

unsupported

+
@unsupported: xpath_query
+

Specifies that the target node contains essential content that can't be represented in the Instant View format. Returns the target nodes.

+

Examples

+
# <p>See the graph below:</p>
+# <canvas class="article_graph" width="600" height="400"></canvas>
+@unsupported: //canvas[has-class("article_graph")]
+
+

Tip: It is important to identify that a page contains essential unsupported content — no IV page will be generated to ensure that the user never gets incomplete info from an article. The system will take care of the most popular cases in the ..after block, but your template must cover everything that the system doesn't catch.

+
+

Supported block functions

+

The general format for a block function is the following:

+
@function(xpath_query) {
+  # block of rules
+}
+

Block functions usually accept the list of nodes returned by the XPath statement as a parameter. Depending on the function and its parameters, rules inside the block can be run several times or never. Block functions can contain any type of rules except conditions.

+

Below is a list of block functions that are supported in Instant View rules.

+

if

+
@if(xpath_query) {
+  # block of rules
+}
+

Executes the block of rules if target nodes exist on the current page. If target nodes do not exist, the block of rules will be skipped. The $$ and $@ variables contain target nodes found by the XPath query.

+

Example

+
@if( //div[has-class("blockquote")] ) { # if div.blockquote exists
+  <blockquote>: $@                      #   change tag name to blockquote
+  <cite>: $@//div[has-class("author")]  #   and mark div.author as a caption
+}
+

if_not

+
@if_not(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules if target nodes do not exist on the current page. If such nodes exist, the block of rules will be skipped. The $$ and $@ variables contain target nodes found by the XPath query.

+

Example

+
@if_not( $body//footer ) {     # if footer does not exist
+  @append(<footer>): $body     #   append it into body
+}
+

map

+
@map(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules once per each target node found by the XPath query. At the beginning of each iteration, the following variables will be set:

+
    +
  • $$ will contain the target nodes found by XPath query;
  • +
  • $@ will contain the current target node;
  • +
  • $index will contain the index of the current target node (starts with 1);
  • +
  • $first will contain <true> if the current target node is the first in the list and an empty list otherwise;
  • +
  • $middle will contain <true> if the current target node is between the first and the last in the list, empty list otherwise;
  • +
  • $last would contain <true> if the current target node is the last one in the list, empty list otherwise.
  • +
+

Example

+
@map( //div[@id="list"]/p ) {   # for each paragraph in list
+  $p: $@                        #   store the current paragraph in $p variable
+  @prepend_to($p): ". "         #   and
+  @prepend_to($p): $index       #   number them starting with 1
+}
+
+

Please note that the @map function should be used only if it is impossible to use regular functions with xpath queries (for example you need to use $index). Otherwise, regular functions are faster because they process several nodes at once.

+
+

Example

+
# Bad way:
+@map( //div[has-class("image")] ) {
+  $image: $@
+  <cite>:       $image//p/span
+  <figcaption>: $image//p
+  <figure>:     $image
+}
+# The same result, but faster:
+$image:       //div[has-class("image")]
+<cite>:       $image//p/span
+<figcaption>: $image//p
+<figure>:     $image
+

repeat

+
@repeat(n) {
+  # block of rules
+}
+

Executes a block of rules n times. At the beginning of each iteration, the following variables will be set:

+
    +
  • $$ and $@ will contain the previous value of $$;
  • +
  • $index will contain the index of the current iteration (starts with 1);
  • +
  • $first will contain <true> if this is the first iteration, an empty list otherwise;
  • +
  • $middle will contain <true> if the current iteration is between the first and last, empty list otherwise;
  • +
  • $last will contain <true> if this is the last iteration, empty list otherwise.
  • +
+

Example

+
# appends "1, 2, 3, 4, 5" to $body
+@repeat( 5 ) {
+  @append_to($body): $index
+  @if_not( $last ) {
+    @append_to($body): ", "
+  }
+}
+

while

+
@while(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules while target nodes exist on the current page. At the beginning of each iteration the following variables will be set:

+
    +
  • $$ and $@ will contain target nodes found by XPath query;
  • +
  • $index will contain the index of the current iteration (starts with 1);
  • +
  • $first will contain <true> if it is the first iteration, an empty list otherwise.
  • +
+

Example

+
@while( //iframe ) {
+  @inline: $@          # inline all nested iframes
+}
+

while_not

+
@while_not(xpath_query) {
+  # block of rules
+}
+

Executes a block of rules while target nodes do not exist on the current page. At the beginning of each iteration the following variables will be set:

+
    +
  • $$ and $@ will contain target nodes found by XPath query;
  • +
  • $index will contain the index of the current iteration (starts with 1);
  • +
  • $first will contain <true> if this is the first iteration, an empty list otherwise.
  • +
+

Example

+
@while_not( //video ) {   # if no video exists on the current page
+  @inline: //iframe       #   try to inline iframes, maybe video is inside the frame
+}
+

Embedded elements

+

Instant View supports widgets from popular services. We display them as embedded elements or specially formatted quotes. The Instant View bot analyzes all iframes in the document body and generates a widget if the service is supported.

+
+

Some popular widgets do not use iframes. Note that the ..after block of rules contains rules to transform such widgets to an Instant View compatible format.

+
+

We currently support the following services:

+
    +
  • Youtube
  • +
  • Vimeo
  • +
  • Tweets & Twitter Videos
  • +
  • Facebook Posts & Videos
  • +
  • Instagram
  • +
  • Giphy
  • +
  • SoundCloud
  • +
  • GithubGist
  • +
  • Aparat
  • +
  • VK.com Videos
  • +
+

Processing pages

+

All pages are processed according to the following rules:

+
# Url: http://example.com/some_page.html
++ example.com
+?true
++ ..after
+

If a page is on a third-level domain and above, the following rules are applied:

+
# Url: http://some.subdomain.example.com/some_page.html
++ some.subdomain.example.com
+?not_exists: $body
++ subdomain.example.com
+?not_exists: $body
++ example.com
+?true
++ ..after
+

In other words, at first the bot attempts to use a block of rules that features the full domain name. If such a block does not exist, the bot checks for the next level up to the second-level domain.

+

..after is a special block of rules that is applied to all pages irrespective of the domain name.

+

Working with subdomains

+

If the page is on a third-level domain or higher, you need to manually select the domain level to which your template will apply. Use this menu in the top left corner of the page:

+
+
+
+ +

Choose a level that hosts pages with the same structure, so that your rules are relevant to all the matching pages on this domain.

+
+

For example, use wikipedia.org to create an IV page for https://en.wikipedia.org/wiki/Domain_name because the page structure doesn't depend on language in Wikipedia.

+
+
+ +
+
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/rules.html b/data/instantview.telegram.org/rules.html new file mode 100644 index 0000000000..55c012e3e0 --- /dev/null +++ b/data/instantview.telegram.org/rules.html @@ -0,0 +1,251 @@ + + + + + Contest Rules - Instant View + + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+
+

Template Competition Rules

+ +
+ +
+ +
+ +

We are holding a new $300,000+ 2-month competition (4 Feb 2019 - 4 April 2019) to create Instant View Templates for news websites and blogs, $100 per template. Everyone is welcome to participate!

+

Goal

+

The goal of the competition is to use Telegram's Instant View Editor to create perfect Instant View templates for as many websites as possible from our suggested domains list.

+

Starting on February, 4, we will be adding 500 new domains to our list of targets approximately every 10 days. The contest will end when all of the 3000+ target domains get a winning template. We expect this to take 2 months.

+
+

Subscribe to the IV contest channel »

+
+

Prizes

+

The first person to submit a fully valid and working template for one of the websites on our list gets $100 for each website they conquered ahead of the others.*

+

The winner will be the person who creates the greatest number of perfect templates (without valid issues) that cover the largest number of domains from our targets list. The winner will be awarded $10,000 in addition to the payout from their individual templates. For the second place, we will award a $5,000 prize on top of the payouts for the individual templates.

+

How to submit?

+

You can submit your template to the contest as soon as it covers a sufficient number of articles. Make sure you've enabled Track Changes for at least 10-15 different pages on the target website and all IV pages are generated correctly.

+

When ready, simply tap Submit to Contest next to a template in My Templates section:

+
+ +

Submit to Contest from My Templates

+ +

We strongly recommend that you make sure that your template satisfies all the criteria for a perfect template before you submit. If you revoke your template to make any adjustments and resubmit it later, the template will lose its place at the top of the list. You could still win in case all the templates that were submitted before your fix also have valid issues, but it's better not to take chances.

+

For the same reason, if you see that your template has some issues, it is best to fix them and resubmit as soon as possible.

+

Finding issues

+

Anyone can check the results (but not the code) of any templates that were submitted for the contest. This means you can take a couple of links and see if a template processes them correctly into perfect Instant View pages (see detailed criteria here).

+

If you see any issues, report them using the Report Issue button. Click to select and highlight incorrectly parsed blocks in the source page or in the Instant View result and provide a detailed explanation of what is wrong (check the general criteria and detailed rules). The author of the template will be able to see all issues, fix and resubmit their work. Note that it is the date of the latest resubmission that counts for the purposes of determining the winner.

+

Determining winners

+

The contest for each individual domain from the list of targets begins when the first corresponding IV template is published. The earliest submitted template is considered the winning candidate and participants get three days (72 hours) to find valid issues with that template.

+

Telegram arbiters will check all issues, accept valid ones and decline non-issues and duplicates. If the winning candidate is rejected, the second-earliest submitted template takes its place.

+

If the reporting period ends with no valid issues accepted on the leading template, participants may no longer create new issues for that template. They still can – and should – create issues on any other templates which were submitted less than 72 hours ago.

+

Arbiters will perform a final check on all remaining issues for the domain – they may also create and accept new issues of their own. If arbiters find no valid issues with the template, it is declared the winner.

+

Fallen leaders

+

If the leading template is rejected as a result of the final check, the contest is reopened and participants may submit issues again.

+
+

Note that the 72-hour reporting period is always calculated from the moment when the template was submitted. This means that if there are two templates for a domain submitted at the same time, and the leading one falls, the second one has the potential to win instantly, if the arbiters find no issues with it. It is important to submit issues for all templates, not just the currently winning one.

+
+

If as a result of this process all templates are rejected because none of them was able to achieve perfection, the contest for the domain starts again as soon as a new template is submitted. In some circumstances, Telegram may decide that the domain is unsuitable for IV and remove it from the contest.

+

Share the work — share the prize

+

When a template wins the competition for a particular domain, the users who helped the author to identify and fix issues will get a share of the prize at the end of the contest. We will award $2 per each of the 25 most recently submitted valid issues. This money (up to $50 per winning template) will be deducted from the template author's reward.

+

This way, if a template wins after other users found many issues with it, the author may get only $50 and the rest will be distributed among their helpers. Authors who submitted perfect templates right away will get the entire $100 for each of their templates when they win.

+

Receiving rewards

+

Rewards will be paid out after the contest ends – when all target domains are either declared unsuitable for IV or get a perfect template. We aim at completing the contest within approximately 2 months.

+

For operational purposes, payouts to both template makers and their helpers who identified issues start at $200. Note that rewards below $200 earned in the First Instant View Contest count towards the minimum limit in this Second Contest.

+

Criteria for a good template

+
+

For more info on templates, see our Introduction and Sample Templates.

+
+

To be considered in the competition, the template must fulfil at least these five basic requirements:

+

1. IVs must only be generated for pages that need them

+

Instant View pages work best with relatively static articles. Dynamic pages, such as the main page of a news site that contains ever-changing lists of links to new articles, would hardly benefit from the IV treatment.

+

You must make sure that your template only generates IV pages for articles and does not affect service areas of the website, as well as any other sections unsuitable for IV. You must also make sure that IV pages are not generated for articles that have content that is not supported in IV. If such a page were generated, it would result in unacceptable loss of information (e.g., IV pages don‘t support dynamic maps — if you generate an IV page for a wiki article that consists of a dynamic map, the user won’t see any useful info from the article).

+

Your template must have successfully passed automatic checks on at least 10-15 URLs from the target domain. Read more about automatic checks and tracking changes.

+

2. All essential content must be represented

+

Your IV page should show the entire text of the article, along with all the headings and subheadings, quotes, cover and other photos, videos, and other kinds of embedded content from the source page.

+

3. Unnecessary elements must be eliminated

+

Your IV page must display the pure content of the source. Remove any bits of interface, ads, and any irrelevant embedded content.

+

4. Template must process any of the pages it covers

+

Check whether pages with irregular elements are processed correctly. Pay special attention that various types of media, embedded elements, quotes, and separators are all displayed nicely. Check at least 10-15 different links before submitting your template to the competition.

+

5. No extraneous info may be added

+

Any attempts to add content that is not present on the original page will lead to the rejection of the template.

+

It is allowed to assign the username of the official channel of the website that published the article to the channel property. To be considered official, the channel must be named as such by the relevant company or person (on the website itself or on social media).

+
+

Perfect Templates

+

What's listed above are the general guidelines. If you're looking for more precise information on what a perfect template is (and is not), see the Perfect Template Checklist.

+
+ +
+
+
+
+
+ + + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/samples.html b/data/instantview.telegram.org/samples.html new file mode 100644 index 0000000000..caa2bfc0ba --- /dev/null +++ b/data/instantview.telegram.org/samples.html @@ -0,0 +1,395 @@ + + + + + Sample Templates - Instant View + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+

Sample Templates

+

In this section, you can check out the exact same templates that we're currently using to generate Instant View pages for posts on Medium, Telegra.ph, and the Telegram Blog. We've added many comments to these templates, so they literally speak for themselves.

+ +
+

+ medium.com7 +

+
+
+

7 pages

+

Not modified

+
+
+ +
+

+ telegra.ph2 +

+
+
+

2 pages

+

Not modified

+
+
+ +
+

+ telegram.org7 +

+
+
+

7 pages

+

Not modified

+
+
+ +
+
+
+
+
+ + + + + + + + + diff --git a/data/instantview.telegram.org/templates.html b/data/instantview.telegram.org/templates.html new file mode 100644 index 0000000000..ab8a2985e3 --- /dev/null +++ b/data/instantview.telegram.org/templates.html @@ -0,0 +1,1253 @@ + + + + + Templates - Instant View + + + + + + + + + + +
+ +
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+ +
+
+
+

Templates

+

Enter any article URL to check the currently active Instant View template for issues – or create a new template if Instant View is not yet supported for the website.

+
+
+
+
Domain +
+
+ TemplateLast Update +
+
+
+
+ +
+
+
+
+
+ 01net.com +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 032.ua +
+
+ Template #28 + Jan 1, 1970 + +
+
+
+ 0352.ua +
+
+ Template #102 + Jan 1, 1970 + +
+
+ +
+ Template #28 + Jan 1, 1970 + +
+
+ +
+ Template #4 + Jan 1, 1970 + +
+
+
+ 061.ua +
+
+ Template #92 + Jan 1, 1970 + +
+
+ +
+ Template #3 + Jan 1, 1970 + +
+
+
+ 06blog.it +
+
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+
+ 103.by +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #17 + Jan 1, 1970 + +
+
+
+ 10tv.com +
+
+ Template #6 + Jan 1, 1970 + +
+
+
+ 10tv.in +
+
+ Template #3 + Jan 1, 1970 + +
+
+
+ 110km.ru +
+
+ Template #36 + Jan 1, 1970 + +
+
+
+ 112.ua +
+
+ Template #9 + Jan 1, 1970 + +
+
+
+ 13.cl +
+
+ Template #9 + Jan 1, 1970 + +
+
+
+ 13abc.com +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 15min.lt +
+
+ Template #27 + Jan 1, 1970 + +
+
+
+ 1863x.com +
+
+ Template #8 + Jan 1, 1970 + +
+
+
+ 1car.ir +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #4 + Jan 1, 1970 + +
+
+ +
+ Template #37 + Jan 1, 1970 + +
+
+
+ 1kr.ua +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #12 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+
+ 1nsk.ru +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #13 + Jan 1, 1970 + +
+
+
+ 1plus1.ua +
+
+ Template #7 + Jan 1, 1970 + +
+
+
+ 1prime.ru +
+
+ Template #24 + Jan 1, 1970 + +
+
+
+ 1reg.by +
+
+ Template #3 + Jan 1, 1970 + +
+
+
+ 1tmn.ru +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+ 1tv.ru +
+
+ Template #32 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 2000.ua +
+
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 20min.ch +
+
+ Template #31 + Jan 1, 1970 + +
+
+ +
+ Template #8 + Jan 1, 1970 + +
+
+ +
+ Template #60 + Jan 1, 1970 + +
+
+
+ 218tv.net +
+
+ Template #27 + Jan 1, 1970 + +
+
+
+ 21.by +
+
+ Template #3 + Jan 1, 1970 + +
+
+ +
+ Template #12 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 24.ae +
+
+ Template #13 + Jan 1, 1970 + +
+
+
+ 24.com.eg +
+
+ Template #4 + Jan 1, 1970 + +
+
+
+ 24.hu +
+
+ Template #8 + Jan 1, 1970 + +
+
+
+ 24auto.de +
+
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #4 + Jan 1, 1970 + +
+
+ +
+ Template #11 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #51 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #5 + Jan 1, 1970 + +
+
+
+ 24hod.sk +
+
+ Template #14 + Jan 1, 1970 + +
+
+ +
+ Template #16 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 24smi.org +
+
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 24tv.ua +
+
+ Template #36 + Jan 1, 1970 + +
+
+
+ 24ur.com +
+
+ Template #2 + Jan 1, 1970 + +
+
+
+ 24vest.de +
+
+ Template #6 + Jan 1, 1970 + +
+
+
+ 24vita.de +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #12 + Jan 1, 1970 + +
+
+
+ 2m.ma +
+
+ Template #10 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 2sao.vn +
+
+ Template #42 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 34.ua +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+ 34mag.net +
+
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #5 + Jan 1, 1970 + +
+
+ +
+ Template #66 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 360tv.ru +
+
+ Template #7 + Jan 1, 1970 + +
+
+ +
+ Template #21 + Jan 1, 1970 + +
+
+
+ 368.media +
+
+ Template #14 + Jan 1, 1970 + +
+
+
+ 36kr.com +
+
+ Template #62 + Jan 1, 1970 + +
+
+
+ 36ng.ng +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+ 36on.ru +
+
+ Template #30 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+ +
+ Template #6 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+ +
+ Template #38 + Jan 1, 1970 + +
+
+ +
+ Template #2 + Jan 1, 1970 + +
+
+
+ 3dnews.ru +
+
+ Template #65 + Jan 1, 1970 + +
+
+ +
+ Template #1 + Jan 1, 1970 + +
+
+
+ 3dpapa.ru +
+
+ Template #20 + Jan 1, 1970 + +
+
+ +
+ Template #16 + Jan 1, 1970 + +
+
+
+ 3rbdr.net +
+
+ Template #1 + Jan 1, 1970 + +
+
+
+
+
+
+
+
+ + + + + + + + + + diff --git a/data/macos.telegram.org.html b/data/macos.telegram.org.html new file mode 100644 index 0000000000..00293b1396 --- /dev/null +++ b/data/macos.telegram.org.html @@ -0,0 +1,521 @@ + + + + + Telegram for macOS + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ + +
+ +
+ + + + + +
+
This software is available under GPL v2 license.

Source code is available on GitHub.

Beta version
+
+ +
+ +
+
+

Version history

+ +

8.5 2022-02-01

+
    +
  • VIDEO STICKERS, BETTER REACTIONS AND MORE
  • +
  • Video Stickers
  • +
  • Use a new type of detailed stickers with smooth animations.
  • +
  • Create new sets by sending .webm videos to @stickers.
  • +
  • Bring your custom animated stickers from other apps.
  • +
  • Better Reactions
  • +
  • See smaller, compact animations when reacting to messages.
  • +
  • Press and hold an emoji in the reaction menu to send a bigger animation.
  • +
  • See real-time animations in chat when a user reacts to your message.
  • +
  • React with additional emoji expressing love, appreciation, anger or surprise.
  • +
  • Read Status for Reactions
  • +
  • Tap the new button in chats to jump to your messages that have unseen reactions.
  • +
  • Watch the animations for unseen reactions play when you hit the button.
  • +
+ +

8.4.1 2021-12-30

+
    +
  • REACTIONS, SPOILERS, CONTEXT MENU
  • +
  • Reactions
  • +
  • Double tap a message to send a quick :thumbsup: reaction.
  • +
  • Press and hold a message for more reactions.
  • +
  • Change your quick reaction emoji in Settings > Stickers and Emoji.
  • +
  • Group and Channel admins can enable reactions in their chat via Chat Info > Edit > Reactions.
  • +
  • Spoilers
  • +
  • Use ||Text|| formatting to hide some or all of the contents of a message.
  • +
  • Tap the spoiler animation in chat to reveal its hidden text.
  • +
  • Spoiler formatting hides text in chat, as well as in the chat list and notifications.
  • +
  • Context Menu
  • +
  • All context menus in the app were redesigned with beautifully animated icons.
  • +
+ +

8.4 2021-12-30

+
    +
  • REACTIONS, SPOILERS, CONTEXT MENU
  • +
  • Reactions
  • +
  • Double tap a message to send a quick :thumbsup: reaction.
  • +
  • Press and hold a message for more reactions.
  • +
  • Change your quick reaction emoji in Settings > Stickers and Emoji.
  • +
  • Group and Channel admins can enable reactions in their chat via Chat Info > Edit > Reactions.
  • +
  • Spoilers
  • +
  • Select text when typing and choose 'Spoiler' formatting to hide some or all of the contents of a message.
  • +
  • Tap the spoiler animation in chat to reveal its hidden text.
  • +
  • Spoiler formatting hides text in chat, as well as in the chat list and notifications.
  • +
  • Context Menu
  • +
  • All context menus in the app were redesigned with beautifully animated icons.
  • +
+ +

8.4 2021-12-30

+
    +
  • PROTECTED CONTENT, DEVICE MANAGEMENT AND MORE
  • +
  • Protected Content in Groups and Channels
  • +
  • Content creators can restrict the ability to forward messages from their groups and channels.
  • +
  • When forwarding is restricted, users will also be unable to directly save media from the chat or take screenshots.
  • +
  • Toggle this option on or off via Chat Info > Group / Channel Type.
  • +
  • Manage Connected Devices
  • +
  • Choose how long a device may stay inactive before it's logged out automatically.
  • +
  • Select a device to control whether it is allowed to accept Calls or new Secret Chats.
  • +
  • Anonymous Posting in Public Groups
  • +
  • Comment as one of your channels in public groups and channel comments.
  • +
  • Tap the profile picture next to the message bar to choose which channel you will appear as when you send the message.
  • +
+ +

8.2 2021-11-06

+
    +
  • JOIN REQUESTS, GLOBAL CHAT THEMES AND MORE
  • +
  • Join Requests for Groups and Channels
  • +
  • Create special invite links that require admins to approve users before they become members.
  • +
  • Admins can view the applicants’ profiles and bios by tapping the Join Requests bar at the top of the chat.
  • +
  • Add internal labels to your chat's Invite Links to keep them organized.
  • +
  • Global Chat Themes
  • +
  • Apply one of 8 new preset themes to your entire app – each theme has a Day and Night mode, colorful animated backgrounds and gradient message bubbles.
  • +
  • Personalize these themes and find custom theme options in Appearance Settings.
  • +
  • More Interactive Emoji
  • +
  • Send one :joy:, :money_with_wings:, :face_vomiting:, :thumbs_down:, :ghost: or :jack_o_lantern: emoji to any private chat, then tap on the animated emoji to launch a fullscreen effect.
  • +
  • If your chat partner also has the chat open, you will both see the effects and feel the vibrations simultaneously.
  • +
  • This also works with :fireworks:, :party_popper:, :balloon:, :pile_of_poo:, :thumbs_up: and :heart:.
  • +
+ +

8.1.4 2021-10-12

+
    +
  • CHAT THEMES, INTERACTIVE EMOJI, READ RECEIPTS IN GROUPS AND LIVE STREAM RECORDING
  • +
  • Chat Themes
  • +
  • Choose one of 8 new preset themes for any individual private chat.
  • +
  • Click (⋯) in a chat then 'Change Colors' to pick a theme.
  • +
  • Both chat participants will see the same theme in that chat – on all their devices.
  • +
  • Each new theme features colorful gradient message bubbles, beautifully animated backgrounds and unique background patterns.
  • +
  • All chat themes have day and night versions and will follow your overall dark mode settings.
  • +
  • More chat themes coming soon.
  • +
  • Interactive Emoji
  • +
  • Some animated emoji now have fullscreen effects.
  • +
  • Send :fireworks:, :party_popper:, :balloon:, :pile_of_poo:, :thumbs_up: or :heart: to any private chat, then tap on the animated emoji to launch the effect.
  • +
  • If your chat partner also has the chat open, you will both see the effects and feel the vibrations simultaneously.
  • +
  • See the "Watching" status when your chat partner is enjoying emoji effects with you.
  • +
  • More interactive emoji coming soon.
  • +
  • Read Receipts in Small Groups
  • +
  • Select one of your outgoing messages in small groups to see who recently viewed it.
  • +
  • To protect privacy, read receipts are only stored for 7 days after the message was sent.
  • +
  • Record Live Streams and Video Chats
  • +
  • Record video and audio from live broadcasts in your group or channel.
  • +
  • Admins can start recording from the Settings.
  • +
  • Choose between recording in portrait or landscape orientation.
  • +
  • Finished recordings are sent to the admin's Saved Messages and can be easily shared.
  • +
+ +

8.0 2021-09-02

+
    +
  • Live Streams, Flexible Forwarding, Jump to Next Channel and More
  • +
  • Live Stream to an unlimited number of viewers in groups and channels.
  • +
  • Remove sender names before forwarding.
  • +
  • Trending Stickers are now shown above 'Recently Used'.
  • +
  • Set stickers or GIFs as your profile video — or as profile videos for your groups or channels.
  • +
  • Profile pictures in groups follow the messages as you scroll the chat.
  • +
  • There's more! View the full list of changes in-app or on our blog.
  • +
+ +

7.9 2021-08-02

+
    +
  • Video Calls with up to 1000 Viewers, Video Messages 2.0 and More
  • +
  • Group Video Calls 2.0
  • +
  • Group Video Calls now support up to 1000 video viewers, as well as unlimited audio-only listeners.
  • +
  • To start a Group Video Call, create a Voice Chat from the info page of any group where you are an admin — then turn your video on.
  • +
  • Video Messages 2.0
  • +
  • Enjoy higher resolution from video messages in your chats.
  • +
  • Timestamps
  • +
  • Add timestamps like '0:45' to video captions and replies to automatically create links that play the video from that specific moment.
  • +
  • Screen Sharing with Sound
  • +
  • Share your screen in 1-on-1 video calls, as well as group video calls.
  • +
+ +

7.8.1 2021-07-15

+
    +
  • Improved group video calls in voice chats.
  • +
+ +

7.8 2021-06-25

+
    +
  • Group Video Calls
  • +
  • Start video conferences from Voice Chats in any group.
  • +
  • Share your screen or video from your camera with up to 30 participants (limit to be increased soon).
  • +
  • Talk without video with an unlimited number of participants.
  • +
  • Create voice chats from the info page of any group where you are an admin.
  • +
  • Group video calls are supported natively on all devices, including iPads and laptops.
  • +
+ +

7.7 2021-04-28

+
    +
  • Scheduled Voice Chats
  • +
  • Schedule voice chats to let participants know about them in advance.
  • +
  • View a countdown to the voice chat and get notified when it starts.
  • +
  • Who is Who in Voice Chats
  • +
  • Browse full-sized profile pictures and expanded bios directly in the list of participants.
  • +
  • Update your profile pic and bio from the voice chat window.
  • +
  • Payments 2.0
  • +
  • Offer real goods and services for sale in any group, channel or bot – Telegram doesn't charge a commission.
  • +
  • Pay for goods directly using one of 8 integrated payment providers – Telegram doesn't see your payment info.
  • +
+ +

7.6 2021-03-19

+
    +
  • VOICE CHATS 2.0: CHANNELS, MILLIONS OF LISTENERS, RECORDED CHATS, ADMIN TOOLS
  • +
  • Millions of Concurrent Listeners
  • +
  • Start limitless Voice Chats in Groups and Channels.
  • +
  • Host discussions that can be listened to by millions of people simultaneously.
  • +
  • Voice Chat Recordings
  • +
  • Record voice chats to share or publish in Channels later.
  • +
  • See that a chat is being recorded from the red dot next to its title.
  • +
  • Improved List of Participants
  • +
  • See user bio texts right from the list of participants.
  • +
  • Raise your hand to show admins you want to speak.
  • +
  • Management Tools
  • +
  • Create separate Voice Chat Invite Links for listeners or speakers.
  • +
  • Change the title of your Voice Chat to give people an idea of the current topic.
  • +
  • Join Voice Chats as one of your Channels to hide your personal account.
  • +
+ +

7.5.1 2021-03-05

+
    +
  • AUTO-DELETE, INVITE LINKS 2.0 AND MORE
  • +
  • Auto-Delete Messages
  • +
  • Set messages to auto-delete for everyone 24 hours or 7 days after sending.
  • +
  • Control auto-delete settings in any of your chats, as well as in groups and channels where you are an admin.
  • +
  • To enable auto-delete, press and hold on any message > Select > Clear Chat in the top left corner.
  • +
  • New Invite Links for Groups and Channels
  • +
  • Create invite links that work for a limited time or a limited number of uses.
  • +
  • See which users joined using your, or your admins’, invite links.
  • +
  • To manage invite links, open your group or channel Profile > Edit > Invite Links.
  • +
  • Groups with Unlimited Members
  • +
  • Convert groups that are approaching the member limit into unlimited Broadcast Groups.
  • +
+ +

7.4 2021-01-29

+
    +
  • Adjust volume for individual participants of a voice chat.
  • +
  • Report fake groups or channels impersonating famous people or organizations by opening their Profile > More > Report.
  • +
  • Bug fixes and minor improvements.
  • +
+ +

7.3 2020-12-24

+
    +
  • Voice Chats Done Right
  • +
  • Voice Chats in Groups
  • +
  • Turn any of your group chats into a hop-on, hop-off conference call.
  • +
  • Choose 'Start Voice Chat' under in the profile of any group where you are an admin to create a voice chat.
  • +
  • Get up to several thousand participants in each voice chat.
  • +
  • Control the number of speakers with flexible admin tools.
  • +
  • Sticker Outlines
  • +
  • Download stickers faster and watch shimmering outlines as they load.
  • +
+ +

7.2.4 2020-11-29

+
    +
  • Added support for new ARM processors. Entering Hyperspace.
  • +
+ +

7.2.3 2020-11-18

+
    +
  • Fixed a wisdom tooth.
  • +
  • Say 'bug fixes' again. Say 'bug fixes' again, I dare you. I DOUBLE DARE YOU!
  • +
  • The sun is shining, the icon is sweet.
  • +
+ +

7.2.1 2020-11-09

+
    +
  • PINNED MESSAGES 2.0, PLAYLISTS AND MORE
  • +
  • Multiple Pinned Messages
  • +
  • Pin several messages in any chat, including one-on-one chats.
  • +
  • Jump between pinned messages or open them all on a separate page via the top bar.
  • +
  • Playlists and More
  • +
  • Send several music tracks as a playlist.
  • +
  • View detailed statistics about the performance of individual posts in your channels.
  • +
  • Send a :slot_machine: emoji to any chat to try your luck.
  • +
+ +

7.1 2020-10-02

+
    +
  • ANONYMOUS GROUP ADMINS, CHANNEL COMMENTS AND MORE
  • +
  • Anonymous Group Admins
  • +
  • Turn on 'Remain Anonymous' in an admin's Permissions to let them post on behalf of the group and become invisible in the list of members.
  • +
  • Channel Comments
  • +
  • Comment on posts in channels that have a discussion group.
  • +
  • Get notified about replies to your comments via the new Replies chat (if you are not a member in the discussion group).
  • +
  • Silent Messages, now in Secret Chats
  • +
  • Send messages silently in Secret Chats by holding the Send button.
  • +
+ +

7.0.1 2020-09-07

+
    +
  • Yes, Video Calls (alpha version)
  • +
  • Telegram turns 7 years old!
  • +
  • Thank you for your support over all these years. Because of you, this year Telegram reached 400 million active users and is now one of the top 10 most downloaded apps in the world.
  • +
  • To celebrate our 7th anniversary together, we are launching the first version of the feature you’ve been asking for – ultra secure and fast Video Calls.
  • +
+ +

6.3.1 2020-07-31

+
    +
  • PROFILE VIDEOS, 2 GB FILE SHARING, AND MORE
  • +
  • Telegram is now among the top 10 most downloaded and most used apps in the world.
  • +
  • Increased limits for sending files
  • +
  • Share and store unlimited files of any type, now up to 2 GB each.
  • +
  • Profile Videos
  • +
  • Set a Profile Video instead of a static picture.
  • +
  • Quickly change back to a previous profile photo or video by tapping ‘Set as Main’.
  • +
  • Mini-thumbnails, Group Stats and More
  • +
  • See what media is in a message thanks to new mini-thumbnails in the chat list, message search and notifications.
  • +
  • View detailed statistics for the large groups you own.
  • +
  • If you're getting too much attention, flip a switch in Privacy and Security settings to automatically archive and mute all new chats from non-contacts.
  • +
  • Send a single football emoji to see if you score a goal.
  • +
+ +

6.2.5 2020-07-22

+
    +
  • Bug fixes and minor improvements.
  • +
+ +

6.2.3 2020-06-18

+
    +
  • Better GIFs
  • +
  • Enjoy greatly enhanced loading times for GIFs.
  • +
  • Quickly find GIFs in emoji-based sections covering the most popular emotions.
  • +
  • Check the Trending Tab for the top reactions of the day.
  • +
  • Bug fixes and other minor improvements.
  • +
+ +

6.1.4 2020-05-07

+
    +
  • Bug fixes and other improvements.
  • +
+ +

6.1.2 2020-04-30

+
    +
  • 400 MILLION USERS, QUIZZES 2.0 AND €400K FOR QUIZ CREATORS.
  • +
  • Access Shared Media faster from fully redesigned profile pages.
  • +
  • Use the new brush tools in the photo editor to draw on photos when sending or editing.
  • +
  • If you have too many folders, try the alternative mode with folder tabs on the left.
  • +
  • Send a single dart emoji to see if you hit the bullseye.
  • +
  • Add explanations that appear after users respond to a quiz question.
  • +
  • See how much time you have left to answer a question from @QuizBot with the new countdown animation.
  • +
  • Quiz Creator Contest
  • +
  • Participate in Telegram's €400,000 contest by using @QuizBot to create and publish an educational test on any subject.
  • +
+ +

6.0 2020-03-30

+
    +
  • Chat Folders and More
  • +
  • Organize chats into Chat Folders if you have too many chats.
  • +
  • Create custom folders with flexible settings, or use default recommendations.
  • +
  • Pin an unlimited number of chats in each folder.
  • +
  • Archive chats to hide them from "All chats". Muted chats will always stay in the Archive.
  • +
  • View detailed statistics about the growth of your large channels and the performance of their posts.
  • +
  • Send 🎲 to any chat to try your luck and get a random number from the animated dice.
  • +
  • Send 🦠, 🤒, 😷, 🤕, 🤧, 🤢, 🤮, 🧼, 💉, 💊 or 🚑 to try out the new animated emoji.
  • +
+ +

5.9.3 2020-02-23

+
    +
  • Bug fixes and minor improvements.
  • +
+ +

5.9.2 2020-02-20

+
    +
  • Increased stability, optimized memory usage.
  • +
  • Bug fixes and minor improvements.
  • +
  • The oracle would like to know what you think of the color blue.
  • +
+ +

5.9.1 2020-01-23

+
    +
  • Polls 2.0: Open Polls, Multiple Answers, and Quiz Mode
  • +
  • Create three new kinds of polls.
  • +
  • See who voted in Open Polls with non-anonymous results.
  • +
  • Vote for several options in polls that allow Multiple Answers.
  • +
  • Try to guess the correct answer in Quiz-style polls.
  • +
  • Explore various ways of combining the different poll options.
  • +
  • Just like before, you can add polls from the attachment menu in any group or channel.
  • +
+ +

5.8.1 2019-10-30

+
    +
  • Mute chats for a specific time.
  • +
  • Switch between accounts from the improved status bar menu.
  • +
  • Enjoy improved design and animations (e.g. try clicking and holding on a sticker to preview).
  • +
  • Look for new bugs that were introduced while we were fixing the old ones.
  • +
+ +

5.8 2019-10-22

+
    +
  • Enhanced design and other improvements.
  • +
  • Bug fixes.
  • +
+ +

5.8 2019-10-21

+
    +
  • Enhanced design and other improvements.
  • +
+ +

5.7 2019-09-09

+
    +
  • SCHEDULED MESSAGES
  • +
  • Hold the 'Send' button and select 'Schedule Message' to automatically send something at a specified time.
  • +
  • Schedule reminders for yourself in the 'Saved Messages' chat.
  • +
  • Get a notification when any of your scheduled messages are sent.
  • +
  • CUSTOM CLOUD THEMES
  • +
  • Choose a custom accent color and quickly create a new theme in Settings > Appearance.
  • +
  • Share your themes with other users on Telegram across platforms.
  • +
  • Update your theme for all its users when you change something.
  • +
  • NEW PRIVACY SETTINGS AND MORE
  • +
  • Choose who can find you on Telegram when they add your number to their phone contacts.
  • +
  • Share documents to Telegram from your favorite apps using the Share Extension.
  • +
  • Send a single 😁, 😧, 😡, 💩, 😢 or 😮 to check out what's new in the animated emoji department.
  • +
+ +
+ +
+
+
+ +
+
+
+ + + + + + + diff --git a/data/promote.telegram.org.html b/data/promote.telegram.org.html new file mode 100644 index 0000000000..67a1c66e8f --- /dev/null +++ b/data/promote.telegram.org.html @@ -0,0 +1,205 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
+

Telegram Ad Platform

+ +

Telegram provides a free and secure messaging service for more than 500 million monthly active users around the world. In addition to sending private messages and chatting in private groups, Telegram users can subscribe to public one-to-many channels.

+

Every month, Telegram users generate over 500 billion views in one-to-many channels.

+
+ +
+ +

+

Advertising on Telegram

+

Sponsored messages on Telegram are displayed in large public one-to-many channels with 1000+ subscribers and are limited to 160 characters. Sponsored Messages are based solely on the topic of the public channels in which they are shown.

+

This means that no user data is mined or analyzed to display ads, and every user viewing a particular channel on Telegram sees the same sponsored messages.

+
+ +
+ +

Context-based advertising

+

Advertisers can choose the language and approximate topics of channels where their ads will be displayed. It is also possible to choose specific channels where a certain ad will be shown – or add specific channels where it will not be displayed.

+

This allows advertisers to serve precise and efficient ads while preserving user privacy.

+

Privacy-conscious ads

+

Unlike other apps, Telegram doesn’t track or profile users based on their interactions with sponsored messages or other activities. We also prevent external links in sponsored messages to ensure that third parties can’t spy on our users. We believe that everyone has the right to privacy, and technological platforms should respect that.

+

Revenue sharing with channel owners

+

Sponsored Messages are currently in test mode. Once they are fully launched and allow Telegram to cover its basic costs, we will start sharing ad revenue with the owners of public channels in which sponsored messages are displayed.

+

Getting started

+

Telegram welcomes all responsible advertisers. Anyone can study Telegram's Ad Policies and Guidelines, create an account on the Ad Platform and try out the interface. For a detailed overview of the platform, see this guide.

+

+
+ +
+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/auth.html b/data/promote.telegram.org/auth.html new file mode 100644 index 0000000000..a59bd80a6a --- /dev/null +++ b/data/promote.telegram.org/auth.html @@ -0,0 +1,206 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
+

Telegram Ad Platform

+ +

Telegram provides a free and secure messaging service for more than 500 million monthly active users around the world. In addition to sending private messages and chatting in private groups, Telegram users can subscribe to public one-to-many channels.

+

Every month, Telegram users generate over 500 billion views in one-to-many channels.

+
+ +
+ +

+

Advertising on Telegram

+

Sponsored messages on Telegram are displayed in large public one-to-many channels with 1000+ subscribers and are limited to 160 characters. Sponsored Messages are based solely on the topic of the public channels in which they are shown.

+

This means that no user data is mined or analyzed to display ads, and every user viewing a particular channel on Telegram sees the same sponsored messages.

+
+ +
+ +

Context-based advertising

+

Advertisers can choose the language and approximate topics of channels where their ads will be displayed. It is also possible to choose specific channels where a certain ad will be shown – or add specific channels where it will not be displayed.

+

This allows advertisers to serve precise and efficient ads while preserving user privacy.

+

Privacy-conscious ads

+

Unlike other apps, Telegram doesn’t track or profile users based on their interactions with sponsored messages or other activities. We also prevent external links in sponsored messages to ensure that third parties can’t spy on our users. We believe that everyone has the right to privacy, and technological platforms should respect that.

+

Revenue sharing with channel owners

+

Sponsored Messages are currently in test mode. Once they are fully launched and allow Telegram to cover its basic costs, we will start sharing ad revenue with the owners of public channels in which sponsored messages are displayed.

+

Getting started

+

Telegram welcomes all responsible advertisers. Anyone can study Telegram's Ad Policies and Guidelines, create an account on the Ad Platform and try out the interface. For a detailed overview of the platform, see this guide.

+

+
+ +
+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/basics.html b/data/promote.telegram.org/basics.html new file mode 100644 index 0000000000..67a1c66e8f --- /dev/null +++ b/data/promote.telegram.org/basics.html @@ -0,0 +1,205 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
+

Telegram Ad Platform

+ +

Telegram provides a free and secure messaging service for more than 500 million monthly active users around the world. In addition to sending private messages and chatting in private groups, Telegram users can subscribe to public one-to-many channels.

+

Every month, Telegram users generate over 500 billion views in one-to-many channels.

+
+ +
+ +

+

Advertising on Telegram

+

Sponsored messages on Telegram are displayed in large public one-to-many channels with 1000+ subscribers and are limited to 160 characters. Sponsored Messages are based solely on the topic of the public channels in which they are shown.

+

This means that no user data is mined or analyzed to display ads, and every user viewing a particular channel on Telegram sees the same sponsored messages.

+
+ +
+ +

Context-based advertising

+

Advertisers can choose the language and approximate topics of channels where their ads will be displayed. It is also possible to choose specific channels where a certain ad will be shown – or add specific channels where it will not be displayed.

+

This allows advertisers to serve precise and efficient ads while preserving user privacy.

+

Privacy-conscious ads

+

Unlike other apps, Telegram doesn’t track or profile users based on their interactions with sponsored messages or other activities. We also prevent external links in sponsored messages to ensure that third parties can’t spy on our users. We believe that everyone has the right to privacy, and technological platforms should respect that.

+

Revenue sharing with channel owners

+

Sponsored Messages are currently in test mode. Once they are fully launched and allow Telegram to cover its basic costs, we will start sharing ad revenue with the owners of public channels in which sponsored messages are displayed.

+

Getting started

+

Telegram welcomes all responsible advertisers. Anyone can study Telegram's Ad Policies and Guidelines, create an account on the Ad Platform and try out the interface. For a detailed overview of the platform, see this guide.

+

+
+ +
+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/getting-started.html b/data/promote.telegram.org/getting-started.html new file mode 100644 index 0000000000..9a9149a8f2 --- /dev/null +++ b/data/promote.telegram.org/getting-started.html @@ -0,0 +1,321 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
  1. Telegram Ad Platform Explained
+
+
+
+

Telegram Ad Platform Explained

+ +
+

This document explores the Telegram Ad Platform in greater detail, for basic information about sponsored messages, please see this page.

+
+

Getting Started

+

The Telegram Ad Platform is a tool to create sponsored messages in public one-to-many channels with 1000+ subscribers. With this tool you can easily manage your ads and budgets, choose where your ads will be displayed and monitor their performance. For step-by-step instructions on how to create, publish and manage your ads, continue reading below.

+

Logging In

+

To start creating ads on the platform, you must first log in. This requires that you have an existing Telegram account – if you do not yet have an account, download one of our mobile apps for Android or iOS and sign up. Once you have an account, enter the account’s phone number on the login page, after which you instantly receive a message in Telegram (from our verified service account) to confirm your login to the platform.

+
+ +
+ +

Choosing an Account

+

Once you've logged in on the platform, you can proceed either with your Personal Account or by Creating an Organization.

+

Organizations are built around Telegram Groups and Channels – linking your group or channel as an organization gives all admins of that chat the ability to manage advertisements created by the organization.

+
+

Only the owner of the Group or Channel is allowed to create an organization for that chat.

+
+
+ +
+ +

After logging in, you can click Create Ad to start designing a sponsored message or Manage Budget to add funds to your account.

+

Creating an Ad

+

Click ‘Create a new ad’ to start building your advertisement. There you will see a template with several fields to fill in – such as giving your ad a Title, Text, and URL.

+

All links included in the Text and URL field must link to a channel or bot on Telegram, using the format t.me/link or @link. Links to external sites are not allowed.

+
+ +
+ +
+

The link entered in the URL field will be added to a button underneath your sponsored message. If you include a link in the text as well, it must go to the same destination as the link in the URL field.

+
+

CPM and Ad Budget

+

Once the text of your sponsored message is completed, you can set a CPM (Cost-Per-Mille) for the ad, which is the price for one thousand views of your ad. The minimum CPM for a sponsored message is €2.

+

Your ad budget is the amount of funds you are willing to spend on a particular sponsored message. The sponsored message will continue to be shown until it reaches this amount.

+
+

To increase an ad's budget, open it or click the budget field right from your homepage.

+

To decrease an ad's budget, stop and delete the ad – the remaining funds will be returned to your overall budget.

+
+

Language, Topics and Target Channels

+

Sponsored messages are displayed in public channels with 1000+ subscribers. To better customize which channels can host your advertisements, select languages and topics that suit your audience – for example English and Spanish channels related to Movies and Music. You are able to combine several languages and topics, or even leave the fields blank if you prefer.

+

If there are individual channels in which you would specifically like your sponsored message to appear, you can include them via their unique link, such as t.me/durov. Certain topics and channels can also be excluded, giving even more customization. When you are ready, check the box to confirm you have read the Ad Platform Terms of Service and click ‘Create Ad’.

+
+

Note that once your ad is created, its targeting parameters can’t be changed. But you can always use the 'Create a similar ad' function to quickly create a new ad with the same parameters and tweak whatever you wanted to change.

+
+

Copying Ads

+

When you open any of your existing ads, you can use the 'Create similar ad' link next to its name to create a new ad with the same text and parameters. This can be handy if you want to create several ads with slightly different targeting parameters, change targeting parameters in an ad you created, or lower the budget of an ad.

+
+ +
+ +

Adding Funds

+

If you are creating an ad for the first time, you may not have funds in your account yet. When you try to create your ad, you may see a ‘Your balance is too low’ message under the Budget field. Click ‘Add Funds’ to put money on your account – the ad will be saved as a draft so you can easily publish it later.

+
+ Add funds +
+ +
+

You can also publish ads without a budget to get a feel for the platform – then return when you’re ready to launch them.

+
+

You can also access the interface by opening the Manage Budget page and clicking Add Funds.

+
+ +
+ +

Fill in the details about your company on the page that opens and click ‘Send Request’ – our team will review your information and contact you via a verified service account on Telegram with the necessary documents for our advertising agreement and deposit transfer.

+
+

You will receive a confirmation in Telegram each time funds are credited to your account.

+
+ + +

Managing Your Ads

+

Ad Status

+

Once you have submitted an ad, you will see it listed on your account’s homepage. An advertisment can have the following statuses:

+
    +
  • Stopped. This is the default status shown for all new ads without a budget. This status is also shown when the ad's budget has run out.
  • +
  • In Review. Our team is currently checking the ad content before it can be displayed in channels.
  • +
  • Declined. Your ad must be changed before it can go live. Open the ad to see a more detailed explanation and a link to the relevant guidelines.
  • +
  • Active. Your ad is live, and sponsored messages are appearing in Telegram according to your parameters
  • +
  • On Hold. You have paused the ad, but it's ready to become active again whenever you're ready.
  • +
+ + +

Ad Info

+

Click any of your ads on the homepage to make changes to its content and CPM, increase its budget, or see statistics. The title, text and URL of your sponsored message can be updated at any time (but not its targeting parameters) – to see a preview of how the sponsored message looks inside a channel, click ‘Preview Ad’.

+
+ +
+ +
+

If you would like to change the targeting parameters, click ‘Create a similar ad’ – this opens a new template with the same content so you can quickly make a new version.

+
+

Ad Budget

+

To increase the budget of your ad, click the ‘Current Budget’ field. You can also change the CPM to be higher or lower from the ‘CPM’ field. If you need to delete your ad (perhaps to resubmit it with new targeting parameters or a lower budget) tap ‘Delete Ad’.

+
+

It is not possible to decrease the budget of an ad once it has been submitted – in this case, it is best to use ‘Create a similar ad’ and submit a new ad with a lower budget.

+
+ + +

The budget can also be increased from the ‘Budget’ tab. This tab also contains the ad’s Transaction History, showing the ad's spending as well as any increases to the budget – including the amount and time of the increase.

+ + +

Statistics

+

The ‘Statistics’ tab has an overview of your advertisement, such as the date it was created, CPM, budget and overall views. Underneath, you will see a detailed graph showing views of your sponsored message and the number of times a user joined your channel or started the bot after viewing the sponsored message, able to be displayed in increments of minutes or days.

+

Your Account and Organizations

+

Click your name in the top-right corner to open a menu – here you can edit your account info, create a new organization, switch accounts, or log out. On the ‘Edit Account Info’ page, you can change your personal info, such as your email. You can also click the ‘Budget’ tab to see the full transaction history of your account.

+
+ Edit account +
+ +

The Telegram Ad Platform allows you to be simultaneously logged in to multiple organizations, as well as your personal ad account. To switch accounts, simply click your name in the top-right corner and select ‘Switch to …’ from the menu.

+
+ Switching accounts +
+ +
+

Further Questions

+

The platform is currently running in test mode. We will be expanding this document with more details.

+

Once you've added funds to your account, you will get access to Telegram's dedicated Ad Platform Support.

+
+ +
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/guidelines.html b/data/promote.telegram.org/guidelines.html new file mode 100644 index 0000000000..012fd88cfb --- /dev/null +++ b/data/promote.telegram.org/guidelines.html @@ -0,0 +1,313 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
  1. Ad Policies and Guidelines
+
+
+
+

Ad Policies and Guidelines

+ +

These Ad Policies and Guidelines apply to all ads displayed on the Telegram Ad Platform and describe what ad content is allowed on Telegram.

+

Advertisers are responsible for their ads and for complying with these Ad Policies and Guidelines, the Telegram Ad Platform Terms of Service, the Telegram Terms of Service and Privacy Policy.

+
+

1. Ad format
2. Editorial requirements
3. Link format
4. Destination
5. Prohibited content
5.1. Graphic, shocking, or sexual content
5.2. Hate, violence, harassment
5.3. Third party rights
5.4. Deceptive, misleading, or predatory advertising
5.5. Election or political ads
5.6. Gambling
5.7. Deceptive or harmful financial products or services
5.8. Medical services, medications, supplements
5.9. Drugs, alcohol, tobacco, fast food
5.10. Weapons, firearms, explosives, ammunition
5.11. Spam software, malware, hacking
5.12. Products of questionable legality

+
+

1. Ad format

+

Ads can only promote products inside Telegram, such as channels or bots. Each ad consists of an ad text and a button that opens a link to the advertised product. The maximum length of the ad text is 160 characters including spaces.

+

2. Editorial requirements

+

Standard requirements of style, clarity, spelling and punctuation apply to all ads. Numbers, marks and symbols must be used properly. The following is not allowed:

+
    +
  • Profanity or vulgarity, including slur acronyms and spelling variations, in any language, and masked vulgarity (e.g., f**k)
  • +
  • Unrecognizable or unclear meaning, such as overbroad or vague descriptions, repetition of words and phrases
  • +
  • Excessive or gimmicky use of CaPiTaLiZaTiOn, highlighting, s p a c i n g and s,y,m,b,o,l,s, including Unicode art, ASCII art and box-drawing
  • +
  • Intrusive, excessive or gimmicky use of emoji and other emoticons
  • +
  • Line breaks, bullet points, numbering lists
  • +
+

3. Link format

+

In addition to the main ad link submitted in the ‘URL’ field, ads may also include one optional link in the ad text itself, using the format t.me/link or @link. The ad link and the link in the ad text must both lead to the same channel or bot on Telegram.

+

If the destination is a Telegram bot, links may include start parameters for the bot.

+

Links must be used properly. Particularly, the following is not allowed:

+
    +
  • Using more than one link in the ad text
  • +
  • Using any external links, such as URL shorteners or links to any other websites, even if users are ultimately redirected to the channel or bot
  • +
+

4. Destination

+

The destination channel or bot on Telegram must be technically and visually complete and functional, and its content should be consistent with the ad. Destination channels must be public. Particularly, the following is not allowed:

+
    +
  • Destinations solely designed for displaying ads
  • +
  • Unrelated destinations, such as when the destination link doesn’t correspond with the ad text
  • +
  • Invalid or unsupported destinations, such as external links, etc.
  • +
+

5. Prohibited content

+

These Ad Policies and Guidelines prohibit some types of content to ensure a safe and pleasant experience for Telegram users. The following requirements apply to ads on the Telegram Ad Platform and to the products they promote, whether implied or explicit. All examples given are non-exhaustive.

+

5.1. Graphic, shocking, or sexual content

+

Ads must not promote graphic, shocking, or sexual content, products and services.

+

Examples:

+
    +
  • Gruesome, disgusting, or shocking imagery, including gore, bodily fluids, accident photos, graphic details of torture
  • +
  • Nudity, sexually explicit and sexually suggestive content, including excessively exposed intimate body parts, sexual merchandize and entertainment, dating services
  • +
+

5.2. Hate, violence, harassment

+

Ads must not promote hatred, intolerance, harassment, discrimination, violence, or abuse.

+

Examples:

+
    +
  • Violence and its promotion, including supporting organizations or movements with ties to violence
  • +
  • Promoting harassment or bullying, including dehumanizing speech, statements of inferiority, defamatory content, disclosing contact details or personal data
  • +
  • Discrimination towards individuals, groups, or organizations, including hateful messages on the basis of race, religion, color, national or ethnic origin, age, beliefs, sexual orientation or practices, physical or mental abilities
  • +
+

5.3. Third party rights

+

Ads and promoted content must not violate third party rights, including trademark, copyright, privacy or other personal or proprietary rights.

+

Examples:

+
    +
  • Unauthorized distribution of copyrighted content, including pirated software and content such as movies, music, or books
  • +
  • Plagiarism, including impersonating public figures or brands, misusing brand logos or assets, e.g., the Telegram logo
  • +
+

5.4. Deceptive, misleading, or predatory advertising

+

Ads must not contain information that is false, misleading or simply does not match the product. This includes false statements, claims or offers, together with predatory advertising practices.

+

Examples:

+
    +
  • Clickbait or similar unrealistic statements, including you-just-won-X claims, shock or scare tactics
  • +
  • Exaggerated comparisons and absolute claims, including unsupported use of comparatives and superlatives: “highest incomes”, “best company”, and comparing your brand to a different one
  • +
  • Asserting personal attributes, including by using words ‘your’, ‘other’ and derivatives, such as “We know that your family prefers Telegram”
  • +
  • Capitalizing on tragedies, health crises or acts of mass violence
  • +
+

5.5. Election or political ads

+

Ads must not promote political campaigns, elections, political parties, movements, or candidates.

+

Examples:

+
    +
  • Advocating for or against a politician, political party, or political movement
  • +
  • Exploiting political controversy, including encouraging political unrest, disrupting public order
  • +
+

5.6. Gambling

+

Ads must not promote online or offline gambling, gaming, or casino-based activities involving real money, prizes, or goods of any value.

+

Examples:

+
    +
  • Games of chance or casinos, including sports betting, lotteries, bingo, fantasy sports
  • +
  • Tips, odds, forecasts, including sports picks, odds calculators
  • +
+

5.7. Deceptive or harmful financial products or services

+

Ads must not promote content, products, or services associated with deceptive or harmful financial practices.

+

Examples:

+
    +
  • Payday loans, cash loans, predatory lending, including short-term loans
  • +
  • Get-rich-quick offers, pyramid schemes, multilevel marketing, including offers of investment with guaranteed return, claims on providing insider tips on investments
  • +
+

5.8. Medical services, medications, supplements

+

Ads must not promote content, products, or services related to health and wellness.

+

Examples:

+
    +
  • Nutrition products, including weight loss products, herbal drugs, dietary supplements, vitamins, pregnancy, and fertility-related products
  • +
  • Medical devices, services, and treatments, including medical masks, plastic surgeries, pregnancy termination, therapies
  • +
  • Products with claims of healthful, curative or stimulating effects
  • +
  • Prescriptions for medications
  • +
+

5.9. Drugs, alcohol, tobacco, fast food

+

Ads must not promote psychoactive substances, alcoholic beverages, tobacco products or fast food.

+

Examples:

+
    +
  • Alcoholic beverages, including home brewing kits, non-alcoholic beer
  • +
  • Tobacco, including e-cigarettes, rolling papers, chewing tobacco
  • +
  • Recreational drugs, including equipment and paraphernalia, e.g., pipes, bongs
  • +
  • Instructions on producing drugs
  • +
  • Fast food, including fast-food chains, etc.
  • +
+

5.10. Weapons, firearms, explosives, ammunition

+

Ads must not promote the sale of weapons, explosives or ammunition, or any related content.

+

Examples:

+
    +
  • Firearms, including sporting, recreational guns, or any antique functioning guns that can cause harm
  • +
  • Ammunition or accessories, including any firearm parts or components, even unfinished, such as magazines, scopes, silencers
  • +
  • Knives and other melee weapons, including pepper spray, daggers, axes
  • +
  • Explosives, including bombs, grenades, fireworks, or firecrackers
  • +
  • Instructions on assembling or acquiring any product covered in this section
  • +
+

5.11. Spam software, malware, hacking

+

Ads must not promote content, products, or services that facilitate unsolicited communications, are intended to harm or gain unauthorized access to a user's device, or cause deceptive or unexpected consequences.

+

Examples:

+
    +
  • Social media growth manipulation, including encouraging growth of social media profiles
  • +
  • Incentivized or automated clicks, including requests to perform actions on websites or services, complete online surveys
  • +
  • Services for generating automated traffic, including services for inflating metrics/followers, sending automated content to social media platforms or other services
  • +
  • Phishing, including promotion of services that trick a user into providing personal or other information
  • +
  • Software causing deceptive or unexpected consequences, including modified apps containing malware, viruses, or any other malicious code
  • +
+

5.12. Products of questionable legality

+

Ads must not promote content, products, or services of questionable legality.

+

Examples:

+
    +
  • Forgery, including fake IDs, passports, visas, official documents
  • +
  • Human-trafficking, including marriage brokering
  • +
  • Stolen or leaked data, including carding, passwords to subscription services
  • +
  • Sale of body parts, including bodily fluids
  • +
  • Counterfeit products, including fake or bootleg goods, inauthentic artwork or digital goods, counterfeit currency
  • +
+
+

All examples on this page are non-exhaustive.

+
+ +
+
+ + + + + + + + + + + + + + + + + diff --git a/data/promote.telegram.org/tos.html b/data/promote.telegram.org/tos.html new file mode 100644 index 0000000000..0dea1f9f50 --- /dev/null +++ b/data/promote.telegram.org/tos.html @@ -0,0 +1,253 @@ + + + + + Telegram Ads + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
  1. Telegram Ad Platform Terms of Service
+
+
+
+

Telegram Ad Platform Terms of Service

+ +

1. TERMS AND DEFINITIONS

+

1.1. Account – a personalized record of the Advertiser within the Telegram Ad Platform with unique access details, containing the information on the Services, Statistics, Advertiser’s information, Ads and their status, Balance, operating tools and features.

+

1.2. Ad – an advertisement created using the Telegram Ad Platform that specifies where, how, when and which Advertising Materials are to be displayed, including the type and format of the Advertising Materials, their placement (particular channels, groups, games), CPM, Maximum Budget.

+

1.3. Advertiser – the person or entity who has entered into the Agreement with the Company.

+

1.4. Advertising Materials – any graphic/media file and/or any and all accompanying information supplied by the Advertiser to the Company to be displayed for advertising purposes in Publication Spaces. The Advertiser retains all rights, whether owned by the Advertiser or by a third party, and/or licensed or otherwise used by the Advertiser, in relation to any Advertising Materials and grants to the Company a worldwide, non-sublicensable, non-exclusive, royalty-free license to use, serve, copy, reproduce, distribute and display the Advertising Materials, in any known, agreed or hereafter developed manner.

+

1.5. Agreement – the present Terms of Service along with the Advertising Agreement reached between the Company and the Advertiser.

+

1.6. Auction – the automated system that uses certain algorithms to determine the best offered CPM in relation to an Ad for the provision of the Services.

+

1.7. Balance – the amount of money which is available on the Account and can be spent on the Services.

+

1.8. Confidential Information – all information of a Party including, without limitation, information and/or personal data provided by a Party, its related corporations, affiliates, employees, agents, representatives, advisors, or consultants, whether disclosed or communicated verbally, in writing or in any other tangible form, and whether relating to a Party’s business, operations, processes, plans, requirements, inventions, product or service information, pricing, know-how, design rights, trade secrets, software, systems, market opportunities, customers and business affairs.

+

1.9. CPM – Cost-Per-Mille, the price for one thousand Impressions of an Ad.

+

1.10. Company – the legal entity which belongs to Telegram group of companies and has a right to enter the Agreement with the Advertiser for the Services.

+

1.11. Data Protection Laws – the following legislations to the extent applicable from time to time: (a) national laws implementing the Directive on Privacy and Electronic Communications (2002/58/EC) (as amended by Directive 2009/136); (b) the General Data Protection Regulation (2016/679) (the GDPR) and the UK GDPR and any national law supplementing the GDPR or UK GDPR (such as, in the UK, the Data Protection Act 2018), and (c) any other data protection or privacy laws, regulations, or regulatory requirements, guidance and codes of practice applicable to the processing of personal data (as amended and/or replaced from time to time).

+

1.12. Impression – each occurrence of a display of an Ad to a user in a Publication Space, as evidenced by Statistics.

+

1.13. Improper Advertising – any act or omission which violates the Consumer Protection from Unfair Trading Regulations 2008 or any other applicable laws or regulations relating to advertising or marketing standards.

+

1.14. Intellectual Property Rights – trademarks, service marks, rights in trade names, business names, logos or get-up, goodwill and the right to sue for passing off, patents, supplementary protection certificates, rights in inventions, registered and unregistered design rights, copyrights (including rights in software), database rights, image rights and rights to personality, rights in domain names and URLs and social media presence accounts, and all other similar rights in any part of the world (including in confidential information, trade secrets and know-how) and whether registered or not, including, where such rights are obtained or enhanced by registration, any registration of such rights and applications and rights to apply for such registrations.

+

1.15. Maximum Budget – the maximum amount of funds, confirmed by the Advertiser, that can be deducted from the Balance for displaying a particular Ad in a Publication Space. Reaching the Maximum Budget shall result in the Ad being put on hold.

+

1.16. Publication Space – a digital space for Advertising Materials made available by the Company including, without limitation, in Telegram channels, Telegram groups and Telegram games.

+

1.17. Reporting Period – calendar month. The first Reporting Period commences on the date of signing of the Agreement and lasts up to the last day of the relevant calendar month (as an example, June 10 – June 30), the last Reporting Period commences on the first day of the relevant calendar month and lasts up to the date of the Agreement’s termination (as an example, June 01 – June 15).

+

1.18. Services – the display of the Advertising Materials in the context of a particular Ad, in the relevant Publication Space.

+

1.19. Statistics – a detailed report on the Advertiser’s Ads, which specifies the scope of the Services provided. It includes the Advertising Materials data, the cost of the Services in the Reporting Period and other data generated by the Company upon the results of automated checks.

+

1.20. Telegram App – a cloud-based mobile and desktop messaging app with a focus on security and speed, including but not limited to mobile apps for iPhone/iPad/Android/Windows phone, desktop apps for PC/Mac/Linux/macOS/Web-browser, Telegram web and all other interfaces and/or versions which exist or will be created in future.

+

1.21. Telegram Ad Platform – the software solution which provides the Advertiser with the opportunity to create Ads that participate in Auctions for Publication Spaces, control and terminate their Ads, and access the relevant Statistics within the Account.

+

1.22. Telegram Ad Policies and Guidelines – Telegram Ad Policies and Guidelines as available at: https://promote.telegram.org/guidelines.

+

1.23. Telegram Privacy Policy – Telegram Privacy Policy as available at: https://telegram.org/privacy.

+

1.24. Telegram Terms of Service – Telegram Terms of Service as available at: https://telegram.org/tos.

+

1.25. Terms of Service – Telegram Ad Platform Terms of Service as available at: https://promote.telegram.org/tos.

+

2. REQUIREMENTS FOR ADVERTISING MATERIALS

+

2.1. Advertising Materials shall be in compliance with all applicable laws, rules and regulations, present Terms of Service, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable.

+

2.2. Advertising Materials shall be in compliance with Telegram Ad Policies and Guidelines. Advertising Materials must not relate to the topics as indicated at Ad Policies and Guidelines/Prohibited Content.

+

2.3. The Company reserves the right to update Telegram Ad Policies and Guidelines and the list of topics at clause 2.2 from time to time.

+

3. RIGHTS AND OBLIGATIONS

+

3.1. The Company shall:

+

(a) pursuant to and in accordance with the Advertiser’s instructions submitted via the Telegram Ad Platform in relation to a particular Ad, provide the Services whenever the Advertiser’s CPM bid wins the Auction for a particular Publication Space, for as long as the Ad’s Maximum Budget and the Advertiser’s Balance allow.

+

3.2. The Company may, at its sole discretion:

+

(a) conduct an audit of the Advertising Materials to verify their compliance with all applicable laws, rules and regulations, present Terms of Service, Telegram Ad Policies and Guidelines, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable. The Company shall not be bound by any time frames in conducting an audit under this clause 3.2(a);

+

(b) terminate or suspend the Services without any liability in the event that the Advertising Materials, as may be evidenced by the results of any audit undertaken by the Company under clause 3.2(a) above, are in conflict with any applicable laws, rules and regulations, present Terms of Services, Telegram Ad Policies and Guidelines, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable, and inter alia, contain any elements of Improper Advertising, and/or explicitly violate the generally accepted moral and ethical standards, and/or are inconsistent with the Company’s values and principles, including the Company’s stance on fundamental human rights, freedom of speech and data privacy;

+

(c) request any supporting documentation regarding Advertising Materials, including, without limitation, the relevant licenses/permits/certificates for licensed goods/services, agreements with Advertiser’s customers for distribution of goods/services which contain Intellectual Property Rights, and suspend provision of Services until and unless such information is provided to the satisfaction of the Company;

+

(d) request any supporting documentation on Advertiser’s legal status, including, but not limited to, its constitutional documents, tax numbers, residency and related details, powers and rights of representatives, and suspend provision of Services until and unless such information is provided to satisfaction of the Company;

+

(e) transfer any information concerning Advertiser and the Advertising Materials which is required to be disclosed by any regulatory authority, any auditor of the Parties, by judicial or administrative process or otherwise by applicable law or regulation;

+

(f) change the parameters of the Services in the Telegram Ad Platform and, in particular, change the list of available Publication Spaces and minimum CPM; and

+

(g) make changes to these Terms of Service at any time by uploading an updated version of the Terms of Service to its website, which can be accessed here: https://promote.telegram.org/tos.

+

3.3. The Advertiser shall:

+

(a) be fully responsible for the compliance of the placed Advertising Materials with all applicable laws, rules and regulations, present Terms of Services, Telegram Ad Policies and Guidelines, Telegram Terms of Service, Telegram Privacy Policy, Apple App Store terms and rules as may be applicable, and Google Play terms and rules as may be applicable;

+

(b) promptly provide the Company with any information, documents and other materials that the Company may request from time to time in accordance with clauses 3.2(c) to 3.2(e) above;

+

(c) promptly inform the Company of all changes impacting the Company under this Agreement, including but not limited to the Advertiser’s business, contact details, bank details and authorized persons;

+

(d) mark the Advertising Materials, if so required by applicable law, with an indication of the age category of persons for whom it is addressed and any other indications. The Advertiser is solely responsible for correct labelling of the Advertising Materials; and

+

(e) not permit any third party to put forward a bid at an Auction using its Account.

+

3.4. The Advertiser may:

+

(a) place requests for the Services by creating Ads on the Telegram Ad Platform;

+

(b) use the Telegram Ad Platform interfaces to interact with their Ads, e.g. launch Ads and put them on hold, submit changes to the CPM and Maximum Budget of Ads, etc. Without prejudice to clause 3.2(a), changes will be usually applied after fifteen (15) minutes, but no later than in sixty (60) minutes after the request is registered by the Telegram Ad Platform; and

+

(c) be informed of the Statistics.

+

4. LIABILITY

+

4.1. In case of non-compliance or inadequate performance by the Parties of their respective obligations under this Agreement, the Parties will incur liability as provided for under applicable law; except that the Company shall not be liable for failure to fulfill or the improper fulfillment of the Agreement caused by breakdown of telecommunication and energy networks, effects of malicious software or fraudulent acts by the third parties.

+

4.2. The Company undertakes all possible effort to provide the best Services it can. Notwithstanding clause 4.1 above, however, these Services are provided "as is” and “as available” and the Company makes no guarantees that the Services always will be error-free, or that they will function without delays and disruptions. The Company disclaims all warranties, whether express or implied, including the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

+

4.3. Without prejudice to the generality of clause 4.1 above, the Advertiser shall be liable for security of the access details to the Account and shall compensate the Company for any losses related to such use by the persons not authorized to act on behalf of the Advertiser. For the avoidance of doubt, where the Advertiser is in violation of its obligations under this Agreement, the Advertiser shall reimburse the Company for any and all losses incurred as a result of such violation.

+

4.4. The Company's total aggregate liability under this Agreement whether in contract, tort (including negligence), under a warranty, undertaking or representation under statute or otherwise, for any losses or damages suffered or incurred by the Advertiser shall not exceed the total amount of the Advertiser's Balance spent in the previous calendar year.

+

4.5. The Company shall not be liable under or in connection with this Agreement whether in contract, tort (including negligence), under a warranty, undertaking or representation under statute or otherwise, for any indirect or consequential losses, any loss of business, business opportunities or goodwill, or any loss of revenue, savings or profits, whether actual or prospective or for any punitive damages, howsoever arising, whether such losses or damage were foreseeable or in the contemplation of the Advertiser or the Company.

+

4.6. Nothing in this Agreement shall limit or exclude any liability for (i) death or personal injury resulting from negligence, (ii) fraud, fraudulent misrepresentation or willful default, or (iii) for any other liability to the extent it cannot be lawfully excluded or limited.

+

5. WARRANTIES AND INDEMNIFICATION

+

5.1. Warranties – Each Party warrants to the other that:

+

(a) to the best of its knowledge, nothing in this Agreement violates any applicable law, including Data Protection Laws;

+

(b) it has the necessary financial resources to perform its obligations under this Agreement;

+

(c) it has the requisite legal right, power and authority to execute, deliver, and to perform its obligations under this Agreement;

+

(d) this Agreement constitutes its binding obligations in accordance with its terms; and

+

(e) nothing contained in this Agreement will result in a breach of any provision of its constitutional documents or result in a breach of any agreement, license or other instrument, order, judgment or decree of any court or governmental body to which it is bound.

+

5.2. Indemnity – The Advertiser hereby indemnifies, defends and holds harmless on an after tax basis the Company and each of the companies in the Company’s group and its and their directors, employees, officers, contractors, agents and any other related parties (each an Indemnified Person) from and against:

+

(a) all or any claims, actions, proceedings, liabilities, investigations, demands, judgements and/or awards (in each case whether or not successful, compromised or settled and whether joint or several) (together Claims and each a Claim) which may be asserted, established, instituted, made, pending, threatened or alleged against or otherwise involve an Indemnified Person in any jurisdiction by any person whatsoever, including without limitation by a third party or by any supervisory or regulatory agency or body; and/or

+

(b) all or any loss, damage, cost, liability, demand, charge, expense or tax (including, without limitation, (i) any direct, indirect or consequential losses, loss of profit, loss of business, business opportunities or goodwill, loss of reputation, (ii) all interest, penalties, legal costs and all other professional costs and expenses, (iii) all losses suffered or incurred in investigating, preparing for or disputing or defending or providing evidence in connection with or settling any Claim and/or in establishing its right to be indemnified pursuant to this clause 5.2 and/or in seeking advice regarding any Claim and/or in any way related to or in connection with the indemnity contained in this clause 5.2) (together Losses and each a Loss) which may be suffered or incurred by an Indemnified Person,

+

which, directly or indirectly, arise out of, or are attributable to, or are connected with the performance of the Agreement, the Ads, the Advertising Materials, the advertised goods or services or consumption thereof, or non-compliance by the Advertiser with any terms of this Agreement.

+

5.3. Conduct of claims

+

(a) Each Indemnified Person shall give notice as soon as reasonably practicable to the Advertiser of any action commenced against it after receipt of a written notice of any Claim or the commencement of any action or proceeding in respect of which a Claim for indemnification may be sought hereunder, insofar as may be consistent with any obligation of confidentiality or other legal or regulatory obligation which that Indemnified Person owes to any third party or to any regulatory request that has been made of it, but failure to so notify the Advertiser shall not relieve the Advertiser from any liability or any obligation to indemnify the Advertiser and in any event shall not relieve the Advertiser from any liability which the Advertiser may have. Legal advisers to any Indemnified Person shall be selected by such Indemnified Person in its absolute discretion.

+

(b) The Advertiser shall, at the request of any Indemnified Person, conduct the defense of any such action and shall do so at its own expense; provided, however, that legal advisers to the Advertiser shall be reasonably satisfactory to the Indemnified Persons and shall not (except with the consent of the Indemnified Person) also be legal advisers to the Indemnified Person. If the Advertiser conducts the defense of an action, it shall provide each relevant Indemnified Person with all relevant information in respect of any such action on a timely basis (including, without limitation, on request) and the Advertiser will take such action, in each case, as each relevant Indemnified Person may reasonably request.

+

(c) The Advertiser shall not, without the prior written consent of the Indemnified Persons, settle or compromise or consent to the entry of any judgment with respect to any litigation, or any investigation or proceeding by any supervisory or regulatory agency or body, commenced or threatened, or any claim whatsoever in respect of which indemnification could be sought under clause 5.2 (whether or not the Indemnified Persons are actual or potential parties thereto), unless such settlement, compromise or consent: (i) includes an unconditional release of each Indemnified Person from all liability arising out of such Claim; and (ii) does not include a statement as to or an admission of fault, culpability or a failure to act by or on behalf of any Indemnified Person.

+

(d) The provisions of this clause 5 shall not affect or be affected by any other agreement to which any Indemnified Person is a party with respect to indemnification.

+

5.4. Contracts (Rights of Third Parties) Act 1999 – Each Indemnified Person will have the right under the Contracts (Rights of Third Parties) Act 1999 to enforce its rights against the Advertiser under this clause 5; provided that only the consent of the specified parties to the Agreement shall be required to make any amendment of the Agreement or give any waiver under the Agreement.

+
+ +
+
+ + + + + + + + + + + + + + + + + diff --git a/data/telegram.org.html b/data/telegram.org.html new file mode 100644 index 0000000000..c8aca89b2d --- /dev/null +++ b/data/telegram.org.html @@ -0,0 +1,283 @@ + + + + + Telegram Messenger + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ + + + + + +
+ +

Why Telegram?

+ +
+
+
+
+

Simple

+
Telegram is so simple you already know how to use it.
+
+
+ +
+
+
+

Private

+
Telegram messages are heavily encrypted and can self-destruct.
+
+
+ +
+
+
+

Synced

+
Telegram lets you access your chats from multiple devices.
+
+
+ +
+
+
+

Fast

+
Telegram delivers messages faster than any other application.
+
+
+ +
+
+
+

Powerful

+
Telegram has no limits on the size of your media and chats.
+
+
+ +
+
+
+

Open

+
Telegram has an open API and source code free for everyone.
+
+
+ +
+
+
+

Secure

+
Telegram keeps your messages safe from hacker attacks.
+
+
+ +
+
+
+

Social

+
Telegram groups can hold up to 200,000 members.
+
+
+ +
+
+
+

Expressive

+
Telegram lets you completely customize your messenger.
+
+
+
+
+ +
+ +
+
+
+ + + + + + + + diff --git a/data/telegram.org/android.html b/data/telegram.org/android.html new file mode 100644 index 0000000000..b3446fa6dc --- /dev/null +++ b/data/telegram.org/android.html @@ -0,0 +1,79 @@ + + + + + Telegram for Android + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+ + +

Telegram for Android

+
+
You can download Telegram for your Android device here. This version has fewer restrictions and receives automatic updates directly from telegram.org
+ + + +
+

How to Install Telegram?

+
This video shows how to install Telegram on your Android device. See this page for detailed steps on various versions of Android.
+
+ +
+
More comfortable with installing apps
from the Google Play Store?

Download Telegram from Google Play
+
+
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/api.html b/data/telegram.org/api.html new file mode 100644 index 0000000000..909849ddfc --- /dev/null +++ b/data/telegram.org/api.html @@ -0,0 +1,283 @@ + + + + + Telegram Messenger + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ + + + + + +
+ +

Why Telegram?

+ +
+
+
+
+

Simple

+
Telegram is so simple you already know how to use it.
+
+
+ +
+
+
+

Private

+
Telegram messages are heavily encrypted and can self-destruct.
+
+
+ +
+
+
+

Synced

+
Telegram lets you access your chats from multiple devices.
+
+
+ +
+
+
+

Fast

+
Telegram delivers messages faster than any other application.
+
+
+ +
+
+
+

Powerful

+
Telegram has no limits on the size of your media and chats.
+
+
+ +
+
+
+

Open

+
Telegram has an open API and source code free for everyone.
+
+
+ +
+
+
+

Secure

+
Telegram keeps your messages safe from hacker attacks.
+
+
+ +
+
+
+

Social

+
Telegram groups can hold up to 200,000 members.
+
+
+ +
+
+
+

Expressive

+
Telegram lets you completely customize your messenger.
+
+
+
+
+ +
+ +
+
+
+ + + + + + + + diff --git a/data/telegram.org/apple_privacy.html b/data/telegram.org/apple_privacy.html new file mode 100644 index 0000000000..e1b3a7e78d --- /dev/null +++ b/data/telegram.org/apple_privacy.html @@ -0,0 +1,178 @@ + + + + + Apple Privacy Labels Explained + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Apple Privacy Labels Explained

+ +

Telegram has several fundamental principles when it comes to collecting and processing private data:

+
    +
  • We don't use your data to track you or show you ads.
  • +
  • We don't use your data to help others track you or show you ads.
  • +
  • We only store the data that Telegram needs to function as a secure and feature-rich messaging service, for as long as you need it.
  • +
+

This page explains Apple's privacy labels shown for Telegram iOS and how they can be misleading.

+
+

Note that Telegram apps, including Telegram for iOS, are open source. Independent researchers can confirm that the app is not doing anything behind your back, and verify that Telegram downloaded from the App Store is built from the exact same code that was published.

+
+ +
+

Purchases

+

Purchase History. This label may mislead you.
If you decide to use a Telegram bot to buy something, the bot may send a confirmation message or receipt to your chat with the bot. Like other messages in cloud chats, Telegram will store that message to display it to you on all your devices.

+

More in the Privacy Policy »

+
+

Financial Info

+

Payment info. This label is completely irrelevant.
When you use a Telegram bot to buy something, you can enter your credit card details and may opt to store them with the payment provider. Credit card information is never shared with Telegram.

+

More in the Privacy Policy »

+
+

Any third-party researcher can confirm this by checking Telegram's open source code (1 and 2).

+
+
+

Location

+

Precise Location. This label may mislead you.
If you share your Live Location in any chat or turn on ’Make Myself Visible’ in People Nearby, Telegram will use your data to display your location to those users with whom you are sharing it – only for as long as you keep the features enabled. By default, you don't share your location with anyone.

+

More in the Privacy Policy »

+
+

Contact Info

+

Name, Phone Number

+

Telegram uses phone numbers as unique identifiers so that it is easy for you to switch from SMS and other messaging apps and retain your social graph. Telegram does not verify display names and users are free to choose any display name they like.

+

More in the Privacy Policy »

+
+

Contacts

+

Telegram stores your up-to-date contacts in order to notify you as soon as one of your contacts signs up for Telegram and to properly display names in notifications. We only need the number and name (first and last) for this to work and store no other data about your contacts.

+

Our automatic algorithms can also use anonymized sets of phone numbers to calculate the average number of potential contacts an unregistered phone number may have on Telegram. When you open the 'Invite friends' interface, we display the resulting statistics next to your contacts to give you an idea of who could benefit most from joining Telegram.

+

Users are not required to share their contacts with Telegram, and can delete their synced contacts at any time.

+

More in the Privacy Policy »

+
+

User Content

+

Emails or Text Messages, Photos or Videos, Audio Data

+

Telegram is a cloud service. We store messages, photos, videos and documents from your cloud chats on our servers so that you can access your data from any of your devices anytime without having to rely on third-party backups. All data is stored heavily encrypted and the encryption keys in each case are stored in several other data centers in different jurisdictions. This way local engineers or physical intruders cannot get access to user data.

+

More in the Privacy Policy »

+

Gameplay Content. This label may mislead you.
If you use a bot like @gamebot to play a game, it will publish your high scores as a message in the chat. Like other messages in cloud chats, Telegram will store that message to display it to you on all your devices.

+
+

Identifiers

+

User ID
Like any other app where users have accounts (as opposed to, say, a weather or stocks app that just shows you info that is not connected to you), Telegram needs an “identifier” for each user to know which chats they will see when they log in. Like in other messaging apps, this identifier is linked to your phone number, so you easily switch from SMS and other messaging apps and retain your social graph.

+

We also support optional usernames that help users get in touch without sharing phone numbers with each other.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog.html b/data/telegram.org/blog.html new file mode 100644 index 0000000000..84769c8768 --- /dev/null +++ b/data/telegram.org/blog.html @@ -0,0 +1,268 @@ + + + + + Telegram Blog + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+

Telegram News

+
+
+ +
+

Video Stickers, Better Reactions and More

+
This update brings easy-to-make video stickers, better reactions with more compact animations and extra emoji, a button to review unseen…
+
+
Jan 31, 2022
+
+ +
+

Reactions, Spoilers, Translation and QR Codes

+
Telegram's 12th update of the year introduces reactions, message translation, themed QR codes, hidden text (spoilers), and more.
+
+
Dec 30, 2021
+
+ +
+

Protected Content, Delete by Date, Device Management and More

+
Today's update brings tools to prevent others from saving content from groups and channels, the ability to delete messages for specific…
+
+
Dec 7, 2021
+
+ +
+

Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

+
Today's update brings new ways to find memories in shared media with accelerated scrolling…
+
+
Nov 3, 2021
+
+ +
+

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

+
Today's update lets you set different themes for individual chats, share your feelings with…
+
+
Sep 19, 2021
+
+ +
+

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

+
Telegram 8.0 brings live streams with unlimited viewers to groups and channels, options to…
+
+
Aug 31, 2021
+
+ +
+

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

+
This update takes video to the next level. Group video calls now have up to 1000 viewers,…
+
+
Jul 30, 2021
+
+ +
+

Group Video Calls

+
Today's update lets you turn on your camera or share your screen during Voice Chats in groups – on all devices, including tablets and desktops. This brings voice chats to a whole new…
+
+
Jun 25, 2021
+
+ +
+

Animated Backgrounds

+
In addition to Group Video Calls, this update adds animated backgrounds and message sending animations, as well as a new menu button for bots, new ways to import stickers, reminders…
+
+
Jun 25, 2021
+
+ +
+

Payments 2.0, Scheduled Voice Chats, New Web Versions

+
This update brings Payments 2.0 for all Telegram chats, Scheduling and Mini Profiles for Voice Chats, new versions of Telegram Web for…
+
+
Apr 26, 2021
+
+ +
+

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+
Voice Chats first appeared in December, adding a new dimension of live talk to Telegram groups. Starting today, they become available in…
+
+
Mar 19, 2021
+
+ +
+

Auto-Delete, Widgets and Expiring Invite Links

+
This update brings an auto-delete timer for messages in any chat, as well as new flexible invite links and faster access to your chats…
+
+
Feb 23, 2021
+
+ +
+

Moving Chat History from Other Apps

+
Over 100 million new users joined Telegram this January, seeking more privacy and freedom. But what about the messages and memories that remain in older apps? Starting today, everyone…
+
+
Jan 28, 2021
+
+ +
+

Voice Chats Done Right

+
Today, Telegram groups get an entire new dimension with Voice Chats – persistent conference calls that members can join and leave as they please. Our 12th update in 2020 brings them…
+
+
Dec 23, 2020
+
+ +
+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+
Halloween is just around the corner and we've assembled choice tools to help organize your trick-or-treating. Practice your voodoo skills…
+
+
Oct 30, 2020
+
+ +
+

Search Filters, Anonymous Admins, Channel Comments and More

+
Your personal Telegram Cloud is endless and full of spicy memes – to help you find your way around it, we're introducing Search Filters.…
+
+
Sep 30, 2020
+
+ +
+

Video Calls and Seven Years of Telegram

+
Today marks seven years of Telegram. In 2013, we began as a small app focused on secure messaging and have since grown into a platform with over 400M users. Now this platform also…
+
+
Aug 14, 2020
+
+ +
+

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

+
Today's update brings Profile Videos along with improved People Nearby features, unlimited file sharing with up to 2 Gigabytes per file…
+
+
Jul 26, 2020
+
+ +
+

Video Editor, Animated Photos, Better GIFs and More

+
In 2015, Telegram released the most powerful photo editor to be implemented in a messaging app, letting you enhance image quality and add…
+
+
Jun 4, 2020
+
+ +
+

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

+
Telegram has reached 400,000,000 monthly users, up from 300 million a year ago. Every day…
+
+
Apr 24, 2020
+
+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/200-million.html b/data/telegram.org/blog/200-million.html new file mode 100644 index 0000000000..c3b6ab458c --- /dev/null +++ b/data/telegram.org/blog/200-million.html @@ -0,0 +1,222 @@ + + + + + 200,000,000 Monthly Active Users + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

200,000,000 Monthly Active Users

+ +
+ +
+ +

Within the last 30 days, Telegram was used by 200,000,000 people. This is an insane number by any standards. If Telegram were a country, it would have been the sixth largest country in the world.

+
+ +
+ +

We owe reaching this milestone to you alone – our users. We have never promoted Telegram with ads, so all these 200 million people are on Telegram because you invited them to join.

+

This is why you – our users – have been and will always be our only priority. Unlike other popular apps, Telegram doesn’t have shareholders or advertisers to report to. We don’t do deals with marketers, data miners or government agencies. Since the day we launched in August 2013 we haven’t disclosed a single byte of our users' private data to third parties.

+

We operate this way because we don’t regard Telegram as an organization or an app. For us, Telegram is an idea; it is the idea that everyone on this planet has a right to be free.

+
+

Above all, we at Telegram believe in people. We believe that humans are inherently intelligent and benevolent beings that deserve to be trusted; trusted with freedom to share their thoughts, freedom to communicate privately, freedom to create tools. This philosophy defines everything we do.

+
+

This was the reason why Telegram became the first messaging app to roll out end-to-end encryption to tens of millions of users in 2013. This was also the reason why Telegram became the first mainstream messaging app to fully open source its client code, and why Telegram became the first popular messenger to provide 100% open APIs for third party app and bot developers.

+

Over the years, our unconditional trust in people allowed us to do things other apps were hesitant to implement; things such as support for insanely large group chats, unlimited broadcast channels and a free user-generated sticker platform. In all these cases, our belief in people yielded extraordinary results, and users put these tools to great use.

+

What inspires us most is that, judging by the rapid growth of Telegram’s popularity, this belief might be mutual. While we unconditionally believe in people, it turns out 200,000,000 humans also believe in us.

+

Thank you for this – we will always have your back.

+

+
+

+ + +

March 22, 2018,
Pavel Durov

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/400-million.html b/data/telegram.org/blog/400-million.html new file mode 100644 index 0000000000..2cfa223db0 --- /dev/null +++ b/data/telegram.org/blog/400-million.html @@ -0,0 +1,272 @@ + + + + + 400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

+ +
+ +
+ +
+ 400 Million Users, 20,000 stickers, Quizzes 2.0 and €400K for Quiz Creators +
+ +

Telegram has reached 400,000,000 monthly users, up from 300 million a year ago.

+

Every day at least 1.5 million new users sign up for Telegram. Features like folders, cloud storage and desktop support make Telegram ideal for remote work and study during the quarantine. It's no wonder Telegram is the #1 most downloaded social media application in over 20 countries – people all over the world are switching to Telegram at an accelerating pace.

+
+ Telegram's growth over the last 7 years. +
+ +

When we started Telegram 7 years ago, we assumed that people will always choose freedom and quality over restrictions and mediocrity. As the gap in popularity between Telegram and its older competitors narrows, we find more and more validity in that original assumption. Thank you for being smart and free!

+

What's next, you might ask? The current global lockdown highlighted the need for a trusted video communication tool. Video calls in 2020 are much like messaging in 2013. There are apps that are either secure or usable, but not both. We'd like to fix that, and we will focus on bringing you secure group video calls in 2020.

+

When will they be ready? You'll be the first to know when we're done, promise. So stop asking. 😈

+

Better Quizzes

+

We added Quiz Mode to Telegram Polls back in January, allowing users to flex their trivia muscles. In recent weeks, we witnessed a surge of more serious educational tests and quizzes created using @QuizBot. Today's update upgrades quizzes with educational features.

+

You can now add explanations that appear as users respond to quiz questions, helping them learn from their mistakes, or giving them more context. Explanations make Telegram quizzes suitable not only for testing knowledge — but also for spreading it.

+
+ +
+ +
+

For example, update the app and try this test on Telegram History and Features.

+
+

When you create a quiz via @QuizBot, you can set a timer for questions. Timers add to the competitive element of Telegram quizzes, which are often used for exam preparation in student group chats. With the new countdown animation, everyone can see how much time they have left.

+

€400K for Creators of Educational Tests

+

With 2 billion students currently away from schools, the world is in dire need of online educational tools. We’d like to contribute to solving this problem by creating a database of educational tests for all subjects and levels. To do that, today we’re announcing a crowd-sourcing initiative in which we will distribute EUR 400,000 among creators of educational tests.

+

To take part, use @QuizBot to create and publish an original educational test on any subject at any difficulty level, in any language. Feel free to choose anything from basic Medieval European History in English to Mikrobiologie für Experten auf Deutsch – and add any media you require to your questions, but make sure all intellectual property rights are respected.

+

We will publish the quizzes you submit in a searchable directory. Based on their quality and popularity we will then announce the winners in several stages. Submissions for the first stage end on May 15.

+
+

Subscribe to the @contest channel for updates on this and other competitions we run. Last year alone, we distributed 2 Million Euro among the winners of our contests. 💰

+
+

20,000 Stickers

+

While Telegram has been the go-to place for stickers since they first came out, until today there wasn’t an easy way to see all the best stickers all at once. Meet the new sticker directory, where you can browse and search the over 20,000 high-quality free Telegram stickers created in the last 5 years.

+
+ +
+ +

If you have a particular set in mind, you can find it via search, or if you feel like taking a trip through the Museum of Sticker History, you can scroll through the list and go all the way from today's trends to the first Sticker Sapiens that walked the earth.

+

New Attachment Menu on Android

+

On Android, all sections of the attachment menu are now accessible as expandable layers, making the menu sleek, chic, and easier to use. Also, don't miss the cute animated icons.

+
+ +
+ +

macOS Improvements

+

Users of Telegram for macOS can now access Shared Media straight from the redesigned profile pages. Those who have a lot of Folders may like the new folder sidebar with icons in the style of Telegram Desktop.

+

By the way, this screenshot was created using the updated in-app photo editor which now allows you to draw on pictures when sending or editing:

+
+ New macOS features. +
+ +

Bullseye

+

To accompany the animated 🎲 emoji from last update, you can now take a shot at throwing animated darts 🎯 in any chat to see who hits the bullseye first.

+
+ +
+ +

We hope you like this update – all 400,000,000 of you.

+

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/6-years.html b/data/telegram.org/blog/6-years.html new file mode 100644 index 0000000000..63918b1cdb --- /dev/null +++ b/data/telegram.org/blog/6-years.html @@ -0,0 +1,1355 @@ + + + + + Celebrating 6 Years of Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Celebrating 6 Years of Telegram

+ +
+ +
+ +

We launched Telegram 6 years ago, on August 14, 2013 – and immediately set to work on the next update. That‘s how it’s been ever since.

+

After a little while we noticed that our work not only brings progress to Telegram – but also results in the evolution of messaging as a whole. It is heartwarming to see our solutions and design decisions adopted as de facto standards across the board.

+

To keep you entertained while we‘re working on this month’s second update, we've compiled a brief history of Telegram. It ended up rather on the ‘humongous’ side of ‘brief’ – but it's not like the next update is tomorrow either. So read on.

+

Oh, and if you want to give us a gift, bring two of your best friends to Telegram today.

+
+
+ A poster celebrating 6 years of Telegram +
+ +

A (Not So) Brief History of Telegram

+

For some reason, we started writing this backwards – from the latest update to the primordial summer of 2013. And then it was too late to change the order because the guy who compiled the post said he would go on a hunger strike if we tried.

+

So if you're a fan of chronology, please jump to the end and scroll up from there. (By the way, we decided we're going to keep this post up to date as new updates arrive.)

+

September 2019

+

Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy

+

The end of summer brought scheduled messages and reminders to better keep track of important tasks and appointments. On the visual side, shareable Custom Cloud Themes came to all platforms, along with more animated emoji.

+

An important privacy option was added for those who need it most – Who Can Find Me By My Phone Number. This new setting can prevent random users (or government organizations) from being able to match a number from their device's contacts to your Telegram account.

+

On Telegram since September 2019:

+ +

August 2019

+

Silent Messages, Slow Mode, Admin Titles and More

+

The August update brought a way to send silent messages – which result in a notification without sound. We also added custom titles and a slow mode for group admins. But you probably remember this, it's only been a week.

+

Following the success of animated stickers, this update also introduced animated emoji for ❤️, 👍, 😒, 😳 and 🥳. More followed.

+
+ TITLE +
+ +

On Telegram since August 2019:

+ +

July 2019

+

Animated Stickers Done Right

+

The July update introduced animated stickers. We managed to achieve a smooth 60 FPS at just 20-30 KB per sticker. Animated stickers consume less bandwith than static ones and less battery than GIFs, while commanding more attention than the two combined.

+

Here are some sample animated sets in case you missed them: Hot Cherry, Tidy Tie Tom, Resistance Dog, Fred the Pug, Melie the Cavy, Earl the Wolf, Egg Yolk

+

These stickers are powered with uranium and dreams and are guaranteed to keep going forever.

+
+ TITLE +
+ +

On Telegram since July 2019:

+ +
+

June 2019

+

Location-Based Chats, Adding Contacts Without Phone Numbers and More

+

The June update focused on making it easier to add people to contacts. A universal Add button was introduced to all new chats, making it possible to add users to contacts even if you don't know their number yet.

+

A new Add People Nearby section was created to quickly exchange numbers with people close to you. The new section also allows creating location-based public chats.

+
+ TITLE +
+ +

On Telegram since June 2019:

+ +
+

May 2019, Second Update

+

Focused Privacy, Discussion Groups, Seamless Web Bots and More

+

The second May update made Telegram Privacy Settings even more flexible. You can add whole groups to ‘Never Share’ or ‘Always Share’ exceptions. Settings will adjust automatically as people join and leave the groups.

+

On Telegram, your phone number was never visible to random people in groups, the default being ‘My Contacts’. This update offered even more control via Settings > Privacy & Security > Phone Number.

+

The update also introduced an easier way to integrate web services with Telegram, adding one-tap authorization via bots. Last but not least, it offered two new ways of adding comments to channels – via Comments.app and connected discussion groups. (We didn't start the flame war.)

+
+ TITLE +
+ +

On Telegram since May 31, 2019:

+ +
+

May 2019, First Update

+

Archived Chats, a New Design on Android and More

+

The first May update introduced Archived Chats. Unmuted chats pop out of the archive with the next incoming message – but muted chats stay archived forever (or until they generate a notification via a mention or reply). An unlimited number of chats can be pinned in the archive.

+

Android design got a major overhaul. Aside from the visual improvements, this update added a three-lines-per-chat view option for the Android chat list (similar to the iOS default), as well as bulk actions in the chats list to easily delete, archive or mute multiple chats at once.

+
+ TITLE +
+ +

On Telegram since May 9, 2019:

+ +

March 2019

+

Taking Back Our Right to Privacy

+

Before the March update, you could delete your messages within 48 hours of sending them. As of this update, you can delete any message you've ever sent or received in any private chat, there's no time limit. This also applies to clearing entire chats. The deleted messages don't leave a mark in the chat.

+

This update also introduced a setting for Anonymous Forwards, allowing you to control when messages forwarded from your account link back to it. This way people you chat with have no verifiable proof you ever sent them anything.

+
+ TITLE +
+ +

On Telegram since March 2019:

+ +

February 2019

+

Autoplaying Videos, Automatic Downloads and Multiple Accounts

+

Following the February update, smaller videos start playing without sound when they reach your screen. Pressing the volume buttons on your device unmutes them.

+

This update also introduced presets for autodownload settings to switch between Low, Medium, High and Custom data consumption in a few taps. Default settings for data usage have become more generous but depend on the affordability of mobile data in each particular country.

+

As of this update, iOS users can also log in to Telegram with multiple accounts from one app, easily switch between them and get notifications. Support for multiple accounts was added to Android in December 2017.

+
+ TITLE +
+ +

On Telegram since February 2019

+ +

January 2019, Second Update

+

Chat Backgrounds 2.0: Make Your Own

+

The second update in January brought chat wallpapers to version 2.0, adding support for motion and blur effects, plain color backgrounds and patterns, as well as an option to share backgrounds via links and find new ones in search.

+

For those who appreciate art history, the classical Telegram backgrounds which were used at launch can be found here.

+
+ TITLE +
+ +

On Telegram since January 31, 2019

+ +

January 2019, First Update

+

Group Permissions, Undo Delete and More

+

The first January update brought group permissions, allowing admins to restrict all members from posting specific kinds of content or even from messaging altogether. The maximum size for groups was doubled to 200,000 members.

+

The update also added an ‘Undo’ option after deleting chats or clearing history. It's like a time machine, but with fewer paradoxes.

+
+ TITLE +
+ +

On Telegram since January 21, 2019

+ +
+

2018

+
+

December 2018, Second Update

+

Polls: Bringing Choice to Communities

+

As of the second update from December '18, Telegram users can create polls in groups and channels, letting group members vote anonymously.

+

Poll bots have been available since the dawn of the Bot Platform.

+
+ TITLE +
+ +

On Telegram since December 22, 2018

+ +

December 2018, First Update

+

Custom Languages, Instant View 2.0 and More

+

This first December update in 2018 revolutionized app interfaces, adding custom languages – whether that's Māori, Scottish Gaelic or Transliterated Klingon. Qapla'. Users can share translated language packs with dedicated sharing links.

+

Everyday be talk like a pirate day if ye've downloaded the pirate speak chest. Babel fish now optional.

+
+ TITLE +
+ +

On Telegram since December 10, 2018

+ +

October 2018

+

Introducing Telegram 5.0 for iOS

+

Telegram for iOS was rebuilt from scratch for this update – using the Swift programming language. The new client is slicker, faster and more battery-friendly. If the old Telegram was a race car, this one is a race car with jet engines and a well-caffeinated driver.

+

New badge counter settings were added on iOS, allowing users to exclude messages from muted chats or count unread chats instead of messages.

+

The native macOS client added swipe gestures to navigate interfaces. MacBook Pro owners got touch bar support.

+
+ TITLE +
+ +

On Telegram since October 2018

+ +

August 2018

+

Chat Export Tool, Better Notifications and More

+

This update brought an easy way to download copies of your chats, including photos and other media using Telegram Desktop. August '18 also saw the birth of Notification Exceptions – a way to customize notification settings for particular users.

+
+ TITLE +
+ +

On Telegram since August 2018

+ +

July 2018

+

Introducing Telegram Passport

+

Telegram Passport was launched as a unified authorization service for ICOs, financial services and other platforms based on real-life ID. You no longer have to upload scans of your ID each time a different service requires it.

+
+ TITLE +
+ +

On Telegram since July 2018

+ +

June 2018

+

Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More

+

The June '18 update brought the ability to replace photos and videos when editing messages – in case you accidentally sent a picture of your lunch instead of the company's new logo.

+

As of this update, voice and video messages can be played at 2x speed and users can mark chats as read or unread.

+
+ TITLE +
+ +

On Telegram since June 2018:

+ +

March 2018

+

Sticker Search, Multiple Photos and More

+

Since they were introduced, stickers have become a key method of communication for many Telegram users. As of this update, users can search for new sticker packs.

+

I'm not addicted to sending stickers. I can stop any time.

+
+ TITLE +
+ +

200,000,000 Monthly Active Users

+

Telegram has never been promoted with ads, so every user joined because they were invited by others. Telegram is more than a messaging app, it's the idea that everyone on the planet has a right to be free.

+
+ TITLE +
+ +

On Telegram since March 2018:

+ +

February 2018

+

Two updates were launched on February 6, 2018.

+

Streaming and Auto-Night Mode on Android

+

This was when the apps got streaming support, allowing you to view videos without waiting for them to fully download. This update also introduced auto-night mode for Android users, shielding weary eyes from bright light when browsing memes in bed.

+
+ TITLE +
+ +

Telegram Login for Websites

+

Another update introduced the Telegram Login Widget for external websites, empowering businesses to use Telegram bots to automate anything from customer support to accepting payments or tracking shipments.

+
+ TITLE +
+ +

On Telegram since February 2018

+ +

January 2018

+

Two updates were launched on January 31, 2018.

+

Telegram X: Progress through Competition

+

Two Telegram X clients were unveiled as alternatives to the main iOS and Android apps – built from the ground up to be faster and easier to use, while featuring smooth animations and a sleek design. Telegram X for iOS has since become the native client on iPhones around the world.

+
+ TITLE +
+ +

TDLib - Build Your Own Telegram

+

The Telegram Database Library helps developers make their own versions of Telegram – and was used to create Telegram X for Android. TDLib handles network implementation, encryption, and local storage, giving third-party developers more time to focus on the fun parts of app design. All the API methods are fully documented and the code is available on GitHub.

+

Both Telegram X and the Telegram Bot API are an example of what can be done with this library.

+
+ TITLE +
+ +

On Telegram since January 2018

+ +
+

2017

+
+

December 2017

+

Themes, Multiple Accounts and More

+

Themes came to iOS, with simple ‘Day’ and ‘Night’ options. We considered adding a ‘Twilight’ option but it got sabotaged by lovesick vampires and werewolves.

+

Android added support for multiple accounts, to quickly switch between up to three profiles (or personalities) without logging out.

+
+ TITLE +
+ + +

On Telegram since December 2017

+ +

November 2017

+

Albums, Saved Messages and Better Search

+

Albums and Saved Messages came to Telegram in November as a way to cut down on clutter and keep things organized. Multiple media items could be sent as one message, neatly arranged instead of filling up the chat with individual messages and multiple notifications.

+

Saved Messages brought bookmarks and personal storage, giving users the ability to forward messages there for later reference.

+
+ TITLE +
+ + +

On Telegram since November 2017

+ +

October 2017

+

Live Locations, Media Player and Languages

+

October '17 expanded location sharing to include a live feed, useful for finding your friends or seeing how far they are from a destination. The interactive maps support multiple users, so your entire group can share their locations and see each other in one place.

+

Telegram also expanded its localization, launching the Translations Platform for users to refine the currently-available translations.

+
+ TITLE +
+ + +

On Telegram since October 2017

+ +
+

August 2017

+

Better Replies, Stickers & Invitations

+

Keeping track of replies and mentions was streamlined in August’s update, adding the new ‘@’ badge to the chat list, and ‘@’ button inside chats to jump from mention to mention.

+

The option to set favorite stickers was added, while groups got the ability to choose official sticker sets.

+
+ TITLE +
+ +

On Telegram since August 2017

+ +
+

July 2017

+

Disappearing Media, Your Bio & More Speed

+

July’s update added a self-destruct timer for photos and videos to give users the option to send disappearing media in Private Chats.

+

To help say a little more about themselves, user profiles were given a bio section.

+
+ TITLE +
+ + +

On Telegram since July 2017

+ +
+

June 2017

+

Supergroups 10,000: Admin Tools & More

+

Groups leveled up in June '17, increasing the maximum members to 10,000 and introducing a suite of new tools to manage the masses.

+

Admin permissions became individual, allowing for specific privileges. So did members’, meaning people could be put under custom restrictions for acting up.

+

The Recent Actions page was added for admins, showing a summary of all notable group activity within the past 48 hours.

+
+ TITLE +
+ + +

On Telegram since June 2017

+ +
+

May 2017

+

Three updates were released on May 18, 2017.

+

Video Messages and Telescope
Just in time for Summer, video messages were introduced to add another dimension to chats and channels.

+
+ TITLE +
+ +

Instant Views for Everyone & a $200K Contest

+

Instant View grew into a platform for reformatting articles from the Web into lightweight, uniform pages which instantly open in Telegram, rather than a browser. A contest to create new templates was launched.

+
+ TITLE +
+ +

Payments for Bots
Bot payments joined the pool party as well, so users could pay for goods and services right in the app.

+
+ TITLE +
+ + +

On Telegram since May 2017

+ +
+

March 2017

+

Voice Calls: Secure, Crystal-Clear, AI-Powered

+

March '17 brought voice calls to Telegram, featuring end-to-end encryption, crisp sound and incredible speed.

+

The video editor received a compression slider to change the quality at which a video is sent.

+
+ TITLE +
+ +

On Telegram since March 2017

+ +
+

February 2017

+

Custom Themes

+

Custom themes first came to the Android phone app, along with a theme editor, giving users the ability to recolor individual elements and share their creations with others.

+
+ TITLE +
+ +

Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL

+

Telegram Desktop, first launched in January '14, reached version 1.0, with a new design, refined animations and custom theme support, in addition to all its earlier features.

+

The GMail bot made its debut as well, allowing users to condense all their communications into one platform.

+
+ TITLE +
+ +

Telegram for Android Wear 2.0

+

Telegram came to wrists with its Android Wear 2.0 version, featuring fully-functional messaging capability, plus added themes to keep things chic.

+
+ TITLE +
+ + +

On Telegram since February 2017

+ +
+

January 2017

+

Unsend Messages, Network Usage, and More

+

Telegram rang in the New Year with a completely new feature - the ability to unsend messages sent within the past 48 hours.

+

To keep track of users' data consumption, Network Usage was added to Settings.

+
+ TITLE +
+ +

On Telegram since January 2017

+ +
+

2016

+
+

December 2016, Second Update

+

Meet the Telegraph API for Logins and Stats

+

The Telegraph API opened to the public in the final update of 2016. Publishing and organizing articles gained automated support with the new @Telegraph bot.

+
+ TITLE +
+ +

On Telegram since December 20, 2016

+ +
+

December 2016, First Update

+

Pinned Chats and IFTTT Integrations

+

Conversation management became easier with the option to pin chats to the top of the chat list.

+

IFTTT integration was introduced to help link Telegram to over 360 services at launch. This gives users control over their accounts on other services straight from the Telegram app – including social media, mail clients and even things like smart appliances or other devices.

+
+ TITLE +
+ +

On Telegram since December 7, 2016

+ +
+

November 2016

+

Instant View, Telegraph, and Other Goodies

+
+ TITLE +
+ +

Instant View came in November 2016, instantly loading articles and web pages all inside the Telegram app. Added in the same update, the Telegraph platform is a minimalist word processor compatible with Instant View, designed for quickly publishing documents and articles.

+

On Telegram since November 2016

+ +
+

This is where wide full-color illustrations for our blog posts end – or begin, depending on which direction you just came from.

+
+
+

October 2016

+

Gaming Platform 1.0

+

With winter not far off, Telegram introduced a Games platform that allows users to play games through bots. Players get the chance to challenge friends, while creators have an easy and accessible way to bring their game ideas to life.

+
+ +
+ +

On Telegram since October 2016

+ +
+

September 2016

+

Photo Editor 2.0, Masks and Homemade GIFs

+

In September ‘16, the time came to improve Telegram’s Photo Editor with fun new decorations like masks, text, stickers and drawings. Additionally, the video editor added the ability to make GIFs out of videos by tapping its new ‘Mute’ button.

+
+ +
+ +

On Telegram since September 2016

+ +
+

August 2016

+

Trending Stickers, Storage and More

+

A Trending Stickers option was added so popular sticker packs can be easily found and added to one's collection. Groups received previews so prospective members can see what they‘re about and who’s in them before joining the party.

+
+ +
+ +

On Telegram since August 2016

+ +
+

June 2016

+

Drafts, Picture-in-Picture, and More

+

June '16 brought cross-platform cloud drafts, syncing your unfinished messages across devices. Since then, users have been able to start typing on one device and finish on another. For more multitasking, Picture-in-Picture support was added to let users work and watch simultaneously.

+
+ +
+ +

On Telegram since June 2016

+ +
+

May 2016

+

Edit Messages, New Mentions and More

+

Fast typers rejoiced as the ability to edit sent messages was introduced in all chats. Mentions were expanded to include users without usernames, and Bots were given their own space in the attachment menu for easy access.

+
+ +
+ +

On Telegram since May 2016

+ +
+

April 2016, Second Update

+

Instant Camera and More 3D Touch

+

Instant camera was added so users could snap and send photos faster, saving the extra thumb-work to make sure the moment is captured.

+
+ +
+ +

On Telegram since April 28, 2016

+ +
+

April 2016, First Update

+

Bot Platform 2.0

+

Starting in April 2016, inline bots no longer require you to use a keyboard. These software-controlled friends now immediately present clickable options to get results with no typing required. They were also integrated with services like YouTube and Foursquare for easy video and location sharing.

+
+ +
+ +

Sharing and Previews

+

This update gave users a new way of sharing media between chats, introducing GIF and sticker previews to make the selection process more straightforward.

+
+ +
+ +

On Telegram since April 12, 2016

+ +
+

March 2016

+

Supergroups 5000: Public Groups, Pinned Posts

+

To keep order as supergroups grew from 1,000 members to 5,000, important announcements could be placed at the top of the screen as pinned messages. Additional moderation tools were introduced that helped prevent spam in public supergroups. This included the ability to report spam, ban a user outright, or simply erase all of their posts from the group.

+
+ +
+ +

On Telegram since March 2016

+ +
+

February 2016, Second Update

+

Channels 2.0 and More

+

Channels got plenty of new features including admin signatures and silent broadcasts. It became possible to edit your messages in channels and supergroups.

+
+ +
+ +

On Telegram since February 24, 2016

+ +

February 2016, First Update

+

Voice Messages 2.0, Secret Chats 3.0 and…

+

Chatting got easier with raise-to-speak and raise-to-listen functionality, streamlining voice messages by giving a no-tap way to play and record. On the privacy end, users got the ability to restrict who can invite them to groups and channels.

+
+ +
+ +

On Telegram since February 12, 2016

+ +
+

January 2016

+

Introducing Inline Bots

+

Inline bots make it possible to use bot services in any chat without adding those bots as members – you just start any message with their username and everything that comes after becomes a query for the bot. These utilities can link Wikipedia articles, post YouTube videos or search for GIFs to entertain friends. Unfortunately, while being very good at fetch, they still can't pull a sled – even after all these years.

+
+ +
+ +

GIF Revolution

+

GIF file size was reduced by 95%, making them load 20x faster. Autoplay for all GIFs was enabled to show off their new-found speed.

+
+ +
+ +

On Telegram since January 2016

+ +
+

2015

+
+

December 2015

+

Clearing Cache and Reordering Stickers

+

The space-saving option of clearing cache was introduced, including chat-by-chat specificity. This was coupled with a setting to choose how long to keep media before it gets deleted from the cache (to be re-downloaded from the cloud should you need it again).

+
+ +
+ +

On Telegram since December 2015

+ +
+

November 2015

+

Admins, Supergroups and More

+

This update added the admin role. Admins have the power to manage group chats and enforce rules. Just in time, as the maximum number of users for group chats grew to 1,000 people with the addition of supergroups.

+
+ +
+ +

On Telegram since November 2015

+ +
+

September 2015

+

Channels: Broadcasting Done Right

+

September '15 brought channels, the perfect tool for broadcasting messages to the masses. Channels can have unlimited followers, offer view counters for each post and only let the admins post. These one-way chats give updates the spotlight by moving the discussion elsewhere. Channels were quickly adopted in regions where freedom of speech falls short.

+
+ +
+ +

On Telegram since September 2015

+ +
+

August 2015

+

Shared Links and Recent Searches

+

Telegram delivered quality of life updates in August '15, showing shared links on chat info pages as well as a list of recent searches when beginning a new one.

+
+ +
+ +

On Telegram since August 2015

+ +
+

July 2015

+

In-App Media Playback and Search in Chats

+

This update added the ability to view media, enjoy music and watch videos from external sources directly in the app. Chat-specific search was implemented as well, making it easier to find messages from a particular conversation.

+
+ +
+ +

On Telegram since July 2015

+ +
+

June 2015

+

Telegram Bot Platform

+

In June of 2015, Telegram released the Bot API and created a platform for users to create and publish their own bots. Bots exist to add features to Telegram and make user's lives easier - bots can handle payments, moderate groups, fetch emails and much more.

+
+ +
+ +

Telegram on Apple Watch

+

Telegram also received Apple Watch support. With a flick of the wrist, users can view recent chats, reply with stickers, dictate messages and more. Anything that can't fit on the watch display gets a shortcut to open on your phone instead.

+
+ +
+ +

On Telegram since June 2015

+ +
+

May 2015

+

Custom Sticker Sets

+

Since May '15, stickers can be uploaded and shared as sticker sets. All apps got a dedicated sticker panel. Tapping on any sticker shows its set and lets you add the lot.

+
+ +
+ +

On Telegram since May 2015

+ +
+

April 2015

+

Migrating Existing Group Chats to Telegram

+

Invite links were added so users can easily bring their friends to group chats, even when those friends are lost in another messenger.

+
+ +
+ +

Places, Captions and more

+

Users gained the ability to caption photos, so the context and content can be sent as one message.

+
+ +
+ +

Active Sessions and Two-Step Verification

+

Telegram rolled out an essential privacy feature in April 2015 - Two-step Verification – adding an extra layer of protection by requiring a password when logging into a new device.

+
+ +
+ +

Link Previews

+

Link previews were introduced to help users see where a link leads without having to click on it and find out for themselves.

+
+ +
+ +

On Telegram since April 2015

+ +
+

March 2015, Second Update

+

Sending Files On Steroids — And More

+

This update brought the ability to send multiple files at once and trim videos before sending them.

+
+ +
+ +

On Telegram since March 25, 2015

+ +
+

March 2015, First Update

+

Reinventing Group Chats: Replies, Mentions, Hashtags and More

+

March '15 made messaging more convenient – Telegram added replies, mentions and hashtags. Replies make it easier to keep continuity in group chats, while mentions help get someone's attention and hashtags allow users to label messages for future use.

+
+ +
+ +

On Telegram since March 19, 2015

+ +
+

February 2015, Second Update

+

Photo Editor and Passcode Lock

+

February '15 delivered the most powerful photo editor among messaging apps – featuring auto-enhance, crop and rotate functions in its initial version. To keep those photos and chats secure, users were given the option to lock their app with a passcode.

+
+ +
+ +

On Telegram since February 25, 2015

+ +
+

February 2015, First Update

+

Shared Files and Fast Mute

+

This update introduced the Files tab to better view all documents shared in a particular chat (some media outlets mistakenly thought this was when we introduced sending files). Additionally, the update brought in Mute shortcuts, helping users disable notifications more quickly.

+
+ +
+ +

On Telegram since February 1, 2015

+ +
+

January 2015

+

Stickers Done Right

+

January '15 saw the first sticker on Telegram. Since then, starting a message with a single emoji brings up a list of emotionally corresponding sticker suggestions.

+

The first official stickers from Telegram formed the classic Great Minds set. Artists were invited to publish their work on the free and open platform.

+
+ +
+ +

On Telegram since January 2015

+ +
+

2014

+
+

December 2014

+

Telegram.me, Changing Numbers, PFS and more

+

Users with usernames were offered Telegram.me/username links, which open their profile page in Telegram. This update also enabled changing the phone number of a Telegram account. Single-column mode was added for Telegram Desktop, making multitasking easier on smaller screens.

+
+ +
+ +
+

Fun fact: In 2016, Instagram will restrict users from adding Telegram.me (and Snapchat) links to their bios.

+
+

On Telegram since December 2014

+ +
+

November 2014

+

There were two Telegram updates on November 19, 2014.

+

Hiding Last Seen Time - Done Right

+

This update expanded Privacy Settings to cover Last Seen status, allowing unprecedented flexibility with ‘Always Share With’ and ‘Never Share With’ exceptions for individual users.

+

This was also when account self-destruction was introduced. Telegram doesn‘t aim to accumulate and store your data when you don’t need it anymore. So if you throw away your SIM card and it gets a new owner in 6 months, they won't access your chats.

+
+ +
+ +

Material Design on Android, Instant Search for Messages and more

+

November '14 also delivered Instant Full-Text Search to iOS and Android. Since then you can quickly find any message you ever sent or received on Telegram.

+

GIF search was first supported on iOS. The Android app got a massive redesign, consistent with material guidelines.

+
+ +
+ +

On Telegram since November 2014

+ +
+

October 2014

+

Public usernames, smaller timers for Secret Chats, and more

+

October '14 marks the beginning of properly recorded history on Telegram. The first update ever to be described in a blog post brought public usernames, adding the ability to share your Telegram contact without disclosing your phone number.

+

Secret Chats got a major upgrade, with self-destructing media showing blurred thumbnails and starting the countdown only after they are first opened. This prevented them from disappearing before actually being viewed. This was also when screenshot notifications were first introduced.

+

Telegram for Android received several updates, adding support for Android Wear and tablets, as well as video compression.

+
+ +
+ +

On Telegram since October 2014

+ +
+
+ +
+ +

September 2014

+

GIFs, iPad support and broadcast lists on iOS

+

Telegram has supported iPads since September '14. In this update, the iOS app learned to play GIF animations and added cloud search for messages, as well as adding search by file name to the Shared Documents section. iOS also caught up with Android, adding support for broadcast lists.

+
+ +
+ +

On Telegram since September 2014

+ +
+

August 2014

+

Broadcast lists were first introduced to Android in August '14, only to be replaced with channels a little over a year later.

+
+ +
+ +

On Telegram since August 2014

+ +
+

June 2014

+

Multiple photo upload and more

+

Telegram for Android caught up with iOS, allowing users to preview photos before sending — as well as select and send many photos at once. Notifications were improved to be more reliable.

+
+ +
+ +

On Telegram since June 2014

+ +
+

March 2014

+

Voice Messages, Delete Messages for both sides in Secret Chats, Language Settings on Android

+

The March '14 update introduced voice messages to Telegram. Messages deleted in Secret Chats began disappearing for both sides.

+

Telegram for Android added the option to change the app language in Settings. The first languages to be added were German and Italian.

+
+ +
+ +

On Telegram since March 2014

+ +
+

February 2014

+

New apps, autodownload settings and contact management tools for Android

+

More Telegram apps entered the fray. An unofficial Telegram app for Web was introduced and later moved to web.telegram.org to become the official web version. Telegram for Windows Phone was created in a contest for app developers.

+

Meanwhile, an update introduced autodownload settings and new tools to manage contacts on Android.

+
+ +
+ +

On Telegram since February 2014

+ +
+

January 2014

+

Send documents and files

+

First thing in 2014, Telegram allowed documents of any type to be sent, including .pdf, .doc, .png, .mp3, etc. The size limit is 1,5 GB per file.

+

An unofficial Telegram app for PC was announced, which would later become the official Telegram Desktop.

+
+ +
+ +

On Telegram since January 2014

+ +
+

2013

+
+

December 2013

+

Crowdsourcing a more secure future

+

The only significant vulnerability to ever be discovered in the MTProto protocol was fixed during the First Telegram Crypto Contest. The researcher who discovered it was awarded a bounty of $100,000.

+
+ +
+ +

On Telegram since December 2013

+ +
+

October 2013

+

After a contest for Android developers, the alpha version of Telegram for Android was officially launched. Telegram apps got Secret Chats with self-destruct timers.

+

The MTProto Protocol specification and Telegram API were fully documented and the code of the apps became open source.

+
+ +
+ +

On Telegram since October 2013

+ +
+

August 14, 2013

+

Telegram for iOS was launched.

+
+

Congratulations on completing this (not very) brief course on the history of Telegram. You just got an honorary PhD in Instant Messaging – unless you simply jumped down here, in which case you still have a long way 👆to go to get back to the top.

+

Armed with this much knowledge, you should probably join our Volunteer Support Force. And if that‘s not your cup of tea – just tell us in the comments which feature you didn’t know existed.

+

+ +

August 15, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/admin-revolution.html b/data/telegram.org/blog/admin-revolution.html new file mode 100644 index 0000000000..cfb3035f2f --- /dev/null +++ b/data/telegram.org/blog/admin-revolution.html @@ -0,0 +1,261 @@ + + + + + Supergroups 10,000: Admin Tools & More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Supergroups 10,000: Admin Tools & More

+ +
+ +
+ +
+ +
+ +
+

This is an old blog post. In case you missed it, groups can already have up to 200,000 members each.

+
+

With Telegram 4.1, we're increasing the maximum size of supergroups to 10,000 members each. That’s a lot of people packed into one group, and now users and admins can use search to find specific users among them:

+
+ +

Search for members

+
+ +

Admins can also search for members in their channels.

+

With groups as big as 10,000 people – the size of a decent small town – you may be looking for some more powerful management tools. And that’s exactly what Telegram 4.1 gives you.

+ + +

Admin Rights

+

You can now add admins with specific sets of privileges to help you run your community. Choose who among your trusted admins will be able to add new users, manage messages, block members, edit group info, or even add new admins.

+
+ +

Admin rights

+
+ +

Partial Bans

+

Admins who don’t want to completely ban members from their supergroups can now partially restrict their rights in order to stop behavior that's causing problems. You can put nasty users into read-only mode or maybe stop them from sending stickers or media for a certain period of time. Now you can do all of this with absolute precision:

+
+ +

Partial bans

+
+ +

Even robots can get in on the fun. With Bot API version 3.1, you can use admin bots to automatically impose temporary or permanent bans based on member actions. Check out the docs here to start building your robotic police force today.

+

Recent Admin Actions

+

When multiple admins are working with one group, it’s easy to get confused about which admin did what and when (or which admin bot has gone Skynet on your members). That’s why we've added a “Recent Actions” section to the admins page. This section stores a log of all service actions taken in the group in the last 48 hours and is visible to admins only.

+
+
+ +

Recent admin actions

+
+
+ +

Precise filters

+
+ +

Recent actions in supergroups also show messages that were deleted in the last 48 hours and the original versions of edited messages for the same period, so nasty behavior like self-deleted spam will no longer help anyone escape the admins’ wrath.

+

Sharing and Android Pay

+

In other news, Telegram 4.1 for iOS brings you an improved sharing extension. When sharing stuff from other apps to Telegram you can add an optional comment and select multiple recipients easily. 3D Touch on the app icon to see some new actions, including taking a photo/video and sending it to multiple recipients.

+
+ +

New sharing extension

+
+ +

On Android, Telegram 4.1. gets you Android Pay support for Bot Payments and improved media selection – photos and videos are now shown together when sharing from the attachment menu or gallery.

+

Free speech

+

This update also features anti-censorship tools such as the ability to set up a Proxy server in the “Data and Storage” section of the Settings.

+

We believe in free and secure communication. It’s our responsibility to offer technology to defend our users’ right to privacy and freedom of speech around the world.

+

June 30, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/albums-saved-messages.html b/data/telegram.org/blog/albums-saved-messages.html new file mode 100644 index 0000000000..b61f9fc5fd --- /dev/null +++ b/data/telegram.org/blog/albums-saved-messages.html @@ -0,0 +1,268 @@ + + + + + Albums, Saved Messages and Better Search + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Albums, Saved Messages and Better Search

+ +
+ +
+ +
+ +
+ +

Starting with Telegram 4.5, whenever you send multiple photos or videos they are grouped into albums. Each album can include up to 10 photos or videos, arranged in the chat as elegantly proportioned thumbnails. They will also result in one notification instead of ten on the recipient’s side.

+
+
+ +
+
+ +

Photo Order

+

From now on, you can control the order in which photos are sent. Each photo you choose for sharing will show its sequence number. This makes it easy to double check that your “before-and-after” pics will be sent in the correct order.

+

Multiple Profile Photos

+

When viewing a photo from an album, you’ll see other pictures from the same group as thumbnails in the lower part of the screen. Profile photos are now also displayed this way, which makes them much easier to navigate.

+
+
+ +
+
+ +

Saved Messages

+

You can now bookmark important messages by quickly forwarding them to Saved Messages – your personal cloud storage for any messages or media you may want to send or forward there. Each saved message has a “go to” button that takes you to the right place in the chat where it was originally posted.

+
+ +

Saved Messages Chat

+
+ +

The Saved Messages chat is always displayed at the top of the list in the sharing and forwarding menus. This makes it easy to save your favorites while keeping things as tidy as before.

+
+ +

Number One in the Sharing Menu

+
+ +

Saved Messages are easy to find: they are accessible both from the Chats list and from the side panel on Android / Settings on iOS.

+

Improved Search

+

Speaking of finding things, we’ve upgraded the global search algorithm used for finding public channels, groups and bots. Now you can search for public channels and bots by their titles, and most popular items will always be displayed first.

+

Pinned Messages in Channels

+

Channel admins can now pin messages to focus their subscribers’ attention on important announcements. This tool can also come in handy if you want to help new subscribers navigate your channel.

+
+ +

Pinned Message

+
+ + +

iOS: New Settings, iPhone X Support

+

Telegram 4.5 comes packed with goodies for iOS users. The Settings screen and the context menu in chats got a makeover. Version 4.5 also works great on iPhone X.

+
+
+ +

Redesigned Settings

+
+
+ +

Edit Settings

+
+ +

And that’s it for today. We hope you enjoy these new features while we’re working on the next update!

+
+

+
+ +

November 15, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-2-0.html b/data/telegram.org/blog/android-2-0.html new file mode 100644 index 0000000000..80f5a9fe0c --- /dev/null +++ b/data/telegram.org/blog/android-2-0.html @@ -0,0 +1,257 @@ + + + + + Telegram 2.0 for Android: Material Design + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram 2.0 for Android: Material Design

+ +
+ +
+ +

Telegram for Android received a massive update today, featuring a full redesign along Android 5.0 material guidelines and adding long awaited features such as instant full-text cloud search, new flexible privacy settings for last-seen timestamps and account self-destruction.

+

Material Design

+

Every screen was updated to make Telegram consistent with Android 5.0 design standards and animations. We've also added support for the new standards on Android 4.x and even on older 2.x devices.

+
+ + + + + +
+
+ + +

Demo

+

Here‘s what Telegram’s new material design looks like in motion on a Google Nexus phone, just to give you a taste of the animations:

+
+
+
+
+
+
+ +
+
+ + +

Instant Full-Text Search

+

You can now find any message you sent or received in Telegram by using the universal search. Tapping a message in search results sends you to its place in your message history. This way you can find stuff even if you only vaguely remember the context.

+
+ + +
+
+ +

The search is much faster than what you have in GMail and other apps. Our technology guarantees that even if your inbox grows to several hundred thousands of messages, instant search will stay just as fast.

+

Hiding Last Seen Time

+

We take privacy very seriously, so we invested a lot of time and effort to make this feature right. As a result, the Who can see your Last Seen time control allows unprecedented precision and flexibility.

+
+ + + +

+
+ +

In fact, it's so good that we wrote a whole separate blog post about it. Read more here:
Privacy Revolution — Last Seen Done Right »

+

Account Self-Destruction

+

Big companies like to accumulate data about their users and keep it for an indefinite time. Telegram is not a commercial organization and we value our disk space greatly. Last year we introduced self-destructing messages, today we are adding self-destructing accounts.

+

From now on, if you stop using Telegram and do not login for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct – with options ranging from 1 month to 1 year.

+

..but I'm on iOS

+

Most of these new features are also avaible to iOS fans among Telegram users — except for material design of course. In order to maintain the balance, we're also adding a few nifty features to our iOS app today. Read all about them here:
The new Telegram for iOS — GIF search and more »

+

+ +

The Telegram Team,
November 19, 2014

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-gif.html b/data/telegram.org/blog/android-gif.html new file mode 100644 index 0000000000..d162095dea --- /dev/null +++ b/data/telegram.org/blog/android-gif.html @@ -0,0 +1,218 @@ + + + + + GIF and Image Search on Android + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

GIF and Image Search on Android

+ +
+ +
+ +

One of the best beloved features of our iOS app finally comes to Telegram for Android. You can now easily search the web for GIFs and images and send them to your friends.

+

To do this, simply open the Gallery attachment menu — you will find the new Search Web and Search GIF tabs at the top.

+
+ + + + + + +
+
+ +

Your recent gifs and images will be saved, so you can send them again with just a few taps. This is very useful when you're out of words and emoji are just not enough.

+

+ +

Stay tuned for more updates this year!

+

December 20,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-streaming.html b/data/telegram.org/blog/android-streaming.html new file mode 100644 index 0000000000..627aecfa9b --- /dev/null +++ b/data/telegram.org/blog/android-streaming.html @@ -0,0 +1,241 @@ + + + + + Streaming and Auto-Night Mode on Android + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Streaming and Auto-Night Mode on Android

+ +
+ +
+ +
+ +
+ +

Today's 4.8 update to Telegram for Android introduces video streaming. You can now start watching videos right away – without having to fully download them first.

+
+ +

Streaming-ready video in a chat

+
+ +

All videos newly uploaded from official Telegram apps can be streamed with version 4.8. You can see the caching progress as a light grey strip:

+
+ +

Streaming in progress

+
+ +

Auto-Night Mode

+

As of this update, Telegram for Android can automatically switch to the dark version of the interface after nightfall or in low-light conditions. To set up Auto-Night Mode, go to Settings > Theme > Auto-Night Mode.

+
+ +

Auto-night mode settings

+
+ +

Telegram for Android supports a multitude of custom themes, so you can choose which theme the app will switch to using the ‘Preferred Night Theme’ setting.

+

Сonnected websites

+

We're also launching a Telegram Login Widget today. Version 4.8 includes a ‘Logged in with Telegram’ section in the Privacy & Security settings that lists all the websites you are logged in to via Telegram.

+
+

Read more about the Telegram Login Widget

+
+

All these features are also coming to iOS, so stay tuned for our next updates.

+

+ +

February 6, 2018,
The Telegram Team

+

P.S.

+

Don‘t miss the other updates we’ve launched in the last few days:

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-themes.html b/data/telegram.org/blog/android-themes.html new file mode 100644 index 0000000000..0f0410c4ab --- /dev/null +++ b/data/telegram.org/blog/android-themes.html @@ -0,0 +1,246 @@ + + + + + Custom Themes + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Custom Themes

+ +
+ +
+ +
+ +
+ +

We believe in freedom. This is why Telegram is a free and open platform – for stickers, for bots, and even for third-party client apps. We believe that if we give you freedom, you’ll know what to do with it.

+

Starting today, 85% of Telegram users can completely change what Telegram looks like for them. We are rolling out Custom Themes on Android, and will later support them on less popular platforms.

+

To switch to a different theme or create a new one, go to Settings > Theme. We‘ve included a Dark Theme in that menu for those of you who don’t want to use Telegram as a flashlight in dark places.

+
+
+ +

The new dark theme

+
+
+ +

Easy on the eyes

+
+ +

Create Your Own

+

We've also added a Theme Editor to the app. You can now create new themes and easily share them with other users.

+
+
+ +

Choose an element

+
+
+ +

Pick a color

+
+ +

Just like stickers and bots, Telegram themes are part of an open platform, so anybody can create a theme and dazzle the world with new colors and backgrounds. Here's another example of a theme created by our users:

+
+
+ +

Theme preview: Chats list

+
+
+ +

Chat screen

+
+ +

Check out the @AndroidThemes and Desktop Themes channels for more new themes made by Telegram users.

+

If you're using our iOS app, hold on for a couple of weeks. You‘ll get themes eventually, but for now we’re building something different for you – and it’s truly epic.

+

+ +

February 20, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/android-wear-2-0.html b/data/telegram.org/blog/android-wear-2-0.html new file mode 100644 index 0000000000..68abc7173b --- /dev/null +++ b/data/telegram.org/blog/android-wear-2-0.html @@ -0,0 +1,224 @@ + + + + + Telegram for Android Wear 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram for Android Wear 2.0

+ +
+ +
+ +
+ +
+ +

Google has just unveiled Android Wear 2.0, the latest in smartwatch platforms. It supports standalone apps, so today we're releasing Telegram for Android Wear 2.0. It‘s everything you’d want from a perfect watch app — compact, beautiful, and super-fast.

+
+ +
+ +

Using this tiny yet powerful app, you can browse your chats and quickly reply to messages with voice, text, emoji, or stickers. You can also view your contacts and even create groups right from your watch.

+
+
+ +
+
+ +

The smartwatch app also supports several themes in different colors. By the way, theme support is coming to our main Android app soon, so stay tuned.

+

Telegram for Android Wear 2.0 is available for download on Google Play. If you have Android Wear 2.0 installed on your watch, just search for Telegram in the store.

+

+ +

February 9, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/animated-backgrounds.html b/data/telegram.org/blog/animated-backgrounds.html new file mode 100644 index 0000000000..13126f2520 --- /dev/null +++ b/data/telegram.org/blog/animated-backgrounds.html @@ -0,0 +1,302 @@ + + + + + Animated Backgrounds + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Animated Backgrounds

+ +
+
+
+ +
+ Introducing animated backgrounds and more +
+ +

In addition to Group Video Calls, this update adds animated backgrounds and message sending animations, as well as a new menu button for bots, new ways to import stickers, reminders to help keep your account safe, and more.

+

Animated Backgrounds

+

Meet animated backgrounds for chats – first time in a messaging app! These multi-color gradient wallpapers are generated algorithmically and move beautifully every time you send a message.

+
+ +
+ +

Our designers added these smooth, energy-efficient animations to all default themes.

+
+

You can find more animated backgrounds in Settings. Android: Chat Settings > Change Chat Background. iOS: Appearance > Chat Background.

+
+

Creating & Sharing Backgrounds

+

In case the default options are not enough, it's super-easy to create your own animated backgrounds. Choose three or four colors to unlock the animation, then add an optional pattern for extra style.

+
+ +
+ +

When ready, share your animated wallpapers with friends and family to upgrade them to a new level of messaging experience.

+

Message Sending Animations

+

Stickers and emoji now seamlessly hop from your keyboard into the chat – with lightweight animations that won’t affect your battery.

+

On iOS, this also applies to media you send from the attachment panel, and even text messages. Your input text smoothly transforms into the message bubble as it flies into the chat.

+
+ +
+ +

iOS: Semi-Transparency & New App Icons

+

On iOS, backgrounds are now partially visible through the header and the footer in chats, giving the interface a classy new look.

+

Two new gradient app icons are available in Settings > Appearance in addition to the classic blue and black versions:

+
+ Two new app icons on iOS +
+ +

We also added a Telegram Features button at the bottom of the Settings menu on iOS, which opens the Telegram Tips channel. Tips are available in 10 languages, including the newly added Turkish version.

+
+

The same button was already on Android, you can find it in the side menu.

+
+

Login Info Reminders

+

It is essential to keep your Telegram phone number up to date to ensure you can always log in to your account. If your phone number has changed, you can quickly update it right from the new reminder in Settings on iOS.

+
+ Reminder about keeping your phone number up to date +
+ +

Android users will get these reminders in the next update, for now they can simply update their phone number by tapping on it in Settings.

+ + +

Users on all platforms will receive a notification from Telegram each time their Two-Step Verification settings are changed.

+
+

Two-Step Verification on Telegram lets you set up an additional password, which you will need to enter every time you log in to your account.

+
+

Bot Menu

+

We made it easier to communicate with bots, adding a special menu button that lets you browse and send commands. Bots can also change the placeholder in the input field to give you a better idea of what kind of message they are expecting.

+
+ +
+ +
+

Bot developers can now create commands that change based on a user’s interface language and chat type, as well as special commands that only appear in specific chats or for admins.

+

More info is available in the Bot API documentation.

+
+

Importing Stickers

+

The @stickers bot can help you create new sticker packs as well as get usage stats for your stickers.

+

Today we're giving third-party developers the tools to make apps that help people generate new custom unique stickers and import their creations to Telegram in one tap.

+
+ +
+ +
+

If you are a developer interested in making apps that help users create stickers and publish them on Telegram, check out the new Sticker Importing Manual.

+
+

Remember, if you simply want Telegram users to install the stickers you made, you don't need any apps! Just upload your stickers using our bot, then share the link to your pack with others.

+

New animated emoji

+

This update is all about motion, so we couldn't go without new animated emoji. As always, simply send a message with a single emoji to get one of these in a chat:

+
+ +
+ +

Time to try out the new features — while we get back to building more of what you asked for, plus a few surprises we have in mind. Stay tuned.

+
+

Read on to learn about Group Video Calls, if you haven't already.

+
+

+ +

June 25, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/animated-stickers.html b/data/telegram.org/blog/animated-stickers.html new file mode 100644 index 0000000000..07eafcd86b --- /dev/null +++ b/data/telegram.org/blog/animated-stickers.html @@ -0,0 +1,261 @@ + + + + + Animated Stickers Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Animated Stickers Done Right

+ +
+ +
+ +
+ Cover Image +
+ +

We launched stickers back in January 2015. Since then, the Telegram sticker format has been adopted by other apps to reach a total of 2 billion people. Today we're introducing a new format for animated stickers.

+

We asked ourselves: Can animated stickers have higher quality than static ones while taking less bandwidth? The answer turned out to be YES (but only after we told developers they'd get moving cat pictures).

+
+ +
+ + + +

Smooth Animations, Tiny Size

+

Telegram engineers experimented with vector graphics, packaging methods and forbidden magic to create the Lottie-based .TGS format, in which each sticker takes up about 20-30 Kilobytessix times smaller than the average photo.

+

Thanks to various optimizations, animated stickers consume less battery than GIFs and run at a smooth 60 frames per second. If a picture is worth a thousand words, that's 180,000 words per sticker.

+
+ +
+ + + +

Open Platform

+

Naturally, animated stickers are a free platform. All artists are welcome to create new sets and share them with Telegram users.

+

Like its static predecessor, the Telegram animated sticker format is likely to become the new industry standard in messaging. Check out this quick guide to get started.

+
+ +
+ +

Starter Packs

+
+ +To get your conversations moving right away, our artists have created a few sample sets ranging from Rambunctious Rodents to Sentient Snacks. You can find more animated sticker sets in the 'Trending' section of your sticker panel. 🔥 + +

+ +

As always, the fastest way to find a sticker that fits your mood is to type in a relevant emoji – Telegram will immediately suggest matching stickers.

+
+ +
+ +

Keep an eye out for new animated stickers – and our next update.

+

+ +

July 6, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/apple-watch.html b/data/telegram.org/blog/apple-watch.html new file mode 100644 index 0000000000..1572cb68d5 --- /dev/null +++ b/data/telegram.org/blog/apple-watch.html @@ -0,0 +1,225 @@ + + + + + Telegram on Apple Watch + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram on Apple Watch

+ +
+ +
+ +
+

Telegram for iOS reaches version 3.0 today, packed with the Bot Platform, dedicated sticker tabs and our first take on Apple Watch support.

+
+

Finally! Telegram 3.0 arrived with full Apple Watch support. You can view your recent chats and reply to messages with stickers, locations, emoji, preset phrases or dictated text. You can also view user and group profiles, start new chats, and even block users.

+
+ + + + +
+
+ +

Chats on your Apple Watch will show all the content available on Telegram: photos, stickers, locations, documents and videos. For those cases when the watch can‘t handle something, we’ve added a shortcut to easily open any message on your Phone.

+
+ + + + +
+ +

We've made sure that Telegram on Apple Watch does as much as the platform can support right now — and that it does more than any other messaging app out there.

+

+ +

The Telegram Team,
June 24, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/autodelete-inv2.html b/data/telegram.org/blog/autodelete-inv2.html new file mode 100644 index 0000000000..bb7290b577 --- /dev/null +++ b/data/telegram.org/blog/autodelete-inv2.html @@ -0,0 +1,299 @@ + + + + + Auto-Delete, Widgets and Expiring Invite Links + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Auto-Delete, Widgets and Expiring Invite Links

+ +
+
+
+ +
+ Auto-Delete, Widgets and Expiring Invite Links +
+ +

This update brings an auto-delete timer for messages in any chat, as well as new flexible invite links and faster access to your chats with home screen widgets. Also, groups can now have unlimited members.

+

Auto-Delete Messages

+

Some conversations aren't meant to last forever, which is why Telegram users can delete messages for all participants in a conversation at any time, without a trace. Since 2013, users can also set a self-destruct timer for messages in Secret Chats.

+

Starting today, you can enable an auto-delete timer in all Telegram chats, which will automatically erase messages for all participants either 24 hours or 7 days after sending.

+
+ +
+ +

Auto-delete only applies to messages sent after the timer is set, earlier messages will stay in the chat history. Unlike in Secret Chats, the countdown starts when messages are sent, not read.

+
+

To enable the timer on Android, tap ⋮ > Clear History then choose a duration.
On iOS, press and hold a message, tap Select > Clear Chat (top-left) > Enable Auto-Delete.

+
+

All messages show a countdown to their deletion time – simply tap on Android or press and hold on iOS to take a look. 🕵️

+
+ Time before expiry +
+ +

In groups and channels, only admins can enable or modify the timer.

+

Home Screen Widgets

+

For instant access to your most important chats, add a Telegram widget to your home screen. The Chat Widget shows a preview of recent messages, while the Shortcut Widget shows only names and profile pictures.

+
+ +
+ +

On Android, chats and messages in the widget will always be up to date, and you can further expand the widget to take up more of your screen. On iOS, widgets will only get fresh data occasionally and can't be expanded – this is due to system limitations.

+
+

To add a widget, press and hold on your home screen, then tap Widgets on Android or the (+) on iOS and search for Telegram.

+
+

Expiring Invite Links

+

Invite links are a quick and easy way to bring 1 or 1 million people to your groups and channels. Along with the main invite link, owners and admins can now create additional links with a limited duration, number of uses, or both.

+
+ +
+ +

Any invite link can be converted into a scannable QR Code to put on everything from brochures to billboards. You can also see which users joined using each invite link to find out where new members came from or which format has been most effective for growth. 🚀

+
+ +
+ +
+

To view and manage invite links, tap to open your Group or Channel's Profile > Edit > Invite Links. Tap (⋮) or (⋯) to convert a link to a QR Code.

+
+

Groups with Unlimited Members

+

Telegram groups allow up to 200,000 members to exchange messages, media and stickers. Groups that are close to the limit can now convert into Broadcast Groups that allow unlimited members.

+

Converting to a Broadcast Group makes it so that only admins can send messages, but members can still join voice chats.

+
+ +
+ +

Broadcast Groups are ideal for large communities, where people can follow along and catch exclusive interviews, news, or just casual talks.

+

Improved Chat Import

+

Our developers are continuing to refine and expand the chat import feature added to Telegram last month. With today’s update, imported messages will now appear sorted by their original date if added to a Telegram chat that is new or has fewer than 1000 messages.

+
+ +
+ +
+

Sorting by original date is currently available when importing to all one-on-one chats, all newly created groups, and smaller existing groups.

+
+

Improved Reporting System

+

Telegram processes millions of user reports each month to make sure the platform is not abused. To help make this more efficient, we will now always ask you to select specific messages when sending a report.

+

Additionally, all reporting options allow you to add a comment to give more context – like when reporting fake accounts.

+
+ +
+ +

And More Animated Emoji

+

A new update always means new animations, so test out the new characters below by sending a single emoji in any chat.

+
+ +
+ +

That's all for today's changes, this message will now delete in 3, 2, 1 … oh. Never mind, this is a blog post, they don't do that yet. 😅

+

+ +

February 23, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/autoplay.html b/data/telegram.org/blog/autoplay.html new file mode 100644 index 0000000000..a10ca780f0 --- /dev/null +++ b/data/telegram.org/blog/autoplay.html @@ -0,0 +1,245 @@ + + + + + Autoplaying Videos, Automatic Downloads and Multiple Accounts + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Autoplaying Videos, Automatic Downloads and Multiple Accounts

+ +
+ +
+ +
+ Autoplaying Videos and New Automatic Download Settings +
+ +

Today's update will make Telegram chats livelier with Autoplaying Videos. Smaller videos will start playing without sound when they reach your screen. To unmute them, simply press the volume buttons on your device.

+
+ +
+ +

If you like to be in control of your data usage, try the new auto-download settings. It‘s easy to see your current settings at a glance and we’ve added a new quick way to switch between Low, Medium and High presets for Mobile, Roaming and Wi-Fi.

+

You can also manually set up automatic downloads by chat type, media type and file size. The app will remember your choices as the Custom preset in case you need to temporarily switch to Low and back — or the other way around.

+

To Each According to Their Needs

+

Default settings for data usage have become more generous but depend on the affordability of mobile data in your country. We know that in some places it's easier to buy an aircraft carrier than download an extra 20MB (looking at you, Ethiopia). Telegram will try to download less data for users in such countries.

+

On the other hand, if you're likely to have a monster data allowance, Telegram will try to save you from tapping the “download” arrow too often.

+

These new default limits for automatic downloads are not set in stone. Starting today, we can change them remotely, based on your feedback and the cost of data in each country.

+

To Log Out or Not to Log Out?

+

New users often bring their logout habits from other apps and don't realize that this is rarely necessary on Telegram. To help them find their way around the app, the logout menu now shows several alternative options to logging out:

+
+ Logout Alternatives +

Logout Alternatives

+
+ + +

Multiple Account Support

+

Some of us have several phone numbers and multiple Telegram accounts: one for work, another strictly personal and a third one provided by benevolent aliens along with instructions to never use it except in a planetary emergency.

+

You can add all these accounts to your app and easily switch between up to 3 phone numbers without logging out.

+
+ Add account +

Add Account in Settings > Edit

+
+ +

If you've added several accounts, you will receive push notifications for all of them. Notifications will include information on which account they were sent to. You can also tap and hold on an account in Settings for a sneak peek of its chats list:

+
+ +
+ +

The multiple accounts feature was born in Telegram for Android and is now also available on iOS. We hope your alter-egos will be pleased.

+

+ +

February 26, 2019,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/backgrounds-2-0.html b/data/telegram.org/blog/backgrounds-2-0.html new file mode 100644 index 0000000000..d84f3ba709 --- /dev/null +++ b/data/telegram.org/blog/backgrounds-2-0.html @@ -0,0 +1,231 @@ + + + + + Chat Backgrounds 2.0: Make Your Own + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Backgrounds 2.0: Make Your Own

+ +
+ +
+ +
+ Telegram 5.3: Introducing the Backgrounds Platform +
+ +

No chat can be dull if you have a really cool chat background. Today's update will ensure you get one. You can now search the web for wallpapers, add effects and then share your backgrounds with friends via links.

+

Telegram backgrounds now support motion and blur effects. You can also set any color as your background, apply a pattern and tweak its intensity.

+
+ +
+ +

Just like before, you can set any photo from your gallery as your chat background. On Android, you can add some extra effects in the built-in photo editor.

+

Share links

+

Having used this new arsenal to create the perfect chat background, you can easily set it to Telegram on all your other devices. What's more, you can infect the rest of the world with your genius by sharing your background via a link, just like this one:
https://t.me/bg/l7jg-vpxmEYBAAAA1e0rNKySlkk

+
+ Message containning a Telegram background +
+ +

Search backgrounds

+

If you don‘t feel very creative and would like to simply set something nice real quick, we’ve added new backgrounds to the official selection.

+

We've also included a background search option. Find your dream wallpaper based on keywords or color and then set it in just a few taps.

+
+ Background Search Results +
+ +

We're also announcing the Instant View 2.0 Template Competition: two months, $300,000+ in prizes, $100 per template. See Instant View Contest 2.0 for details.

+

+ +

January 31, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/bot-revolution.html b/data/telegram.org/blog/bot-revolution.html new file mode 100644 index 0000000000..181e96e086 --- /dev/null +++ b/data/telegram.org/blog/bot-revolution.html @@ -0,0 +1,279 @@ + + + + + Telegram Bot Platform + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Bot Platform

+ +
+ +
+ +
+

UPD: Check out the new Inline bots as well!

+
+

Telegram is about freedom and openness – our code is open for everyone, as is our API. Today we’re making another step towards openness by launching a Bot API and platform for third-party developers to create bots.

+

Bots are simply Telegram accounts operated by software – not people – and they'll often have AI features. They can do anything – teach, play, search, broadcast, remind, connect, integrate with other services, or even pass commands to the Internet of Things.

+
+ + + +

+ +
+ + +

Today’s 3.0 update to the Telegram apps makes interacting with bots super-easy. In most cases you won’t even have to type anything, because bots will provide you with a set of custom buttons.

+
+

"Every application needs a slightly optimized set of buttons, just for it.
Steve Jobs, 2007 iPhone launch

+
+

Bots can now provide you with custom keyboards for specialized tasks that could look like this for example:

+
+ + + +
+ +

+ +

Here are some sample bots that were built by the platform's beta testers this past weekend:

+
    +
  • @ImageBot – send this bot a keyword and it’ll provide you with a relevant picture.
  • +
  • @TriviaBot – test your trivia knowledge or add to groups to compete with friends.
  • +
  • @PollBot – add this one to group chats to create polls.
  • +
  • @RateStickerBot – discover and rate new stickers.
  • +
  • @AlertBot – set a time and this bot will send you a reminder for anything you like.
  • +
  • @HotOrBot – find friends with this Tinder-like dating bot.
  • +
  • @GithubBot – track GitHub updates.
  • +
  • @StoreBot – find new bots and rate them.
  • +
+
+ +
+ +

Our beta testers needed only a few hours to build these bots – setting up a new bot is a breeze. Just generate a key with @BotFather and use a simple https API to control your bot. If you’re an engineer, check out our Introduction to bots for details.

+

Bots in Telegram will look different from human users: their chat and profile screens have a slightly different UI and they don't have access to all messages by default when added to groups.

+

Taking over the world

+

Once you've launched your bot, watch it spread. In Telegram, any forwarded message contains a link to its original sender. This means any message from your bot forwarded to a person or group is a messaging equivalent of a retweet – bots are viral.

+

Additionally, all bots have an Add To Group and a Share button in their profile. You can set up a description and link that will be used when people share your bot on Telegram or other platforms.

+
+ + + + + + +
+ +

+ +

A typical link to a bot looks like this:

+
+

https://telegram.me/your_bot

+
+

Opening such a link starts a chat with that bot if you have Telegram installed. These links are easy to identify because all bot usernames must end in bot.

+

If the bot developer wants to pass their bot some additional info (like an auth key for example, see deep linking), the link might also look like this:

+
+

https://telegram.me/your_bot?start=value

+
+

The bots are coming

+

Starting today, you'll see links like this in Telegram and elsewhere. Embrace them, they are bots! They will provide the services you asked us for – polls, news, games, integrations, e-butlers or cat images. Any dream can come true with bots.

+

+ +

The Telegram Team,
June 24, 2015

+

+ +

P.S. All bot developers are welcome to share ideas for our Bot API on @BotSupport.

+
+

You can read more about the our bot platform in the Introduction to Bots and in the Bot API Manual.

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/bots-2-0.html b/data/telegram.org/blog/bots-2-0.html new file mode 100644 index 0000000000..8450c72736 --- /dev/null +++ b/data/telegram.org/blog/bots-2-0.html @@ -0,0 +1,260 @@ + + + + + Bot Platform 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Bot Platform 2.0

+ +
+ +
+ +

At Telegram, we made it our mission to redefine the boundaries of what you can do with your messaging app. Last year we launched the Bot Platform that has unleashed the creativity of thousands of developers.

+

Today we are giving bot developers a whole new dimension with Bots 2.0: inline keyboards, callback and URL buttons, location permissions and on-the-fly message editing. The new bots can also generate any type of content for you to share with friends, including documents, MP3s, videos, stickers, animations and contacts.

+

To give you a taste of the new possibilities, we built some sample bots last weekend – @music, @youtube, @foursquare and @sticker (make sure your Telegram app was updated today before you try them).

+

New Keyboards, New Actions

+

Here's how @music works – it uses an inline keyboard that allows you to interact with it without sending any messages. And it updates its own messages on the fly as you flip through the pages of search results:

+
+
+ +
+
+ +

New Types of Content

+

The @music bot also works in inline mode, which means it can help you send MP3s to any of your chats, right from the input field:

+
+
+ +
+
+ +

Inline bots can now send all types of attachments that are available on Telegram. We suspect you're going to like the @sticker inline bot – it can find you relevant stickers based on emoji.

+

New Mechanics

+

Like the @music bot, @youtube also works in two modes. It uses the new clever chat switching mechanic to connect your Telegram account with YouTube:

+
+
+ +
+
+ +

Once a Youtube account is connected, you can access additional settings via the new menu option above the results.

+

New Permissions

+

Now, @foursquare is an inline bot that utilizes our new location features and helps you send addresses of places and venues nearby. Note how it asks for permission to use your location when you try to send something for the first time:

+
+
+ +
+
+ + +

New Horizons

+

These sample bots are but the beginning. Our Bot API 2.0 allows developers to create fluid and easy-to-use interfaces for powerful bots. And we will be seeing a lot of new ones in the coming months, after all, 2016 is the year of bots.

+

If you are a developer, take a look at our Introduction to Bots 2.0 and read the full changelog. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

+

If you are a user, hang on – soon you will have plenty of cool bots to play with. Meanwhile, enjoy the sample bots!

+

+ + +
+

Oh. And we almost forgot we've got more new stuff today!
Read on about Sharing and Previews »

+
+

+ +

April 12, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/cache-and-stickers.html b/data/telegram.org/blog/cache-and-stickers.html new file mode 100644 index 0000000000..2dfdf95a3c --- /dev/null +++ b/data/telegram.org/blog/cache-and-stickers.html @@ -0,0 +1,231 @@ + + + + + Clearing Cache and Reordering Stickers + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Clearing Cache and Reordering Stickers

+ +
+ +
+ +

Unlike most messengers, Telegram can take up nearly zero space on your phone, even if you‘re using it heavily. When you remove Telegram data from your device’s local cache to free up space, we'll keep it in the cloud for as long as you need, with virtually no limitations.

+

Today we are introducing new cache management options that make it even easier to maintain Telegram’s slender footprint when space is short — without having to sacrifice useful data. The new Clear Cache option allows you to quickly delete cached media by type.

+
+ + + +

+
+ +

Using the Keep Media setting, you can control how long unused media stays on your device. If you haven't accessed a file for the specified time, it is automatically deleted from the cache. Naturally, your data will instantly re-download from the cloud the moment you access it again.

+

On iOS it is also possible to clear cached files on a chat-by-chat basis. On Android, this currently works with supergroups and channels (just tap and hold in the chats list, then ‘Delete from Cache’).

+
+ +

+
+ +

Available on iOS and Android (and coming to WindowsPhone soon), these simple settings help ensure that Telegram will only require the least amount of space on your devices.

+

Reorder Sticker Packs

+

We've also improved the ordering of sticker packs. You can now manually arrange your sticker packs in the order you prefer, and the order will be synced across your devices. Access sticker settings via the new button, right on the sticker panel.

+
+ + +

+
+ +

We're not done for 2015 yet, so watch out for more updates this year.

+

+ + +

December 8, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/calls.html b/data/telegram.org/blog/calls.html new file mode 100644 index 0000000000..bcc00b60f9 --- /dev/null +++ b/data/telegram.org/blog/calls.html @@ -0,0 +1,266 @@ + + + + + Voice Calls: Secure, Crystal-Clear, AI-Powered + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Calls: Secure, Crystal-Clear, AI-Powered

+ +
+ +
+ +
+ +
+ +
+

UPD, August 2020: Telegram also supports end-to-end encrypted video calls.

+

UPD, December 2020: You can start a voice chat with thousands of participants in any group.

+
+

Over the past few months, we’ve worked hard to make sure Telegram calls are the best in terms of quality, speed, and security. The wait is over: today Voice Calls are available all over the world in our mobile and desktop apps.

+

The Voice Call interface is familiar and easy to use, but as always, you get loads of innovation under the hood with Telegram.

+
+ +
+ +

Secure

+

Telegram Calls are built upon the time-tested end-to-end encryption of Telegram's Secret Chats. The key verification UI we came up with in 2013 to protect against man-in-the-middle attacks served well for Telegram (and for other apps that adopted it), but for Calls we needed something easier.

+

That's why we've improved the key exchange mechanism. To make sure your call is 100% secure, you and your recipient just need to compare four emoji over the phone. No lengthy codes or complicated pictures!

+
+ +

Key verification

+
+ +

Super-Fast

+

Whenever possible, your calls will go over a peer-to-peer connection, using the best audio codecs to save traffic while providing crystal-clear quality.

+

If a peer-to-peer connection can't be established, Telegram will use the closest server to you to connect you with the person you’re calling in the fastest way possible. Unlike other apps, Telegram has a distributed infrastructure all over the world which we’ve already been using to deliver your texts faster than other apps. Now these servers will also be used for calls.

+

In the coming months, we’ll be expanding our content delivery network around the globe, getting the connection up to light-speed even in remote areas.

+

AI-Powered

+

Each time you make a Voice Call on Telegram, a neural network learns from your and your device's feedback (naturally, it doesn't have access to the contents of the conversation, it has only technical information such as network speed, ping times, packet loss percentage, etc.). The machine optimizes dozens of parameters based on this input, improving the quality of future calls on the given device and network.

+

These parameters can also be adjusted during a conversation if there's a change in your connection. Telegram will adapt and provide excellent sound quality on stable WiFi — or use less data when you walk into a refrigerator with bad reception.

+

According to our tests, Telegram Calls are already superior to any of our competitors on comparable connections. But the quality of Telegram Calls will further improve as you and others use them, thanks to the built-in machine learning.

+

Complete Control

+

If you’re like us, you don’t like to be bothered. On Telegram, you can control who can and who can't call you with granular precision. You can even switch voice calls off altogether, blocking anyone and everyone from calling you.

+
+ +

Privacy settings for calls

+ +

By default, Telegram calls are lightweight and automatically adapt to the speed and type of your connection, so as to consume the least data possible. But if you want to reduce your data spending by another 25-30% at the expense of sound quality, you’re welcome to enable the Use Less Data option in Data and Storage Settings.

+

No Added Calories

+

Telegram is the most powerful messaging platform out there, but it is also famous for being the easiest one to use. We want to keep things this way, and that’s why by default we won’t clutter your screen with additional tabs and redundant buttons.

+

Once you start making calls, Telegram for iOS will offer you to add a dedicated tab for calls on the main screen of the app. Alternatively, you can turn the Calls tab on right away from the Recent Calls section in Settings. On Android, the call tab is accessible via the pull-out main menu on the left.

+

It's always easy to make a call, even if you've never opened the calls tab. As soon as Voice Calls are enabled for your country, a phone icon will appear on every profile page. You can also call by tapping the top bar in a chat and choosing 'Call' on iOS. On Android, the Call button is in the '…' menu at the top.

+
+ +

New call button

+
+ +

One more thing

+

For those of you who don’t do voice calls, v.3.18 brings something different: direct control over the quality of videos you share. Use this brand-new setting to select the degree of compression before sending a video. For the first time in the history of messaging, you can preview how the recipient will see your video before you send it.

+
+
+ +
+
+ +

The app will remember the compression rate you selected and will use it by default for your future video uploads.

+

+ +

And that's it for today. Stay tuned, there's always more coming!

+

+ +

March 30, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/captions-places.html b/data/telegram.org/blog/captions-places.html new file mode 100644 index 0000000000..c843fb55c1 --- /dev/null +++ b/data/telegram.org/blog/captions-places.html @@ -0,0 +1,244 @@ + + + + + Places, Captions and more + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Places, Captions and more

+ +
+ +
+ +

Today we are adding several long-awaited features in one epic update to our Android and iOS apps.

+

Places

+

When sharing a location, you can now choose venues and landmarks. And when viewing a location, you can get directions. The section was also beautifully redesigned.

+
+ + + +
+
+ +

Photo Captions

+

Another thing Telegram was lacking – captions for photos. You can now add them to any picture you send, just tap the T in the photo editing panel.

+
+ + + +
+
+ +

New Voice Messages

+

You can now see whether the recipient has listened to your voice message — and keep track of which ones you've listened to yourself. Voice messages that have not been played yet are now marked with a small dot.

+
+ +
+
+ +

Smart Notifications

+

Tired of buzzing notifications from active group chats? Sick of multiple notifications every time somebody forwards you a dozen messages? Getting notifications on mobile while chatting with the same person from your desktop? Fixed! Starting today, you will be notified only when it is necessary.

+

Rich link previews

+

As promised, link previews now work for almost any news site — in addition to previews for the most popular services like YouTube and Twitter.

+

Android Goodies

+

Telegram for Android joins the iOS app in showing extended ‘typing’ statuses: you can now see when your chat partner is sending you a photo or recording a voice message. Scrolling and photo animations have become smoother than ever.

+

Last but not least, we've fully redesigned the emoji menu on Android so that it now features a dedicated stickers tab. This is the first drumbeat of the stickers revolution that is coming to Telegram soon.

+
+ +
+
+ +

Invite Links for Groups

+

OK, this feature is so awesome that it deserves a separate post.

+

+ +

The Telegram Team,
April 30, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/channels-2-0.html b/data/telegram.org/blog/channels-2-0.html new file mode 100644 index 0000000000..d94037040c --- /dev/null +++ b/data/telegram.org/blog/channels-2-0.html @@ -0,0 +1,246 @@ + + + + + Channels 2.0 and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Channels 2.0 and More

+ +
+ +
+ +

Telegram channels are becoming a worldwide trend. Each day they get more than 400,000,000 views. Today we are introducing several features that will make channels and bots even more powerful tools for connecting with your audience.

+

Links to Posts

+

The Quick Share menu now allows you to copy links to individual messages inside a channel. You can send these links to friends outside of Telegram or post them to other social networks. Following such links will open the channel and highlight the message.

+
+ +

Copy Share Link

+
+ +

Silent Messages

+

“Is it OK to post now?” “Is this urgent enough to notify everyone?” If you're a channel admin, you know these questions too well. Luckily, you can now send silent messages that will not notify your subscribers. This is very useful for late night or non-urgent updates. Tap on the bell icon to toggle silent messages on and off.

+
+ +

Silent messages

+
+ +

Admin Signatures

+

There are times when it‘s important to know who posted a certain message. Starting today, you can enable signatures in Channel Info. New messages will be signed with the posting admin’s chosen screen name but will not link to their profile.

+
+
+ +

Channel Settings

+
+
+ +

Signed Messages

+
+ +

Edit Messages in Channels and Supergroups

+

Made a typo? Missed a word? Itching to add something? As of today, you can edit your messages after they were posted. Tap the message (double tap on iOS), then press ‘Edit’. This feature works with supergroups and channels because they both use the same underlying technology.

+

Quick Share Button for Bots

+

Many news organizations are building bots to provide tailored subscriptions. In this update we've made it easier to share the links, pictures and videos you get from bots. Check out the new official @forbesbot to see how this works.

+
+ +

Quick Share button for bots

+
+ +

Bonus: Sticker Previews

+

In other news, sticker previews now work everywhere including sticker suggestions when you type an emoji and the ‘Add stickers’ screen. Tap and hold on a sticker to see it in full size before sending. The devil's in the details, right?

+

Try it out with the Harry set: https://telegram.me/addstickers/harry

+

+ +

And that‘s all we’ve got for you this month.
Stay tuned for more updates in March!

+

+ +

February 24, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/channels.html b/data/telegram.org/blog/channels.html new file mode 100644 index 0000000000..2d8ac564e9 --- /dev/null +++ b/data/telegram.org/blog/channels.html @@ -0,0 +1,224 @@ + + + + + Channels: Broadcasting Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Channels: Broadcasting Done Right

+ +
+ +
+ +
+

UPD: See Channels 2.0 for info on links to posts, silent messages and admin signatures.

+
+

Today we are introducing Channels, a new tool for broadcasting your messages to large audiences. Channels replace the old Broadcast lists and are better in every way. They can have an unlimited number of members, they can be public with a permanent URL and each post in a channel has its own view counter.

+
+ +

+
+ +

Views from forwarded copies of your messages will be included in the total count. Last but not least, new members can see the entire message history in a channel once they join — all the way to day one.

+

If you'd like an example, join our official Telegram channel to get notified about our updates, or try creating your own channels from the ‘New Message’ menu.

+

iOS 9 Notifications

+

In other good news, we‘ve added Quick Replies from notifications, which are now supported on iOS 9 devices. This means you can reply to messages in Telegram, directly from your iPhone’s lock screen. Split View and more iOS 9 features will become available in early October.

+

Unfortunately, due to a bug in iOS 9, it is currently not possible to display the input field for Quick Replies right away — you‘ll need to press the ’Reply' button in order for it to appear. Quick replies will work as expected when iOS 9.1 is released with the relevant bugfixes.

+

Photo Editor

+

The in-app Photo Editor for iOS was updated with tools to adjust an image's tint, fade, and curves. The existing shadows and highlights tools default to 50% and are now functional in both directions.

+
+ + +

+
+ +

September 22, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html new file mode 100644 index 0000000000..4a6b82ce4d --- /dev/null +++ b/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html @@ -0,0 +1,297 @@ + + + + + Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

+ +
+
+
+ + +
+ Introducing Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording +
+ +

Today's update lets you set different themes for individual chats, share your feelings with loved ones using interactive emoji with fullscreen effects, see detailed read receipts in groups and record video and audio from live broadcasts.

+

Chat Themes

+

Telegram has dozens of features to organize your chats and customize their appearance, from Chat Folders to Animated Backgrounds. In this update, coordination and decoration come together with new themes for individual chats.

+

Our designers created 8 new themes that you can apply to specific private chats. Each of the new themes features colorful gradient message bubbles, beautifully animated backgrounds and unique background patterns.

+
+ +
+ +

Both you and your chat partner can choose the theme for both sides and make any conversation easy to recognize, even when you can't find your glasses. This way you can set different themes for chats with co-workers and family members, so you won't accidentally send that video to your boss again.

+
+

To set a theme for your chat on Android, tap ⋮ > Change Colors. On iOS, tap the Chat Header > ⋯ > Change Colors. Your chat partner will see the theme if they are using the latest version of Telegram.

+
+

Each theme comes with a day and night version and will follow your app's night mode settings – whether you keep it dark all day, or have your chats follow the sun.

+

These first 8 themes are just the beginning – our designers are already working on adding more.

+

Interactive Emoji

+

We love animating emoji, but there are times when even a big red beating heart – that makes your phone vibrate with each beat! – is simply not enough to express your feelings.

+

With a little code, a little drawing and a lot of dark magic, we've created a new way of sharing emotion in real time. Send a single 🎆 🎉 🎈 👍 💩 or ❤️ to any private chat, then tap on the animated emoji to unleash a fullscreen effect.

+

If both you and your chat partner have the chat open, the animations and vibrations play simultaneously on your devices, so you feel close even when you're far apart.

+
+ +
+ +
+

Your chat partner will only see the effects if they are using the latest version of Telegram.

+
+

Our artists are already back in the dungeons, working on new fullscreen effects for more animated emoji.

+

Read Receipts in Small Groups

+

Both chat themes and interactive emoji currently only work in private chats. But this update also includes a big change for groups.

+

Group messages are marked as read (✓✓) as soon as one other member sees them. In small groups, you can now also select a message you sent to see which group members have read it.

+
+ +
+ +
+

To protect users' privacy, read receipts in groups are only stored for 7 days after the message was sent. It is not Telegram's business to keep a record of everything you've ever seen.

+
+

Record Live Streams and Video Chats

+

Telegram hosts millions of communities that can create live events for unlimited viewers. Whether it's a once-in-a-lifetime concert or an everyday algebra class, admins can now record Live Streams and Video Chats to publish them for those who missed the live version.

+ + +
+ +
+ +

Admins can start a recording right from the Live Stream or Video Chat menu – with options to record Video and Audio or Only Audio. To record video, choose an orientation for the final video file, Portrait or Landscape. After you finish recording or end the broadcast, the file is instantly uploaded to your Saved Messages.

+
+

Tap ⋮ or ⋯ to open the broadcast menu and start recording. While recording, a red dot appears next to the title of the broadcast.

+
+ + +

And that should give you enough things to do until we're back with the next update. As always, it shouldn't take us long.

+

+ +

September 19, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/contacts-local-groups.html b/data/telegram.org/blog/contacts-local-groups.html new file mode 100644 index 0000000000..1ab722b8ca --- /dev/null +++ b/data/telegram.org/blog/contacts-local-groups.html @@ -0,0 +1,272 @@ + + + + + Location-Based Chats, Adding Contacts Without Phone Numbers and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Location-Based Chats, Adding Contacts Without Phone Numbers and More

+ +
+ +
+ +
+ Telegram 5.8: Adding Contacts Without Phone Numbers, Location-Based Chats and More +
+ +

In the previous update, we improved privacy settings and added a way for you to control who can see your phone number. Today we're making it easier to exchange contact info on Telegram.

+

All new chats now have an Add to Contacts button at the top. This allows you to quickly add anyone who messages you to your Telegram contacts, even if you don't know their phone number yet.

+
+ Add/Block Buttons in a Chat +
+ +

If you'd prefer they disappeared instead, the Block button is right next door.

+

Add People Nearby

+

Ever scrambled for business cards at a beach party? Or dropped somebody's phone into the pool in a “let me type in my number for you” moment? Worry no more.

+

Simply open Contacts > Add People Nearby to quickly exchange contact info with Telegram users who are standing next to you (and also have this section open).

+
+ +
+ +

This feature comes in especially handy when several people meet to perform the take-my-number dance. Now you can catch all your pokémon in just a few taps.

+

Location-Based Chats

+

Speaking of pokémon, the new People Nearby section also shows Groups Nearby – location-based group chats open for anyone around to join.

+
+ +
+ +

Tap Create a Local Group to unite your dormitory or apartment building, and maybe you can get Todd in 2C to finally turn his music down.

+
+ Location-based group +
+ +

This update opens up a new world of location-based group chats for anything from conferences, to festivals, to stadiums, to campuses, to chatting with people hanging out in the same cafe.

+

Transfer Group Chats

+

If you ever get tired of being the host of your group, you can pass the burden on to another administrator. Telegram apps now support transferring ownership rights from any groups and channels to other users.

+

Grant full admin rights to your Chosen One to see the Transfer Ownership button.

+
+ Transfer group ownership +
+ +

Whether your watch has ended, or you have some business to attend to in King's Landing, passing the torch is a simple, two-tap affair.

+

Enhanced Notification Exceptions

+

Notification Exceptions just got more powerful. You can now toggle message previews for specific chats. If you have many exceptions, use Search to find the right chat — or ‘Delete All’ to get back to square one instantly.

+
+ Notification exceptions +
+ +

Siri Shortcuts

+

Owners of iOS devices can now use Siri shortcuts to open chats with people. No hands just got no-handsomer.

+
+ Siri +
+ +

Theme Picker and Icon style

+

We've also revamped the Appearance settings on iOS so that it's easier to see what the different themes will look like even before you apply them.

+
+ New theme picker on iOS +
+ +

A while back, the Telegram X app for iOS was promoted, becoming the official Telegram, and its previous shell was removed from the store. If you are still using it for some reason, this is a good time to switch — ol' Telegram X is now three versions behind the main branch.

+

Some users told us they didn't want to switch because they liked the Telegram X icon better. So this update adds a way for your iOS app icon to get back in black:

+
+ Pick your poison +
+ +

By the way, Telegram X for Android is still there and is not going anywhere for now. If you're looking for an alternative interface, feel free to give it a try.

+

+ +

June 23, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/coronavirus.html b/data/telegram.org/blog/coronavirus.html new file mode 100644 index 0000000000..9ffb9f4b8f --- /dev/null +++ b/data/telegram.org/blog/coronavirus.html @@ -0,0 +1,254 @@ + + + + + Coronavirus News and Verified Channels + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Coronavirus News and Verified Channels

+ +
+ +
+ +
+ Verified Channels and Coronavirus Info +
+ +

Telegram Channels are a powerful tool for broadcasting your messages to unlimited audiences. Since 2015, media organizations and public figures have been using them to reach readers, voters and fans – especially in countries where freedom of speech is limited.

+

Recently, we noticed a new type of channel gaining popularity: those created by Ministries of Health from around the world. India, Malaysia, Israel and many other countries now send news updates, warnings and tips via Telegram.

+
+ +
+ +
+

More about Channels and their features »

+
+

New Verification Tools

+

To help users distinguish trustworthy sources from fake news, we're launching a streamlined verification process today.

+

If you have verified accounts on other social media services, simply contact our new @VerifyBot to get a verification badge for your channel, group or bot.

+
+

More about Telegram Verification Guidelines »

+
+

Notifications for Users

+

Information is the most powerful weapon in the fight for global health – at least until we get a vaccine. To do our part, we've been sending notifications to all users in countries that have official channels with updates about the virus, offering them to join.

+

We invite all health officials to collaborate on keeping people informed. If you work for your country's Ministry of Health and would like to promote its channel, please verify it first using @VerifyBot, then contact us at corona@telegram.org.

+

Coronavirus Info

+

To make sure users find accurate and relevant information about the pandemic in their region, we've created a special channel which shows up as the top result for all coronavirus-related keywords in Search. It contains a list of official news sources by country:

+

+ +

Beyond Channels: Groups and Bots

+

Telegram Channels are good for massive one-way broadcasts, but if you're looking for more interactive ways to inform people, try groups or bots.

+

Telegram Groups can have up to 200,000 members each and offer powerful tools for maintaining order. For example, doctors from the Indian state of Karnataka are using this public group to answer questions from users.

+
+

More about Telegram Groups »

+
+

Telegram Bots are third-party apps that you can interact with right from your chat list. You talk to them using buttons – and they reply with messages and media of all kinds. Bots are extremely flexible and can be used for anything from providing information to integrating with other web services.

+

For example, check out @QuizBot which can create and run quizzes like this one.

+
+

More about Telegram Bots »

+
+

And One More Thing

+

We couldn't do anything about the shortage of masks in the real world, but our artists found a way to squeeze an inexhaustible supply into your app.

+

You can apply masks from this set to any pictures you send using Telegram's Photo Editor. Whether to raise awareness, maintain digital hygiene, or simply to hide your nose is up to you.

+
+ +
+ +

Stay home. Wash your hands. Be safe. And stay tuned for our next updates!

+

+ +

April 3, 2020,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/crowdsourcing-a-more-secure-future.html b/data/telegram.org/blog/crowdsourcing-a-more-secure-future.html new file mode 100644 index 0000000000..22264c5df6 --- /dev/null +++ b/data/telegram.org/blog/crowdsourcing-a-more-secure-future.html @@ -0,0 +1,212 @@ + + + + + Crowdsourcing a More Secure Future + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Crowdsourcing a More Secure Future

+ +
+ +
+ +

A few days ago we launched a contest to improve Telegram's security and are delighted to already have the first results. A Russian IT-community user identified a potentially vulnerable spot in our secret chat implementation. While this would not help him decipher the traffic and win the contest, his achievement deserves a notice — and a big prize.

+
+

The habrahabr user x7mz had discovered that in case the Telegram server could be seized by a malicious third party, it could send different nonce numbers to each of the clients participating in a secret chat.

+

These nonce numbers were introduced to add more randomness to the secret chat keys, mostly because of possible undiscovered vulnerabilities of the random generators on mobile devices (for example, one such vulnerability was found this August in android phones).

+

As was pointed out, this solution would have also made it possible for the visual representations of the shared secret key to be identical in case of a man-in-the-middle attack — provided such attack was done by the seized server. Obviously, the server has been under Telegram's control all this time, so this theoretical threat never had a chance to come to life.

+
+

The developer who found the potential weakness has earned a reward of $100,000. We have contacted him to find out how he would like to collect his prize.

+

A similar reward awaits anyone who finds viable ways of compromising MTProto’s security (and there is an outstanding reward of $200,000 for deciphering Telegram traffic). All submissions to security@telegram.org which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

+

This story showcases the importance of keeping the protocol specification and source code open — this way thousands of bright minds from all over the world can help us find potential vulnerabilities and improve the protocol.

+

Let’s keep on looking for any weak spots. Together we can make Telegram unbreakable.

+

December 21, 2013
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/cryptocontest-ends.html b/data/telegram.org/blog/cryptocontest-ends.html new file mode 100644 index 0000000000..5b08eb8485 --- /dev/null +++ b/data/telegram.org/blog/cryptocontest-ends.html @@ -0,0 +1,214 @@ + + + + + Crypto Contest Ends + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Crypto Contest Ends

+ +
+ +
+ +
+

This contest is over, but Telegram's bug bounty program is always open.

+

Security researchers are welcome to submit any issues they find in the Telegram apps or protocol to us at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

+
+

The current round of our contest to crack Telegram’s encryption ends with no winners. Despite the $300,000 bounty and the fact that contestants could act as the Telegram server passing info between the users (i.e. use any kinds of active attacks, manipulate traffic etc.) no one could decipher their Secret Chats by the beginning of February.

+

To demonstrate that the contest was fair, we‘ve added a decryption method to the contest bot’s list of commands – KEY. KEY returns the 256-byte encryption key used in the secret chat, so the task of the contest is now easily achieved.

+

Why are contests important?

+

One of the reasons we trust Telegram’s Secret Chats more than many of their alternatives, is that they're open to scrutiny from the world’s security experts. And while having open source apps and a well documented API makes this kind of scrutiny possible, it is our contests that create incentive for it.

+

That’s why we will definitely launch the next round of our contest later this year. It’ll take us some time to determine whether we can further simplify the task for the contestants. Once ready, we’ll announce the new round on Twitter.

+

Thank you for the vast amount of advice and comments you sent us during these last few months - your input allows us to improve Telegram with each new build.

+

+ +

February 11, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/cryptocontest.html b/data/telegram.org/blog/cryptocontest.html new file mode 100644 index 0000000000..7ca25a4dad --- /dev/null +++ b/data/telegram.org/blog/cryptocontest.html @@ -0,0 +1,224 @@ + + + + + $300,000 for Cracking Telegram Encryption + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

$300,000 for Cracking Telegram Encryption

+ +
+ +
+ +
+

This contest is over, but Telegram's bug bounty program is always open.

+

Security researchers are welcome to submit any issues they find in the Telegram apps or protocol to us at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

+
+

Earlier this year we had a contest to decipher intercepted Telegram messages, that did not produce a winner. Today we announce a new contest with an easier task and a larger prize — $300,000 for cracking Telegram's encryption, and this time contestants can not only monitor traffic, but also act as the Telegram server and use active attacks, which vastly increases their capabilities.

+

In this contest you assume the role of a malicious entity in full control of both the communication lines and the Telegram servers themselves.

+
+

UPD The current round of the contest is over. Go to results »

+
+

Your goal is to extract sensitive data (a secret email address) from a Secret Chat between two users — Nick and Paul. You control the entire process, from chat creation to the sending of each individual message and can perform various active attacks, including MITM, KPA, CPA, replay attacks, etc.

+

Contest Interface

+

In order to facilitate the task, we have created an interface, using which you can act as the server and determine which side gets what data. For more details, please check out the Cracking Contest Description.

+

Objectives

+

In order to confirm that Telegram crypto was indeed cracked and claim your $300,000, you‘ll need to send an email to the secret email address that you’ve extracted from one of the messages exchanged by Paul and Nick.

+

Your email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

+

There is also a bonus objective with an independent prize of $100,000.
See full description for details »

+

End Date

+

To prove that the competition was fair, we will add a command that returns the keys used for encryption as soon as a winner is announced. In case there is no winner by February 4, 2015, decryption commands will be added at that date.

+
+
+
+ +

November 4, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/desktop-1-0.html b/data/telegram.org/blog/desktop-1-0.html new file mode 100644 index 0000000000..9577f65739 --- /dev/null +++ b/data/telegram.org/blog/desktop-1-0.html @@ -0,0 +1,250 @@ + + + + + Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL

+ +
+ +
+ +
+ +
+ +

Telegram was available for desktops and laptops since 2013. Today it finally graduates to version 1.0 with a fabulous new design.

+

Consistent material design, great animations, and support for custom themes make Telegram for Windows, Mac, and Linux the tool for messaging from your Mac or PC.

+

This is what Telegram Desktop 1.0 looks like:

+
+
+ +

Login Screen

+
+
+ +

Your Chats

+
+
+ +

Smooth animations are now everywhere:

+
+ +
+ +

Custom Themes

+

If you're looking for an alternative design, Telegram Desktop also supports customized themes. Anyone can make a theme for Telegram Desktop. This theme, for example, changes green outgoing messages to blue:

+
+ +

Blue theme

+
+ +

And here’s a third-party night mode theme:

+
+ +

Dark theme

+
+ +

What Else Makes Telegram Desktop Cool?

+

The best thing about Telegram Desktop is that it automatically syncs messages from your phone with your computer using Telegram’s encrypted cloud. Just install it and log in to your account! All your messages, documents, photos and videos will be synced for you from the secure cloud.

+

Thanks to Cloud Drafts, you can even start typing on your phone, then continue on your desktop when you reach home or work.

+

Who needs email now? Telegram Desktop is many times faster and handles attachments like a pro. Just share your t.me/username with those who want to reach you.

+

+ +

January 11, 2017
The Telegram Team

+

+ +

P.S. For desktop experiences, we also have Telegram Web and Telegram Mac, but our founder insists that Telegram Desktop is the way to go on all platforms.

+

P.P.S. If you're looking for an easy way to get your emails right in Telegram, check out this Gmail bot. Helps one to stay in touch with those who insist on using antique methods of communication.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/desktop-compact.html b/data/telegram.org/blog/desktop-compact.html new file mode 100644 index 0000000000..9a9fe046b0 --- /dev/null +++ b/data/telegram.org/blog/desktop-compact.html @@ -0,0 +1,213 @@ + + + + + Telegram Desktop Adds Compact Mode + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Desktop Adds Compact Mode

+ +
+ +
+ +

The official Telegram app for Windows, OSX and Linux is now available in compact mode — you can resize the window so that only a single column remains. This makes it easier to use Telegram on smaller desktop or laptop screens.

+
+ + + +
+ +

You can download Telegram Desktop at desktop.telegram.org. As of last week, this app is also available in the Mac AppStore, alongside with our native OSX app.

+

To log in on your computer, simply enter your phone number and get a code delivered via Telegram to your phone. All your messages (except those from Secret Chats) are instantly synced between all your devices, so you can continue right where you left off.

+

+ +

December, 22
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/discover-stickers-and-more.html b/data/telegram.org/blog/discover-stickers-and-more.html new file mode 100644 index 0000000000..414cbe6cb5 --- /dev/null +++ b/data/telegram.org/blog/discover-stickers-and-more.html @@ -0,0 +1,246 @@ + + + + + Sticker Search, Multiple Photos, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Sticker Search, Multiple Photos, and More

+ +
+ +
+ +
+ +
+ +
+

In other news: Telegram has now reached 200 million monthly active users.

+
+

Today we're launching Telegram 4.8 for iOS and Telegram 4.8.5 for Android which make it much easier to discover new stickers. From now on, when you type one emoji, you will see suggestions not just from the sticker sets you've added, but also from other popular sets.

+
+ +

Suggested Stickers

+
+ +

Sticker Search

+

We've added search for sticker sets. Scroll up in the sticker panel to find the new search field that will help you find something quickly – be it a set you've added, or a brand new pack of easter bears.

+
+ +
+ +

Multi-Shot Sending

+

Need a couple of extra selfies to maximize dramatic effect? Dog can't stop doing adorable tricks? Not a problem. Use the new + button when taking a photo to take and send multiple media one after another.

+
+ +

Take & Send Multiple Photos

+
+ +

Auto-Night Mode and Connected Websites

+

Telegram for iOS v.4.8 also includes some of the goodies which Android users have been enjoying since the previous release. With Auto-Night Mode settings you can automatically switch to the dark version of the interface after nightfall or in low-light conditions:

+
+ +

Auto-Night Mode Settings on iOS

+
+ +

As of v.4.8, the iOS app also supports text formatting in media captions, reporting individual messages in public entities, and has a section where you can manage connected websites.

+

Oh, and we've optimized battery usage so that you can enjoy all of the above even longer on a single charge.

+

+ +

March 22, 2018,
The Telegram Team

+

+ +
+

P.S. In case you missed this, Telegram has now reached 200 million active users.

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/drafts.html b/data/telegram.org/blog/drafts.html new file mode 100644 index 0000000000..29a8f0741c --- /dev/null +++ b/data/telegram.org/blog/drafts.html @@ -0,0 +1,242 @@ + + + + + Drafts, Picture-in-Picture, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Drafts, Picture-in-Picture, and More

+ +
+ +
+ +

Telegram has replaced email for business communication for many of our users. But in a messenger, a lot of people are competing for your attention. Sometimes they interrupt you halfway through typing an important message, and you forget all about it. Good news! With our latest update, this is no longer a problem.

+

Today we're introducing Drafts. Unfinished messages are now clearly visible in the chats list, and the chat with an unsent draft will move to the top. What's more – all your drafts are now synced across all your devices. Now you can start typing on your phone, then continue on your computer – right where you left off.

+
+ +

Drafts in the chats list

+
+ +

Picture-in-Picture

+

On iOS, YouTube and Vimeo videos get a new button in the bottom right corner. Tap it to shrink the video and continue watching and listening while accomplishing other tasks.

+
+
+ +
+
+ +

You can drag the minimized video around the screen so that it doesn't get in the way. On iPads, videos in PiP mode will follow you around even if you switch to a different app. PiP will become available for all videos in Telegram in one of the next updates.

+

Internal Video Player for Android

+

Android users will enjoy the new built-in video player, available for Android 4.1+.

+
+ +

New built-in video player on Android

+
+ + +

…and more

+

On top of this, Telegram v.3.10 allows you to view the entire set of a group‘s profile pictures instead of just the latest one. The beautiful ’Scroll to bottom' button with an unread messages counter has made it to Android and Telegram Desktop.

+
+ +

New unread messages counters

+ + +

We've improved design across all of our apps. Telegram Desktop now sports nifty blue unread message counters, new buttons, and fully revamped profile pages.

+

+ +

We at Telegram are hard at work expanding the boundaries of what you can do with a messaging app. Stay tuned for more updates coming soon!

+

+ +

June 14, 2016
The Telegram Team +

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/edit.html b/data/telegram.org/blog/edit.html new file mode 100644 index 0000000000..cb8c80e6f9 --- /dev/null +++ b/data/telegram.org/blog/edit.html @@ -0,0 +1,245 @@ + + + + + Edit Messages, New Mentions and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Edit Messages, New Mentions and More

+ +
+ +
+ +

Farewell to typos! Starting today, you can edit the text of your messages after sending them. This works across all Telegram chats, including groups and one-on-one conversations.

+
+ +

Edit messages

+
+ +

Simply tap and hold on a message, then press ‘Edit’. If you're on desktop, press the up arrow button to edit your last message. The messages will display a small ‘edited’ label so that it's easy to tell which were altered.

+

New Mentions

+

Mentioning other people in groups is handy since it sends them a notification about your message even if they muted the group. Starting today, you can mention any members in a group – even if they don't have a username. Just type the @ symbol and select whoever you would like to address. Easy!

+
+ +

Mention group members

+
+ +

People List

+

Speaking of addressing people, you can now get to your recent chats much faster using the new People list in Search.

+
+ +

Recent chats

+
+ + +

Bot Attachments

+

We've also made it easier for you to access your favorite inline bots. Simply scroll down the attachment menu – and there they are. The more you use them, the higher they will climb.

+
+ +

Bots in attachment menu

+
+ +

Naturally, you will only see inline bots in the attachment menu if you used them at least once. Try @youtube, @gif or @imdb if you don't know where to start. Check out this post for more info on how to use inline bots.

+

Interface Improvements

+

We‘ve added quick sharing buttons to forwarded messages from bots, channels, and public groups. Notifications about messages with stickers will now show the relevant emoji so that you’ll know the general idea at first glance.

+
+ +

Scroll to bottom

+
+ +

Last but not least, if you're on iOS, your app now remembers the scroll position in chats when switching to a different chat and back. And scrolling up in a chat summons a new button that will send you back to the bottom in one tap. This button also displays a handy unread message counter if new ones are waiting for you there.

+

+ +

And that's it for today. Stay tuned for more updates coming soon!

+

+ +

May 15, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/encrypted-cdns.html b/data/telegram.org/blog/encrypted-cdns.html new file mode 100644 index 0000000000..c17dc4917b --- /dev/null +++ b/data/telegram.org/blog/encrypted-cdns.html @@ -0,0 +1,228 @@ + + + + + More Speed and Security! + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

More Speed and Security!

+ +
+ +
+ +
+
+ +

We at Telegram love to build sophisticated technologies that combine speed with security. Starting with Telegram 4.2, we support CDN caching. CDNs are third-party caching nodes that we’ll use to cache publicly available videos and photos posted in massive channels (say, with 100,000+ subscribers) for users in remote locations where Telegram is popular.

+

This will increase download speeds for tens of millions of users as CDN caching allows data to travel shorter distances and helps avoid bottlenecks that exist between regions.

+

While these caching nodes are only used to temporarily store public media (imagine Telegram versions of superpopular YouTube hits), all data that goes through them is encrypted with a key unknown to the caching nodes. In other words, we treat these CDN caching nodes just like we treat your internet provider – they only ever get encrypted junk they can't decipher.

+

Here’s how it works

+
+ +
+ +

If you're interested in the technical details, feel free to check out this page that describes the relevant encryption and security checks. And as always – the updated source code for the Telegram apps is open and available for your scrutiny. Security experts are welcome to verify the implementation of CDNs based on the open source code we make available for all of our apps.

+

Thanks to this technology, the download speed for public photos and videos in places like South America, Turkey, Indonesia, India, Iran or Iraq will significantly increase without the slightest compromise in security.

+

To sum up

+
    +
  • Download speeds for popular public media are set to increase several times for millions of Telegram users.
  • +
  • CDN caching nodes are not Telegram servers and not part of the Telegram cloud.
  • +
  • CDNs are used only for caching popular public media from massive channels. Private data never goes there.
  • +
  • CDNs only get encrypted data and they never have the keys: even if they are accessed by hackers or third parties, the attacker won’t be able to decipher the files.
  • +
  • Data downloaded from CDN caching nodes is always verified by the receiving Telegram app by way of hash: attackers won’t be able to replace any files with their own versions.
  • +
  • Detailed technical info about CDNs can be found here, the updated source code of Telegram apps ready for CDN support can be found here.
  • +
  • Telegram 4.2 also includes a bucketful of other goodies for you to enjoy.
  • +
+

+ +

Stay safe (and fast)!

+

July 23, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/export-and-more.html b/data/telegram.org/blog/export-and-more.html new file mode 100644 index 0000000000..8f62446caa --- /dev/null +++ b/data/telegram.org/blog/export-and-more.html @@ -0,0 +1,238 @@ + + + + + Chat Export Tool, Better Notifications and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Export Tool, Better Notifications and More

+ +
+ +
+ +
+ +
+ +

Today’s Telegram update brings you an easy way to save conversations on your disk. In just a few taps, you can export some (or all) of your chats, including photos and other media they contain. As a result you’ll get all your data accessible offline in JSON-format or in beautifully formatted HTML.

+
+ +

Data Export Results

+
+ +

To use this feature, make sure you have the latest version of Telegram Desktop installed on your computer, then click Settings > Export Telegram data. This tool will be particularly useful for users who have millions of messages and can’t easily access the oldest parts of their messaging history.

+
+ +
+ +

You can export individual chats by opening the menu in any chat and choosing Export chat history.

+

Exceptions in Notifications

+

Telegram was the first app to give its users notorious flexibility in fine-tuning how their message notifications work. Today we are taking this further by adding Exceptions to the notifications settings, where you can see which chats are excluded from the global settings you defined in Settings > Notifications.

+
+ +

Notifications Exceptions

+
+ +

Muting all chats but a few (or vice versa) has never been easier.

+

Improved Telegram Passport

+

We’ve been overwhelmed by the reception of Telegram Passport – the tool to log into third-party apps that require real-life identity. Just two weeks after its launch, Passport can be used to sign up for many services, from established sharing economy services to blockchain startups.

+
+To name just a few projects that integrated Telegram Passport: Sum & Substance (KYC & user verification), CEX.IO and Xena (cryptocurrency exchanges), CryptoPay (wallet), YouDrive (carsharing), Profi and Worki (job marketplaces), Minter Network and Minexcoin (blockchain startups), KICKICO, Cryptonomos and ICOadmin (ICO platforms).

+ +

Building on this success, today we’re upgrading Passport to support names in original languages and additional types of documents. We’ve also strengthened the algorithms that encrypt Passport data to better protect your data against hacking attacks coming from Telegram (however unlikely those may seem). This way we further ensure that only you have access to your private data.

+

Source Code and APIs

+

As always, you do not have to take our word on how our encryption works. The updated source code of Telegram apps reflecting all of today’s changes is available on GitHub and open for everybody to review. If you are a developer of a service that requires identity verification, make sure you check out these docs explaining how Telegram Passport can be integrated into your app.

+

+ +

August 27, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/files-on-steroids.html b/data/telegram.org/blog/files-on-steroids.html new file mode 100644 index 0000000000..9e33d82155 --- /dev/null +++ b/data/telegram.org/blog/files-on-steroids.html @@ -0,0 +1,240 @@ + + + + + Sending Files On Steroids — And More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Sending Files On Steroids — And More

+ +
+ +
+ +

Many of you love Telegram for the ability to send huge files up to 1.5 Gb.

+

Today’s iOS update brings you a radically improved Send File menu. We have integrated cloud services like iCloud, DropBox, Google Drive and others, so you can now easily share your existing documents directly from the Send File menu.

+
+ + + + + + + +
+ +

Share multiple files and trim videos

+

Starting today, you can also share multiple media files at once and see their size and resolution before sending them. As for sharing videos, we added the long-awaited preview and trim functionality to the iOS app.

+

Another improvement that is specific to iOS for now is the ability to open locations in Google Maps and other non-default map applications, as well as get driving directions.

+
+ + + + +
+ +

Hashtags and Android features

+

Hashtags now support non-latin characters on both mobile platforms, and what is more important, recently used hashtags will be instantly suggested when you type the # symbol. This makes them much more usable.

+

As for improvements to the Android app, this update includes the ability to erase search history for Web images, GIFs and hashtags (simply tap and hold on recent items in search), sounds for incoming and outgoing messages in the currently opened chat and a multitude of design and UI improvements.

+

In fact, we were lucky to get feedback from the Google design team that provided ideas on how to improve the UI of our Android app. This release has some of these ideas implemented – for example, if you set a custom background for your Telegram chats, it will also be used in the Menu Drawer.

+
+ + + + + +
+ +

Stay tuned – we are shipping another great update next week.

+

+
+ +

March 25, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/filters-anonymous-admins-comments.html b/data/telegram.org/blog/filters-anonymous-admins-comments.html new file mode 100644 index 0000000000..20e5bcd4dd --- /dev/null +++ b/data/telegram.org/blog/filters-anonymous-admins-comments.html @@ -0,0 +1,261 @@ + + + + + Search Filters, Anonymous Admins, Channel Comments and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Search Filters, Anonymous Admins, Channel Comments and More

+ +
+
+
+ +
+ Introducing Search Filters, Anonymous Group Admins, Channel Comments and More +
+ +

Your personal Telegram Cloud is endless and full of spicy memes. To help you find your way around it, we're introducing Search Filters. Today's update also features Anonymous Admins to make your battle for freedom safer and Channel Comments to make sure everyone's voice is heard.

+

Search Filters

+

From now on, you can filter search results by type using the new tabs: Media, Links, Files and others. To search a particular time period, just type “August 14” or “Yesterday”. Typing the name of any person, group, channel or bot will add a filter by source.

+
+ +
+ +

These search filters can be combined, which lets you look for something as specific as messages with a link, sent in March 2016, containing the word “boat”.

+

Anonymous Group Admins

+

Telegram is increasingly used to organize protests for democracy and freedom. Today we're introducing another tool for safer protests.

+

Toggle Remain Anonymous in Admin rights to enable Batman mode. The anonymized admin will be hidden in the list of group members, and their messages in the chat will be signed with the group name, similar to channel posts.

+
+ Post from an anonymous admin in a group +
+ +

Channel Comments

+

Speaking of Channels, we've added a comment button to posts on channels with discussion groups. Comments show up in a cozy little thread of their own, but will also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

+
+ +
+ +

If you are not a member of the channel's discussion group, you will be notified about replies to your comments via a new chat called Replies.

+
+

For a limited time only, you can test this feature in this channel.

+
+

If you'd like to enable discussions in your own channel, head to Channel Settings > Discussion.

+

Amazing Android Additions

+

Our Android wizards didn't forget to pack some new smooth animations. To get a taste, try expanding or hiding your keyboard – or switching between your day and night themes from the left menu. You will also see animated popups when deleting messages, changing notifications, saving media, etc.

+
+ +
+ +

In case you're more into practical things, press and hold on any profile picture in a group chat to take a closer look. And if you're using multiple accounts in one app, you can now preview the chat lists of your other accounts using the same gesture in the account switcher.

+

More Animated Emoji

+

We carry on with our quest to animate every emoji in existence. To get one of these 👇 in a chat, simply send a message with a single emoji.

+
+ +
+ + +

+ +

And that's all for today, see you in the comments.

+

+ +

September 30, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/folders.html b/data/telegram.org/blog/folders.html new file mode 100644 index 0000000000..be41e8623c --- /dev/null +++ b/data/telegram.org/blog/folders.html @@ -0,0 +1,298 @@ + + + + + Chat Folders, Archive, Channel Stats and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Chat Folders, Archive, Channel Stats and More

+ +
+ +
+ +
+ Introducing Chat Folders +
+ +

Many of our users rely on Telegram for their work and studies, even more so in the last weeks. To make sure everyone's chat lists can handle the increased load and you don't miss important messages, we're introducing Chat Folders today.

+

If you have too many chats, you can now separate fun from work, or family stuff from school stuff – then swipe between the tabs to quickly access any of your chats.

+
+ +
+ +

You can include or exclude all chats of a particular type, like Channels, or Unread – or one by one.

+

Folders become available in the interface when your chat list is long enough to start getting cluttered. Alternatively, you may use this link in your app to enable Chat Folders.

+

Unlimited Pins

+

Each of your folders can have as many pinned chats as you like.

+
+ Pinned chats in folders +
+ +

Archived Chats

+

Chat Folders work best to make some of your chats more visible. If you're looking to hide some of your chats from view, try archiving them instead.

+

Swipe left on a chat to transfer it to your archived chats folder. When an archived chat gets a notification, it will pop out of the folder and back into your chat list. Muted chats will stay archived forever.

+
+ +
+ +

You can hide the archive by swiping left on it. See it again by dragging the screen down.

+

On Android, if you are already using Folders, swiping will not work for archiving. Instead, you can long press on a chat to open the bulk actions menu where you can select multiple chats and then pin, mute, archive or delete them all at once.

+
+ Archive button in the bulk actions menu +
+ + +

Desktop Sync

+

Like everything on Telegram (except for Secret Chats), your Chat Folders will seamlessly sync to all your other connected apps, including our Desktop Apps.

+

Thanks to the extra space available on your computer screen, we've added a folder sidebar – as well as some icons to make your folders more recognizable:

+
+ +
+ +
+

Get the multiplatform Telegram Desktop or our dedicated macOS app. If you're not using those, you're only enjoying half of Telegram.

+
+

Channel Stats

+
+If you have a channel with more than 1000 50 subscribers, you can now view detailed statistics about its growth and the performance of its posts. +
+ +
+ +
+ +

With this information, you can find out what's working and what's working really well. Hint: Cat Pictures.

+

Voice Recording Animations on Android

+

Our designers added some fancy wavy animations below your finger when you're recording a voice or video message.

+
+ +
+ +

Tip of the day: Did you know you can slide your finger up to lock recording and keep talking without holding the button?

+

New Animated Emoji

+

The latest additions to our army of animated emoji can help you be brave and urge your friends to stay safe and healthy. Send 🦠, 🤒, 😷, 🤕, 🤧, 🤢, 🤮, 🧼, 💉, 💊 or 🚑 to any chat to check them out.

+
+ +
+ +

Most of our sticker packs now also have something to say about the situation. Type 🦠 in any chat and wait to see the suggestions:

+
+ +
+ +

And One More Thing

+

Missing your Catan or D&D partners while the world is on lockdown? Send 🎲 to any chat to get a certified random number from the animated dice.

+

Besides trying to test your luck, you can also use it as a tiebreaker if a group poll or friendly debate ends in a split decision. Pick a number – the closest one wins!

+
+ +
+ +

Stay home, stay safe and stay tuned for our next updates!

+

+ +

March 30, 2020,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/games.html b/data/telegram.org/blog/games.html new file mode 100644 index 0000000000..1208c848c0 --- /dev/null +++ b/data/telegram.org/blog/games.html @@ -0,0 +1,264 @@ + + + + + Gaming Platform 1.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Gaming Platform 1.0

+ +
+ +
+ +

Last year we launched a Bot Platform for Telegram. Free, powerful, and open, it was an instant hit among users and developers. Today we are aiming to push the boundaries further by launching a bot-powered Gaming Platform on Telegram. That’s right: you can now use bots to play games in your chats, complete with graphics and sound.

+
+
+ +
+
+ +

Ready to Play

+

Hundreds of games are headed your way, but about 30 are ready to be played on Telegram now, most of them published by @gamee. You can start a game by interacting with their bot directly, or by invoking it from any of your chats. To do that, try typing “@gamee “ in a group and choose a game to start playing with your friends:

+
+ +

Select a game

+
+ +

If you spot a great game on Telegram, you can challenge your friends from other chats by sharing the game with them.

+
+ +

Challenge your friends

+
+ +

Better with Friends

+

The best part of the Telegram Gaming Platform is the competition across all your existing chats. We save high scores for every game played in every chat, and you can instantly check out how you and your friends are doing against each other. Every time there’s a new leader in the game, other playing members of the chat are notified that they need to step it up.

+
+
+ +

In-game high scores

+
+
+ +

New high score in chat

+
+ +

Easy to Build

+

Building games for Telegram is easy (check out the API). Here’s MathBattle, a game that took our developer only 3 hours to build. You can launch it from any chat by typing @gamebot and choosing Math Battle:

+
+
+ +
+
+ +

This is Corsairs, a demo game that took its dev just 5 hours to build and set up. That includes sound, graphics and animations:

+
+
+ +
+
+ +

While these demos look basic, Telegram games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. The underlying technology is HTML5, so games are loaded on-demand as needed, just like ordinary webpages. Games will work on iPhones 4 and newer and on Android 4.4 devices and newer. Note that your friends will need Telegram 3.13 or higher to play.

+

If you are a developer, take a look at our Introduction to Games. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

+

No Added Calories

+

We know you love Telegram because it’s lean and efficient. This is why the new Gaming Platform requires 0 bytes of disk space and won’t add a single byte to the size of our apps. The only thing we're adding today is countless more fun moments in your chats.

+

+ +

And now let's see how high you can score.

+

+ +

October 3, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/gif-revolution.html b/data/telegram.org/blog/gif-revolution.html new file mode 100644 index 0000000000..a2e6bfe127 --- /dev/null +++ b/data/telegram.org/blog/gif-revolution.html @@ -0,0 +1,224 @@ + + + + + GIF Revolution + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

GIF Revolution

+ +
+ +
+ +

Good news for GIF-lovers! As of today, you can send and download GIFs up to 20x faster. This is possible because we're now re-encoding all GIFs to mpeg4 videos that require up to 95% less disk space for the same image quality.

+

We've optimized our apps so that they can smoothly play even dozens of GIFs on the screen at the same time. GIFs will now play automatically, so there's no need to launch each one manually anymore. (You can turn this off in Settings when you need a break.)

+

Sending GIFs

+

To make sending your favorite animations easier, we've added a dedicated GIF tab to the sticker panel. Tap on GIFs in chats (long tap on iOS) and ‘Save’ to add them to the panel. Then send them to any chat in one tap.

+
+ +

+
+ +

iOS users can now also send GIFs from the Gallery using the fully redesigned attachment menu.

+
+ +
+
+ +

GIF Bot

+

Last but not least, our new Inline Bots feature offers another innovative way of finding and sharing GIFs. These bots deserve a separate blog post.

+
+

Read on!

+
+

+ +

The Telegram Team,
January 4, 2016

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/gifs.html b/data/telegram.org/blog/gifs.html new file mode 100644 index 0000000000..57c3aeb673 --- /dev/null +++ b/data/telegram.org/blog/gifs.html @@ -0,0 +1,223 @@ + + + + + GIF Search and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

GIF Search and More

+ +
+ +
+ +

OK, so there is a celebration in the Android camp today. Telegram for Android was redesigned and loaded with new features. But what about the iPhone fan army? It turns out, the iOS app got something just as great.

+

In addition to granular controls for hiding your Last Seen and other privacy settings, today’s iPhone update introduces a great media feature – Animated GIF search.

+

How Does This Work?

+

You can find and share images from the Web using the “Find Images” attachment option. Today the Web image search got two new tabs – GIFs and Recent. The GIFs tab allows you to search through thousands of great GIF animations, powered by Giphy. Just type in a keyword and have fun.

+

All images from the Web and GIFs you share will be saved in the Recent tab. You can go that tab whenever you're out of words and instantly share any of them just in three quick taps. If you forward an incoming GIF to a contact, that animation will also be available from the Recent tab. And yes, you can send multiple GIFs at once.

+
+
+ +
+
+ + +

One More Thing

+

Another media feature we added to the iPhone app today are previews for YouTube and Instagram links. If a message contains nothing but a link to YouTube or Instagram, it will be transformed into a thumbnail with relevant information, such as title and duration. Check it out!

+

..but I'm on Android

+

All of this is coming to our Android app in the next updates. So for now, sit back and enjoy your new privacy settings and material design. Soon we'll have GIFs and images for you as well!

+

+ +

The Telegram Team
November 19, 2014

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/inline-bots.html b/data/telegram.org/blog/inline-bots.html new file mode 100644 index 0000000000..d205fd3371 --- /dev/null +++ b/data/telegram.org/blog/inline-bots.html @@ -0,0 +1,234 @@ + + + + + Introducing Inline Bots + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Introducing Inline Bots

+ +
+ +
+ +

Bots became an integral part of Telegram for many users, but communication with them wasn't always easy. You had to send them messages in separate chats or add them to your groups. Today we are introducing a quicker way to contact bots.

+

With the new inline mode, bots become omnipresent and can be used as a tool in any of your chats, groups or channels – it doesn't matter, whether the bot is a member or not. Inline bots can help you with dozens of different tasks, like quickly sending relevant GIFs, pictures from the Web, YouTube videos, Wikipedia articles, etc.

+
+
+ +
+
+ +

How does it work?

+

We've created several sample bots for you to try out: @gif, @vid, @pic, @bing, @wiki, @imdb and @bold. To see them in action, simply type one of their @usernames in the message field in any chat, then type some keywords. The bot will offer you relevant content.

+
+ + +
+
+ + +

Tap on an item to instantly send it to the chat. This way you can share stuff from bots without any hassle. Inline bots don't see any messages in your chats – they only receive what you type after their username in the input field.

+
+ + +
+
+ +

Tap on ‘via @username’ to send a new request to the bot. Recently used inline bots will also show up in the suggestion box when you type @ in the input field in any chat.

+

A new dimension for bots

+

Like pretty much everything else at Telegram, inline bots are part of an open platform, available for free to every developer in the world starting today. Hundreds of new inline bots are sure to arrive once developers start supporting the new mode.

+

If you are a developer, take a look at our Introduction to Inline Bots. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

+

+ +

The Telegram Team,
January 4, 2016

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/instant-camera.html b/data/telegram.org/blog/instant-camera.html new file mode 100644 index 0000000000..eeab87a2c0 --- /dev/null +++ b/data/telegram.org/blog/instant-camera.html @@ -0,0 +1,229 @@ + + + + + Instant Camera and More 3D Touch + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Instant Camera and More 3D Touch

+ +
+ +
+ +

When taking pictures, even a split second can make the difference between capturing the perfect moment or missing it entirely. Starting today, our iOS users can snap a photo or take a video in no time. To access your camera quickly, simply tap and hold the attachment button, and you're ready to shoot:

+
+
+ +
+
+ +

This quick camera interface defaults to selfie mode with flash on, but you can change this and it will remember your choice.

+

With this update it also becomes easier to record videos using the standard camera interface. Press and hold the big button and the recording starts. By popular demand, videos you record in-app will now be saved to your device in Full HD quality.

+

More 3D Touch and More

+

Starting today you can use 3D Touch to preview photos and videos everywhere, including the attachment menus, message history, and the Shared Media section. The same goes for profile pictures: That's right, you no longer need to go to chat info to check them out in full size.

+
+
+ +

We've also added Uber and Citymapper as options for opening a location:

+
+
+ +

And, speaking of opening stuff, we've fixed the issue with files – you can now open any file you get in other apps again. This is extremely useful, given that you can share and store an unlimited number of documents and files of any type on Telegram.

+

+ +

That's it for today, stay tuned for more updates coming soon! The cool features we are adding in the next release will be available for all platforms.

+

+ + +

April 28, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/instant-view-contest-200K.html b/data/telegram.org/blog/instant-view-contest-200K.html new file mode 100644 index 0000000000..8d1434b327 --- /dev/null +++ b/data/telegram.org/blog/instant-view-contest-200K.html @@ -0,0 +1,273 @@ + + + + + Instant Views for Everyone & a $200K Contest + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Instant Views for Everyone & a $200K Contest

+ +
+ +
+ +
+

Version 4.0 is the mother of all Telegram updates. Note that we're also launching Video messages + Telescope and Payments for Bots today.

+
+
+ +
+ +
+

UPD 30.05: We've increased the prize fund of our contest to $315,000 by adding more target domains. Join today!

+
+

Rejoice, brethren and sistren, the day has come! Instant View is now ready to support thousands of websites, including your favorite ones. Soon you will no longer need to launch a web browser to view any article shared with you on Telegram, because today we are launching the Instant View Platform.

+

Instant What?

+

With Instant View, you can enjoy articles from any blog or media outlet in a uniform and easily readable way. Beyond merely showing the text of an article, Instant View pages support images, videos, and any other media. They work great even if the source website isn't optimized for mobile devices.

+
+
+ +

Instant View Button

+
+
+ +

Instant View Page

+
+ +

Instant View pages are lightweight and cached on Telegram servers, so they load instantly on pretty much any connection — hence the name. But the best part is that webmasters don't need to change anything on their sites for Instant Views to work.

+

Meet the Instant View Platform

+
+ +
+ +

To generate Instant View pages, our parser bot uses templates — sets of rules that tell the bot where to find useful content and what to ignore on a particular domain or URL. The bot uses these instructions to create a slim and beautiful Instant View representation of the source page.

+

Today we are launching the Instant View Platform that allows anyone to create their own templates for websites. Like everything else we launch, this platform is completely open. All are welcome to join us in our quest to make the world's information more accessible (in a much more elegant way) to users everywhere!

+
+

Start here, check out our samples, then open the Instant View Editor and you‘re ready to rock. Also, here’s the full reference doc in case you want to know everything.

+
+

$200,000 Competition for Rule Makers

+

To get the ball rolling, we're also launching a $200,000 (now $315,000!) crowdsourcing competition for template makers. If you know a bit of HTML and want to participate, check out the Contest page. The task is easy: choose a website from our list and be the first to come up with the perfect set of rules to parse articles from that site into the Instant View format. Head over to the docs to get started!

+

For each website that you were the first to describe with an accurate set of rules before the end of the contest, you get $100 from our fund. The one who manages to best describe the most contest domains with their templates will be declared the winner and will get $10,000 on top of the payout from their templates. The second place winner gets a $5,000 prize on top of what they made on successful template submissions.

+
+

Winning templates will be used to display Instant View pages to all Telegram users after we approve them.

+
+

Even if you don't know anything about HTML or programming, you can help our brave template-makers by finding and reporting issues with their work. If somebody wins with a bit of your help, you may get a share of the reward.

+

Tips for website owners

+

If you own a website and want your articles to be viewed natively inside Telegram, simply have a developer add a template for your site.

+

If you distribute your content via a Telegram channel, you don't even have to wait for us to approve your template. Simply send specially formatted links to your subscribers and they will get Instant View pages based on your template right away.

+

You can also direct users who view Instant View pages from your site to join your channel on Telegram (more on how to do that):

+
+ +

Join Button

+ +

If any of this seems too complicated, just sit back and relax: crowdsourcing will take care of it for you in due time.

+

One More Thing

+

In version 4.0 we‘ve added some nifty Instant View settings. You can now view your articles in dark, gray, or sepia-toned environments, as well as adjust the font type and size. The Auto-Night Theme setting will soothe your eyes by automatically showing dark pages when it’s late.

+
+ +

Instant View Settings

+
+ +

When you find something noteworthy on an Instant View page, simply long tap on the paragraph to select it for quickly copying or sharing it with your contacts.

+
+ +

Quick Copy / Share

+
+ +

+ +

Good luck making rules, identifying issues, or – if you’re a regular user – happy Instant Viewing!

+
+

P.S. Follow @IVContest to get the latest updates about the contest.

+
+

+ +

May 18, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/invite-links.html b/data/telegram.org/blog/invite-links.html new file mode 100644 index 0000000000..3c98d9290e --- /dev/null +++ b/data/telegram.org/blog/invite-links.html @@ -0,0 +1,217 @@ + + + + + Migrating Existing Group Chats to Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Migrating Existing Group Chats to Telegram

+ +
+ +
+ +

In addition to numerous great features in today's update, we’re happy to introduce a new way to move your existing group chats to Telegram — invite links for admins.

+

Each passing month brings more reasons to switch to Telegram from older services. Persistent history, instant full-text search, open platform, unlimited file sharing, rich link previews, native desktop apps, replies, mentions, hashtags and much more.

+

And yet, if you‘ve ever tried moving your existing group chats from other apps to Telegram, you know it was not easy. There was simply too much work to do and too much friction — you had to collect everyone’s usernames or phone numbers and add them to your group one by one. We're glad to announce that these days are over.

+

Invite Links

+

With invite links for groups, all you have to do is send a link to your existing group chat in any messaging service that your friends might still be using. As soon as they get Telegram, they can instantly join your Telegram group just by following that link.

+

Where do you get the link? Once you've created a group on Telegram, head to the "Add participant…” section and tap “Invite to Group via Link”. Easy!

+
+ + + +
+
+ +


+ +

The Telegram Team,
April 30, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/link-preview.html b/data/telegram.org/blog/link-preview.html new file mode 100644 index 0000000000..0ff5fd1f8b --- /dev/null +++ b/data/telegram.org/blog/link-preview.html @@ -0,0 +1,217 @@ + + + + + Link Previews + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Link Previews

+ +
+ +
+ +

In addition to new security features, today‘s update brings you rich link summaries. All links to tweets, Instagram photos and YouTube videos will now be beautifully rendered so that you’ll see what the link is all about before opening it.

+

Once you paste a URL to the message input field, Telegram will start analyzing the link and getting a preview for it. If you prefer to send a particular message without the preview, just tap the x to remove it.

+
+ + + + + +

+ +
+ +

Rich link previews are now shown for most websites.

+

+ +

April 8, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/live-locations.html b/data/telegram.org/blog/live-locations.html new file mode 100644 index 0000000000..32b9e99871 --- /dev/null +++ b/data/telegram.org/blog/live-locations.html @@ -0,0 +1,243 @@ + + + + + Live Locations, Media Player and Languages + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Live Locations, Media Player and Languages

+ +
+ +
+ +
+ +
+ +

Starting with Telegram 4.4, you can broadcast your current location to any chat in real time.

+

This is useful when you are on your way to an appointment or are trying to coordinate with friends at a large event. Instead of sending static locations on the map every minute, you can now share your Live Location with the people you’re meeting – for 15 minutes, 1 hour, or 8 hours.

+

To use this feature, select ‘Location’ from the attachment menu and choose ‘Share My Location for…’:

+
+
+ +
+
+ +

You can also share your Live Location in groups, and if other members of the group do the same, you’ll get an interactive map of everyone’s current coordinates. Thanks to a bar at the top of the screen, you will always remember who you’re sharing your location with. And you only need two taps to stop sharing whenever you choose to.

+

New Media Player

+

We’ve completely redesigned our in-app audio player to better support the playback of MP3s and other music files you send and receive. Try the @cctracks channel for a demo – we’ve uploaded some free music there to demonstrate how the new media player works. After downloading an audio file, tap the play button to start listening. To view the cover image and the rest of the chat's playlist, tap on the title of the playing track in the top bar.

+
+
+ +
+
+ + +

More Languages

+

We’re also launching a new translation platform for Telegram apps. Starting today, Telegram is available in French, Indonesian, Malay, Russian and Ukrainian – with more languages like Persian coming soon. Telegram now supports 13 languages, which are available in Settings.

+

If you don’t like how a specific element in Telegram's interface is translated in your language, you can now use the localization platform to suggest an alternative word or phrase. Everyone can suggest translations and vote for them, making Telegram localization a community-driven effort.

+
+ +

Screenshots make translations easier

+
+ +

Unlike other services, Telegram can instantly push new translations of words and phrases to the apps. Thanks to this, users won't need to wait for an update in the stores to get the new localized version.

+

This also means that our developers won't have to wait for all translations to be finished before the apps are released, so this new interface will speed up Telegram development too.

+

Better Group Chats

+

As always, we’re trying to make Telegram group chats better. In large groups, you can now recognize messages from admins by the new ‘admin’ badge. And Admins in supergroups can now control whether new members get to see the earlier message history.

+

+ +

October 10, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/live-streams-forwarding-next-channel.html b/data/telegram.org/blog/live-streams-forwarding-next-channel.html new file mode 100644 index 0000000000..d9f50e579b --- /dev/null +++ b/data/telegram.org/blog/live-streams-forwarding-next-channel.html @@ -0,0 +1,285 @@ + + + + + Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

+ +
+
+
+ +
+ Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More +
+ +

Telegram was launched just over 8 years ago and today we are continuing our tradition of monthly updates with version 8.0. This update brings live streams with unlimited viewers to groups and channels, options to remove captions from media and hide sender names when forwarding, an easy way to jump to the next unread channel without going back to your chat list, an improved sticker panel, new animated emoji and more.

+

Unlimited Live Streams

+

Our previous update made Group Video Calls a powerful tool for live broadcasts — and now their audience is unlimited (except by the popularity of your channel, or the population of Earth, whichever is more relevant in your case).

+

Start a Live Stream in a channel or a Video Chat in a group – both now support unlimited viewers. The power to run your own TV station is here, right in your pocket.

+
+ +
+ +
+

To begin, tap 'Video Chat' (in Groups) or 'Live Stream' (in Channels) on the profile page of a community where you are an admin.

+
+

The viewers of your Live Stream can also raise their hand and join your broadcast if you allow them to speak.

+

Flexible Forwarding

+

Forwarding has become a much more relaxing experience. Tap the 'Forward Message' label above the message bar to open a preview window, showing how the messages will look when they are sent – along with several customization options.

+
+ +
+ +

You can choose to hide the sender's name or hide captions on media messages. You can also deselect messages you don't want to send or change the recipient if you tapped the wrong chat.

+

Jump to Next Channel

+

There are millions of one-to-many channels on Telegram that users follow for news, events, and content.

+

To keep up with the news easily, you can now scroll through the channels you follow without going back to your chat list. When you reach the bottom of a channel, pull up to go to the next unread channel.

+
+ +
+ +

If you have organized your chat list with Folders or Archived Chats, the app will follow the structure you have set up: channels in the current folder, then within each folder, then those left in All Chats and the Archive. Simply open a channel from your Studies folder to read them all without getting distracted by Memes — and vice versa.

+

Trending Stickers

+

Thanks to an open platform and thousands of free, high-quality stickers in the sticker directory, there's a perfect sticker for every situation. This update makes it easier to find the one.

+

Trending Stickers are now shown above ‘Recently Used’ in your sticker panel. Tap 'Add' to save a pack for the future — the trending sticker section is one of the few things in this world that gets updated more often than the Telegram apps.

+

When you scroll through your packs at the top of the panel, the thumbnails expand and show the names of your sticker packs.

+
+ +
+ +

Telegram for Android also got larger previews for sticker suggestions. To get suggestions, enter one emoji in the input field. To see more suggested stickers, pull upward on the suggestions panel.

+
+

If you have a particular thing in mind and don't have it among your sets, type a word in the search field to find matches from the sticker directory. Try 'yellow', 'animal', 'dog', etc.

+
+

Choosing a Sticker

+

Similar to 'typing…' or 'recording a voice message', the apps now show a 'choosing a sticker' status at the top of the chat — so you know that your chat partner is still there, just looking for the perfect animated response.

+
+ +
+ +

Unread Comment Counters

+

Many channels have comments enabled for their posts so that subscribers can interact and share their thoughts. We've recently had a great chance to test this with thousands of birthday wishes — thank you all for your support.

+

Just like with chats, when you open a comment thread that has new messages, a counter will now appear showing the number of unread comments.

+
+ Unread comments in a thread you just opened +
+ +

New Animated Emoji

+

This month we asked ourselves: “Should we stop animating more and more emoji with each update?” After a heated discussion we arrived at this answer: “Probably not.” Send a message with a single emoji to get one of these new masterpieces in a chat:

+
+ +
+ +

That's it for today — and we already have some cool stuff in development for the next update. See you there!

+

+ +

August 31, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/login.html b/data/telegram.org/blog/login.html new file mode 100644 index 0000000000..8cbbb3248d --- /dev/null +++ b/data/telegram.org/blog/login.html @@ -0,0 +1,257 @@ + + + + + Telegram Login for Websites + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Login for Websites

+ +
+

This post is from Feb 2018. For up-to date information on integrating services with Telegram please see this post. For Telegram Widgets, see this page.

+
+
+ +
+ +
+ +
+ +

Today we present a Telegram Login Widget for external websites. When you use Telegram login for the first time, our widget asks for your phone number and sends you a confirmation message via Telegram to authorize your browser.

+
+

Once this is done, you get a two-click login on every website that supports signing in with Telegram. Try it here:

+

Once this is done, you get a two-click login on every website that supports signing in with Telegram:

+
+
+ + +
+ +

+ +

Logging in will send your Telegram name, username, and your profile picture to the website owner. Your phone number remains hidden. The website can also request permission to send you messages from their bot.

+

Permission to speak

+

Telegram bots are a powerful communication tool, but until today they couldn't start a conversation. Even if you wanted them to reach out to you, you had to chat them up first.

+

With the new login widget, moving from interacting with a website to a conversation on Telegram becomes completely frictionless.

+
+ +

Message from a bot

+
+ +

The potential use cases are limitless. Bots could be used for providing customer support, accepting payments, or sending notifications of any kind – including account statements, shipment tracking, flight updates, and so much more.

+

Stay in control

+

After each login, Telegram will send you a summary message about the permissions you‘ve granted and the data you’ve passed to the website owner. You can revoke the authorization by tapping the appropriate button under the login summary.

+

Telegram for Android 4.8, also released today, includes a section in the Privacy & Security settings that lists all the websites where you logged in using Telegram. Other apps will soon follow.

+

+ +

This simple login tool is the first phase of the Telegram ID project, which we will be rolling out throughout this year.

+ +

+ +

February 6, 2018,
The Telegram Team

+

P.S.

+

Don‘t miss the other updates we’ve launched in the last few days:

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/masks.html b/data/telegram.org/blog/masks.html new file mode 100644 index 0000000000..1e5b415f63 --- /dev/null +++ b/data/telegram.org/blog/masks.html @@ -0,0 +1,248 @@ + + + + + Photo Editor 2.0, Masks and Homemade GIFs + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Photo Editor 2.0, Masks and Homemade GIFs

+ +
+ +
+ +

Last year we introduced the most powerful photo editing tool ever to be implemented in a messaging app. This allowed you to instantly improve photos before sending them on iOS and Android.

+

Today we’re pushing the photo editor to the next level with the fun stuff: you can now add drawings, masks, stickers and text right onto your pictures.

+
+
+ +
+
+ +

This is easy: just choose a mask, and it will be automatically positioned in the right place. Telegram identifies faces on photos and uses mask meta-data to find the perfect spot.

+

Our artists created hundreds of beautiful and fun masks as examples, but everything we do here in Telegram is an open platform. So as of today, anyone can use the /newmasks command for the @stickers bot to upload their own masks.

+
+
+ +

Masks Button (top right)

+
+
+ +

Adding Masks

+
+ +

When opening a photo, you will see a list of mask sets that were used on it. This way popular custom masks will quickly become viral.

+

GIFs Democratized

+

Another thing that’s likely to spread virally now are your GIF-animations. Creating your own GIFs has never been easier: simply record a video in Telegram and tap the new “mute” button to share it as a looped autoplayed GIF.

+
+
+ +
+
+ +

The animation will be saved to your GIFs section so that you can quickly react to anything with a set of your own prerecorded GIF-emotions.

+

Trending stickers

+

The last addition to this entertainment-heavy update is the trending stickers tab. Whenever you’re feeling hungry for new stickers you can find the latest additions in the stickers panel in any of your chats.

+
+ +

In-chat Trending Stickers

+
+ +

+ +

We're back from the summer break, so watch out for more updates coming your way soon.

+

+ +

September 23, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/moar-stickers.html b/data/telegram.org/blog/moar-stickers.html new file mode 100644 index 0000000000..30be8c9d12 --- /dev/null +++ b/data/telegram.org/blog/moar-stickers.html @@ -0,0 +1,343 @@ + + + + + MOAR Stickers! + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

MOAR Stickers!

+ +
+ +
+ +

Two months ago we launched a new kind of stickers, bringing popular memes, art and history together as an enhanced way of expressing emotions. Over the last few days we've added 15 new stickers to the original set.

+

Start a message with an emoji from this list to see emotionally corresponding stickers:

+
+ + +
+
Napoléon Bonaparte:
"In France, only the impossible is admired" +
+
+ +
+
+ + +
+
Jimi Hendrix accepts the challenge +
+
+ +
+
+ + +
+
Dante's "What the HELL?!" +
+
+ +
+
+ + +
+
LOL Marley +
+
+ + +
+
+ + +
+
Screamin' Jay Hawkins:
"Don't put that spell on me!" + +
+
+ +
+
+ + +
+
Audrey is on the verge of tears +
+
+ +
+
+ + +
+
Malcolm X: "Mother of..." +
+
+ +
+
+ +
+
Virginia Woolf: "Go on..." +
+
+ +
+
+ + +
+
Poe is sceptical +
+
+ +
+
+ +
+
Coco Chanel is unmoved +
+
+ +
+
+ + +
+
Frederick Douglass is in a dark mood +
+
+ +
+
+ + +
+
Princess Diana blushing +
+
+ + +
+
+ + +
+
Julius Caesar approves +
+
+ +
+
+ + +
+
On second thought... No. +
+
+ +
+
+ + +
+
Kisses from Cleopatra +
+
+ +
+

Remember that it's easy to send your own stickers in Telegram. Simply send a .webp image with a transparency layer as a file in your chat, and it will become a sticker.

+

+ +

March 11, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/move-history.html b/data/telegram.org/blog/move-history.html new file mode 100644 index 0000000000..e389baa40c --- /dev/null +++ b/data/telegram.org/blog/move-history.html @@ -0,0 +1,284 @@ + + + + + Moving Chat History from Other Apps + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Moving Chat History from Other Apps

+ +
+
+
+ +
+ Moving Chat History from Other Apps and More Privacy +
+ +

Over 100 million new users joined Telegram this January, seeking more privacy and freedom. But what about the messages and memories that remain in older apps?

+

Starting today, everyone can bring their chat history – including videos and documents – to Telegram from apps like WhatsApp, Line and KakaoTalk. This works both for individual chats and groups:

+
+ +
+ +

To move a chat from WhatsApp on iOS, open the Contact Info or Group Info page in WhatsApp, tap Export Chat, then choose Telegram in the Share menu.

+

On Android, open a WhatsApp chat, tap ⋮ > More > Export Chat, then choose Telegram in the Share menu:

+
+ +
+ +
+

WhatsApp for iOS also lets you export chats directly from the chat list. Swipe left on a chat, then choose '…' > Export Chat.

+
+

Messages will be imported into the current day but will also include their original timestamps. All members of the chat on Telegram will see the messages.

+

Move Chats and Save Space

+

The best part is that the messages and media you move don’t need to occupy extra space. Older apps make you store all data on your device – but Telegram can take up virtually no space while letting you access all your messages, photos and videos anytime you need them.

+
+

You can free up space and control your cache size in Settings > Data and Storage > Storage Usage.

+
+

Control Your Digital Footprint

+

Your data is your business, which is why Telegram users can not only export their chats, but also delete messages they send and receive for both sides – without a trace.

+

With this update, you get even more control: secret chats, groups you created and call history can now also be deleted for all sides at any time.

+
+ +
+ +

Telegram servers don’t store information about deleted chats and call logs, so the data will disappear completely, forever.

+

Improved Voice Chats

+

You can now see which of your groups have active Voice Chats from the top of the Call History page.

+

While in a voice chat you can adjust the volume of individual participants to manage microphone levels. Adjustments made by group admins are applied for all listeners.

+
+ +
+ +

Improved Audio Player

+

When a track is playing, tap the author name in the player to see their tracks from all your chats. If you need to skip ahead or repeat something you missed, press and hold on the Next and Previous buttons to fast-forward and rewind.

+
+ +
+ +

We’ve also added a fade effect to please your ears when you pause and resume the music.

+

Greeting stickers

+

If you have contacts who joined Telegram recently, it may be a nice touch to welcome them using one of Telegram's unique features. A greeting sticker will be suggested in your new chats, ready to send in one tap.

+
+ +
+ +

New Android Animations

+

A new update means sleek new interface animations. See if you can catch them all when downloading files, playing music, or loading chats after logging in.

+
+ +
+ +

Reporting Fake Channels

+

All Telegram apps let you report spam and other types of illegal content, including calls to violence or child abuse. Now you can also report fake channels or groups that impersonate famous people or organizations. Open their profile page and tap '…' > Report > Fake Account to let our moderators know.

+

Improved Accessibility

+

Many accessibility improvements have been added for both TalkBack and VoiceOver users. As we continue to refine app interfaces for all users, we welcome additional feedback on our Suggestions Platform.

+

A warm welcome to everyone who joined us recently! The next update shouldn’t take long.

+

+ +

January 28, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/new-profiles-people-nearby.html b/data/telegram.org/blog/new-profiles-people-nearby.html new file mode 100644 index 0000000000..d5c5d02873 --- /dev/null +++ b/data/telegram.org/blog/new-profiles-people-nearby.html @@ -0,0 +1,263 @@ + + + + + New Profiles, Fast Media Viewer and People Nearby 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

New Profiles, Fast Media Viewer and People Nearby 2.0

+ +
+ +
+ +
+ New Profiles, Fast Media Viewer and People Nearby 2.0 +
+ +

Hundreds of millions rely on Telegram to share precious moments with their loved ones. Today we're making it easier to relive shared memories with redesigned profiles, instant access to shared media, and new ways to thumb through pictures and videos.

+

In case you're more of a digital extrovert, the updated People Nearby section offers fresh ways to forge new friendships.

+

Redesigned Profile Pages

+

This update transforms profiles into one of the most functional (and beautiful) sections of the app. It's simpler than ever to see the photos, videos and links you've shared with your friends – or browse their profile pictures.

+
+ +
+ +

Intuitive Media Browsing

+

You can now flip through media from chats and profiles with taps – no more smudges on your screen from repeatedly swiping. Simply hit the right or left side of an image to go forward and back.

+

In case you're wondering where to best try out these new features, look no further than the updated People Nearby section.

+

People Nearby 2.0

+

Last June, we added People Nearby for exchanging contact info face-to-face. With this update, People Nearby 2.0 can help you meet new friends, or arrange a last-minute date for Valentine's Day.

+

Head over to Contacts > People Nearby to see adventurous Telegram users in the area. Tap Make Myself Visible to join them and display your profile to others around you. They will be able to find you and send you messages – even if you navigate away from the page or close the app.

+
+ +
+ +

If you decide you're no longer in the mood for adventure, tap Stop Showing Me to re-engage your cloaking device.

+

New Animated Emoji

+

We couldn't pass up the chance to let you shower important people in your life with the newest animated emoji. 😘 😍 😻 🥰 💑 💋 💝 🧡 💛 💚 💙 💜 🖤 🤍 🤎 💔 – and of course 💌 – have just become a lot more moving.

+
+ +
+ +

If your emoji has a heart, we'll give it a beat. Stay tuned for the next update!

+ + +

+ +

February 13, 2020
XOXO
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/now-you-see-me.html b/data/telegram.org/blog/now-you-see-me.html new file mode 100644 index 0000000000..199b6c6a88 --- /dev/null +++ b/data/telegram.org/blog/now-you-see-me.html @@ -0,0 +1,235 @@ + + + + + Disappearing Media, Your Bio & More Speed + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Disappearing Media, Your Bio & More Speed

+ +
+ +
+ +
+ +
+ +

Telegram 4.2 is here! We have completely redesigned our photo editing tools, and it takes you even fewer taps to make your photos look amazing. In addition, you can now set a self-destruct timer for any photos and videos you share in private chats.

+
+ +
+ +

If you set a timer, the countdown starts the moment your recipient opens the photo or video you sent. After the time runs out, the photo/video will disappear forever, just like in Secret Chats.

+

If the recipient tries to make a screenshot of your disappearing media, you’ll get a notification immediately.

+

Who are you again?

+

Starting today, you can add a bio to your profile by typing a few words about yourself in Settings. Every time you stumble upon new users in large groups you might want to learn more about them. That's where bios can help.

+
+ +

Bio in your profile

+
+ +

More Speed and Security

+

On top of this, as of 4.2, Telegram apps will rely on a CDN (distributed network) to cache publicly available photos and videos posted in massive channels (100,000+ members). This will result in significantly higher download speeds for tens of millions of Telegram users around the world. Check out this post to learn more about how we managed to do it in a slick and secure way.

+

One More Thing

+

Stickers are now easier to use as you can enlarge the scrolling area. More legroom for your emotions!

+
+
+ +
+

+
+ +

July 23, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/passport.html b/data/telegram.org/blog/passport.html new file mode 100644 index 0000000000..8cca4e32d8 --- /dev/null +++ b/data/telegram.org/blog/passport.html @@ -0,0 +1,233 @@ + + + + + Introducing Telegram Passport + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Introducing Telegram Passport

+ +
+ +
+ +
+ +
+ +

Our digital lives are getting closer and closer to the real world, and the number of services that need to know your real-life ID increases accordingly. Before today, this meant you had to upload the same document scans over and over for each new app. No more!

+

Meet Telegram Passport – a unified authorization method for services that require personal identification. Upload your documents once, then instantly share your data with services that require real-world ID (finance, ICOs, etc.).

+
+ +
+ +

Protected by End-to-End Encryption

+

Your identity documents and personal data will be stored in the Telegram cloud using End-to-End Encryption. It is encrypted with a password that only you know, so Telegram has no access to the data you store in your Telegram passport. When you share data, it goes directly to the recipient.

+
+ +

Sharing Data with an App

+
+ +

In the future, all Telegram Passport data will move to a decentralized cloud.

+

Try It Now

+

If you'd like to see a real-life implementation of Telegram Passport, head over to ePayments.com – the first electronic payments system to support registration and verification with Telegram Passport.

+

You can also try out how Telegram Passport works using this page to request data.

+

Please note that you need the latest version of Telegram to access this feature. Once you've uploaded some documents, you will see your data in Settings > Privacy & Security > Telegram Passport (on iOS: Settings > Telegram Passport).

+

Connect Telegram Passport

+

All developers are welcome to integrate Telegram Passport into their apps and services free of charge. It takes minimum effort and can save many hours of coding.

+

If you are building a service that requires real-life ID, check out the API docs for SDKs and examples.

+

Stay Tuned

+

In the future, we will be adding third-party verification for Telegram Passports. This way, services won't even need to request the data itself, instead relying on the fact that the Telegram account was approved by a verification provider and the person is real.

+

+ +

July 26, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html b/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html new file mode 100644 index 0000000000..6ecb091d68 --- /dev/null +++ b/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html @@ -0,0 +1,319 @@ + + + + + Payments 2.0, Scheduled Voice Chats, New Web Versions + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Payments 2.0, Scheduled Voice Chats, New Web Versions

+ +
+
+
+ +
+ Payments 2.0, Scheduled Voice Chats, New Web Versions and More +
+ +

This update brings Payments 2.0 for all Telegram chats, Scheduling and Mini Profiles for Voice Chats, new Telegram apps for your browser, and more.

+

Payments 2.0

+

We first added support for payments in 2017. Payment bots allowed users to securely pay for goods and services without leaving the app – anything from ordering a pizza to hailing a taxi, to replacing winter tires when you're tired of winter.

+

Starting today, merchants can natively accept credit card payments in any chat, relying on 9 integrated third-party payment providers such as Stripe.

+

Buyers can add a tip whenever they make a purchase to show some extra love to their favorite artists, stores, or delivery drivers. Payments can now be made from any app – including desktop apps.

+
+ +
+ +

This is a free and privacy-conscious platform – Telegram takes no commission, and stores no payment information. Credit card information is sent directly to the payment provider and shipping information is shared with the merchant so they can send you your goods.

+
+

We've created a demo channel with the most exotic imaginary goods and services no money can buy, so you can test how this works without spending a penny.

+
+

Any merchant can start using the Payments API without getting additional approvals from Telegram. Developers interested in integrating payments can find all the details in the Payments Manual.

+

Scheduled Voice Chats

+

Voice Chats give users the option to catch up with a few friends or tune in to massive broadcasts with millions of listeners.

+

Admins of groups and channels can now schedule a Voice Chat for a particular date and time instead of creating one right away. This gives community members time to let their friends know and get the popcorn ready.

+
+ +
+ +

Users will see a colorful countdown at the top of the chat. Those too busy to watch the countdown can opt to receive a notification when the voice chat starts.

+
+ +
+ +
+

Admins can schedule a Voice Chat from their Group or Channel's profile page. On Android, tap ⋮ > Start Voice chat > Schedule Voice Chat. On iOS, tap the Voice Chat button and select Schedule Voice Chat.

+

Don't worry, the chat won't start automatically when the countdown reaches zero – only when an admin presses the Start Now button.

+
+

Mini Profiles for Voice Chats

+

You can now expand profile pictures and bios to get a better idea of who you're chatting with – without leaving the voice chat window.

+
+ +
+ +

You can also change your profile picture and edit your bio without leaving the chat – like changing from Shirley to Grognak the Barbarian as you meet for Dungeons and Dragons.

+

New Web Versions

+

Telegram's first Web Version was launched in 2014. Ever since, our pet demon of internal competition kept whispering: 'Why have one web version when you can have two?'

+

Today we're adding two new, fully-featured Telegram web apps – both supporting animated stickers, dark mode, chat folders and more.

+
+ +
+ +

With the new web versions you can get instant access to your chats on any device – desktop or mobile. These apps are incredibly efficient, requiring only a 400 KB download (that's like two photos of a medium-sized cat) and no installation.

+

Take them for a test drive, and see which one you like best:

+ +

Like other Telegram apps, all our web versions are standalone: once you've logged in, you do not need to keep your phone nearby or connected to the internet.

+
+

If you find an issue with either of the new apps, let us know using our Suggestions Platform.

+
+

Direct Download for Android

+

In case you're more of an app person, you can now also download Telegram for Android directly from telegram.org. Apps installed from the website will automatically update to the latest version. You are likely to get new versions several days or weeks faster this way because you won't have to wait for updates to be reviewed by the store.

+ + +
+ +
+ +
+

Telegram supports reproducible builds, so you can always be sure that the app you have on your device was built from the exact same open source code that is published on GitHub.

+
+

Pinch to zoom

+

Photos and videos can now be expanded directly from the chat – simply pinch to zoom in right away, without tapping to open the media viewer.

+
+ +
+ +

Improved Video Player

+

When watching a video from the media player on iOS, press and hold the + or - 15s buttons to fast-forward and rewind. On Android press and hold on the right or left side of the screen to do the same, and double-tap to jump 10 seconds in either direction.

+
+ +
+ +

Tips and New Android Animations

+

The Android app gets smoother and more dynamic with each update – check out the new animations when opening the side menu or swiping back to the chat list from a chat.

+
+ +
+ +
+

To learn more about what Telegram can do, tap Telegram Features from the side menu or visit the @TelegramTips channel.

+
+

Telegram Jobs

+

That's it for today. We are already working on the next update — and if you just thought 'Wow, that's the spirit!' rather than 'Poor people, have some rest', check out our list of open positions.

+

+ +

April 26, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/payments.html b/data/telegram.org/blog/payments.html new file mode 100644 index 0000000000..61d0a8a1b0 --- /dev/null +++ b/data/telegram.org/blog/payments.html @@ -0,0 +1,253 @@ + + + + + Payments for Bots + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Payments for Bots

+ +
+ +
+ +
+

UPD 2021: For up-to-date information about Payments on Telegram, see Payments 2.0 and the Payments Documentation.

+
+
+ +
+ +

Imagine a world where you can order pizza, pay for a pair of shoes, hire a cab, or refill your subway pass — all in a few button taps on Telegram.

+

To make this world possible, we are launching Bot Payments today. Bot developers can now accept payments from their users around the world, just like that:

+
+
+ +
+
+
+ +

If you have Telegram 4.0 (or newer) installed, you can order goods or services from bots that offer them. These bots may now add a Pay button to their messages. When you tap Pay, you'll be asked to fill in your credit card and shipping information and confirm the payment. Then you get what you paid for. Voila!

+

If your account is protected by 2-Step Verification, you can save your card for future purchases. If you do that, ordering stuff from bots will only take two taps. Bot Payments also support Apple Pay for a completely frictionless experience.

+

Check It Out Now

+

Try our demo @ShopBot to get a taste of what's coming. (Note: Our demo bot thinks it sells time machines, but they're not a part of what's coming. Sadly.) If you're looking to test a real payment with actual money, stop by our @TelegramDonate bot.

+

Telegram is an open platform, so bot developers can implement the necessary APIs and accept payments from users starting right now, without lengthy approval dramas. If you’re a bot developer, check out the docs immediately!

+

Behind the Scenes

+
+ +
+ +

At launch, most of the payments were handled by Stripe, but Telegram Bot Payments are a platform for payment providers all over the world. When accepting a payment from a user, the bot developer can choose between all available payment providers, selecting the one already used by the buyer or the one with the lowest commission.

+
+

UPD, 14.06.2017: Bot developers can now process payments from more than 200 countries via the global payment provider Paymentwall.

+

UPD, 02.06.2017: Yandex.Money and Payme are now also available as payment providers.

+

UPD, 01.09.2017: Rave by Flutterwave is now available, which is especially helpful for developers in Nigeria, Kenya, Ghana, South Africa, and Uganda.

+
+

This is just the beginning. In the next few days, payments will become available to developers in India via Razorpay, in Russia Qiwi will be joining the club a little later.

+

Follow our @BotNews channel to be the first to know about new providers joining.

+

If you’re a payment provider (especially in a developing country), click here to learn how to get on board.

+

Just Passing Through

+

Telegram acts as a messenger (pun intended) between the paying user, the bot developer, and their chosen payment system. The user sends their credit card details directly to the payment system. Then the payment system's response and the shipping details entered by the user are passed to the bot developer so that they can process the order.

+

Due to this structure, it is impossible for Telegram to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.

+

Since Telegram doesn't process the payments, we don't store and can't access any sensitive data. We also don't take any commission from payments and don't profit from these transactions.

+

Instead, we just do what every sheriff has to do with strangers passing through their turf: shoot the bad bots and award the good ones with a badge. We’re sure there’ll be plenty of good ones.

+

If You Are…

+ +

And if you're none of the above for some weird reason, be a user, do the right thing. Happy shopping, everyone!

+

+ +

May 18, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/permissions-groups-undo.html b/data/telegram.org/blog/permissions-groups-undo.html new file mode 100644 index 0000000000..0d2efdc7f5 --- /dev/null +++ b/data/telegram.org/blog/permissions-groups-undo.html @@ -0,0 +1,265 @@ + + + + + Group Permissions, Undo Delete and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Group Permissions, Undo Delete and More

+ +
+ +
+ +
+ Introducing Telegram 5.2: New permissions for groups, unified group settings, undo deleting chats and more +
+ +

Ever wanted to run a sticker-free or GIF-free community? With group permissions, admins can now restrict all members from posting specific kinds of content. Or even restrict members from sending messages altogether – let the admins chat amongst themselves while everybody else witnesses their wisdom in silent awe.

+
+ +
+ +

In case you ever felt lonely in a group with 100,000 members, Telegram groups now support up to 200,000 members – so now you can feel twice as lonely 🙃. To make managing groups more enjoyable, we've streamlined all group interfaces, including the Settings screens, Admin panels and Member lists.

+
+ New group, redesigned empty screen +

A newly created group

+
+ +

As of today, supergroups and basic groups are simply groups. It now takes just a few taps to make any group public, add admins with granular privileges or toggle persistent history.

+

Have fun bossing around groups the size of the city of Kassel!

+

Undo clearing history and deleting chats

+

Deleting the wrong chat is rarely fun – but now you'll have a chance to reconsider.

+

When you delete a chat or clear chat history, you'll get a detailed confirmation dialog and an option to restore the chat within the next 5 seconds. Once the time is up, the chat is irretrievably lost in the jaws of Telegram’s underground data shredders.

+
+ +
+ +

If you relied on “I accidentally deleted the chat with my homework” in your studies, please accept our apologies. From now on, you'll have to blame your digital dog.

+

Sort your contacts

+

Back to the topic of bossing people around, you can now sort your contacts by name and by last seen time on both iOS and Android.

+
+
+ Sorting contacts on iOS +

iOS

+
+
+ Sorting contacts on Android +

Android

+
+ +

Thumbnails and download animations

+

Waiting for large media downloads to finish ranks very low on the list of “The Most Exciting Things to Do Online”. We decided to spice this process up a bit by improving our animation algorithms and adding an ultra-light thumbnail to each photo and video:

+
+ +
+ +

From now on, every photo you receive will start its life as an obscure blur instead of an empty square. Isn’t this just beautiful?

+

Search bars, dark mode and moar profile pics

+

Search bars on Telegram for iOS and the default dark mode theme on Android got some face-lifting. The Android app also allows you to set up a profile picture when you create an account, so expect to see more friends with faces from now on.

+

Meanwhile on Desktop…

+

The new group permissions also work in Telegram Desktop. Additionally, version 1.5.8 introduces support for automatically downloading files and music and choosing input and output devices for Telegram Calls.

+

Last but not least, you can now change your visuals before heading into an emoji fight:

+
+ Choose your emoji on Telegram Desktop +

Choose how you see emoji on Telegram Desktop

+
+ +

Another glorious Telegram update is coming in a week or two, so STAY TUNED!

+

+ +

January 21, 2019,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/photo-editor-and-passcodes.html b/data/telegram.org/blog/photo-editor-and-passcodes.html new file mode 100644 index 0000000000..bc8ca9a721 --- /dev/null +++ b/data/telegram.org/blog/photo-editor-and-passcodes.html @@ -0,0 +1,252 @@ + + + + + Photo Editor and Passcode Lock + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Photo Editor and Passcode Lock

+ +
+ +
+ +

Today’s update to our iOS and Android apps reflects the essence of Telegram — a combination of easy-to-use privacy tools and popular mass market features.

+

Photo Editor

+

Each day Telegram users share 35 million photos, and this number is growing by the hour. For comparison, Instagram users shared 70 million photos daily in December. Yet up until now, messaging app users couldn’t enjoy a photo editing experience on the level that is offered by photo-sharing apps. We’re changing this today.

+
+
+ +
+
+ + +

With the new photo editor, you can crop, rotate and auto-enhance photos before sending them. On top of that, you can use Photoshop-class granular controls for brightness, contrast, warmth, saturation, highlights, sharpening, blurring and more.

+

The auto-enhance tool is our favorite though — it can improve photos in an instant.

+
+ + + + +
+
+ +

Passcode Lock

+

Telegram is one of the few messaging apps that can be used on multiple devices at once. While this is definitely convenient, it also raises the bar when it comes to privacy. What if one of your Telegram devices, e.g. an iPad or another tablet, is sometimes used by your colleagues or family members?

+

In order to give you more control in such cases, we are introducing passcodes. Starting today, you can lock your iOS or Android device with a passcode – a simple 4-digit PIN or a longer password. The iOS app, and soon the Android app as well, can use passwords to encrypt the local database against such extreme cases as phone theft.

+
+ + + + + + + + +

+
+ +Without entering this passcode, no one will be able to access your Telegram messages. When Telegram is locked, notifications about new messages will not include texts or sender names, so private data stays hidden from prying eyes. + +
+

+ +


+
+ +

Since unlocking Telegram each time can get annoying, we implemented both manual and auto-lock. You can lock the app manually from the chats screen or enable auto-lock after a specified period of inactivity. iOS users can use Touch ID to unlock the app.

+

+
+ +

February 25, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/pin-and-ifttt.html b/data/telegram.org/blog/pin-and-ifttt.html new file mode 100644 index 0000000000..71f1a39ad7 --- /dev/null +++ b/data/telegram.org/blog/pin-and-ifttt.html @@ -0,0 +1,263 @@ + + + + + Pinned Chats and IFTTT Integrations + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Pinned Chats and IFTTT Integrations

+ +
+ +
+ +
+ +
+ +

If you’re like us, you probably have dozens of active chats on Telegram. But none of them matter when you miss a new message from your Mom. Or Spouse. Or Mad Boss. Today we’re launching Telegram 3.15, which allows you to pin important conversations to the top of your inbox.

+

This feature is also valuable for teams that coordinate their work over Telegram. Pinned chats offer an easy way of keeping work-related chats reachable in a predictable order whenever you open Telegram.

+
+
+ +
+
+ +

To pin a chat, long tap on it (swipe left on iOS) and select Pin. Easy! You can pin up to 5 chats to the top (plus 5 secret chats).

+

IFTTT (If This Then That)

+

Starting today, you can link your Telegram account with more than 360 other services by setting up “If This Then That” integrations (or “Applets”). This works with anything from social networks like Twitter and Instagram, to productivity tools like Gmail or Pocket, entertainment apps like Spotify or Pinterest, cloud services like Dropbox or Google Drive, and Internet of Things devices like Nest, LIFX, or Philips Hue.

+

Telegram is the first messaging app to be fully integrated with IFTTT. Unlike most services, we allow two-way interactions: You can control other services via Telegram, or receive notifications and content like photos and videos when they do something.

+

You can also invite the @IFTTT bot to any of your groups so members can collaboratively interact with your services or devices.

+
+
+ +
+
+
+
+
+
+ + +

To get started, talk to the @IFTTT bot, then enable some Applets or create your own. Since the IFTTT platform supports over 360 services, endless combinations are possible. Here are just a few examples:

+ +
+

Check out the IFTTT website for a full list of existing Telegram Applets and don’t hesitate to create your own.

+
+

Making Android Great Again, Part 2

+

Remember our promise to Make Android Great Again? We were serious. In Telegram 3.15 for Android, we bring you three great features: High-precision rotation and cropping in the photo editor, a new player for Youtube videos with Picture-In-Picture mode, and forwarding messages and media to secret chats.

+

1. At long last, you can make that horizon look horizontal. Rotate your photos by any small number of degrees in the updated photo editor.

+
+ +

Rotate and Crop

+
+ + +

2. Want to continue chatting while watching a YouTube video? Tap the Picture-In-Picture icon in the new sleek video player for YouTube/Vimeo links. The video will shrink, and you can drag it around the screen so that it doesn't get in the way. The new video player also toggles fullscreen mode when you rotate your phone accordingly.

+
+ +

Picture-In-Picture

+
+ +

3. Secret Chats are the most secure way to share data on Planet Earth, and it is only natural they don’t let you forward stuff from them. However, they don’t restrict you from importing texts and media into them. With Telegram 3.15 for Android, you can forward messages and media from Cloud Chats and Channels to Secret Chats.

+

We know many of you got a bit addicted to Telegram updates, and keep asking us for more. We're happy to oblige. Stay tuned for more updates coming this December!

+


+ +

December 7, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/pinned-messages-locations-playlists.html b/data/telegram.org/blog/pinned-messages-locations-playlists.html new file mode 100644 index 0000000000..4ea6e28a60 --- /dev/null +++ b/data/telegram.org/blog/pinned-messages-locations-playlists.html @@ -0,0 +1,282 @@ + + + + + Pinned Messages 2.0, Improved Live Locations, Playlists and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+ +
+
+
+ +
+ Introducing Pinned Messages 2.0, Improved Live Locations, Playlists and More +
+ +

Halloween is just around the corner and we're introducing new features to help organize your trick-or-treating. Practice your voodoo skills with multiple pinned messages in every chat, watch out for other zombies on the block with Live Locations 2.0, put suspenseful music into Playlists, and more.

+
+

If you'd like to read about this update in simple English and without all most of the Halloween stuff, try this page.

+
+

Multiple Pinned Messages

+

Pinned messages are a lot like chips, it's hard to stop at just one, which is why you can now pin multiple messages in any chat. Tap the top bar to jump between them – or use the new button if you want to see them all on a separate page.

+
+ +
+ +

In addition to channels and groups, pinned messages now work in one-on-one chats, useful for everything from shopping lists to friendly wagers and beyond.

+

Improved Live Locations

+

When friends share their live location, you can set up an alert that will notify you when they're close. Icons on the live location map now also show which direction they are facing.

+
+ +
+ +

Never pass each other again when meeting on the street, even if everyone around (including you) is dressed up as a mummy.

+

Playlists

+

When you send multiple songs at the same time, they'll be arranged together in a playlist – easier to play, forward, or comment on. Opening one of the songs will queue them all up in Telegram's built-in media player.

+
+ Playlist sent to a chat +
+ +

Sending multiple files together also displays them in one chat bubble. Just like with photo albums, you can always select each file or track individually.

+

Channel Post Stats

+

Comments have boosted subscriber activity in channels, and now we're introducing new tools for admins to track it. In addition to channel statistics, you can view stats for individual posts in your channel – including a list of public channels to which your post was forwarded.

+
+ Channel post stats page +
+ +

Sleek New Animations on Android

+

Meanwhile, our Android Frankensteins keep adding new animations, this time for sending messages and switching songs in the music player.

+
+ +
+ +

Also on Android: when viewing a photo you’ve received, you can edit and send it back right away, skipping the download-upload ritual. Just tap the brush button when viewing a photo to quickly mark a spot with an X, or put skull stickers on faces.

+

Jackpot

+

Monaco is gradually reopening for tourists, but there is another way to try your luck: send 🎰 to any chat and see if you hit the jackpot.

+
+ +
+ +

In case you missed it, this also works for 🎲, 🏀, ⚽️ and 🎯.

+

And Ghoulishly Delightful Animated Emoji

+

Given the occasion, we couldn't help but animate every spooky emoji we could find. To get one of these 👇 in a chat, simply send a message with a single emoji. When viewing animated emoji for ⚰️ or 🎃, tap on them for an extra thrill.

+
+ +
+ +

Even if you don’t dig 🗿 all the Halloween hype, we’ve got you covered animated:
+ +
+ +
+ +

How to Get This Update

+

The new version with these features is already available for all our Android users via Google Play or APK. If you're on iOS, you'll get the update as soon as either a) Apple finishes reviewing it OR b) you decide it's time to switch to Android. 👀 UPD: (October, 31) The iOS part of the update has now also been approved.

+

Now we'll get back to working on our costume. We're going as the Ghost of Group Chats Past: 256 members, no moderation tools and completely covered in green slime. See you on the other side!

+

+ +

October 30, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/pinned-messages-locations-playlists/world.html b/data/telegram.org/blog/pinned-messages-locations-playlists/world.html new file mode 100644 index 0000000000..2bfa008998 --- /dev/null +++ b/data/telegram.org/blog/pinned-messages-locations-playlists/world.html @@ -0,0 +1,278 @@ + + + + + Pinned Messages 2.0, Improved Live Locations, Playlists and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+ +
+
+
+ +
+ +
+ +

Starting today you can pin several messages in every chat, get notified when friends get near if they are sharing their Live Location, send music as Playlists, and more.

+

Multiple Pinned Messages

+

Each chat now supports multiple pinned messages. To jump between them, simply tap the top bar several times – or use the new button to see all pinned messages on a separate page.

+
+ +
+ +

In addition to channels and groups, pinned messages now work in one-on-one chats.

+

Improved Live Locations

+

When friends share their live location, you can set up an alert that will notify you when they're close. Icons on the live location map also show which direction people are facing.

+
+ +
+ +

Playlists

+

When you send multiple songs at once, they'll be arranged together in a playlist – easier to play, forward, or comment on. Opening one of the songs will queue them all up in Telegram's built-in media player.

+
+ Playlist sent to a chat +
+ +

Sending multiple files together also displays them in one chat bubble. Just like with photo albums, you can always select each file or track individually.

+

Channel Post Stats

+

Comments have boosted subscriber activity in channels, and now we're introducing new tools for admins to track it. In addition to channel statistics, you can view stats for individual posts in your channel – including a list of public channels to which your post was forwarded.

+
+ Channel post stats page +
+ + +

New Animations on Android

+

Our Android developers added new animations for sending messages and switching songs in the music player.

+
+ +
+ +

Also on Android: when viewing a photo you’ve received, you can edit and send it back right away, instead of downloading and uploading it again. Just tap the brush button when viewing a photo to quickly draw or put stickers on it.

+

Jackpot

+

Send 🎰 to any chat to see if you hit the jackpot.

+
+ +
+ +

In case you missed it, this also works for 🎲, 🏀, ⚽️ and 🎯.

+

And More Animated Emoji

+

We've animated some new emoji for Halloween. To get one of these 👇 in a chat, simply send a message with a single emoji. When viewing animated emoji in chats, try tapping on ⚰️ or 🎃 for a surprise.

+
+ +
+ +

If you are not a fan of Halloween, we've got another new animated emoji for you:

+
+ +
+ +

How to Get This Update

+

The new version with these features is already available for all our Android users via Google Play or APK. If you're on iOS, you'll get the update as soon as either a) Apple finishes reviewing it OR b) you decide it's time to switch to Android. 👀 UPD: (October, 31) The iOS part of the update has now also been approved.

+

And that's it for today, stay tuned for the next update!

+

+ +

October 30, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/polls-2-0-vmq.html b/data/telegram.org/blog/polls-2-0-vmq.html new file mode 100644 index 0000000000..b0e6a10f83 --- /dev/null +++ b/data/telegram.org/blog/polls-2-0-vmq.html @@ -0,0 +1,271 @@ + + + + + Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode

+ +
+ +
+ +
+ Introducing Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode +
+ +

Since we first added polls for groups and channels, they've been used for everything from deciding where to have lunch to organizing leaderless protests. Today we're expanding the range of possibilities with three new kinds of Telegram polls.

+
+ +
+ +

Visible Votes

+

Previously, all polls on Telegram were anonymous. With this update, you can create polls that allow everyone in the group to see who voted for what. Now you will know exactly which friends you disagree with on the matter of pineapple and pizza.

+
+ A poll that shows who voted for which option +
+ +

Naturally, you can still create anonymous polls to make sure nobody finds out it was you who voted for broccoli instead of cookies.

+

Multiple Answers

+

One of the best ways to settle the score is with polls that allow people to select multiple answers. Scheduling events, or choosing a playlist of songs for a party – sometimes you need more than one choice.

+
+ A poll that allows people to select multiple answers +
+ +

Our aunt who has a knack for statistics and exploring bizarre correlations kept asking for this feature – and we just couldn't say no. (33% of developers who didn't refuse this request were also found to be addicted to cheese.)

+

Quiz Mode

+

For the game show guru and “Who Wants To Be A Millionaire” contestant in all of us, polls now have Quiz Mode. Such polls have one correct answer and can power anything from trivia games to public service exams.

+
+ Quiz mode +
+ +

As if guessing right wasn't sweet enough, correct answers will trigger a shower of confetti.

+

Creating Polls

+

Polls can be created in groups or channels (they feel lonely in one-on-one chats). Simply choose the “Poll” option in the attachment menu. Type in your question, add answer options, choose the settings that fit your purpose best – and you're ready to go:

+
+ +
+ +

Bot API and Quiz Bot

+

All the new poll types are supported in today's update to our Bot API, so bot developers can build on this new functionality.

+

As an example, we've created a Quiz Bot that lets you create multi-question quizzes and share them with others. It also lets you add text or media before questions to help create exam-style prompts with graphs and tables – or better yet, your own Know Your Meme tests.

+

Once your quiz is ready, you can share it to a group or channel – or invite users to answer questions privately, in a chat with the bot. To see how this works, try our demo quiz: Who is Who in the 'Great Minds' sticker pack.

+
+ Demo Quiz +
+ +

The bot will keep tabs on how many questions users got right and how much time it took them to complete the quiz. It also keeps a global leaderboard for each quiz you create.

+

Message Corners

+

In addition to the new polls, our apps just got a new visual setting. If you find your Telegram messages too hip to be square (or round, depending on your platform), you can tweak the appearance of message bubbles in Settings:

+
+ +
+ +

Download Progress Counters on Android

+

Just like on iOS, Android users can now see exact progress counters when downloading or uploading files – if they're in the mood to count bits and bytes.

+
+ Download progress counters on Android +
+ +

And that's it for today. Here's to a good new year full of updates. Stay tuned!

+

+ +

January 23, 2020
The Telegram Team

+
+ +
+ +
+ +
+
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/polls.html b/data/telegram.org/blog/polls.html new file mode 100644 index 0000000000..1c007defe0 --- /dev/null +++ b/data/telegram.org/blog/polls.html @@ -0,0 +1,230 @@ + + + + + Polls: Bringing Choice to Communities + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Polls: Bringing Choice to Communities

+ +
+ +
+ +
+ +
+ +

Large communities on Telegram frequently use polls to coordinate their activities and stay in touch with their members. Today, we're rolling out a dedicated tool for polls in addition to existing bots like @vote. We hope the new built-in polls will be a welcome addition to groups with 100,000 members and channels with millions of subscribers.

+
+ +
+ +

Polls can be forwarded to increase reach and pinned for better visibility (and also to notify all members of the community).

+

At the moment, polls are anonymous, meaning that no one can see who voted for what. Going forward, we may introduce non-anonymous polls where the voters lists will be public, but such polls will be explicitly marked as non-anonymous.

+
+

Telegram has your back when it comes to privacy: we never disclose the private data you entrusted us with to third parties and never monetize it.

+
+
+

Image Search and Other Improvements on iOS

+

Back to more mundane matters, you can use Web Search again to find images when sending Photo & Video attachments or choosing profile pictures in our iOS app. Setting a Grinch avatar for Christmas has never been easier:

+
+ +
+ +

The Great iOS Bug Hunt goes on and the app received numerous fixes in version 5.1.1.

+

To name a few improvements: Clearing the cache in Settings > Data and Storage > Storage Usage now correctly reduces the space taken by the app. Files and media will keep downloading for a while after you close the app. You will see detailed progress when downloading and uploading files. We've also added online indicators for the ‘People’ section in search results.

+

Happy Winter Solstice!

+

+ +

December 22, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/privacy-discussions-web-bots.html b/data/telegram.org/blog/privacy-discussions-web-bots.html new file mode 100644 index 0000000000..16a6dc3480 --- /dev/null +++ b/data/telegram.org/blog/privacy-discussions-web-bots.html @@ -0,0 +1,284 @@ + + + + + Focused Privacy, Discussion Groups, Seamless Web Bots and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Focused Privacy, Discussion Groups, Seamless Web Bots and More

+ +
+ +
+ +
+ +
+ +

Telegram is about privacy. In 2014 we pioneered granular privacy settings in messaging. Today we are making them even more flexible with exceptions for group chats.

+

From now on, you can make something visible for all your classmates in one group chat and keep it private from, say, all your colleagues in another – with just two taps:

+
+ +
+ +

Settings will adjust automatically as people join and leave the groups. So when your half-brother unexpectedly gets a job as a data broker, you'll just need to kick him out of one group to update all your settings.

+

Who can see my phone number?

+

On Telegram, you can send messages in private chats and groups without making your phone number visible. But there may be cases when you want to make your number known (e.g. to all your coworkers), so we added a new dedicated privacy control – Who Can See My Number.

+
+ A screenshot of the redesigned Privacy & Security settings screen +

Redesigned privacy settings on iOS

+
+ + +

Meet Seamless Web Bots

+

We've made it easier to integrate bots with web services. Bots can now help you log in with your Telegram account on a website when you open a link. If you allow them to, you'll be logged in by the time the page loads in the browser:

+
+ A confirmation dialog that offers to open a link and optionally authorize on the website +
+ +

While this is purely optional, it opens the door for a vast variety of new bots. To try out this seamless authorization, press the ‘comments’ button under this post.

+

You can also make our sample @discussbot an admin in any of your broadcast channels to get a comments button under the posts you publish. The comments button opens a website where you are already logged in and ready to leave a comment. The bot will notify you if someone replies to what you wrote there.

+

Anyone can create similar bots to connect their existing services to Telegram on the fly. Integrating all kinds of social, gaming, productivity, dating or e-commerce services into your channels is now a breeze.

+

Broadcasts meet Group Chats

+

Telegram channels are a tool for broadcasting your thoughts to unlimited audiences. Telegram group chats offer a democratic way for communities of up to 200,000 members to discuss things.

+

Ever since we launched channels and groups, users have been asking us to add discussions to channels and announcements to groups. With this update, admins can add a group chat to their channel to serve as a discussion board:

+
+ +
+ +

Subscribers will see a ‘Discuss’ link on the bottom panel, and each new post from the channel will be automatically forwarded to and pinned in the discussion group.

+
+ +
+ +

View public channels

+

Speaking of channels, you can now view any public channel from the web – even if you aren‘t logged in to Telegram. The same also goes for those retro people who don’t have a Telegram account at all. Yet.

+
+ A public channel, as seen from the web +
+ +

Simply open the channel link in a browser and select “Preview channel” to see something like this: t.me/s/telegram

+

Scam Alerts

+

Telegram apps will now show a scam label for suspicious accounts.

+
+ Chat with a scammer +
+ +

iOS Goodies

+

In other news, Telegram 5.7 for iOS introduces thumbnails for PDF files. Keep in mind that Telegram lets you share files of any type, up to 1,5GB each in size (so you can telegram a PDF payload worthy of Elon's rockets).

+
+ PDF file with a thumbnail +
+ +

Telegram for iOS also catches up with the rest of our apps in terms of text links. You can now make any text a link to a website, keeping all the cords under the carpet.

+
+ Creating a text link on iOS +
+ +

Mind that people will get a warning about where exactly the link leads when they open it. (Hint: use URL shorteners if you want to rick-roll people).

+

Android Delights

+

As for Android, we've redesigned the majority of confirmation dialogs in the app, and improved the design for message search and adding people to groups. Additionally, the app got a new theme switcher in Chat Settings.

+
+ +
+ +

Have fun with all that and stay tuned for our next updates.

+

+ +

May 31, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/privacy-revolution.html b/data/telegram.org/blog/privacy-revolution.html new file mode 100644 index 0000000000..f100e74092 --- /dev/null +++ b/data/telegram.org/blog/privacy-revolution.html @@ -0,0 +1,226 @@ + + + + + Hiding Last Seen Time - Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Hiding Last Seen Time - Done Right

+ +
+ +
+ +

Each day our volunteer-driven support team gets several thousand requests from our users to help them hide their Last Seen time. We knew it's important, and have been working hard to get this feature right. We wanted to make sure that Telegram users would have unprecedented precision and flexibility, without the usual tradeoffs.

+

Starting today, you can specify exactly who will see your Last Seen time in both our iOS and Android apps. You can choose between the three basic options (“Everybody”, “My Contacts” and “Nobody”) and add any number of exceptions into the “Always Share With…” and “Never Share With…” sections.

+
+

For example, this way you can make your Last Seen time available to everybody but your boss, or to nobody with the exception of your marriage partner (or vice versa, it's up to you). If you’d like to share your Last seen time only with your contacts plus the members of some work-related group you have, you can do it in just a few taps. This makes countless combinations possible.

+
+

Why Is This Important?

+

To make things fair, you won’t see Last Seen timestamps for people with whom you don‘t share your own. That’s why it‘s important to have granular controls — Telegram’s precision helps you avoid difficult choices. For example, you don't need to choose between hiding your Last Seen from your boss and being able to know when your best friend was online. You can have both.

+
+ + +
+
+ +

Last Seen Recently

+

Of course, the absence of a Last Seen timestamp makes it difficult to know whether the person you're about to contact is a regular user of Telegram and will be able to read your message. That is why even if the exact Last Seen time is hidden, you will still see an approximate value, like “last seen recently” (i.e. from one minute ago to about 3 days) or “last seen within a month”. This keeps stalkers away, but makes it possible to understand whether a person is reachable over Telegram.

+

Speaking of inactive users, we're not going to have too many of them soon. Starting today, Telegram accounts will self-destruct after 6 months of inactivity by default.

+

Self-Destructing Accounts

+

Big companies like to accumulate data about their users and keep it for an indefinite time. Telegram is not a commercial organization and we value our disk space greatly. Last year we introduced self-destructing messages, today we are adding self-destructing accounts.

+

From now on, if you stop using Telegram and do not login for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct – with options ranging from 1 month to 1 year.

+


+ +

These new features are already available in our iOS and Android apps. Stay tuned for more privacy-related updates.

+
+ +

The Telegram Team,
November 19, 2014

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/profile-videos-people-nearby-and-more.html b/data/telegram.org/blog/profile-videos-people-nearby-and-more.html new file mode 100644 index 0000000000..1d2c5e897a --- /dev/null +++ b/data/telegram.org/blog/profile-videos-people-nearby-and-more.html @@ -0,0 +1,315 @@ + + + + + Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

+ +
+
+
+ +
+ Introducing Profile Videos, Improved People Nearby, 2 GB File Sharing and More +
+ +

Today's update brings Profile Videos along with improved People Nearby features, unlimited file sharing with up to 2 Gigabytes per file, mini-thumbnails for your chat list and notifications, group stats, and much more.

+

Profile Videos

+

You can now upload a video to your profile – and choose any frame you like for your static profile picture in chats. Capture yourself in action, or wink and wave at people like you're in a magical picture from Harry Potter.

+
+ +
+ +

Same as with any videos you upload, our media editor will help you enhance quality – or decorate yourself with animated stickers.

+

As your mood changes, you can quickly switch back to a previous profile photo or video by tapping ‘Set as Main’. Great for rewinding time and staying young forever.

+

Soften Skin

+

Speaking of the media editor, any photo or video you take with the front-facing camera now has a soften skin option in the media editor. But you don't need it to look fabulous, you already are fabulous.

+
+ +
+ + + + +

Improved People Nearby

+

Profile videos make meeting new people a dozen times more interesting, and we've beefed up the People Nearby section for the occasion.

+

When people contact you via the People Nearby section, you will see how far away they are. And when you start a chat with someone nearby, Telegram will suggest a greeting sticker to break the ice. Luckily, all our stickers are extroverts.

+
+ Improved People Nearby +
+ +

Now that people are carefully emerging into this brave new world, it's time to make friends and repopulate the earth compare your sticker collections. Head over to Contacts > Find People Nearby and try tapping on ’Make myself visible’.

+

Mini-thumbnails

+

Ever wondered whether the incoming picture is just another meme or that selfie you've been waiting for? Get an idea of what media is in a message right away thanks to the new chat list thumbnails.

+
+ Mini-thumbnails in the chat list +
+ +

The new thumbnails also appear in notifications and message search results. Never lose a cat photo again.

+
+

Speaking of previews, you can hold on a profile picture in the chat list to preview messages without opening the chat. This feature is from 2018, but we had a dream in which a talking squid told us to mention it here.

+
+

Filter New Chats from Non-Contacts

+

Thanks to People Nearby and groups with up to 200,000 members, you can always find someone to chat with. Public figures sometimes have the opposite problem and may wish to tone down the attention they receive — we've got this covered too.

+

If you're getting too many messages from non-contacts, try the new switch in Privacy & Security settings to automatically archive and mute new chats from people not in your contacts. You can access these chats anytime from the Archive folder and bring them back to the main chat list in a tap.

+
+ +
+ + + +

Group Stats

+

Owners of large groups with over 500 members can now view beautiful, detailed graphs about their activity and growth. Group stats also show a list of top members by number of messages and average message length.

+
+ +
+ +

By the way, the minimum number of subscribers to get Channel Stats has been reduced to 500 as well. 🎉 We're planning to roll out access to group stats for admins of all groups with 100 members or more in the near future.

+

Android Extras

+

On Android, the music player has been redesigned with sleek new icons and an expandable track list. Tap the button on the left to control looping, shuffling and to reverse the track order so your playlist can moonwalk with you.

+

The message input bar will grow smoothly as you type a long message. And the video editor now allows cropping and rotating videos – to help you hide any evidence you were filming vertically.

+
+ +
+ +

Multiple Accounts on Telegram Desktop

+

Telegram lets you stay signed in on 3 accounts from different phone numbers without logging out. Our mobile users have been enjoying this feature since 2017, and today it's coming to the multi-platform Telegram Desktop.

+
+ +
+ +

As always, this doesn't require an active connection to your phone – all our apps are completely self-sufficient.

+

More Animated Emoji

+

Our animated emoji army keeps growing (note to self: build a bigger barracks). To get one of these 👇 in a chat, simply send a message with a single emoji – and watch it jump to life.

+
+ +
+ +

Be careful, one of them bites. And we're not allowed to tell you which one.

+

If you're looking for something more interactive, try sending a single ⚽️ in any chat to see if you score a goal:

+
+ +
+ +

And One More Thing

+

Since 2014, Telegram users have been sharing files up to 1,5 GB each, which happens to be 93 times larger than 16 MB (which is a totally random number, we have no idea what it could possibly mean).

+

From now on, you can send unlimited numbers of media and files of any kind – up to 2 GB each.

+
+

And that‘s it for today. We're now in the middle of the year — with eight major updates behind us and long-awaited features just around the corner. Stay tuned!

+

+ +

July 26, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/protected-content-delete-by-date-and-more.html b/data/telegram.org/blog/protected-content-delete-by-date-and-more.html new file mode 100644 index 0000000000..6da624710b --- /dev/null +++ b/data/telegram.org/blog/protected-content-delete-by-date-and-more.html @@ -0,0 +1,324 @@ + + + + + Protected Content, Delete by Date, Device Management and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Protected Content, Delete by Date, Device Management and More

+ +
+
+
+ +
+ Protected Content, Delete by Date, Device Management and More +
+ +

Today's update brings tools to prevent others from saving content in groups and channels, the ability to delete messages from specific dates, new ways to manage your connected devices, an option to post anonymously in public groups on behalf of your channel and more.

+

Protected Content in Groups and Channels

+

With this update, we're helping creators protect the content they publish on Telegram and ensure that it is available only for their intended audience.

+

Group and Channel owners who want to keep their content members-only can restrict message forwarding from their chat, which also prevents screenshots and limits the ability to save media from posts.

+
+ +
+ +
+

To change users' ability to forward messages open the Group or Channel Info page > Group / Channel Type > Restrict Saving Content.

+
+

Delete Messages by Date

+

Telegram users have complete control over their digital footprint and can delete any messages from a conversation at any time. With this update, you can clear chat history from a specific day or date range in any one-on-one chat.

+
+ +
+ +

To open the calendar, tap the date bar that pops up as you scroll through the chat – then choose which days to clear.

+
+

Clearing history by date currently only works in one-on-one chats, but messages in any chat can be set to auto-delete one day, week, or month after sending.

+
+

Manage Connected Devices

+

You can use Telegram on all your devices at the same time, and the Devices menu helps you control where your account is logged in. We've added a new button to quickly link a desktop device and a setting to automatically log out inactive devices after some time.

+
+ +
+ +

Tap any device in the list to view more information and toggle whether it can accept calls or new Secret Chats.

+
+

Telegram is available for every platform – check out telegram.org/apps to download the app on your other devices.

+
+

Anonymous Posting in Public Groups

+

Public Groups and Channel Comments allow for discussions of any topic in massive communities with thousands of members. These groups are used for everything from defending democracy to chatting with fans, which is why we've added the ability to appear as a channel when sending messages in these chats.

+
+ +
+ +

Tap the profile picture next to the message bar and choose one of your channels – the messages you send after that will appear with the name and photo of the channel instead of your personal account.

+
+

When posting as your channel, you’ll also see the channel name at the top of your message bubbles.

+
+

New Ways to Log In via Call

+

Starting today, some mobile devices will be offered the option to receive a login call from Telegram and then enter several digits of the phone number that called – instead of getting codes via text message.

+
+ +
+ +

Responses to Join Requests

+

When you request to join a group or channel and its admin responds with a message, you will see which community they are from at the top of the chat.

+
+ +
+ +

As of this update, bot admins can contact users requesting to join a chat where they are an admin — even if the user didn't communicate with the bot before. This opens up endless possibilities: from simply accepting the rules of a group chat before joining, to passing an admission test, to making a small donation to the creators of a channel.

+

Global Chat Themes on Android

+

Our September update introduced 8 new themes that you could set for individual chats – and now they're available for your entire app on Android (iOS users received this in the previous update).

+

Chat Settings have been fully redesigned, giving the new themes center stage. Built by the Telegram Team, every theme has a Day and Night mode, colorful animated background and gradient message bubbles.

+
+ +
+ +

Like all themes, you can personalize these designs and tweak the colors or change the pattern. For more options and custom settings, tap ‘Browse Themes’ to edit and share your creations.

+

Text Recognition on iOS 13+

+

On devices with iOS 13 and above, Text Recognition (Live Text) is enabled for photos in Telegram chats, allowing you to quickly select, copy and search without touching your keyboard. This image recognition is securely handled entirely on your device.

+
+ +
+ +

The list of supported languages is managed by Apple, so if yours isn't in the list yet, stay tuned for future OS updates.

+

Format Text in Media Captions on iOS

+

A little bit of bold or italics can add just the right emphasis to a message, and now you can use all text formatting options in media captions as well – including text links.

+
+ +
+ +

Before you ask why Android isn't getting this feature – it's because Android already has it. 😉

+

Redesigned Contact Info on iOS

+

Contacts, Groups and Channels have updated info pages with a new look in the style of iOS 15.

+
+ Redesigned contact info on iOS +
+ +

And that's it for now. Let's see how many more features we can build for you this year.

+

+ +

December 7, 2021
The Telegram Team

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/replies-mentions-hashtags.html b/data/telegram.org/blog/replies-mentions-hashtags.html new file mode 100644 index 0000000000..1afaafb35a --- /dev/null +++ b/data/telegram.org/blog/replies-mentions-hashtags.html @@ -0,0 +1,238 @@ + + + + + Reinventing Group Chats: Replies, Mentions, Hashtags and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Reinventing Group Chats: Replies, Mentions, Hashtags and More

+ +
+ +
+ +

Group chats have not evolved much since they first appeared in messaging apps many years ago. Today's new features bring group chat communication much closer to what it should look like in 2015. iOS, Android, OSX and Telegram Web get them first.

+

Replies

+

To reply to a specific message in a group chat, simply tap on it (double-tap on iOS) and choose Reply. Easy as that!

+
+ + + + + +

+ +

The person you replied to will be notified about your message even if s/he muted the group chat — their notification settings for you personally apply in this case.

+

Replies also make group chats much easier to navigate. If you tap on the quote, the app scrolls up to the original message.

+

Mentions

+

If you want several people within a group chat to get instantly involved in the conversation, you may now also mention them in a message, provided they have a username:

+
+ + +

+
+ +

They will be notified about this message, even if they muted the group chat — unless they've muted you personally, of course!

+

Hashtags

+

Another new way of bringing structure to group chats is by using hashtags. Any word starting with a “#” will be clickable. Tap on a hashtag to get instant search results from your Telegram messages.

+
+ + +
+
+ +

Forwarding with comments

+

On top of this, you can now add a comment to the stuff you forward. This comment will be shown before the forwarded messages.

+
+

Group chats are becoming larger and livelier — a Telegram group may include up to 200 members that share thousands of messages daily. We hope that these new tools will help you bring order and clarity to the chaos of a thriving group chat.

+

+ +

March 19, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/replies-mentions-stickers.html b/data/telegram.org/blog/replies-mentions-stickers.html new file mode 100644 index 0000000000..af38987e40 --- /dev/null +++ b/data/telegram.org/blog/replies-mentions-stickers.html @@ -0,0 +1,257 @@ + + + + + Better Replies, Stickers & Invitations + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Better Replies, Stickers & Invitations

+ +
+ +
+ +
+ +
+ + +

Since 2015 when we first introduced replies, the maximum group size on Telegram has increased by 100 times – from 200 max members to 20,000. These days you can get new mentions or replies in group chats many times during a day – and it’s important not to miss those messages.

+

Starting with Telegram 4.3, whenever somebody replies to you or mentions you in a group, you’ll notice this straight away by the ‘@’ badge in the chats list:

+
+
+ +
+
+ + +

If you have new replies/mentions in a group, you can now instantly reach them by tapping the new ‘@’ button when inside the chat. This button will disappear once you’ve read all the relevant messages.

+

Favorite Stickers

+

Anyone can create and upload stickers on Telegram. As a result, thousands of new stickers are added to the platform each day, and some of us have dozens of sticker sets installed.

+

Starting today, anyone with five or more sticker sets installed can mark individual stickers as ‘favorites’, and have them always accessible at the top of the sticker panel in the ‘star’ section.

+
+
+ +
+
+ +

Stickers of the Group

+

Speaking of stickers, large groups with 100 members and more can now choose an official sticker set for all the members of the group to see and use while they're chatting in the group — without the need of adding it to their panels.

+
+ +

Group Stickers

+
+ +

Invite Friends

+

The ‘Invite Friends’ section (accessible from Contacts) has been completely redesigned. Your contacts that are not on Telegram yet but have many of their friends already using it are now listed at the top. If you invite any of them to join, they’ll be welcomed by tens of Telegram veterans among their contacts:

+
+ +

Invite Friends to Telegram

+
+ +

…And More

+

As always with new releases, we've included several small goodies you may also like:

+
    +
  • Twitch videos are now supported in the Telegram in-app player, so you can watch Twitch streams in Picture-in-Picture mode while chatting with your friends.
  • +
  • When on a Telegram voice call, you can now check the signal strength thanks to the new indicator.
  • +
  • On iOS, you can edit any photo you pasted directly to a chat from clipboard before sending.
  • +
  • On Android, when forwarding a message, you can long tap to select multiple recipients.
  • +
  • On Android, when viewing photos in Shared Media, you can go to the place in chat where the photo was posted.
  • +
  • On Android, if you have many new messages in many active chats, synchronization will happen much, much faster.
  • +
+

+ +

Summer is over. Stay tuned, another update is already brewing in our dungeons!

+

September 3, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/scheduled-reminders-themes.html b/data/telegram.org/blog/scheduled-reminders-themes.html new file mode 100644 index 0000000000..6d9f505a90 --- /dev/null +++ b/data/telegram.org/blog/scheduled-reminders-themes.html @@ -0,0 +1,264 @@ + + + + + Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy

+ +
+ +
+ +
+ Introducing Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy +
+ +

In our previous update, we added a handy menu when you hold the send button. Today we're populating this menu with a new option that helps you plan ahead.

+

Hold the ‘Send’ button in any chat and select ‘Schedule Message’ to automatically send things at a specified time in the future (DeLorean not included).

+
+ +
+ +

Scheduling also works in your ‘Saved Messages’ chat, turning your planned posts into reminders. Be your own time-travelling secretary – whether it's about a dentist appointment next week, or waking up in time for pizza delivery.

+
+ +
+ +

Whenever a scheduled message or reminder is sent, you get a special notification marked with a 📅, so you don't get caught off-guard by messages you planned in the past.

+

Custom Cloud Themes

+

You could first customize Telegram's appearance way back in 2017. Today's update makes this easier than ever across all platforms, including our native desktop apps.

+

Choose a pre-set accent color or pick something unique from the color wheel, and the app will adjust all elements accordingly. See how it looks in your favorite color, blue – no, yellow!

+
+ +
+ +

You can now easily create new themes based on your color and wallpaper choices, then fine-tune them manually or share right away. Each theme has a sharing link which allows anyone to switch to your theme and wallpaper in just two taps.

+
+ Creating a new theme on iOS +
+ +

When you change your theme, it gets updated for all its users. This way you can update your app's looks to evolve as Telegram updates – or to change with the seasons.

+

To try out cloud themes, take a look at Sky Blue or Desert. These will work for both iOS and Android, and we solemnly swear to update them to acid green on orange when you least expect it.

+

Redesigned Message Options

+

On iOS, we have condensed message options into a single menu for forwarding, replying and more. You can now also select any portion of the message to copy or share, instead of only the full text.

+
+ +
+ + +

New Privacy Settings

+

Telegram groups can be public and may hold up to 200,000 members each. When launching them, we were thinking of campuses, conventions and spaces where you could properly brag about your cats. However, Telegram communities are also increasingly used by people to organize themselves in the face of oppression.

+

We believe that all people have a right to express their opinions and communicate privately. To further protect these rights, we‘re expanding Telegram’s arsenal of Privacy Settings today.

+

If you set Who Can See My Phone Number to ‘Nobody’, a new option will appear below, allowing you to control your visibility for those who already have it. Setting Who Can Find Me By My Number to ‘My Contacts’ will ensure that random users who add your number as a contact are unable to match your profile to that number.

+

If, like the majority of our users, you rely on uploading phone contacts to identify friends and family members on the app, this setting won't get in your way.

+

More Animated Emoji

+

Regardless of whether you‘re fighting for freedom or queuing for coffee, you’ll likely find a use for the new additions to our animated emoji family.

+

As before, send a single 😁, 😧, 😡, 💩, 😢 or 😮 to unleash their spirit in motion.

+
+ +
+ +

And that's all, folks! While waiting for our next update, check out this brief history of Telegram. Or, if you're not into reading, run a bath and enjoy these animated rubber duck stickers.

+

+ +

September 5, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/search-and-media.html b/data/telegram.org/blog/search-and-media.html new file mode 100644 index 0000000000..e7b6239671 --- /dev/null +++ b/data/telegram.org/blog/search-and-media.html @@ -0,0 +1,232 @@ + + + + + In-App Media Playback and Search in Chats + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

In-App Media Playback and Search in Chats

+ +
+ +
+ +

The new version of Telegram allows you to play media from services like YouTube, Vimeo or SoundCloud directly from Telegram – without having to leave the app. Just tap on the preview of a link to an external media to view the video or listen to the audio file (speaking of audio files, they are now beautifully rendered and played in chats).

+
+ + + + + +

+ +
+ +

The new attachment menu in Android is not only gorgeous and beautifully animated; it also allows you to share contacts, audios and recent photos way easier:

+
+ +
+
+ +

All of your communications in Telegram are already instantly searchable with the multi-purpose search field, but now you can also search for messages in specific chats. Just tap on the name of the chat in iOS or toggle the Actions menu in Android:

+
+ + + + + +

+
+ +

You will see the number of occurrences of the keyword in the chat and will be able to navigate through them with the up/down arrows. Enjoy!

+

+ +

The Telegram Team,
July 17, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/sessions-and-2-step-verification.html b/data/telegram.org/blog/sessions-and-2-step-verification.html new file mode 100644 index 0000000000..81108f82a9 --- /dev/null +++ b/data/telegram.org/blog/sessions-and-2-step-verification.html @@ -0,0 +1,220 @@ + + + + + Active Sessions and Two-Step Verification + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Active Sessions and Two-Step Verification

+ +
+ +
+ +

We know you love Telegram for its seamless multi-device sync. And since there are native Telegram apps for all major mobile, tablet and desktop OSs, a lot of you folks must be logged into your Telegram accounts from several devices at once.

+

Today's Telegram update, in addition to rich link summaries, adds Active Sessions to your Privacy and Security settings. This screen shows all your logged in devices with IP info. You can also close any sessions that are outdated or (God forbid!) suspicious.

+
+ +
+
+ +

Two-Step Verification

+

Another addition to the Privacy and Security section is Two Step Verification. It allows you to set up a password that will be required every time you log into your account from a new device – in addition to the code you get in the SMS.

+

Be careful though: if you forget this password, you won't be able to access your messages from other devices. We recommend setting up a recovery e-mail or at least a hint for your password, if you decide to turn on Two Step Verification.

+
+ +

+
+ +

Stay safe!

+

+ +

April 8, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/share-preview.html b/data/telegram.org/blog/share-preview.html new file mode 100644 index 0000000000..3196d9b936 --- /dev/null +++ b/data/telegram.org/blog/share-preview.html @@ -0,0 +1,269 @@ + + + + + Sharing and Previews + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Sharing and Previews

+ +
+ +
+ +

In addition to a major update to our Bot Platform, we're making several design and interface improvements to our apps today. This post mostly shows iOS screenshots, but be sure to check out the massive Android redesign we did in this version.

+

A fresh new look at sharing

+

Starting today, our iOS users can easily share photos and videos to other Telegram chats with a comment, or send them to other apps.

+
+
+ +

New sharing menu

+
+
+ +

Open in other apps

+
+ +

New video player

+

We've also added a new slick in-app media player so that you can watch videos from YouTube and other services in style. It will also take you fewer taps to start watching.

+
+ +

New in-app video player

+
+ +

Preview sticker packs and stickers

+

Adding new sticker packs has become easier. Tapping on any sticker in a chat will now instantly open the relevant sticker pack. You can preview and send stickers right from this menu. Now you won't have to teach your grandparents how to add stickers.

+
+
+ +

View sticker pack

+
+
+ +

Preview sticker

+
+ + +

Preview GIFs and bot content

+

On iOS, ‘Tap and hold to preview’ also works with GIFs in the GIF panel. Pull up for additional actions.

+
+
+ +
+
+ +

The same is true for content from inline bots. Tap and hold to preview results suggested by inline bots before sending. Try it now with @gif, @sticker or @coub.

+

Don't worry, this is coming soon to Android too! Speaking of which…

+

New design

+

The Android app received a major tuneup in the design department. We've redesigned the chat screen, optimized the colors, reimagined buttons and message bubbles, created beautiful progress bars, fully revamped documents and other attachments.

+
+
+ +
+
+ +
+
+ +
+
+ +

We've also improved the design of our iOS app, adding juicy progress bars and a new look for documents. Telegram Desktop has also received multiple design improvements and now fully supports the new bots.

+

+ +
+

Yes, don‘t forget that in addition to the above we’re introducing the biggest update to our bot platform since June 2015 today. Read more about Bots 2.0 »

+
+

+ +

April 12, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/shared-files.html b/data/telegram.org/blog/shared-files.html new file mode 100644 index 0000000000..c5af8c0350 --- /dev/null +++ b/data/telegram.org/blog/shared-files.html @@ -0,0 +1,231 @@ + + + + + Shared Files and Fast Mute + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Shared Files and Fast Mute

+ +
+ +
+ +

A huge advantage of Telegram over any other tool is sharing large documents. Since Telegram's launch in 2013, you can send files up to 1.5 GB and access them from any of your devices, including computers. Perfect for everything from studying to sharing personal archives.

+

For this iOS and Android update, we have fully rewritten the Shared Media section. From now on, you can use the ‘Files’ overview to see all documents that were shared in a chat. It is also possible to search for specific files using the instant search.

+
+
+ + + +

+
+ +

Any document you receive in Telegram can be forwarded to email or other apps – just open the file and tap on the Share button. In addition, Android users will find a ‘Share’ option in the file‘s context menu (tap on ’…' next to the file inside a chat).

+

Bonus for iOS users: Telegram is now supported in the iOS8 sharing menu – you can open it while you're viewing any document on your iOS device.

+

Mute Notifications

+

You can now temporarily mute notifications from particular contacts and groups for 1 hour, 8 hours or 2 days. On Android, open the ‘…’ menu in a chat and choose ‘Mute notifications’. On iOS, go to group or contact info and tap on Notifications. iOS8 users can now also use interactive notifications to mute a contact or group for 8 hours.

+
+
+ + + +

+
+ +

Multisearch

+

Instead of looking for the right search box, just type your query in the new universal search field and get instant results — contacts, chats, groups, usernames or messages.

+
+
+

+
+ +

February 1, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/shared-links.html b/data/telegram.org/blog/shared-links.html new file mode 100644 index 0000000000..f7034c0274 --- /dev/null +++ b/data/telegram.org/blog/shared-links.html @@ -0,0 +1,221 @@ + + + + + Shared Links and Recent Searches + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Shared Links and Recent Searches

+ +
+ +
+ +

Have you ever tried to find a link somebody shared in a busy chat? It’s not always easy. Of course, you could use message search, but now it's even easier – simply go to the new Shared Links section in Shared Media. Voila!

+
+ + +

+
+ +

You will see the text of the message that accompanied the link, or the rich preview data in case the link was sent by itself. This feature is currently available for iOS and Android, but will make its way to our other apps soon.

+

Recent Search Results

+

By the way, as of the previous update on both iOS and Android, tapping the universal search field now gives you quick access to recent search results.

+
+ + +

+
+ +

We‘re ramping up for massive updates this Fall. Stay tuned!

+

+ +

The Telegram Team,
August 20, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/silent-messages-slow-mode.html b/data/telegram.org/blog/silent-messages-slow-mode.html new file mode 100644 index 0000000000..9c474f5cd9 --- /dev/null +++ b/data/telegram.org/blog/silent-messages-slow-mode.html @@ -0,0 +1,296 @@ + + + + + Silent Messages, Slow Mode, Admin Titles and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Silent Messages, Slow Mode, Admin Titles and More

+ +
+ +
+ +
+ 5.10 update cover +
+ +

The previous update brought more movement to Telegram – this one brings more peace of mind. You can now message friends freely when you know they are sleeping, studying or attending a meeting.

+

Simply hold the Send button to have any message or media delivered without sound.

+
+ +
+ +

Your recipient will get a notification as usual, but their phone won't make a sound – even if they forgot to enable the Do Not Disturb mode.

+
+ Silent notification on the lock screen +
+ +

This also works in groups, should you get an urgent idea at five in the morning – but not urgent enough to wake up everyone in your work chat.

+

Slow Mode

+

In case a group you manage is getting hard to follow, the Group Permissions section now features a Slow Mode switch.

+
+ Slow Mode settings in the Group Permissions section +
+ +

When an admin enables Slow Mode in a group, you will only be able to send one message per the interval they choose. A timer will show how long you have to wait before sending your next message.

+
+ Slow Mode timer as seen in a user's input field +
+ +

Slow Mode can make conversations in the group more orderly, while raising the value of each individual message. Keep it on permanently, or toggle as necessary to throttle rush hour traffic.

+

Admin Titles

+

If new time-lord powers aren't enough, group owners can now set custom titles for admins like ‘Meme Queen’, ‘Spam Hammer’ or ‘El Duderino’.

+
+ Custom title section on the admin rights screen +
+ +

As with the default admin labels, custom titles are shown with every message in the group so members know that they‘re talking to the designated ’Myth Buster'.

+
+ A message from an admin with a custom title in a group +
+ +

To add a custom title, edit the admin's rights in Group Settings.

+

Timestamps and Improved Scrubbing

+

Videos now display thumbnail previews as you scrub through, to help you find the moment you were looking for.

+

If you add a timestamp like 0:45 to a video caption, it will be automatically highlighted as a link. Tapping on a timestamp will play the video from the right spot. This also works if you mention a timestamp when replying to a video.

+
+ +
+ +

Timestamps are also supported for YouTube videos, in case you want to mark your favorite moments when sharing a Kurzgesagt episode.

+

Animated Emoji

+

When you have animated stickers, why not go one step further and get animated emoji? To check them out, send a single ❤️, 👍, 😒, 😳 or 🥳 to any chat.

+
+ +
+ +

If your life feels a little too animated recently, Sticker Settings now offer a toggle for looped playback. When disabled, animated stickers will play just once then stay still.

+

Android's New Attachment Menu

+

Android’s attachment menu got a makeover, giving media more real estate. Larger thumbnails make it easier to pick photos and videos at a glance, and swiping up will reveal your full Gallery for better browsing.

+
+ +
+ +

You can scroll left and right through the other attachment options like locations, polls and music. When selecting media, tap ‘…’ to send items as uncompressed documents.

+
+ A screenshot of the options from the '...' menu +
+ +

Accent Colors for Night Mode on iOS

+

iOS users can now choose accent colors for night themes. The night doesn't always have to be black and blue, after all.

+
+ +
+ +

Comments Widget

+

Comments.App, our tool for commenting on channel posts, now lets you add a comments widget to your website.

+

With the widget in place, Telegram users will be able to log in with just two taps and leave comments with text and photos, as well as like, dislike and reply to comments from others.

+

They can also subscribe to comments and get notifications from @DiscussBot.

+
+ A screenshot of the Comments Widget featuring a photo sent as a reply to another comment +
+ +

Open this page in your browser to try the new widget – it doesn't support Instant View pages… yet. 😈

+

That’s all for now, and don’t worry — the next Telegram update won’t be sent silently.

+

+ +

August 9, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/stickers-meet-art-and-history.html b/data/telegram.org/blog/stickers-meet-art-and-history.html new file mode 100644 index 0000000000..bda6891a72 --- /dev/null +++ b/data/telegram.org/blog/stickers-meet-art-and-history.html @@ -0,0 +1,338 @@ + + + + + When Stickers Meet Art And History + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

When Stickers Meet Art And History

+ +
+ +
+ +

Today Telegram launched a new kind of stickers – a free emotion-based platform for artists. We mentioned several technological and architectural points that make Telegram stickers a completely new experience – open, free and limitless. But there’s another way in which they are unique, and it also has a lot to do with our values.

+

When designing our first set of stickers, we didn’t want to use just any cartoon characters to express emotions. Instead we decided to portray people we respect most. These are great artists, poets, actors, scientists and leaders.

+

We'd like to give them credit for their contributions to human civilization, and we hope that millions of Telegram users share our respect for these outstanding individuals.
Don't forget to check out Part 2: MOAR stickers!

+
+
+ +
+
Abraham Lincoln approves
+
+ +
+
+ +
+ + +
+
Salvador Dali unlocks achievement
+
+ +
+
+ +
+ + +
+
Albert Einstein explains
+
+ +
+
+ +
+ + +
+
Mahatma Gandhi likes where this is going
+
+ +
+
+ +
+ + +
+
Charlie Chaplin had a bad day
+
+ +
+
+ +
+ + +
+
Steve Jobs laughs out loud
+
+ +
+
+ +
+ + +
+
Kafka is not happy. He never is...
+
+ +
+
+ +
+ + +
+
John Lennon, but...
+
+ +
+
+ +
+ + +
+
Richard Wagner's told you
+
+ +
+
+ +
+ + +
+
Nikola Tesla is unimpressed
+
+ +
+
+ +
+ + +
+
One doesn't simply send a Tolkien sticker
+
+ +
+
+ +
+ + +
+
Mark Twain, huh?
+
+ +
+
+ +
+ +
+
That Freudian scowl...
+
+ +
+
+ +
+ + +
+
And the famous Monroe kiss
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/stickers-revolution.html b/data/telegram.org/blog/stickers-revolution.html new file mode 100644 index 0000000000..e60ea9afc4 --- /dev/null +++ b/data/telegram.org/blog/stickers-revolution.html @@ -0,0 +1,231 @@ + + + + + Custom Sticker Sets + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Custom Sticker Sets

+ +
+ +
+ +
+

Check out Pavel's Channel for some cool sticker sets »

+
+

Starting today, artists can submit their custom sticker sets via the Telegram @stickers bot. Each sticker set gets a permanent link, so that users can easily add new stickers and share them with friends.

+

This enables artists of the world to unleash their creativity and help Telegram users customize their experience. Our in-house artist (responsible for the graphic art in this blog) created the Animals set as an example. If you have Telegram installed and updated, this link will open the set: https://telegram.me/addstickers/Animals.

+
+ +

+
+ +

Independent designers already began submitting their sticker sets, and we notice stickers like Flags of the World or Vicky uploaded to the @stickers bot.

+

Sharing Stickers

+

Sending a link isn‘t the only way to share a sticker set. When you receive a sticker from a set you do not currently have installed, simply tap on it and choose ’Add to Stickers‘ (’Info' on iOS) to preview and add the whole set.

+
+ + +

+
+ +

Once you've added a set, its stickers become available via emoji tooltips or the dedicated sticker panel. The iOS app now has one too — you can manually switch it on/off in Chat Settings — Stickers.

+

The new Stickers menu allows you to view, uninstall and share your sticker sets.

+
+ +

+
+ +

This update is available for Android and iOS and is coming to other apps soon. Sticker sets on Telegram are now fully equipped to spread virally and devour the world.

+

+ +

The Telegram Team,
May 19, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/stickers.html b/data/telegram.org/blog/stickers.html new file mode 100644 index 0000000000..c970ba1480 --- /dev/null +++ b/data/telegram.org/blog/stickers.html @@ -0,0 +1,225 @@ + + + + + Stickers Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Stickers Done Right

+ +
+ +
+ +
+

This January 2015 post has some outdated info.
Check out our custom sticker sets announcement instead.

+
+

At Telegram, we try to reinvent the ordinary tools. The concept of stickers is not an exception. We've always felt that stickers in messaging apps sucked, because they typically provided a limited and paid experience in a walled-garden environment.

+

Today's update to Telegram for Android, iOS, Windows Phone and Desktops introduces a new kind of stickers – a free platform for artists and users willing to share emotions, built using an efficient and open technology.

+
+ + + + + +
+ +

Telegram stickers are grouped around emotions, not characters. They do not clutter the interface, but are shown only when they are relevant – you will see a list of emotionally corresponding stickers whenever you start a message with an emoji. All our stickers are and will be completely free, and you can always create and share your own stickers.

+

You can find the initial 14 stickers in this post.
And dozens more will soon follow.

+

Sharing your own stickers

+

To share stickers of your own, just save your sticker in WebP format with a transparency layer and send it to your friend as a document in Telegram (e.g. via Telegram Desktop). It will be shown as a sticker. Thanks to the WebP file format, Stickers on Telegram are displayed 5x faster compared to the other formats usually used in messaging apps.

+

Creating new stickers

+

Telegram is focused on people who like to create content. If you want your sticker to be seen by all Telegram users in the context menu corresponding to one of the emojis, you are welcome to submit it via a chat with our Stickers bot – telegram.me/stickers.

+

Freelancers can also sell us their work – we normally pay $100 for the exclusive use of a 512x512px sticker. Note that we accept only high-quality stickers that meet our criteria. Please study the stickers that we have designed in-house for the launch.

+
+
+ +

January 2, 2015
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/supergroups.html b/data/telegram.org/blog/supergroups.html new file mode 100644 index 0000000000..97a041bc98 --- /dev/null +++ b/data/telegram.org/blog/supergroups.html @@ -0,0 +1,251 @@ + + + + + Admins, Supergroups and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Admins, Supergroups and More

+ +
+ +
+ +

Telegram groups are democratic by design. Everyone can invite new members and change the group‘s name and photo, which is ideal for small bands of friends or coworkers. But Telegram can also support much larger communities that need more administration. To make life easier in big groups, we’re introducing admins today.

+

From now on, you can choose how your groups will operate. By default, all members are still in control. But if you want more order, you can throw the switch and appoint additional administrators to your group.

+
+ +

+
+ +

If you enable the new restricted mode, only administrators will be able to add new people and change the name and photo of the group. Admins also have the power to remove other members from the group.

+

Supergroups

+
+

UPD: Check out Supergroups 2.0: Pinned posts, Public groups, new moderation tools!

+
+

Telegram groups have always been several steps ahead of the competition. You could have groups of up to 200 people communicating efficiently using replies, mentions and hashtags. Now it's time to go further.

+

Ever since our launch in 2013, our users have been telling us they would like to migrate even larger communities to Telegram. As of today, once your group is full, you can upgrade it to a supergroup that supports up to 5000 members.

+
+ +

+
+ +

Supergroups are optimized to host large online communities and will load quickly, even if you‘ve missed many messages while away. Here’s what you need to know about how they work:

+
    +
  • New members can see the entire message history when they join.
  • +
  • Deleted messages will disappear for all members.
  • +
  • Ordinary members can only delete their own messages.
  • +
  • Supergroups are muted by default and send fewer joined/left notifications.
  • +
+

All official Telegram clients are getting this update today.

+
+

Please note that you need the latest version of Telegram to access a supergroup. You may want to wait a little bit before upgrading your groups so that the update rolls out to all Telegram users, and they can see their groups.

+
+

iOS Bonus: Best In-App Notifications Ever

+

iOS users will enjoy our new in-app notifications. Pull down on a notification to expand it, view the full text of the message or preview attached media.

+
+ +

+
+ +

You can immediately send a quick reply or a sticker — all without leaving that particular spot in some other conversation.

+

Android Bonus: Quick Share for Channels

+

Meanwhile, Android users can enjoy the new quick sharing menu in channels. Just tap on the forwarding buttons right next to channel messages.

+
+ +
+
+ +
+

We have a few more surprises up our sleeve for this year. Stay tuned for more updates!

+

+ +

The Telegram Team,
November 25, 2015

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/supergroups5k.html b/data/telegram.org/blog/supergroups5k.html new file mode 100644 index 0000000000..efe0b447f1 --- /dev/null +++ b/data/telegram.org/blog/supergroups5k.html @@ -0,0 +1,232 @@ + + + + + Supergroups 5000: Public Groups, Pinned Posts + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Supergroups 5000: Public Groups, Pinned Posts

+ +
+ +
+ +

Telegram is famous for its awesome group chats. Today’s update makes them even more awesome. To begin with, we’re increasing the number of people who can join a supergroup from 1000 to 5000 members. That's 5 times as good.

+

Supergroup admins can now inform all members about important news using pinned messages. Pinned messages are displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from the group.

+
+ +

A pinned message

+
+ +

Starting today, supergroups can become public and get a short link, like telegram.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

+
+ +

A public group

+
+ +

We know what you’re thinking. What about spammers? To prevent potential spam issues, we're introducing powerful moderation tools for group admins. From now on, they can quickly delete all messages from a specific member, block and report them.

+
+ +

New tools for admins

+
+ +

These features work only in supergroups, but starting today, any group can be converted to a supergroup by its creator. Group admins are now shown in group members’ lists, so ping your group admin if you think this would be cool.

+
+

Good old groups still work great for smaller communities, so there's no need to convert your group right away.

+
+

And that's it for today, watch out for more updates coming soon!

+

+ +

March 13, 2016
The Telegram Team

+

+ +

P.S. Please note that we’ll be rolling out public groups gradually. They’re already live in Europe and America, but are currently not available in several countries in Asia, from which we detected significant spam activity in the past.

+

We’ll be making the feature available in more countries as we improve our anti-spam algorithms and scale our abuse team.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/tdlib.html b/data/telegram.org/blog/tdlib.html new file mode 100644 index 0000000000..60d1a1c77b --- /dev/null +++ b/data/telegram.org/blog/tdlib.html @@ -0,0 +1,228 @@ + + + + + TDLib – Build Your Own Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

TDLib – Build Your Own Telegram

+ +
+ +
+ +
+ +
+ +

Telegram offers developers more than just the Bot API. Since day one, we've also had a free and open Telegram API that allows anyone to create their own messaging apps operating in the Telegram cloud. These apps openly compete with the official ones and some of them have now reached more than 10 million downloads on Google Play.

+

Users of these alternative clients can communicate with anyone on Telegram, but the apps often offer experimental, highly specialized or locally flavored features. Today we are introducing a new tool for third-party developers that will make it even easier to build fast, secure and feature-rich Telegram apps on our platform.

+

Introducing TDLib

+

Meet TDLib – the Telegram Database Library. TDLib takes care of all network implementation details, encryption and local data storage, so that developers can dedicate more time to design, responsive interfaces and beautiful animations.

+
Universally useful
+

TDLib supports all Telegram features and makes developing Telegram apps a breeze on any platform. It can be used on Android, iOS, Windows, macOS, Linux and virtually any other system. The library is compatible with any programming language that can execute C functions; it also has native bindings to Java and C#.

+
Open and well-documented
+

All TDLib API methods and public interfaces are fully documented. The code is, of course, completely open and available on GitHub.

+
Secure and reliable
+

TDLib will remain stable on slow and unreliable Internet connections and guarantees that all updates will be delivered in the correct order. All local data is encrypted using a user-provided encryption key.

+
Optimized for performance
+

The library is fully asynchronous and optimized for high performance. We use TDLib in the Telegram Bot API, where each TDLib instance handles more than 18,000 active bots simultaneously.

+
Battle-tested
+

Our new Android X client is an example of what can be done with TDLib. Using TDLib, it took the developer of the app approximately one year to reproduce all the major features of Telegram for Android – and add plenty of his own.

+

+ +

Let's see what else TDLib will help bring to the Telegram ecosystem this year.

+

January 31, 2018,
The Telegram Team

+

+ +
+

P.S. Today, we're also introducing Telegram X for Android, a new official app.
Check out the announcement here »

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegram-5-ios.html b/data/telegram.org/blog/telegram-5-ios.html new file mode 100644 index 0000000000..3e94c9e1eb --- /dev/null +++ b/data/telegram.org/blog/telegram-5-ios.html @@ -0,0 +1,268 @@ + + + + + Introducing Telegram 5.0 for iOS + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Introducing Telegram 5.0 for iOS

+ +
+ +
+ +
+ +
+ +

For the last couple of years we've been quietly rebuilding Telegram for iOS from scratch with Swift – a programming language released by Apple as a faster alternative to Objective C.

+

Today Telegram 5.0 goes live for all our iOS users, becoming the most popular messaging app written fully in Swift. This new version of Telegram looks just like the old one, but is slicker, more battery-friendly and faster (which is surprising, given how fast the old one already was).

+
+ +
+ +

The new app is superior in many ways. We love the new smooth animations in chats. Messages will now sync quickly, even if you haven‘t opened Telegram for a long time and there’s a LOT to sync. We‘ve also improved the app’s activity in the background to ensure that all of your unmuted chats are always up to date.

+

Step aside — and back

+

The new expandable in-app notifications will help you focus on whatever you‘re doing in the app without having to ignore incoming messages. When a notification arrives, pull it down to open the relevant chat. When you’re done with the interruption, simply close it to get right back to what you were doing.

+
+ +

Expanded Notification

+
+ +

This works everywhere in the app, including when you are viewing media or reading Instant View articles.

+

Make every chat count

+

Previously, badge counters could become less useful after you've joined a group or two with 100,000 members. Today we're making private chats great again.

+

You can now switch the unread counter to display the number of unmuted chats with unread messages. So instead of 1001 for a thousand messages in a muted group and one very important message from your dog, your badge counter will look like this:

+
+ +

One Unread Chat

+
+ +

You can adjust this behavior in Settings > Notifications and Sounds.

+

When was that again?

+

We've improved navigation in busy chats (and elsewhere). Scroll up a little to see the date when the messages you are viewing were sent. Tap this date to go to the first message of the day in question.

+

The bugs are dead. Long live the bugs!

+

As much as we would‘ve liked to, we couldn’t port over any of the bugs from the Objective C version. All the old bugs are now gone forever — or, should we say, fixed. We might‘ve added some brand new bugs while coding the new version. But don’t worry, we'll fix those in no time. The same goes for any small features that may be missing.

+

Meanwhile on macOS…

+

You can now use swipe gestures to navigate the interfaces on Telegram for macOS. Most notably, you can swipe to reply and the chats list now works the same way it does on iOS: swipe right to Mark as Read/Unread, and left to Pin, Mute or Delete.

+
+ +

Swipe Left or Right for Options

+
+ +

Fancy MacBook Pro owners just got advanced Touch Bar support to help them send stickers and media, control buttons in alerts and pop-up windows and more.

+
+ +

Stickers and more on MacBook Pro

+
+ +

Other new features include auto-night mode settings and a photo editor to rotate and crop pictures before sending. You can also drag and drop photos, media, and documents to change the order in which they will be sent.

+

…And Telegram Desktop

+

As for our universal Telegram Desktop app, it just got a massive overhaul in the Settings department. The new layout is similar to what you're used to in our mobile apps:

+
+ +

Telegram Desktop Settings

+
+ +

The latest Telegram Desktop also features improved caching for images and GIFs, as well as new local storage settings. Go to Settings > Advanced > Local Storage to control how much disk space Telegram uses on your machine.

+

We've also redesigned the theme selector to make it easier to choose a day and night theme that suits you best. Remember, you can make your own themes – or check out some themes created by other users.

+
+ +

Pick Your Colors

+
+ + +

And that's it for today. Stay tuned for more updates on all our platforms.

+

+ +

October 1, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegram-me-change-number-and-pfs.html b/data/telegram.org/blog/telegram-me-change-number-and-pfs.html new file mode 100644 index 0000000000..a1e2f9bdc0 --- /dev/null +++ b/data/telegram.org/blog/telegram-me-change-number-and-pfs.html @@ -0,0 +1,228 @@ + + + + + Telegram.me, Changing Numbers and PFS + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram.me, Changing Numbers and PFS

+ +
+ +
+ +
+

Our iOS and Android apps got updated with three new features today.

+
+

Opening a telegram.me/YourUsernameHere link on your phone will now automatically fire up your Telegram app and open a chat with that user. You can share username links with friends, write them on business cards or put them up on your website.

+
+ +
+ +
Here's what people will see if they don't have Telegram yet
+ +

Changing Your Phone Number

+

It is easy to switch to Telegram and retain your social graph, since it is based on phone numbers. But what if you need to change the phone number itself? As of today, you can change your number in Telegram — and keep everything, including all your contacts, messages and media from the Telegram cloud, as well as all your secret chats.

+
+ + + +
+
+ +

Your mutual contacts (people in your contacts, who also have your number) will get your new number added to your contact in their address book unless you have blocked them in Telegram. This makes changing numbers even easier.

+

Perfect Forward Secrecy

+

Last but not least, Telegram's Secret Chats now support Perfect Forward Secrecy. What this means is that your Secret Chats will now automatically change encryption keys after a period of time, in order to keep past communications safe. This way you no longer need to manually re-create Secret Chats to achieve this level of security.

+

+ +

And that's it for today. Stay tuned for more updates coming your way on all platforms!

+
+

December 1, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegram-x.html b/data/telegram.org/blog/telegram-x.html new file mode 100644 index 0000000000..1a46515ba4 --- /dev/null +++ b/data/telegram.org/blog/telegram-x.html @@ -0,0 +1,262 @@ + + + + + Telegram X: Progress through Competition + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram X: Progress through Competition

+ +
+ +
+ +
+ +
+ +
+

UPD: As of October 2018, Telegram X for iOS has replaced the older Objective-C based client. If you're looking for the best iOS experience, switch to the main Telegram app.

+
+

Our mission is to make Telegram faster, slicker and easier to use with each passing month. Competition is the soul of progress, so at first we got plenty of inspiration from other messengers that spurred us on. But as years passed, we saw less and less innovation coming from competitors, who now seem content merely to adapt Telegram features to their platforms with an average lag of two years.

+

In this environment, we started relying on internal competition to feed our flames. This is why for the last two years we've been developing a new generation of Telegram clients in parallel with the main versions.

+

The Telegram X project features apps written from scratch, with an entirely new code base and without all the legacy components that our older apps have accumulated through the years.

+

Telegram X

+

The goal of Telegram X is to reinvent Telegram and explore new frontiers in speed, ease of use, quality of animations and all other aspects. Today we are glad to present two new official apps – Telegram X for Android and iOS.

+

Both these apps are experimental and may or may not eventually replace the existing official apps. But even if they don't, they will speed up the development of Telegram by allowing us to quickly test new approaches and technologies.

+

X for Android

+

Telegram X for Android was born in the furnaces of a contest for Android developers that our founder launched two years ago. The winner then used the power of TDLib to create a stunning app with a special focus on smooth animations.

+

X for Android is faster and more battery-efficient than the original app and features a sleek new design:

+
+ +
+ +

Telegram X also supports a clean bubble-free mode for chats, where messages and photos get more breathing space – and photos in channels assume the full width of the screen:

+
+ +

Bubble-free Photo in a Channel

+
+ +

In Telegram X, you can tap and hold on any chat to preview its content without opening. This works everywhere, including in the forwarding and sharing menus, as well as in the Calls tab and ‘Groups in Common’.

+

The app also offers an abundance of useful swiping actions. For example, you can switch between ‘Chats’ and ‘Calls’ by swiping left and right on the main screen. You can also swipe right on any message to instantly open the forwarding menu:

+
+ +

Swipe right to share

+
+ +

The app includes a reimagined music player and attachment menu, as well as optimized profile pages with quick access to shared media. You can easily switch between different types of shared media by swiping.

+
+ +

New profile page with shared media

+
+ +

This is by no means an exhaustive list of features, Telegram X for Android is full of little surprises in every corner.

+

The app is now ready to begin its experimental journey with new features scheduled to appear as early as next week.

+

X for iOS

+
+

UPD: As of October 2018, Telegram X for iOS has replaced the older Objective-C based client. If you're looking for the best iOS experience, switch to the main Telegram app.

+
+

Telegram X for iOS is written entirely in Swift and is significantly lighter, faster and more battery-efficient than the original app, built with Objective C.

+

The design and feature set are closer to what iOS users have learned to expect from Telegram, but you will definitely notice the smooth animations and faster speed and loading times on most iPhones.

+

The internal structure of Telegram X for iOS is also much better optimized for the things that are expected of a Telegram app in 2018 and beyond. Just as with X for Android, today's X release for iOS is the beginning of a long journey.

+

+ +

Look out for our next updates, both to the experimental versions and their classic counterparts.

+

+ +

January 31, 2018,
The Telegram Team

+

+ +
+

P.S. Today, we're also releasing TDLib – a tool for building custom Telegram apps. Check out the announcement here »

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/telegraph.html b/data/telegram.org/blog/telegraph.html new file mode 100644 index 0000000000..7dbb2cb8f0 --- /dev/null +++ b/data/telegram.org/blog/telegraph.html @@ -0,0 +1,238 @@ + + + + + Meet the Telegraph API for Logins and Stats + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Meet the Telegraph API for Logins and Stats

+ +
+ +
+ +
+ +
+ +

Last month, we launched Telegra.ph, a minimalist publishing tool that allows you to create richly formatted posts and push them to the Web in just a click.

+

We tried to keep Telegraph‘s interface as simple as possible: there’s no need to log in or navigate menus. You just open telegra.ph, write your post, hit publish, and it's live.

+
+ +

Yes, it's that simple

+
+ +

Better with Bots

+

This simplicity has its price of course. Sometimes you want to edit your articles on several devices or stay logged in to avoid having to write your name and profile link under each new title. If any of this sounds familiar, meet our new @Telegraph bot.

+

This simple bot will help you log in and manage your Telegraph posts across any number of devices. In addition, it can give you page view statistics for any post on Telegraph. Just send it a link and watch the numbers roll in.

+

A Time to Gather Stones

+

If you have created some Telegraph posts in the past using browsers on your different devices, the @Telegraph bot helps unite them all under your rule.

+
+
+ +

A time to log in

+
+
+ +

And a time to gather posts

+
+ +

Simply press the Log in on this device button, and all posts you‘ve previously written in that device’s browser will be added to your Telegraph account.

+

Telegraph API

+

Mind you, Telegraph is not intended just for Telegram users. Anyone can use this dead-simple publishing tool. For those who are suffering the constraints of other messengers and can't enjoy the comfort offered by the @Telegraph bot, we have created an open Telegraph API.

+

Using the Telegraph API, any developer can create bots like @Telegraph for any other platform, or even standalone interfaces.

+
+

Here's the full documentation, in case you're interested.

+
+

Meanwhile, allow us to return to our coding dungeons where we're brewing another update to our apps for you this year.

+

+ +

December 20, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/themes-accounts.html b/data/telegram.org/blog/themes-accounts.html new file mode 100644 index 0000000000..829b00b601 --- /dev/null +++ b/data/telegram.org/blog/themes-accounts.html @@ -0,0 +1,247 @@ + + + + + Themes, Multiple Accounts and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Themes, Multiple Accounts and More

+ +
+ +
+ +
+ +
+ +

Happy winter holidays, everyone! To reinforce the festive mood, we‘re updating Telegram for the second time this December, adding features you’ve been asking for.

+

With version 4.7 for iOS, you can change what your Telegram looks like in the new Appearance settings. Choose between four different themes, including a minimalistic one (“Day”) and two dark themes (“Night” and “Night Blue”). The “Day” theme also allows you to pick an accent color for the entire app, like pink or purple.

+
+ +
+ +

Multiple accounts

+

The Android app already supported multiple themes, so it had to go further with 4.7 by supporting multiple accounts. You can add up to three accounts with different phone numbers to your Telegram app, and then quickly switch between them from the side menu. Notifications will keep coming from all accounts, unless you change this in the Notification settings.

+
+ +
+ +

Quick replies

+

Telegram now supports quick replies on both mobile platforms. To use them, just swipe left on any message in a chat.

+
+
+ +
+
+ +

In case you missed it…

+

Telegram 4.6, released earlier this month, introduced new granular settings for auto-downloading media, better link previews, albums in Secret Chats, improved security, and embeds for messages from public groups and channels. Here’s what an embed of a Telegram message looks like when included on a web page:

+

+ +

+
+ +

To get the HTML-code for embedding a message, open its t.me link in a web browser:

+
+
+
+ +

Have a happy new year – and stay tuned for the product updates we are going to announce in January.

+

+ +

The Telegram Team,
December 30, 2017

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/translations-iv2.html b/data/telegram.org/blog/translations-iv2.html new file mode 100644 index 0000000000..d61a63107a --- /dev/null +++ b/data/telegram.org/blog/translations-iv2.html @@ -0,0 +1,276 @@ + + + + + Custom Languages, Instant View 2.0 and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Custom Languages, Instant View 2.0 and More

+ +
+ +
+ +
+Introducing custom languages, IV 2.0, a new design for Android and more +
+ + + +

Telegram's Translations Platform allows you to suggest better wording for Telegram interfaces in any language. We've recently rolled out support for most mainstream languages, and translations are already underway.

+

Today's update brings equal treatment to the smaller linguistic communities around the world. Anyone can now use the translation platform to create their own custom language packs – and translate Telegram into any minority language or local dialect, be that Māori, Scottish Gaelic or Transliterated Klingon.

+

We've made it easy to spread your translations. To translate the interface of your app, simply follow the dedicated sharing link of the desired language. Sharing links can be obtained in the translation panel.

+
+ Applying a custom language +
+ +

Each language also gets its own public group for discussions. Here are the links for the Catalan language, for example:

+ +

Once a user switches to your translation, all changes you apply in the interface will be applied immediately. The days of waiting for the apps to update or passing around localization files are over.

+

Instant View 2.0

+

Another unique feature of Telegram is the Instant View technology that allows Telegram users to view web pages in a consistent way, with zero loading time.

+

Today we're expanding the platform with support for right-to-left languages, blocks of related articles, image links, tables, nested lists, horizontal scrolling, collapsible text blocks and much more.

+

Now you can get beautiful instant view pages for even very complex articles. If you're reading this from one of our newly updated mobile apps, try this Wikipedia page for an example.

+
+ +
+ + + +

Soon we will announce a new crowdsourcing contest to make Instant View pages available for an even larger part of the internet.

+

The Great iOS Bug Hunt

+

We've made close to a thousand fixes and improvements to the iOS app since the major release of version 5.0. The new Telegram for iOS 5.1 features some 400 minor improvements.

+

New Design for Android

+

Telegram for Android has now reached version 5.0 and received a major overhaul in the design department. It is now much easier to access shared media from the profiles of users, groups and channels:

+ + +
+ +
+ +

Shared media now offers high quality crisp previews, increased loading speed, more info in the links and files sections, and more efficient design.

+
+ Shared Files +
+ +

The Settings screens were redesigned for a more streamlined experience:

+
+ +
+ +

Following in the footsteps of the iOS app, Android users can take advantage of the new detailed settings for the badge counter in Settings > Notification and Sounds:

+
+ Badge Counter Settings +
+ +

We've upgraded the photo selector for profile pictures so that you can choose the correct head to be displayed on your profile:

+
+ Choose an area to use for the photo +
+ +

Last but not least, you can zoom videos during playback and browse full-resolution images sent as documents just like normal photos, by swiping left and right.

+

+ +

December 10, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/trending-stickers.html b/data/telegram.org/blog/trending-stickers.html new file mode 100644 index 0000000000..6ea0731043 --- /dev/null +++ b/data/telegram.org/blog/trending-stickers.html @@ -0,0 +1,262 @@ + + + + + Trending Stickers, Storage and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Trending Stickers, Storage and More

+ +
+ +
+ +

Telegram users share hundreds of millions of stickers every day. Many of these are custom-created on the spot using pictures of friends or local politicians. Others are made by professional artists from all over the world. Starting today, we will be showcasing popular sticker sets made exclusively for Telegram in the new Trending Stickers tab.

+
+
+ +

Sticker panel

+
+
+ +

Trending tab in settings

+
+ +

You can find the new Trending tab on the Stickers panel and in Telegram Settings. We've made adding new stickers easier for people who have many sets installed. When you go over the limit of 200 sets, older unused stickers are archived automatically. You can reactivate them from the Archived Stickers tab in Sticker Settings later.

+

Personal storage

+

Many people have been using a chat with themselves or a small group to store their favorite messages or personal media. Starting today, there's no need for such lifehacks anymore. Just head to the Contacts tab and open the storage chat with yourself by tapping on your number at the top.

+
+
+ +

New contacts screen

+
+
+ +

Your storage chat

+
+ +

Feel free to forward favorite messages to the storage chat or send photos you want to quickly pass between devices. The handy ‘Shared Media’ sections will make finding content a breeze and you can always use in-chat Search for specific queries.

+

You can also access everything you send to the storage chat on any number of devices you connect, so this can serve as a simple but effective way to replace services like Dropbox right inside your messenger.

+

Group previews

+

Invite links are a handy way to add people to groups, even when they‘re not on Telegram yet. Today we’re making it easier for you to understand just what you're joining when you open them.

+
+ +

New group previews

+
+ +

As of Telegram v.3.11., you will be able to see who else is in the group and how many members it has before joining it.

+

Android Camera and More

+

If you're running Android 4.1. or higher, Telegram just got a brand new camera interface so that you can take photos in fewer taps. It is also now possible to preview bot content before sending.

+
+
+ +

Bot content preview

+
+
+ +

Check out before sending

+
+
+ +

Another nice bonus in this Android update is that you can now download large media and files 2x to 4x faster.

+

New looks and new viewer for Telegram Desktop

+

Telegram Desktop users can now enjoy an in-app player for videos. We've also improved the design in chats, adding sleek new message bubbles.

+
+ +

New desktop video player

+
+ + + +

And that‘s about all we’ve got for you in version 3.11.
As usually, stay tuned for more updates – coming after our little summer break.

+

+ +

August 3, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/unread-replace-2x.html b/data/telegram.org/blog/unread-replace-2x.html new file mode 100644 index 0000000000..3b20dcf11b --- /dev/null +++ b/data/telegram.org/blog/unread-replace-2x.html @@ -0,0 +1,259 @@ + + + + + Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More

+ +
+ +
+ +
+ +
+ +

Telegram 4.8.3 for iOS and 4.8.10 for Android are out today, bringing several nifty features and improvements.

+

Replace Media and Add Captions

+

Sending the wrong picture by accident is rarely fun. On Telegram, it was already possible to delete the message for everyone and send a new one instead. Now you can just replace photos or videos with the correct versions right away:

+
+ +
+ +

Start editing the message, then tap the paperclip button to replace the attached media. You can also add captions to photos or videos that didn't have one.

+

Double-Time Playback for Voice and Video Messages

+

You'll like this one if your friends enjoy sending long and thoughtful voice notes. From now on, you can switch to 2X playback and hear people get to the point faster.

+
+ +

Works with voice and video messages

+
+ +

We‘ve spent a few extra hours to ensure that your friends don’t sound like Helium-breathing chipmunks as a result. Well, most of the times.

+

Mark as Read or Unread

+
+ +
+ +

This offers a quick way to get less important messages out of the way and highlight the chats that require your future attention.

+

Share Detailed Contact Info

+

Sometimes you want to share more info about a contact than just one number. With this update, you can select what data you want to send when sharing a contact. For example, several phone numbers or other vCard fields.

+
+ +

Choose which fields to share

+
+ +

Try sharing a contact that has multiple fields with data to check this out.

+

One More Thing

+

When you open a chat from Global Search and then go back, you will return to the search results and keep your position in the list.

+

And Three More (on Android 💪)

+

Android users are getting a few extra goodies with version 4.8.10. Tap and hold on profile pictures in the chats list to preview chats:

+
+ +

Tap and hold on the profile picture

+
+ +

Use the “create link” option in the formatting menu to make text URLs:

+
+ +

Select some text, then tap '...'

+
+ +

Last but not least, it is now possible to cancel sending messages before they are sent.

+

And that's it for today, stay tuned for our next updates!

+

+ +

June 27, 2018
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/unsend-and-usage.html b/data/telegram.org/blog/unsend-and-usage.html new file mode 100644 index 0000000000..b4b9878776 --- /dev/null +++ b/data/telegram.org/blog/unsend-and-usage.html @@ -0,0 +1,273 @@ + + + + + Unsend Messages, Network Usage, and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Unsend Messages, Network Usage, and More

+ +
+ +
+ +
+ +
+ + +

Happy new 2017! We hope everybody had a great celebration. We at Telegram certainly did. One of our engineers got so excited about the new year that he mistakenly shared these stickers with his Mom:

+
+ +

Ooops!

+
+ +

To fix this, he quickly added a way to unsend recently sent messages. This smart move saved his morning, and it can still save yours! If you use Telegram v.3.16, you can now unsend any weird messages you shared within the last 48 hours.

+
+ +

Works in groups and PM

+
+ +

Naturally, this isn‘t a one-time feature. After this update, you’ll be able to retract any messages within 48 hours of sending them. Take that, Friday nights!

+

Network usage

+

The holiday season is in high swing in many parts of the world, so we figured some of you folks are busy traveling. If that's the case, you may want to check out the new Network Usage section that shows exactly how much data you consumed while in roaming or wi-fi or whatever.

+
+
+ +

Data and Storage

+
+
+ +

Network Usage

+
+ +

Don't forget to hop on the hotel wifi before any serious Telegramming in foreign lands. And remember that you can toggle automatic media download in Telegram Settings.

+

T.me Links

+

This is the perfect season to meet new people. Want to give them some contact information, but a phone number seems like too much? That's exactly the reason we added usernames and Telegram.me links waaay back in 2014.

+

Starting today, you can use t.me instead of telegram.me. Take a napkin, write t.me/username in no time, and give it to someone before they can get away!

+

This also works with channels:
t.me/telegram
Public groups:
t.me/snowballfight
And stickers:
t.me/addstickers/NickSantini

+

Android Developers Never Sleep

+

85% of Telegram users are on Android. Our CEO is worried that, if ignored, this Android population can start a rebellion and dethrone him. To please the mob, he made us introduce the following features to the Android app:

+
    +
  • Messages from one sender are now neatly grouped together, and scrolling up shows the date right away, making the chats easier to navigate.
  • +
  • The app now restores your previous scroll position when you switch back to a chat. Very useful when somebody sends you a saga in 1,000 messages, and you want to patiently read them in the right order.
  • +
+
+ +

That's the date up there

+
+ +
    +
  • Sharing files (a feature we had since forever) has become easier because you see a list of recently downloaded files right on the sharing screen.
  • +
+
+ +

Recently downloaded files

+
+ +
    +
  • We now support GBoard, the Google keyboard that can apparently send cat GIFs.
  • +
  • And for those 2 users that already have Android 7.1 installed, we are happy to announce that we've added a fast action menu with frequent chats to your home screen. All hail the early adopters!
  • +
  • Back to the important stuff: the cowboy, the clown, and the sick face emoji (also known as the ‘exfoliating green tea mask face’ emoji) have found their way to Android. We support all of them now.
  • +
+
+ +

New emoji

+
+ +

What do these emoji mean? When are you supposed to use them? Is the singular form of ‘emoji’ in fact ‘emojus’? To answer all these questions with utmost accuracy, we've also added support for this one:

+
+ +
+ +

+ +

January 3, 2017
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/unsend-privacy-emoji.html b/data/telegram.org/blog/unsend-privacy-emoji.html new file mode 100644 index 0000000000..510f91e58c --- /dev/null +++ b/data/telegram.org/blog/unsend-privacy-emoji.html @@ -0,0 +1,261 @@ + + + + + Taking Back Our Right to Privacy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Taking Back Our Right to Privacy

+ +
+ +
+ +
+ Unsending messages, anonymized forwarding, improved search and VoiceOver/TalkBack support +
+ + +

For us, your private data is sacred. We never use your data to target ads. We never disclose your data to third parties. We store only what is absolutely necessary for Telegram to work.

+

In 2013, we gave millions of people power over their data with end-to-end encryption.

+

Today, we are giving hundreds of millions of users complete control of any private conversation they have ever had. You can now choose to delete any message you have sent or received for both sides in any private chat. The messages will disappear for both you and the other person – without leaving a trace.

+

Unsend Anything

+

The “Unsend” feature we introduced 2 years ago was only available for messages sent by you and only for 48 hours. Now you can remove messages you have sent or received, and there is no time limit. You can also fully delete any private chat from both your and the other person's device in just two taps.

+
+ +
+ +

Anonymous Forwarding

+

To make your privacy complete, we’ve also introduced a way to restrict who can forward your messages. When this setting is enabled, messages you send that are forwarded by another user will no longer lead to your profile – instead they will show your display name in plain unlinked text. This way the messages you send can't be used to verify that you were their author.

+
+ +
+ +
+

You can enable this option in Settings > Privacy and Security > Forwarded Messages.

+
+

By the way, you can now also restrict who can view your profile photos.

+

Settings Search

+

Since the Settings section keeps getting bigger, we’ve added a search tool that allows you to quickly find the settings you're looking for.

+
+ +
+ +

You can also use this tool to find answers for Telegram-related questions based on our FAQ.

+
+ +
+ +

Emoji Search and GIFs

+

GIF and Sticker Search has been upgraded on all mobile platforms – with an updated interface that looks better (and finds more cats). You can press and hold to preview a GIF before sending.

+

Sticker packs now have unique icons, which makes it easier to select the right set. Large GIFs and video messages on Telegram are now streamed, so you can start watching them without waiting for them to fully download.

+

On Telegram for Android, you can now use keywords in many languages to find a specific emoji. If we are missing a keyword for an emoji, you’re welcome to suggest it here – emoji search results will constantly update and improve in real time, without the need to update your Telegram app.

+
+ +
+ +

You’ll also see a list of related emoji when typing a message. If you like an emoji enough to send it without any accompanying text, the emoji will appear larger in the chat.

+

VoiceOver and TalkBack

+

We’ve added support for screen-reading features – VoiceOver on iOS and TalkBack on Android. These accessibility platforms give spoken feedback so that you can use Telegram without needing to see the screen.

+
+

Tell us what you think the next update should be.

+
+

March 24, 2019
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/usernames-and-secret-chats-v2.html b/data/telegram.org/blog/usernames-and-secret-chats-v2.html new file mode 100644 index 0000000000..509d6a1637 --- /dev/null +++ b/data/telegram.org/blog/usernames-and-secret-chats-v2.html @@ -0,0 +1,222 @@ + + + + + Usernames and Secret Chats 2.0 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Usernames and Secret Chats 2.0

+ +
+ +
+ +

Telegram apps for both Android and iOS have been updated today.

+

Usernames

+ +

From now on, you can choose a public username in the Settings section of Telegram. If you do, anyone will be able to find you by your username and contact you – without having to know your phone number.

+

To find people by username, just start typing any name in the search field of the Contacts section. Once entered at least 5 characters, you will see the Global Search section in your search results. This list contains people with corresponding usernames.

+

You can find out more details about usernames in our FAQ.

+ +

Secret Chats 2.0

+ +

Secret Chats got a major upgrade today.

+ +

The self-destruct timer in Secret Chats now includes more small values ranging from 1 to 60 seconds. In chats with these shorter self-destruct timers, the countdown for photos, videos and voice messages will begin only after they are first opened. So the content will never disappear before you have seen it or listened to it.

+ +

Photos with short self-destruct timers now work in 'Tap and Hold to View' mode, and you will receive a notification each time the recipient of a self-destructing photo makes a screenshot of it.

+ +
+ +
+
+ +

October 23, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/verifiable-apps-and-more.html b/data/telegram.org/blog/verifiable-apps-and-more.html new file mode 100644 index 0000000000..277dc0b29d --- /dev/null +++ b/data/telegram.org/blog/verifiable-apps-and-more.html @@ -0,0 +1,392 @@ + + + + + Verifiable Builds, New Theme Editor, Send When Online and So Much More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Verifiable Builds, New Theme Editor, Send When Online and So Much More

+ +
+ +
+ +
+ Dude in a jacket inspecting the hologram of a mechanical dog to verify it's built according to the blueprints provided. +
+ + + +

Telegram is the only mass market messaging app with open source apps. Since 2013, this not only allows independent researchers to verify the integrity of end-to-end encryption, but also helps look for vulnerabilities (or backdoors 😈).

+

As of this update, Telegram becomes the first messaging app to allow you to independently verify that the code on GitHub is the exact same code that was used to build the app you downloaded from App Store or Google Play. Security researchers are welcome to check out our Guide to Reproducible Builds for iOS and Android.

+

But we know security isn't the only reason you love Telegram – so we've also added dozens of new features and improvements. Gather round, this blog post is a long one.

+

Theme Editor 2.0

+

Using the new theme editor in Chat Settings (or Appearance Settings on iOS), you can quickly tweak the style of elements in Telegram chats and add awesome gradients to both your messages and your background. Switch between tabs (Main Color, Background, My Messages) to see how deep this rabbit hole goes:

+
+ +
+ +

Once you're done editing, you can quickly share the result of your work with friends so that they can continue tuning your theme.

+

By the way, this update includes dozens of new cool patterns you can apply to your background. Our favorites are the Math and Parisian motifs, but there's also one we made especially for New Year's Eve.

+
+ Screenshot demonstrating some of the new background patterns. +
+ +

There are new patterns with cats as well. And space. And cats in space. No time to explain, go check them all out.

+ + +

New Predefined Colors

+

Not in a creative mood? Not a problem – we've added a boatload of new predefined color schemes for Telegram's default themes. The theme of your dreams may be just a few taps away, try the new options under Classic, Night, Day, etc.

+
+ +
+ +

Send When Online

+

Some things are best served fresh, like sushi and today's hot memes. For messages that have to be delivered at the perfect moment, we've added the option to schedule messages to be sent when your recipient comes online.

+

Now you can slide your message in with the morning post – or time a funky duck sticker for the exact moment a meeting gets boring.

+
+ +
+ +

Note that this option is only available if you are allowed to see your recipient's online status. You can still sneak out of bed without anyone noticing.

+

Improved Venue Sharing

+

Location sharing has been updated to make finding venues easier. You can now tap a place directly on the map to select it, rather than scrolling through a list of all the power converter purveyors in Tosche Station.

+
+ +
+ + +

View Search Results as a List

+

The Search function allows you to easily jump between messages containing a keyword – or sent by a particular person, or even from a certain day. Tapping the bottom bar will now switch to list view in case you want to see all the results on one page.

+
+ +
+ +

On iOS, you can also select several messages without leaving Search Mode. (Before you ask, this feature was already available on Android.)

+
+ Screenshot showing several messages selected in a chat on iOS – without leaving the Search Mode. +
+ + +

Podcast and Audiobook Support

+

You've always been able to share files of up to 1,5 GB, but podcasts and audiobooks now get special treatment. Telegram apps will remember your last position when resuming playback of audio files longer than 20 minutes.

+

If you'd like to make podcasts get to the point a little faster, try the new 2x button (which you already know from voice messages). We've eliminated voice chipmunking in 96.8% of cases.

+
+ Screenshot showing the location of the 2x playback button for long audio files. +
+ +

On iOS, you can skip forward and back with high-precision scrubbing: just hold on the progress bar and slide your finger down, then left or right.

+

New On Android

+

Switch to Night Mode Faster

+

Telegram has shielded your eyes in dark places with Night Mode since 2017. The power of the sun and moon are now even easier to control, with the Night Mode Switch at the top of the menu. Tap the moon icon and watch the sun rise and fall at your whim.

+
+ +
+ +

Maps have also joined the dark side in Night Mode, so you don't accidentally burn yourself while browsing locations late in the evening. Ve do as the count vills. (•,..,•)

+
+ A shared location on a map in Night Mode on Telegram for Android. +
+ +

On iOS, dark maps turn on and off with the system dark mode. Speaking of which, we recently added the option to sync your Telegram theme with system dark mode on iOS 13.

+ + +

Sleek New Animations

+

We've peppered the interface with little ripple animations when you press on things to help you get more joy out of buttons. Snappy new animations await when jumping between messages in a chat, opening global search or pulling out the archive folder. To get a closer look at a user's profile picture, drag down on their profile page.

+
+ +
+ +

Select Parts of Messages

+

Following in the footsteps of the iOS app, Android now also lets you select a portion of the message text to copy or share, instead of only the full text. Sometimes you only want a slice, rather than the whole pie.

+
+ +
+ +

Multi-sharing from Other Apps

+

Sharing is caring, so we've made it easier than ever to share content from other apps with your friends. You can now tap and hold to select multiple recipients – and even add a comment in case your savage subtweet needs some context.

+
+ +
+ +

Mark Archive as Read

+

A cluttered chat list reflects a cluttered mind. Clear up those extra unread message counters in your archive by tapping and holding the archive folder and marking them all read. (Not to be confused with marking it red, that's a job for themes.)

+
+ Mark all messages as read in the Archive on Android. +
+ +

And Other Android Goodies

+

You can сhoose video quality in a more intuitive way when sending videos.

+
+ New button for selecting video quality when sending a video. +
+ +

Sending contacts now uses a simple, card-style interface that won't take up your whole screen (unless you pull up to expand it).

+
+ New contact sharing screen. +
+ +

When you're done listening to a voice message with your phone up to your ear, Telegram automatically records a reply - but now you can disable that by turning off Raise to Speak in your Chat Settings.

+

We found 31 other shiny bugs to fix and improvements to make on Android, just in time for your Telegram advent calendar. See if you can find them all.

+

New on iOS

+

Text Size, All the Way

+

You've been able to adjust the size of message text on Telegram from the beginning, but now you can scale the font size throughout the app. I'm not sure if Grandma reads this blog regularly, so you may have to tell her yourself.

+
+ Telegram for iOS with enlarged font. +
+ +

Choose Your Browser

+

External browsers are now supported for opening links – you can select your preferred app in Settings > Data and Storage > Other.

+
+ Browser settings screen. +
+ +

Share Sheet Settings

+

Your most popular Telegram chats were recently added to the iOS Share Sheet. In case you'd like to control what can (or can't 😉) appear there, you can use the new toggles under Settings > Data and Storage > Other > Share Sheet.

+
+ Share Sheet settings screen. +
+ +

Switch Accounts Faster

+

Superman has had a hard time finding phone booths lately, so we added a way to swiftly switch accounts right from your home screen on iOS 13. Simply hold down on the app icon any time you need to change costumes.

+
+ App menu on an iOS 13 home screen, featuring a 'Switch Account' button +
+ +

Remember that you can use Telegram with multiple accounts, switching between up to 3 phone numbers without logging out.

+

Storage Usage At a Glance

+

The Storage Usage page has been redesigned to more quickly find the settings you're looking for. It also shows your device's storage status, and how much space all those other pesky apps are using compared to Telegram. Bigger, after all, is not always better.

+

You did know that with Telegram there's no need to store every silly meme people ever sent you on your precious device, right?

+
+ Storage Usage settings screen. +
+ +

Cache-Clearing Shortcuts

+

Selecting multiple messages in a group or channel gives you the option to clear the chat's cache. Like we said, no need to store what you don't need – but also no need to delete actual messages. Just keep things in the cloud, like the cool kids.

+
+ Clear Cache button in a channel. +
+ +

Check out Settings > Data and Storage > Storage Usage for more options.

+

Member Lists: The Shorter Scrolls

+

In case you're looking to leave some large groups and start fresh in the new decade, long member lists will collapse, so you can get to the 'Leave Group' button without scrolling.

+

By the way, swiping on a group or channel from the chat list and selecting 'Delete' is still the shortest way out, but now there is more than one way to leave the New Year's party early.

+
+ Group members screen with a collapsed member list. +
+ +

And that's all for today. Happy New Year!

+

2020 is going to be fun. Enjoy winter while we get back to our little warm R&D bunker deep deep underground.

+

+ +

December 31, 2019,
The Telegram Team

+

+ +
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/video-1000.html b/data/telegram.org/blog/video-1000.html new file mode 100644 index 0000000000..849a17bd81 --- /dev/null +++ b/data/telegram.org/blog/video-1000.html @@ -0,0 +1,354 @@ + + + + + Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

+ +
+ +
+
+ +
+ Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More +
+ +

This update takes video to the next level. Group video calls now have up to 1000 viewers, video messages record in higher quality and can be expanded, regular videos may be watched at 0.5 or 2x speed. We've also added screen sharing with sound to all video calls, including 1-on-1 calls — and much more.

+

Group Video Calls 2.0

+

Group video calls allow up to 30 users broadcast video from both their camera and screen – and now 1000 people can watch anything from online lectures to live rap battles.

+

We will keep increasing this limit until all humans on Earth can join one group call and watch us yodel in celebration (coming soon).

+
+ +
+ +
+

To start a Group Video Call, create a Voice Chat from the info page (in the ⋮ menu on Android) of any group where you are an admin – then turn your video on.

+
+

Video Messages 2.0

+

Video messages are a quick way to check in or share your surroundings without adding another video to your gallery. They now have higher resolution and you can tap on a video message to expand it and take in all those extra pixels.

+
+ +
+ +

Tapping on an expanded video message pauses it and gives you the opportunity to fast forward or rewind the message in case you missed a word.

+
+

To record a video message, tap the microphone icon in the message bar to switch from voice message recording to video. Press and hold to record, then tap the camera icon to switch back.

+
+

Audio from your device will keep playing as you record so you can now sing along to your favorite songs or reply without pausing your podcast. Additionally, recording with your rear camera lets you pinch to zoom in and capture things at a distance or add a dramatic effect (eerie music not included).

+

Video Playback Speed

+

To power through lecture videos and replay kung fu moves in slow motion, the media player now supports 0.5x, 1.5x and 2x playback speeds. Our Android developer is a fan of hummingbirds, so his app also supports 0.2x speed.

+
+ +
+ +
+

To change your video playback speed, tap ⋮ on Android or ⋯ on iOS when watching a video in fullscreen.

+
+

On Android, you can also press and hold the 2X button when playing voice or video messages to switch between 0.5x, 1x, 1.5x and 2x playback speed.

+

Timestamp Links

+

Since 2019, putting a timestamp like 0:30 in the captions or replies to videos and YouTube links lets users jump to that exact second – and you can now press and hold on a timestamp in a message to copy the link and share the moment in another chat.

+

Screen Sharing With Sound

+

Screen sharing has been added to 1-on-1 calls as well, and now includes the sound from your device when broadcasting in any video call. So make sure you quit Super Mario before its your turn to present — or don't, and use the game for sound effects.

+
+ +
+ +

When switching on video during any call, you can swipe to choose a camera or share your screen instead — and use the video preview to make sure that everything is perfect before going live.

+ + +
+

To share your screen during a video call, tap the camera button and select your screen as the video source.

+
+

Auto-Delete After 1 Month

+

Messages in any chat can be set to erase themselves after 1 day or 1 week – and now 1 month, in case you need your chats to stick around for a full lunar cycle before disappearing.

+
+ Auto-Delete After 1 Month +
+ + + +
+

To enable the timer on Android, tap ⋮ > Clear History then choose a duration. On iOS, press and hold a message, tap Select > Clear Chat (top-left) > Enable Auto-Delete.

+
+

Precision Drawing

+

The media editor allows you to illustrate and decorate your photos and videos with drawings, text and stickers. To more easily add fine details (or that perfect mustache and pointy ears), the width of your brush now decreases as you zoom in – giving you the precision of a professional.

+
+ +
+ +
+

To change the width of your brush at any time, drag the dot up from the color selector.

+
+

The Telegram Desktop app now has its own photo editor to crop, rotate or flip images – and add drawings or stickers. Unique to desktop, your edited versions can be sent as uncompressed files by unchecking the Compress Images box.

+

Passcode Animations

+

New animations make the passcode lock interfaces even snappier than before. If you're using an animated background, it will also appear on the passcode lock screen. The disco never stops.

+
+ +
+ +

Password Recovery and Reminders

+

We've added a new prompt in Settings to help you practice entering your Two-Step Verification password.

+
+ Practice Your 2-Step Verification Password +
+ +

If you forgot your password, there is a new password reset option that works even if you don’t have a recovery email — as long as you're still logged into your account. The process will take 7 days and can be cancelled from any of your devices.

+

Message Sending Animations on Android

+

Like emoji and stickers, text messages have new lightweight animations – when you hit Send, your text smoothly transforms into the message bubble as it flies into the chat. iOS users received these energy-efficient animations in the previous update.

+
+ +
+ +

New In-App Camera on iOS

+

The in-app camera now utilizes all zoom levels on your device – including 0.5x and 2x if available. You can also press and hold to open a zoom wheel that lets you zoom in and out with granular control.

+
+ +
+ +
+

To use the in-app camera, tap the 📎 icon in the message bar and then tap the camera feed in the attachment menu.

+
+

More for iOS

+

Choose multiple recipients for forwarded messages by tapping 'Select' in the forwarding menu to share your best memes with all your best friends.

+
+ Forwarding to multiple recipients +
+ +

Scrolling with two fingers in the chat list quickly selects several chats for bulk actions like archive, delete or mark all as read.

+ + + + +

Profile pictures now follow the messages as you scroll in group chats so you always know who sent each one, even in long chains of one. word. after. another.

+
+ +
+ +

New Animated Emoji

+

No Telegram update is complete without new animated emoji. As always, simply send a message with a single emoji to get one of these in a chat:

+
+ +
+ + +

And that's all for today's update – we're working on the next one at 2X speed.

+

+ +

July 30, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/video-calls.html b/data/telegram.org/blog/video-calls.html new file mode 100644 index 0000000000..95c93e6e3f --- /dev/null +++ b/data/telegram.org/blog/video-calls.html @@ -0,0 +1,234 @@ + + + + + Video Calls and Seven Years of Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Calls and Seven Years of Telegram

+ +
+
+
+ +
+ Video Calls and Seven Years of Telegram +
+ +

Today marks seven years of Telegram. In 2013, we began as a small app focused on secure messaging and have since grown into a platform with over 400M users. Telegram is now one of the top 10 most-downloaded apps and is used all over the world to stay in touch with family, collaborate with classmates and coordinate coworkers.

+

We did not reach this milestone on our own – Telegram has never advertised and every user has come to the app because of a recommendation from someone they trust. Strong principles and quality features speak for themselves, and millions of you listened. We've heard you as well, and will continue to develop features that make Telegram much more than just a messaging app. Today we're adding the one you've been asking for – fast and secure video calls.

+

Video Calls

+

2020 highlighted the need for face-to-face communication, and our alpha version of video calls is now available on both Android and iOS. You can start a video call from your contact's profile page, and switch video on or off at any time during voice calls. Like all other video content on Telegram, video calls support picture-in-picture mode, allowing you to scroll through chats and multitask while maintaining eye contact.

+
+ +
+ +

All video calls are protected with end-to-end encryption. To confirm your connection, compare the four emoji shown on-screen for you and your chat partner – if they match, your call is 100% secured by time-tested encryption also used in Telegram's Secret Chats and Voice Calls. You can find more details on this page.

+
+

Our apps for Android and iOS have reproducible builds, so anyone can verify encryption and confirm that their app uses the exact same open source code that we publish with each update.

+
+

Video calls will receive more features and improvements in future versions, as we work toward launching group video calls in the coming months. But for this midyear milestone, you can now enjoy a little one-on-one time with those closest to you, whether they're in the other room or on another continent.

+

More animated emoji

+

To help you celebrate, we've added another batch of new animated emoji. To get one of these 👇 in a chat, simply send a message with a single emoji.

+
+ +
+ +

Stay tuned for more updates!

+

+ +

August 14, 2020,
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/video-editor-gifs.html b/data/telegram.org/blog/video-editor-gifs.html new file mode 100644 index 0000000000..4b9f3ebdbb --- /dev/null +++ b/data/telegram.org/blog/video-editor-gifs.html @@ -0,0 +1,252 @@ + + + + + Video Editor, Animated Photos, Better GIFs and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Editor, Animated Photos, Better GIFs and More

+ +
+ +
+ +
+ Introducing an New Media Editor, Better GIFs, and More +
+ +

In 2015, Telegram released the most powerful photo editor to be implemented in a messaging app, letting you enhance image quality and add drawings, stickers and text to pictures. Today we're upgrading the media editor with support for animated stickers and editing videos.

+
+ +
+ +

You can now enhance video quality automatically in two taps – or manually tweak a dozen parameters, like brightness or saturation, until your inner Kubrick is satisfied.

+

For perfect paintbrush precision, zoom in on photos or videos when drawing on them to get every line just right. Your made-up makeup – or your classmates' handlebar moustaches – will never look the same.

+

Animated Stickers on Media

+

Most importantly, you can now add animated stickers to any photo or video – just in case you were looking for ways to decorate your dinner table with twerking cherries. Putting an animated sticker on a photo turns it into a GIF:

+
+ +
+ + +

Speaking of GIFs

+

The GIF panel has been upgraded with a new Trending section and emoji-based tabs that cover the most popular emotions. You won't ever need to wrestle with words again when looking for Robert Downey Jr. 🙄

+
+ +
+ +

We've also improved loading times for GIFs in the panel, so you can find that perfect GIF faster. Hold on any GIF you haven't sent before to save it to your Recent tab for later use.

+

Flexible Folders

+

If you have many chats and use folders, hold on any chat in the list to add it to one of your folders. This also works for removing chats from folders. Last call for spring cleaning!

+
+ Chat options menu with 'Add to Folder' highlighted. +
+ +

Android Goodies

+

Android users get a few extra features to make their app slicker. Messages now get sent, edited and deleted with new smooth animations. We've also improved the video player to make sure that controls and long captions get out of your way quickly. Videos shorter than 30 seconds get looped automatically and voice messages play with even more wavy animations.

+
+ +
+ +

Cache management interfaces on Android got a facelift as well. Not only can you keep Telegram's storage footprint on your device incredibly small – you can do it in style. See Settings > Data and Storage > Storage Usage.

+

Last but not least, monkeys. You know that protecting your account with a Two-Step Verification password is a good idea, but we thought we'd sleep easier at night if we knew that a monkey was overseeing the process. No, this is totally not a coded message, go see for yourself.

+

And that's it for today. Enjoy making post-ironic memes with the new tools while we go back to the dungeons and continue working on you-know-what (and not only that).

+

+ +

June 4, 2020
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/video-messages-and-telescope.html b/data/telegram.org/blog/video-messages-and-telescope.html new file mode 100644 index 0000000000..075c2b6960 --- /dev/null +++ b/data/telegram.org/blog/video-messages-and-telescope.html @@ -0,0 +1,247 @@ + + + + + Video Messages and Telescope + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Messages and Telescope

+ +
+ +
+ +
+ +
+ +

We know you love the speed and simplicity of voice messages on Telegram. Starting today, you can also send video messages – just as swiftly:

+
+
+ +
+
+
+ +

To send a video message, go to any chat on Telegram and tap the mic icon to switch to camera mode. Now all you need to do is tap and hold the camera icon and record a video message. When you’re done, just release the recording button to dispatch your message — and it will arrive in the blink of an eye.

+

Video messages are so fast because Telegram compresses them and sends them even as you record them. By the way, if holding the button seems like too much work, you can lock the camera in recording mode by swiping up. This also works with voice messages now (here's one for you, cab drivers).

+

Video messages are automatically downloaded and autoplayed by default (you can change this in Settings if you’re on a data diet though) and generally feel and act like voice messages – on visual steroids.

+
+ +

Picture in Picture

+ +

While watching a video message, you can freely browse your other chats – the video will pop up in a corner and continue playing. You can move it around the screen and pause it from anywhere in Telegram. Cool, eh? Well, there's more:

+

Meet Telescope

+

Lots of popular folks address their fans via public channels on Telegram. Video messages will make their connection to fans more direct and intimate than ever. But we want to kick this up another notch.

+

Today we are launching Telescope, a dedicated video hosting platform for those who use videos to communicate with their audiences (here's one for you, blogger people!)

+

With Telescope, public video messages can go viral beyond the Telegram ecosystem. Telescope hosts autoplayed round videos of up to 1 minute in duration – the same format we use for Telegram video messages. And yes, you heard that right, you don't need a Telegram account to view them.

+

Every public channel on Telegram now has a telesco.pe URL, such as telesco.pe/channel_name, where all of its video messages are available to the world wide web and the wide, wide world.

+
+ +

A Telescope Channel

+ +

Whenever you post a video message to a public channel, it will also be uploaded to Telesco.pe and have a public URL there.

+
+ +

Share Telescope Videos

+ +

With Telescope, even those users who don’t have Telegram installed will be able to enjoy your public video messages and share them on Twitter or Facebook. As a result, this content will generate more views. And who would refuse more views these days, hmm?

+
+

This was just 1/3 of Telegram 4.0. Keep reading to learn more about Payments for Bots and the new Instant View Platform.

+
+

+ +

May 18, 2017,
The Telegram Team

+

+ +

P.S. Our founder has this weird urge to keep launching platforms that start with “Tele-”. Be sure to check out Telegraph, the publishing platform we launched last year.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/video-stickers-better-reactions.html b/data/telegram.org/blog/video-stickers-better-reactions.html new file mode 100644 index 0000000000..fbcafb07e7 --- /dev/null +++ b/data/telegram.org/blog/video-stickers-better-reactions.html @@ -0,0 +1,273 @@ + + + + + Video Stickers, Better Reactions and More + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Video Stickers, Better Reactions and More

+ +
+
+
+ +
+ Video Stickers, Better Reactions and More +
+ +

This update brings easy-to-make video stickers, better reactions with compact animations and extra emoji, a button to review unseen reactions, improved navigation between chats and more.

+

Video Stickers

+

Telegram's animated stickers have unmatched quality and efficiency – needing less than 30 KB of data per sticker. However, creating such stickers requires experience and specialized software such as Adobe Illustrator.

+

Today, we're adding support for stickers converted from regular videos, so that anyone can easily create detailed animated stickers using any video editing program.

+
+ +
+ +

Like always, you can publish your packs with the @Stickers bot – or add some of the new sets made by others. Whatever you do, never stare back at the tomato.

+
+

Check out the Video Sticker Manual for more details.

+

Developers can use the Sticker Import API to build powerful apps for creating and importing stickers to Telegram.

+
+

Better Reactions

+

Reactions now have more compact animations. To send a larger effect, press and hold on a reaction in the menu.

+

Like interactive emoji, reactions are now synchronized, so your recipients will see the animations in real time.

+
+ +
+ +

Reactions are used not only to express emotion, but also to answer questions and show approval – which is why they now have read status. Like for replies or @-mentions, a new ♡ button appears when your messages have unseen reactions.

+

New Reactions and Interactive Emoji

+

This update also adds 5 new reactions 🥰🤯🤔🤬👏 to help you discuss anything from Christopher Nolan's movies to global economic news.

+

These reactions can also be sent as interactive emoji. Send a single 🥰🤯🤔🤬 or 👏 to any private chat, then tap on the animated emoji to unleash a synchronized fullscreen effect.

+
+ +
+ +

Navigating Recent Chats

+

When jumping through unread channels or moving between chats, press and hold the 'Back' button to return to a specific chat. Opening chats from forwarded messages, links, usernames, profiles, etc. adds them to the list.

+
+ +
+ +

Bug Busting and More

+

Our developers spent two weeks in January focusing completely on fixing known issues in Telegram apps. Among other things, they improved call quality, added support for translation to Instant View pages (and bios on iOS), added the option to send silent messages from the sharing menu – and dozens of other improvements.

+

On iOS, you'll also notice new animations when tapping icons in the tab bar.

+
+ +
+ +

And that's it for today. Let's leave some features for February.

+

January 31, 2022
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/voice-2-secret-3.html b/data/telegram.org/blog/voice-2-secret-3.html new file mode 100644 index 0000000000..ae55d6cb2b --- /dev/null +++ b/data/telegram.org/blog/voice-2-secret-3.html @@ -0,0 +1,245 @@ + + + + + Voice Messages 2.0, Secret Chats 3.0 and... + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Messages 2.0, Secret Chats 3.0 and...

+ +
+ +
+ +

Voice messages on Telegram just got a completely new interface with waveform visualizations, a brand new player and raise-to-speak functionality.

+

You can now start listening to a long voice message and switch to other media or chats. The message will continue playing in the background. For who are we to defy the god of multi-tasking?

+
+ +

New looks for voice messages

+
+ +

Recording and listening to voice messages got easier with raise-to-speak and raise-to-listen. When a chat is open, bring your phone to your ear (as if taking a phone call) to listen to new voice messages or record a new one after the signal.

+
+ +

Raise to Speak: Preview before sending

+
+ +

This feature involves plenty of behind-the-scene magic with proximity sensors, gyroscopes and accelerometers. It works well with most modern devices, but is still experimental. Some phones may require arcane intervention from our devs.

+

Secret Chats 3.0

+

With their self-destruct timers and end-to-end encryption, secret chats are a great way to pass sensitive information. Today we’re bringing the best features from cloud chats over to secret chats: detailed link previews, replies, photo and video captions, sticker sharing, inline bots and GIFs. We’ve also improved key visualizations to make secret chats immune to potential alien invasions.

+
+ +

A Secret Chat full of new goodies

+
+ +

…and…

+

Privacy. When overly active friends start adding you to random groups or channels, it gets overwhelming quickly. Now you can decide who may add you to groups and channels with granular precision. E.g. “All my contacts. Except those two.”

+

Supergroups. Supergroup creators also get more control. They can now change who may add new members to their group: all existing members or only selected admins. Supergroups can have up to 1000 members, and finding a balance between order and chaos is important if you want them to grow.

+

Sharing extension. Sharing on iOS devices has become way smoother. You can now share any photo, video, audio, document or location to any Telegram chat or channel straight from default iOS apps like Contacts, Maps, Voice Memos and Photos. It is also possible to share stuff to several chats or channels at once.

+

Attachment Menu. Media files will zoom beautifully when you select them in the attachment menu. Note that we’ve moved ‘Image Search’ to the ’Photo or Video’ section (tap the magnifying glass icon in the top right corner).

+

Hotkeys. iPad users with external keyboards get hotkey support. Now you can navigate chats and send messages without ever touching your iPad’s screen. Saves a lot of time.

+

Photo Editor. In the Android corner, we’re introducing additional photo-editing tools – rotate, fade, tint and curves.

+
+
+ +

Photo editor

+
+
+ +

Curves tool

+
+
+ +

We’re not done with updates this month – more features and good news are coming very soon to a Telegram Messenger near you.

+

+ + +

February 12, 2016
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/blog/voice-chats-on-steroids.html b/data/telegram.org/blog/voice-chats-on-steroids.html new file mode 100644 index 0000000000..d2695f795c --- /dev/null +++ b/data/telegram.org/blog/voice-chats-on-steroids.html @@ -0,0 +1,275 @@ + + + + + Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+ +
+
+
+ +
+ Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools +
+ +

Voice Chats first appeared in December, adding a new dimension of live talk to Telegram groups. Starting today, they become available in channels too – and there are no more limits on the number of participants.

+

This update also brings recordable voice chats, rich lists of participants, raise hand mechanics, invite links for speakers and listeners, voice chat titles, and a way for public figures to join voice chats as their channels.

+

Limitless Voice Chats

+

Admins of channels and public groups can now host voice chats for millions of live listeners. No matter how popular your talk gets, new people will be able to tune in. It's like public radio reinvented for the 21st century.

+
+ +
+ +
+

To start a Voice Chat, open the profile of any group or channel where you're an admin, tap (⋮) or (⋯) and select Start Voice Chat.

+
+

Recorded Chats

+

While some conversations are meant to be temporary, others are worth preserving and passing on. Admins can now record audio from voice chats to save talks and publish them for followers who missed the live event.

+
+ +
+ +

Once you finish recording, the audio file becomes instantly available in your Saved Messages. To avoid surprises, chats that are being recorded are marked with a red light next to their title.

+

Raise Hand

+

In chats where participants are muted, listeners can tap to raise their hand and alert the admins that they want to speak. Just like calling in to a talk show – but with addictive animations.

+
+ +
+ +

Your bio text is now visible in the list of participants, which you can use to detail your expertise, interests, or just a little bit about yourself. This info might help admins find a good slot for your questions or comments.

+

Speaker and Listener Links

+

Admins of public groups and channels can now create invite links that open the voice chat right away. Separate links can be made for speakers and listeners. This way you won't need to unmute important guests when they join – and they can use a different link to promote the upcoming chat to their communities.

+
+ +
+ +

Voice chats also have optional titles which help users see the topic of conversation before they join.

+

Join As…

+

When entering a voice chat in a channel, users have the option to join with their personal account or appear as one of their channels. Celebrities and public figures can use this to avoid drawing too much attention to their personal accounts.

+
+ Joining a voice chat as a channel +
+ + +
+

For example, the Presidents of Brazil and Turkey could meet for a talk in Pavel Durov's Channel and answer questions from users without the risk of having their chat lists flooded with fan mail.

+
+

And More

+

If you choose the wrong chat by mistake when forwarding messages, press the X button before sending them – to either cancel forwarding or choose a different chat.

+
+ Choose a different chat or cancel forwarding +
+ +

You can also resume playback from where you left off when listening to long voice messages. This was previously available for long videos and long audio tracks, and we thought we'd covered everything – but then our grandma signed up.

+

Last but not least, Android users can choose which action is assigned to swiping left in the chat list: archiving chats, pinning, muting, deleting or marking them as read. (On iOS, all these swipe actions are always available, depending on which way you swipe.)

+
+ +
+ +

And that's it for today, stay tuned for the next update!

+

+ +

March 18, 2021
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/voice-chats.html b/data/telegram.org/blog/voice-chats.html new file mode 100644 index 0000000000..a36d1a44d7 --- /dev/null +++ b/data/telegram.org/blog/voice-chats.html @@ -0,0 +1,311 @@ + + + + + Voice Chats Done Right + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Voice Chats Done Right

+ +
+
+
+ +
+ Voice Chats Done Right +
+ +

Since 2013, we've been expanding the definition of Group Chats, adding features like replies, mentions, polls, admin tools, statistics – and allowing hundreds of thousands of members per group. Many of these features were later incorporated into other apps and redefined how people communicate.

+

Today, Telegram groups get an entire new dimension with Voice Chats – persistent conference calls that members can join and leave as they please. Our 12th update in 2020 brings them to you just in time for remote Christmas carols.

+
+

UPD March 2021: Don't miss Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+
+

Voice Chats

+

Any Telegram group can now become a voice chat room that is always on. Voice Chats run in parallel to existing text and media-based communication, adding a live layer of ephemeral talk to the group. They can be used as virtual office spaces for teams or informal lounges for any community.

+

While Voice Chats are not group calls, they can achieve similar goals – at the same time offering flexibility instead of old school scheduling. In larger groups, they also provide serendipitous opportunities for talking to people.

+
+ +
+ +

Groups with active voice chats have a special bar at the top that shows who is talking at the moment (and even how loud they are). This can help you pick the right moment to join – like noticing your friends going over to the cooler.

+
+ +
+ +

After joining a voice chat, you are free to move around the app, browse conversations and send messages. You stay connected to the chat and the microphone controls remain on screen so that you can quickly mute and unmute yourself at any time.

+

If you're on Android, you can enjoy the full Voice Chat experience with a system-wide floating widget that shows your mic controls and who is currently talking, even when Telegram is in the background. Santa is on Android too – and he needs his sleigh navigator open at all times.

+
+ +
+ +

You can chat with whomever is online or invite more people via the handy menu. Voice Chats can accommodate a few thousand participants, which means they'll work for everything from consulting family members while out shopping to a massive live event.

+

Last but not least, Voice Chats show spectacular animations. To get these right, our designer had to sell his soul to the devil – and we think it was totally worth it.

+
+

To create a Voice Chat and find your own unique way of using them, open the profile of any group where you're an admin, tap (⋯) or (⋮) and select Start Voice Chat.

+
+

Like Telegram groups before them, we hope that Voice Chats will change the way people collaborate and keep in touch. In the coming weeks, we'll be refining them further, listening to your feedback, improving noise suppression, and adding more features like video and screen sharing.

+

Push-to-Talk Shortcuts

+

On Telegram Desktop and in the native macOS app, you can choose a push-to-talk key for Voice Chats, to control your mic even when Telegram is not focused. At long last, we've found a use for your Caps Lock key.

+
+ +
+ +

Sticker Outlines

+

Animated stickers on Telegram are optimized for efficiency and deliver smooth 180 frame animations with infinite resolution in less than 50 KB.

+

With today's update, stickers will load even faster than before – and show a shimmering outline of what you're about to see. Be careful not to blink though, or you'll miss it.

+
+ +
+ +

SD Card Storage on Android

+

Users on Android devices can now move their Telegram app data from internal storage to their SD card, allowing those with minimal storage to save more media and files and maximize their Telegram experience.

+
+ Storage Usage settings +
+ +
+

Remember that you can always keep Telegram's storage footprint on your device incredibly small. See Settings > Data and Storage > Storage Usage.

+
+

New Animations on Android

+

We've added slick new animations throughout the Android app – when tapping the New Message button, opening profiles, managing chat folders and anywhere you see message counters.

+
+ +
+ +

Announce Messages on iOS

+

If you're still on iOS, you can have Siri read incoming messages aloud in your headphones. Open iOS Settings > Notifications > Announce Messages and set Telegram to ON to stay up to date on your chats even while washing the dishes.

+

Editing Improvements

+

Android users can now quickly edit a photo which they've already sent to add effects, drawings or stickers with our powerful media editor. iOS users can tap the pen button to quickly edit and send back a photo they have received.

+

Each of these features was previously available only on one of the platforms, but now both iOS and Android offer equal opportunities for drawing moustaches on selfies.

+
+ Editing Improvements on iOS and Android +
+ +

When editing a message or caption, as you approach the maximum message length, a counter will appear showing how many remaining characters you have lef

+

More Animated Emoji

+

No update is complete without even more animated emoji. As usual, simply send a message with a single emoji to get one of these 👇 in a chat.

+
+ +
+ +

There's a story in there somewhere about a cyber cowboy solving a murder mystery.

+

Feature Suggestion Platform

+

Many Telegram features started out as user suggestions. To help identify potential new features and locate bugs within the app, we're launching a public Bug and Suggestion Platform.

+ + +

We'll be rolling out the ability to suggest new features and report bugs gradually to make sure each submission gets the attention it deserves. All Telegram users are already welcome to view existing entries and vote on them.

+

And that's all for today, we'll see you in 2021 or once we're done building the next big thing – whichever comes first.

+

+ +

December 23, 2020
The Telegram Team

+

+ +
+

P.S. The end of the year is normally a time to look back at the past 12 months. Instead, our founder Pavel Durov has just announced his strategy for making Telegram sustainable, to continue providing you with great features for decades to come.

+
+
+ +
+ + +
+ + +
+
+
+ + + + + + + + diff --git a/data/telegram.org/blog/winter-contest-ends.html b/data/telegram.org/blog/winter-contest-ends.html new file mode 100644 index 0000000000..1b651c3bac --- /dev/null +++ b/data/telegram.org/blog/winter-contest-ends.html @@ -0,0 +1,224 @@ + + + + + Winter Contest Ends + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Winter Contest Ends

+ +
+ +
+ +

The contest to decrypt intercepted traffic of Telegram produced no winners as of March, 1. As promised, today we are publishing the encryption keys necessary to decrypt the traffic.

+
SECRET CHAT:
+2e 20 9f 9d 99 c9 fc 8a 3d dc d5 6d 21 26 46 c9 d8 1a 26 f8 ec f7 f2 7e c9 28 65 95 52 dc 1c 21 bb 95 60 b1 d8 5f 94 5f 43 8d 7e 8e 96 fa e6 89 91 a9 90 39 8b df ef 50 22 06 f8 52 80 e6 50 20 62 71 c4 b2 f5 f8 88 4d 83 ae 66 ec fe cd ec 92 26 69 72 5e 85 f9 ea 58 b0 d6 9f 5b 1e b7 68 15 76 5b 12 88 3d 17 f6 62 49 8b 1f 9d 7a 11 94 67 8d d1 ee d6 55 50 d4 51 c0 5e a5 9a 1a eb 8a 8c 7c 44 1b db 96 5a fd cd 85 47 5b f0 8a 1e b8 d6 74 a4 c7 e7 af 19 3f a6 0a ff e5 3b 9f c4 fc ea 59 af f6 72 60 16 6f 40 af 58 95 98 06 0c 22 00 d7 3d be 96 19 56 54 06 74 d2 6b 38 8d c2 a0 97 62 6d e4 10 99 b9 cf d5 0f 56 9d d3 bb 49 86 d5 15 23 86 03 c3 52 67 82 77 5e 53 e9 ba e8 63 58 ed 55 b0 ef ec 69 65 a0 e5 1d e4 b6 6e 5a 3d 5f 9b 9a 20 67 f5 d5 c4 d7 60 14 c6 56 2d 12 1b 0a
+
+DC 1:
+5e a6 0d a2 9c 90 8e f4 36 d5 48 fe 76 a3 11 f6 66 13 4e 94 bb 11 32 d6 cf fd b0 2f 7b 77 bb 01 d7 42 a4 22 d3 04 e7 d2 fc 5b 32 48 d6 71 eb 18 51 19 99 76 49 46 1a 43 d8 cf cd 8a e2 fe 42 2c 36 d7 05 8b 0c 5e 00 8a 5a bc 35 4f ec 75 b4 10 e1 84 bb cb af ec e3 d6 fd 59 fd 01 83 ef 8b dd 13 50 24 5b 80 09 75 7e c3 c3 08 ba 59 f4 ec c0 87 71 ba 9f 45 8c 15 df 2a cd a5 bc 81 a9 20 fe 42 e2 65 78 02 77 80 11 0e e4 67 f3 40 cf 72 be fc c2 8d 0b ad d9 9e 6e 1a c3 03 71 39 be b9 dd df 7c 63 a6 27 45 ee 8e 00 5e 12 51 51 6c 6a 10 a6 73 3a 10 5d d8 f3 b6 c5 70 fe 91 c2 64 4b d0 74 2d 47 e7 4e 00 cf d5 d3 65 15 2b 48 9c 75 eb a8 96 aa ce 09 49 9b 5e ea 76 06 19 f3 b3 e7 7b af df 5d 68 5e 80 10 48 ec 00 35 90 d3 e5 96 c6 59 a7 44 d8 20 a8 a2 b6 93 64 4f 98 44 23 8e fd
+
+DC 2:
+63 ab 0d b7 98 e1 78 ef 5f 05 9c e4 84 3b 53 b3 4f 6e d1 d3 8a 6d 59 19 32 26 73 60 c2 e2 fe ee d3 2d 74 35 18 08 ba 04 87 cf 7f d9 87 4b 64 d5 80 06 05 f5 01 56 6d c2 66 7e 2d ef f6 a3 82 3d 31 0e ed 6b 46 4c 11 d5 ec 0f 7b be 64 79 26 87 a9 d3 34 27 d8 8b aa b5 36 8b 95 2f a7 c7 2a a6 bf a9 44 51 c5 c8 06 04 78 d2 64 87 e8 13 f3 f0 9b c9 8c bc 29 01 55 a2 80 e1 e8 4e 74 53 7e 05 22 1b 51 3d 1a c5 61 b3 04 98 c2 2f 71 e3 76 2e 31 bd d8 55 15 4b 3e 34 ed 84 b2 56 d0 bd c6 9a 1a 2a 4b 2f fc 68 8e c4 e3 81 23 6f 07 3f 3a 6b 56 f6 ee 31 e6 aa 0d 49 36 6a 51 79 25 bf b6 40 64 8c e2 14 c8 70 37 cb 70 ad a1 83 ed 1f b9 78 b9 93 0c 7c 0c ed 6d c6 aa c2 d0 da 51 ce ae cf 99 8f 65 eb 5a 42 e6 ff 4a 51 a9 97 da 6e ac e5 63 c1 05 a9 fe d0 da da 43 e3 50 14 fc b1 46 ea
+
+DC 3:
+16 0c be 58 e1 74 74 f5 f9 8f f8 82 71 ed 57 84 20 49 bd da 17 0e 00 a8 a4 24 71 79 86 1f ef 3e 41 70 31 de c9 c2 19 23 37 fd ec 2f fa 9e 89 29 4f a2 af 69 cf 24 3a 6e 44 5d 89 d2 8b 50 45 26 3c ff e3 d4 4d 7d b4 88 54 8c 87 09 c5 ac 09 5c e6 62 43 73 b5 3e 96 ea f3 62 76 58 1b fd 8a 36 45 65 4a fc 7b ee 7b 13 06 e5 2f 9d 8f cb b9 a7 6f 76 00 f4 9a ab 50 fb 91 e0 2b ce 28 db 95 02 a0 62 33 bb e7 41 13 7b 2c 7e ba 7c d5 87 12 33 de 44 8d 4b 76 af 59 cc 80 42 02 69 56 90 8a 5d 95 0b 3e 8b ef 65 17 fc 79 62 b4 69 1b 21 aa 89 5b 22 f6 33 67 80 d0 22 f7 76 f2 6c 4b af 69 07 0f 2c 3a af 67 6b 74 c0 7f 8c 83 85 85 8e 47 b7 55 42 c1 3d 70 33 9d 87 60 7c f6 8b 99 96 1d af 82 b8 d2 37 c7 a3 fc ac 25 fe 77 f0 29 4d 82 a4 15 89 cb c2 27 ae 4f 16 d6 b8 4c cb de 2a 59 d7
+
+DC 4:
+b4 aa dc bc 8e e5 6a f4 9f 7b 65 de cd 1c 28 3d f1 58 f6 03 e1 34 9d 63 54 b0 15 a7 b8 a6 45 4e de dd cd e4 1a 54 d7 9b fe 46 05 c7 62 19 d9 7a c0 00 6b e6 72 83 3d 15 00 99 d9 9b 97 c0 4a a8 85 e7 85 3c 3f a4 2f 6a 57 0b 3c b0 2a 97 65 6f bf 4e 0d 93 f7 55 3b 3a 39 a1 1a 0f db 9d 7a df 5b c6 9b 45 9a ea e4 27 92 8c c3 d2 75 53 66 e4 1c 29 f1 14 fc fd e8 c0 c8 12 47 ee 5a 92 f1 bf 1f 6f 8e 95 a5 90 81 37 d6 5d bd 5c 4c 41 61 29 6e 4f 7e 83 e1 b9 ef 00 00 de 25 33 f4 df 1a 94 f0 e7 1c fd 35 c0 75 65 88 ef c5 aa b5 c9 7d 0e e4 6d b7 9f 10 ca 4b f0 c9 c7 2d 30 20 e9 e1 b8 03 de a2 60 4e 3f 59 dc 36 a2 50 f8 52 5e 32 c8 c1 84 87 84 d6 54 42 dd ab b4 1b d6 fe e4 29 d3 70 4e 3e 48 ba 86 80 39 b7 94 3c 31 18 f8 bd 7b d8 89 6b 32 77 5c 89 4a a1 ca 18 ba 1e 6a 87 6a
+
+DC 5:
+4c 76 1f 87 08 53 54 cb 12 fd 01 bd bd e6 42 d2 6b 47 4b d8 0b 6a eb 9f 24 8b ee 77 1f 8b a5 3f f5 f1 c7 80 05 80 2c 20 29 7c 3c 14 59 2b 5e 7f 69 58 3b 7e 07 37 25 67 3d 18 ac f2 28 43 63 8f a5 41 c1 ba 53 dd eb 3d 36 0d 7b d3 14 f7 f9 83 aa 0c 81 20 89 e0 c7 d7 e9 ef 11 aa 43 ca 54 2a 9f 69 0f 1d 99 ef f6 55 14 71 6d a3 1e c2 75 fb 1c 88 f7 c0 21 64 5d 34 db 3f a4 e7 a9 f0 af 9f 9d 14 a4 3a 49 7c 50 e6 45 24 3a cb a4 a6 2a 35 dd 6c 9c ce 87 24 d1 ff 13 19 15 43 89 a4 8c 39 66 a2 22 df 4e 94 76 e1 89 b5 03 7a 2b 34 e7 39 09 f9 22 5d cb 36 4e ce 37 e7 cf 7d ab b5 8b db 81 c6 c8 f4 c7 7c 3a 22 59 fc e6 32 19 aa 46 d2 95 96 61 61 e6 cc 57 f0 0e 87 5c 7d 5b 87 e7 64 28 c6 03 38 3c 0b a6 5e 4a 21 a3 67 af e5 b3 88 cc 9d 03 98 33 ac c6 87 b4 b6 82 42 c4 41 33 39
+


+ +

We would like to use this opportunity to thank the users ABC, @DefuseSec, @hackappcom, @Morj and x7mz who helped us further improve security of the client apps and expand guidelines for third-party developers.

+

Since we have no winner in the current challenge, we are going to launch a new competition, with an easier task, but a larger prize. The new competition will allow participants not only to intercept traffic, but to manipulate it as well. We are now building the tools that will enable the contestants to perform all kinds of active attacks. Once the platform is ready later this month, we will announce the new contest on Twitter. Please follow us at @telegram!

+

March 2, 2014
The Telegram Team

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/evolution.html b/data/telegram.org/evolution.html new file mode 100644 index 0000000000..d79af7b532 --- /dev/null +++ b/data/telegram.org/evolution.html @@ -0,0 +1,1801 @@ + + + + + The Evolution of Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+
+

The Evolution of Telegram

+ +
+ +
+ +
+ +
+
+ Evolution of Messaging +
+ +

On this page, we've compiled a Brief History of Telegram. It ended up rather on the 'humongous' side of 'brief' – but that's what you get for never, ever, ever updating the app with a description like 'contains bug fixes and minor improvements'.

+

A (Not So) Brief History of Telegram

+

For some reason, we started writing this backwards – from the latest update to the primordial summer of 2013. And then it was too late to change the order because the guy who compiled the post said he would go on a hunger strike if we tried.

+

So if you're a fan of chronology, please jump to the end and scroll up from there. This page gets updated each time a new post hits the Telegram blog.

+ + + + +

2021

+
+

December 2021, Second Update

+

Reactions, Spoilers, Translation and QR Codes

+

Telegram’s unique interactive emoji became available as reactions – giving users the ability to directly share their feelings on messages.

+

Spoiler formatting was introduced, allowing anyone to hide parts of a message under a special animation.

+

Message translation was brought to Settings > Language, adding a dedicated button to translate any message directly in the app.

+

Customizable QR codes were included for all public usernames – including users, groups, channels and bots – to quickly share a chat in any app.

+
+ Reactions, Spoilers, Translation and QR Codes +
+ +

On Telegram since December 30, 2021:

+ +
+

December 2021, First Update

+

Protected Content, Delete by Date, Device Management and More

+

A new setting was added to Groups and Channels that allows creators to keep their content exclusive by restricting message forwarding – while also preventing screenshots and limiting the ability to save media.

+

The option to delete all messages from a day or range of dates was added to 1-on-1 chats, giving users a way to clear specific sections of chat history.

+

The Devices menu in Settings was fully redesigned, including a new auto-logout timer for inactive sessions and the ability to toggle whether a specific device can accept incoming calls or Secret Chats.

+

In Public Groups and Channel Comments, users were given the choice to send messages anonymously – appearing as one of their public channels instead of their personal account.

+
+ Protected Content, Delete by Date, Device Management and More +
+ +

On Telegram since December 7, 2021:

+ +

Android-Specific:
- Global Chat Themes (on iOS since November, 2021)

+

iOS-Specific:
- Text Recognition for iOS 13+
- Format Text in Media Captions (already on Android)

+
+

November 2021

+

Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

+

Accelerated scrolling and pinch to zoom for media thumbnails were added to Shared Media to find past photos, videos, files (and more) even faster. Tapping the date bar opens a calendar view, with media previews for each date.

+

Join requests let group and channel admins confirm new members before they are allowed join. This creates new options for communities – like a special superfans chat or super-secret channel.

+
+ Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More +
+ +

On Telegram since November 3, 2021:

+ +

iOS-Specific:
- Global Chat Themes
(added to Android in December 2021)
- Transit Times for Shared Locations
- Instant Media Captions (added to Android in December 2021)

+
+

September 2021

+

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

+

It became possible to set different themes for individual private chats – for both participants. The release included 8 new themes, each with their own day and night versions, gradient message bubbles, animated backgrounds, and unique patterns.

+

Nonverbal communication got a boost with interactive emoji: tapping on animated versions of 🎆 🎉 🎈 👍 💩 or ❤️ launches fullscreen effects that appear simultaneously for both chat partners. Vibrations are also synched, so you can almost touch someone's hand – even if you're far apart.

+

A new Seen By field was added to outgoing messages in smaller Group Chats, allowing you to see which members have read it. To protect privacy, these read receipts are stored only for 7 days.

+

The ability to record video came to Live Streams and Video Chats, so communities can save and share anything from online lectures to rock concerts. You can choose to record the video file in portrait or landscape orientation, and the file is instantly uploaded to your Saved Messages once you stop recording.

+
+ Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More +
+ +

On Telegram since September 19, 2021:

+ +
+

August 2021

+

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

+

Live video with unlimited viewers became available for both groups and channels. Voice chats were, consequently, renamed to Video Chats (in groups) and Live Streams (in channels).

+

Forwarding became even more flexible with new options: a preview window that shows how messages will appear after they are forwarded and lets you hide sender names from messages or remove captions from media.

+

Channels became easier to navigate. Swiping up at the bottom of the channel brings you to the next unread channel. Catching up with the news is now possible without going back to the chat list.

+
+ Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More +
+ +

On Telegram since August 31, 2021:

+ +
+

July 2021

+

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

+

Group Video Calls could now have up to 1000 viewers (previously 30), in addition to unlimited audio-only listeners.

+

Video Messages got a brand new look – recording in higher resolution with options to expand the message and fast-**forward** or rewind while watching. Additionally, audio from your device would continue playing while you recorded, and you could zoom in when recording with the rear camera.

+

Screen Sharing was added to 1-on-1 video calls (previously existed in groups), and included sound from the users device when broadcasting in both individual and group video calls.

+
+ Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More +
+ +

On Telegram since July 30, 2021:

+ +

Desktop-specific:

+ +

iOS-specific:

+ +
+

June 2021, Second update

+

Animated Backgrounds

+

Animated Chat Backgrounds were added to all default themes – moving beautifully with each message. Users could pick from dozens of presets or create their own custom backgrounds with 3 or 4 colors in the theme editor.

+

New sending animations were given to stickers and emoji, making them jump from the keyboard to the chat.

+

A menu button was created for chats with bots, displaying all its commands as well as placeholders to give users an example of what to send. Bot developers also got the ability to display flexible lists of commands that change based on a user’s language, chat type, admin status and more.

+

We released an API to help developers build tools that let users import stickers from other apps, or easily make stickers from their own content.

+
+ Animated Backgrounds +
+ +

On Telegram since June 25, 2021:

+ +

iOS-specific:

+ +
+

June 2021, First update

+

Group Video Calls

+

Group Video Calls came to Telegram, adding video to (now awkwardly named) voice chats in groups. Users could turn on their camera or share their screen from any device – including tablets and desktop.

+

Tablets and Desktops got custom display options – including an expanding side panel for split-screen mode. Desktop also offered selective screensharing, letting users choose a specific program to broadcast.

+

Noise supression was implemented in voice chats, eliminating background noise and boosting audio quality on all devices.

+
+ Group Video Calls +
+ +

On Telegram since June 25, 2021

+ +

Desktop-specific:

+ +
+

April 2021

+

Payments 2.0, Scheduled Voice Chats, New Web Versions

+

Payments were first supported in chats with Telegram bots in 2017. This time, merchants received the ability to accept credit cards in any Telegram chat using one of 8 integrated payment providers. Telegram doesn't store credit card info and charges no commission.

+

Voice Chats were further improved with scheduling, showing a countdown timer and allowing users to get a notification when the chat starts.

+

Two new web versions were launched, adding full support for features like animated stickers, chat folders and dark mode. Both work well in desktop and mobile browsers.

+
+ Payments 2.0, Scheduled Voice Chats, New Web Versions +
+ +

On Telegram since April 26, 2021:

+ +
+

March 2021

+

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

+

Voice Chats first appeared in Telegram groups in December 2020. Three months later they became available in channels, with support for millions of live listeners.

+

Admins got the option to record voice chats and create instant podcasts, as well as choose titles for their voice chats and add users via specific Speaker and Listener links. Muted listeners could raise their hand to let admins know they wanted a turn to speak.

+

Public figures, celebrities and other users who prefer to keep their personal accounts hidden got the ability to join voice chats as one of their channels.

+
+ Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools +
+ +

On Telegram since March 19, 2021:

+ +
+

February 2021

+

Auto-Delete, Widgets and Expiring Invite Links

+

Telegram has had self-destructing messages since 2013 in Secret Chats, but this update added an auto-delete timer for any chat to erase messages either 24 hours or 7 days after sending.

+

Two customizable home screen widget styles became available for both Android and iOS, giving users the option to show previews of recent messages on their home screen, or shortcuts to chats.

+

Invite links for groups and channels were upgraded, allowing for additional links with a limited duration or number of uses that can also be converted into QR codes.

+

Broadcast Groups were introduced, allowing large communities to have unlimited members. Only admins can send messages in Broadcast Groups, but everyone can still read along and join voice chats.

+
+ Auto-Delete, Widgets and Expiring Invite Links +
+ +

On Telegram since February 23, 2021

+ +
+

January 2021

+

Moving Chat History from Other Apps

+

Over 100 million new users joined Telegram within one month, bringing their friends and families with them. After January's update, they could also bring their old message histories from other apps. Users can now import messages and media from apps like WhatsApp, Line and KakaoTalk.

+

In addition to deleting messages for both sides without a trace (2019), call history, and groups users created could also be deleted for all participants at any time. While secret chat messages disappeared for both sides since 2013, this update made it possible to remove entire Secret Chats from the chat lists of both participants.

+

Voice Chats got two improvements: users could see active voice chats from their groups at the top of the Call History page, and got the ability to adjust the volume of individual participants inside the chat.

+

This update also improved the audio player, accessibility, and added the ability to report fake groups and channels impersonating famous people or organizations.

+
+ Moving Chat History from Other Apps +
+ +

On Telegram since January 28, 2021

+ +
+

2020

+
+

December 2020

+

Voice Chats Done Right

+

We closed the year by adding a new dimension to groups with Voice Chats – persistent conference calls that run in parallel to existing text and media-based communication in the group. Voice Chats add a live layer of ephemeral talk to the group and can be used as virtual office spaces or informal lounges for any community.

+

Android users got an option to use their SD Card for storing Telegram data. iOS users received support for Siri's Announce Messages feature. iOS and Android caught up with each other to offer equal opportunities for drawing moustaches on selfies editing photos and other media.

+

We've unveiled a public platform for suggesting features and reporting issues at bugs.telegram.org.

+

Pavel Durov also presented a strategy for making Telegram sustainable for decades to come.

+
+ Voice Chats Done Right +
+ +

On Telegram since December 23, 2020

+ +

iOS-specific:

+ +
+

October 2020

+

Pinned Messages 2.0, Improved Live Locations, Playlists and More

+

Pinned Messages were upgraded, allowing for multiple pinned messages in all chats, including one-on-one chats.

+

Distance Alerts were added to live locations, giving users the option to receive a notification when another location-sharing user gets close. The map icons were updated as well, to show which way a user is facing.

+

Playlist and album support was added for files – sending multiple audio tracks will create a playlist, while sending multiple files creates an album.

+

Channel Statistics were expanded to include detailed metrics about reach and engagement for individual posts in a channel.

+
+ Pinned Messages 2.0, Improved Live Locations, Playlists and More +
+ +

On Telegram since October 30, 2020

+ +

Android-specific:

+ +
+

September 2020

+

Search Filters, Anonymous Admins, Channel Comments and More

+

Global Search received new filters: typing a chat name or time period adds filters by date and source, and media tabs at the top of the screen sort results by type, like Files or Links.

+

Support for Anonymous Admins was added to groups. When enabled, the admin’s name is hidden in the list of group members and their messages are signed with the group name instead, similar to channel posts.

+

Comments were added to Channels with a linked discussion group. Subscribers will see a comment button under each post, where they can share their thoughts on the latest updates. To try channel comments, head over to @durov.

+
+ Search Filters, Anonymous Admins, Channel Comments and More +
+ +

On Telegram since September 30, 2020:

+ +

Android-specific:

+ +
+

August 2020

+

Video Calls and Seven Years of Telegram

+

In celebration of Telegram’s 7th Anniversary and its status as one of the world's top 10 apps, the first version of Video Calls was launched for Telegram’s mobile and desktop platforms.

+

All video calls are secured with end-to-end encryption and support picture-in-picture mode, so users can search and send messages without closing the call.

+
+ Video Calls and Seven Years of Telegram +
+ +

On Telegram since August 14, 2020:

+ +
+

July 2020

+

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

+

Users got the option to add motion pictures to their profile page with Profile Videos. People Nearby was improved to make finding friends in your local community even easier.

+

For users who receive a notable number of messages from non-contacts, a switch was added to automatically archive and mute new chats from people not in their contacts.

+

The update also included a series of expanded features: the upload size for media and files was increased to 2 GB (previously 1.5 GB), detailed statistics became available for large groups, and the default icons used in the chat list for photos, videos and links were replaced with mini-thumbnails of the sent media.

+
+ Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More +
+ +

On Telegram since July 26, 2020:

+ +

Android-specific:

+
    +
  • Crop and Rotate videos (on iOS since time immemorial)
  • +
+

Telegram Desktop:

+ +
+

June 2020

+

Video Editor, Animated Photos, Better GIFs and More

+

The photo editor was tranformed into a universal media editor – adding the ability to edit and enhance visuals for video, put animated stickers on any media, and zoom in when drawing or decorating (just to name a few).

+

The GIF panel got upgraded, adding emoji-based sections and a Trending tab for the most relevant and popular expressions. To make them even easier to search and scroll through, loading times were greatly improved.

+
+ Video Editor, Animated Photos, Better GIFs and More +
+ +

On Telegram since June 4, 2020:

+ +

Android-Specific:

+ +
+

April 2020, Second Update

+

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

+

To celebrate 400 million active users, the sticker panel was revamped, allowing users to scroll and search through thousands of popular stickers from professional artists.

+

The Quiz Polls introduced in January 2020 received new tools geared toward educational tests, including explanations and a timer animation. With the need for online learning tools at a new high, a €400K contest was announced to help build a platform for educational tests on Telegram.

+
+ 400 Million Active Users +
+ +

On Telegram since April 24, 2020:

+ +

Android-specific:

+ +

MacOS-specific:

+ +
+

April 2020, First Update

+

Coronavirus News and Verified Channels

+

While the world locked down during the COVID-19 pandemic, Health Ministries began creating Telegram channels to keep their citizens informed of the latest updates. To help facilitate the spread of accurate information, the channel verification process was streamlined with a new @VerifyBot and a directory was created to help users find official coronavirus news sources for their country.

+
+ Coronavirus News and Verified Channels +
+ +

On Telegram since April 3, 2020:

+ +
+

March 2020

+

Chat Folders, Channel Stats and More

+

Expanding on Archived Chats from 2019, Chat Folders were added that let users filter their chat list into custom categories. Folders support unlimited pins, and sync across all devices on the account to keep everything organized.

+

Channel Stats were also introduced, giving channels with more than 1000 subscribers analytics and graphs to track post performance and overall growth.

+
+ Chat Folders, Channel Stats and More +
+ +

On Telegram since March 2020:

+ +
+

February 2020

+

New Profiles, Fast Media Viewer and People Nearby 2.0

+

This Valentine-themed update made it easier to make friends and view media. Profile pages were redesigned with instant access to Shared Media and users got the option to flip through photos and videos simply by tapping on them.
People Nearby was updated so users could make themselves visible to others in their area, displaying their profile even if they closed the app (until they selected ‘Stop Showing Me’).

+
+ New Profiles, Fast Media Viewer and People Nearby 2.0 +
+ +

On Telegram since February 2020:

+ +
+

January 2020

+

Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode

+

Focused on polls, the first update of 2020 added plenty of ways to get competitive – or organized - in groups and channels. Polls 2.0 introduced options to show users’ votes and the ability to select more than one answer, as well as quiz-style polls, complete with a platform for making quizzes.

+

A new slider was added to adjust how round or square chat bubbles appear, and Android users received numerical progress counters to track uploads and downloads (previously iOS-only).

+
+ TITLE +
+ +

On Telegram since January 2020:

+ +
+

2019

+
+

December 2019

+

Verifiable Builds, New Theme Editor, Send When Online and So Much More

+

On the final day of 2019, security researchers got the tools needed to confirm that the open source code we post on GitHub is the same that can be downloaded from App Store and Google Play.

+

The Theme Editor leveled up to 2.0, adding gradient colors, new background patterns and more default color schemes. Scheduled Messages were expanded with a setting to send when your recipient comes online. Android and iOS both got a slew of other usability and design upgrades.

+
+ Verifiable Builds, New Theme Editor, Send When Online and So Much More +
+ +

On Telegram since December 2019:

+ +

Android-specific:

+ +

iOS-specific:

+ +
+

September 2019

+

Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy

+

The end of summer brought scheduled messages and reminders to better keep track of important tasks and appointments. On the visual side, shareable Custom Cloud Themes came to all platforms, along with more animated emoji.

+

An important privacy option was added for those who need it most – Who Can Find Me By My Phone Number. This new setting can prevent random users (or government organizations) from being able to match a number from their device's contacts to your Telegram account.

+
+ Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy +
+ +

On Telegram since September 2019:

+ +
+

August 2019

+

Silent Messages, Slow Mode, Admin Titles and More

+

The August update brought a way to send silent messages – which result in a notification without sound. We also added custom titles and a slow mode for group admins.

+

Following the success of animated stickers, this update also introduced animated emoji for ❤️, 👍, 😒, 😳 and 🥳. More followed.

+
+ Silent Messages, Slow Mode, Admin Titles and More +
+ +

On Telegram since August 2019:

+ +

July 2019

+

Animated Stickers Done Right

+

The July update introduced animated stickers. We managed to achieve a smooth 60 FPS at just 20-30 KB per sticker. Animated stickers consume less bandwith than static ones and less battery than GIFs, while commanding more attention than the two combined.

+

Here are some sample animated sets in case you missed them: Hot Cherry, Tidy Tie Tom, Resistance Dog, Fred the Pug, Melie the Cavy, Earl the Wolf, Egg Yolk

+

These stickers are powered with uranium and dreams and are guaranteed to keep going forever.

+
+ Animated Stickers Done Right +
+ +

On Telegram since July 2019:

+ +
+

June 2019

+

Location-Based Chats, Adding Contacts Without Phone Numbers and More

+

The June update focused on making it easier to add people to contacts. A universal Add button was introduced to all new chats, making it possible to add users to contacts even if you don't know their number yet.

+

A new Add People Nearby section was created to quickly exchange numbers with people close to you. The new section also allows creating location-based public chats.

+
+ Location-Based Chats, Adding Contacts Without Phone Numbers and More +
+ +

On Telegram since June 2019:

+ +
+

May 2019, Second Update

+

Focused Privacy, Discussion Groups, Seamless Web Bots and More

+

The second May update made Telegram Privacy Settings even more flexible. You can add whole groups to 'Never Share' or 'Always Share' exceptions. Settings will adjust automatically as people join and leave the groups.

+

On Telegram, your phone number was never visible to random people in groups, the default being 'My Contacts'. This update offered even more control via Settings > Privacy & Security > Phone Number.

+

The update also introduced an easier way to integrate web services with Telegram, adding one-tap authorization via bots. Last but not least, it offered two new ways of adding comments to channels – via Comments.app and connected discussion groups. (We didn't start the flame war.)

+
+ Focused Privacy, Discussion Groups, Seamless Web Bots and More +
+ +

On Telegram since May 31, 2019:

+ +
+

May 2019, First Update

+

Archived Chats, a New Design on Android and More

+

The first May update introduced Archived Chats. Unmuted chats pop out of the archive with the next incoming message – but muted chats stay archived forever (or until they generate a notification via a mention or reply). An unlimited number of chats can be pinned in the archive.

+

Android design got a major overhaul. Aside from the visual improvements, this update added a three-lines-per-chat view option for the Android chat list (similar to the iOS default), as well as bulk actions in the chats list to easily delete, archive or mute multiple chats at once.

+
+ TITLE +
+ +

On Telegram since May 9, 2019:

+ +

March 2019

+

Taking Back Our Right to Privacy

+

Before the March update, you could delete your messages within 48 hours of sending them. As of this update, you can delete any message you've ever sent or received in any private chat, there's no time limit. This also applies to clearing entire chats. The deleted messages don't leave a mark in the chat.

+

This update also introduced a setting for Anonymous Forwards, allowing you to control when messages forwarded from your account link back to it. This way people you chat with have no verifiable proof you ever sent them anything.

+
+ Taking Back Our Right to Privacy +
+ +

On Telegram since March 2019:

+ +

February 2019

+

Autoplaying Videos, Automatic Downloads and Multiple Accounts

+

Following the February update, smaller videos start playing without sound when they reach your screen. Pressing the volume buttons on your device unmutes them.

+

This update also introduced presets for autodownload settings to switch between Low, Medium, High and Custom data consumption in a few taps. Default settings for data usage have become more generous but depend on the affordability of mobile data in each particular country.

+

As of this update, iOS users can also log in to Telegram with multiple accounts from one app, easily switch between them and get notifications. Support for multiple accounts was added to Android in December 2017.

+
+ Autoplaying Videos, Automatic Downloads and Multiple Accounts +
+ +

On Telegram since February 2019

+ +

January 2019, Second Update

+

Chat Backgrounds 2.0: Make Your Own

+

The second update in January brought chat wallpapers to version 2.0, adding support for motion and blur effects, plain color backgrounds and patterns, as well as an option to share backgrounds via links and find new ones in search.

+

For those who appreciate art history, the classical Telegram backgrounds which were used at launch can be found here.

+
+ Chat Backgrounds 2.0: Make Your Own +
+ +

On Telegram since January 31, 2019

+ +

January 2019, First Update

+

Group Permissions, Undo Delete and More

+

The first January update brought group permissions, allowing admins to restrict all members from posting specific kinds of content or even from messaging altogether. The maximum size for groups was doubled to 200,000 members.

+

The update also added an 'Undo' option after deleting chats or clearing history. It's like a time machine, but with fewer paradoxes.

+
+ Group Permissions, Undo Delete and More +
+ +

On Telegram since January 21, 2019

+ +
+

2018

+
+

December 2018, Second Update

+

Polls: Bringing Choice to Communities

+

As of the second update from December '18, Telegram users can create polls in groups and channels, letting group members vote anonymously.

+

Poll bots have been available since the dawn of the Bot Platform.

+
+ Polls: Bringing Choice to Communities +
+ +

On Telegram since December 22, 2018

+ +

December 2018, First Update

+

Custom Languages, Instant View 2.0 and More

+

This first December update in 2018 revolutionized app interfaces, adding custom languages – whether that's Māori, Scottish Gaelic or Transliterated Klingon. Qapla'. Users can share translated language packs with dedicated sharing links.

+

Everyday be talk like a pirate day if ye've downloaded the pirate speak chest. Babel fish now optional.

+
+ Custom Languages, Instant View 2.0 and More +
+ +

On Telegram since December 10, 2018

+ +

October 2018

+

Introducing Telegram 5.0 for iOS

+

Telegram for iOS was rebuilt from scratch for this update – using the Swift programming language. The new client is slicker, faster and more battery-friendly. If the old Telegram was a race car, this one is a race car with jet engines and a well-caffeinated driver.

+

New badge counter settings were added on iOS, allowing users to exclude messages from muted chats or count unread chats instead of messages.

+

The native macOS client added swipe gestures to navigate interfaces. MacBook Pro owners got touch bar support.

+
+ Telegram 5.0 for iOS +
+ +

On Telegram since October 2018

+ +

August 2018

+

Chat Export Tool, Better Notifications and More

+

This update brought an easy way to download copies of your chats, including photos and other media using Telegram Desktop. August '18 also saw the birth of Notification Exceptions – a way to customize notification settings for particular users.

+
+ Telegram dude rides a horse-drawn cart with boxes away from a great safe in the clouds. +
+ +

On Telegram since August 2018

+ +

July 2018

+

Introducing Telegram Passport

+

Telegram Passport was launched as a unified authorization service for ICOs, financial services and other platforms based on real-life ID. You no longer have to upload scans of your ID each time a different service requires it.

+
+ Telegram people show their IDs at a counter while dressed up as Korben and Lilu Dallas from the 'Fifth Element'. +
+ +

On Telegram since July 2018

+ +

June 2018

+

Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More

+

The June '18 update brought the ability to replace photos and videos when editing messages – in case you accidentally sent a picture of your lunch instead of the company's new logo.

+

As of this update, voice and video messages can be played at 2x speed and users can mark chats as read or unread.

+
+ The Telegram lady approaches Leonardo da Vinci who is busy refreshing his Mona Lisa in the Louvre museum. He is wearing 2X headphones and is also offering booklets which likely symbolize vCards. +
+ +

On Telegram since June 2018:

+ +

March 2018

+

Sticker Search, Multiple Photos and More

+

Since they were introduced, stickers have become a key method of communication for many Telegram users. As of this update, users can search for new sticker packs.

+

I'm not addicted to sending stickers. I can stop any time.

+
+ TITLE +
+ +

200,000,000 Monthly Active Users

+

Telegram has never been promoted with ads, so every user joined because they were invited by others. Telegram is more than a messaging app, it's the idea that everyone on the planet has a right to be free.

+
+ Telegram lady in aviator costume leans against her spacecraft on an alien beach, watching a sky full of paper-plane-shaped spaceships traveling between planets. +
+ +

On Telegram since March 2018:

+ +

February 2018

+

Two updates were launched on February 6, 2018.

+

Streaming and Auto-Night Mode on Android

+

This was when the apps got streaming support, allowing you to view videos without waiting for them to fully download. This update also introduced auto-night mode for Android users, shielding weary eyes from bright light when browsing memes in bed.

+
+ TITLE +
+ +

Telegram Login for Websites

+

Another update introduced the Telegram Login Widget for external websites, empowering businesses to use Telegram bots to automate anything from customer support to accepting payments or tracking shipments.

+
+ TITLE +
+ +

On Telegram since February 2018

+ +

January 2018

+

Two updates were launched on January 31, 2018.

+

Telegram X: Progress through Competition

+

Two Telegram X clients were unveiled as alternatives to the main iOS and Android apps – built from the ground up to be faster and easier to use, while featuring smooth animations and a sleek design. Telegram X for iOS has since become the native client on iPhones around the world.

+
+ TITLE +
+ +

TDLib - Build Your Own Telegram

+

The Telegram Database Library helps developers make their own versions of Telegram – and was used to create Telegram X for Android. TDLib handles network implementation, encryption, and local storage, giving third-party developers more time to focus on the fun parts of app design. All the API methods are fully documented and the code is available on GitHub.

+

Both Telegram X and the Telegram Bot API are an example of what can be done with this library.

+
+ TITLE +
+ +

On Telegram since January 2018

+ +
+

2017

+
+

December 2017

+

Themes, Multiple Accounts and More

+

Themes came to iOS, with simple 'Day' and 'Night' options. We considered adding a 'Twilight' option but it got sabotaged by lovesick vampires and werewolves.

+

Android added support for multiple accounts, to quickly switch between up to three profiles (or personalities) without logging out.

+
+ TITLE +
+ + +

On Telegram since December 2017

+ +

November 2017

+

Albums, Saved Messages and Better Search

+

Albums and Saved Messages came to Telegram in November as a way to cut down on clutter and keep things organized. Multiple media items could be sent as one message, neatly arranged instead of filling up the chat with individual messages and multiple notifications.

+

Saved Messages brought bookmarks and personal storage, giving users the ability to forward messages there for later reference.

+
+ TITLE +
+ + +

On Telegram since November 2017

+ +

October 2017

+

Live Locations, Media Player and Languages

+

October '17 expanded location sharing to include a live feed, useful for finding your friends or seeing how far they are from a destination. The interactive maps support multiple users, so your entire group can share their locations and see each other in one place.

+

Telegram also expanded its localization, launching the Translations Platform for users to refine the currently-available translations.

+
+ TITLE +
+ + +

On Telegram since October 2017

+ +
+

August 2017

+

Better Replies, Stickers & Invitations

+

Keeping track of replies and mentions was streamlined in August’s update, adding the new '@' badge to the chat list, and '@' button inside chats to jump from mention to mention.

+

The option to set favorite stickers was added, while groups got the ability to choose official sticker sets.

+
+ TITLE +
+ +

On Telegram since August 2017

+ +
+

July 2017

+

Disappearing Media, Your Bio & More Speed

+

July’s update added a self-destruct timer for photos and videos to give users the option to send disappearing media in Private Chats.

+

To help say a little more about themselves, user profiles were given a bio section.

+
+ TITLE +
+ + +

On Telegram since July 2017

+ +
+

June 2017

+

Supergroups 10,000: Admin Tools & More

+

Groups leveled up in June '17, increasing the maximum members to 10,000 and introducing a suite of new tools to manage the masses.

+

Admin permissions became individual, allowing for specific privileges. So did members’, meaning people could be put under custom restrictions for acting up.

+

The Recent Actions page was added for admins, showing a summary of all notable group activity within the past 48 hours.

+
+ TITLE +
+ + +

On Telegram since June 2017

+ +
+

May 2017

+

Three updates were released on May 18, 2017.

+

Video Messages and Telescope
Just in time for Summer, video messages were introduced to add another dimension to chats and channels.

+
+ TITLE +
+ +

Instant Views for Everyone & a $200K Contest

+

Instant View grew into a platform for reformatting articles from the Web into lightweight, uniform pages which instantly open in Telegram, rather than a browser. A contest to create new templates was launched.

+
+ TITLE +
+ +

Payments for Bots
Bot payments joined the pool party as well, so users could pay for goods and services right in the app.

+
+ TITLE +
+ + +

On Telegram since May 2017

+ +
+

March 2017

+

Voice Calls: Secure, Crystal-Clear, AI-Powered

+

March '17 brought voice calls to Telegram, featuring end-to-end encryption, crisp sound and incredible speed.

+

The video editor received a compression slider to change the quality at which a video is sent.

+
+ TITLE +
+ +

On Telegram since March 2017

+ +
+

February 2017

+

Custom Themes

+

Custom themes first came to the Android phone app, along with a theme editor, giving users the ability to recolor individual elements and share their creations with others.

+
+ TITLE +
+ +

Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL

+

Telegram Desktop, first launched in January '14, reached version 1.0, with a new design, refined animations and custom theme support, in addition to all its earlier features.

+

The GMail bot made its debut as well, allowing users to condense all their communications into one platform.

+
+ TITLE +
+ +

Telegram for Android Wear 2.0

+

Telegram came to wrists with its Android Wear 2.0 version, featuring fully-functional messaging capability, plus added themes to keep things chic.

+
+ TITLE +
+ + +

On Telegram since February 2017

+ +
+

January 2017

+

Unsend Messages, Network Usage, and More

+

Telegram rang in the New Year with a completely new feature - the ability to unsend messages sent within the past 48 hours.

+

To keep track of users' data consumption, Network Usage was added to Settings.

+
+ TITLE +
+ +

On Telegram since January 2017

+ +
+

2016

+
+

December 2016, Second Update

+

Meet the Telegraph API for Logins and Stats

+

The Telegraph API opened to the public in the final update of 2016. Publishing and organizing articles gained automated support with the new @Telegraph bot.

+
+ TITLE +
+ +

On Telegram since December 20, 2016

+ +
+

December 2016, First Update

+

Pinned Chats and IFTTT Integrations

+

Conversation management became easier with the option to pin chats to the top of the chat list.

+

IFTTT integration was introduced to help link Telegram to over 360 services at launch. This gives users control over their accounts on other services straight from the Telegram app – including social media, mail clients and even things like smart appliances or other devices.

+
+ TITLE +
+ +

On Telegram since December 7, 2016

+ +
+

November 2016

+

Instant View, Telegraph, and Other Goodies

+
+ TITLE +
+ +

Instant View came in November 2016, instantly loading articles and web pages all inside the Telegram app. Added in the same update, the Telegraph platform is a minimalist word processor compatible with Instant View, designed for quickly publishing documents and articles.

+

On Telegram since November 2016

+ +
+

This is where wide full-color illustrations for our blog posts end – or begin, depending on which direction you just came from.

+
+
+

October 2016

+

Gaming Platform 1.0

+

With winter not far off, Telegram introduced a Games platform that allows users to play games through bots. Players get the chance to challenge friends, while creators have an easy and accessible way to bring their game ideas to life.

+
+ +
+ +

On Telegram since October 2016

+ +
+

September 2016

+

Photo Editor 2.0, Masks and Homemade GIFs

+

In September '16, the time came to improve Telegram's Photo Editor with fun new decorations like masks, text, stickers and drawings. Additionally, the video editor added the ability to make GIFs out of videos by tapping its new 'Mute' button.

+
+ +
+ +

On Telegram since September 2016

+ +
+

August 2016

+

Trending Stickers, Storage and More

+

A Trending Stickers option was added so popular sticker packs can be easily found and added to one's collection. Groups received previews so prospective members can see what they're about and who's in them before joining the party.

+
+ +
+ +

On Telegram since August 2016

+ +
+

June 2016

+

Drafts, Picture-in-Picture, and More

+

June '16 brought cross-platform cloud drafts, syncing your unfinished messages across devices. Since then, users have been able to start typing on one device and finish on another. For more multitasking, Picture-in-Picture support was added to let users work and watch simultaneously.

+
+ +
+ +

On Telegram since June 2016

+ +
+

May 2016

+

Edit Messages, New Mentions and More

+

Fast typers rejoiced as the ability to edit sent messages was introduced in all chats. Mentions were expanded to include users without usernames, and Bots were given their own space in the attachment menu for easy access.

+
+ +
+ +

On Telegram since May 2016

+ +
+

April 2016, Second Update

+

Instant Camera and More 3D Touch

+

Instant camera was added so users could snap and send photos faster, saving the extra thumb-work to make sure the moment is captured.

+
+ +
+ +

On Telegram since April 28, 2016

+ +
+

April 2016, First Update

+

Bot Platform 2.0

+

Starting in April 2016, inline bots no longer require you to use a keyboard. These software-controlled friends now immediately present clickable options to get results with no typing required. They were also integrated with services like YouTube and Foursquare for easy video and location sharing.

+
+ +
+ +

Sharing and Previews

+

This update gave users a new way of sharing media between chats, introducing GIF and sticker previews to make the selection process more straightforward.

+
+ +
+ +

On Telegram since April 12, 2016

+ +
+

March 2016

+

Supergroups 5000: Public Groups, Pinned Posts

+

To keep order as supergroups grew from 1,000 members to 5,000, important announcements could be placed at the top of the screen as pinned messages. Additional moderation tools were introduced that helped prevent spam in public supergroups. This included the ability to report spam, ban a user outright, or simply erase all of their posts from the group.

+
+ +
+ +

On Telegram since March 2016

+ +
+

February 2016, Second Update

+

Channels 2.0 and More

+

Channels got plenty of new features including admin signatures and silent broadcasts. It became possible to edit your messages in channels and supergroups.

+
+ +
+ +

On Telegram since February 24, 2016

+ +

February 2016, First Update

+

Voice Messages 2.0, Secret Chats 3.0 and…

+

Chatting got easier with raise-to-speak and raise-to-listen functionality, streamlining voice messages by giving a no-tap way to play and record. On the privacy end, users got the ability to restrict who can invite them to groups and channels.

+
+ +
+ +

On Telegram since February 12, 2016

+ +
+

January 2016

+

Introducing Inline Bots

+

Inline bots make it possible to use bot services in any chat without adding those bots as members – you just start any message with their username and everything that comes after becomes a query for the bot. These utilities can link Wikipedia articles, post YouTube videos or search for GIFs to entertain friends. Unfortunately, while being very good at fetch, they still can't pull a sled – even after all these years.

+
+ +
+ +

GIF Revolution

+

GIF file size was reduced by 95%, making them load 20x faster. Autoplay for all GIFs was enabled to show off their new-found speed.

+
+ +
+ +

On Telegram since January 2016

+ +
+

2015

+
+

December 2015

+

Clearing Cache and Reordering Stickers

+

The space-saving option of clearing cache was introduced, including chat-by-chat specificity. This was coupled with a setting to choose how long to keep media before it gets deleted from the cache (to be re-downloaded from the cloud should you need it again).

+
+ +
+ +

On Telegram since December 2015

+ +
+

November 2015

+

Admins, Supergroups and More

+

This update added the admin role. Admins have the power to manage group chats and enforce rules. Just in time, as the maximum number of users for group chats grew to 1,000 people with the addition of supergroups.

+
+ +
+ +

On Telegram since November 2015

+ +
+

September 2015

+

Channels: Broadcasting Done Right

+

September '15 brought channels, the perfect tool for broadcasting messages to the masses. Channels can have unlimited followers, offer view counters for each post and only let the admins post. These one-way chats give updates the spotlight by moving the discussion elsewhere. Channels were quickly adopted in regions where freedom of speech falls short.

+
+ +
+ +

On Telegram since September 2015

+ +
+

August 2015

+

Shared Links and Recent Searches

+

Telegram delivered quality of life updates in August '15, showing shared links on chat info pages as well as a list of recent searches when beginning a new one.

+
+ +
+ +

On Telegram since August 2015

+ +
+

July 2015

+

In-App Media Playback and Search in Chats

+

This update added the ability to view media, enjoy music and watch videos from external sources directly in the app. Chat-specific search was implemented as well, making it easier to find messages from a particular conversation.

+
+ +
+ +

On Telegram since July 2015

+ +
+

June 2015

+

Telegram Bot Platform

+

In June of 2015, Telegram released the Bot API and created a platform for users to create and publish their own bots. Bots exist to add features to Telegram and make user's lives easier - bots can handle payments, moderate groups, fetch emails and much more.

+
+ +
+ +

Telegram on Apple Watch

+

Telegram also received Apple Watch support. With a flick of the wrist, users can view recent chats, reply with stickers, dictate messages and more. Anything that can't fit on the watch display gets a shortcut to open on your phone instead.

+
+ +
+ +

On Telegram since June 2015

+ +
+

May 2015

+

Custom Sticker Sets

+

Since May '15, stickers can be uploaded and shared as sticker sets. All apps got a dedicated sticker panel. Tapping on any sticker shows its set and lets you add the lot.

+
+ +
+ +

On Telegram since May 2015

+ +
+

April 2015

+

Migrating Existing Group Chats to Telegram

+

Invite links were added so users can easily bring their friends to group chats, even when those friends are lost in another messenger.

+
+ +
+ +

Places, Captions and more

+

Users gained the ability to caption photos, so the context and content can be sent as one message.

+
+ +
+ +

Active Sessions and Two-Step Verification

+

Telegram rolled out an essential privacy feature in April 2015 - Two-step Verification – adding an extra layer of protection by requiring a password when logging into a new device.

+
+ +
+ +

Link Previews

+

Link previews were introduced to help users see where a link leads without having to click on it and find out for themselves.

+
+ +
+ +

On Telegram since April 2015

+ +
+

March 2015, Second Update

+

Sending Files On Steroids — And More

+

This update brought the ability to send multiple files at once and trim videos before sending them.

+
+ +
+ +

On Telegram since March 25, 2015

+ +
+

March 2015, First Update

+

Reinventing Group Chats: Replies, Mentions, Hashtags and More

+

March '15 made messaging more convenient – Telegram added replies, mentions and hashtags. Replies make it easier to keep continuity in group chats, while mentions help get someone's attention and hashtags allow users to label messages for future use.

+
+ +
+ +

On Telegram since March 19, 2015

+ +
+

February 2015, Second Update

+

Photo Editor and Passcode Lock

+

February '15 delivered the most powerful photo editor among messaging apps – featuring auto-enhance, crop and rotate functions in its initial version. To keep those photos and chats secure, users were given the option to lock their app with a passcode.

+
+ +
+ +

On Telegram since February 25, 2015

+ +
+

February 2015, First Update

+

Shared Files and Fast Mute

+

This update introduced the Files tab to better view all documents shared in a particular chat (some media outlets mistakenly thought this was when we introduced sending files). Additionally, the update brought in Mute shortcuts, helping users disable notifications more quickly.

+
+ +
+ +

On Telegram since February 1, 2015

+ +
+

January 2015

+

Stickers Done Right

+

January '15 saw the first sticker on Telegram. Since then, starting a message with a single emoji brings up a list of emotionally corresponding sticker suggestions.

+

The first official stickers from Telegram formed the classic Great Minds set. Artists were invited to publish their work on the free and open platform.

+
+ +
+ +

On Telegram since January 2015

+ +
+

2014

+
+

December 2014

+

Telegram.me, Changing Numbers, PFS and more

+

Users with usernames were offered Telegram.me/username links, which open their profile page in Telegram. This update also enabled changing the phone number of a Telegram account. Single-column mode was added for Telegram Desktop, making multitasking easier on smaller screens.

+
+ +
+ +
+

Fun fact: In 2016, Instagram will restrict users from adding Telegram.me (and Snapchat) links to their bios.

+
+

On Telegram since December 2014

+ +
+

November 2014

+

There were two Telegram updates on November 19, 2014.

+

Hiding Last Seen Time - Done Right

+

This update expanded Privacy Settings to cover Last Seen status, allowing unprecedented flexibility with 'Always Share With' and 'Never Share With' exceptions for individual users.

+

This was also when account self-destruction was introduced. Telegram doesn't aim to accumulate and store your data when you don't need it anymore. So if you throw away your SIM card and it gets a new owner in 6 months, they won't access your chats.

+
+ +
+ +

Material Design on Android, Instant Search for Messages and more

+

November '14 also delivered Instant Full-Text Search to iOS and Android. Since then you can quickly find any message you ever sent or received on Telegram.

+

GIF search was first supported on iOS. The Android app got a massive redesign, consistent with material guidelines.

+
+ +
+ +

On Telegram since November 2014

+ +
+

October 2014

+

Public usernames, smaller timers for Secret Chats, and more

+

October '14 marks the beginning of properly recorded history on Telegram. The first update ever to be described in a blog post brought public usernames, adding the ability to share your Telegram contact without disclosing your phone number.

+

Secret Chats got a major upgrade, with self-destructing media showing blurred thumbnails and starting the countdown only after they are first opened. This prevented them from disappearing before actually being viewed. This was also when screenshot notifications were first introduced.

+

Telegram for Android received several updates, adding support for Android Wear and tablets, as well as video compression.

+
+ +
+ +

On Telegram since October 2014

+ +
+
+ +
+ +

September 2014

+

GIFs, iPad support and broadcast lists on iOS

+

Telegram has supported iPads since September '14. In this update, the iOS app learned to play GIF animations and added cloud search for messages, as well as adding search by file name to the Shared Documents section. iOS also caught up with Android, adding support for broadcast lists.

+
+ +
+ +

On Telegram since September 2014

+ +
+

August 2014

+

Broadcast lists were first introduced to Android in August '14, only to be replaced with channels a little over a year later.

+
+ +
+ +

On Telegram since August 2014

+ +
+

June 2014

+

Multiple photo upload and more

+

Telegram for Android caught up with iOS, allowing users to preview photos before sending — as well as select and send many photos at once. Notifications were improved to be more reliable.

+
+ +
+ +

On Telegram since June 2014

+ +
+

March 2014

+

Voice Messages, Delete Messages for both sides in Secret Chats, Language Settings on Android

+

The March '14 update introduced voice messages to Telegram. Messages deleted in Secret Chats began disappearing for both sides.

+

Telegram for Android added the option to change the app language in Settings. The first languages to be added were German and Italian.

+
+ +
+ +

On Telegram since March 2014

+ +
+

February 2014

+

New apps, autodownload settings and contact management tools for Android

+

More Telegram apps entered the fray. An unofficial Telegram app for Web was introduced and later moved to web.telegram.org to become the official web version. Telegram for Windows Phone was created in a contest for app developers.

+

Meanwhile, an update introduced autodownload settings and new tools to manage contacts on Android.

+
+ +
+ +

On Telegram since February 2014

+ +
+

January 2014

+

Send documents and files

+

First thing in 2014, Telegram allowed documents of any type to be sent, including .pdf, .doc, .png, .mp3, etc. The size limit is 1,5 GB per file.

+

An unofficial Telegram app for PC was announced, which would later become the official Telegram Desktop.

+
+ +
+ +

On Telegram since January 2014

+ +
+

2013

+
+

December 2013

+

Crowdsourcing a more secure future

+

The only significant vulnerability to ever be discovered in the MTProto protocol was fixed during the First Telegram Crypto Contest. The researcher who discovered it was awarded a bounty of $100,000.

+
+ +
+ +

On Telegram since December 2013

+ +
+

October 2013

+

After a contest for Android developers, the alpha version of Telegram for Android was officially launched. Telegram apps got Secret Chats with self-destruct timers.

+

The MTProto Protocol specification and Telegram API were fully documented and the code of the apps became open source.

+
+ +
+ +

On Telegram since October 2013

+ +
+

August 14, 2013

+

Telegram for iOS was launched.

+
+

Congratulations on completing this (not very) brief course on the history of Telegram. You just got an honorary PhD in Instant Messaging – unless you simply jumped down here, in which case you still have a long way 👆to go to get back to the top.

+
+

Armed with this much knowledge about Telegram, you should probably join our Volunteer Support Force.

+
+
+ +
+
+ +
+
+
+ + + + + + + + + diff --git a/data/telegram.org/faq.html b/data/telegram.org/faq.html new file mode 100644 index 0000000000..720991cb7e --- /dev/null +++ b/data/telegram.org/faq.html @@ -0,0 +1,705 @@ + + + + + Telegram FAQ + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Telegram FAQ

+ +
+

This FAQ provides answers to basic questions about Telegram.
Check out our Advanced FAQ for more technical information.

+
+

+

General

+ +

Telegram Basics

+ +

Groups and Channels

+ +

Usernames and t.me

+ +

Security

+ +

Secret Chats

+ +

Your Account

+ +

Bots

+ +

Deeper Questions

+ +

Troubleshooting

+ +

Contact Telegram Support
Follow Us on Twitter
Facebook
Advanced FAQ

+

+
+

General Questions

+

Q: What is Telegram? What do I do here?

+

Telegram is a messaging app with a focus on speed and security, it’s super-fast, simple and free. You can use Telegram on all your devices at the same time — your messages sync seamlessly across any number of your phones, tablets or computers. Telegram has over 500 million monthly active users and is one of the 10 most downloaded apps in the world.

+

With Telegram, you can send messages, photos, videos and files of any type (doc, zip, mp3, etc), as well as create groups for up to 200,000 people or channels for broadcasting to unlimited audiences. You can write to your phone contacts and find people by their usernames. As a result, Telegram is like SMS and email combined — and can take care of all your personal or business messaging needs. In addition to this, we support end-to-end encrypted voice and video calls, as well as voice chats in groups for thousands of participants.

+
+

Follow our Tips Channel to learn more about Telegram features.

+
+

Q: Who is Telegram for?

+

Telegram is for everyone who wants fast and reliable messaging and calls. Business users and small teams may like the large groups, usernames, desktop apps and powerful file sharing options.

+

Since Telegram groups can have up to 200,000 members, we support replies, mentions and hashtags that help maintain order and keep communication in large communities efficient. You can appoint admins with advanced tools to help these communities prosper in peace. Public groups can be joined by anyone and are powerful platforms for discussions and collecting feedback.

+

In case you're more into pictures, Telegram has animated gif search, a state of the art photo editor, and an open sticker platform (find some cool stickers here or here). What's more, there is no need to worry about disk space on your device. With Telegram's cloud support and cache management options, Telegram can take up nearly zero space on your phone.

+

Those looking for extra privacy should check out our advanced settings and rather revolutionary policy. And if you want secrecy, try our device-specific Secret Chats with self-destructing messages, photos, and videos — and lock your app with an additional passcode.

+
+

We keep evolving — check out our Brief History of Telegram and follow us on twitter and Telegram to stay in touch.

+
+

Q: How is Telegram different from WhatsApp?

+

Unlike WhatsApp, Telegram is a cloud-based messenger with seamless sync. As a result, you can access your messages from several devices at once, including tablets and computers, and share an unlimited number of photos, videos and files (doc, zip, mp3, etc.) of up to 2 GB each.

+

Telegram needs less than 100 MB on your device – you can keep all your media in the cloud without deleting things – simply clear your cache to free up space.

+

Thanks to Telegram's multi-data center infrastructure and encryption, it is faster and way more secure. On top of that, private messaging on Telegram is free and will stay free — no ads, no subscription fees, forever.

+

Telegram's API and code is open, and developers are welcome to create their own Telegram apps. We also have a Bot API, a platform for developers that allows anyone to easily build specialized tools for Telegram, integrate any services, and even accept payments from users around the world.

+

And that's just the tip of the iceberg.

+
+

Follow our Tips Channel to learn more about Telegram features.

+
+

Q: How old is Telegram?

+

Telegram for iOS was launched on August 14, 2013. The alpha version of Telegram for Android officially launched on October 20, 2013. More and more Telegram clients appear, built by independent developers using Telegram's open platform.

+

Q: Which devices can I use?

+

You can use Telegram on smartphones, tablets, and even computers. We have apps for iOS (9.0 and above), Android (4.1 and up), a native macOS app and a universal desktop app for Windows, macOS, and Linux. Telegram Web can also help to quickly do something on the go.

+
+

You can log in to Telegram from as many of your devices as you like — all at the same time. Just use your main mobile phone number to log in everywhere, your cloud chats will sync instantly.

+
+

The Telegram API is open for developers, should you want to build your own applications for other platforms.

+

Q: Who are the people behind Telegram?

+

Telegram is supported by Pavel Durov and his brother Nikolai. Pavel supports Telegram financially and ideologically while Nikolai's input is technological. To make Telegram possible, Nikolai developed a unique custom data protocol, which is open, secure and optimized for work with multiple data-centers. As a result, Telegram combines security, reliability and speed on any network.

+
+

See also: articles about Telegram

+
+

Q: Where is Telegram based?

+

The Telegram development team is based in Dubai.

+

Most of the developers behind Telegram originally come from St. Petersburg, the city famous for its unprecedented number of highly skilled engineers. The Telegram team had to leave Russia due to local IT regulations and has tried a number of locations as its base, including Berlin, London and Singapore. We’re currently happy with Dubai, although are ready to relocate again if local regulations change.

+

Q: Will you have ads in my private chats and groups? Or sell my data? Or steal my beloved and enslave my children?

+

No. See this post for details.

+

Q: How are you going to make money out of this?

+

We believe in fast and secure messaging that is also 100% free.

+

Our founder and CEO Pavel Durov, who financed Telegram throughout most of its history, has outlined a strategy to make Telegram sustainable in this post.

+

While Telegram will introduce monetization in 2021 to pay for the infrastructure and developer salaries, making profits will never be an end-goal for us.

+

Q: What are your thoughts on internet privacy?

+

We think that the two most important components of Internet privacy should be:

+
    +
  1. Protecting your private conversations from snooping third parties, such as officials, employers, etc.
  2. +
  3. Protecting your personal data from third parties, such as marketers, advertisers, etc.
  4. +
+

Telegram's aim is to create a truly free messenger, with a revolutionary privacy policy.

+

Q: What about GDPR?

+

The General Data Protection Regulation (GDPR) came into force in Europe on May 25, 2018. Since taking back our right to privacy was the reason we made Telegram, there wasn't much we had to change. We don’t use your data for ad targeting, we don’t sell it to others, and we're not part of any mafia family “family of companies.”

+

Telegram only keeps the information it needs to function as a feature-rich cloud service. For example, your cloud chats – so that you can access them from any devices without using third-party backups, or your contacts – so that you can rely on your existing social graph when messaging people on Telegram. Please see our Privacy Policy for more information.

+

You can use @GDPRbot to:

+
    +
  • Request a copy of all your data that Telegram stores.
  • +
  • Contact us about Data Privacy.
  • +
+

Q: There's illegal content on Telegram. How do I take it down?

+

All Telegram chats and group chats are private amongst their participants. We do not process any requests related to them.

+

But sticker sets, channels, and bots on Telegram are publicly available. If you find sticker sets or bots on Telegram that you think are illegal, please ping us at abuse@telegram.org.

+

You can also use the 'report' buttons right inside our apps, see this post on our official @ISISwatch channel for details.

+
+

Note: If a scammer is pretending to be you, contact @NoToScam

+
+

Q: A bot or channel is infringing on my copyright. What do I do?

+

All Telegram chats and group chats are private amongst their participants. We do not process any requests related to them. But sticker sets, channels, and bots on Telegram are publicly available.

+

If you see a bot, channel, or sticker set that is infringing on your copyright, kindly submit a complaint to dmca@telegram.org. Please note that such requests should only be submitted by the copyright owner or an agent authorized to act on the owner’s behalf.

+

Q: Wait! 0_o Do you process take-down requests from third parties?

+

Our mission is to provide a secure means of communication that works everywhere on the planet. To do this in the places where it is most needed (and to continue distributing Telegram through the App Store and Google Play), we have to process legitimate requests to take down illegal public content (e.g., sticker sets, bots, and channels) within the app. For example, we can take down sticker sets that violate intellectual property rights or porn bots.

+

User-uploaded stickers sets, channels, and bots by third-party developers are not part of the core Telegram UI. Whenever we receive a complaint at abuse@telegram.org or dmca@telegram.org regarding the legality of public content, we perform the necessary legal checks and take it down when deemed appropriate.

+

Please note that this does not apply to local restrictions on freedom of speech. For example, if criticizing the government is illegal in some country, Telegram won't be a part of such politically motivated censorship. This goes against our founders' principles. While we do block terrorist (e.g. ISIS-related) bots and channels, we will not block anybody who peacefully expresses alternative opinions.

+

Q: My bot or sticker set was banned unfairly, what do I do?

+

If you think we banned your bot, channel, or sticker set for no apparent reasons, drop us a line at abuse@telegram.org.

+

Q: Do you process data requests?

+

Secret chats use end-to-end encryption, thanks to which we don't have any data to disclose.

+

To protect the data that is not covered by end-to-end encryption, Telegram uses a distributed infrastructure. Cloud chat data is stored in multiple data centers around the globe that are controlled by different legal entities spread across different jurisdictions. The relevant decryption keys are split into parts and are never kept in the same place as the data they protect. As a result, several court orders from different jurisdictions are required to force us to give up any data.

+

Thanks to this structure, we can ensure that no single government or block of like-minded countries can intrude on people's privacy and freedom of expression. Telegram can be forced to give up data only if an issue is grave and universal enough to pass the scrutiny of several different legal systems around the world.

+

To this day, we have disclosed 0 bytes of user data to third parties, including governments.

+

Telegram Basics

+
+

Follow our Tips Channel to learn more about Telegram features.

+
+

Q: Who can I write to?

+

You can write to people who are in your phone contacts and have Telegram. Another way of contacting people is to type their Telegram username into the search field – you don't need to know their phone number to do this.

+

Q: Who can contact me?

+

People can contact you on Telegram if they know your phone number or if you message them first.

+

If they don't know your phone number, they can find you in these cases:

+
    +
  • When you both are members of the same group.
  • +
  • If you set a public username. Others can use Global Search and find you by your username.
  • +
  • If you opt-in to appear in the People Nearby section (this is turned off by default).
  • +
+

Q: How do I know who in my contacts has Telegram?

+

Your contacts, who have Telegram, are shown at the top of your Contacts. They also have pictures.

+

Q: How do I invite my friends?

+

iOS: The basic invitations are simple SMS messages. They will be charged as standard outgoing SMS by your carrier (unless sent via iMessage). Naturally, you have other options to bring your friends here. Try sending them a download link via any other messaging service: email, Facebook, WhatsApp, an actual telegram — you name it. The link: https://telegram.org/dl/

+

Android: Open the app menu (swipe right in chat list) > Invite Friends. Then choose an application via which you would like to send out invitations.

+
+

You can give your friends a t.me link with your username so that they can easily find you on Telegram even if they don't have your phone number.

+
+

Q: What do the check marks mean?

+

One check — message delivered to the Telegram cloud and your friend has been notified if he allows notifications.
Two checks — message read (your friend opened Telegram and opened the conversation with the message).

+

We don't have a 'delivered to device' status for messages because Telegram can run on as many devices as you want. So which particular one would that check mean?

+

Q: Can I hide my ‘last seen’ time?

+

You can choose who sees this info in Privacy and Security settings.

+

Remember that you won't see Last Seen timestamps for people with whom you don't share your own. You will, however, see an approximate last seen value. This keeps stalkers away but makes it possible to understand whether a person is reachable over Telegram. There are four possible approximate values:

+
    +
  • Last seen recently — covers anything between 1 second and 2-3 days
  • +
  • Last seen within a week — between 2-3 and seven days
  • +
  • Last seen within a month — between 6-7 days and a month
  • +
  • Last seen a long time ago — more than a month (this is also always shown to blocked users)
  • +
+

Q: Who can see me 'online'?

+

The last seen rules apply to your online status as well. People can only see you online if you're sharing your last seen status with them.

+

There are some exceptions because sometimes it is obvious that you are online. Regardless of the last seen settings, people will see you online for a brief period (~30 seconds) if you do the following:

+
    +
  • Send them a message in a one-on-one chat or in a group where you both are members.
  • +
  • Read a message they sent you in a one-on-one chat.
  • +
  • Broadcast a “typing…” status to their chat with you or to a group where you both are members.
  • +
+

If you're not sharing your last seen timestamp with someone and don't do anything of the above, they'll never see you online. Another way of achieving this is to block that person.

+

Q: What is People Nearby?

+

People Nearby is an optional feature that allows Telegram users to explore local groups, find friends to chat with in their area, or quickly exchange contacts with people who are close.

+

You can find it in Contacts > Find People Nearby, as well as directly in the side menu on Android.

+

While you have the People Nearby section open on your screen, people who are very close will be able to see you there. If you don't open the section, others will never see you in 'People Nearby'.

+

You can also choose to permanently add your profile to the list of nearby people by tapping Make Myself Visible. After becoming visible, you can remove your profile from the list at any time by tapping Stop Showing Me.

+
+

Note: People Nearby is never turned on by default – users must manually enable it. If you are receiving messages from someone you don't know, see Q: Who can contact me?

+
+

Q: Can I delete my messages?

+

Yes. You can always delete any messages you sent or received for both sides in any one-on-one conversation (in groups, it's still your own messages only). You can also clear the entire chat history on both ends. On Telegram, deleted messages do not leave a mark in the chat.

+
+ +
+ +

Together with privacy settings for forwarded messages, this makes exchanging Telegram messages similar to talking face to face (without a tape recorder). As a result, users no longer need to worry about the data accumulating in their chats over the years. Both parties in a conversation have full control over what does and what doesn't belong to their online identity.

+

Q: Can I make calls via Telegram?

+

Yes! You can make end-to-end encrypted Voice Calls and Video Calls.

+

If you want more participants, try starting a Voice Chat in one of the groups you created. Voice Chats add a live layer of ephemeral talk to the group. They can be used as virtual office spaces for teams or informal lounges for any community. While Voice Chats are not group calls, they can achieve similar goals.

+

Q: How can I use emoticons?

+

Type one word in your input field to get relevant emoji suggestions. You can also type “:” followed by any keyword to open emoji search – like :heart.

+

You can suggest missing keywords for emoji in your language using this interface (this will open suggestions for English, don't forget to change to your language in the left menu).

+

Groups and Channels

+

Q: What makes Telegram groups cool?

+

Telegram groups can have up to 200,000 members each and are extremely powerful communication tools. Here are a few key features that make them stand out in the messaging world:

+

Unified history
Edit your messages after posting, delete them so that they disappear for everyone.

+

Cross-platform availability
Access your messages anytime, from any number of your mobile or desktop devices.

+

Instant search
Find the message you're looking for, even among millions. Filter by sender to make searching easier.

+

Replies, mentions, hashtags
Easily trace a conversation and keep communication efficient, no matter the group size.

+

Smart notifications
Mute the group to get notifications only when people mention you or reply to your messages.

+

Pinned messages
You can pin any message to be displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from your group.

+

Moderation tools
Appoint administrators that can mass-delete messages, control membership, and pin important messages. Define their admin privileges with granular precision.

+

Group permissions
Set default permissions to restrict all members from posting specific kinds of content. Or even restrict members from sending messages altogether – and let the admins chat amongst themselves while everybody else is watching.

+

File sharing
Send and receive files of any type, up to 2 GB in size each, access them instantly on your other devices.

+

Public groups
Get a short link for your group and make it public, like t.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

+

Customization via bots
Create custom tools for any specific needs using our Bot API and Inline Bots.

+

Q: What's the difference between groups and channels?

+

Telegram groups are ideal for sharing stuff with friends and family or collaboration in small teams. But groups can also grow very large and support communities of up to 200,000 members. You can make any group public, toggle persistent history to control whether or not new members have access to earlier messages and appoint administrators with granular privileges. You can also pin important messages to the top of the screen so that all members can see them, including those who have just joined.

+

Channels are a tool for broadcasting messages to large audiences. In fact, a channel can have an unlimited number of subscribers. When you post in a channel, the message is signed with the channel's name and photo and not your own. Each message in a channel has a view counter that gets updated when the message is viewed, including its forwarded copies.

+
+

Read more about channels in the Channels FAQ »

+
+

Q: How do I create a group?

+

iOS: Start a new message (tap the icon in the top right corner in Chats) > 'New Group'.
Android: Tap the circular pencil icon in the chat list > 'New Group'.
Telegram Desktop: Click the menu button in the top left corner > 'New Group'.

+

Q: Can I assign administrators?

+

You can add administrators to help you manage your group and define their privileges with granular precision.

+

iOS: Go to Group Info (tap the photo in the top right corner on the group‘s chat screen) > Edit > Administrators.
Android: Go to Group Info (tap the name in the header) > the pencil icon (in the top right corner) > Administrators.
Telegram Desktop: When in the group, click '…' in the top right corner > Manage group > Administrators.

+

Q: How do I add more members? What's an invite link?

+

You can add your contacts, or using search by username.

+

It is easy to migrate existing groups to Telegram by sending people an invite link. To create an invite link, go to Group Info > Add Member > Invite to Group via Link.

+

Anyone who has Telegram installed will be able to join your group by following this link. If you choose to revoke the link, it will stop working immediately.

+
+

Read more about invite links in our blog »

+
+

Usernames and t.me

+

Q: What are usernames? How do I get one?

+

You can set up a public username on Telegram. It then becomes possible for other users to find you by that username — you will appear in contacts search under 'global results'. Please note that people who find you will be able to send you messages, even if they don't know your number. If you are not comfortable with this, we advise against setting up a username in Telegram.

+

You can set up a username in Settings and use the universal search box in the chat list to search for chats, messages, and usernames.

+

Q: How does t.me work?

+

Once you've set up a username, you can give people a t.me/username link. Opening that link on their phone will automatically fire up their Telegram app and open a chat with you. You can share username links with friends, write them on business cards or put them up on your website.

+

This way people can contact you on Telegram without knowing your phone number.

+

Q: What can I use as my username?

+

You can use a-z, 0-9 and underscores. Usernames are case-insensitive, but Telegram will store your capitalization preferences (e.g. Telegram and TeleGram is the same user). The username must be at least five characters long.

+

Q: Do I need a username?

+

You don't have to get one. Remember that Telegram usernames are public and choosing a username on Telegram makes it possible for people to find you in global search and send you messages even if they don't have your number. If you are not comfortable with this, we advise against setting up a username.

+

Q: If someone finds me by username, messages and I reply — will they know my number?

+

No. Neither party will see another's phone number (unless this is permitted by your privacy settings). This is similar to the case when you message a person who you've met in a Telegram group.

+

Q: How do I delete my username?

+

Go to Settings and save an empty username. This will remove your username; people will no longer be able to find you via search. This will not affect existing conversations.

+

Q: What do I do if my username is taken?

+

Telegram usernames are distributed on a first come — first serve basis.

+

We understand that certain usernames are part of an online identity for some of us. If your desired username is already taken, we will be happy to help you acquire it for your account or channel, provided that you have that same username on at least two of these services: Facebook, Twitter, Instagram.

+

Due to the fact that one account can register multiple bot and channel usernames, we reserve the right to recall usernames assigned to unused bots and channels, as well as openly squatted usernames.

+

To request a username, contact @Username_bot.

+

Q: What if someone is pretending to be me?

+

If a scammer is pretending to be you, please contact @NoToScam.

+

Security

+
+

If you are an advanced user, you may find our FAQ for the Technically Inclined useful as well.

+
+

Q: How secure is Telegram?

+

Telegram is more secure than mass market messengers like WhatsApp and Line. We are based on the MTProto protocol (see description and advanced FAQ), built upon time-tested algorithms to make security compatible with high-speed delivery and reliability on weak connections. We are continuously working with the community to improve the security of our protocol and clients.

+

Q: What if I’m more paranoid than your regular user?

+

We've got you covered. Telegram’s special secret chats use end-to-end encryption, leave no trace on our servers, support self-destructing messages and don’t allow forwarding. On top of this, secret chats are not part of the Telegram cloud and can only be accessed on their devices of origin.

+

Q: So how do you encrypt data?

+

We support two layers of secure encryption. Server-client encryption is used in Cloud Chats (private and group chats), Secret Chats use an additional layer of client-client encryption. All data, regardless of type, is encrypted in the same way — be it text, media or files.

+

Our encryption is based on 256-bit symmetric AES encryption, 2048-bit RSA encryption, and Diffie–Hellman secure key exchange. You can find more info in the Advanced FAQ.

+
+

See also: Do you process data requests?

+
+

Q: Why should I trust you?

+

Telegram is open, anyone can check our source code, protocol and API, see how everything works and make an informed decision. Telegram supports verifiable builds, which allow experts to independently verify that our code published on GitHub is the exact same code that is used to build the apps you download from App Store or Google Play.

+

We welcome security experts to audit our system and appreciate any feedback at security@telegram.org.

+

On top of that, Telegram's primary focus is not to bring a profit, so commercial interests will never interfere with our mission.

+
+

See also: articles about Telegram

+
+

Q: Do I need to trust Telegram for this to be secure?

+

When it comes to secret chats, you don't — just make sure that the visualized key of your secret chat matches the one in your friend's secret chat settings. More about this below.

+

Q: What if my hacker friend says they could decipher Telegram messages?

+

Anyone who claims that Telegram messages can be deciphered is welcome to prove that claim in our competition and win $300,000. You can check out the Cracking Contest Description to learn more.

+

Any comments on Telegram's security are welcome at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $100 to $100,000 or more, depending on the severity of the issue. Please note that we can not offer bounties for issues that are disclosed to the public before they are fixed.

+

Q: Can Telegram protect me against everything?

+

Telegram can help when it comes to data transfer and secure communication. This means that all data (including media and files) that you send and receive via Telegram cannot be deciphered when intercepted by your internet service provider, owners of Wi-Fi routers you connect to, or other third parties.

+

But please remember that we cannot protect you from your own mother if she takes your unlocked phone without a passcode. Or from your IT-department if they access your computer at work. Or from any other people that get physical or root access to your phones or computers running Telegram.

+

If you have reasons to worry about your personal security, we strongly recommend using only Secret Chats in official or at least verifiable open-source apps for sensitive information, preferably with a self-destruct timer. We also recommend enabling 2-Step Verification and setting up a strong passcode to lock your app, you will find both options in Settings > Privacy and Security.

+

Q: How does 2-Step Verification work?

+

Logging in with an SMS code is an industry standard in messaging, but if you're looking for more security or have reasons to doubt your mobile carrier or government, we recommend protecting your cloud chats with an additional password.

+

You can do this in Settings > Privacy and Security > 2-Step Verification. Once enabled, you will need both an SMS code and a password to log in. You can also set up a recovery email address that will help regain access, should you forget your password. If you do so, please remember that it's important that the recovery email account is also protected with a strong password and 2-Step Verification when possible.

+

Check this out for tips on creating a strong password that is easy to remember.

+

Q: Why can jailbroken and rooted devices be dangerous?

+

Using a rooted or jailbroken device makes it easier for a potential attacker to gain full administrative control over your device — root access.

+

A user with root access can easily bypass security features built into the operating system, read process memory or access restricted areas, such as the internal storage. Once an attacker has root access, any efforts to mitigate threats become futile. No application can be called safe under these circumstances, no matter how strong the encryption.

+

Secret Chats

+

Q: How are secret chats different?

+

Secret chats are meant for people who want more secrecy than the average fella. All messages in secret chats use end-to-end encryption. This means only you and the recipient can read those messages — nobody else can decipher them, including us here at Telegram (more on this here). On top of this, Messages cannot be forwarded from secret chats. And when you delete messages on your side of the conversation, the app on the other side of the secret chat will be ordered to delete them as well.

+

You can order your messages, photos, videos and files to self-destruct in a set amount of time after they have been read or opened by the recipient. The message will then disappear from both your and your friend's devices.

+

All secret chats in Telegram are device-specific and are not part of the Telegram cloud. This means you can only access messages in a secret chat from their device of origin. They are safe for as long as your device is safe in your pocket.

+

Q: How do I start a secret chat?

+

Open the profile of the user you want to contact. Tap on ‘…’, then ‘Start Secret Chat’.

+

Remember that Telegram secret chats are device-specific. If you start a secret chat with a friend on one of your devices, this chat will only be available on that device. If you log out, you will lose all your secret chats. You can create as many different secret chats with the same contact as you like.

+

Q: How do self-destructing messages work?

+

The Self-Destruct Timer is available for all messages in Secret Chats and for media in private cloud chats.

+

To set the timer, simply tap the clock icon (in the input field on iOS, top bar on Android), and then choose the desired time limit. The clock starts ticking the moment the message is displayed on the recipient's screen (gets two check marks). As soon as the time runs out, the message disappears from both devices. We will try to send a notification if a screenshot is taken.

+

Please note that the timer in Secret Chats only applies to messages that were sent after the timer was set. It has no effect on earlier messages.

+

Q: Can I be certain that my conversation partner doesn't take a screenshot?

+

Unfortunately, there is no bulletproof way of detecting screenshots on certain systems (most notably, some Android and Windows Phone devices). We will make every effort to alert you about screenshots taken in your Secret Chats, but it may still be possible to bypass such notifications and take screenshots silently. We advise to share sensitive information only with people you trust. After all, nobody can stop a person from taking a picture of their screen with a different device or an old school camera.

+

Q: What is this 'Encryption Key' thing?

+

When a secret chat is created, the participating devices exchange encryption keys using the so-called Diffie-Hellman key exchange. After the secure end-to-end connection has been established, we generate a picture that visualizes the encryption key for your chat. You can then compare this image with the one your friend has — if the two images are the same, you can be sure that the secret chat is secure, and no man-in-the-middle attack can succeed.

+

Newer versions of Telegram apps will show a larger picture along with a textual representation of the key (this is not the key itself, of course!) when both participants are using an updated app.

+

Always compare visualizations using a channel that is known to be secure — it's safest if you do this in person, in an offline meeting with the conversation partner.

+

Q: Why not just make all chats 'secret'?

+

All Telegram messages are always securely encrypted. Messages in Secret Chats use client-client encryption, while Cloud Chats use client-server/server-client encryption and are stored encrypted in the Telegram Cloud (more here). This enables your cloud messages to be both secure and immediately accessible from any of your devices – even if you lose your device altogether.

+

The problem of restoring access to your chat history on a newly connected device (e.g. when you lose your phone) does not have an elegant solution in the end-to-end encryption paradigm. At the same time, reliable backups are an essential feature for any mass-market messenger. To solve this problem, some applications (like Whatsapp and Viber) allow decryptable backups that put their users' privacy at risk – even if they do not enable backups themselves. Other apps ignore the need for backups altogether and leave their users vulnerable to data loss.

+

We opted for a third approach by offering two distinct types of chats. Telegram disables default system backups and provides all users with an integrated security-focused backup solution in the form of Cloud Chats. Meanwhile, the separate entity of Secret Chats gives you full control over the data you do not want to be stored.

+

This allows Telegram to be widely adopted in broad circles, not just by activists and dissidents, so that the simple fact of using Telegram does not mark users as targets for heightened surveillance in certain countries. We are convinced that the separation of conversations into Cloud and Secret chats represents the most secure solution currently possible for a massively popular messaging application.

+
+

See also: Why Telegram isn't End-to-End Encrypted “by Default”

+
+

Your Account

+

Q: Who can see my phone number?

+

On Telegram, you can send messages in private chats and groups without making your phone number visible. By default, your number is only visible to people who you've added to your address book as contacts. You can further modify this in Settings > Privacy and Security > Phone Number.

+
+

Note that people will always see your number if they know it already and saved it in their address book.

+
+

Q: I have a new phone number, what do I do?

+

Each phone number is a separate account on Telegram. You have several options if you are using multiple phone numbers:

+
    +
  • If you will no longer use the old number (e.g., you moved to a new country or changed your number for good), simply go to Settings and change the number connected to your Telegram account to the new number. Important: make sure you have access to your connected phone number – otherwise you risk losing access to your account.
  • +
  • If you will use the new number for a limited time (e.g., you're on a trip or vacation), there's no need to do anything.
  • +
  • If you want to keep using both numbers (e.g., you have a work phone and personal phone), choose one as your Telegram number. You may create another Telegram account on the second number as well, for example, if you want to keep work and personal chats separated. It is possible to log in to one Telegram app with up to 3 different accounts at once.
  • +
+

Q: How do I log out?

+

Most users don't need to log out of Telegram:

+
    +
  • You can use Telegram on many devices at the same time. Just use the same phone number to log in on all devices.
  • +
  • You can go to Settings > Data and Storage > Storage Usage> Clear cache to free up space on your device without logging out.
  • +
  • If you use Telegram with multiple phone numbers, you can switch between accounts without logging out.
  • +
  • If you use Telegram on a shared device, you can set up a passcode in Settings > Privacy and Security to make sure only you have access to your account.
  • +
+

If you do want to log out for some reason, here's how you do that:

+

iOS: Go to Settings > Edit > Log out.
Android, Telegram Desktop: Go to Settings > … (in the top right corner) > Log out.

+

If you log out, you will keep all your cloud messages. However, you will lose all your Secret Chats and all messages inside those secret chats when you log out.

+
+

Note that logging out does not trigger remote deletion of your secret chat messages on your partner's device — to do that, choose 'Clear History' first.

+
+

Q: How do I change my phone number?

+

You can change your number in Telegram and keep everything, including all your contacts, messages, and media from the Telegram cloud, as well as all your Secret Chats on all devices.

+

To change your number, go to Settings, then tap on your phone number (just above the username), then 'Change Number'. If you already have a different Telegram account on the target number, you'll need to delete that account first.

+

Q: How do I delete my account?

+

If you would like to delete your account, you can do this on the deactivation page. Deleting your account permanently removes all your messages and contacts. All groups and channels that you've created are orphaned and left without a creator but admins retain their rights.

+

This action must be confirmed via your Telegram account and cannot be undone.

+
+

We recommend using a non-mobile browser for this process.
Note that you'll receive the code via Telegram, not SMS.

+
+

Q: What happens if I delete my account?

+

As was just mentioned above, all your data will be flushed from our system: all messages, groups, and contacts associated with your account will be deleted. That said, your contacts will still be able to chat in the groups that you have created, and they will still have their copy of the messages you sent them. So if you want to send messages that can vanish without a trace, try using our self-destruct timer instead.

+

Termination of a Telegram account is irreversible. If you sign up again, you will appear as a new user and will not get your history, contacts or groups back. People, who have your phone number in their contacts, will be notified. The new user will be displayed as a separate conversation in their messages list and their conversation history with this new user will be empty.

+

Q: How does account self-destruction work?

+

Telegram is not a commercial organization, and we value our disk space greatly. If you stop using Telegram and don't come online for at least six months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct in Settings.

+

Q: My phone was stolen, what do I do?

+

First of all, sorry about your phone. Unfortunately, the phone number is the only way for us to identify a Telegram user at the moment. We don't collect additional information about you, so whoever has the number, has the account. This means we can't help you unless you have access either to the phone number or to Telegram itself on any of your devices.

+
I have access to Telegram on another device
+
    +
  1. Go to Telegram Settings > Privacy and Security and turn on Two-Step Verification. This way the phone number alone will not be enough to log in to your account.
  2. +
  3. Go to Settings > Devices (or Privacy & Security > Active Sessions) and terminate your Telegram session on the old device. Whoever has your phone will not be able to log in again, since they don't know your password.
  4. +
  5. Contact your phone provider, so that they block your old SIM and issue a new one with your number.
  6. +
  7. If you decide to switch to a new phone number, don't forget to go to Settings, tap on your phone number and change your Telegram number to the new one.
  8. +
+
I don't have access to Telegram on any other devices
+
    +
  1. First and foremost, you need to contact your phone provider, so that they block your old SIM and issue a new one with your number.
  2. +
  3. Wait till you receive your new SIM with the old number, log in to Telegram, then go to Settings > Devices (or Privacy & Security > Active Sessions) and terminate your Telegram session on the old device.
  4. +
+
Removing sensitive data
+

Common thieves usually throw out the SIM card immediately (the phone is harder to locate this way), then wipe the devices and sell them, so there isn't much risk for the data in case of regular petty theft. But if you have reasons to worry about the data on the device and are unable to log out the other device, it is best that you wipe it remotely. You can read more about it here: Apple iOS, Android. Unfortunately, this requires you to have prepared in advance for this scenario.

+

You can delete your Telegram account if you are logged in on at least one of your other devices (mobile or desktop). Note that inactive Telegram accounts self-destruct automatically after a period of time — 6 months being the default setting.

+

Bots

+
+

If you're a developer, you may find our Bots FAQ more useful.

+
+

Q: What are bots?

+

Bots are like small programs that run right inside Telegram. They are made by third-party developers using the Telegram Bot API.

+

Q: How do I create a bot?

+

Creating Telegram bots is super-easy, but you will need at least some skills in computer programming. If you're sure you're up to it, our Introduction for Developers is a good place to start.

+

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

+

Q: A bot is sending me messages, how do I make it stop?

+

If you don't want a bot to send you messages, feel free to block it – same as you would block a human user. Some Telegram clients have a 'Stop Bot' button right in the bot's profile.

+

That said, most bot developers offer commands that silence the bot, check its /help for clues.

+

Q: Are bots safe?

+

Yes. Bots are no different from human users that you meet in groups for example. They can see your public name, username, and profile pictures, and they can see messages you send to them, that's it. They can't access your last seen status and don't see your phone number (unless you decide to give it to them yourself).

+

Naturally, any bot should be treated as a stranger — don't give them your passwords, Telegram codes or bank account numbers, even if they ask nicely. Also, be careful when opening files sent by bots, same as you would deal with ordinary humans. Example: If a bot sent us a file called OpenMe.exe, we probably wouldn't open it.

+

Q: If I add a bot to my group, can it read my messages?

+

Bots can work in two modes when you add them to groups. By default, bots only see messages that are meant for them. In this case, you'll see 'has no access to messages' in the group members list next to the bot.

+

Some bots need more information to work, so developers may disable the privacy mode. In this case, the bot will see all messages sent to the group, and you will see 'has access to messages' in the members list next to the bot.

+

Learn more about privacy mode for bots »

+

If your group contains very sensitive information, maybe it's better to avoid adding bots you don't trust 100%.

+

Q: Are bots made by Telegram?

+

No. While we have some official bots for specific purposes (like @gif or @GDPRbot), we don't usually make bots. Bots are made by third-party developers using the Telegram Bot API and platform.

+

Q: Where can I find more bots?

+

There is no official store at the moment, so you'll have to ask your friends or search the web for now. We're pretty sure you'll find some bots to play with.

+

Deeper questions

+

Q: Can I get Telegram's server-side code?

+

All Telegram client apps are fully open source. We offer verifiable builds both for iOS and Android – this technology allows to independently verify that the application you download from the app stores was built using the exact same code that we publish.

+

By contrast, publishing the server code doesn’t provide security guarantees neither for Secret Chats nor for Cloud Chats. This is because – unlike with the client-side code – there’s no way to verify that the same code is run on the servers.

+

As for Secret Chats, you don’t need the server-side code to check their integrity – the point of end-to-end encryption is that it must be solid regardless of how the servers function.

+
+

In a post on his channel, Pavel Durov explained why Telegram hasn't published the server code, even as a publicity stunt.

+
+

The encryption and API used on Telegram's servers are fully documented and open for review by security experts. We welcome any comments at security@telegram.org

+

Q: Can I run Telegram using my own server?

+

Our architecture does not support federation yet. Telegram is a unified cloud service, so creating forks where two users might end up on two different Telegram clouds is unacceptable. To enable you to run your own Telegram server while retaining both speed and security is a task in itself. At the moment, we are undecided on whether or not Telegram should go in this direction.

+

Q: Can I use the Telegram API?

+

Yes. Developers for all platforms are welcome to use our protocol, API and even source code. Check out the Getting started section of the docs.

+
+

Don't forget about our Bot API that lets you build cool stuff on our platform.

+
+

Q: Do you have a Privacy Policy?

+

Sure. Check this out.

+

Q: What does the iOS privacy sheet mean?

+

Apple created privacy sheets to inform users about what data apps may collect, but information there is vague and can be misleading. You can see a detailed explanation of Telegram's sheet here.

+

Q: Why do you have two apps in the Mac App Store?

+

One is our app for macOS, the other is Telegram Lite, the macOS version of our multi-platform client. Both apps are official. Both started out as unofficial applications by two different developers and vary in design and functionality.

+

Telegram for macOS supports many platform-specific features, such as the MacBook Pro Touch Bar, gesture navigation, integration with the Mac's Share menu and more. It has every feature from the iOS version of the app including Secret Chats.

+

Telegram Lite is a lightning-fast app, optimized for work-related tasks and handling large communities. It offers a three-column interface, perfect for multitasking and quick access to media, files and links shared in your chats. This app can also be used to export your Telegram data and chats.

+

Q: Can I translate Telegram?

+

Telegram is officially available in English, Spanish, German, Dutch, Italian, French, Arabic, Portuguese, Korean, Malay, Russian and Ukrainian on most platforms, and we are gradually expanding the list of languages built into the apps.

+

If you don’t like how a specific element in Telegram's interface is translated in your language, or would like to help us maintain the translation, check out our localization platform. Everyone can suggest translations and vote for the best ones, making Telegram localization a community-driven effort.

+

If you're looking to go beyond suggestions for individual phrases and would like to help us maintain the official translation to your language on a continuous basis, you can contact @TelegramAuditions. Please include a hashtag with the English name of your language (e.g. #Albanian) and a few links to phrases on this platform with your translation suggestions or comments. Be sure to read the Style Guide carefully before you apply.

+

Q: Can I help?

+

Yes, we are always looking for volunteers to help us with user support. If you would be interested in answering questions about Telegram to users from your country, contact our auditions account.

+

Before you apply, please check out the Telegram Support Initiative.

+

Passport

+

Telegram Passport is a unified authorization method for services that require personal identification. With Telegram Passport, you can upload your documents once, then instantly share your data with services that require real-world ID (finance, ICOs, etc.).

+

Your identity documents and personal data will be stored in the Telegram cloud using End-to-End Encryption. To Telegram, this data is just random gibberish, and we have no access to the information you store in your Telegram Passport. When you share data, it goes directly to the recipient.

+
+

You can find more information about Telegram Passport on our blog.

+
+

If you're a developer or owner of a service that requires real-life ID, kindly take a look at this manual. You can also try requesting Telegram Passport data using this page.

+
+

Troubleshooting

+

Login and SMS

+

Please make sure you are entering your mobile phone number in the international format.
I.e.: +(country code)(city or carrier code)(your number)

+

If you are having registration or login problems, please contact us using this form.

+

Getting a code via a phone call

+

For security reasons, login codes dictated via a phone call are only available for accounts that have two-step verification enabled (Settings > Privacy & Security > Two-Step Verification).

+

Please also note that Telegram accounts can only be connected to a mobile number. We currently don't support landline numbers.

+

Getting a code via Telegram

+

If you have recently used one of our apps on another device (it could also be a different app on the same device), we may send the login code via Telegram instead of SMS.

+

To receive such a code, just check Telegram from any of your connected devices. You will find it in the chat with Telegram, a verified profile with a blue check:

+
+ +

Login code sent via Telegram

+
+ +

WARNING! Please note that getting codes via Telegram should not be considered an alternative to using an up-to-date phone number. In case of a change in numbers, always make sure Telegram is connected to a phone number you control, otherwise you risk losing access to your account forever.

+

Notification problems

+
+

If the tips below don't help, check out this detailed guide on Troubleshooting Notification Issues.

+
+

ANDROID

+
    +
  1. Go to Telegram Settings — Notifications and Sounds, make sure that notifications are ON and Importance is set to “High” or greater.
  2. +
  3. Check whether contact or group is muted.
  4. +
  5. Make sure Google Play Services are installed on your phone.
  6. +
  7. Check notification priority for Telegram in Android settings, it can be called Importance or Behaviour depending on your device.
  8. +
  9. If your phone uses some battery saving software, make sure that Telegram is whitelisted in that application.
  10. +
+
+

NOTE: Huawei and Xiaomi devices have evil task killer services that interfere with the Telegram notification service. For our notifications to work, you need to add Telegram to allowed apps in those devices' security settings. Huawei: Phone Manager App > Protected Apps > Add Telegram to the list. Xiaomi: Services > Security > Permissions > Autostart, find Telegram and enable autostart.

+
+

iOS

+
    +
  1. Go to Telegram Settings — Notifications and Sounds, make sure that notifications are ON in Telegram.
  2. +
  3. Check that notifications are ON in phone Settings.
  4. +
  5. Check, whether contact or group is muted.
  6. +
  7. Shut down Telegram (go to home screen, double tap home button, swipe upwards on Telegram), then go to phone settings, set the alert style for Telegram to NONE. Relaunch Telegram, go to phone settings, set alert style back to banners.
  8. +
+

Problems with contacts

+

If you know your friends have Telegram, but you can't see them — or they appear as numbers instead of names.

+

Android:

+
    +
  1. Make sure you are using the latest version of the app.
  2. +
  3. Relaunch the app (by terminating it from processes list and launching again).
  4. +
  5. Temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
  6. +
  7. If that didn't help, re-login. Remember that logging out kills your Secret Chats.
  8. +
+

iOS:

+
    +
  1. Force quit the app (double tap home button, then swipe up on Telegram), then relaunch and check if it helped.
  2. +
  3. If that doesn't help, temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
  4. +
  5. If that doesn’t work, re-login: Settings > Edit > Log Out. Remember that logging out kills all your Secret Chats. Then log in again.
  6. +
+

Deleting contacts on Android

+

To delete a contact, open a chat with the person, tap the title in the top area of the chat screen to open their profile, then tap on (⋮) in the top right corner > 'Delete contact'.

+

If you want to delete the contact completely, make sure you also delete them from your phone contacts. Telegram stays in sync and will add the contact back if you don't.

+

Where did my Secret Chat messages go?

+

Secret Chats are established between the two devices they were created on. This means that all those messages are not available in the cloud and cannot be accessed on other devices.

+

Moreover, Secret Chats are also tied to your current login session on the device. If you log out and in again, you will lose all your Secret Chats.

+

Can't send messages to non-contacts

+

When users report unwanted messages from a Telegram account, we apply a limit: Reported accounts can only send messages to people who have their number saved as a contact.

+

This means that if you randomly contact people you don't know and send them annoying messages, you may lose the ability to do so in the future.

+

If you think that this limit was applied to your account wrongly, please visit this page.

+

Telegram uses the camera or microphone in the background!

+

Telegram can use the microphone in the background if you minimize the app when making a call, recording a video, or recording a voice/video message.

+

Permission monitors on Samsung and Xiaomi can inadvertently flag and notify you that Telegram requested access to camera in the background. This happens when the app requests info about the camera — it isn’t using the camera. Unfortunately it may look the same to the Samsung and Xiaomi permission monitors.

+

Camera info is requested by the app when you tap on the attachment button, or start recording a video or a video message. If you do this and quickly close the app, the already initiated request may try to run asynchronously when the app is already in the background, or be sent when the system wakes up the app to show a notification about a new message. In any case, these requests are only for the camera info, the app never uses the camera itself in the background.

+

Anyone can check Telegram’s open source code and confirm that the app is not doing anything behind their back. We also offer reproducible builds that can help you prove that the version you downloaded from App Store or Google Play is built from the exact same source code we publish.

+
+

Telegram Support

+

If you have any other questions, please contact Telegram Support (in Telegram go to Settings — Ask a question). Note that we rely on volunteers for support.

+

If you can't log in to your account, please use this form.

+
+

For media requests, please contact @PressBot on Telegram.

+
+

Twitter?

+

Yep. Follow us! @telegram
Our twitter account in Spanish: @telegram_es
In Italian: @telegram_it
In Korean: @Telegram_kr
In German: @de_telegram
For users from Brazil: @Telegram_br
Our Arabic-speaking users may find @telegram_arabic more interesting.

+

@SmsTelegram, login help on Twitter

+

We have a special account that can help you with login problems, @smstelegram. This account is official. Don't be afraid to DM it the number you use for Telegram, we need this info to investigate issues.

+

Be careful, we don't have any other support accounts on any social media platforms.

+

Facebook or other platforms?

+

If anyone on Facebook or any other platform is telling you they're us, they are not.

+

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/faq_channels.html b/data/telegram.org/faq_channels.html new file mode 100644 index 0000000000..9cd612a10c --- /dev/null +++ b/data/telegram.org/faq_channels.html @@ -0,0 +1,165 @@ + + + + + Channels FAQ + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Channels FAQ

+ +
+

This FAQ is about Telegram channels.
Back to the main FAQ »

+
+

+
+

Q: What's a channel?

+

Channels are a tool for broadcasting public messages to large audiences. In fact, channels can have an unlimited number of subscribers. When you post in a channel, the message is signed with the channel's name and not yours. You can appoint additional administrators to help you manage the channel. New subscribers can see the entire message history in a channel once they join.

+

If you'd like an example, join our official Telegram channel to get notified about our updates.

+

To create a channel:
iPhone: Start a new message (tap the icon in the top-right corner in Chats). Then ‘New Channel’.
Android: Tap the circular pencil icon in the chat list. Then ‘New Channel’.
Windows Phone: Tap the ‘+’ button on the bottom bar. Then ‘New Channel’.

+

Q: How are public and private channels different?

+

Public channels have a username. Anyone can find them in Telegram search and join. Private channels are closed societies – you need to be added by the owner or get an invite link to join.

+

Please note that private channels with publicly available invite links will be treated in the same way as public channels, should it come to content disputes.

+

Q: What can administrators do?

+

The owner of a channel can broadcast messages, delete any messages, add subscribers (the first 200 only), remove subscribers, change the channel's name, profile image and link, as well as delete the channel completely. The owner can also add and remove administators to help manage the channel.

+

You can set up administrator rights for each individual administrator when you appoint them.

+

Q: What happens if I delete a message?

+

If a message is deleted in a channel, it will disappear for all subscribers.

+

Q: How do I add people to my channel?

+

As the channel's owner, you may invite the first 200 subscribers to your channel. Once the subscriber count reaches 200, the channel is on its own. If it's a public channel, it will have a username and a telegram.me/ link (e.g. t.me/telegram) – you can post this link on social networks, advertise it in magazines, or tattoo it on your back. If you have a private channel, you can send an invite link to your friends.

+

Please do not send channel links (or other unsolicited messages) to strangers. If they report spam from your account, you may be banned from contacting other people, however good your intentions.

+

Q: What does the eye icon mean?

+

Each post in a channel has a view counter. Views from forwarded copies of your messages are also included in the total count. This way you can see how far it has spread.

+

Please note that these numbers are approximate — we don't want to keep a record for everything you've ever viewed. After a short while (around 4 days), Telegram will forget that you've seen a post and will count you again if you navigate to it. For this reason you may see several views for posts in a private channel where you are alone.

+

Q: How do I know who posted a message?

+

As the owner of the channel, you can enable admin signatures that users will see next to the view counters. These signature only mention the name of the administrator and no link to their profile.

+

If the signatures are disabled, there is no way for users to know whether a message was posted by the owner or one of the administrators.

+

Q: Are there any feedback options?

+

You can add a discussion group chat to the channel, and your subscribers will see a comment button for each post in the channel. Comments show up in a thread of their own and also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

+

You can also use bots (e.g. the @like bot) to add buttons to your posts.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/faq_spam.html b/data/telegram.org/faq_spam.html new file mode 100644 index 0000000000..a7ff571d34 --- /dev/null +++ b/data/telegram.org/faq_spam.html @@ -0,0 +1,163 @@ + + + + + Spam FAQ + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Spam FAQ

+ +
+

This FAQ is for people whose accounts were limited after being reported for spam.
Back to the main FAQ »

+
+

+
+

Q: What happened to my account?

+

When users press the ‘Report spam’ button in a chat, they forward these messages to our team of moderators for review. If the moderators decide that the messages deserved this, the account becomes limited temporarily.

+

This means that if you have been sending unwanted messages to random strangers or posting spam in groups, you lose the ability to do so.

+

Q: So I can't send messages anymore?

+

No, it's not that bad. Limited accounts can send messages to people who have their number saved as a contact. You can also always reply to anyone who messages you first.

+

Q: Why was I reported?

+

Telegram‘s username search is not a tool for making new friends. People usually don’t like it when strangers contact them — so they will report you if they find your messages annoying. Please only contact people if you're sure that they are expecting messages from you. The same applies to adding people to unwanted groups and channels. In addition to this, group admins can also report users who post spam in their groups.

+

Naturally, all such reports are also checked by human moderators. If the messages contain spam, the account will be temporarily limited.

+

Q: What can people report me for?

+

For private messages, it really doesn‘t matter what you send, as long as the receivers find it unwelcome. It could have been a photo, an invite link or a simple ’hello‘. Please only send messages when you are sure people won’t mind getting them.

+

As a general rule, people do mind getting unsolicited advertisements, links, invite links to groups or channels, random photos and, above all, anything related to commerce or online popularity. If you send them something like this, you will be blocked — and everybody else will be happy.

+

Moderators are more lenient when it comes to messages in groups, but anyone who sends spam or unsolicited advertisments will be limited.

+

Q: What do I do now?

+

If this happened to you for the first time (and you are not an industrial scale spammer), most likely your account will be limited for a few days or so. Please wait and consider that people want a peaceful time using our messenger.

+

Repeated offences will result in longer periods of being blocked. If you keep writing unwanted messages to strangers, you may lose the ability to do so forever.

+

Q: I read all of the above, and I‘m certain that I didn’t break any rules!

+

If you are sure that the limit was wrongfully applied to your account, please contact our @SpamBot.

+

Please forgive us for the inconvenience — even the best systems, algorithms and well-trained people can make mistakes sometimes.

+

Q: I know I was wrong, please release me sooner!

+

We're sorry, but this is impossible. We value the inner peace of Telegram users too much.

+

Q: I‘ve just signed up and didn’t send any messages yet, but my account is limited.

+

Some numbers may trigger an overly harsh response from our system, either due to their previous owners‘ activities or due to them being certain virtual/VOIP numbers. We’re sorry if this resulted in your account being limited for no reason.

+

If you think this is your case, please contact @SpamBot and tell it your story.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/jobs.html b/data/telegram.org/jobs.html new file mode 100644 index 0000000000..de3b038c35 --- /dev/null +++ b/data/telegram.org/jobs.html @@ -0,0 +1,156 @@ + + + + + Jobs + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Jobs

+ +

Telegram stands for freedom and perfection. It is built by a tiny team of world-renowned developers selected in multi-level contests. If you want to join the Telegram team, check out the options below.

+
+

Check out the Telegram Contests channel and our @jobs_bot for ongoing competitions and the latest news.

+
+

Content Moderator

+

Responsibilities: use a specialized interface to manually sort content according to provided guidelines.

+

Preferred qualifications: fluency in English, strong analytical skills, quick reaction, attention to detail.

+

How to apply: contact @jobs_bot and fill in the required info. If your application is accepted, the bot will share a series of test tasks.

+
+

Please submit your applications for the Content Moderator position by Monday, May 10 at 23:59 Dubai time. Applications received after that point will not be considered in this round – and will have to wait for future vacancies.

+
+

Translator

+

Responsibilities: translate app and website interfaces, blog posts, changelogs, and other text with a high level of precision on ambitious deadlines.

+

Preferred qualifications: fluency in English and a native-level fluency in another language, excellent written communication skills with a focus on detail.

+

How to apply: contact @jobs_bot and fill in the required info. If your application is accepted, the bot will share a series of test tasks.

+
+

Please submit your applications for the Translator position by Friday, May 14 at 23:59 Dubai time. Applications received after that point will likely not be considered in this round – and may have to wait for future vacancies.

+
+

C/C++ Software Engineer

+

Responsibilities: work on Telegram's custom-built low-level data storage engines distributed across several data-centers.

+

Preferred qualifications: experience working on scalable C/C++ projects and/or networking protocols, experience working with Linux, top results in programming contests.

+

How to apply: contact @jobs_bot and fill in the required info. The bot will also notify you whenever we're holding relevant coding competitions – which are the fastest and easiest way of joining the team.

+

Site Reliability Engineer

+

Responsibilities: automate routine tasks, proactively identify and solve potential reliability issues, increase fault-tolerance of Telegram's multi-datacenter infrastructure.

+

Preferred qualifications: experience administering *nix like systems, experience developing in C, Python or Perl; knowledge of bash, network protocols, and network equipment of major manufacturers.

+

How to apply: contact @jobs_bot and fill in the required info.

+

Junior Accountant

+

Responsibilities: maintain accounting books and records, ensure documentation of financial transactions, manage payrolls, prepare financial statements and reports (balance sheet, profit and loss statement, cash flow and analytics).

+

Preferred qualifications: high GMAT score, native-level fluency in English, appreciation and working knowledge of accounting principles under IFRS, experience with QuickBooks or Xero software, strong computer literacy with proficient use of Microsoft Excel.

+

How to apply: contact @jobs_bot and fill in the required info.

+

Assistant to the CEO

+

Responsibilities: manage and maintain calendar of the CEO, booking and arranging travel, transport and accommodation.

+

Preferred qualifications: high IQ score, native-level fluency in English, excellent verbal and written communications skills, accuracy and attention to detail, basic financial skills, discretion, persistence.

+

How to apply: contact @jobs_bot and fill in the required info.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/press.html b/data/telegram.org/press.html new file mode 100644 index 0000000000..207c71f716 --- /dev/null +++ b/data/telegram.org/press.html @@ -0,0 +1,194 @@ + + + + + Articles about Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+ +
+ +
+

Articles about Telegram

+ +
+

These articles cover Telegram and its sponsor, global entrepreneur Pavel Durov.
For media requests, please contact @PressBot on Telegram.

+
+

English

+ +

Español

+ +

Italiano

+ +
+

Press contacts

+

If you would like to contact us, please contact @PressBot on Telegram.

+

Telegram logos

+

If you need Telegram logos, take these. Feel free to use them for article illustrations, graphs, “forward to Telegram” buttons, etc. Just make sure people understand you're not representing Telegram officially.

+

You can find some high-quality public-domain screenshots of Telegram on this page.

+

Telegram Widgets

+

If you would like to add Telegram share buttons, comments or other widgets to your website, please see this page.

+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/privacy.html b/data/telegram.org/privacy.html new file mode 100644 index 0000000000..363908ba0d --- /dev/null +++ b/data/telegram.org/privacy.html @@ -0,0 +1,299 @@ + + + + + Telegram Privacy Policy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Telegram Privacy Policy

+ +
+ +

+

1. Introduction

+

This Privacy Policy sets out how we, Telegram Messenger Inc. (“Telegram”), use and protect your personal data that you provide to us, or that is otherwise obtained or generated by us, in connection with your use of our cloud-based messaging services (the “Services”). For the purposes of this Privacy Policy, ‘we’, ‘us’ and ‘our’ refers to Telegram, and ‘you’ refers to you, the user of the Services.

+

1.1 Privacy Principles

+

Telegram has two fundamental principles when it comes to collecting and processing private data:

+
    +
  • We don't use your data to show you ads.
  • +
  • We only store the data that Telegram needs to function as a secure and feature-rich messaging service.
  • +
+

1.2. Terms of Service

+

This Privacy Policy forms part of our Terms of Service, which describes the terms under which you use our Services and which are available at https://telegram.org/tos. This Privacy Policy should therefore be read in conjunction with those terms.

+

1.3. Table of Contents

+

This Privacy Policy explains the following:

+ +

1.4. EEA Representative

+

If you live in a country in the European Economic Area (EEA), the Services are provided by Telegram, which for the purposes of applicable data protection legislation is the data controller responsible for your personal data when you use our Services. However, as Telegram is located outside the EEA, we have designated one of our EEA-based group companies, Telegram UK Holdings Ltd (71-75 Shelton Street, Covent Garden, London, England, WC2H 9JQ), as a representative to whom you may direct any issues you have relating to our processing of your personal data.

+

2. Legal Ground for Processing Your Personal Data

+

We process your personal data on the ground that such processing is necessary to further our legitimate interests (including: (1) providing effective and innovative Services to our users; and (2) to detect, prevent or otherwise address fraud or security issues in respect of our provision of Services), unless those interests are overridden by your interest or fundamental rights and freedoms that require protections of personal data.

+

3. What Personal Data We Use

+

3.1. Basic Account Data

+

Telegram is a communication service. You provide your mobile number and basic account data (which may include profile name, profile picture and about information) to create a Telegram account.

+

To make it easier for your contacts and other people to reach you and recognize who you are, the screen name you choose, your profile pictures, and your username (should you choose to set one) on Telegram are always public. We don't want to know your real name, gender, age or what you like.

+

We do not require your screen name to be your real name. Note that users who have you in their contacts will see you by the name they saved and not by your screen name. This way your mother can have the public name 'Johnny Depp' while appearing as 'Mom' to you and as 'Boss' to her underlings at work (or the other way around, depending on how these relationships are structured).

+

3.2. Your E-mail Address

+

When you enable 2-step-verification for your account or store documents using the Telegram Passport feature, you can opt to set up a password recovery email. This address will only be used to send you a password recovery code if you forget it. That's right: no marketing or “we miss you” bullshit.

+

3.3. Your Messages

+
3.3.1. Cloud Chats
+

Telegram is a cloud service. We store messages, photos, videos and documents from your cloud chats on our servers so that you can access your data from any of your devices anytime without having to rely on third-party backups. All data is stored heavily encrypted and the encryption keys in each case are stored in several other data centers in different jurisdictions. This way local engineers or physical intruders cannot get access to user data.

+
3.3.2. Secret Chats
+

Secret chats use end-to-end encryption. This means that all data is encrypted with a key that only you and the recipient know. There is no way for us or anybody else without direct access to your device to learn what content is being sent in those messages. We do not store your secret chats on our servers. We also do not keep any logs for messages in secret chats, so after a short period of time we no longer know who or when you messaged via secret chats. For the same reasons secret chats are not available in the cloud — you can only access those messages from the device they were sent to or from.

+
3.3.3. Media in Secret Chats
+

When you send photos, videos or files via secret chats, before being uploaded, each item is encrypted with a separate key, not known to the server. This key and the file’s location are then encrypted again, this time with the secret chat’s key — and sent to your recipient. They can then download and decipher the file. This means that the file is technically on one of Telegram’s servers, but it looks like a piece of random indecipherable garbage to everyone except for you and the recipient. We don’t know what this random data stands for and we have no idea which particular chat it belongs to. We periodically purge this random data from our servers to save disk space.

+
3.3.4. Public Chats
+

In addition to private messages, Telegram also supports public channels and public groups. All public chats are cloud chats (see section 3.3.1 above). Like everything on Telegram, the data you post in public communities is encrypted, both in storage and in transit — but everything you post in public will be accessible to everyone.

+
3.4. Phone Number and Contacts
+

Telegram uses phone numbers as unique identifiers so that it is easy for you to switch from SMS and other messaging apps and retain your social graph. We ask your permission before syncing your contacts.

+

We store your up-to-date contacts in order to notify you as soon as one of your contacts signs up for Telegram and to properly display names in notifications. We only need the number and name (first and last) for this to work and store no other data about your contacts.

+

Our automatic algorithms can also use anonymized sets of phone numbers to calculate the approximate number of potential contacts an unregistered phone number may have on Telegram. When you open the 'Invite friends' interface, we display the resulting statistics next to your contacts to give you an idea of who could benefit most from joining Telegram.

+

You can always stop syncing contacts or delete them from our servers in Settings > Privacy & Security > Data Settings.

+
+

If you are using Android, Telegram will ask you for permission to access your phone call logs (READ_CALL_LOG). If you grant this permission, Telegram will be able verify your account by transmitting a phone call instead of asking you to enter a code. Telegram uses this permission only to confirm receipt of the confirmation call by verifying the number in the call log.

+
+

3.5. Location Data

+

If you share a location in a chat, this location data is treated like other messages in cloud or secret chats respectively.

+

If you share your Live Location in any chat or turn on ’Make Myself Visible’ in People Nearby, Telegram will use your data to display your location to those users with whom you are sharing it, even when the app is closed – for as long as you keep these optional features activated.

+
3.6. Cookies
+

The only cookies we use are those to operate and provide our Services on the web. We do not use cookies for profiling or advertising. The cookies we use are small text files that allow us to provide and customize our Services, and in doing so provide you with an enhanced user experience. Your browser should allow you to control these cookies, including whether or not to accept them and how to remove them. You may choose to block cookies with your web browser, however, if you do disable these cookies you will not be able to log in to Telegram Web.

+

4. Keeping Your Personal Data Safe

+

4.1. Storing Data

+

If you signed up for Telegram from the UK or the EEA, your data is stored in data centers in the Netherlands. These are third-party provided data centers in which Telegram rents a designated space. However, the servers and networks that sit inside these data centers and on which your personal data is stored are owned by Telegram. As such, we do not share your personal data with such data centers. All data is stored heavily encrypted so that local Telegram engineers or physical intruders cannot get access.

+

4.2. End-to-End Encrypted Data

+

Your messages, media and files from secret chats (see section 3.3.2 above), as well as the contents of your calls and the data you store in your Telegram Passport are processed only on your device and on the device of your recipient. Before this data reaches our servers, it is encrypted with a key known only to you and the recipient. While Telegram servers will handle this end-to-end encrypted data to deliver it to the recipient – or store it in the case of Telegram Passport data, we have no ways of deciphering the actual information. In this case, we neither store nor process your personal data, rather we store and process random sequences of symbols that have no meaning without the keys which we don’t have.

+

4.3. Retention

+

Unless stated otherwise in this Privacy Policy, the personal data that you provide us will only be stored for as long as it is necessary for us to fulfill our obligations in respect of the provision of the Services.

+

5. Processing Your Personal Data

+

5.1. Our Services

+

Telegram is a cloud service. We will process your data to deliver your cloud chat history, including messages, media and files, to any devices of your choosing without a need for you to use third-party backups or cloud storage.

+

5.2. Safety and Security

+

Telegram supports massive communities which we have to police against abuse and Terms of Service violations. Telegram also has more than 400 million users which makes it a lucrative target for spammers. To improve the security of your account, as well as to prevent spam, abuse, and other violations of our Terms of Service, we may collect metadata such as your IP address, devices and Telegram apps you've used, history of username changes, etc. If collected, this metadata can be kept for 12 months maximum.

+

5.3. Spam and Abuse

+

To prevent phishing, spam and other kinds of abuse and violations of Telegram’s Terms of Service, our moderators may check messages that were reported to them by their recipients. If a spam report on a message you sent is confirmed by our moderators, your account may be limited from contacting strangers – temporarily or permanently. You can send an appeal using @Spambot. In case of more serious violations, your account may be banned. We may also use automated algorithms to analyze messages in cloud chats to stop spam and phishing.

+

5.4. Cross-Device Functionality

+

We may also store some aggregated metadata to create Telegram features (see section 5.5 below) that work across all your devices.

+

5.5. Advanced features

+

We may use some aggregated data about how you use Telegram to build useful features. For example, when you open the Search menu, Telegram displays the people you are more likely to message in a box at the top of the screen. To do this, we calculate a rating that shows which people you message frequently. A similar rating is calculated for inline bots so that the app can suggest the bots you are most likely to use in the attachment menu (or when you start a new message with “@”). To turn this feature off and delete the relevant data, go to Settings > Privacy & Security > Data Settings and disable “Suggest Frequent Contacts”.

+

5.6. No Ads Based on User Data

+

Unlike other services, we don't use your data for ad targeting or other commercial purposes. Telegram only stores the information it needs to function as a secure and feature-rich cloud service.

+

Telegram offers a tool for advertisers to promote their messages in public one-to-many channels, but these sponsored messages are based solely on the topic of the public channels in which they are shown. No user data is mined or analyzed to display ads or sponsored messages.

+

6. Bot Messages

+

6.1. Ecosystem

+

Telegram has an API that allows third-party developers to create bots. Bots are apps that look like special Telegram users: you can talk to them from your chat list, add them to groups or use a special “inline” interface to access their features. By performing any of these actions, you will be sending some of your data to the respective third-party bot developers.

+

6.2. How Bots Can Receive Data

+

You can send data to bot developers when you interact with their bots in one of these ways:

+
    +
  • By sending messages to a bot.
  • +
  • By using an inline bot.
  • +
  • By participating in a group with a bot.
  • +
  • By pressing buttons in messages sent by a bot.
  • +
  • By paying for goods and services via bots (see section 7 below).
  • +
+

6.3. What Data Bots Receive

+

In any of the above cases, the developers of an automated user (bot) can get your public account data (see section 3.1 above): your screen name, username and profile picture(s).

+

Bots can also receive the following data when you interact with them.

+
    +
  • Bots will obviously get your messages when you send them something.
  • +
  • If you click on links or buttons provided by the bot, the bot can potentially get your IP address (provided that it controls the website to which the link leads).
  • +
  • If the bot is a member of the same group with you, it may know you are a member.
  • +
  • When you start your message with the username of an inline bot (e.g. @gif) the interface transforms so that everything you type becomes a query to that bot. This query is sent to the bot so that it can provide its service. We will warn you about this the first time you use an inline bot.
  • +
  • Bots added to groups can operate in two modes: with access to messages in the group or without access. If the bot has access to messages, it can see everything that happens in the group. The interface clearly shows whether or not a bot has access to messages in groups.
  • +
+

6.4. Bots Are Not Maintained by Telegram

+

Other than our own bots, no other bots or third-party bot developers are affiliated with Telegram. They are completely independent from us. They should ask you for your permission before they access your data or you make it available to them.

+ + +

7. Third Party Payment Services

+

7.1. Payment Information

+

The Payment Platform for Bots is available to users as of Telegram 4.0. Telegram does not process payments from users and instead relies on different payment providers around the world. It is the payment providers that handle and store your credit card details. Neither Telegram nor the merchants on the platform (bot developers) have access to this information. Although we work with payment providers they are completely independent from Telegram. Please study their relevant privacy policies before making your data available to them.

+

7.2. Credit Card Information

+

When making a purchase, you enter your credit card details into a form supplied by the payment provider that will be processing the payment, and this information goes directly to the payment provider's server. Your credit card information never reaches Telegram's servers. We do not access and do not store your credit card information. When you save your credit card info, it is saved on the respective payment provider's servers and the payment provider gives Telegram a token that you can reuse for future payments. It is not possible to reconstruct your credit card info from the token.

+

7.3 Shipping Information

+

When you enter shipping information in the process of placing an order, we send it directly to the merchant bot developer. We can store your shipping information for you if you choose to save it for future purchases. We will delete this information immediately if you ask us to.

+

7.4. Clearing Payment Information

+

You can clear all payment information associated with your account at any time by going to Telegram Settings > Privacy & Security > Data Settings and selecting ‘Clear Payment & Shipping Info’. If you choose to remove your payment information, we will delete your stored shipping info and payment tokens from all providers and ask the payment providers to remove your credit card information that they store.

+

7.5. Payment Disputes

+

Due to the fact that Telegram doesn't store any credit card details or transaction information, it is impossible for us to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.

+

8. Who Your Personal Data May Be Shared With

+

8.1. Other Telegram Users

+

Other users of our Services with whom you choose to communicate with and share certain information, who may be located outside the EEA. Note that by entering into the Terms of Service and choosing to communicate with such other users of Telegram, you are instructing us to transfer your personal data, on your behalf, to those users in accordance with this Privacy Policy. We employ all appropriate technical and organizational measures (including encryption of your personal data) to ensure a level of security for your personal data that is appropriate to the risk.

+

8.2. Telegram’s Group Companies

+

We may share your personal data with: (1) our parent company, Telegram Group Inc, located in the British Virgin Islands; and (2) Telegram FZ-LLC, a group member located in Dubai, to help provide, improve and support our Services. We will implement appropriate safeguards to protect the security and integrity of that personal data. This will take the form of standard contract clauses approved by the European Commission in an agreement between us and our relevant group companies. If you would like more information regarding these clauses, please contact us using the details in section 12 below.

+

8.3. Law Enforcement Authorities

+

If Telegram receives a court order that confirms you're a terror suspect, we may disclose your IP address and phone number to the relevant authorities. So far, this has never happened. When it does, we will include it in a semiannual transparency report published at: https://t.me/transparency.

+

9. Your Rights Regarding the Personal Data You Provide to Us

+

9.1. Your Rights

+

Under applicable data protection legislation, in certain circumstances, you have rights concerning your personal data. You have a right to: (1) request a copy of all your personal data that we store and to transmit that copy to another data controller; (2) delete (see section 10 below) or amend your personal data; (3) restrict, or object to, the processing of your personal data; (4) correct any inaccurate or incomplete personal data we hold on you; and (5) lodge a complaint with national data protection authorities regarding our processing of your personal data.

+

9.2. Exercising Your Rights

+

If you wish to exercise any of these rights, kindly contact us using the details in section 12 below.

+

9.3. Data Settings

+

You can control how your data is used (e.g., delete synced contacts) in Settings > Privacy & Security > Data Settings (using one of our mobile apps).

+

Sadly, if you're not OK with Telegram's modest minimum requirements, it won't be possible for us to provide you with our Services. You can delete your Telegram account by proceeding to the deactivation page.

+

10. Deleting data

+

10.1. Accounts

+

If you would like to delete your account, you can do this on the deactivation page. Deleting your account removes all messages, media, contacts and every other piece of data you store in the Telegram cloud. This action must be confirmed via your Telegram account and cannot be undone.

+

10.2. Messages

+
    +
  • In secret chats, deleting a message always instructs the app on the other end to delete it too.
  • +
  • In cloud chats, you can choose to delete a message for all participants within at least 48 hours after sending. Otherwise, deleting a message will delete it from your message history. This means that a copy will stay on the server as part of your partner's message history. As soon as your partner deletes it too, it's gone forever.
  • +
  • As of version 5.5, any party can choose to delete any messages in one-on-one chats, both sent and received, for both sides. There is no time limit. Any party can also opt to clear the entire chat history for both parties, in which case the apps will be instructed to remove all messages in that chat, however many of them are still retained by either of the participants.
  • +
  • In supergroups and channels, deleting a message removes it for all participants. Note that deleted messages and original versions of edited messages from supergroups are stored for 48 hours after deletion in order to be shown in the admins log.
  • +
+

10.3. Self-Destructing Messages

+

Messages in Secret Chats can be ordered to self-destruct. As soon as such a message is read (2 checks appear), the countdown starts. When the timer expires, both devices participating in a secret chat are instructed to delete the message (photo, video, etc.). Media with short timers (less than a minute) are shown with blurred previews. The timer is triggered when they are viewed.

+

10.4. Account Self-Destruction

+

By default, if you stop using Telegram and do not come online for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can go to Settings to change the exact period after which your inactive account will self-destruct.

+

11. Changes to this Privacy Policy

+

We will review and may update this Privacy Policy from time to time. Any changes to this Privacy Policy will become effective when we post the revised Privacy Policy on this page www.telegram.org/privacy. Please check our website frequently to see any updates or changes to our Privacy Policy, a summary of which we will set out below.

+

March 25, 2019

+
    +
  • Expanded [10.2. Deleting Messages] with data on the new features in version 5.5, which allow both participants to remove any messages from one-on-one chats for both sides without a time limit.
  • +
+

March 24, 2021

+ +

October 26, 2021

+ +

Important changes made to this Privacy Policy will be notified to you via Telegram.

+

12. Questions and concerns

+

If you have any questions about privacy and our data policies, please contact our @GDPRbot. Use the /access command to learn how to get a copy of your Telegram data and use the /contact command to leave a request, which we will answer at the earliest opportunity.

+

Telegram is an open source project. You can examine more information on our:

+ +
+

This policy has been expanded on August 14, 2018 to add information required by the EU data protection law.

+
+ +
+ +
+
+
+ + + + + + + + + diff --git a/data/telegram.org/privacy/gmailbot.html b/data/telegram.org/privacy/gmailbot.html new file mode 100644 index 0000000000..e7fec71326 --- /dev/null +++ b/data/telegram.org/privacy/gmailbot.html @@ -0,0 +1,161 @@ + + + + + Telegram GmailBot Privacy Policy + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Telegram GmailBot Privacy Policy

+ +
+ +

1. Introduction

+

This Privacy Policy sets out how we, Telegram Messenger Inc. (“Telegram”), use and protect your personal data that you provide to us, or that is otherwise obtained or generated by us, in connection with your use of our @GmailBot Bot (the Bot). For the purposes of this Privacy Policy, ‘we’, ‘us’ and ‘our’ refers to Telegram, and ‘you’ refers to you, the user of the Services.

+

The Bot is a part of the Telegram Bot Ecosystem. For more information on Telegram messaging services please refer to Telegram Privacy Policy.

+

The Bot's use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

+

Gmail and the Gmail logo are registered trademarks of Google LLC.

+

1.1 Privacy Principles

+

Telegram has two fundamental principles when it comes to collecting and processing private data:

+
    +
  • We don't use your data to show you ads.
  • +
  • We only store the data that Telegram needs to function as a secure and feature-rich messaging service.
  • +
+

1.2. EEA Representative

+

If you live in a country in the European Economic Area (EEA), the Services are provided by Telegram, which for the purposes of applicable data protection legislation is the data controller responsible for your personal data when you use our Services. However, as Telegram is located outside the EEA, we have designated one of our EEA-based group companies, Telegram UK Holdings Ltd (71-75 Shelton Street, Covent Garden, London, England, WC2H 9JQ), as a representative to whom you may direct any issues you have relating to our processing of your personal data.

+

2. Legal Ground for Processing Your Personal Data

+

We process your personal data on the ground that such processing is necessary to further our legitimate interests (including: (1) providing effective and innovative Services to our users; and (2) to detect, prevent or otherwise address fraud or security issues in respect of our provision of Services), unless those interests are overridden by your interest or fundamental rights and freedoms that require protections of personal data.

+

3. What Personal Data We Use

+

3.1. Basic Telegram Data

+

The Bot is available only via the Telegram communication service. Please refer to Telegram Privacy Policy regarding basic Telegram account data.

+

3.2. Gmail Data

+

The Bot requests your permission to access your Gmail Data via OAuth. After you accept the request, we use the Google API to receive your new emails and notify you about them in Telegram. You can reply to those emails, forward, archive and delete them as well as create and send new emails, right from Telegram. In order to provide these features, we store your Gmail API token, your notification preferences and your Gmail screen name. We also store the cache of your incoming messages for the previous 7 days for you to be able to reply to these messages via Telegram; all such cached data older than one week is cleared automatically.

+

4. Keeping Your Personal Data Safe

+

4.1. Storing Data

+

The data related to the Bot is stored separately from the main Telegram Data, in data centers in Germany. These are third-party provided data centers in which Telegram rents a designated space. We do not share your personal data with such data centers.

+

4.2. Retention

+

Unless stated otherwise in this Privacy Policy, the personal data that you provide us will only be stored for as long as it is necessary for us to fulfill our obligations in respect of the provision of the Services.

+

5. Who Your Personal Data May Be Shared With

+

5.1. Telegram’s Group Companies

+

We may share your personal data with: (1) our parent company, Telegram Group Inc, located in the British Virgin Islands; and (2) Telegram FZ-LLC, a group member located in Dubai, to help provide, improve and support our Services. We will implement appropriate safeguards to protect the security and integrity of that personal data. This will take the form of standard contract clauses approved by the European Commission in an agreement between us and our relevant group companies.

+

6. Deleting data

+

If you no longer want to use the Bot, send the /resetbot command to the Bot. You will stop receiving notifications and we will revoke our permission to access your Gmail Data. You can also revoke our permissions to your Gmail account manually here: https://myaccount.google.com/permissions. After the permission is revoked, we will remove all your Gmail data from our servers within 30 days.

+

7. Changes to this Privacy Policy

+

We will review and may update this Privacy Policy from time to time. Any changes to this Privacy Policy will become effective when we post the revised Privacy Policy on this page www.telegram.org/privacy/gmailbot. Please check our website frequently to see any updates or changes to our Privacy Policy, a summary of which we will set out below.

+

Important changes made to this Privacy Policy will be notified to you via Telegram.

+
+ +
+ +
+
+
+ + + + + + + + + diff --git a/data/telegram.org/support.html b/data/telegram.org/support.html new file mode 100644 index 0000000000..6c587013fd --- /dev/null +++ b/data/telegram.org/support.html @@ -0,0 +1,141 @@ + + + + + Telegram support + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Support

+ +
+
+ + +
+
+ + +
+
+ + +
+
+ +
+
+ +
+
+
+
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/teststore.html b/data/telegram.org/teststore.html new file mode 100644 index 0000000000..710beff8d0 --- /dev/null +++ b/data/telegram.org/teststore.html @@ -0,0 +1,283 @@ + + + + + Telegram Messenger + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ + + + + + +
+ +

Why Telegram?

+ +
+
+
+
+

Simple

+
Telegram is so simple you already know how to use it.
+
+
+ +
+
+
+

Private

+
Telegram messages are heavily encrypted and can self-destruct.
+
+
+ +
+
+
+

Synced

+
Telegram lets you access your chats from multiple devices.
+
+
+ +
+
+
+

Fast

+
Telegram delivers messages faster than any other application.
+
+
+ +
+
+
+

Powerful

+
Telegram has no limits on the size of your media and chats.
+
+
+ +
+
+
+

Open

+
Telegram has an open API and source code free for everyone.
+
+
+ +
+
+
+

Secure

+
Telegram keeps your messages safe from hacker attacks.
+
+
+ +
+
+
+

Social

+
Telegram groups can hold up to 200,000 members.
+
+
+ +
+
+
+

Expressive

+
Telegram lets you completely customize your messenger.
+
+
+
+
+ +
+ +
+
+
+ + + + + + + + diff --git a/data/telegram.org/tos.html b/data/telegram.org/tos.html new file mode 100644 index 0000000000..d7b9244bfd --- /dev/null +++ b/data/telegram.org/tos.html @@ -0,0 +1,133 @@ + + + + + Terms of Service + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+

Terms of Service

+ +

By signing up for Telegram, you accept our Privacy Policy and agree not to:

+
    +
  • Use our service to send spam or scam users.
  • +
  • Promote violence on publicly viewable Telegram channels, bots, etc.
  • +
  • Post illegal pornographic content on publicly viewable Telegram channels, bots, etc.
  • +
+

We reserve the right to update these Terms of Service later.

+
+

Citizens of EU countries and the United Kingdom must be at least 16 years old to sign up.

+
+
+ +
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/tour.html b/data/telegram.org/tour.html new file mode 100644 index 0000000000..1b9a1c6de3 --- /dev/null +++ b/data/telegram.org/tour.html @@ -0,0 +1,144 @@ + + + + + Telegram Tour + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + diff --git a/data/telegram.org/tour/channels.html b/data/telegram.org/tour/channels.html new file mode 100644 index 0000000000..a03cc25dcd --- /dev/null +++ b/data/telegram.org/tour/channels.html @@ -0,0 +1,294 @@ + + + + + Telegram Channels + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Channels

+ +
+ +
+ +

Channels are a tool for broadcasting your public messages to large audiences. They offer a unique opportunity to reach people directly, sending a notification to their phones with each post.

+

Telegram Channels can have an unlimited amount of subscribers, and only admins have the right to post. Unlike Telegram Groups, channels show the name and photo of the channel next to messages – instead of the person who posted them.

+
+ +
+ +

Media organizations and public figures use channels to stay in touch with their readers, voters and fans. For some real-life examples, check out @Bloomberg, the Coronavirus Info channel, or join the official @Telegram channel covering our updates.

+

To create your own channel, open the “New Message” menu on Telegram and choose “New Channel”. Newly created channels start as private – but you can edit their profile to make them public.

+

The contents of public channels can be seen on the Web without a Telegram account and are indexed by search engines. For example, try t.me/s/FinancialTimes.

+

Autoplaying Videos and Rich Media

+

Channels aren't just for text messages and links – Telegram supports a wide range of content types, from autoplaying videos to animated stickers, polls and beyond.

+

Videos will start playing automatically with no sound. Pressing the volume buttons on the device unmutes the video, tapping on it launches the video from the beginning in full screen mode.

+
+ TITLE +
+ +

Several photos sent together will form an album with a beautiful layout – and only result in one notification to your subscribers for the whole batch.

+
+ TITLE +
+ +

You can send large files of any type and uncompressed images in full resolution – useful for content like infographics.

+
+ TITLE +
+ +

Podcasts also get special treatment. Telegram apps remember your last position when resuming playback of long audio files. Users who are in a hurry can listen to them at 2x speed:

+
+ Screenshot showing the location of the 2x playback button for long audio files. +
+ + +

Quick Sharing

+

Each post in a channel has a handy Share Button next to it, making it easy for your subscribers to forward things to others – or save them in their Saved Messages.

+
+ TITLE +
+ +

The Quick Share menu also shows a direct link to your post. Following such links inside Telegram opens the channel and highlights the message. If the user doesn't have Telegram, they will see a web page with an embedded post, like this: t.me/corona/16.

+

Powerful Polls

+

You can use polls to judge public opinion, make decisions and help your audience connect with you.

+
+ A poll that shows who voted for which option +
+ +

Quiz-Style Polls

+

To make things more fun – or add extra educational value to your posts 🧐 – use quiz-style polls that have one correct answer.

+
+ TITLE +
+ +

Discussion Groups

+

If you'd like to know what people think about the posts they view, you can set up a discussion group for your channel. New posts from the channel will be automatically forwarded to the group and pinned there.

+

Subscribers will see a comment button for each post in the channel. Comments show up in a thread of their own and also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

+
+ +
+ +

View Counters

+

Each post in a channel has a view counter. Views from forwarded copies of the messages are included in the total count.

+
+ TITLE +
+ +

Detailed Statistics

+

Advanced statistics are available for channels with more than 500 subscribers. You can view beautifully-detailed graphs about its growth and the performance of its posts.

+
+ +
+ +

You can track how many users join, leave and mute your channel, what languages they speak, how they interact with your posts, and how they found your channel – from Telegram search, by following a link, etc.

+

Scheduled and Silent Messages

+

You can plan your posts ahead and let them go live automatically at a specified time. For late night or non-urgent updates, you can send silent messages that will result in a notification with no sound for your subscribers.

+

Hold the “Send” button for extra sending options:

+
+ TITLE +
+ +

Pinned Messages

+

You can pin a message for extra visibility.

+
+ TITLE +
+ +

Hashtags

+

Telegram supports hashtags – tapping on a hashtag in a message will show a search interface with all other tagged posts in the channel. This is useful for adding a layer of navigation for your channel and improving visibility of your older posts.

+
+ TITLE +
+ +

Subscriber Privacy

+

The subscriber list is only visible to the channel owner and admins. Subscribers cannot see who else has signed up – nor can they see which accounts are managing the channel.

+

Extra Admins

+

You can appoint additional admins to help you manage the channel and define their role with granular precision. Choose who will be able to add new subscribers, manage messages, edit channel info, or even add new admins.

+

Admin Signatures

+

There are times when it's important to know who posted a certain message. For that, you can enable signatures in Channel Info. New messages will be signed with the posting admin's chosen screen name but will not link to their profile.

+
+ TITLE +
+ +

Embedded Messages

+

Messages from public channels can be easily embedded in any web page using Telegram Widgets.

+

+ +

+
+ + +

Editing Messages

+

Made a typo? Missed a word? Itching to add something? You can easily edit your messages in channels, regardless of how long ago they were posted. Tap the message (double tap or long tap on iOS), then press 'Edit'.

+

Deleting Messages

+

If you'd like to do a bit of timeline maintenance, you can delete any message at any time, for everyone. Deleted messages will vanish from the feed, for both new and old subscribers.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/tour/groups.html b/data/telegram.org/tour/groups.html new file mode 100644 index 0000000000..0146fa91b5 --- /dev/null +++ b/data/telegram.org/tour/groups.html @@ -0,0 +1,266 @@ + + + + + Group Chats on Telegram + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Group Chats on Telegram

+ +
+
+ +
+

Telegram groups are a powerful tool for building communities and can support up to 200,000 members each.

+
+

Friends and families use groups to share photos and plans, teams and businesses to coordinate their work, massive ICOs to answer questions and keep in touch with their investors. Telegram has many features that make communication in groups easy no matter their size or purpose.

+

Replies

+

To reply to a specific message in a group chat, simply swipe left on it, type your text and hit ‘Send’. If you tap on the quote in a message that is a reply, the app scrolls up to the original message – and shows an arrow button to go back to the previous location. This makes navigating conversations in groups easy even if you've been away for a while.

+

The person you replied to will be notified about your message even if they muted the group chat — their notification settings for you personally apply in this case.

+

Mentions

+

If you want several people within a group chat to get instantly involved in the conversation, you may mention them in a message. They will be notified about your message, even if they muted the group chat — unless they've muted you personally, of course!

+

Reply/Mention alerts

+

In busy groups, you can get new mentions or replies many times during a day – and it’s important not to miss those messages. So whenever this happens, you’ll notice straight away by the ‘@’ badge in the chat list:

+
+
+ +
+
+ +

When you have new replies/mentions in a group, you can instantly reach them by tapping the new ‘@’ button when inside the chat. This button will disappear once you’ve read all the relevant messages (you can also use a long tap on the button to quickly mark them as read).

+

Supersize that

+

Groups are ideal for sharing stuff with friends and family or collaboration in small teams. But they can also host very large communities – in fact, up to to 200,000 members can join any group. We have plenty of admin tools to help admins keep the peace in these virtual cities.

+
+

Hint: If you're doing something massively popular, consider creating a channel. Channels are a tool for broadcasting public messages to large audiences, and can have an unlimited number of subscribers.

+
+

Pinned Messages

+

Group admins can inform all members about important news using pinned messages that are displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from the group.

+
+ +

A pinned message

+
+ +

Groups admins can always edit pinned messages. This means your pinned message can contain an up to date list of links to important messages or other channels and groups.

+ + +

Invite Links

+

It's easy to move your existing group chats to Telegram without any hassle. Simply send your friends an invite link. As soon as they get Telegram, they can instantly join your Telegram group just by following that link.

+

To get the link, first create a group on Telegram, then head to the ‘Add participant…’ section and tap ‘Invite to Group via Link’.

+
+ + + +
+
+ +

Public groups

+

If you want a friendlier-looking link, groups can become public and get a short link, like t.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

+
+ +

A public group

+
+ +

Message links

+

You can copy links to individual messages inside public groups. Anyone will be able to see them by opening their t.me link – no Telegram account required. Tweet with confidence!

+

Better With Bots

+

Bots further extend the potential power of groups, making anything possible – from automated moderation to games, payments and beyond.

+

Admin Tools

+

To help maintain order in your community, you can add admins with specific sets of privileges. Choose who among your trusted admins will be able to add new users, manage messages, block members, edit group info, or even add new admins.

+
+ +

Admin rights

+
+ +

Partial Bans

+

Admins who don’t want to completely ban members from their groups can partially restrict their rights in order to stop behavior that's causing problems. You can put nasty users into read-only mode or maybe stop them from sending stickers or media for a certain period of time. You can do all of this with absolute precision:

+
+ +

Partial bans

+
+ +

Even robots can get in on the fun. With Bot API version 3.1, you can use admin bots to automatically impose temporary or permanent bans based on member actions. Check out the docs here to start building your robotic police force today.

+

Recent Admin Actions

+

When multiple admins are working with one group, it’s easy to get confused about which admin did what and when (or which admin bot has gone Skynet on your members). That’s why we've added a “Recent Actions” section to the admins page. This section stores a log of all service actions taken in the group in the last 48 hours and is visible to admins only.

+
+
+ +

Recent admin actions

+
+
+ +

Precise filters

+
+ +

Recent actions in groups also show messages that were deleted in the last 48 hours and the original versions of edited messages for the same period, so nasty behavior like self-deleted spam will no longer help anyone escape the admins’ wrath.

+

Stickers of the Group

+

Large groups with 100 members and more can choose an official sticker set for all the members of the group to see and use while they're chatting in the group — without the need of adding it to their panels.

+
+ +

Group Stickers

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/tour/quizbot.html b/data/telegram.org/tour/quizbot.html new file mode 100644 index 0000000000..6d20bac47b --- /dev/null +++ b/data/telegram.org/tour/quizbot.html @@ -0,0 +1,215 @@ + + + + + Quizzes + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Quizzes

+ +
+ +
+ +
+

Visit Quiz Directory to try thousands of Quizzes created by participants of the 2020 Quiz Contest.

+
+

Telegram supports powerful polls for groups and channels which can be used for everything from deciding where to have lunch to organizing public service exams or leaderless protests.

+

Quiz-style polls are a special kind of poll that has one correct answer and an optional explanation which makes them ideal for educational purposes.

+
+ +
+ +

Quiz Bot

+

With the help of Quiz Bot you can create multi-question quizzes and share them with others. The bot lets you add text or media before questions to help create exam-style prompts with graphs and tables – or Know Your Meme tests.

+
+ TITLE +
+ +

You can set up a time limit for each question. The bot will keep tabs on how many questions users got right and how much time it took them to complete the quiz. It also keeps a global leaderboard for each quiz you create.

+

Creating a Quiz

+

Creating a quiz is very easy, just open @quizbot on Telegram, press 'START' and follow the prompts. If you're having any difficulty, please take a look at our Step-By-Step Instructions.

+

Sharing your Quiz

+

Once your quiz is ready, you can share it to a group or channel – or invite users to answer questions privately, in a chat with the bot. To see how this works, try our demo quiz: Who is Who in the 'Great Minds' sticker pack.

+
+

You can browse thousands of quizzes created during the 2020 Quiz Contest on quiz.directory.

+
+

Making your own Quiz Bot

+

If you are a developer, you are welcome to use the Telegram Bot API to create your own bot that supports polls and quizzes.

+
+

Creating a Quiz, Step-By-Step

+

Creating a quiz is very easy, just open @quizbot on Telegram, press 'START' and follow the prompts.

+

1. Name and description. First you will give your quiz a name and an optional description – for educational tests, it's best to use the subject matter, like Organic Chemistry I or British Royal History. The description could contain information or instructions like “you will need a graphing calculator for this test”.

+

2. Pre-question text or media. Now comes the time to create the quiz's questions. Tapping the 'Create a question' button opens the template to create your first question. However, if you would like text or media to appear before a question, send that first, before tapping 'Create a question'.

+

3. Questions. Once in the new-question interface, simply fill out the fields for what the question is asking, as well as its possible answers. Select the right answer by tapping on it, which will mark it with a green check.

+

4. Explanations. If you want to participate in our contest, you should add an explanation to each of your questions. Explanations will appear after users choose an answer. They can be used to give more information, clarify common errors, and support full text formatting, including hyperlinks. Once you are finished, tap 'Send' to add the question to your test. Repeat the question-making process until you've added all your quiz's questions, then send /done in the chat.

+

5. Timer. Next, the bot will ask you to choose how long users will have to answer each question. For questions that don't require any calculations, 10 or 15 seconds is usually enough. But for something like math, longer timers like 3 to 5 minutes are best. You can always change this setting later on, so don't worry.

+

6. Shuffle questions or answer options. The bot will then ask whether you'd like to shuffle question and answer options – meaning the questions will come up in a random order, and the answers for individual questions will be in a random order as well. It's normally a good idea to say 'Yes' here, so students can retake the quiz for practice without simply memorizing the order. However, if you have “all of the above” style answers, or questions that work best if presented in a specific order, select 'No'. Again, this setting can be changed in the future if needed.

+

7. Submitting your quiz to the contest. The bot will ask if you would like to submit your quiz to the contest. If you choose yes, it will ask a couple of additional questions to confirm your submission.

+

8. Testing or sharing your quiz. Your quiz is complete! From here, you'll see an overview of your new quiz, showing the number of questions and its settings. You can 'Start this quiz’, which will do so in a private chat with QuizBot, start it in a group, or forward the quiz to someone via 'Share quiz'. To copy the unique link to your quiz, press and hold 'Start quiz in a group'.

+

9. Editing your quizzes. Tapping 'Edit quiz' will allow you to alter any of the quiz's questions or settings, including its title and description. From 'Edit questions' you can add pre-question text or media, replace the question with improved answers, or even add additional questions. To select an individual question to edit, tap its /view link from the panel.

+

10. Quiz stats. Lastly, you can view Quiz Stats. This shows how many people have taken the quiz, along with who answered the questions most correctly and quickest. You are now the quiz master, ready to put your subjects to the test.

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/tour/screenshots.html b/data/telegram.org/tour/screenshots.html new file mode 100644 index 0000000000..4029c0ce4f --- /dev/null +++ b/data/telegram.org/tour/screenshots.html @@ -0,0 +1,217 @@ + + + + + Telegram Logos and App Screenshots + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ +
+
+

Telegram Logos and App Screenshots

+ +
+ +
+ +

Logos

+

Please feel free to use these Telegram logos for article illustrations, graphs, “forward to Telegram” buttons, etc. Just make sure people understand you're not representing Telegram officially.

+
+

Download Telegram Logos

+
+

Screenshots

+

All Telegram screenshots on this page are dedicated to the public domain, see CC0 1.0 Universal. Click on images to download hi-res versions.

+
+
+ List of chats, main screen of the Telegram app +

List of chats

+
+
+ A group chat with 2,500 members and a poll +

Group chat with poll

+
+ +
+
+ A secret chat with disappearing media as viewed on a device with dark mode enabled +

Secret chat using a dark theme

+
+
+ A private chat with a user, open sticker panel +

Private chat with stickers

+
+ +
+
+ Shared media section, accessible from a contact's profile page +

Shared media section from a chat

+
+
+ Group chat, dowloading a large file in progress +

Group chat with a downloading file

+
+ +
+ + +
+ + +
+
+
+ + + + + + + diff --git a/data/telegram.org/verify.html b/data/telegram.org/verify.html new file mode 100644 index 0000000000..02fc386f61 --- /dev/null +++ b/data/telegram.org/verify.html @@ -0,0 +1,151 @@ + + + + + Page Verification Guidelines + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+
+
+

Page Verification Guidelines

+ +
+ Verification +
+ +

The Telegram team generally verifies active official channels, bots or public groups that have verified accounts on at least two of these services:

+
    +
  1. TikTok
  2. +
  3. Instagram
  4. +
  5. Facebook
  6. +
  7. YouTube
  8. +
  9. Twitter
  10. +
  11. VK
  12. +
  13. Snapchat
  14. +
+

Please add a link to your Telegram channel to your profiles on these services — so that we can confirm that they indeed belong to you. Once this is done, please contact our @VerifyBot for verification.

+

What if I don't have a verified account on two of these services?

+

If you have an undisputed page on Wikipedia, that satisfies Wikipedia's Notability Guidelines – and that page lists a link to your channel, bot or public group on Telegram – it can be counted as one of the missing verified accounts.

+

In the case of organizations, a link to the Telegram channel from the official website of the organization may also be taken into account. The bot will offer to submit additional data and comments after checking the social media links.

+
+

If you're using a Wikipedia or Official Website link instead of one of the social media accounts, please make sure that they include a link to the channel, group or bot you want to verify on Telegram.

+
+

Can my user account be verified?

+

Sorry, Telegram doesn’t verify user accounts at the moment. Verification is only available for big and active official channels, groups and bots.

+

Do I need verification?

+

Note that verification doesn't give any additional abilities in Telegram - it is simply one of the ways to demonstrate that your channel, group or bot is official. A link to Telegram on your official site or other official accounts elsewhere can achieve a similar result.

+

How do I change the name or short link after verification?

+

A verified channel, group or bot can't change its name or short link (t.me/…). If changes are necessary, you can remove verification status first. Contact @VerifyBot and send /unverify. You can then reobtain verification using the bot.

+
+ +
+
+ +
+
+
+ + + + + + + diff --git a/data/telegram.org/what-can-you-do-with-Telegram.html b/data/telegram.org/what-can-you-do-with-Telegram.html new file mode 100644 index 0000000000..710beff8d0 --- /dev/null +++ b/data/telegram.org/what-can-you-do-with-Telegram.html @@ -0,0 +1,283 @@ + + + + + Telegram Messenger + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+
+ + + + + + +
+ +

Why Telegram?

+ +
+
+
+
+

Simple

+
Telegram is so simple you already know how to use it.
+
+
+ +
+
+
+

Private

+
Telegram messages are heavily encrypted and can self-destruct.
+
+
+ +
+
+
+

Synced

+
Telegram lets you access your chats from multiple devices.
+
+
+ +
+
+
+

Fast

+
Telegram delivers messages faster than any other application.
+
+
+ +
+
+
+

Powerful

+
Telegram has no limits on the size of your media and chats.
+
+
+ +
+
+
+

Open

+
Telegram has an open API and source code free for everyone.
+
+
+ +
+
+
+

Secure

+
Telegram keeps your messages safe from hacker attacks.
+
+
+ +
+
+
+

Social

+
Telegram groups can hold up to 200,000 members.
+
+
+ +
+
+
+

Expressive

+
Telegram lets you completely customize your messenger.
+
+
+
+
+ +
+ +
+
+
+ + + + + + + + diff --git a/data/themes.telegram.org.html b/data/themes.telegram.org.html new file mode 100644 index 0000000000..37f3420801 --- /dev/null +++ b/data/themes.telegram.org.html @@ -0,0 +1,162 @@ + + + + + Telegram Themes + + + + + + + + + + + + + + + + + + + +
+ +
+ Don't have Telegram yet? Try it now + +
+
+
+

Telegram Theme Editor

+

The online theme editor allows you to create and modify your existing cloud themes for every platform. Any changes will appear in the apps immediately after you save them.

+ +
+
+ + + + + + + + + + + + + diff --git a/data/themes.telegram.org/auth.html b/data/themes.telegram.org/auth.html new file mode 100644 index 0000000000..8c95fff6af --- /dev/null +++ b/data/themes.telegram.org/auth.html @@ -0,0 +1,163 @@ + + + + + Telegram Themes + + + + + + + + + + + + + + + + + + + +
+ +
+ Don't have Telegram yet? Try it now + +
+
+
+

Telegram Theme Editor

+

The online theme editor allows you to create and modify your existing cloud themes for every platform. Any changes will appear in the apps immediately after you save them.

+ +
+
+ + + + + + + + + + + + + diff --git a/data/translations.telegram.org.html b/data/translations.telegram.org.html new file mode 100644 index 0000000000..8f30c3b857 --- /dev/null +++ b/data/translations.telegram.org.html @@ -0,0 +1,298 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ +
+
+
+
+
+ +
+
+
+
+
+ +
+
+
+

Translating Telegram

+ +
+ +
+ +

We've worked hard to make Telegram's English version as smooth as possible in terms of language. Now we're looking for equally smooth translations into the rest of the world's languages. If you're a linguist, pro translator or language geek and would like to help us get closer to perfection, you've come to the right place.

+

Start Translating

+ +

The Interface

+

To get started, simply log in, find a phrase in your language that you can improve and suggest a new translation – or vote for an existing suggestion. As soon as your suggestions are reviewed and accepted, the new phrases become immediately available in Telegram apps, no updates required.

+

Official Translations

+

We're gradually expanding the list of languages available to all users from the “Language” menu in their apps. If you would like to help us maintain the official translation to your language on a continuous basis, see this page.

+
+

Style Guide

+

We think a good translation should be:

+
1. Consistent
+

The same things need to have the same names everywhere. Not just within one app, but also on all platforms. Telegram features should have the same names on Android, iOS, Windows and macOS – unless they have to do with platform defaults. For system features, we should always use platform defaults (unless they are truly ugly or don't fit).

+
2. Natural
+

You don't have to always stick to the English original. Sometimes it makes more sense to simply describe what the app does in your own language.

+

But please don't get carried away:

+
3. Default
+

It's no longer 2001 and our users have seen many other apps. It will be much easier for them to use Telegram if familiar concepts have familiar names here. Whenever you're looking for a word, focus on those that people are used to seeing in relevant context. What does Apple use in this case? What does Google use? What do Telegram's main competitors in your region use?

+
4. Beautiful
+

Use good language that would make the app look as if it was built in your region. Respect your language's grammar and style where possible. Avoid abbreviations. Try to find ways around gender problems instead of going for things like o(a), unless the workaround looks even more awkward. In most cases it's possible to find a way of saying anything without hurting the language.

+
5. And it MUST FIT
+

This last one is never easy. Sometimes you need to look to the surrounding phrases and change them for the problematic phrase to fit and work.

+
+

An example: the German team couldn't make the secret chats description fit into the lines on an empty chat page. The English text says: 'A user has invited you to a secret chat. Secret chats:' then comes a list that has this item: 'use end-to-end encryption'. The maximum length for the list items is 25 characters. The problem with German is that the term for end-to-end encryption is 'Ende-zu-Ende Verschlüsselung' and is 28 characters long even without the 'use'. An anglicized version would have been 'End-to-end Verschlüsselung' — but it's still too long at 26 characters.

+

The German team found a workaround. They went and changed the first phrase, so that it now says 'A user has invited you to an end-to-end encrypted secret chat. Secret chats:' and then they came up with a new list item to replace the E2E encryption one, which was moved to the top - where there was enough room.

+
+
+

Typography

+

What we're looking for is not just linguistic, but also typographic and aesthetic correctness. The text is inseparable from design. Text is design and we need to make sure it works. So approach the text as a magazine editor would:

+
    +
  1. Everything must fit into its allotted space. So always check in-app after editing. Words and phrases that are too long will be automatically cut (Like thi…) or contracted (Li…is) — we can't allow this to happen. In other cases the text may flow over into the next line.
  2. +
  3. The text should ideally be kept from spreading over two lines where the original only has one line.
  4. +
  5. Same with double lines, try to avoid letting them spread into triple lines. Although this is a less strict requirement — it isn't too bad if you let the double-line descriptions in Settings become triple lined.
  6. +
  7. We need to avoid hanging words when there's just one or two words left on a new line.
  8. +
  9. We need to avoid gaps in the text, for example when the top right space is empty before the line break. A good way of avoiding this is to use shorter words, so that they wrap more easily. When short words are not an option, put your long ones at the beginning of the line, then add short words as padding.
  10. +
  11. There will be times when making things fit will seem impossible. Our experience shows that it never is. Several determined people focusing on a word and the phrases around it will always find a solution after a few weeks, or even earlier. After all, it's just words.
  12. +
+

This takes some effort, but it really makes you feel proud when you're done.

+
+

Applied Typography

+

On the whole, we've worked hard to make the English version as typographically sound as possible. So as a rule of thumb, if your phrase is the same length as the English one, it will fit well. If it is shorter — not too much of a problem, but beware of hanging words and gaps.

+

Note for iPhone Plus users: When checking strings in-app, try iOS Settings > Display & Brightness > View > 'Zoomed'. Using this mode you can make sure that strings will fit the screens of the narrower models.

+
+

And that‘s about it. Let’s bring perfection to the localized versions of Telegram, together.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en.html b/data/translations.telegram.org/en.html new file mode 100644 index 0000000000..56b13f103e --- /dev/null +++ b/data/translations.telegram.org/en.html @@ -0,0 +1,335 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+
+

+ English (English) + +

+
+ +
+
+

DiscussionsNEW

+

+ Feel free to join the discussion of this language pack. + View Discussion +

+
+
+

Sharing LinkNEW

+

+ Anyone can switch their Telegram interface to English by following this link: +

+ +
+
+

Actions

+ +
+
+
+ +
English
+
English
+
Please open this link on a desktop to help translate Telegram into English:
+ + +
Feel free to join the discussion of this language pack.
+
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/android.html b/data/translations.telegram.org/en/android.html new file mode 100644 index 0000000000..f8fd948a07 --- /dev/null +++ b/data/translations.telegram.org/en/android.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ Android4364 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/android_x.html b/data/translations.telegram.org/en/android_x.html new file mode 100644 index 0000000000..9cd94c5ba9 --- /dev/null +++ b/data/translations.telegram.org/en/android_x.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ Android X3635 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/ios.html b/data/translations.telegram.org/en/ios.html new file mode 100644 index 0000000000..011f2ff625 --- /dev/null +++ b/data/translations.telegram.org/en/ios.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ iOS5114 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/macos.html b/data/translations.telegram.org/en/macos.html new file mode 100644 index 0000000000..2b0efdc956 --- /dev/null +++ b/data/translations.telegram.org/en/macos.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ macOS3695 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/translations.telegram.org/en/tdesktop.html b/data/translations.telegram.org/en/tdesktop.html new file mode 100644 index 0000000000..f6fd44142f --- /dev/null +++ b/data/translations.telegram.org/en/tdesktop.html @@ -0,0 +1,390 @@ + + + + + Translations + + + + + + + + + + + + + + + + + + +
+ +
+ +
+ +
+

+ TDesktop2916 + +

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org.html b/data/tsf.telegram.org.html new file mode 100644 index 0000000000..2c260d5f6e --- /dev/null +++ b/data/tsf.telegram.org.html @@ -0,0 +1,240 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+

Telegram Support Initiative

+ +

Our users ask us tens of thousands of questions each day. We would like to answer them all — and we are looking for brilliant people from all over the world who would like to help us do this. If you are interested in joining us, please read this Telegram Support Force Manifesto — and don't miss the tiny FAQ below.

+
+ +
+ +

Harnessing the power of procrastination

+
    +
  1. Telegram is a free messaging system that is used by tens of millions of people daily. Each of our apps has an ‘Ask a question’ button. Our users press it thousands of times each day: some have questions, others just want to chat, still others are bored trolls. We think that they all deserve an answer of some kind.

    +
  2. +
  3. Robots and algorithms are good at handing out answers at scale, but they sometimes cause frustration, fundamentally lack human touch and are bad conversation partners. FAQs are a remedy for the select few that enjoy finding answers in FAQs. To be happy, humanity requires human answers.

    +
  4. +
  5. Manually answering tens of thousands of questions daily requires considerable resources. Manually answering them in style — even when assisted by algorithms and templates — requires limitless resources. But, the resources in question being humans and time, the modern world happens to have a limitless source of just such energy.

    +
  6. +
  7. This world is full of bright-minded, elegant, downright wonderful people who, like you and me, sometimes just can't get started with whatever they were supposed to be doing. And procrastinate instead. This brings countless people in any profession to hours and hours of unnecessary house-cleaning, dog-walking and web-surfing every day. Millions of hours go to waste — procrastination is as ubiquitous in the XXI century as are people who do their work behind computer screens.

    +
  8. +
  9. It is our goal to harness the power of procrastination. For user support, we rely on an army of volunteers from all over the world. They donate a fraction of their time to answer a few questions from Telegram users — every now and then, or all the time. We call this the Telegram Support Force and you are welcome to join.

    +
  10. +
  11. Answering questions may be devilishly tricky at times, so we couldn't accept everyone even if we wanted to. The Telegram Support Force needs patient, inquisitive people, who are no strangers to elegance, humor and style. Although Telegram volunteers help people from their own countries, proficiency in English is also a requirement, since the data you will be getting from us, as well as pretty much all communication inside the team, will be in English.

    +
  12. +
  13. We believe in support as an art form. Support should be fun — for people on both ends of the line. So we are looking for perfect, human and precise answers to the world's questions. Something to make them smile and to make you proud.

    +
  14. +
+

If this is something you might be interested in doing, don't hesitate to contact our @TelegramAuditions account. Please write us a few phrases in English describing how your favourite feature works (don’t copy it, let it be your hand-made text). Include a picture of a marmot if you want a better chance at convincing us that you actually read all of the above and below and, therefore, are inquisitive enough.

+

Markus Ra
@Telegram

+
+

Manifesto FAQ

+

Q: Do I need to know anything special to be eligible?

+

No, not really. But you do need to know how to learn things. And be inquisitive enough to want to learn them.

+

Q: What else is required?

+

We‘re looking for perfectionists. It’d also be nice if you loved your language and had at least a moderate affection for the people of Earth. It'd be cool if you like to read and write. And then, patience and understanding are very useful at times.

+

Q: Will the people I answer know who I am or get my number?

+

No, they will not. Unless you choose to tell them for some mysterious reason.

+

Q: What should I say when I contact you?

+

We'd love to know more about you (who you are, what you think, what you like — not a CV, no!), the languages you speak and the devices you use (mobile, desktop OS).

+

Q: How long does it take for you to reply?

+

We try not to take too long. But we sometimes do, so we apologize in advance. Sorry. Don‘t lose heart and remember that thing about patience above. We’ll get back to you as soon as we can.

+

Q: Is that thing about sending a marmot picture a joke?

+

No.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/auth.html b/data/tsf.telegram.org/auth.html new file mode 100644 index 0000000000..f0138823b5 --- /dev/null +++ b/data/tsf.telegram.org/auth.html @@ -0,0 +1,241 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+

Telegram Support Initiative

+ +

Our users ask us tens of thousands of questions each day. We would like to answer them all — and we are looking for brilliant people from all over the world who would like to help us do this. If you are interested in joining us, please read this Telegram Support Force Manifesto — and don't miss the tiny FAQ below.

+
+ +
+ +

Harnessing the power of procrastination

+
    +
  1. Telegram is a free messaging system that is used by tens of millions of people daily. Each of our apps has an ‘Ask a question’ button. Our users press it thousands of times each day: some have questions, others just want to chat, still others are bored trolls. We think that they all deserve an answer of some kind.

    +
  2. +
  3. Robots and algorithms are good at handing out answers at scale, but they sometimes cause frustration, fundamentally lack human touch and are bad conversation partners. FAQs are a remedy for the select few that enjoy finding answers in FAQs. To be happy, humanity requires human answers.

    +
  4. +
  5. Manually answering tens of thousands of questions daily requires considerable resources. Manually answering them in style — even when assisted by algorithms and templates — requires limitless resources. But, the resources in question being humans and time, the modern world happens to have a limitless source of just such energy.

    +
  6. +
  7. This world is full of bright-minded, elegant, downright wonderful people who, like you and me, sometimes just can't get started with whatever they were supposed to be doing. And procrastinate instead. This brings countless people in any profession to hours and hours of unnecessary house-cleaning, dog-walking and web-surfing every day. Millions of hours go to waste — procrastination is as ubiquitous in the XXI century as are people who do their work behind computer screens.

    +
  8. +
  9. It is our goal to harness the power of procrastination. For user support, we rely on an army of volunteers from all over the world. They donate a fraction of their time to answer a few questions from Telegram users — every now and then, or all the time. We call this the Telegram Support Force and you are welcome to join.

    +
  10. +
  11. Answering questions may be devilishly tricky at times, so we couldn't accept everyone even if we wanted to. The Telegram Support Force needs patient, inquisitive people, who are no strangers to elegance, humor and style. Although Telegram volunteers help people from their own countries, proficiency in English is also a requirement, since the data you will be getting from us, as well as pretty much all communication inside the team, will be in English.

    +
  12. +
  13. We believe in support as an art form. Support should be fun — for people on both ends of the line. So we are looking for perfect, human and precise answers to the world's questions. Something to make them smile and to make you proud.

    +
  14. +
+

If this is something you might be interested in doing, don't hesitate to contact our @TelegramAuditions account. Please write us a few phrases in English describing how your favourite feature works (don’t copy it, let it be your hand-made text). Include a picture of a marmot if you want a better chance at convincing us that you actually read all of the above and below and, therefore, are inquisitive enough.

+

Markus Ra
@Telegram

+
+

Manifesto FAQ

+

Q: Do I need to know anything special to be eligible?

+

No, not really. But you do need to know how to learn things. And be inquisitive enough to want to learn them.

+

Q: What else is required?

+

We‘re looking for perfectionists. It’d also be nice if you loved your language and had at least a moderate affection for the people of Earth. It'd be cool if you like to read and write. And then, patience and understanding are very useful at times.

+

Q: Will the people I answer know who I am or get my number?

+

No, they will not. Unless you choose to tell them for some mysterious reason.

+

Q: What should I say when I contact you?

+

We'd love to know more about you (who you are, what you think, what you like — not a CV, no!), the languages you speak and the devices you use (mobile, desktop OS).

+

Q: How long does it take for you to reply?

+

We try not to take too long. But we sometimes do, so we apologize in advance. Sorry. Don‘t lose heart and remember that thing about patience above. We’ll get back to you as soon as we can.

+

Q: Is that thing about sending a marmot picture a joke?

+

No.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals.html b/data/tsf.telegram.org/manuals.html new file mode 100644 index 0000000000..1344cba84d --- /dev/null +++ b/data/tsf.telegram.org/manuals.html @@ -0,0 +1,224 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Manuals

+ +

These manuals are intended for volunteers of the TSF, but anyone else is free to take a look as well.

+

Telegram Support BIOS

+

A meta-text and mother of all answers.

+

Answering Questions (TSF-AQ)

+

Covers important topics ranging from our goals to what you do when the user says 'fuck you!'

+

Handling Bugs and Troubleshooting (TSF-BT)

+

Covers investigating, reporting and following up bugs, troubleshooting common issues, reporting tips.

+

Bug Hunting Algorithm (TSF-BHA)

+

An in-depth guide to investigating issues.

+

Feature Philosophy (TSF-FF)

+

A general text to help you understand our reasoning when contemplating new features.

+

Leaving and Coming Back (TSF-OFF)

+

When you realise you're no longer with us.

+

Bug Herding Explained (TSF-BHDE)

+

An advanced manual on handling bugs like a pro.

+

Basic FAQ on End-to-End Encryption (TSF-E2E)

+
+

Public docs

+
Telegram Support Force Manifesto (TSFM)
+

Contains general info on what we do and how to join us.

+
Translating Telegram (TTM)
+

A style guide and manifesto for Telegram translators.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/answering_questions.html b/data/tsf.telegram.org/manuals/answering_questions.html new file mode 100644 index 0000000000..eb6578c289 --- /dev/null +++ b/data/tsf.telegram.org/manuals/answering_questions.html @@ -0,0 +1,265 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Answering Questions

+ +

We answer questions. This document holds general ideas on how to handle them.
This was intended for volunteers of the Telegram Support Force, but anyone else is free to take a look as well.

+

General

+
    +
  1. Our goal is to bring human support to human beings. To achieve this goal, we rely on volunteers. Your pay is perfection in what you do, so be cool.

    +
  2. +
  3. Corporate support standards do not apply here. Treat people in a kind, personal, informal manner. No need to pretend to be something you are not (unless you're a dog in disguise — keep human appearances in this case).

    +
  4. +
  5. Never lie to people.

    +
  6. +
  7. Check everything before you reply. Things change or may no longer work the way you remember. This includes interface details, links (!) and, well, everything.

    +
  8. +
  9. Support is a form of Art, so be fun and creative.

    +
  10. +
+

The result

+

As support volunteers, we need to provide a solution for the user. Remember, that this doesn't always have to be the solution the user was asking for. So first, we want to understand the problem that drove them to ask the question. And then find a way of solving — completely or partially — that problem.

+

For example, some users ask us for an option to send sketches or drawings to their friends. While this is not possible directly, one could take a photo with their thumb on the camera (to get a black picture), then use the drawing tools built into the photo editor to make their doodle.

+

This isn‘t what the user was looking for, but it solves the problem — and it is even more flexible and customizable than the original idea (since you could also add stickers and emoji out of the box). Some solutions are less elegant. For example, right now you can’t email your Telegram conversations. While there is much less need to do so, since you can access everything in the cloud from any of your devices, this may be a problem in some cases. What one could do then, is open the conversation in Telegram Web (or any other desktop client), select multiple messages with the mouse, then copy and paste them into a text document. Any solution is better than no solution at all.

+

There will be cases, when it is not possible to solve the problem at all. As a user in this situation, I want that people on the other end of the line understand me and care about the whole thing. Therefore, two things become important:

+
    +
  • Make it clear that you understand the issue. ‘No, you can’t do that‘ is not a good answer. ’No, I‘m afraid it is not possible to make Telegram wash your dishes in a fast and securely encrypted way’ — is better.
  • +
  • Be gentle. Gentle doesn‘t mean soft — if we really can’t do something, it means just that — we can‘t. But adding ’Sorry about that' helps a lot.
  • +
+

Lastly, whatever the outcome, I always look for help from a human being, not a dumb interface. When you're casual and witty, the user feels more at ease. On the other hand, human beings, as opposed to dumb interfaces, usually understand what is appropriate in which situation. For example, when a user is in distress, he most likely needs help first — and jokes can wait until the crisis has been dealt with.

+
+

To sum up, we need to be: smart (to identify the problem and find an approach to the user), inventive (to find a solution, not always the obvious one), compassionate (in case there is no immediate solution) — and witty (otherwise it gets boring). I'm sure we are.

+

What if I don't know the answer

+

Happens to all. Don't worry, you can always find one. The TSF BIOS will tell you what to do in most situations. In case it doesn‘t or you’re not sure, ask your fellow volunteers in the group — they should know. If worst comes to worst, consult Markus.

+

Admitting you don't know something is infinitely better than trying to cover it up. So when cornered use this mantra: ‘I’m afraid I don‘t know this. Will ask my teammates and get back to you’. Just make sure that the question is not in the FAQs before you say this.

+

Handling user suggestions

+

The three rules for requests and suggestions are: don‘t lie, don’t promise anything, and don't give an exact timeframe.

+
    +
  • The internal Suggestions board on Trello has a list of most frequently suggested features together with estimations on how likely, when and why they will be introduced.
  • +
  • For insights into the decision making process, check our Feature Philosophy.
  • +
+

Plans change frequently, so it‘s best if we only talk about things that exist. Never say that something will be done. ’We may do this‘, ’we will definitely add this at some point in the future‘ or ’this is coming soon' — is as far as we can go.

+

Same applies to the negative: never say we will never do something (except steal users‘ spouses and enslave their children, as mentioned in the general FAQ). The worst thing that can happen is ’we are currently not working on this‘, ’we may consider this', etc.

+

Even if you know something is happening tomorrow, say ‘in the next few days’. People love it when they get things earlier than they expected — and get downright angry if we get 5 minutes (or a few months) late.

+

Reporting bugs in Telegram

+

Every now and then you will get actual bug-reports. We have an internal board on trello, so you will be able to search all known issues and get the relevant info.

+
    +
  • The Handling Bugs manual covers all you need to know about bug reporting in Telegram.
  • +
  • The internal Issues board on Trello lists all known issues.
  • +
+

If you are not part of the team and are looking for advanced troubleshooting tips, you may find the Troubleshooting section interesting.

+

Chatting

+

Truth is, most users come to simply say ‘hello’. Hello them back if you have the time. Sometimes these users do have a question after all. In other cases they may be new to Telegram, without many friends to chat with or show them around. So you can tell them more about Telegram, point to interesting features — or even other Telegram apps. No need to advertise, just explain what needs explaining.

+

Remember: we’re here to help those we can help and talk to others that we feel we have the time to talk to, but not more. If kids get too insistent without any real needs, it’s ok to ignore them after a few replies. If somebody seems to be a nice conversation partner, it’s always a good idea to discuss Telegram, see what the user thinks is missing. Maybe tell them about our Support Initiative.

+

Real-life problems

+

Unfortunately, we cannot really help people with real-life problems. A few kind words wouldn‘t hurt, but generally we should send those users to places where they can get actual help, like a crisis line or chat. (Now, if you want to be a member of the TSF and read this far, go send a picture of a kangaroo to the auditions account. No, this is not a joke. It is a test that helps us understand whether or not you actually read this. And don’t tell others. If you're already a member, you know what to do: humpa viceroy squid)

+

Insults

+

Yep, everyone gets their share of those. First of all, remember that these people are not really talking to you. They just see an abstract ‘Telegram’ entity. My advice is to humor them — I usually send a ‘well, that escalated quickly’ picture and it helps many users. Joke around with them and you’ll be surprised how that can humble people. And never insult back, even if they manage to get you angry for some reason. Nonviolent irony is always your best — and only — weapon.

+
+
Other TSF documents:
+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bios.html b/data/tsf.telegram.org/manuals/bios.html new file mode 100644 index 0000000000..1a1fb07614 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bios.html @@ -0,0 +1,331 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

TSF BIOS

+ +
+ +
+

This page will help you navigate our docs and interfaces in any situation.
It will only be of interest to TSF members. Here's how you become one.

+
+

1. Getting started

+

Answering Questions is our constitution. Come back to it anytime you're in doubt.

+
    +
  1. Our creed and goals
  2. +
  3. I don't know the answer
  4. +
  5. User wants to chat
  6. +
  7. User has real life problems
  8. +
  9. User is insulting me
  10. +
+

The TSupport client is your rifle.
Learn all its features, and use an up to date template file.

+

1a. Asking teammates for help

+

Never hesitate to ask for help in your local TSF group. But remember: Not everyone in your group uses the same support account and speaks the same languages as you. When you want to ask something:

+
    +
  1. Write a summary of the user's question in one message (don't copy-paste, be brief)
  2. +
  3. Always use English (there are team members in your group who don't speak your language)
  4. +
  5. Always include the entire footer from the question (all hashtags)
  6. +
+

1b. Coming back from the dead

+

If you notice that you haven't answered any questions lately, go read the Coming and Going manual.

+

2. Tracing your progress

+

You can check our TSF Panel to see your stats and how you compare against other TSF members. You can also add a little TSF Bio in the panel, so that others know more about you, what you like, what you do, what devices you have and what languages you can speak.

+

3. Basic questions

+

You should be able to handle these easily. Here's where you find information:

+
    +
  1. FAQ
  2. +
  3. Tips & Tricks Trello
  4. +
  5. App comparison table
  6. +
  7. Screenshots (wiki)
  8. +
  9. Answer templates (wiki)
  10. +
  11. Articles about Telegram in the media
  12. +
+

Whenever you learn something that was not in the docs,
make sure that this new info finds its way into the docs!

+

4. Bug reports

+

Search our trello boards before you do anything. In most cases, you will find all the info right away. Ask in your local group if anything is not clear. Use the bug report groups if you need to test things on devices you don't have.

+
    +
  1. Reporting bugs from Answering Questions
  2. +
  3. Bug Handling Manual
  4. +
  5. Investigating Bugs
  6. +
  7. Issues disambiguation board on Trello
  8. +
+

5. User suggestions

+

Search trello boards first. It could be a bug, a feature or a known suggestion. Discuss in local groups if new suggestions need to be added, then add the suggestion to the board. Don't do this if you're not sure. And remember that not all suggestions need to be added to the board. Use common sense and the feature philosophy.

+
    +
  1. Handling user suggestions from Answering Questions
  2. +
  3. Feature philosophy
  4. +
  5. Suggestions Trello board (about)
  6. +
+
+

Read the About section of the Suggestions Board before you add anything.

+
+

6. Projects and suggestions for the TSF

+

The Telegram Support Force is full of brilliant and creative people, and there are many more useful things that can be done besides answering questions. If you're interested in doing more, check out the TSF Projects board where you'll find a list of currently active projects initiated by our TSF members. Find one to your liking or just sign up to be notified when something that requires your skills is going on.

+

The list of projects is not very long for now, but we're working on adding more. If you have an idea for a project, see this card.

+

If you have other suggestions and ideas for the general workings of the TSF, our templates, and interfaces, don't hesitate to contact Markus about it. Oh, and: Rude frescoes. If you have no idea what this last thing was about, read on to the end of this document.

+
+

WARNING: If you've just joined the TSF and are still figuring out what's going on, we'd suggest not to get too involved with things like side projects. It's a better idea to first get comfortable with answering user questions before you spread out.

+
+

7. Security questions

+

Stick to the FAQ in case of ordinary users. Always consult Markus (unless the matter is fully covered in the Bestiary). If Markus is not available at the moment, ask in your local group. Don't be afraid to tell an advanced user that you are not a specialist — you don't have to be.

+
    +
  1. Ask users for the source of their doubts, most likely you'll get a link
  2. +
  3. The Features & Tricks board has a Bestiary section, look there for known articles
  4. +
  5. Advanced FAQ
  6. +
  7. Advanced concerns and questions should be mailed to security@telegram.org
  8. +
+

To use trello search for links, remove the http(s):// part. E.g.:

+
+ +
+ +

Trello search is not perfect for links even this way, so may be a good idea to take a personal look at the Bestiary if the search doesn't return anything. New links for problems that are covered in the Bestiary should be added to the relevant cards.

+

8. New language requests

+

Anyone can use the Translation platform to suggest improvements to our current translations — or create their own custom language packs and translate Telegram into any language.

+
    +
  1. Translations instructions in the FAQ
  2. +
  3. Translations section
  4. +
+

9. Join support force requests

+

Don't give our manifesto to just anybody. Try to see if the user is reasonable. If not, you can tell them that finding how to join us is the first test.

+

10. Media requests

+

Explain that you're a volunteer and can't handle press requests, but they can submit a request to @PressBot.

+

Never promise anything. Be extra careful when handling any questions from journalists. If it's something related to simple Telegram features, reply – but make sure they understand that you've volunteered to help users in support and are not a spokesperson for Telegram.

+

If it's anything more complicated, e.g.:

+
    +
  • Touches on any sensitive subjects like encryption, privacy, moderation, etc. in any way
  • +
  • Contains a list of questions
  • +
+

=> Simply direct to @PressBot.

+

11. Legal stuff

+

You as our volunteers are not trained in legal matters, so it's safer to do nothing at all, should you encounter any kind of legal requests. Lawyers know how to reach us. So simply ignore those messages, do not open, do not reply, do not worry. We'll handle everything.

+

12. Secret words

+

By the way, when reading our manuals, you will sometimes notice words that are definitely out of place. For example, a text may at some point say something like Bionic sycophants out of the blue – only in real life the strange words won't be highlighted in italics. If you find such words in our manuals, talk to @Gladosbot and send her the /sendsecret command (without parameters). The bot will ask you for the secret words you've found and respond if you've entered them correctly.

+

Try this now with the secret words you've just found in the paragraph above – and keep your eyes opened for more of them in other documents. Please don't neglect this! Secret words help us understand whether or not you are up to date on our docs in a friendly way.

+

13. Spam-related requests

+

Some users will complain that they were unfairly limited to only sending messages to their mutual contacts. We at the TSF do not have the tools to handle such requests, but our friendly @spambot is always ready to help them – and it speaks many different languages, including those that we don't. Feel free to send the spambot template to such users. If they keep insisting that you do something about their situation, it is OK to ignore them.

+

Some users will have you believe that somebody reported them 'for fun' or 'by mistake', but the reality is usually very different. We have a dedicated team of moderators that process every report aided by sophisticated algorithms, so it is not easy to get limited by mistake. Naturally, both humans and algorithms can err, but the @spambot has all the tools necessary for filing an appeal.

+

And remember: the vast, absolute majority of Telegram users never get reported at all, most reports are declined, and most of the people that do get limited never even notice it. They can talk to anyone they've talked to before, they can reply to any messages other people send them, and the initial limitation lasts for only a short period of time. Most likely, you wouldn't notice if we limited your account for a week or even a month.

+

Learn more about our antispam systems on Trello »

+

14. Abuse requests

+

The Telegram Support Force is an organization of volunteers that exists to help Telegram users find their way around the apps; you, our volunteers, are not qualified to solve cases involving illegal content — and neither am I (Markus). It is not an issue of trust, rather consider this:

+
    +
  1. We would like our volunteers to be safe from possible legal consequences in case of misunderstandings and incorrectly handled cases.
  2. +
  3. Exposure to certain materials can result in life-long mental scarring, so we want to leave this to professionals that choose to handle such materials for a living.
  4. +
+

For these good reasons the Telegram abuse department is completely separate from the TSF and is staffed by professionals and not volunteers. It is their job to deal with any public content and abuse-related disputes. Please tell users to write to abuse@telegram.org and include all the details and links — or use the built-in report buttons in our apps.

+
+

Please note: spam@telegram.org is NOT used for complaints about spam. More info

+
+

15. Stick to the BIOS

+

This is where you go whenever you're not sure of what to do next. If you don't find your answer in the BIOS, tell Markus about it. It's important to keep this document up to date.

+
+

TSF manuals

+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bug_herding.html b/data/tsf.telegram.org/manuals/bug_herding.html new file mode 100644 index 0000000000..40ea804181 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bug_herding.html @@ -0,0 +1,334 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Bug Herding Explained

+ +
+ +
+

This document is intended for advanced TSF members. If you just joined us, come back later.
There's plenty of more urgent stuff for you to study, don't read this one yet.

+
+

The TSF is made up of volunteers who usually only have a fraction of their time to offer to our cause. They come and go, some of them disappear completely after 500 answers (some after 10, some without even leaving a single one). Our organization must be flexible enough to survive this.

+

Among other things, this means that our Trello boards must be accessible and easy to use for anyone, even if they are just passing by. Therefore, we need dedicated people who can take care of the boards and keep them well maintained for the rest of us, we need bug herders.

+

This manual is for those who would like to become part of this caste.

+
+

Herder protocol

+

You know from the bug handling manual that our final goal, when it comes to issues, is to get a trello card marked either as confirmed by dev or feature. As bug herders, we have more detailed responsibilities. We follow issues from the moment they are found to the public release in which they are resolved — and beyond.

+
    +
  1. Make sure that all newly discovered issues have their own cards (exceptions can be made for problems found in a recent beta version if the dev is in active development and says he'll fix it on the go).
  2. +
  3. Optimize all newly added cards, they must be: easy to find (good name, search keywords), specific (as in 'not vague'), have all the necessary details, but not too verbose.
  4. +
  5. Report all issues to the relevant developer group, not forgetting to include the trello link and an #issue_tag (the same way we do in questions).
  6. +
  7. Find all the requested info and add it to the card, move it to the Reviewed & Reported list, add a comment about this to the card so that we know when this happened.
  8. +
  9. Remind developers about trending issues that have been neglected for too long.
  10. +
  11. Check issues that are marked as fixed (are they?) and add relevant comments.
  12. +
  13. Whenever a new version is out, mark issues as fixed and comment with the version number.
  14. +
  15. Older issues that were fixed need to be archived or deleted after a while (but not immediately, since we will still be getting reports from people who forgot to update their apps).
  16. +
+

Herder goals

+

A bug herder has nothing left to do, if the Unsorted list is empty. Any card in that list should be seen as a call to action. Now let's look at the job in more detail.

+
+

Creating cards

+

If you found a problem, there is a good chance that somebody else from the TSF will soon get a question about it too. So it's important to create a trello card early. Create the card as soon as you have enough info to set the issue apart from the rest.

+

Information in a good card is ordered in this manner:
Problem (what) > Conditions (when) > Explanation (why; optional)

+

The Problem must be described in specific terms (photos are blurry, app crashes, voice messages stop playing).
The Conditions include:

+
    +
  1. The exact circumstances of the problem (photos are blurry in secret chats, app crashes when opening the contacts section, voice messages stop playing when a new message is received).
  2. +
  3. Steps to reproduce the issue.
  4. +
  5. Affected device/OS combinations.
  6. +
+

The Explanation part is optional, but it's nice to have it in cards that could potentially live long lives — e.g., when a bug depends on a specific device/OS combination and can't be fixed easily. (For example: 'This happens when photos are sent from an older version of the app and will stop being relevant when everyone updates.')

+

Title

+

The name of the card should be pretty general, details should be placed in the description. When composing the title, think from the perspective of somebody looking for the issue, who does not know too many details yet.

+

A good title should be structured this way:
Problem, general condition

+

Specific conditions and the explanation go to the description.

+
+

E.g., this card is useless: 'If the contact's name begins with “A” or “S”, iPhone 4s (7.1.2) users will not see messages from them'. When somebody encounters this issue, he will not have enough info to find this card. Most likely, he will only know that an iOS user doesn't get messages from some of their contacts. So if we want someone looking at the card to know that it describes their issue, we need to name it like this, for example: 'User doesn't see new messages if they come from contacts with names starting with “A” or “S”'. We will add a description, saying that the problem was encountered in iPhones 4s with iOS 7.1.2. And we will add all the necessary tags to make search easier, e.g. 'iOS, messages, invisible, not delivered', etc.'

+
+

Description and more info

+

Once you've got a card going, gradually expand it: improve the title, optimize keywords for searchability, add more info, don't forget adding #tq tags from affected users to the comments. Try to avoid any vagueness and ambiguity. E.g.:

+
    +
  • Avoid 'sometimes', 'in some cases', etc if you can. These words signal that additional investigation is required.
  • +
  • Use specific terms. Not 'doesn't work', but 'app crashes' or 'becomes unresponsive', etc.
  • +
  • Don't use 'latest', 'current' or 'previous' in terms of app version. Better stick to actual version numbers — some cards live long lives.
  • +
+

Generally, you need to strike a balance between enough info — and not too much. Developers are busy people, they will not have time to read through a long text, or might even get scared away by verbosity.

+
+

Bad example:

+
+
+ +
+
+ + +
+

And here's almost the same amount of info. But with higher chances to be read by the developer:

+
+
+ +
+ +

One card — one issue

+

If you read the examples above, you will have noticed that the initial card was dedicated to two bugs instead of one. This is very bad. Each issue must have a card to itself, even if the problematic behaviour seems similar. Imagine that your house had a leaky roof and burst water pipes at the same time — both problems mean it'll be very wet inside. But the underlying issues are very different.

+

Keywords & Search

+

The title and text of the card are searchable, but sometimes we need additional keywords. We usually mention them at the bottom, after a separator. This is useful if there are many ways to refer to a problem.

+

Once you've created a card, it's always a good idea to try to search for it yourself. Imagine that you've just met a user with this issue and are looking for info on Trello. What will you type in?

+
    +
  • This may give you ideas for additional keywords.
  • +
  • You may find that there are older cards from the 'Fixed' list are shown at the top of the search so that the card is not visible. Check if it's time to delete them.
  • +
  • You may find that another card is showing up because of bad wording. Try to rewrite it or remove excessive keywords (but only if they are unnecessary).
  • +
+

If there is a card and you had to show it to one of our volunteers who couldn't find it, think how you can improve its wording and keywords.

+
+

E.g., you have a card called 'App freezes when user joins supergroup'. One of the new volunteers asks in their regional group: 'I have a user that says his app crashes when people add him to groups'. You show them your card, but realize that it didn't mention the words 'crash', 'add', or 'group'.
So you add them to the list of keywords below the card. Then you check if it's now possible to find your card using a different description of the problem. You find that a card from 2013 called 'A group of aliens crash-landed on DC1, adding more trouble for the admins' is shown first for this query and delete it because it's a lie and therefore shouldn't be on Trello.

+
+

Affected devices

+

Be careful when mentioning affected devices in the card's title or description. If you can reproduce something on iOS8 — it doesn't mean this is an iOS8 bug yet. This is an iOS8 bug only if you can't reproduce it on iOS7.

+

Hence, the general rule: unless there are devices where the bug can't be reproduced, don't place device/OS version info in the title. Put them in a list under 'reproduced on'.

+

As soon as we see some kind of consistency, we can add things to the title. E.g., if we see that all iOS8 devices have the problem and devices running any other version of the OS do not.

+
+

Reporting to developers

+

Bug herders are also specialists in developer relations. Here's what we should do:

+
    +
  1. Let's stick to the existing app groups for all our contacts with the devs.
  2. +
  3. Let's contact developers when we already have an issue card going — at least a very basic version. (Exceptions could be made for bugs in beta versions that are in active testing.)
  4. +
  5. When contacting the devs, describe the issue, add a trello link and an #issue_tag. This way we can later look up what exactly the developer said about this or that issue (or didn't) and act accordingly. (If issues are investigated in local TSF groups, do insert the #issue_tag there to make the relevant info discoverable there as well.)
  6. +
  7. Once the issue has been optimized and reported, move it to the Reviewed & Reported list.
  8. +
  9. If the developer asks for more info, supply it to the group (and the card if relevant). If you cannot do that right away for any reason, add the questions as a comment to the card, and add the yellow label.
  10. +
  11. Remember that developers are biased and will frequently tell you that the problem belongs to some other developer or even is related to the OS or device and is not our bug. If this happens, it is your task to make sure that we've traced the problem back to the right dev (in the former case) and that we can't demostrate other apps that do the same well on the same device or platform (in the latter).
  12. +
+
+

Archiving issues

+

Once an update is out that fixes an issue, we add a comment along the lines of 'fixed in v.2.9'. Then we leave the issue on the board for about 2 weeks or so — our volunteers will still meet people that need to upgrade to fix their problem. Sometimes an issue deemed to be fixed can also come back to life (likely in a modified form, e.g. 'now only for iPads', etc.).

+

Once the 2 weeks are out, we can assume that the issue is indeed fixed for good. We can then archive the card. Note that archived cards will still show up in search (unless you specifically exclude them). Therefore, it may be more reasonable to delete the cards in case of smaller bugs and interface glitches (this is especially true for interface oversights and feature-like issues).

+

It is acceptable to archive an issue that couldn't be reproduced by us and had no activity (complaints, #tq tags, etc.) for 3-4 months. But don't delete those.

+

Archive:

+
    +
  • Trending issues
  • +
  • Major issues
  • +
  • Inter-app issues
  • +
  • Hard to reproduce issues
  • +
  • Obscure issues without any recent activity
  • +
+

Delete examples:

+
    +
  • Wrong error message when setting a username starting or ending with an underscore
  • +
  • Shared media / shared files selector glitch in landscape mode on iOS 7
  • +
  • Can't forward photo when opening from shared media
  • +
+

..and all other minor interface bugs

+

Deleting cards

+

Since anything that is deleted is lost forever, we shouldn't rush this. But if you're sure, go ahead and do it. If you're not sure, make sure it should be, then go ahead and delete it.

+

Herder responsibility

+

When you create a card or review & report somebody else's card, subscribe to it. And follow it to the end. In the event that something has to be done with it and nobody is doing it — you do it. This way we will not have Mexican standoffs when everybody knows something has to be done, but since technically nobody has to do it, it's never done at all.

+

And that's about it. If we all observe the simple procedures outlined above, peace and prosperity will come down on our homes and trello boards — and all TSF volunteers will only be a few keystrokes aways from any answer they might need.

+

How do I join?

+

You talk to Markus or Daria. But bear in mind that he'll like to see some 20-30 bugs you've created, reviewed and otherwise took care of on Trello. All bug herders should be prepared to spend a lot of time answering questions and tending their issues.

+
+

P.S. Bugging the devs — a note on bug relevance

+

Bugs and even trending bugs have different priorities. Those priorities can be calculated in the same way as one would determine whether a feature is worth considering.

+

I mentioned 'reminding the developers about bugs' as a responsibility of the herder, especially of a herder who is subscribed to a bug. But do remember that there are good and bad times to do this.

+

Whenever an update is imminent, it is a good idea to go through existing issues and make sure that all the critical stuff is fixed. Don't bug pre-release devs with exotic stuff — if it wasn't fixed at this point, it'll have to wait until the next release.

+

The best time for reminding about older issues would probably be a few days after a major release, or as soon as the dust has settled — maybe one day after the release if no major new bugs were found.

+

Such a reminder is best done in the form of a digest. You could collect a few links to well-investigated issues and offer them for consideration in the app's group. Alternatively, you could also gather a few issues that are less clear and ask about them again. Just don't do it in 20 separate messages over the course of seven hours — make it one nice but not too fat message.

+

If that doesn't work, try a smaller number. Maybe choose three important issues and ping him again with a nice concise message. Once he says something of that is fixed, show him your earlier digest and ask to take care of that stuff as well since he's here already.

+

Be cool.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bug_hunting.html b/data/tsf.telegram.org/manuals/bug_hunting.html new file mode 100644 index 0000000000..ed147d79f8 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bug_hunting.html @@ -0,0 +1,270 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Bug Hunting Algorithm

+ +
+ +
+

You already know how to handle bugs in general and what to do with them once they're identified. But how exactly do you investigate a problem and what questions should you ask? Here's an easy algorithm for you.

+
+

0. Reproduce it!

+

Before we even start investigating, we should try to cut out the middleman (in this case, the user). You‘ll save a lot of time if you can reproduce the issue yourself. Then you simply need to investigate the bug, alert your group, log it to Trello if necessary, then present the user with a solution, workaround, or a report that the devs know about the issue and will do something eventually. If you don’t have the necessary devices, try asking in your local group or the Chat.

+

So investigate the bug with the help of the user only if you can‘t reproduce the issue, or don’t understand what steps are necessary to reproduce it, or if the TSF lacks the necessary devices. Otherwise, do it yourself.

+

1. Find out what's wrong

+

We need to figure out why things are not working the way they are supposed to. A million things can go wrong in a computer program. Each one of our apps consists of many thousand lines of code, and we need to tell our developers where to look. Turns out, the easiest way of finding out is by confirming where NOT to look.

+

We want to make the problem smaller and the questions we ask ourselves or the user must eliminate possibilities. As soon as we‘ve removed enough options, we’ll have a pretty good idea of what‘s going on. Remember the game where you need to guess a person’s name that is written on a card stuck to your forehead by asking yes / no questions? Goes like that:

+
+

Is this a real person? No. Is it a comic book character? Yes. Is it a girl? No. Did he appear in a new movie recently? Yes. Does he have cancer? Yes. Deadpool! Right.

+
+

With each step, we eliminate a million wrong answers and get closer and closer to the right one. We can apply the same treatment to bugs. The task then becomes to find the questions that give us the most information and are easiest to answer.

+

But what info do we need?

+

1.1. Locate the responsible party

+

Above all, we need to know which developer is responsible for the bug – in some cases, a bug may not even have to do with Telegram at all. And if it does, the right developer will possibly know what to do and what else to ask. That is, if we can convince him that it's his bug. So, depending on the issue, we may start with one of these questions:

+
    +
  • Does this only happen in one app? Try [insert a different (official) Telegram client].
    This is relatively easy to check and an answer gives us a lot of information. If the issue is not present in other apps, we can assume that it may be platform-specific and that it's unlikely (although still faintly possible) to be a server-side thing. If the issue does reproduce in apps on other OSs‘, it’s likely to be server-related. Only after this question is answered will you truly know the responsible developer. Note: Please only use official clients for this check. Doesn't help us at all if we check whether stuff works in Telegram forks or not.

    +
  • +
  • Does this only happen in Telegram? Try [insert a different standard app that can do the same thing].
    Some issues, especially when they are related to standard components (e.g., keyboard, input field), may be system-wide. If the same glitches reproduce in other apps, our developers are less likely to be able to do something about them (although sometimes they will). Just make sure that you ask people to check stuff in apps they already have installed.

    +
  • +
  • When investigating connection issues: Does this happen on mobile, WiFi or both?
    While not exactly a yes-no question, this one lets our system administrators know where to look for lags. Naturally, it doesn't give us anything useful when the problem is not related to network connections.

    +
  • +
+

Naturally, there are many cases when you can be pretty sure that the bug belongs to the app it was seen on — this is true for interface glitches and any strange behavior in app-specific components. If that's the case, you skip the questions from this section and move on to the next. Brawny pink pastries.

+

1.2. Pinpoint the bug

+

Once you know the problem‘s general address, the possibilities for elimination begin branching out – each issue will require its own pattern. Here are several ideas for questions, but this is by no means an exclusive or required list. You’ll need to adapt heavily to the situation you're dealing with each time.

+
    +
  • Is this a local problem or does it involve more than one device/app?
    Since Telegram is about people sending stuff to other people, things can go wrong on one, or two sides, or both. For example: a video can't be played. The problem may be in the receiving app (bug in video player) – or it could be in the sending app (bug in video encoder).

    +
  • +
  • Does it happen in a particular kind of chats?
    One-on-one chats, secret chats, basic groups and channels/supergroups use very different underlying technologies. This means that each kind of chats may have its unique problems.

    +
  • +
  • Can this be related to specific settings on the device?
    Some problems may be triggered by external circumstances. E.g., privacy settings that restrict access to photos or contacts. As another example, Android devices may experience high battery drain because some battery-saving software is trying to shut down Telegram processes – Telegram reopens itself all the time and this war is heating up the device.

    +
  • +
  • Does it reproduce in the latest OS version for the relevant device?
    If yes, we don't need to look further into OS versions. If no, we should find out which versions are affected, this will help the developer greatly.

    +
  • +
+

Try to think along these lines. But don't go too deep.

+

1.3. Stop when you have enough

+

For most issues, we only need to know three things:

+
    +
  • What exactly goes wrong and how (detailed description, maybe screenshot)
  • +
  • Which one of the developers is responsible
  • +
  • What steps do we take to reproduce the issue
  • +
+

For issues that can't be easily reproduced, we need additional info:

+
    +
  • What special conditions must be met to reproduce the issue (OS version, exotic device, conjunction of stars…)
  • +
+

Sometimes the developer will ask for additional information or conditions, but generally, that's IT. If you have all this info, you're done – stop tormenting yourself or the user and go report to your local group (and maybe file a Trello card if necessary).

+

1.4. Bundle your questions

+

It is not always possible to have a real-time conversation with the user, so we should load our messages with the maximum possible payload. Instead of saying “are you still having this issue?” and running off, it's better to come up with a small set of questions. Select three or four (more is possible, but can be overwhelming for the user) that would give you the best overview of the problem.

+

Try to come up with several reasons why the issue could be happening, and choose such questions that could either prove or disprove your theories. This way you will use our users‘ time efficiently and keep them happy. Even if they can’t reply right away, you will come back to useful information.

+

Always send numbered lists of questions. This way, the user is less likely to miss one and you will find their reply much easier to read.

+

And that's about it. You are ready to Report the Bug, read about it in more details in the Bug Handling Manual.

+

A few more things before we wrap it up:

+

Appendix A: Useless questions and requests

+

Our goal is not to make the issue disappear for the user we're currently talking to. Our goal is to find out what was wrong and to make the issue go away forever, for everyone.

+

Things like “log out and in again” or “reinstall the app” do not give us any information. Therefore, let's never ask our users to do those things, unless this was expressly recommended by the docs or by the devs. The only exception is when you‘ve run out of options and nobody can reproduce the issue – in this case we’re allowed to say:

+
+

"Well, this is very strange. We can't reproduce this on our side and you say none of our suggestions help. Sorry! You could try reinstalling the app – this shouldn‘t help, but since you’ve already tried everything else, why not do that as well. Tell me if for some reason it does change anything."

+
+

Please note: It is absolutely, 100%, unquestionably FORBIDDEN to START DEBUGGING by asking the user to try logging out and in again, reinstalling the app or any such nonsense.

+

Appendix B: Saving time

+

When talking to people who are having issues, we‘re often tempted to ask some random question, get a +1 to our leaderboard stats and run off to the next question before they return. If you do this, both you and the user are performing utterly useless actions: you’re not helping anyone and they aren't giving us any info.

+

So whenever you ask the user to do something, ask yourself first: If I were alone, diagnosing this issue on my own with an intention to collect information as quickly as possible, would I do this now? If the answer is no, think of something useful instead.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/bugs.html b/data/tsf.telegram.org/manuals/bugs.html new file mode 100644 index 0000000000..27b766f077 --- /dev/null +++ b/data/tsf.telegram.org/manuals/bugs.html @@ -0,0 +1,460 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Handling Bugs and Troubleshooting

+ +
+ +
+

This manual is intended for volunteers of the TSF, but anyone else is free to take a look as well.

+
+

Every now and then users will report bugs in Telegram. The step-by-step guide and troubleshooting tips on this page will help you deal with those reports in style and eventually help Telegram get rid of the bugs themselves.

+

See the Bug Hunting Algorithm for tips on investigating new issues.

+
+

Reporting a bug

+

1. Search known issues

+

We use Trello boards to keep track of bugs (sorry, these boards are TSF-only, here's how you join), features and user suggestions, so your first stop when encountering a bug report is Trello search. Most likely, we already know about the issue — sometimes it is not a bug at all. So make sure you study all the relevant cards.

+

If you have found the issue on Trello, leave a comment in the card with your user's #tq tag and device info (skip this step if the card already has too many comments of that kind or is in the “Hot and Trending” list). Then go right to step 4.

+
+ +
+ +

Trello cards are organized in lists that are pretty self-explanatory:

+
    +
  • The 'Hot & Trending' list has the most important cards
  • +
  • Every card begins its journey in the 'Unsorted' list.
  • +
  • Once the issue was reviewed by a bug herder and reported to the developer, it moves to the 'Reviewed & Reported' list. we can report any new occurrences in the comments (don't forget the footers) and try to find missing puzzle pieces (e.g. the issue happens only on specific devices / OS versions).
  • +
  • Finally, at some point, the card reaches 'Fixed' status, is declared a 'Feature' (this is how we want this to work), or 'Not our bug' (platform restrictions, etc.).
  • +
+
+

The very first card on each board contains a description for all labels and fields.

+
+

Fields
Cards can have a status field which describes what state the issue is in and whether or not it requires any actions on our TSF side. (E.g., “Needs info”, “Needs logs”, or “Confirm fix”). Feel free to update Happens in with the latest version you were able to reproduce the issue in. Other fields are mostly reserved for bug herders, including the Dev Priority field.

+

Labels

+
    +
  • Blue – A notable card. Being aware of what's inside may potentially help you recognize important issues and answer questions from users more easily.
  • +
+
    +
  • Yellow – This card is missing important information.
  • +
  • Sky blue – This card mentions a workaround for the issue.
  • +
+
+

2. Investigate the bug

+
+

IMPORTANT: Please see the Bug Hunting Algorithm after this manual for an in-depth look at investigating bugs.

+
+

If you can't find anything useful on Trello:

+
    +
  1. Check app version. Must be the latest available.
  2. +
  3. Reproduce the bug, if you have a relevant device on hand – using the store version. Mention if you can't reproduce it. Ask in the bug groups if you don't have the device – don't forget to include all hashtags from the user's footer with your question and English summary (don't just forward the messages!).
  4. +
  5. Check the Troubleshooting Tips below, there are some useful tips for identifying and reporting common issues.
  6. +
  7. Find and ask the right questions that allow to locate the bug — in as few steps as possible. We have a separate and rather exciting manual on this topic, known as the Bug Hunting Algorithm.
  8. +
+
+

Reporting a bug is in many regards like convicting the developer of a crime. Just as in that case, you need a clear vision of what happened and why, hard evidence (screenshots) and witnesses (users). Unlike in a criminal case, though, it is considered appropriate and even necessary to reproduce the deed (see if you can reproduce the bug and get the same results).

+

Another crucial difference: our defendant is also the judge. He is accountable, of course, but still biased. It is in the developer's best interest to convince you and the public that the bug is not related to his work. Server-side devs will blame the client devs, client devs will blame the server-side devs — and they all together will blame the OS and device manufacturers. While sometimes this is true, we need to leave no escape for them if it isn't.

+
+

3. Report the bug

+

If the bug is not mentioned on the Issues board and the Troubleshooting manual doesn't have any special instructions for the case, we need to report it on Trello.

+
    +
  1. Make sure you've really completed steps 1 and 2 of this guide.
  2. +
  3. Important: Discuss the issue in the relevant bug group — you never know what your teammates may have to say. Maybe there's no need to create a card and an existing one needs editing instead.
  4. +
  5. If you're sure this is necessary, add the issue to the board. We've added templates like this one to all boards. You can copy them and fill with info.
  6. +
  7. Make sure your heading has all the relevant info. Fill in the rest of the details.
  8. +
  9. Always add the user's (and/or your own, if you reproduced the issue) footer with the system hashtags.
  10. +
  11. Add relevant screenshots or video to the issue. This is optional if the issue is clear enough without them.
  12. +
  13. If the problem involves particular items (account, photo, group, message, etc) we need the coordinates required to locate that particular item (tq/footer, phone number, username, link, Telegram Web address bar string, forwarded copy). Think: if you were a developer who just received your question, would you need to ask for more info instead of giving an answer?
  14. +
  15. Make sure that your description has all the relevant keywords, so that it's easy to find the issue via search.
  16. +
  17. When you add your first issue to Trello send the link to Daria — along with a picture of a beetle.
  18. +
  19. Think of the words you would use if you were looking for that issue — try them in the search box. Adjust the description accordingly.
  20. +
  21. Ask your teammates if you have any doubts.
  22. +
+
Bug Groups
+

We're currently experimenting with TSF-wide bug groups for reporting and investigating issues in the apps. You can find a list in this card.

+
Custom Fields and Comments
+
    +
  • There are several custom fields. Fill in 'Happens in' with the hashtag of the version, e.g. #5_1_1_870. The rest of the custom fields are reserved for bug herders, please don't change them unless you're 200% sure you know what you're doing. You can read more about the fields in the first card on each board.
  • +
  • Add a comment whenever a bug's state is changed.
  • +
  • Discuss in the groups, comments are for important updates to the bug only.
  • +
  • Make sure the bug's description covers all the important info that emerged in the comments.
  • +
+

4. Notify the user

+

Once we're done, we need to get back to the user and tell them that we've located the issue or are investigating it. You never know how long that might take, but the user must know that he succeeded in alerting us — and helped us greatly. Parachutes and pasties

+
    +
  • Always include an issue ID hashtag in your reply in this situation.
  • +
  • All Trello cards have unique identifiers (open card, click on “share and more”, then 'link to this card', take the last part of the link, after /c/ — e.g. vMFS4MZf).
  • +
  • We use this ID to create a hashtag (e.g. #issue_vMFS4MZf) and include it in our reply to the user with that problem. Like this, for example:
  • +
+
+

We are terribly sorry that you are not able to delete old profile pictures in channels on the Android application. We reproduced it and are already working on a bug fix. Your issue #issue_lLyHjLRa has been recorded and we'll get back to you as soon as we have any news.

+

By the way, you can delete old profile pictures on the desktop client. Tell us if you want to learn more about it.

+
+

This allows us to use Telegram hashtag search to track issues for follow-up questions. The bot can use these hashtags to send automatic replies when a bug is fixed. We can also search for this issue on Trello by its ID.

+
+ +
+ +

5. Stick to our goals

+
    +
  1. Our final goal in case of any bug is to create a report in Trello that would get the status confirmed by a developer or feature.
  2. +
  3. If no report was created or no existing relevant report found — we did nothing, regardless of how much time we spent talking to the user or TSF members in our groups and diagnosing the issue.
  4. +
+

In order to achieve this goal with a clear conscience, we need to respect our users' time and effort — a little more on this below:

+
+

A note on users

+

One may think that users are people with problems. Wrong. It is us, who have problems — the user is just a convenient medium for studying them. Our problem is either that something is wrong in our system. Or that we can't understand what the user is doing wrong. When you look at it this way, you quickly realize that the user is our most important asset when it comes to bugs. They can help us identify bugs and improve usability.

+

So when somebody comes with a problem, we are not looking for a way to make them go away. Instead we must do all we can to not let the user leave before we find the problem. This means that everything you ask them to do must tell you something important. Nobody enjoys rebooting their phone or logging out and in. The general rule is minimum actions — maximum effect. Rabid bunnies alert

+

If you do ask something that requires at least some effort, please be nice about it! People don't have any obligations to Telegram — we need to convince them to help us and to thank them when they do. It's the least we can do.

+
+

Now that we're done with the basic reporting process, below are some common issues and what you should do when somebody is complaining about similar stuff.

+
+

Troubleshooting common issues

+
+

This advanced troubleshooting guide is intended for volunteers of the Telegram Support Force.
Everyone else is also welcome to take a look. Help friends and loved ones — or troubleshoot yourself!

+
+

+
+

Can’t Install App

+

iOS: Device must run iOS 8 or higher.

+

Android:
- If SDK >= 16 —> Android version must be 4.1
- Ask whether other applications install ok
- If nothing helps we need to know the Android version and device model

+

Messages not getting delivered

+

The following cases cover pretty much all the complaints:

+
    +
  • The user may be confused by the check system. In Telegram: 1 check = message sent, 2 checks = message read (opened by the recipient). So the sender may think the message is not getting delivered or is delivered slowly, while they are in fact waiting for it to be read.
  • +
  • The user may be blocked. When a user is blocked, they will not be notified in any way. Their messages will just stop being read: one tick, always. He should ask his partner to check Settings — Blocked users. Blocked users don't see your online and last seen status and don't see a person's profile picture.
  • +
  • The user may confuse messages and notifications and say that messages are not getting delivered, when he in fact means notification issues. If a person sees the message upon opening the app, but doesn't get notified until he opens the app — see notification problems.
  • +
  • Since people can delete messages for everyone after sending them, it could be that a user means notifications for messages that have already been deleted by the sender.
  • +
  • Lastly, when dealing with Secret Chats, users must remember, that messages will only be delivered to the device that was used when the Secret Chat was created.
  • +
+

In case it's none of these five (but it must be one of these five, really), this is one of the worst things that can ever happen in Telegram. We need to know:

+
    +
  • Phone numbers for all participating users
  • +
  • Devices and app types for all users
  • +
  • Secret chats or cloud chats? Or both?
  • +
  • One-way or two-way problem?
  • +
+

Notification problems

+

iOS:

+
    +
  • Make sure notifications are on in Telegram AND in phone settings (Settings > Notifications), check app version.
  • +
  • Make sure notifications weren’t disabled for a specific chat or group.
  • +
  • Shut down Telegram (go to home screen, swipe up or double tap home button, swipe upwards on Telegram), then go to Phone Settings and disable alerts. Relaunch Telegram, go to Phone Settings, enable alerts.
  • +
+

What we need to know if nothing helps:

+
    +
  • User’s footer tag.
  • +
  • Type of problem (notifications: a. never come, b. come only sometimes)
  • +
  • Logs that capture the problem and time of when the message was received.
  • +
+

Android:

+
    +
  • Make sure the latest app version is installed.
  • +
  • Go to Telegram Settings > Notifications and Sounds, make sure that notifications are ON and Importance is set to “High” or greater.
  • +
  • Check notification priority for Telegram in Android settings, it can be called Importance or Behaviour depending on the device.
  • +
  • Make sure notifications weren’t disabled for a specific chat.
  • +
  • Make sure that Google Play Services are installed on the device.
  • +
+
+

NOTE: Huawei and Xiaomi devices have evil task killer services that interfere with the Telegram notification service. In order for our notifications to work, users need to add Telegram to allowed apps in those devices' security settings. Samsung devices also may require some manipulations.

+

Huawei: Phone Manager App > Protected apps > Add Telegram to the list.
Xiaomi: Services > Security > Permissions > Autostart, find Telegram and enable autostart.
Samsung: Settings > Device Maintenance > Battery > Unmonitored Apps, then add Telegram to that list.

+
+

In case you went through all the steps to no avail, we need to know:

+
    +
  • User’s phone number (username) or footer tag so we can find the user again to followup.
  • +
  • Type of problem (notifications: a. never come, b. come only sometimes)
  • +
  • System and app logs that capture the problem and time of when the message was received.
  • +
+

Contact importing problems

+

User doesn’t see his contacts in Telegram. Or sees numbers instead of names in Messages list.

+
+

Important: Naturally, one of the easiest ways to solve this would be to save the number in international format. Do not advise this before other methods. Our systems must correctly parse any contacts. Therefore it is imperative to collect these samples and bring them to your local group so that we can adjust the algorithms.

+
+

iOS:

+
    +
  • Temporarily change the name of the missing contact in Phone Contacts (not in Telegram) — add a few symbols, then change back again
  • +
  • If that doesn’t help, relogin
  • +
+

Things we need to know if nothing helps:

+
    +
  • User’s phone number
  • +
  • Phone number(s) of the contact(s)
  • +
  • How exactly these numbers are stored in users phone book (international format or anything else?)
  • +
  • Devices and app versions for all users
  • +
+

Android:

+
    +
  • Relaunch the app (not relogin! that won’t help) — swipe the app off the currently-running-apps list
  • +
  • Temporarily change the name of the contact in phone contacts (add a few symbols, then change back again)
  • +
+

Things we need to know if nothing helps:

+
    +
  • User’s phone number
  • +
  • Phone number(s) of the contact(s)
  • +
  • How exactly these numbers are stored in users phone book (international format or anything else?)
  • +
  • Devices and app versions for all users
  • +
+

Speed issues

+

Make sure that we're really talking about speed issues here. In Telegram, 1 check = message sent, 2 checks = message read (opened by the recipient).

+

What we need to know:

+
    +
  • Problem occurs in one app only, or in all apps (e.g. in iOS and TDesktop on the same Wi-Fi).
  • +
  • Problem occurs when sending or receiving (uploading / downloading)? Or both?
  • +
  • What Internet connection is being used? If Wi-Fi, advise user to try LTE and vice versa and see what changes.
  • +
  • Recipient and sender's footer tags (or username/number).
  • +
  • Time of problem (better include the timezone too).
  • +
  • In case of a photo/video, ask the user to forward it to us. Not upload it again, just forward the original message with the attachment.
  • +
+

Connection issues

+

When people are reporting connection issues, check Twitter first: are there any widespread problems. If the problem is local, we need to find out a lot of information before things can be investigated. Things to ask:

+
    +
  • Do other (non-Telegram) apps work OK?
  • +
  • What exactly is happening? (always 'connecting…' / always 'updating…' / seems ok, but messages are not sent / not delivered, etc.)
  • +
  • At what time did it start? Is it still happening?
  • +
  • Is this happening all the time or sometimes?
  • +
  • Does this happen with all Telegram apps — or just one?
  • +
  • Does web.telegram.org work?
  • +
  • The problem happens on Wi-Fi, on mobile connection or in both cases?
  • +
+

Don't forget to include with your report:

+
    +
  • User's footer tag.
  • +
  • Results of @connectivity_test. Which GIFs are downloaded slowly or not downloaded?
  • +
+

It is possible that we'll need a Traceroute to our servers, here's how you get that. Wait for instructions from the server cultists to get the right IP to trace the route to — each case potentially requires a different one.

+

Last seen time is not displayed correctly

+
    +
  • We use the user’s time zone. If he has manually entered a time different from the time zone, he will see the wrong time.
  • +
  • If an app force-quits, the user may remain online for 5-7 minutes after this.
  • +
+

If none of the two, pass to the volunteer group. We need to know:

+
    +
  • The time zone and time set
  • +
  • Detailed description of the problem
  • +
+
+

NOTE: Support accounts are slightly different from ordinary user accounts. Due to some limitations, it is normal if you don't see the correct last seen time for users who are contacting Support.

+
+

User was blocked, but still sees last seen / online status

+

The changes that come with blocking sometimes do not take effect immediately. Give it a few minutes, maybe half an hour — and the blocked user will stop seeing the status.

+

If a blocked user restarts the app or relogins, but can still see online status — pass to the volunteer group. This cannot happen under normal conditions.

+
+

TSF Manuals

+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/come-and-go.html b/data/tsf.telegram.org/manuals/come-and-go.html new file mode 100644 index 0000000000..e3b10448b2 --- /dev/null +++ b/data/tsf.telegram.org/manuals/come-and-go.html @@ -0,0 +1,229 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Leaving and Coming Back

+ +

If you‘re like 80% of us, you’ll most likely realize one day that a whole week had passed and you haven't sent a single answer to a user. Don't panic — that's what volunteering is all about. This manual will help you deal with it.

+

Going away

+

You know how it goes: you don‘t have time today, maybe tomorrow. Then tomorrow you don’t have time again. And then after a while you just forget about it, until one day — bang! — you remember. Now that you did remember, there are three things you can do:

+
    +
  1. Stop by Markus and your local TSF group and say: ‘Hey guys, I’m not going to be around for a while‘. It’s always good to know who's actually with us. OR, since you're here anyway:
  2. +
  3. If you were away for a few days, take 5 questions and answer them. It won‘t take longer than 5-6 minutes — and it means a lot to those who’ll get the answers. OR
  4. +
  5. If you were away for a few weeks, see below, then take 5 questions and answer them. You can do it! And it means a lot to the people out there.
  6. +
+

Coming back

+

Sometimes it‘s hard to come back when you’ve been away for a while. Feels like there‘s a ton of things you’ve missed, and you don't quite know where to start. Well, here:

+
    +
  1. Go to twitter.com/telegram and read all the tweets you‘ve missed. Don’t mind the @replies by Telegram, just read our actual tweets. This way you'll know everything important that happened in the public domain: important updates, blog articles, etc.
  2. +
  3. Open the TSF Notifications group and read everything that‘s been said there. There won’t be much, since we keep the group free of chatting.
  4. +
  5. Go to your local TSF group. Don't read the messages you've missed there — there may be thousands of them, and most of them will no longer be relevant. Just say hello to your teammates and ask them if there are any other new things that you should know.
  6. +
  7. Stick to the BIOS whenever in doubt.
  8. +
+

And that's it. Easy! You're ready to answer some questions again.

+
+

TIP: It is always a good idea to start by searching for your own #tsfUsernameTag, regardless of how long you've been away for. This way you will always be sure that no users are waiting for you to come back and finish the conversation.

+
+

Or not?

+

Look inside you and ask yourself one thing: ‘Why am I here? Do I want to answer their questions?’ And if the answer is ‘errr, no’. Or ‘well, I’m here to get the latest news about Telegram'. Or ‘ummm, I’m here because I want to beta test the apps'.

+

If it‘s one of these, let’s be honest about it — just tell Markus. There's no shame in that, really.

+
+

Addendum: On bugs and testing

+

Testing Telegram apps and finding problems is a useful activity. But, unfortunately, this is not what the Telegram Support Force is about. As volunteers, we go deeper. When we see an issue, we create Trello cards and fill them with info, we collect all the necessary details and make sure the developers know, we find users with similar issues to pinpoint problems — and we tell those users that we know about their problem and salvation is at hand.

+

If you‘re doing all that when you encounter an issue while using the app, you have my sincerest gratitude. But merely writing about bugs in a local TSF group and letting other volunteers do the actual work — I’m afraid, this does not mean being part of the TSF.

+

So if testing and looking for bugs is what you‘d like to do, it’s either this or this. And I'm glad to have met you, regardless of the option you choose.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/e2ee-simple.html b/data/tsf.telegram.org/manuals/e2ee-simple.html new file mode 100644 index 0000000000..95115e07af --- /dev/null +++ b/data/tsf.telegram.org/manuals/e2ee-simple.html @@ -0,0 +1,284 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+

End-to-End Encryption FAQ

+ +
+ +

While checking the results of a recent quiz on how End-to-End Encryption (E2EE) works on Telegram, I noticed that not everyone in the TSF understands this. This document offers some templates along with the basic ideas behind our design decisions.

+

1. Why are Secret Chats only available on their devices of origin?

+

The question goes pretty deep, so it‘s best not confuse the user with too many details right away. Let’s send this first and then explain if any extra questions arise:

+
+

While your Cloud Chats can be accessed from any of your devices anytime, Secret Chats are not part of the Telegram Cloud and are device-specific by design. This way you can always be sure that they are safe for as long as your phone is safe in your pocket. Secret Chats also use end-to-end encryption, so they can’t be synced in the same simple and convenient way as Cloud Chats. We may add support for multi-device Secret Chats in the future.

+

Meanwhile, if you want your conversations to be synced across many devices, consider using Cloud Chats. Please note that they are encrypted as well and are further protected by Telegram's distributed infrastructure. Let me know if you want to learn more about security on Telegram.

+
+

See also: The ‘Learn more’ template »

+

Note: Same as with any templates, please be very careful when sending this one. Take care to adapt the text in such a way that it fits the user‘s questions and situation perfectly. This is especially important when dealing with security-related questions. If you’re not sure you‘re qualified to continue the conversation, don’t hesitate to ask in your local group. There's always help!

+

Now let's look at the question in a little more detail:

+

Multi-device End-to-end encrypted chats are a mess

+

The concept of End-to-End Encryption has no limits for the number of communicating devices. However, if you want to access your end-to-end encrypted chats from multiple devices, you’re facing many technical difficulties, especially when it comes to connecting new devices, loading chat history and restoring backups.

+

Most of our competitors (notably, Whatsapp and iMessage) solve these problems in ways that make their end-to-end encryption useless (this is a big topic, so requires a separate manual). To solve them in a secure way, you’d have to sacrifice usability and some of the features you’re used to – the result would never be as fluent and simple as what we offer in Cloud Chats.

+

One-device Secret Chats are a feature

+

Secret Chats are not just about End-to-End Encryption, otherwise we‘d have simply called them ’end-to-end encrypted chats'. Secret Chats are a bundle of tools for private single-device communication. They are self-sanitizing thanks to self-destruct timers, and you can’t forward messages from them. That secret chats are only available on their devices of origin is also a feature.

+

We like to keep our Secret Chats where we can see them. With single-device chats you can be 100% sure that nobody can access your chats without accessing your (or your chat partner’s) phone first. Politicians and businesspeople around the world appreciate this and have been among Telegram’s early adopters in most countries. The impact for regular users is even higher since they are more likely to leave their work or home computers unlocked and unattended.

+

Most of us have one main device and can manage to keep an eye on it at all times. As a mass user, you probably don’t want these constraints to apply to all of your data, and this is where Cloud Chats come to the rescue.

+

Naturally, it would have been possible to have three types of chats: Cloud Chats, Single-Device Secret Chats, and Multi-Device Secret Chats – a stripped-down and somewhat lamer version of cloud chats. But such levels of complexity are unacceptable for a mass market app, so we had to choose. We chose to have fully functional multi-device cloud chats and single-device secret chats with their own suite of functions like self-destruct timers, protection from forwarding, etc.

+

What makes Cloud Chats cool?

+

Cloud chats don't use E2EE, but we went out of the way to make them as secure as possible while retaining the flexibility that made them famous.

+

These are the most important features of Telegram’s cloud chats for our users:
1. You can log in on any device and see all your chats, immediately.
2. You can start typing on one device, then continue on another – even if you just logged in there for the first time.
3. If you lose your device, you can immediately get all your cloud chats and contacts back.
4. If you need to find a message, you can use instant search to find it, regardless of when and which of your devices you were using when you sent or received it.

+

Are Cloud Chats secure?

+

Since without E2EE Cloud Chat data is theoretically accessible, we use a unique distributed infrastructure to protect it. Cloud Chat data is stored in multiple data centers around the globe that are controlled by different legal entities spread across different jurisdictions. The relevant decryption keys are split into parts and are never kept in the same place as the data they protect. As a result, local intruders or engineers can't access this data, and several court orders from different jurisdictions are required to force us to give up any of it.

+

Thanks to this structure, we can ensure that no single government or block of like-minded countries can intrude on people's privacy and freedom of expression. Telegram can be forced to give up data only if an issue is grave and universal enough to pass the scrutiny of several different legal systems around the world.

+

As a result, we have disclosed 0 bytes of user data to third parties, including governments, to this day.

+

To sum up: Single-device Secret Chats

+
    +
  • Secret Chats are only available on their devices of origin. This is a feature.
  • +
  • Eliminates risk for private conversation if another device is lost, stolen or simply left unattended.
  • +
  • Multi-device Secret Chats would never be as fluent and easy to use as Cloud Chats: no history sync on new devices, no automatic backups, no server search, no cloud drafts.
  • +
  • Other messengers claim they have both E2EE and these features, but in fact they invalidate their E2EE (e.g., iMessage supports multiple devices, but thanks to the way they do it their e2e claims are also invalidated. WhatsApp pushes third-party unencrypted backups to their users, these backups nullify their e2e claims. More on this in a more detailed manual coming soon.)
  • +
  • Cloud chats are stored heavily encrypted and are protected by Telegram’s unique distributed infrastructure.
  • +
  • We may introduce multi-device Secret Chats in the future, even though this requires a lot of work and careful planning.
  • +
+

2. Why are there no Secret Chats on desktop apps?

+

The answers to this question are closely connected to the fact that we decided to restrict Secret Chats to their devices of origin (see above). You could use this template for starters:

+
+

Secret chats require permanent storage on the device, something that Telegram Desktop and Telegram Web don’t support at the moment. We may add this in the future. Currently, both the desktop and the web app load messages from the Cloud on startup and discard them when you quit. Since secret chats are not part of the cloud, this would kill all your secret chats each time you shut down your computer.

+

Secret chats are also device-specific and disappear if you log out — considering this, it is handier to keep them on the one device that you always carry with you. In case you are concerned about the security of your chats on desktop, please note that they are encrypted as well and are further protected by Telegram's distributed infrastructure. Let me know if you want to learn more about security on Telegram.

+
+

See also: The ‘Learn more’ template »

+

Note: Same as with any templates, please be very careful when sending this one. Take care to adapt the text in such a way that it fits the user‘s questions and situation perfectly. This is especially important when dealing with security-related questions. If you’re not sure you‘re qualified to continue the conversation, don’t hesitate to ask in your local group. There's always help!

+

Now let's look at the question in a little more detail:

+

Desktops are less personal

+

We log in from many places on web and desktop. Many of our desktops are monitored by network administrators at work, or accessed by family members at home. We often leave our desktops and even laptops unattended. It's much easier to keep an eye on your phone.

+

Open systems vs. Sandboxed systems

+

Desktop systems and browsers are much more open environments, as opposed to sandboxed environments like mobile OSs. To have Secret Chats, you need your app to store data on the device, and implementing this is slightly more complicated in open systems. The Web and Desktop apps currently get all data from the cloud on startup and discard it when you quit or log out. This would mean losing all your secret chats each time you shut down your computer.

+

But the real challenges for desktop chats arise because Telegram’s Secret Chats are meant to be single-device chats (see above):

+

A chaos of chats with the same person

+

If each chat only connects two devices, users get many different chats with the same person. Imagine two people that have a laptop, a desktop at work and a mobile device each. That’s 9 secret chats in total, and most of them are useless at any given moment.

+

“Is she still at work?” “Should I message him at the home PC?” Most of us will have multiple desktops (work, home, laptop), most of us will have only one main phone. It is most likely that you can get the person by messaging their mobile phone.

+

Search-related troubles

+

There’s an added twist when it comes to finding a certain message. Since no server-side search for messages is possible in the E2EE paradigm, the user would have to remember on their own where to look for a particular message (was it in this chat on this device, or in that chat on that device?). Telegram wouldn’t be able to help in any way.

+

Remember those 9 secret chats with the average person? Each would have an independent chat history, and no server-side search could tell you which one has that important message.

+

Temporary sessions

+

And if that wasn’t enough, desktop sessions tend to be a lot more transient. One of the important features of secret chats is that they are destroyed on your device when you log out. Most desktop users log out rather frequently. Telegram Web users do this even more often.

+

Each time a user logs out, this creates an unusable discarded chat on their partner’s device. Having them on Desktop and Web would mean a lot more such unusable chats cluttering our chat lists.

+

What about Secret Chats in the Mac OS native app?

+

The Mac OS native app, like many others, began as a third-party unofficial app. We always keep an eye out for what third-party developers are doing in our ecosystem. Sometimes features they implement become very popular and make their way to our official apps. This was not the case for Secret Chats in the Mac OS app, which enjoyed a statistically marginal existence. After the app became part of Telegram's official lineup, we did not cut this functionality in order to see if official status would change anything.

+

Several years later, statistics confirm our guesses about the viability of Secret Chats on desktops: same as before, only 2% of the Mac OS app users use them in that app. At the same time, all users of the Mac OS app actively use Secret Chats on their mobile devices – just like other Telegram users.

+

To sum up: No desktop Secret Chats

+
    +
  • Desktops are a much less personal environment, frequently monitored at work and left unattended at home. It’s easier to keep an eye on mobile devices.
  • +
  • Implementing secure storage is more complicated in open desktop systems as opposed to sandboxed mobile environments. Secret Chats require storage to work.
  • +
  • Secret Chats are single-device, so adding more potential sources would result in many Secret Chats with the same person. A mess in UI and no idea which chat to send your message to. You’re more likely to reach a person on the mobile phone.
  • +
  • To find a message, you’d have to search across multiple Secret Chats with the same person on many devices. The server wouldn’t be able to tell you where to look.
  • +
  • Logging out kills Secret Chats, temporary sessions create garbage chats on the partner's device.
  • +
  • We may introduce Secret Chats to our desktop and web apps in the future, even though this requires a lot of work and careful planning.
  • +
+

Note: These arguments and templates are meant for the majority of Telegram users that use a mobile phone as their primary device. If a user tells us that they use their desktop as a primary device, these templates won't work as well. Such users require a different, bespoke approach.

+

The ‘Learn more’ template

+

Both templates in this manual have the line ‘Let me know if you want to learn more about security on Telegram’. Here's a general template you could give to a user who wants to learn more after getting one of them:

+
+

All Telegram data is encrypted and cannot be deciphered by your ISP, network administrator, or random hackers. Cloud chats are stored encrypted in the Telegram Cloud, and the keys needed to decipher this data are kept in other data centers spread across different jurisdictions. This way, local intruders or engineers can't access this data, and several court orders from different jurisdictions are required to force us to give up anything. More on this in the FAQ: https://telegram.org/faq#q-do-you-process-data-requests

+

Secret chats are meant for people who want even more than that. They use end-to-end encryption, so there is no way to decipher your data without accessing your device. It means you don‘t even need to trust Telegram when you use Secret Chats — their secrecy is guaranteed client-side and anyone can check the source code of Telegram clients.

+

If you are concerned about security in general, there are other important precautions you could take. Consider protecting your account by enabling 2-Step Verification and setting up a strong passcode to lock your app, then it won’t be possible to access your chats by stealing your device or even by intercepting your SMS code. You will find both options in ‘Settings’ under ‘Privacy and Security,’ ask me if you’d like more details.

+
+

Note: Same as with any templates, please be very careful when sending this one. Take care to adapt the text in such a way that it fits the user‘s questions and situation perfectly. This is especially important when dealing with security-related questions. If you’re not sure you‘re qualified to continue the conversation, don’t hesitate to ask in your local group. There's always help!

+

Further reading

+

This text and templates should be enough for conversations with ordinary Telegram users. If you would like to go deeper down the rabbit hole, you can study this in-depth manual on End-to-End Encryption. If you have any questions about that one, contact Markus without hesitation. It’s very important that we understand everything.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/e2ee.html b/data/tsf.telegram.org/manuals/e2ee.html new file mode 100644 index 0000000000..fbd858a506 --- /dev/null +++ b/data/tsf.telegram.org/manuals/e2ee.html @@ -0,0 +1,202 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+
+

A Detailed Guide to End-to-End Encryption

+ +

Alas, this magnificent work is not finished yet. Come back later. Yes.

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + + diff --git a/data/tsf.telegram.org/manuals/feature_philosophy.html b/data/tsf.telegram.org/manuals/feature_philosophy.html new file mode 100644 index 0000000000..92101f9e99 --- /dev/null +++ b/data/tsf.telegram.org/manuals/feature_philosophy.html @@ -0,0 +1,263 @@ + + + + + Telegram Support Force + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+
+ +
+
+
+
+ +
+
+ +

Feature Philosophy

+ +
+

This manual is intended for volunteers of the TSF, but anyone else is free to take a look as well.

+
+

There's a million things you could do, and yet you can't do them all at once. Building a messenger, as anything else, is about making the right choices. This manual covers the factors we always keep in mind when considering new features. This text serves as a companion to our (internal) user suggestions board where you can find more detailed estimates on the likelihood for particular features to be added to Telegram.

+

Determining priority

+

The formula to determine which feature gets implemented first is pretty straightforward:

+
(relevance for the project + UX improvement) / (added complexity x speed impact x development time)
+

This formula is everything you really need, although I will describe the components in greater detail below.

+
+

1. Relevance

+

Telegram is a mass market messenger with a focus on speed and security. A good product needs to be consistent, so every feature we add must be relevant to these core aspects. And they are all equally important, we can't give too much preference to any one of them. We must keep all the aspects in harmony.

+
+

E.g. any security-related feature we introduce must allow us to stay comprehensible for the masses and just as fast. Same with mass market features, we must stay as secure as possible when introducing them.

+
+

2. UX improvement

+

While we love our users very much, we are not building our messenger to please individuals. This is a mass market messenger, and we cater to the masses. This automatically means two things:

+
    +
  • Any new feature must be useful to at least 5% of the users (and 50% is better,)
  • +
  • Any new feature must be useful at least 5% of the time (and 50% is better)
  • +
+
+

So ask yourself: Will tens of millions of people around the world use this feature more than once a month?

+
+

Exotic features may look fancy and bring in good press, but they are wasteful. They don't contribute much to overall user experience (since they are used so rarely by so few users) — but they cost you time, developer resources and result in increasing complexity of the interfaces. Introducing a seemingly harmless exotic feature can sometimes result in damaging the UX instead:

+

3. Complexity

+

A good user interface is about minimizing choice and diversity. For example, 90% of Telegram is just 5 screens: list of chats, messages in a chat, profile screen, list of contacts, settings screen. The ultimate goal of a good UI is to rely on as few entities, options and settings as possible.

+

Yes, settings are evil because they fragment the user experience. Each new setting increases the complexity of your app and steepens the learning curve. You cannot escape choices by just offering settings and pushing the decisions you must make over to the user. The more settings you get, the more tuning your user will need to do to arrive at usability.

+

We don't have the luxury of the users' attention and nobody spends an afternoon setting up and studying how an app works. So everything we have must be instantly clear to anyone. Ideally. This may not be exactly the case even now, but the important thing is — we must not make it worse. Extra settings and options are a necessary evil sometimes, but generally we should find ways of avoiding them by providing the one true path out of the box.

+

4. Speed

+

As a mass market messenger Telegram must successfully compete with players that provide fewer encryption options, use weaker algorithms, or neutralize their own encryption for the sake of usability and speed. Thanks to certain breakthroughs in MTProto's design we are above our competition in terms of speed staying more secure at the same time. But we must always be on our guard and take care that the features we introduce do not slow us down too much.

+

5. Development resources

+

Telegram is a small band of very focused developers. We only have one specialist per app — and yet we usually try to update our apps at least once a month, ideally twice. In order to achieve this pace, we must choose wisely what we implement. Some of our plans are affected by the current Telegram infrastructure: certain things are easier to introduce, while other require massive changes in the server-side code, API or the MTProto protocol itself.

+
+

To sum up

+

On the whole, it is better to be rich and healthy than poor and sick. In an ideal universe this means only implementing things that are relevant to the project and to the masses, add zero complexity to the interface, have positive effect on app speed, while costing nothing in terms of time and developer effort.

+

In a more real world this means that we usually wouldn't do things that are irrelevant to the project, or highly exotic, or introduce too much complexity, or slow Telegram down too much, or require too much time and effort (when that same time and effort could be used to make several other things happen, possibly with a higher UX impact).

+

That said, every now and then we do the impossible or the unheard of. Being too rational all the time would be boring, right? Fracture holy chipmunks.

+
+

Feature Philosophy FAQ

+

Q: So who decides?

+

We monitor our users' reactions closely via our support channels, twitter and store reviews. But in order to maintain consistency in the product, the ultimate power of decision must lie in the hands of one person. In Telegram's case this person is Pavel Durov, his vision and experience got us this far — and will hopefully get us much further.

+

Q: Why not let the people decide?

+

User requests are an essential part of Telegram's development. But uncontrolled democratic processes in software development can be dangerous. Unfortunately, vocal minorities don't always properly represent silent majorities. And those silent majorities in turn only become vocal when changes in the system begin hurting them. All of this can result in erratic behavior: adding features just to remove them 6 months later, introducing conciliatory settings. This is usually followed by the slow and inevitable demise of the project.

+

So in Telegram we've opted for a well informed autocratic approach.

+

Q: X has this feature! Why don't we?

+

Many of our competitors have features that we don't have — or don't have yet. It is important to understand that they have those features for a reason. And this reason is not necessarily relevant for Telegram.

+
+

A good example of this is the 'delivered to device' status that some of the WhatsApp fans ask us to introduce. This status would be useless here, Telegram being a cross-platform cloud messenger. I'm logged in on my PC at home and on my phone. So what does it matter to you that my PC downloaded the message while I'm stuck on a mountain with no network coverage on my phone?

+
+

But whatever the situation may be right now, there is always a chance that things will change in the future. So never be radical and never burn your bridges. We're constantly looking for meaningful ways to improve Telegram. This means that any suggestion has a chance of becoming reality — at some point in the future, in some way.

+
+

More TSF manuals

+

+
+ +
+
+
+
+ + + + + + + + + + + + + + + + +