From 99ea79571676869fe5a21b26a9a37c52229b84b8 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 5 Feb 2022 04:41:48 +0000 Subject: [PATCH] Update content of files --- data/core.telegram.org/api.html | 253 + data/core.telegram.org/api/config.html | 422 + data/core.telegram.org/api/end-to-end.html | 244 + .../api/end-to-end/video-calls.html | 215 + data/core.telegram.org/api/pin.html | 149 + data/core.telegram.org/api/stats.html | 297 - .../api/url-authorization.html | 160 + ...sages.sendBroadcast => apple_privacy.html} | 49 +- data/core.telegram.org/bots.html | 437 + .../core.telegram.org/bots/api-changelog.html | 670 -- data/core.telegram.org/bots/api.html | 9488 +++++++++++++++++ data/core.telegram.org/bots/inline.html | 182 + .../constructor/account.authorizationForm | 174 - .../constructor/auth.codeTypeCall | 132 - .../constructor/auth.passwordRecovery | 152 - .../constructor/baseThemeTinted.html | 132 - .../constructor/boolTrue.html | 132 - .../botCommandScopePeerAdmins.html | 150 - .../constructor/channel.html | 289 - ...nnelAdminLogEventActionChangeLocation.html | 152 - .../constructor/contacts.contactsNotModified | 132 - .../decryptedMessageMediaAudio.html | 174 - .../constructor/inlineQueryPeerTypePM.html | 132 - .../constructor/inputFileLocation.html | 165 - .../inputKeyboardButtonUrlAuth.html | 176 - ...userEmpty.html => inputMediaGeoPoint.html} | 24 +- ...html => inputReportReasonPornography.html} | 18 +- .../messageActionInviteToGroupCall.html | 152 - .../messageActionPaymentSentMe.html | 179 - .../messages.allStickersNotModified | 132 - .../constructor/messages.exportedChatInvite | 152 - .../constructor/peerNotifySettings.html | 182 - .../constructor/secureValueTypeAddress.html | 132 - .../secureValueTypeTemporaryRegistration.html | 132 - .../{textUnderline.html => statsURL.html} | 24 +- .../constructor/stickerSet.html} | 99 +- ...tml => topPeerCategoryCorrespondents.html} | 16 +- .../constructor/updateChannelTooLong.html | 161 - ...mpty.html => updateDialogFilterOrder.html} | 28 +- ...eActionDeleteMessages.html => upload.file} | 35 +- data/core.telegram.org/contest300K.html | 237 - .../core.telegram.org/css/bootstrap-extra.css | 3274 ------ data/core.telegram.org/css/core-widgets.css | 105 - data/core.telegram.org/css/telegram-extra.css | 246 - data/core.telegram.org/getProxyConfig.html | 24 + data/core.telegram.org/import-stickers.html | 159 + data/core.telegram.org/js/core-widgets.js | 279 - data/core.telegram.org/js/jquery-ui.min.js | 9 - .../js/telegram-passport2.js | 413 - ...essages.searchGifs => account.verifyPhone} | 54 +- ...ges.editChatTitle => messages.editMessage} | 189 +- ...earAllDrafts => messages.getDialogFilters} | 26 +- .../method/messages.getHistory | 232 - .../method/messages.readDiscussion} | 51 +- .../method/messages.uninstallStickerSet} | 38 +- .../method/payments.clearSavedInfo | 160 - ...cussionMessage => stats.getMegagroupStats} | 56 +- .../method/stats.getMessagePublicForwards | 212 - data/core.telegram.org/mtproto.html | 260 + .../mtproto/TL-polymorph.html | 170 + data/core.telegram.org/mtproto/TL-types.html | 124 + .../mtproto/description_v1.html | 205 + data/core.telegram.org/mtproto/serialize.html | 240 + data/core.telegram.org/passport/example.html | 585 - .../reproducible-builds.html | 488 + data/core.telegram.org/schema.html | 1800 ++++ .../schema/end-to-end-json.html | 1 - data/core.telegram.org/stickers.html | 249 + .../stickers/webm-vp9-encoding.html | 159 + data/core.telegram.org/tdlib.html | 147 + data/core.telegram.org/tdlib/options.html | 501 - data/core.telegram.org/techfaq.html | 333 + .../type/ChannelAdminLogEventAction.html | 298 - .../type/ChannelLocation.html | 148 - .../type/ChatParticipant.html | 153 - .../type/ExportedChatInvite.html | 162 - .../type/ExportedMessageLink.html | 162 - .../type/InputStickerSetItem.html | 143 - ...ortedAuthorization => LangPackString.html} | 41 +- data/core.telegram.org/type/Null.html | 143 - .../type/PasswordKdfAlgo.html | 151 - data/core.telegram.org/type/SavedContact.html | 143 - data/core.telegram.org/type/SecureFile.html | 151 - .../type/SecureValueType.html | 203 - .../StatsGroupTopAdmin.html} | 35 +- data/core.telegram.org/type/Updates.html | 508 - .../type/{contacts.Found => WallPaper.html} | 36 +- .../type/auth.PasswordRecovery | 165 - .../type/messages.ArchivedStickers | 162 - .../type/payments.BankCardData | 162 - data/core.telegram.org/video_stickers.html | 115 + data/corefork.telegram.org.html | 253 + .../api/animated-emojis.html | 187 + .../api/auth.html | 6 +- .../api/bots/commands.html | 140 + .../corefork.telegram.org/api/datacenter.html | 148 - .../corefork.telegram.org/api/discussion.html | 151 + data/corefork.telegram.org/api/drafts.html | 131 + .../api/end-to-end/seq_no.html | 173 - data/corefork.telegram.org/api/errors.html | 189 + data/corefork.telegram.org/api/files.html | 568 + data/corefork.telegram.org/api/folders.html | 179 + data/corefork.telegram.org/api/import.html | 173 + data/corefork.telegram.org/api/invoking.html | 154 + data/corefork.telegram.org/api/mentions.html | 152 + .../api/obtaining_api_id.html | 140 + data/corefork.telegram.org/api/search.html | 179 + data/corefork.telegram.org/api/srp.html | 307 + data/corefork.telegram.org/api/threads.html | 182 + .../api/url-authorization.html | 160 + data/corefork.telegram.org/cdn.html | 210 - .../constructor/auth.sentAppCode | 163 - ...nLogEventActionParticipantToggleAdmin.html | 155 - ...nLogEventActionToggleGroupCallSetting.html | 147 - .../channelParticipantsAdmins.html | 132 + ...ns.html => channelParticipantsBanned.html} | 24 +- .../constructor/channelParticipantsBots.html | 132 + .../channelParticipantsContacts.html | 147 + .../channelParticipantsKicked.html | 147 + ....html => channelParticipantsMentions.html} | 41 +- .../channelParticipantsRecent.html | 6 +- ...ne.html => channelParticipantsSearch.html} | 24 +- .../decryptedMessageActionResend.html | 155 - ...ages.recentStickers => help.countriesList} | 40 +- .../constructor/help.countriesListNotModified | 132 + .../constructor/inputAppEvent.html | 162 - ...{pageBlockAudio.html => inputChannel.html} | 32 +- ...ryChannels.html => inputChannelEmpty.html} | 18 +- .../constructor/inputChannelFromMessage.html | 160 + .../inputDocumentFileLocation.html | 167 - .../constructor/inputMediaPhoto.html | 157 - .../inputPeerChannelFromMessage.html | 160 + .../{peerUser.html => inputPeerChat.html} | 22 +- .../constructor/inputPeerEmpty.html | 132 + .../constructor/inputPeerSelf.html | 6 +- ...pdateGroupCall.html => inputPeerUser.html} | 32 +- .../constructor/inputPeerUserFromMessage.html | 160 + .../inputPrivacyKeyAddedByPhone.html | 132 - .../{photoSizeEmpty.html => inputUser.html} | 33 +- ...ickerSetEmpty.html => inputUserEmpty.html} | 18 +- .../constructor/inputUserFromMessage.html | 160 + ...geBlockDivider.html => inputUserSelf.html} | 18 +- .../messageActionInviteToGroupCall.html | 152 - ...ntMessageLink => messages.affectedHistory} | 40 +- .../constructor/peerLocated.html | 157 - .../{photoPathSize.html => photoSize.html} | 36 +- .../constructor/savedPhoneContact.html | 162 - .../constructor/secureSecretSettings.html | 157 - .../constructor/{chatEmpty.html => true.html} | 37 +- ...ileReuploadNeeded => updateMessageID.html} | 32 +- .../css/telegram-extra.css | 246 - .../corefork.telegram.org/getProxyConfig.html | 24 + .../js/telegram-passport2.js | 413 - .../method/account.getWallPapers | 153 - .../method/account.getWebAuthorizations | 136 - .../method/account.reportProfilePhoto | 165 - .../method/account.updateProfile | 187 - .../method/auth.requestPasswordRecovery | 159 - ...tStickerSet => channels.deleteUserHistory} | 63 +- .../method/channels.getAdminedPublicChannels | 191 - .../method/channels.getSponsoredMessages | 154 - .../method/contacts.getContactIDs | 151 - ...UpNotification => contacts.toggleTopPeers} | 25 +- .../method/help.getAppConfig | 142 - .../method/help.getAppUpdate | 150 - .../method/help.getPromoData | 135 - .../method/help.getSupport | 134 - .../method/help.saveAppLog | 150 - .../method/help.setBotUpdatesStatus | 156 - .../method/messages.deleteHistory} | 67 +- .../method/messages.getSplitRanges | 133 - ...suggestShortName => messages.readMentions} | 45 +- .../method/messages.sendEncryptedService | 205 - ...etChatThemes => messages.unpinAllMessages} | 32 +- .../method/photos.deletePhotos | 148 - .../mtproto/TL-abstract-types.html | 202 + .../mtproto/TL-combinators.html | 251 + .../mtproto/TL-dependent.html | 236 + .../mtproto/TL-formal.html | 319 + .../mtproto/TL-optargs.html | 6 +- .../mtproto/TL-patterns.html | 129 + .../mtproto/TL-polymorph.html | 170 + data/corefork.telegram.org/mtproto/TL-tl.html | 308 + .../mtproto/TL-types.html | 124 + .../mtproto/serialize.html | 240 + .../passport/sdk-android.html | 180 - data/corefork.telegram.org/themes.html | 143 + .../corefork.telegram.org/type/CdnConfig.html | 164 - ...ey.html => ChannelParticipantsFilter.html} | 62 +- .../type/ImportedContact.html | 143 - ...WebFileLocation.html => InputChannel.html} | 31 +- .../type/{RecentMeUrl.html => InputPeer.html} | 54 +- .../{PageListItem.html => InputUser.html} | 36 +- .../type/PageListOrderedItem.html | 148 - .../type/PaymentSavedCredentials.html | 143 - .../type/ReceivedNotifyMessage.html | 143 - data/corefork.telegram.org/type/RichText.html | 218 - .../{RestrictionReason.html => True.html} | 24 +- .../type/auth.CheckedPhone | 128 - .../{help.DeepLinkInfo => help.CountriesList} | 32 +- .../type/long.html} | 30 +- ...swordSettings => messages.AffectedHistory} | 46 +- data/corefork.telegram.org/widgets.html | 141 + .../widgets/discussion.html | 226 + ...android.html => desktop.telegram.org.html} | 46 +- .../auth.html} | 3 +- data/instantview.telegram.org/docs.html | 1527 +++ data/instantview.telegram.org/samples.html | 395 - data/promote.telegram.org/basics.html | 205 - .../promote.telegram.org/getting-started.html | 321 + data/promote.telegram.org/tos.html | 253 - .../api.html => telegram.org.html} | 4 +- ...d-and-usage.html => admin-revolution.html} | 116 +- ...rounds-2-0.html => animated-stickers.html} | 86 +- data/telegram.org/blog/apple-watch.html | 225 - data/telegram.org/blog/cryptocontest.html | 224 - data/telegram.org/blog/folders.html | 298 - ...vacy-emoji.html => group-video-calls.html} | 109 +- .../blog/instant-view-contest-200K.html | 273 + data/telegram.org/blog/invite-links.html | 217 - .../blog/photo-editor-and-passcodes.html | 252 - .../pinned-messages-locations-playlists.html | 282 + .../blog/privacy-discussions-web-bots.html | 284 + ...profile-videos-people-nearby-and-more.html | 315 - ...ected-content-delete-by-date-and-more.html | 324 + .../blog/reactions-spoilers-translations.html | 300 + ...lling-calendar-join-requests-and-more.html | 343 + .../blog/silent-messages-slow-mode.html | 296 + ...android-2-0.html => translations-iv2.html} | 133 +- .../blog/verifiable-apps-and-more.html | 392 - .../blog/video-stickers-better-reactions.html | 273 + .../blog/voice-chats-on-steroids.html | 275 + .../{blog/6-years.html => evolution.html} | 850 +- data/telegram.org/faq.html | 705 ++ data/telegram.org/faq_spam.html | 163 - data/telegram.org/jobs.html | 156 + data/telegram.org/js/games.js | 206 - data/telegram.org/privacy.html | 299 + data/telegram.org/privacy/gmailbot.html | 161 + data/telegram.org/tos.html | 133 + data/telegram.org/tour.html | 144 + data/telegram.org/tour/channels.html | 294 + data/telegram.org/tour/screenshots.html | 217 - .../e2ee.html => themes.telegram.org.html} | 84 +- data/translations.telegram.org.html | 297 - data/translations.telegram.org/en.html | 333 - .../translations.telegram.org/en/android.html | 388 - .../en/android_x.html | 388 - data/translations.telegram.org/en/ios.html | 388 - data/translations.telegram.org/en/macos.html | 388 - .../en/tdesktop.html | 388 - data/tsf.telegram.org.html | 240 - data/tsf.telegram.org/css/billboard.css | 359 - data/tsf.telegram.org/css/bootstrap-extra.css | 3274 ------ data/tsf.telegram.org/css/bootstrap.min.css | 10 - data/tsf.telegram.org/css/health.css | 1422 --- data/tsf.telegram.org/css/jquery-ui.min.css | 6 - data/tsf.telegram.org/css/tchart.min.css | 1 - data/tsf.telegram.org/css/telegram.css | 4872 --------- data/tsf.telegram.org/css/tsf.css | 2473 ----- data/tsf.telegram.org/js/billboard.min.js | 13 - data/tsf.telegram.org/js/bootstrap.min.js | 11 - data/tsf.telegram.org/js/jquery-ui.min.js | 9 - data/tsf.telegram.org/js/jquery.min.js | 4 - data/tsf.telegram.org/js/main-aj.js | 1148 -- data/tsf.telegram.org/js/main.js | 685 -- data/tsf.telegram.org/js/stats.js | 683 -- data/tsf.telegram.org/js/tchart.min.js | 1 - data/tsf.telegram.org/js/tsf.js | 1236 --- 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 - 276 files changed, 31625 insertions(+), 46129 deletions(-) create mode 100644 data/core.telegram.org/api.html create mode 100644 data/core.telegram.org/api/config.html create mode 100644 data/core.telegram.org/api/end-to-end.html create mode 100644 data/core.telegram.org/api/end-to-end/video-calls.html create mode 100644 data/core.telegram.org/api/pin.html delete mode 100644 data/core.telegram.org/api/stats.html create mode 100644 data/core.telegram.org/api/url-authorization.html rename data/core.telegram.org/{method/messages.sendBroadcast => apple_privacy.html} (68%) create mode 100644 data/core.telegram.org/bots.html delete mode 100644 data/core.telegram.org/bots/api-changelog.html create mode 100644 data/core.telegram.org/bots/api.html create mode 100644 data/core.telegram.org/bots/inline.html delete mode 100644 data/core.telegram.org/constructor/account.authorizationForm delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeCall delete mode 100644 data/core.telegram.org/constructor/auth.passwordRecovery delete mode 100644 data/core.telegram.org/constructor/baseThemeTinted.html delete mode 100644 data/core.telegram.org/constructor/boolTrue.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopePeerAdmins.html delete mode 100644 data/core.telegram.org/constructor/channel.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html delete mode 100644 data/core.telegram.org/constructor/contacts.contactsNotModified delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaAudio.html delete mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypePM.html delete mode 100644 data/core.telegram.org/constructor/inputFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html rename data/core.telegram.org/constructor/{userEmpty.html => inputMediaGeoPoint.html} (91%) rename data/core.telegram.org/constructor/{privacyValueDisallowContacts.html => inputReportReasonPornography.html} (91%) delete mode 100644 data/core.telegram.org/constructor/messageActionInviteToGroupCall.html delete mode 100644 data/core.telegram.org/constructor/messageActionPaymentSentMe.html delete mode 100644 data/core.telegram.org/constructor/messages.allStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvite delete mode 100644 data/core.telegram.org/constructor/peerNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeAddress.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html rename data/core.telegram.org/constructor/{textUnderline.html => statsURL.html} (91%) rename data/{corefork.telegram.org/constructor/langPackLanguage.html => core.telegram.org/constructor/stickerSet.html} (73%) rename data/core.telegram.org/constructor/{topPeerCategoryForwardUsers.html => topPeerCategoryCorrespondents.html} (92%) delete mode 100644 data/core.telegram.org/constructor/updateChannelTooLong.html rename data/core.telegram.org/constructor/{photoSizeEmpty.html => updateDialogFilterOrder.html} (86%) rename data/core.telegram.org/constructor/{decryptedMessageActionDeleteMessages.html => upload.file} (87%) delete mode 100644 data/core.telegram.org/contest300K.html delete mode 100644 data/core.telegram.org/css/bootstrap-extra.css delete mode 100644 data/core.telegram.org/css/core-widgets.css delete mode 100644 data/core.telegram.org/css/telegram-extra.css create mode 100644 data/core.telegram.org/getProxyConfig.html create mode 100644 data/core.telegram.org/import-stickers.html delete mode 100644 data/core.telegram.org/js/core-widgets.js delete mode 100644 data/core.telegram.org/js/jquery-ui.min.js delete mode 100644 data/core.telegram.org/js/telegram-passport2.js rename data/core.telegram.org/method/{messages.searchGifs => account.verifyPhone} (77%) rename data/core.telegram.org/method/{messages.editChatTitle => messages.editMessage} (66%) rename data/core.telegram.org/method/{messages.clearAllDrafts => messages.getDialogFilters} (88%) delete mode 100644 data/core.telegram.org/method/messages.getHistory rename data/{corefork.telegram.org/method/account.resetAuthorization => core.telegram.org/method/messages.readDiscussion} (84%) rename data/{corefork.telegram.org/method/langpack.getLanguages => core.telegram.org/method/messages.uninstallStickerSet} (86%) delete mode 100644 data/core.telegram.org/method/payments.clearSavedInfo rename data/core.telegram.org/method/{messages.getDiscussionMessage => stats.getMegagroupStats} (72%) delete mode 100644 data/core.telegram.org/method/stats.getMessagePublicForwards create mode 100644 data/core.telegram.org/mtproto.html create mode 100644 data/core.telegram.org/mtproto/TL-polymorph.html create mode 100644 data/core.telegram.org/mtproto/TL-types.html create mode 100644 data/core.telegram.org/mtproto/description_v1.html create mode 100644 data/core.telegram.org/mtproto/serialize.html delete mode 100644 data/core.telegram.org/passport/example.html create mode 100644 data/core.telegram.org/reproducible-builds.html create mode 100644 data/core.telegram.org/schema.html delete mode 100644 data/core.telegram.org/schema/end-to-end-json.html create mode 100644 data/core.telegram.org/stickers.html create mode 100644 data/core.telegram.org/stickers/webm-vp9-encoding.html create mode 100644 data/core.telegram.org/tdlib.html delete mode 100644 data/core.telegram.org/tdlib/options.html create mode 100644 data/core.telegram.org/techfaq.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEventAction.html delete mode 100644 data/core.telegram.org/type/ChannelLocation.html delete mode 100644 data/core.telegram.org/type/ChatParticipant.html delete mode 100644 data/core.telegram.org/type/ExportedChatInvite.html delete mode 100644 data/core.telegram.org/type/ExportedMessageLink.html delete mode 100644 data/core.telegram.org/type/InputStickerSetItem.html rename data/core.telegram.org/type/{auth.ExportedAuthorization => LangPackString.html} (79%) delete mode 100644 data/core.telegram.org/type/Null.html delete mode 100644 data/core.telegram.org/type/PasswordKdfAlgo.html delete mode 100644 data/core.telegram.org/type/SavedContact.html delete mode 100644 data/core.telegram.org/type/SecureFile.html delete mode 100644 data/core.telegram.org/type/SecureValueType.html rename data/core.telegram.org/{constructor/inlineQueryPeerTypeBroadcast.html => type/StatsGroupTopAdmin.html} (86%) delete mode 100644 data/core.telegram.org/type/Updates.html rename data/core.telegram.org/type/{contacts.Found => WallPaper.html} (79%) delete mode 100644 data/core.telegram.org/type/auth.PasswordRecovery delete mode 100644 data/core.telegram.org/type/messages.ArchivedStickers delete mode 100644 data/core.telegram.org/type/payments.BankCardData create mode 100644 data/core.telegram.org/video_stickers.html create mode 100644 data/corefork.telegram.org.html create mode 100644 data/corefork.telegram.org/api/animated-emojis.html rename data/{core.telegram.org => corefork.telegram.org}/api/auth.html (98%) create mode 100644 data/corefork.telegram.org/api/bots/commands.html delete mode 100644 data/corefork.telegram.org/api/datacenter.html create mode 100644 data/corefork.telegram.org/api/discussion.html create mode 100644 data/corefork.telegram.org/api/drafts.html delete mode 100644 data/corefork.telegram.org/api/end-to-end/seq_no.html create mode 100644 data/corefork.telegram.org/api/errors.html create mode 100644 data/corefork.telegram.org/api/files.html create mode 100644 data/corefork.telegram.org/api/folders.html create mode 100644 data/corefork.telegram.org/api/import.html create mode 100644 data/corefork.telegram.org/api/invoking.html create mode 100644 data/corefork.telegram.org/api/mentions.html create mode 100644 data/corefork.telegram.org/api/obtaining_api_id.html create mode 100644 data/corefork.telegram.org/api/search.html create mode 100644 data/corefork.telegram.org/api/srp.html create mode 100644 data/corefork.telegram.org/api/threads.html create mode 100644 data/corefork.telegram.org/api/url-authorization.html delete mode 100644 data/corefork.telegram.org/cdn.html delete mode 100644 data/corefork.telegram.org/constructor/auth.sentAppCode delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsAdmins.html rename data/corefork.telegram.org/constructor/{updateDcOptions.html => channelParticipantsBanned.html} (89%) create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsBots.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsContacts.html create mode 100644 data/corefork.telegram.org/constructor/channelParticipantsKicked.html rename data/corefork.telegram.org/constructor/{channelParticipantCreator.html => channelParticipantsMentions.html} (79%) rename data/{core.telegram.org => corefork.telegram.org}/constructor/channelParticipantsRecent.html (98%) rename data/corefork.telegram.org/constructor/{textUnderline.html => channelParticipantsSearch.html} (89%) delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionResend.html rename data/corefork.telegram.org/constructor/{messages.recentStickers => help.countriesList} (84%) create mode 100644 data/corefork.telegram.org/constructor/help.countriesListNotModified delete mode 100644 data/corefork.telegram.org/constructor/inputAppEvent.html rename data/corefork.telegram.org/constructor/{pageBlockAudio.html => inputChannel.html} (88%) rename data/corefork.telegram.org/constructor/{topPeerCategoryChannels.html => inputChannelEmpty.html} (91%) create mode 100644 data/corefork.telegram.org/constructor/inputChannelFromMessage.html delete mode 100644 data/corefork.telegram.org/constructor/inputDocumentFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaPhoto.html create mode 100644 data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html rename data/corefork.telegram.org/constructor/{peerUser.html => inputPeerChat.html} (91%) create mode 100644 data/corefork.telegram.org/constructor/inputPeerEmpty.html rename data/{core.telegram.org => corefork.telegram.org}/constructor/inputPeerSelf.html (98%) rename data/corefork.telegram.org/constructor/{updateGroupCall.html => inputPeerUser.html} (87%) create mode 100644 data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html rename data/corefork.telegram.org/constructor/{photoSizeEmpty.html => inputUser.html} (87%) rename data/corefork.telegram.org/constructor/{inputStickerSetEmpty.html => inputUserEmpty.html} (92%) create mode 100644 data/corefork.telegram.org/constructor/inputUserFromMessage.html rename data/corefork.telegram.org/constructor/{pageBlockDivider.html => inputUserSelf.html} (92%) delete mode 100644 data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html rename data/corefork.telegram.org/constructor/{messages.sentMessageLink => messages.affectedHistory} (86%) delete mode 100644 data/corefork.telegram.org/constructor/peerLocated.html rename data/corefork.telegram.org/constructor/{photoPathSize.html => photoSize.html} (87%) delete mode 100644 data/corefork.telegram.org/constructor/savedPhoneContact.html delete mode 100644 data/corefork.telegram.org/constructor/secureSecretSettings.html rename data/corefork.telegram.org/constructor/{chatEmpty.html => true.html} (90%) rename data/corefork.telegram.org/constructor/{upload.cdnFileReuploadNeeded => updateMessageID.html} (85%) delete mode 100644 data/corefork.telegram.org/css/telegram-extra.css create mode 100644 data/corefork.telegram.org/getProxyConfig.html delete mode 100644 data/corefork.telegram.org/js/telegram-passport2.js delete mode 100644 data/corefork.telegram.org/method/account.getWallPapers delete mode 100644 data/corefork.telegram.org/method/account.getWebAuthorizations delete mode 100644 data/corefork.telegram.org/method/account.reportProfilePhoto delete mode 100644 data/corefork.telegram.org/method/account.updateProfile delete mode 100644 data/corefork.telegram.org/method/auth.requestPasswordRecovery rename data/corefork.telegram.org/method/{messages.getStickerSet => channels.deleteUserHistory} (77%) delete mode 100644 data/corefork.telegram.org/method/channels.getAdminedPublicChannels delete mode 100644 data/corefork.telegram.org/method/channels.getSponsoredMessages delete mode 100644 data/corefork.telegram.org/method/contacts.getContactIDs rename data/corefork.telegram.org/method/{account.setContactSignUpNotification => contacts.toggleTopPeers} (87%) delete mode 100644 data/corefork.telegram.org/method/help.getAppConfig delete mode 100644 data/corefork.telegram.org/method/help.getAppUpdate delete mode 100644 data/corefork.telegram.org/method/help.getPromoData delete mode 100644 data/corefork.telegram.org/method/help.getSupport delete mode 100644 data/corefork.telegram.org/method/help.saveAppLog delete mode 100644 data/corefork.telegram.org/method/help.setBotUpdatesStatus rename data/{core.telegram.org/method/payments.getPaymentForm => corefork.telegram.org/method/messages.deleteHistory} (78%) delete mode 100644 data/corefork.telegram.org/method/messages.getSplitRanges rename data/corefork.telegram.org/method/{stickers.suggestShortName => messages.readMentions} (85%) delete mode 100644 data/corefork.telegram.org/method/messages.sendEncryptedService rename data/corefork.telegram.org/method/{account.getChatThemes => messages.unpinAllMessages} (83%) delete mode 100644 data/corefork.telegram.org/method/photos.deletePhotos create mode 100644 data/corefork.telegram.org/mtproto/TL-abstract-types.html create mode 100644 data/corefork.telegram.org/mtproto/TL-combinators.html create mode 100644 data/corefork.telegram.org/mtproto/TL-dependent.html create mode 100644 data/corefork.telegram.org/mtproto/TL-formal.html rename data/{core.telegram.org => corefork.telegram.org}/mtproto/TL-optargs.html (98%) create mode 100644 data/corefork.telegram.org/mtproto/TL-patterns.html create mode 100644 data/corefork.telegram.org/mtproto/TL-polymorph.html create mode 100644 data/corefork.telegram.org/mtproto/TL-tl.html create mode 100644 data/corefork.telegram.org/mtproto/TL-types.html create mode 100644 data/corefork.telegram.org/mtproto/serialize.html delete mode 100644 data/corefork.telegram.org/passport/sdk-android.html create mode 100644 data/corefork.telegram.org/themes.html delete mode 100644 data/corefork.telegram.org/type/CdnConfig.html rename data/corefork.telegram.org/type/{InputPrivacyKey.html => ChannelParticipantsFilter.html} (70%) delete mode 100644 data/corefork.telegram.org/type/ImportedContact.html rename data/corefork.telegram.org/type/{InputWebFileLocation.html => InputChannel.html} (84%) rename data/corefork.telegram.org/type/{RecentMeUrl.html => InputPeer.html} (73%) rename data/corefork.telegram.org/type/{PageListItem.html => InputUser.html} (81%) delete mode 100644 data/corefork.telegram.org/type/PageListOrderedItem.html delete mode 100644 data/corefork.telegram.org/type/PaymentSavedCredentials.html delete mode 100644 data/corefork.telegram.org/type/ReceivedNotifyMessage.html delete mode 100644 data/corefork.telegram.org/type/RichText.html rename data/corefork.telegram.org/type/{RestrictionReason.html => True.html} (88%) delete mode 100644 data/corefork.telegram.org/type/auth.CheckedPhone rename data/corefork.telegram.org/type/{help.DeepLinkInfo => help.CountriesList} (82%) rename data/{core.telegram.org/type/string.html => corefork.telegram.org/type/long.html} (66%) rename data/corefork.telegram.org/type/{account.PasswordSettings => messages.AffectedHistory} (74%) create mode 100644 data/corefork.telegram.org/widgets.html create mode 100644 data/corefork.telegram.org/widgets/discussion.html rename data/{telegram.org/android.html => desktop.telegram.org.html} (50%) rename data/{instantview.telegram.org.html => instantview.telegram.org/auth.html} (99%) create mode 100644 data/instantview.telegram.org/docs.html delete mode 100644 data/instantview.telegram.org/samples.html delete mode 100644 data/promote.telegram.org/basics.html create mode 100644 data/promote.telegram.org/getting-started.html delete mode 100644 data/promote.telegram.org/tos.html rename data/{telegram.org/api.html => telegram.org.html} (99%) rename data/telegram.org/blog/{unsend-and-usage.html => admin-revolution.html} (58%) rename data/telegram.org/blog/{backgrounds-2-0.html => animated-stickers.html} (55%) delete mode 100644 data/telegram.org/blog/apple-watch.html delete mode 100644 data/telegram.org/blog/cryptocontest.html delete mode 100644 data/telegram.org/blog/folders.html rename data/telegram.org/blog/{unsend-privacy-emoji.html => group-video-calls.html} (58%) create mode 100644 data/telegram.org/blog/instant-view-contest-200K.html delete mode 100644 data/telegram.org/blog/invite-links.html delete mode 100644 data/telegram.org/blog/photo-editor-and-passcodes.html create mode 100644 data/telegram.org/blog/pinned-messages-locations-playlists.html create mode 100644 data/telegram.org/blog/privacy-discussions-web-bots.html delete 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/reactions-spoilers-translations.html create mode 100644 data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html create mode 100644 data/telegram.org/blog/silent-messages-slow-mode.html rename data/telegram.org/blog/{android-2-0.html => translations-iv2.html} (52%) delete mode 100644 data/telegram.org/blog/verifiable-apps-and-more.html create mode 100644 data/telegram.org/blog/video-stickers-better-reactions.html create mode 100644 data/telegram.org/blog/voice-chats-on-steroids.html rename data/telegram.org/{blog/6-years.html => evolution.html} (57%) create mode 100644 data/telegram.org/faq.html delete mode 100644 data/telegram.org/faq_spam.html create mode 100644 data/telegram.org/jobs.html delete mode 100644 data/telegram.org/js/games.js create mode 100644 data/telegram.org/privacy.html create mode 100644 data/telegram.org/privacy/gmailbot.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 delete mode 100644 data/telegram.org/tour/screenshots.html rename data/{tsf.telegram.org/manuals/e2ee.html => themes.telegram.org.html} (64%) delete mode 100644 data/translations.telegram.org.html delete mode 100644 data/translations.telegram.org/en.html delete mode 100644 data/translations.telegram.org/en/android.html delete mode 100644 data/translations.telegram.org/en/android_x.html delete mode 100644 data/translations.telegram.org/en/ios.html delete mode 100644 data/translations.telegram.org/en/macos.html delete mode 100644 data/translations.telegram.org/en/tdesktop.html delete mode 100644 data/tsf.telegram.org.html delete mode 100644 data/tsf.telegram.org/css/billboard.css delete mode 100644 data/tsf.telegram.org/css/bootstrap-extra.css delete mode 100644 data/tsf.telegram.org/css/bootstrap.min.css delete mode 100644 data/tsf.telegram.org/css/health.css delete mode 100644 data/tsf.telegram.org/css/jquery-ui.min.css delete mode 100644 data/tsf.telegram.org/css/tchart.min.css delete mode 100644 data/tsf.telegram.org/css/telegram.css delete mode 100644 data/tsf.telegram.org/css/tsf.css delete mode 100644 data/tsf.telegram.org/js/billboard.min.js delete mode 100644 data/tsf.telegram.org/js/bootstrap.min.js delete mode 100644 data/tsf.telegram.org/js/jquery-ui.min.js delete mode 100644 data/tsf.telegram.org/js/jquery.min.js delete mode 100644 data/tsf.telegram.org/js/main-aj.js delete mode 100644 data/tsf.telegram.org/js/main.js delete mode 100644 data/tsf.telegram.org/js/stats.js delete mode 100644 data/tsf.telegram.org/js/tchart.min.js delete mode 100644 data/tsf.telegram.org/js/tsf.js delete mode 100644 data/tsf.telegram.org/manuals.html delete mode 100644 data/tsf.telegram.org/manuals/answering_questions.html delete mode 100644 data/tsf.telegram.org/manuals/bios.html delete mode 100644 data/tsf.telegram.org/manuals/bug_herding.html delete mode 100644 data/tsf.telegram.org/manuals/bug_hunting.html delete mode 100644 data/tsf.telegram.org/manuals/bugs.html delete mode 100644 data/tsf.telegram.org/manuals/come-and-go.html diff --git a/data/core.telegram.org/api.html b/data/core.telegram.org/api.html new file mode 100644 index 0000000000..f6775268b5 --- /dev/null +++ b/data/core.telegram.org/api.html @@ -0,0 +1,253 @@ + + + + + Telegram APIs + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+
+
+
+

Telegram APIs

+ +

We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

+

You can also add Telegram Widgets to your website.

+

Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

+
+

Bot API

+
+ +
+

This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

+

To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle 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.

+
+

Learn more about the Bot API here »

+
+

Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

+
+

TDLib – build your own Telegram

+

Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

+

TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

+

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 open source and compatible with virtually any programming language.

+
+

Learn more about TDLib here »

+
+
+

Telegram API

+

This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

+ +

Getting started

+

Creating an application

+

How to get your application identifier and create a new Telegram app.

+

User authorization

+

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

+

Two-factor authentication

+

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

+

QR code login

+

QR code login flow

+

Error handling

+

How to handle API return errors correctly.

+

Handling different data centers

+

How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

+

Handling updates

+

How to subscribe to updates and handle them properly.

+

Handling PUSH-notifications

+

How to subscribe and handle them properly.

+

Channels, supergroups and groups

+

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

+

Channel statistics

+

Telegram offers detailed channel statistics for channels and supergroups.

+

Calling methods

+

Additional options for calling methods.

+

Uploading and Downloading Files

+

How to transfer large data batches correctly.

+

Pagination

+

How to fetch results from large lists of objects.

+

Client configuration

+

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

+

Security

+

Secret chats, end-to-end encryption

+

End-to-end-encrypted messaging.

+

Security guidelines

+

Important checks required in your client application.

+

Perfect Forward Secrecy

+

Binding temporary authorization key to permanent ones.

+

End-to-End Encryption in Voice and Video Calls

+

End-to-end-encrypted calls.

+

Optimization

+

Client optimization

+

Ways to boost API interactions.

+

API methods

+

Available method list

+

A list of available high-level methods.

+

API TL-schema, as JSON

+

Text and JSON-presentation of types and methods used in API.

+

Available layer list

+

A list of available schema versions.

+

Other articles

+

Working with bots, using the MTProto API

+

How to work with bots using the MTProto API.

+

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.

+

Search & filters

+

Telegram allows applying detailed message filters while looking for messages in chats. +This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

+

Polls

+

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

+

Admin, banned and default rights for channels, supergroups and groups

+

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

+

Discussion groups

+

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

+

Channel comments and message threads

+

Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

+

Admin log

+

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

+

Pinned messages

+

Telegram allows pinning multiple messages on top of a specific chat.

+

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.

+

Live geolocations

+

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

+

Min constructors

+

Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

+

Account deletion

+

How to reset an account if the 2FA password was forgotten.

+

Imported messages

+

Telegram allows importing messages and media from foreign chat apps.

+

Telegram Passport

+

How to work with Telegram Passport directly using the MTProto API.

+

Telegram Payments

+

How to work with Telegram Payments directly using the MTProto API.

+

Styled text with message entities

+

How to create styled text with message entities

+

Working with animated emojis

+

Graphical telegram clients should transform emojis into their respective animated version.

+

Working with animated dice

+

Telegram supports sending animated dice emojis.

+

Message drafts

+

How to handle message drafts

+

Folders

+

Working with folders

+

Top peer rating

+

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

+

Handling file references

+

How to handle file references.

+

Seamless Telegram Login

+

Handle Seamless Telegram Login URL authorization requests.

+

Web events

+

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + diff --git a/data/core.telegram.org/api/config.html b/data/core.telegram.org/api/config.html new file mode 100644 index 0000000000..5e804b24ce --- /dev/null +++ b/data/core.telegram.org/api/config.html @@ -0,0 +1,422 @@ + + + + + Client configuration + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+
+
+
+

Client configuration

+ +
+ +

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

+

MTProto configuration

+
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;
+
+---functions---
+
+help.getConfig#c4f9186b = Config;
+help.getNearestDc#1fb33026 = NearestDc;
+

The huge config constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the constructor page for more information.

+

Client configuration

+
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;
+
+---functions---
+
+help.getAppConfig#98914110 = JSONValue;
+

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
+While help.getConfig returns MTProto-specific configuration with information about server-side limitations and other MTProto-related information, help.getAppConfig returns configuration parameters useful for graphical Telegram clients.

+

Typical fields included in the resulting JSON object are:

+
    +
  • emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)
    • +
  • keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean)
    • +
  • background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)
    • +
  • emojies_send_dice - A list of supported animated dice stickers (array of strings).
    • +
  • emojies_send_dice_success - For animated dice emojis other than the basic 🎲, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 🎆 (object with emoji keys and object values, containing value and frame_start float values)
    • +
  • emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs, with emoji string keys)
    • +
  • gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)
    • +
  • gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis)
    • +
  • stickers_emoji_suggest_only_api - Specifies that the app should not display local sticker suggestions for emojis at all and just use the result of messages.getStickers (bool)
    • +
  • stickers_emoji_cache_time - Specifies the validity period of the local cache of messages.getStickers, also relevant when generating the pagination hash when invoking the method. (int)
    • +
  • qr_login_camera - Whether the Settings->Devices menu should show an option to scan a QR login code (boolean)
    • +
  • qr_login_code - Whether the login screen should show a QR code login option, possibly as default login method (string, "disabled", "primary" or "secondary")
    • +
  • dialog_filters_enabled - Whether clients should show an option for managing dialog filters AKA folders (boolean)
    • +
  • dialog_filters_tooltip - Whether clients should actively show a tooltip, inviting the user to configure dialog filters AKA folders; typically this happens when the chat list is long enough to start getting cluttered. (boolean)
    • +
  • autoarchive_setting_available - Whether clients can invoke account.setGlobalPrivacySettings with globalPrivacySettings.archive_and_mute_new_noncontact_peers = boolTrue, to automatically archive and mute new incoming chats from non-contacts. (boolean)
    • +
  • pending_suggestions - Contains a list of suggestions that should be actively shown as a tooltip to the user. (Array of strings, possible values shown in the suggestions section ».
    • +
  • url_auth_domains - A list of domains that support automatic login with manual user confirmation, click here for more info on URL authorization ». (array of strings)
    • +
  • autologin_domains - A list of Telegram domains that support automatic login with no user confirmation, click here for more info on URL authorization ». (array of strings)
    • +
  • autologin_token - Autologin token, click here for more info on URL authorization ». (string)
    • +
  • round_video_encoding - Contains a set of recommended codec parameters for round videos.
    • +
  • chat_read_mark_size_threshold - Per-user read receipts, fetchable using messages.getMessageReadParticipants will be available in groups with less than chat_read_mark_size_threshold participants. (int)
    • +
  • chat_read_mark_expire_period - To protect user privacy, read receipts are only stored for chat_read_mark_expire_period seconds after the message was sent. (int)
    • +
+

Example value:

+
{
+    "test": 1,
+    "emojies_animated_zoom": 0.625,
+    "emojies_send_dice": [
+        "\ud83c\udfb2",
+        "\ud83c\udfaf",
+        "\ud83c\udfc0",
+        "\u26bd",
+        "\u26bd\ufe0f",
+        "\ud83c\udfb0",
+        "\ud83c\udfb3"
+    ],
+    "emojies_send_dice_success": {
+        "\ud83c\udfaf": {
+            "value": 6,
+            "frame_start": 62
+        },
+        "\ud83c\udfc0": {
+            "value": 5,
+            "frame_start": 110
+        },
+        "\u26bd": {
+            "value": 5,
+            "frame_start": 110
+        },
+        "\u26bd\ufe0f": {
+            "value": 5,
+            "frame_start": 110
+        },
+        "\ud83c\udfb0": {
+            "value": 64,
+            "frame_start": 110
+        },
+        "\ud83c\udfb3": {
+            "value": 6,
+            "frame_start": 110
+        }
+    },
+    "emojies_sounds": {
+        "\ud83c\udf83": {
+            "id": "4956223179606458539",
+            "access_hash": "-2107001400913062971",
+            "file_reference_base64": "AGFhvoKbftK5O9K9RpgN1ZtgSzWy"
+        },
+        "\u26b0": {
+            "id": "4956223179606458540",
+            "access_hash": "-1498869544183595185",
+            "file_reference_base64": "AGFhvoJIm8Uz0qSMIdm3AsKlK7wJ"
+        },
+        "\ud83e\udddf\u200d\u2642": {
+            "id": "4960929110848176331",
+            "access_hash": "3986395821757915468",
+            "file_reference_base64": "AGFhvoLtXSSIclmvfg6ePz3KsHQF"
+        },
+        "\ud83e\udddf": {
+            "id": "4960929110848176332",
+            "access_hash": "-8929417974289765626",
+            "file_reference_base64": "AGFhvoImaz5Umt4GvMUD5nocIu0W"
+        },
+        "\ud83e\udddf\u200d\u2640": {
+            "id": "4960929110848176333",
+            "access_hash": "9161696144162881753",
+            "file_reference_base64": "AGFhvoIm1QZsb48xlpRfh4Mq7EMG"
+        },
+        "\ud83c\udf51": {
+            "id": "4963180910661861548",
+            "access_hash": "-7431729439735063448",
+            "file_reference_base64": "AGFhvoKLrwl_WKr5LR0Jjs7o3RyT"
+        },
+        "\ud83c\udf8a": {
+            "id": "5094064004578410732",
+            "access_hash": "8518192996098758509",
+            "file_reference_base64": "AGFhvoKMNffRV2J3vKED0O6d8e42"
+        },
+        "\ud83c\udf84": {
+            "id": "5094064004578410733",
+            "access_hash": "-4142643820629256996",
+            "file_reference_base64": "AGFhvoJ1ulPBbXEURlTZWwJFx6xZ"
+        },
+        "\ud83e\uddbe": {
+            "id": "5094064004578410734",
+            "access_hash": "-8934384022571962340",
+            "file_reference_base64": "AGFhvoL4zdMRmYv9z3L8KPaX4JQL"
+        }
+    },
+    "gif_search_branding": "tenor",
+    "gif_search_emojies": [
+        "\ud83d\udc4d",
+        "\ud83d\ude18",
+        "\ud83d\ude0d",
+        "\ud83d\ude21",
+        "\ud83e\udd73",
+        "\ud83d\ude02",
+        "\ud83d\ude2e",
+        "\ud83d\ude44",
+        "\ud83d\ude0e",
+        "\ud83d\udc4e"
+    ],
+    "stickers_emoji_suggest_only_api": false,
+    "stickers_emoji_cache_time": 86400,
+    "qr_login_camera": false,
+    "qr_login_code": "disabled",
+    "dialog_filters_enabled": true,
+    "dialog_filters_tooltip": false,
+    "autoarchive_setting_available": false,
+    "pending_suggestions": [
+        "AUTOARCHIVE_POPULAR",
+        "VALIDATE_PASSWORD",
+        "VALIDATE_PHONE_NUMBER",
+        "NEWCOMER_TICKS"
+    ],
+    "autologin_token": "string",
+    "autologin_domains": [
+        "instantview.telegram.org",
+        "translations.telegram.org",
+        "contest.dev",
+        "contest.com",
+        "bugs.telegram.org",
+        "suggestions.telegram.org",
+        "themes.telegram.org"
+    ],
+    "url_auth_domains": [
+        "somedomain.telegram.org"
+    ],
+    "round_video_encoding": {
+        "diameter": 384,
+        "video_bitrate": 1000,
+        "audio_bitrate": 64,
+        "max_size": 12582912
+    },
+    "chat_read_mark_size_threshold": 50,
+    "chat_read_mark_expire_period": 604800
+}
+

Suggestions

+

The API can return a set of useful suggestions for users of graphical clients.

+

Basic suggestions

+
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;
+
+---functions---
+
+help.getAppConfig#98914110 = JSONValue;
+

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
+A full list of these parameters can be seen in the Client Configuration section », but we're mostly interested in the pending_suggestions and autoarchive_setting_available fields of the returned JSON object:

+ +

Channel suggestions

+
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.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;
+
+---functions---
+
+channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
+

Some channel/supergroup-related suggestions can also be contained in the pending_suggestions field of the channelFull constructor, returned by channels.getFullChannel.
+Here's a list of possible suggestions:

+ +

Dismissing suggestions

+
boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+---functions---
+
+help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
+

help.dismissSuggestion can be used to dismiss a suggestion.
+Pass inputPeerEmpty to peer for basic suggestions and the channel/supergroup's peer for channel suggestions.

+

App-specific configuration

+
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;
+
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
+
+help.inviteText#18cb9f78 message:string = help.InviteText;
+
+---functions---
+
+help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
+help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
+
+help.getInviteText#4d392343 = help.InviteText;
+
    +
  • help.getAppUpdate - Get info about an application update, can contain the updated application binary in the attached document
    • +
  • help.getAppChangelog - Get a list of service messages with app-specific changelogs
    • +
  • help.getInviteText - Returns a localized invitation message that can be sent via SMS to contacts that haven't signed up to Telegram yet
    • +
+

Terms of service

+
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
+help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
+
+help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
+
+auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
+
+---functions---
+
+help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
+help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
+
+auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
+
+account.deleteAccount#418d4e0b reason:string = Bool;
+

These methods can be used for managing consent to Telegram's Terms Of Service.

+

Typically, before a user signs up by invoking auth.signUp, apps should show a pop-up (if the popup flag of the help.termsOfService method is set), asking the user to accept Telegram's terms of service; in case of denial, the user is to be returned to the initial page of the login flow.

+

When signing up for the first time, the help.termsOfService is to be obtained from the auth.authorizationSignUpRequired constructor returned by the auth.signIn.

+

After signing up, or when logging in as an existing user, apps are supposed to call help.getTermsOfServiceUpdate to check for any updates to the Terms of Service; this call should be repeated after expires seconds have elapsed.
+If an update to the Terms Of Service is available, clients are supposed to show a consent popup; if accepted, clients should call help.acceptTermsOfService, providing the termsOfService id JSON object; in case of denial, clients are to delete the account using account.deleteAccount, providing Decline ToS update as deletion reason.

+

Example implementation: android (signup), android (after login)

+

Telegram support info

+
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;
+
+help.support#17c6b5f6 phone_number:string user:User = help.Support;
+help.supportName#8c05f1c9 name:string = help.SupportName;
+
+---functions---
+
+help.getSupport#9cdf08cd = help.Support;
+help.getSupportName#d360e72c = help.SupportName;
+

These methods can be used for fetching info about Telegram's support user, that users can use to get support and ask questions about the app.

+ +

Country information and login phone patterns

+
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;
+
+---functions---
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
+

help.getCountriesList can be used to fetch a list of localized names for all available countries and phone code patterns for logging in.

+

The phone code pattern should be used when showing the login screen, or when changing phone number: for example, a pattern value of XXX XXX XXX with country_code +39 indicates that the phone field for login should accept a spaced pattern like +39 123 456 789.
+Also, the beginning of the national part of the phone number (123 456 789) should match one of the prefixes, if any were returned.

+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + + + diff --git a/data/core.telegram.org/api/end-to-end.html b/data/core.telegram.org/api/end-to-end.html new file mode 100644 index 0000000000..40675ab00d --- /dev/null +++ b/data/core.telegram.org/api/end-to-end.html @@ -0,0 +1,244 @@ + + + + + End-to-End Encryption, Secret Chats + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+
+
+
+

End-to-End Encryption, Secret Chats

+ +
+ +
+

This article on MTProto's End-to-End encryption is meant for advanced users. +If you want to learn more about Secret Chats from a less intimidating source, kindly see our general FAQ.

+
+
+

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.

+
+
+
Related articles
+

+ +

+
+

Secret Chats are one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants. Note that the schema for these end-to-end encrypted Secret Chats is different from what is used for cloud chats:

+
+ +
+

A note on MTProto 2.0

+

This article describes the end-to-end encryption layer in the MTProto protocol version 2.0. +The principal differences from version 1.0 (described here for reference) are as follows:

+
    +
  • SHA-256 is used instead of SHA-1;
    • +
  • Padding bytes are involved in the computation of msg_key;
    • +
  • msg_key depends not only on the message to be encrypted, but on a portion of the secret chat key as well;
    • +
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
    • +
+

See also: MTProto 2.0: Cloud Chats, server-client encryption

+

Key Generation

+

Keys are generated using the Diffie-Hellman protocol.

+

Let us consider the following scenario: User A would like to initiate end-to-end encrypted communication with User B.

+

Sending a Request

+

User A executes messages.getDhConfig to obtain the Diffie-Hellman parameters: a prime p, and a high order element g.

+

Executing this method before each new key generation procedure is of vital importance. It makes sense to cache the values of the parameters together with the version in order to avoid having to receive all of the values every time. If the version stored on the client is still up-to-date, the server will return the constructor messages.dhConfigNotModified.

+

Client is expected to check whether p 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 to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

+

If the client needs additional entropy for the random number generator, it can pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. +Important: using the server’s random sequence in its raw form may be unsafe, it must be combined with a client sequence.

+

Client A computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and executes messages.requestEncryption after passing in g_a := pow(g, a) mod dh_prime.

+

User B receives the update updateEncryption for all associated authorization keys (all authorized devices) with the chat constructor encryptedChatRequested. The user must be shown basic information about User A and must be prompted to accept or reject the request.

+

Both clients are to check that g, g_a and g_b are greater than one and smaller than p-1. We recommend checking that g_a and g_b are between 2^{2048-64} and p - 2^{2048-64} as well.

+

Accepting a Request

+

After User B confirms the creation of a secret chat with A in the client interface, Client B also receives up-to-date configuration parameters for the Diffie-Hellman method. Thereafter, it generates a random 2048-bit number, b, using rules similar to those for a.

+

Having received g_a from the update with encryptedChatRequested, it can immediately generate the final shared key: key = (pow(g_a, b) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. Its fingerprint, key_fingerprint, is equal to the 64 last bits of SHA1 (key).

+

Note 1: in this particular case SHA1 is used here even for MTProto 2.0 secret chats.

+

Note 2: this fingerprint is used as a sanity check for the key exchange procedure to detect bugs when developing client software — it is not connected to the key visualization used on the clients as means of external authentication in secret chats. Key visualizations on the clients are generated using the first 128 bits of SHA1(initial key) followed by the first 160 bits of SHA256(key used when secret chat was updated to layer 46).

+

Client B executes messages.acceptEncryption after passing it g_b := pow(g, b) mod dh_prime and key_fingerprint.

+

For all of Client B’s authorized devices, except the current one, updateEncryption updates are sent with the constructor encryptedChatDiscarded. Thereafter, the only device that will be able to access the secret chat is Device B, which made the call to messages.acceptEncryption.

+

User A will be sent an updateEncryption update with the constructor encryptedChat, for the authorization key that initiated the chat.

+

With g_b from the update, Client A can also compute the shared key key = (pow(g_b, a) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. If the fingerprint for the received key is identical to the one that was passed to encryptedChat, incoming messages can be sent and processed. Otherwise, messages.discardEncryption must be executed and the user notified.

+

Perfect Forward Secrecy

+

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.

+
+

The re-keying protocol is further described in this article: Perfect Forward Secrecy in Secret Chats.

+
+

Please note that your client must support Forward Secrecy in Secret Chats to be compatible with official Telegram clients.

+

Sending and Receiving Messages in a Secret Chat

+

Serialization and Encryption of Outgoing Messages

+

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 46).

+
+

The TL-Schema for the contents of end-to-end encrypted messages is available here »

+
+

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is prepended by 4 bytes containing the array length not counting these 4 bytes.

+

The byte array is padded with 12 to 1024 random padding bytes to make its length divisible by 16 bytes. (In the older MTProto 1.0 encryption, only 0 to 15 padding bytes were used.)

+

Message key, msg_key, is computed as the 128 middle bits of the SHA256 of the data obtained in the previous step, prepended by 32 bytes from the shared key key. (For the older MTProto 1.0 encryption, msg_key was computed differently, as the 128 lower bits of SHA1 of the data obtained in the previous steps, excluding the padding bytes.)

+

For MTProto 2.0, the AES key aes_key and initialization vector aes_iv are computed ( key is the shared key obtained during Key Generation ) as follows:

+
    +
  • msg_key_large = SHA256 (substr (key, 88+x, 32) + plaintext + random_padding);
    • +
  • 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, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
    • +
+

For MTProto 2.0, x=0 for messages from the originator of the secret chat, x=8 for the messages in the opposite direction.

+

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

+

Data is encrypted with a 256-bit key, aes_key, and a 256-bit initialization vector, aes-iv, using AES-256 encryption with infinite garble extension (IGE). Encryption key fingerprint key_fingerprint and the message key msg_key are added at the top of the resulting byte array.

+

Encrypted data is embedded into a messages.sendEncrypted API call and passed to Telegram server for delivery to the other party of the Secret Chat.

+

Upgrading to MTProto 2.0 from MTProto 1.0

+

As soon as both parties in a secret chat are using at least Layer 73, they should only use MTProto 2.0 for all outgoing messages. Some of the first received messages may use MTProto 1.0, if a sufficiently high starting layer has not been negotiated during the creation of the secret chat. After the first message encrypted with MTProto 2.0 (or the first message with Layer 73 or higher) is received, all messages with higher sequence numbers must be encrypted with MTProto 2.0 as well.

+

As long as the current layer is lower than 73, each party should try to decrypt received messages with MTProto 1.0, and if this is not successfull (msg_key does not match), try MTProto 2.0. Once the first MTProto 2.0-encrypted message arrives (or the layer is upgraded to 73), there is no need to try MTProto 1.0 decryption for any of the further messages (unless the client is still waiting for some gaps to be closed).

+

Decrypting an Incoming Message

+

The steps above are performed in reverse order. +When an encrypted message is received, you must check that msg_key is in fact equal to the 128 middle bits of the SHA256 hash of the decrypted message, prepended by 32 bytes taken from the shared key. +If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

+

Sequence numbers

+

It is necessary to interpret all messages in their original order to protect against possible manipulations. Secret chats support a special mechanism for handling seq_no counters independently from the server.

+
+

Proper handling of these counters is further described in this article: Sequence numbers in Secret Chats.

+
+

Please note that your client must support sequence numbers in Secret Chats to be compatible with official Telegram clients.

+

Sending Encrypted Files

+

All files sent to secret chats are encrypted with one-time keys that are in no way related to the chat’s shared key. Before an encrypted file is sent, it is assumed that the encrypted file’s address will be attached to the outside of an encrypted message using the file parameter of the messages.sendEncryptedFile method and that the key for direct decryption will be sent in the body of the message (the key parameter in the constructors decryptedMessageMediaPhoto, decryptedMessageMediaVideo and decryptedMessageMediaFile.

+

Prior to a file being sent to a secret chat, 2 random 256-bit numbers are computed which will serve as the AES key and initialization vector used to encrypt the file. AES-256 encryption with infinite garble extension (IGE) is used in like manner.

+

The key fingerprint is computed as follows:

+
    +
  • digest = md5(key + iv)
    • +
  • fingerprint = substr(digest, 0, 4) XOR substr(digest, 4, 4)
    • +
+

The encrypted contents of a file are stored on the server in much the same way as those of a file in cloud chats: piece by piece using calls to upload.saveFilePart. +A subsequent call to messages.sendEncryptedFile will assign an identifier to the stored file and send the address together with the message. The recipient will receive an update with encryptedMessage, and the file parameter will contain file information.

+

Incoming and outgoing encrypted files can be forwarded to other secret chats using the constructor inputEncryptedFile to avoid saving the same content on the server twice.

+

Working with an Update Box

+

Secret chats are associated with specific devices (or rather with authorization keys), not users. A conventional message box, which uses pts to describe the client’s status, is not suitable, because it is designed for long-term message storage and message access from different devices.

+

An additional temporary message queue is introduced as a solution to this problem. When an update regarding a message from a secret chat is sent, a new value of qts is sent, which helps reconstruct the difference if there has been a long break in the connection or in case of loss of an update.

+

As the number of events increases, the value of qts increases by 1 with each new event. The initial value may not (and will not) be equal to 0.

+

The fact that events from the temporary queue have been received and stored by the client is acknowledged explicitly by a call to the messages.receivedQueue method or implicitly by a call to updates.getDifference (the value of qts passed, not the final state). All messages acknowledged as delivered by the client, as well as any messages older than 7 days, may (and will) be deleted from the server.

+

Upon de-authorization, the event queue of the corresponding device will be forcibly cleared, and the value of qts will become irrelevant.

+

Updating to new layers

+

Your client should always store the maximal layer that is known to be supported by the client on the other side of a secret chat. When the secret chat is first created, this value should be initialized to 46. This remote layer value must always be updated immediately after receiving any packet containing information of an upper layer, i.e.:

+
    +
  • any secret chat message containing layer_no in its decryptedMessageLayer with layer>=46, or
    • +
  • a decryptedMessageActionNotifyLayer service message, wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d).
    • +
+

Notifying the remote client about your local layer

+

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer.

+

There are two cases when your client must notify the remote client about its local layer:

+
    +
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
    2. +
  2. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 46 to Layer 47).
    3. +
+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + + + 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?

+
+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + diff --git a/data/core.telegram.org/api/pin.html b/data/core.telegram.org/api/pin.html new file mode 100644 index 0000000000..b5528f5a39 --- /dev/null +++ b/data/core.telegram.org/api/pin.html @@ -0,0 +1,149 @@ + + + + + Pinned messages + + + + + + + + + + + + + +
+
+
+
+ + +
+
+
+
+
+
+
+

Pinned messages

+ +
+ +

Telegram allows pinning multiple messages on top of a specific chat.

+
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;
+
+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;
+
+---functions---
+
+messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+
+messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
+channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
+

The messages.updatePinnedMessage method can be used to pin or unpin a specific message in an arbitrary chat.
+The unpin flags specifies whether to unpin or pin the message, and pm_oneside specifies whether the message should only be pinned on the local side of a one-to-one chat.

+

messages.unpinAllMessages can be used to unpin all messages in a chat.

+

When (un)pinning messages, a updatePinnedMessages or updatePinnedChannelMessages update will be emitted, containing IDs of pinned or unpinned messages.

+

Pinned messages will also have the will also have the pinned flag of message set.

+

Getting pinned messages

+
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;
+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;
+
+inputMessagesFilterPinned#1bb00451 = MessagesFilter;
+
+---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;
+

The pinned_msg_id of userFull, chatFull, channelFull contains the ID of only the latest pinned message.
+To obtain a full list, use messages.search with inputMessagesFilterPinned filter.

+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + + + diff --git a/data/core.telegram.org/api/stats.html b/data/core.telegram.org/api/stats.html deleted file mode 100644 index c9372acb5a..0000000000 --- a/data/core.telegram.org/api/stats.html +++ /dev/null @@ -1,297 +0,0 @@ - - - - - Channel statistics - - - - - - - - - - - - - -
-
-
-
- - -
-
-
-
-
-
-
-

Channel statistics

- -
- -

Telegram offers detailed channel statistics for channels and supergroups.

-

Channel statistics

-

Schema:

-
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;
-
----functions---
-
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getBroadcastStats to get detailed channel statistics.
-The returned stats.broadcastStats contains multiple statistics:

-
    -
  • Period-related statistics: a pair of values, one at the beginning and one at the end of the period in consideration (period).
    The period typically depends on channel activity.
      -
    • Absolute follower count (followers)
      • -
    • total_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).
      • -
    • total_sharecount/postcount, for posts posted during the period in consideration (shares_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).
      • -
    -
    • -
  • Percentage statistics
      -
    • Percentage of subscribers with enabled notifications (enabled_notifications)
      • -
    -
    • -
  • Graphs: graphs are described below ».
    • -
-

Supergroup statistics

-

Schema:

-
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
-statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
-statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
-
-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;
-

Administrators of supergroups of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMegagroupStats to get detailed supergroup statistics.
-The returned stats.broadcastStats contains multiple statistics, see the constructor page for more info ».

-

Message statistics

-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
----functions---
-
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMessageStats to get statistics of a specific message.
-The returned stats.messageStats contains the view graph of the message.

-

Graph visualization

-

There are four available visualizations for graph types:

- -

Graph modifiers (see various graphs for examples):

-
    -
  • y_scaled - Indicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph
    • -
  • percentage - Indicates whether value percentages should be shown in labels
    • -
  • stacked - Depending on the graph type, indicates stacking of multiple columns in the same graph
    • -
-

Graph syntax

-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Certain graphs are not directly sent in the stats.broadcastStats constructor to reduce server load: instead, those graphs will be sent as a statsGraphAsync constructor, and should be fetched separately using stats.loadAsyncGraph.

-

After obtaining the full statsGraph constructor, clients should parse the JSON graph object in the json field.

-

Object structure:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
KeyGraph title
columnsArray of all data column arrays in the chart. Each column array has its label at position 0, followed by values.
typesGraphs types for each of the column arrays (object, "label": "type"):
- line - line graph
- area - area graph
- step - step graph
- bar - bar graph
- x - x axis values for each of the charts at the corresponding positions, UNIX timestamps in milliseconds.
colorsColor for each type (object, "label": "colorKey#AAAAAA"; see chart colors).
namesLocalized name for each variable (object, "label": "Name")
subchartObject indicating the default zoom range for the graph, this is object's structure:
- show - Whether to use the specified zoom range (boolean)
- defaultZoom - An array with two x values, indicating the two ends of the default zoom range
y_scaledIndicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph (boolean, see various graphs for examples)
percentageIndicates whether value percentages should be shown in labels (boolean, see various graphs for examples)
stackedDepending on the graph type, indicates stacking of multiple columns in the same graph (boolean, see various graphs for examples)
- -

The following chart restrictions apply:

-
    -
  • Up to 50 columns on one graph must be supported.
    • -
  • Chart types are always the same for every column in the graph.
    • -
  • The bar chart type and stacked option are always used together.
    • -
  • percentage is always used with the area graph. - -
    • -
-

Chart zooming

-
statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Graphs that support zooming will contain a zoom_token in the statsGraph constructor.
-Said token should be then used as token in a new stats.loadAsyncGraph call triggered when the user clicks on the label, related to a certain x axis in the graph (see graph examples).
-The x coordinate of the label should be provided to the x parameter; the method will then return (if available) a more detailed subgraph.
-If not enough data is available, a localized statsGraphError will be returned.

-

Typical zoom visualization rules:

- -

Chart colors

-

Chart colors can be provided as a color key, followed by the primary color value in hex format:

-
red#e05356
-

The color key can be one of red, lightblue, lightgreen, golden, green, orange, blue, indigo.
-Apps can choose to use a color value specified by the currently loaded theme: for example, the android app uses statisticChartLine_* themekeys for each of the color keys, check out the assets directory for a bunch of default themes with various colors for channel statistics.

-

However, the server may also choose to return just a plain color value in hex format:

-
#e05356
-

In this case, the dark flag of the stats.getBroadcastStats method can be used to choose the palette of returned colors.

-

Graph examples

-

Line graph

-

Simple single line graph

-

Step graph

-

Step graph, always "stacked" (to indicate multiple lines)

-

Bar graph

-

Bar graph with multiple lines, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Area graph

-

Mixed bar/line graph, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Piechart

-

Piechart, typically obtained only when zooming into percentage graphs

- -
- -
-
-
-
-
-
Telegram
-
- Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
- -
-
About
- -
-
-
Mobile Apps
- -
-
-
Desktop Apps
- -
-
-
Platform
- -
-
-
-
-
About
-
-
-
Blog
-
-
-
Apps
-
-
-
Platform
-
-
-
Twitter
-
-
-
-
- - - - - - - - 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.

+ +
+ +
+
+
+
+
+
Telegram
+
+ Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
+ +
+
About
+ +
+
+
Mobile Apps
+ +
+
+
Desktop Apps
+ +
+
+
Platform
+ +
+
+
+
+
About
+
+
+
Blog
+
+
+
Apps
+
+
+
Platform
+
+
+
Twitter
+
+
+
+
+ + + + + + + + diff --git a/data/core.telegram.org/method/messages.sendBroadcast b/data/core.telegram.org/apple_privacy.html similarity index 68% rename from data/core.telegram.org/method/messages.sendBroadcast rename to data/core.telegram.org/apple_privacy.html index 5244109ad0..749930f957 100644 --- a/data/core.telegram.org/method/messages.sendBroadcast +++ b/data/core.telegram.org/apple_privacy.html @@ -2,12 +2,14 @@ - messages.sendBroadcast + Page moved - - + + - + @@ -26,7 +28,7 @@
  • Home
    • -
  • API
    • +
  • API
  • Protocol
  • Schema
    • @@ -36,40 +38,11 @@
    -
    -

    messages.sendBroadcast

    +
    +

    Page moved

    -

    Sends multiple messages to contacts.

    -

    {schema}

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    contactsVector<InputUser>List of user ID to whom a message will be sent
    messagestringMessage text
    mediaInputMediaMessage media-contents
    -

    Result

    -

    messages.StatedMessages

    +

    This is not the droid you're looking for.
    The page has been moved.

    +
    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. +
    2. Set up a webhook for incoming messages
      3. +
    3. Generate a random string of a sufficient length, e.g. $memcache_key = "vCH1vGWJxfSeofSAs0K5PA"
      4. +
    4. Put the value 123 with the key $memcache_key into Memcache for 3600 seconds (one hour)
      5. +
    5. Show our user the button https://t.me/ExampleComBot?start=vCH1vGWJxfSeofSAs0K5PA
      6. +
    6. 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.
      7. +
    7. 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.
      8. +
    +

    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 »

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/core.telegram.org/bots/api-changelog.html b/data/core.telegram.org/bots/api-changelog.html deleted file mode 100644 index c515fad459..0000000000 --- a/data/core.telegram.org/bots/api-changelog.html +++ /dev/null @@ -1,670 +0,0 @@ - - - - - Bot API changelog - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    Bot API changelog

    - -
    - -
    -

    The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
    To learn how to create and set up a bot, please consult our Introduction to Bots »

    -
    -

    You will find all changes to our Bot API on this page.

    -

    Recent changes

    -
    -

    Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

    -
    -

    January 31, 2022

    -

    Bot API 5.7

    - -

    December 30, 2021

    -

    Bot API 5.6

    - -

    December 7, 2021

    -

    Bot API 5.5

    -
      -
    • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
      • -
    • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
      • -
    • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
      • -
    • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
      • -
    • Added the field has_protected_content to the classes Chat and Message.
      • -
    • Added the field is_automatic_forward to the class Message.
      • -
    -

    Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

    -

    Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

    -

    Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

    -

    November 5, 2021

    -

    Bot API 5.4

    - -
    -
    -

    ⚠️ WARNING! ⚠️
    User identifiers will become bigger than 2^31 - 1 before the end of this year and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

    -
    -
    -

    June 25, 2021

    -

    Bot API 5.3

    -

    Personalized Commands

    -
      -
    • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
      • -
    • Added the class BotCommandScope, describing the scope to which bot commands apply.
      • -
    • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
      • -
    • Added the parameters scope and language_code to the method getMyCommands.
      • -
    • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
      • -
    • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
      • -
    -

    Custom Placeholders

    - -

    And More

    -
      -
    • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
      • -
    • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
      • -
    • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
      • -
    • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
      • -
    -
    -
    -

    ⚠️ WARNING! ⚠️
    After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

    -
    -
    -

    April 26, 2021

    -

    Bot API 5.2

    -
      -
    • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
      • -
    • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
      • -
    • Allowed sending invoices to group, supergroup and channel chats.
      • -
    • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
      • -
    • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
      • -
    • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
      • -
    • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
      • -
    • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
      • -
    -
    -
    -

    ⚠️ WARNING! ⚠️
    After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

    -
    -
    -
    -

    ⚠️ WARNING! ⚠️
    Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

    -
    -
    -
    -

    ⚠️ WARNING! ⚠️
    After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

    -
    -
    -

    March 9, 2021

    -

    Bot API 5.1

    -

    Added two new update types

    -
      -
    • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
      • -
    -

    Improved Invite Links

    -
      -
    • Added the class ChatInviteLink, representing an invite link to a chat.
      • -
    • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
      • -
    • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
      • -
    • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
      • -
    -

    Voice Chat Info

    - -

    And More

    -
      -
    • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
      • -
    • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
      • -
    • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
      • -
    • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
      • -
    -
    -
    -

    ⚠️ WARNING! ⚠️
    After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

    -
    -
    -

    November 4, 2020

    -

    Introducing Bot API 5.0

    -

    Run Your Own Bot API Server

    -
      -
    • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
      • -
    • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
      • -
    • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
      • -
    -

    Transfer Bot Ownership

    -
      -
    • You can now use @BotFather to transfer your existing bots to another Telegram account.
      • -
    -

    Webhooks

    -
      -
    • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
      • -
    • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
      • -
    • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
      • -
    -

    Working with Groups

    -
      -
    • The getChat request now returns the user's bio for private chats if available.
      • -
    • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
      • -
    • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
      • -
    • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
      • -
    -

    Working with Files

    -
      -
    • Added the field file_name to the classes Audio and Video, containing the name of the original file.
      • -
    • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
      • -
    -

    Multiple Pinned Messages

    -
      -
    • Added the ability to pin messages in private chats.
      • -
    • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
      • -
    • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
      • -
    -

    File Albums

    -
      -
    • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
      • -
    -

    Live Locations

    - -

    Anonymous Admins

    -
      -
    • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
      • -
    • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
      • -
    • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
      • -
    • Added the custom title of an anonymous message sender to the class Message as author_signature.
      • -
    -

    And More

    - -

    And Last but not Least

    -
      -
    • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
      • -
    -

    June 4, 2020

    -

    Bot API 4.9

    -
      -
    • Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
      • -
    • Supported video thumbnails for inline GIF and MPEG4 animations.
      • -
    • Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
      • -
    -

    April 24, 2020

    -

    Bot API 4.8

    -
      -
    • Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll.
      • -
    • Added the fields explanation and explanation_entities to the Poll object.
      • -
    • Supported timed polls that automatically close at a certain date and time. Set up by specifying the parameter open_period or close_date in the method sendPoll.
      • -
    • Added the fields open_period and close_date to the Poll object.
      • -
    • Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
      • -
    • Added the field emoji to the Dice object.
      • -
    -

    March 30, 2020

    -

    Bot API 4.7

    -
      -
    • Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
      • -
    • Added the field dice to the Message object.
      • -
    • Added the method getMyCommands for getting the current list of the bot's commands.
      • -
    • Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
      • -
    • Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
      • -
    • Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
      • -
    • Added the field thumb to the StickerSet object.
      • -
    • Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
      • -
    -

    January 23, 2020

    -

    Bot API 4.6

    -
      -
    • Supported Polls 2.0.
      • -
    • Added the ability to send non-anonymous, multiple answer, and quiz-style polls: added the parameters is_anonymous, type, allows_multiple_answers, correct_option_id, is_closed options to the method sendPoll.
      • -
    • Added the object KeyboardButtonPollType and the field request_poll to the object KeyboardButton.
      • -
    • Added updates about changes of user answers in non-anonymous polls, represented by the object PollAnswer and the field poll_answer in the Update object.
      • -
    • Added the fields total_voter_count, is_anonymous, type, allows_multiple_answers, correct_option_id to the Poll object.
      • -
    • Bots can now send polls to private chats.
      • -
    • Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
      • -
    • Added the optional field language to the MessageEntity object.
      • -
    -

    December 31, 2019

    -

    Bot API 4.5

    -
      -
    • Added support for two new MessageEntity types, underline and strikethrough.
      • -
    • Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
      • -
    • Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
      • -
    • Added a new parse mode, MarkdownV2, which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
      • -
    • Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
      • -
    • Added the field custom_title to the ChatMember object.
      • -
    • Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
      • -
    • Added the field slow_mode_delay to the Chat object.
      • -
    -

    July 29, 2019

    -

    Bot API 4.4

    -
      -
    • Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker.
      • -
    • Added support for default permissions in groups. New object ChatPermissions, containing actions which a member can take in a chat. New field permissions in the Chat object; new method setChatPermissions.
      • -
    • The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
      • -
    • Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
      • -
    • The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility.
      • -
    • Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
      • -
    • Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
      • -
    • File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
      • -
    • All webhook requests from the Bot API are now coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
      • -
    • As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
      • -
    -

    May 31, 2019

    -

    Bot API 4.3

    -
      -
    • Added support for Seamless Telegram Login on external websites.
      • -
    • Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
      • -
    -
    - TITLE -
    - -

    Also in this update:

    -
      -
    • Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
      • -
    • If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
      • -
    • Bots now receive the edited_message Update even if only Message.reply_markup has changed.
      • -
    • Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
      • -
    • Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
      • -
    -

    April 14, 2019

    -

    Bot API 4.2

    -
      -
    • Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
      • -
    • The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
      • -
    • Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
      • -
    • Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
      • -
    • Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
      • -
    • Starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
      • -
    • Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
      • -
    -

    August 27, 2018

    -

    Bot API 4.1

    - -

    July 26, 2018

    -

    Bot API 4.0.

    -
      -
    • Added support for Telegram Passport. See the official announcement on the blog and the manual for details.
      • -
    • Added support for editing the media content of messages: added the method editMessageMedia and new types InputMediaAnimation, InputMediaAudio, and InputMediaDocument.
      • -
    • Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.
      • -
    • Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.
      • -
    • tg:// URLs now can be used in inline keyboard url buttons and text_link message entities.
      • -
    • Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height.
      • -
    • Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
      • -
    • Added two new MessageEntity types: cashtag and phone_number.
      • -
    • Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method.
      • -
    • You can now create inline mentions of users, who have pressed your bot's callback buttons.
      • -
    • You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
      • -
    • If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
      • -
    • Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
      • -
    -

    February 13, 2018

    -

    Bot API 3.6.

    -
      -
    • Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption.
      • -
    • In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
      • -
    • Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
      • -
    • Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
      • -
    -

    November 17, 2017

    -

    Bot API 3.5.

    - -

    October 11, 2017

    -

    Bot API 3.4.

    - -

    August 23, 2017

    -

    Bot API 3.3.

    -
      -
    • Bots can now mention users via inline mentions, without using usernames.
      • -
    • getChat now also returns pinned messages in supergroups, if present. Added the new field pinned_message to the Chat object.
      • -
    • Added the new fields author_signature and forward_signature to the Message object.
      • -
    • Added the new field is_bot to the User object.
      • -
    -

    July 21, 2017

    -

    Bot API 3.2. Teach your bot to handle stickers and sticker sets.

    - -

    June 30, 2017

    -

    Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:

    - -

    May 18, 2017

    -

    Introducing Bot API 3.0.

    -

    NEW Payment Platform

    -

    See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.

    - -

    NEW Video Messages

    -
      -
    • As of Telegram v.4.0, users can send short rounded video messages, using an interface similar to that of voice notes.
      • -
    • Added the sendVideoNote method, the new field video_note to Message, the fields record_video_note or upload_video_note to sendChatAction.
      • -
    -

    NEW Multilingual Bots

    -
      -
    • The User object now may have a language_code field that contains the IETF language tag of the user's language.
      • -
    • Thanks to this, your bot can now offer localized responses to users that speak different languages.
      • -
    -

    More power to admin bots

    -
      -
    • unbanChatMemeber now also works in channels!
      • -
    • New method deleteMessage that allows the bot to delete its own messages, as well as messages posted by other in groups and channels where the bot is an administrator.
      • -
    -

    Minor Changes

    -
      -
    • Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
      • -
    • Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
      • -
    • New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
      • -
    -

    December 4, 2016

    -

    Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.

    -
      -
    • Use the new field max_connections in setWebhook to optimize your bot's server load
      • -
    • Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
      • -
    • deleteWebhook moved out of setWebhook to get a whole separate method for itself.
      • -
    -

    November 21, 2016

    -

    Bot API 2.3

    -
      -
    • Modified bot privacy mode for the sake of consistency.
      • -

    • Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.

      -
      • -

    • You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.

      -
      • -
    • Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
      • -
    • The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
      • -
    • Added the new field forward_from_message_id to Message.
      • -
    • Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
      • -
    • Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
      • -
    -

    October 3, 2016

    -

    Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
    If you're not a developer, you may like this user-friendly blog post better.

    - -

    Other changes

    - -
      -
    • New field all_members_are_administrators in the Chat object.
      • -
    • Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
      • -
    -

    May 25, 2016

    - -

    May 22, 2016

    - -

    May 12, 2016

    - -

    May 6, 2016

    -
      -
    • Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
      • -
    • Added the field forward_from_chat to the Message object for messages forwarded from channels.
      • -
    -

    April 9, 2016

    -

    Introducing Bot API 2.0. Check out this page for a review of this major update.

    - -

    Inline bots

    -
      -
    • Added support for all content types available on Telegram. 19 types of InlineQueryResult objects are now supported.
      • -
    • Inline bots can now substitute all kinds of content with text. Added 4 types of InputMessageContent objects.
      • -
    • Your inline bot can also ask users for permission to use their location. Added the new Botfather command /setinlinegeo, added field location to the InlineQuery object, added fields location and inline_message_id to the ChosenInlineResult object.
      • -
    • Added an easy way to switch between inline mode and a private chat with the bot – useful for settings, establishing external connections and teaching users how to use your bot in inline mode. Added parameters switch_pm_text and switch_pm_parameter to the method answerInlineQuery.
      • -
    -

    Miscellaneous

    - -

    February 20, 2016

    -
      -
    • Added the disable_notification parameter to all methods that send messages or any kind.
      • -
    • Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
      • -
    -

    January 20, 2016

    -
      -
    • By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
      • -
    -

    January 14, 2016

    -
      -
    • You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object.
      • -
    -

    January 4, 2016

    - -

    November, 2015

    -
      -
    • Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
      • -
    • New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
      • -
    -

    October 8, 2015

    -
      -
    • Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
      • -
    • The Chat field in the Message is now of the new type Chat.
      • -
    • You can now pass a channel username (in the format @channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
      • -
    -

    September 18, 2015

    -
      -
    • Bots can now download files and media sent by users.
      • -
    • Added getFile and File.
      • -
    -

    September 7, 2015

    -
      -
    • You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
      • -
    • Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
      • -
    -

    August 29, 2015

    -
      -
    • Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
      • -
    • You can now make new requests when responding to webhook updates.
      • -
    -

    August 15, 2015

    -
      -
    • Added new type Voice and new method sendVoice for sending voice messages.
      • -
    • Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
      • -
    • Added optional fields performer, title to the Audio object and sendAudio method.
      • -
    • Added optional field voice to the Message object.
      • -
    -

    July 2015

    -
      -
    • The thumb field is now optional for Video, Sticker and Document objects
      • -
    • The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
      • -
    • caption and duration optional fields have been added to the sendVideo method.
      • -
    • Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
      • -
    -

    June 24, 2015

    -

    The bot platform was officially launched.

    -
    -

    Back to the Bot API Manual »

    -
    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - - - diff --git a/data/core.telegram.org/bots/api.html b/data/core.telegram.org/bots/api.html new file mode 100644 index 0000000000..b80cdfcfc8 --- /dev/null +++ b/data/core.telegram.org/bots/api.html @@ -0,0 +1,9488 @@ + + + + + Telegram Bot API + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Telegram Bot API

    + +
    + +
    +

    The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
    To learn how to create and set up a bot, please consult our Introduction to Bots and Bot FAQ.

    +
    +

    Recent changes

    +
    +

    Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

    +
    +

    January 31, 2022

    +

    Bot API 5.7

    + +

    December 30, 2021

    +

    Bot API 5.6

    + +

    December 7, 2021

    +

    Bot API 5.5

    +
      +
    • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
      • +
    • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
      • +
    • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
      • +
    • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
      • +
    • Added the field has_protected_content to the classes Chat and Message.
      • +
    • Added the field is_automatic_forward to the class Message.
      • +
    +

    Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

    +

    Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

    +

    Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

    +

    November 5, 2021

    +

    Bot API 5.4

    + +

    See earlier changes »

    +

    Authorizing your bot

    +

    Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

    +

    Making requests

    +

    All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:

    +
    https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe
    +

    We support GET and POST HTTP methods. We support four ways of passing parameters in Bot API requests:

    +
      +
    • URL query string
      • +
    • application/x-www-form-urlencoded
      • +
    • application/json (except for uploading files)
      • +
    • multipart/form-data (use to upload files)
      • +
    +

    The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals True, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

    +
      +
    • All methods in the Bot API are case-insensitive.
      • +
    • All queries must be made using UTF-8.
      • +
    +

    Making requests when getting updates

    +

    If you're using webhooks, you can perform a request to the Bot API while sending an answer to the webhook. Use either application/json or application/x-www-form-urlencoded or multipart/form-data response content type for passing parameters. Specify the method to be invoked in the method parameter of the request. It's not possible to know that such a request was successful or get its result.

    +
    +

    Please see our FAQ for examples.

    +
    +

    Using a Local Bot API Server

    +

    The Bot API server source code is available at telegram-bot-api. You can run it locally and send the requests to your own server instead of https://api.telegram.org. If you switch to a local Bot API server, your bot will be able to:

    +
      +
    • Download files without a size limit.
      • +
    • Upload files up to 2000 MB.
      • +
    • Upload files using their local path and the file URI scheme.
      • +
    • Use an HTTP URL for the webhook.
      • +
    • Use any local IP address for the webhook.
      • +
    • Use any port for the webhook.
      • +
    • Set max_webhook_connections up to 100000.
      • +
    • Receive the absolute local path as a value of the file_path field without the need to download the file after a getFile request.
      • +
    +

    Do I need a Local Bot API Server

    +

    The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of these features, you're welcome to switch to your own at any time.

    +

    Getting updates

    +

    There are two mutually exclusive ways of receiving updates for your bot — the getUpdates method on one hand and Webhooks on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.

    +

    Regardless of which option you choose, you will receive JSON-serialized Update objects as a result.

    +

    Update

    +

    This object represents an incoming update.
    At most one of the optional parameters can be present in any given update.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    update_idIntegerThe update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
    messageMessageOptional. New incoming message of any kind — text, photo, sticker, etc.
    edited_messageMessageOptional. New version of a message that is known to the bot and was edited
    channel_postMessageOptional. New incoming channel post of any kind — text, photo, sticker, etc.
    edited_channel_postMessageOptional. New version of a channel post that is known to the bot and was edited
    inline_queryInlineQueryOptional. New incoming inline query
    chosen_inline_resultChosenInlineResultOptional. 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.
    callback_queryCallbackQueryOptional. New incoming callback query
    shipping_queryShippingQueryOptional. New incoming shipping query. Only for invoices with flexible price
    pre_checkout_queryPreCheckoutQueryOptional. New incoming pre-checkout query. Contains full information about checkout
    pollPollOptional. New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot
    poll_answerPollAnswerOptional. A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.
    my_chat_memberChatMemberUpdatedOptional. The bot's chat member status was updated in a chat. For private chats, this update is received only when the bot is blocked or unblocked by the user.
    chat_memberChatMemberUpdatedOptional. A chat member's status was updated in a chat. The bot must be an administrator in the chat and must explicitly specify “chat_member” in the list of allowed_updates to receive these updates.
    chat_join_requestChatJoinRequestOptional. A request to join the chat has been sent. The bot must have the can_invite_users administrator right in the chat to receive these updates.
    +

    getUpdates

    +

    Use this method to receive incoming updates using long polling (wiki). An Array of Update objects is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    offsetIntegerOptionalIdentifier of the first update to be returned. Must be greater by one than the highest among the identifiers of previously received updates. By default, updates starting with the earliest unconfirmed update are returned. An update is considered confirmed as soon as getUpdates is called with an offset higher than its update_id. The negative offset can be specified to retrieve updates starting from -offset update from the end of the updates queue. All previous updates will forgotten.
    limitIntegerOptionalLimits the number of updates to be retrieved. Values between 1-100 are accepted. Defaults to 100.
    timeoutIntegerOptionalTimeout in seconds for long polling. Defaults to 0, i.e. usual short polling. Should be positive, short polling should be used for testing purposes only.
    allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.

    Please note that this parameter doesn't affect updates created before the call to the getUpdates, so unwanted updates may be received for a short period of time.
    +
    +

    Notes
    1. This method will not work if an outgoing webhook is set up.
    2. In order to avoid getting duplicate updates, recalculate offset after each server response.

    +
    +

    setWebhook

    +

    Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success.

    +

    If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot's token, you can be pretty sure it's us.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    urlStringYesHTTPS url to send updates to. Use an empty string to remove webhook integration
    certificateInputFileOptionalUpload your public key certificate so that the root certificate in use can be checked. See our self-signed guide for details.
    ip_addressStringOptionalThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
    max_connectionsIntegerOptionalMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
    allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.
    Please note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
    drop_pending_updatesBooleanOptionalPass True to drop all pending updates
    +
    +

    Notes
    1. You will not be able to receive updates using getUpdates for as long as an outgoing webhook is set up.
    2. To use a self-signed certificate, you need to upload your public key certificate using certificate parameter. Please upload as InputFile, sending a String will not work.
    3. Ports currently supported for Webhooks: 443, 80, 88, 8443.

    +

    NEW! If you're having any trouble setting up webhooks, please check out this amazing guide to Webhooks.

    +
    +

    deleteWebhook

    +

    Use this method to remove webhook integration if you decide to switch back to getUpdates. Returns True on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    drop_pending_updatesBooleanOptionalPass True to drop all pending updates
    +

    getWebhookInfo

    +

    Use this method to get current webhook status. Requires no parameters. On success, returns a WebhookInfo object. If the bot is using getUpdates, will return an object with the url field empty.

    +

    WebhookInfo

    +

    Contains information about the current status of a webhook.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    urlStringWebhook URL, may be empty if webhook is not set up
    has_custom_certificateBooleanTrue, if a custom certificate was provided for webhook certificate checks
    pending_update_countIntegerNumber of updates awaiting delivery
    ip_addressStringOptional. Currently used webhook IP address
    last_error_dateIntegerOptional. Unix time for the most recent error that happened when trying to deliver an update via webhook
    last_error_messageStringOptional. Error message in human-readable format for the most recent error that happened when trying to deliver an update via webhook
    max_connectionsIntegerOptional. Maximum allowed number of simultaneous HTTPS connections to the webhook for update delivery
    allowed_updatesArray of StringOptional. A list of update types the bot is subscribed to. Defaults to all update types except chat_member
    +

    Available types

    +

    All types used in the Bot API responses are represented as JSON-objects.

    +

    It is safe to use 32-bit signed integers for storing all Integer fields unless otherwise noted.

    +
    +

    Optional fields may be not returned when irrelevant.

    +
    +

    User

    +

    This object represents a Telegram user or bot.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idIntegerUnique identifier for this user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
    is_botBooleanTrue, if this user is a bot
    first_nameStringUser's or bot's first name
    last_nameStringOptional. User's or bot's last name
    usernameStringOptional. User's or bot's username
    language_codeStringOptional. IETF language tag of the user's language
    can_join_groupsBooleanOptional. True, if the bot can be invited to groups. Returned only in getMe.
    can_read_all_group_messagesBooleanOptional. True, if privacy mode is disabled for the bot. Returned only in getMe.
    supports_inline_queriesBooleanOptional. True, if the bot supports inline queries. Returned only in getMe.
    +

    Chat

    +

    This object represents a chat.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idIntegerUnique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
    typeStringType of chat, can be either “private”, “group”, “supergroup” or “channel”
    titleStringOptional. Title, for supergroups, channels and group chats
    usernameStringOptional. Username, for private chats, supergroups and channels if available
    first_nameStringOptional. First name of the other party in a private chat
    last_nameStringOptional. Last name of the other party in a private chat
    photoChatPhotoOptional. Chat photo. Returned only in getChat.
    bioStringOptional. Bio of the other party in a private chat. Returned only in getChat.
    has_private_forwardsTrueOptional. True, if privacy settings of the other party in the private chat allows to use tg://user?id=<user_id> links only in chats with the user. Returned only in getChat.
    descriptionStringOptional. Description, for groups, supergroups and channel chats. Returned only in getChat.
    invite_linkStringOptional. Primary invite link, for groups, supergroups and channel chats. Returned only in getChat.
    pinned_messageMessageOptional. The most recent pinned message (by sending date). Returned only in getChat.
    permissionsChatPermissionsOptional. Default chat member permissions, for groups and supergroups. Returned only in getChat.
    slow_mode_delayIntegerOptional. For supergroups, the minimum allowed delay between consecutive messages sent by each unpriviledged user; in seconds. Returned only in getChat.
    message_auto_delete_timeIntegerOptional. The time after which all messages sent to the chat will be automatically deleted; in seconds. Returned only in getChat.
    has_protected_contentTrueOptional. True, if messages from the chat can't be forwarded to other chats. Returned only in getChat.
    sticker_set_nameStringOptional. For supergroups, name of group sticker set. Returned only in getChat.
    can_set_sticker_setTrueOptional. True, if the bot can change the group sticker set. Returned only in getChat.
    linked_chat_idIntegerOptional. Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats. This identifier may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier. Returned only in getChat.
    locationChatLocationOptional. For supergroups, the location to which the supergroup is connected. Returned only in getChat.
    +

    Message

    +

    This object represents a message.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    message_idIntegerUnique message identifier inside this chat
    fromUserOptional. Sender of the message; empty for messages sent to channels. For backward compatibility, the field contains a fake sender user in non-channel chats, if the message was sent on behalf of a chat.
    sender_chatChatOptional. Sender of the message, sent on behalf of a chat. For example, the channel itself for channel posts, the supergroup itself for messages from anonymous group administrators, the linked channel for messages automatically forwarded to the discussion group. For backward compatibility, the field from contains a fake sender user in non-channel chats, if the message was sent on behalf of a chat.
    dateIntegerDate the message was sent in Unix time
    chatChatConversation the message belongs to
    forward_fromUserOptional. For forwarded messages, sender of the original message
    forward_from_chatChatOptional. For messages forwarded from channels or from anonymous administrators, information about the original sender chat
    forward_from_message_idIntegerOptional. For messages forwarded from channels, identifier of the original message in the channel
    forward_signatureStringOptional. For forwarded messages that were originally sent in channels or by an anonymous chat administrator, signature of the message sender if present
    forward_sender_nameStringOptional. Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
    forward_dateIntegerOptional. For forwarded messages, date the original message was sent in Unix time
    is_automatic_forwardTrueOptional. True, if the message is a channel post that was automatically forwarded to the connected discussion group
    reply_to_messageMessageOptional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
    via_botUserOptional. Bot through which the message was sent
    edit_dateIntegerOptional. Date the message was last edited in Unix time
    has_protected_contentTrueOptional. True, if the message can't be forwarded
    media_group_idStringOptional. The unique identifier of a media message group this message belongs to
    author_signatureStringOptional. Signature of the post author for messages in channels, or the custom title of an anonymous group administrator
    textStringOptional. For text messages, the actual UTF-8 text of the message, 0-4096 characters
    entitiesArray of MessageEntityOptional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
    animationAnimationOptional. Message is an animation, information about the animation. For backward compatibility, when this field is set, the document field will also be set
    audioAudioOptional. Message is an audio file, information about the file
    documentDocumentOptional. Message is a general file, information about the file
    photoArray of PhotoSizeOptional. Message is a photo, available sizes of the photo
    stickerStickerOptional. Message is a sticker, information about the sticker
    videoVideoOptional. Message is a video, information about the video
    video_noteVideoNoteOptional. Message is a video note, information about the video message
    voiceVoiceOptional. Message is a voice message, information about the file
    captionStringOptional. Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
    caption_entitiesArray of MessageEntityOptional. For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
    contactContactOptional. Message is a shared contact, information about the contact
    diceDiceOptional. Message is a dice with random value
    gameGameOptional. Message is a game, information about the game. More about games »
    pollPollOptional. Message is a native poll, information about the poll
    venueVenueOptional. Message is a venue, information about the venue. For backward compatibility, when this field is set, the location field will also be set
    locationLocationOptional. Message is a shared location, information about the location
    new_chat_membersArray of UserOptional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
    left_chat_memberUserOptional. A member was removed from the group, information about them (this member may be the bot itself)
    new_chat_titleStringOptional. A chat title was changed to this value
    new_chat_photoArray of PhotoSizeOptional. A chat photo was change to this value
    delete_chat_photoTrueOptional. Service message: the chat photo was deleted
    group_chat_createdTrueOptional. Service message: the group has been created
    supergroup_chat_createdTrueOptional. Service message: the supergroup has been created. This field can't be received in a message coming through updates, because bot can't be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
    channel_chat_createdTrueOptional. Service message: the channel has been created. This field can't be received in a message coming through updates, because bot can't be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
    message_auto_delete_timer_changedMessageAutoDeleteTimerChangedOptional. Service message: auto-delete timer settings changed in the chat
    migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
    migrate_from_chat_idIntegerOptional. The supergroup has been migrated from a group with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
    pinned_messageMessageOptional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
    invoiceInvoiceOptional. Message is an invoice for a payment, information about the invoice. More about payments »
    successful_paymentSuccessfulPaymentOptional. Message is a service message about a successful payment, information about the payment. More about payments »
    connected_websiteStringOptional. The domain name of the website on which the user has logged in. More about Telegram Login »
    passport_dataPassportDataOptional. Telegram Passport data
    proximity_alert_triggeredProximityAlertTriggeredOptional. Service message. A user in the chat triggered another user's proximity alert while sharing Live Location.
    voice_chat_scheduledVoiceChatScheduledOptional. Service message: voice chat scheduled
    voice_chat_startedVoiceChatStartedOptional. Service message: voice chat started
    voice_chat_endedVoiceChatEndedOptional. Service message: voice chat ended
    voice_chat_participants_invitedVoiceChatParticipantsInvitedOptional. Service message: new participants invited to a voice chat
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
    +

    MessageId

    +

    This object represents a unique message identifier.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    message_idIntegerUnique message identifier
    +

    MessageEntity

    +

    This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the entity. Currently, can be “mention” (@username), “hashtag” (#hashtag), “cashtag” ($USD), “bot_command” (/start@jobs_bot), “url” (https://telegram.org), “email” (do-not-reply@telegram.org), “phone_number” (+1-212-555-0123), “bold” (bold text), “italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text), “spoiler” (spoiler message), “code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs), “text_mention” (for users without usernames)
    offsetIntegerOffset in UTF-16 code units to the start of the entity
    lengthIntegerLength of the entity in UTF-16 code units
    urlStringOptional. For “text_link” only, url that will be opened after user taps on the text
    userUserOptional. For “text_mention” only, the mentioned user
    languageStringOptional. For “pre” only, the programming language of the entity text
    +

    PhotoSize

    +

    This object represents one size of a photo or a file / sticker thumbnail.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    widthIntegerPhoto width
    heightIntegerPhoto height
    file_sizeIntegerOptional. File size in bytes
    +

    Animation

    +

    This object represents an animation file (GIF or H.264/MPEG-4 AVC video without sound).

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    widthIntegerVideo width as defined by sender
    heightIntegerVideo height as defined by sender
    durationIntegerDuration of the video in seconds as defined by sender
    thumbPhotoSizeOptional. Animation thumbnail as defined by sender
    file_nameStringOptional. Original animation filename as defined by sender
    mime_typeStringOptional. MIME type of the file as defined by sender
    file_sizeIntegerOptional. File size in bytes
    +

    Audio

    +

    This object represents an audio file to be treated as music by the Telegram clients.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    durationIntegerDuration of the audio in seconds as defined by sender
    performerStringOptional. Performer of the audio as defined by sender or by audio tags
    titleStringOptional. Title of the audio as defined by sender or by audio tags
    file_nameStringOptional. Original filename as defined by sender
    mime_typeStringOptional. MIME type of the file as defined by sender
    file_sizeIntegerOptional. File size in bytes
    thumbPhotoSizeOptional. Thumbnail of the album cover to which the music file belongs
    +

    Document

    +

    This object represents a general file (as opposed to photos, voice messages and audio files).

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    thumbPhotoSizeOptional. Document thumbnail as defined by sender
    file_nameStringOptional. Original filename as defined by sender
    mime_typeStringOptional. MIME type of the file as defined by sender
    file_sizeIntegerOptional. File size in bytes
    +

    Video

    +

    This object represents a video file.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    widthIntegerVideo width as defined by sender
    heightIntegerVideo height as defined by sender
    durationIntegerDuration of the video in seconds as defined by sender
    thumbPhotoSizeOptional. Video thumbnail
    file_nameStringOptional. Original filename as defined by sender
    mime_typeStringOptional. Mime type of a file as defined by sender
    file_sizeIntegerOptional. File size in bytes
    +

    VideoNote

    +

    This object represents a video message (available in Telegram apps as of v.4.0).

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    lengthIntegerVideo width and height (diameter of the video message) as defined by sender
    durationIntegerDuration of the video in seconds as defined by sender
    thumbPhotoSizeOptional. Video thumbnail
    file_sizeIntegerOptional. File size in bytes
    +

    Voice

    +

    This object represents a voice note.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    durationIntegerDuration of the audio in seconds as defined by sender
    mime_typeStringOptional. MIME type of the file as defined by sender
    file_sizeIntegerOptional. File size in bytes
    +

    Contact

    +

    This object represents a phone contact.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    phone_numberStringContact's phone number
    first_nameStringContact's first name
    last_nameStringOptional. Contact's last name
    user_idIntegerOptional. Contact's user identifier in Telegram. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
    vcardStringOptional. Additional data about the contact in the form of a vCard
    +

    Dice

    +

    This object represents an animated emoji that displays a random value.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    emojiStringEmoji on which the dice throw animation is based
    valueIntegerValue of the dice, 1-6 for “🎲”, “🎯” and “🎳” base emoji, 1-5 for “🏀” and “⚽” base emoji, 1-64 for “🎰” base emoji
    +

    PollOption

    +

    This object contains information about one answer option in a poll.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    textStringOption text, 1-100 characters
    voter_countIntegerNumber of users that voted for this option
    +

    PollAnswer

    +

    This object represents an answer of a user in a non-anonymous poll.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    poll_idStringUnique poll identifier
    userUserThe user, who changed the answer to the poll
    option_idsArray of Integer0-based identifiers of answer options, chosen by the user. May be empty if the user retracted their vote.
    +

    Poll

    +

    This object contains information about a poll.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idStringUnique poll identifier
    questionStringPoll question, 1-300 characters
    optionsArray of PollOptionList of poll options
    total_voter_countIntegerTotal number of users that voted in the poll
    is_closedBooleanTrue, if the poll is closed
    is_anonymousBooleanTrue, if the poll is anonymous
    typeStringPoll type, currently can be “regular” or “quiz”
    allows_multiple_answersBooleanTrue, if the poll allows multiple answers
    correct_option_idIntegerOptional. 0-based identifier of the correct answer option. Available only for polls in the quiz mode, which are closed, or was sent (not forwarded) by the bot or to the private chat with the bot.
    explanationStringOptional. 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
    explanation_entitiesArray of MessageEntityOptional. Special entities like usernames, URLs, bot commands, etc. that appear in the explanation
    open_periodIntegerOptional. Amount of time in seconds the poll will be active after creation
    close_dateIntegerOptional. Point in time (Unix timestamp) when the poll will be automatically closed
    +

    Location

    +

    This object represents a point on the map.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    longitudeFloatLongitude as defined by sender
    latitudeFloatLatitude as defined by sender
    horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
    live_periodIntegerOptional. Time relative to the message sending date, during which the location can be updated; in seconds. For active live locations only.
    headingIntegerOptional. The direction in which user is moving, in degrees; 1-360. For active live locations only.
    proximity_alert_radiusIntegerOptional. Maximum distance for proximity alerts about approaching another chat member, in meters. For sent live locations only.
    +

    Venue

    +

    This object represents a venue.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    locationLocationVenue location. Can't be a live location
    titleStringName of the venue
    addressStringAddress of the venue
    foursquare_idStringOptional. Foursquare identifier of the venue
    foursquare_typeStringOptional. Foursquare type of the venue. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
    google_place_idStringOptional. Google Places identifier of the venue
    google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
    +

    ProximityAlertTriggered

    +

    This object represents the content of a service message, sent whenever a user in the chat triggers a proximity alert set by another user.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    travelerUserUser that triggered the alert
    watcherUserUser that set the alert
    distanceIntegerThe distance between the users
    +

    MessageAutoDeleteTimerChanged

    +

    This object represents a service message about a change in auto-delete timer settings.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    message_auto_delete_timeIntegerNew auto-delete time for messages in the chat; in seconds
    +

    VoiceChatScheduled

    +

    This object represents a service message about a voice chat scheduled in the chat.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    start_dateIntegerPoint in time (Unix timestamp) when the voice chat is supposed to be started by a chat administrator
    +

    VoiceChatStarted

    +

    This object represents a service message about a voice chat started in the chat. Currently holds no information.

    +

    VoiceChatEnded

    +

    This object represents a service message about a voice chat ended in the chat.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    durationIntegerVoice chat duration in seconds
    +

    VoiceChatParticipantsInvited

    +

    This object represents a service message about new members invited to a voice chat.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    usersArray of UserOptional. New members that were invited to the voice chat
    +

    UserProfilePhotos

    +

    This object represent a user's profile pictures.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    total_countIntegerTotal number of profile pictures the target user has
    photosArray of Array of PhotoSizeRequested profile pictures (in up to 4 sizes each)
    +

    File

    +

    This object represents a file ready to be downloaded. The file can be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile.

    +
    +

    Maximum file size to download is 20 MB

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    file_sizeIntegerOptional. File size in bytes, if known
    file_pathStringOptional. File path. Use https://api.telegram.org/file/bot<token>/<file_path> to get the file.
    +

    ReplyKeyboardMarkup

    +

    This object represents a custom keyboard with reply options (see Introduction to bots for details and examples).

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    keyboardArray of Array of KeyboardButtonArray of button rows, each represented by an Array of KeyboardButton objects
    resize_keyboardBooleanOptional. Requests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). Defaults to false, in which case the custom keyboard is always of the same height as the app's standard keyboard.
    one_time_keyboardBooleanOptional. Requests 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. Defaults to false.
    input_field_placeholderStringOptional. The placeholder to be shown in the input field when the keyboard is active; 1-64 characters
    selectiveBooleanOptional. Use 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.
    +

    KeyboardButton

    +

    This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields request_contact, request_location, and request_poll are mutually exclusive.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    textStringText of the button. If none of the optional fields are used, it will be sent as a message when the button is pressed
    request_contactBooleanOptional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
    request_locationBooleanOptional. If True, the user's current location will be sent when the button is pressed. Available in private chats only
    request_pollKeyboardButtonPollTypeOptional. If specified, the user will be asked to create a poll and send it to the bot when the button is pressed. Available in private chats only
    +

    Note: request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.
    Note: request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message.

    +

    KeyboardButtonPollType

    +

    This object represents type of a poll, which is allowed to be created and sent when the corresponding button is pressed.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringOptional. If quiz is passed, the user will be allowed to create only polls in the quiz mode. If regular is passed, only regular polls will be allowed. Otherwise, the user will be allowed to create a poll of any type.
    +

    ReplyKeyboardRemove

    +

    Upon receiving a message with this object, Telegram clients will remove the current custom keyboard and display the default letter-keyboard. By default, custom keyboards are displayed until a new keyboard is sent by a bot. An exception is made for one-time keyboards that are hidden immediately after the user presses a button (see ReplyKeyboardMarkup).

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    remove_keyboardTrueRequests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup)
    selectiveBooleanOptional. Use this parameter 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.
    +

    InlineKeyboardMarkup

    +

    This object represents an inline keyboard that appears right next to the message it belongs to.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    inline_keyboardArray of Array of InlineKeyboardButtonArray of button rows, each represented by an Array of InlineKeyboardButton objects
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.

    +

    InlineKeyboardButton

    +

    This object represents one button of an inline keyboard. You must use exactly one of the optional fields.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    textStringLabel text on the button
    urlStringOptional. HTTP or tg:// url to be opened when the button is pressed. Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.
    login_urlLoginUrlOptional. An HTTP URL used to automatically authorize the user. Can be used as a replacement for the Telegram Login Widget.
    callback_dataStringOptional. Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes
    switch_inline_queryStringOptional. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.

    Note: This offers an easy way for users to start using your bot in inline mode when they are currently in a private chat with it. Especially useful when combined with switch_pm… actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.
    switch_inline_query_current_chatStringOptional. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.

    This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.
    callback_gameCallbackGameOptional. Description of the game that will be launched when the user presses the button.

    NOTE: This type of button must always be the first button in the first row.
    payBooleanOptional. Specify True, to send a Pay button.

    NOTE: This type of button must always be the first button in the first row and can only be used in invoice messages.
    +

    LoginUrl

    +

    This object represents a parameter of the inline keyboard button used to automatically authorize a user. Serves as a great replacement for the Telegram Login Widget when the user is coming from Telegram. All the user needs to do is tap/click a button and confirm that they want to log in:

    +
    + TITLE +
    + +

    Telegram apps support these buttons as of version 5.7.

    +
    +

    Sample bot: @discussbot

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    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.
    forward_textStringOptional. New text of the button in forwarded messages.
    bot_usernameStringOptional. Username 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.
    request_write_accessBooleanOptional. Pass True to request the permission for your bot to send messages to the user.
    +

    CallbackQuery

    +

    This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idStringUnique identifier for this query
    fromUserSender
    messageMessageOptional. Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
    inline_message_idStringOptional. Identifier of the message sent via the bot in inline mode, that originated the query.
    chat_instanceStringGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
    dataStringOptional. Data associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
    game_short_nameStringOptional. Short name of a Game to be returned, serves as the unique identifier for the game
    +
    +

    NOTE: After the user presses a callback button, Telegram clients will display a progress bar until you call answerCallbackQuery. It is, therefore, necessary to react by calling answerCallbackQuery even if no notification to the user is needed (e.g., without specifying any of the optional parameters).

    +
    +

    ForceReply

    +

    Upon receiving a message with this object, Telegram clients will display a reply interface to the user (act as if the user has selected the bot's message and tapped 'Reply'). This can be extremely useful if you want to create user-friendly step-by-step interfaces without having to sacrifice privacy mode.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    force_replyTrueShows reply interface to the user, as if they manually selected the bot's message and tapped 'Reply'
    input_field_placeholderStringOptional. The placeholder to be shown in the input field when the reply is active; 1-64 characters
    selectiveBooleanOptional. Use this parameter if you want to force reply from 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 poll bot for groups runs in privacy mode (only receives commands, replies to its messages and mentions). There could be two ways to create a new poll:

    +
      +
    • Explain the user how to send a command with parameters (e.g. /newpoll question answer1 answer2). May be appealing for hardcore users but lacks modern day polish.
      • +
    • Guide the user through a step-by-step process. 'Please send me your question', 'Cool, now let's add the first answer option', 'Great. Keep adding answer options, then send /done when you're ready'.
      • +
    +

    The last option is definitely more attractive. And if you use ForceReply in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.

    +
    +

    ChatPhoto

    +

    This object represents a chat photo.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    small_file_idStringFile identifier of small (160x160) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
    small_file_unique_idStringUnique file identifier of small (160x160) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    big_file_idStringFile identifier of big (640x640) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
    big_file_unique_idStringUnique file identifier of big (640x640) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    +

    ChatInviteLink

    +

    Represents an invite link for a chat.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    invite_linkStringThe invite link. If the link was created by another chat administrator, then the second part of the link will be replaced with “…”.
    creatorUserCreator of the link
    creates_join_requestBooleanTrue, if users joining the chat via the link need to be approved by chat administrators
    is_primaryBooleanTrue, if the link is primary
    is_revokedBooleanTrue, if the link is revoked
    nameStringOptional. Invite link name
    expire_dateIntegerOptional. Point in time (Unix timestamp) when the link will expire or has been expired
    member_limitIntegerOptional. Maximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
    pending_join_request_countIntegerOptional. Number of pending join requests created using this link
    +

    ChatMember

    +

    This object contains information about one member of a chat. Currently, the following 6 types of chat members are supported:

    + +

    ChatMemberOwner

    +

    Represents a chat member that owns the chat and has all administrator privileges.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    statusStringThe member's status in the chat, always “creator”
    userUserInformation about the user
    is_anonymousBooleanTrue, if the user's presence in the chat is hidden
    custom_titleStringOptional. Custom title for this user
    +

    ChatMemberAdministrator

    +

    Represents a chat member that has some additional privileges.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    statusStringThe member's status in the chat, always “administrator”
    userUserInformation about the user
    can_be_editedBooleanTrue, if the bot is allowed to edit administrator privileges of that user
    is_anonymousBooleanTrue, if the user's presence in the chat is hidden
    can_manage_chatBooleanTrue, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
    can_delete_messagesBooleanTrue, if the administrator can delete messages of other users
    can_manage_voice_chatsBooleanTrue, if the administrator can manage voice chats
    can_restrict_membersBooleanTrue, if the administrator can restrict, ban or unban chat members
    can_promote_membersBooleanTrue, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by the user)
    can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
    can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
    can_post_messagesBooleanOptional. True, if the administrator can post in the channel; channels only
    can_edit_messagesBooleanOptional. True, if the administrator can edit messages of other users and can pin messages; channels only
    can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages; groups and supergroups only
    custom_titleStringOptional. Custom title for this user
    +

    ChatMemberMember

    +

    Represents a chat member that has no additional privileges or restrictions.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    statusStringThe member's status in the chat, always “member”
    userUserInformation about the user
    +

    ChatMemberRestricted

    +

    Represents a chat member that is under certain restrictions in the chat. Supergroups only.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    statusStringThe member's status in the chat, always “restricted”
    userUserInformation about the user
    is_memberBooleanTrue, if the user is a member of the chat at the moment of the request
    can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
    can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
    can_pin_messagesBooleanTrue, if the user is allowed to pin messages
    can_send_messagesBooleanTrue, if the user is allowed to send text messages, contacts, locations and venues
    can_send_media_messagesBooleanTrue, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes
    can_send_pollsBooleanTrue, if the user is allowed to send polls
    can_send_other_messagesBooleanTrue, if the user is allowed to send animations, games, stickers and use inline bots
    can_add_web_page_previewsBooleanTrue, if the user is allowed to add web page previews to their messages
    until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is restricted forever
    +

    ChatMemberLeft

    +

    Represents a chat member that isn't currently a member of the chat, but may join it themselves.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    statusStringThe member's status in the chat, always “left”
    userUserInformation about the user
    +

    ChatMemberBanned

    +

    Represents a chat member that was banned in the chat and can't return to the chat or view chat messages.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    statusStringThe member's status in the chat, always “kicked”
    userUserInformation about the user
    until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is banned forever
    +

    ChatMemberUpdated

    +

    This object represents changes in the status of a chat member.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    chatChatChat the user belongs to
    fromUserPerformer of the action, which resulted in the change
    dateIntegerDate the change was done in Unix time
    old_chat_memberChatMemberPrevious information about the chat member
    new_chat_memberChatMemberNew information about the chat member
    invite_linkChatInviteLinkOptional. Chat invite link, which was used by the user to join the chat; for joining by invite link events only.
    +

    ChatJoinRequest

    +

    Represents a join request sent to a chat.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    chatChatChat to which the request was sent
    fromUserUser that sent the join request
    dateIntegerDate the request was sent in Unix time
    bioStringOptional. Bio of the user.
    invite_linkChatInviteLinkOptional. Chat invite link that was used by the user to send the join request
    +

    ChatPermissions

    +

    Describes actions that a non-administrator user is allowed to take in a chat.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    can_send_messagesBooleanOptional. True, if the user is allowed to send text messages, contacts, locations and venues
    can_send_media_messagesBooleanOptional. True, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes, implies can_send_messages
    can_send_pollsBooleanOptional. True, if the user is allowed to send polls, implies can_send_messages
    can_send_other_messagesBooleanOptional. True, if the user is allowed to send animations, games, stickers and use inline bots, implies can_send_media_messages
    can_add_web_page_previewsBooleanOptional. True, if the user is allowed to add web page previews to their messages, implies can_send_media_messages
    can_change_infoBooleanOptional. True, if the user is allowed to change the chat title, photo and other settings. Ignored in public supergroups
    can_invite_usersBooleanOptional. True, if the user is allowed to invite new users to the chat
    can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages. Ignored in public supergroups
    +

    ChatLocation

    +

    Represents a location to which a chat is connected.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    locationLocationThe location to which the supergroup is connected. Can't be a live location.
    addressStringLocation address; 1-64 characters, as defined by the chat owner
    +

    BotCommand

    +

    This object represents a bot command.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    commandStringText of the command; 1-32 characters. Can contain only lowercase English letters, digits and underscores.
    descriptionStringDescription of the command; 1-256 characters.
    +

    BotCommandScope

    +

    This object represents the scope to which bot commands are applied. Currently, the following 7 scopes are supported:

    + +

    Determining list of commands

    +

    The following algorithm is used to determine the list of commands for a particular user viewing the bot menu. The first list of commands which is set is returned:

    +

    Commands in the chat with the bot

    +
      +
    • botCommandScopeChat + language_code
      • +
    • botCommandScopeChat
      • +
    • botCommandScopeAllPrivateChats + language_code
      • +
    • botCommandScopeAllPrivateChats
      • +
    • botCommandScopeDefault + language_code
      • +
    • botCommandScopeDefault
      • +
    +

    Commands in group and supergroup chats

    +
      +
    • botCommandScopeChatMember + language_code
      • +
    • botCommandScopeChatMember
      • +
    • botCommandScopeChatAdministrators + language_code (administrators only)
      • +
    • botCommandScopeChatAdministrators (administrators only)
      • +
    • botCommandScopeChat + language_code
      • +
    • botCommandScopeChat
      • +
    • botCommandScopeAllChatAdministrators + language_code (administrators only)
      • +
    • botCommandScopeAllChatAdministrators (administrators only)
      • +
    • botCommandScopeAllGroupChats + language_code
      • +
    • botCommandScopeAllGroupChats
      • +
    • botCommandScopeDefault + language_code
      • +
    • botCommandScopeDefault
      • +
    +

    BotCommandScopeDefault

    +

    Represents the default scope of bot commands. Default commands are used if no commands with a narrower scope are specified for the user.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be default
    +

    BotCommandScopeAllPrivateChats

    +

    Represents the scope of bot commands, covering all private chats.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be all_private_chats
    +

    BotCommandScopeAllGroupChats

    +

    Represents the scope of bot commands, covering all group and supergroup chats.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be all_group_chats
    +

    BotCommandScopeAllChatAdministrators

    +

    Represents the scope of bot commands, covering all group and supergroup chat administrators.

    + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be all_chat_administrators
    +

    BotCommandScopeChat

    +

    Represents the scope of bot commands, covering a specific chat.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be chat
    chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    +

    BotCommandScopeChatAdministrators

    +

    Represents the scope of bot commands, covering all administrators of a specific group or supergroup chat.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be chat_administrators
    chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    +

    BotCommandScopeChatMember

    +

    Represents the scope of bot commands, covering a specific member of a group or supergroup chat.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringScope type, must be chat_member
    chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    user_idIntegerUnique identifier of the target user
    +

    ResponseParameters

    +

    Contains information about why a request was unsuccessful.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
    retry_afterIntegerOptional. In case of exceeding flood control, the number of seconds left to wait before the request can be repeated
    +

    InputMedia

    +

    This object represents the content of a media message to be sent. It should be one of

    + +

    InputMediaPhoto

    +

    Represents a photo to be sent.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be photo
    mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
    captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    +

    InputMediaVideo

    +

    Represents a video to be sent.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be video
    mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
    thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    widthIntegerOptional. Video width
    heightIntegerOptional. Video height
    durationIntegerOptional. Video duration in seconds
    supports_streamingBooleanOptional. Pass True, if the uploaded video is suitable for streaming
    +

    InputMediaAnimation

    +

    Represents an animation file (GIF or H.264/MPEG-4 AVC video without sound) to be sent.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be animation
    mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
    thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptional. Caption of the animation to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the animation caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    widthIntegerOptional. Animation width
    heightIntegerOptional. Animation height
    durationIntegerOptional. Animation duration in seconds
    +

    InputMediaAudio

    +

    Represents an audio file to be treated as music to be sent.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be audio
    mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
    thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptional. Caption of the audio to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    durationIntegerOptional. Duration of the audio in seconds
    performerStringOptional. Performer of the audio
    titleStringOptional. Title of the audio
    +

    InputMediaDocument

    +

    Represents a general file to be sent.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be document
    mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
    thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    disable_content_type_detectionBooleanOptional. Disables automatic server-side content type detection for files uploaded using multipart/form-data. Always True, if the document is sent as part of an album.
    +

    InputFile

    +

    This object represents the contents of a file to be uploaded. Must be posted using multipart/form-data in the usual way that files are uploaded via the browser.

    +

    Sending files

    +

    There are three ways to send files (photos, stickers, audio, media, etc.):

    +
      +
    1. If the file is already stored somewhere on the Telegram servers, you don't need to reupload it: each file object has a file_id field, simply pass this file_id as a parameter instead of uploading. There are no limits for files sent this way.
      2. +
    2. Provide Telegram with an HTTP URL for the file to be sent. Telegram will download and send the file. 5 MB max size for photos and 20 MB max for other types of content.
      3. +
    3. Post the file using multipart/form-data in the usual way that files are uploaded via the browser. 10 MB max size for photos, 50 MB for other files.
      4. +
    +

    Sending by file_id

    +
      +
    • It is not possible to change the file type when resending by file_id. I.e. a video can't be sent as a photo, a photo can't be sent as a document, etc.
      • +
    • It is not possible to resend thumbnails.
      • +
    • Resending a photo by file_id will send all of its sizes.
      • +
    • file_id is unique for each individual bot and can't be transferred from one bot to another.
      • +
    • file_id uniquely identifies a file, but a file can have different valid file_ids even for the same bot.
      • +
    +

    Sending by URL

    +
      +
    • When sending by URL the target file must have the correct MIME type (e.g., audio/mpeg for sendAudio, etc.).
      • +
    • In sendDocument, sending by URL will currently only work for GIF, PDF and ZIP files.
      • +
    • To use sendVoice, the file must have the type audio/ogg and be no more than 1MB in size. 1-20MB voice notes will be sent as files.
      • +
    • Other configurations may work but we can't guarantee that they will.
      • +
    +

    Inline mode objects

    +

    Objects and methods used in the inline mode are described in the Inline mode section.

    +

    Available methods

    +
    +

    All methods in the Bot API are case-insensitive. We support GET and POST HTTP methods. Use either URL query string or application/json or application/x-www-form-urlencoded or multipart/form-data for passing parameters in Bot API requests.
    On successful call, a JSON-object containing the result will be returned.

    +
    +

    getMe

    +

    A simple method for testing your bot's authentication token. Requires no parameters. Returns basic information about the bot in form of a User object.

    +

    logOut

    +

    Use this method to log out from the cloud Bot API server before launching the bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive updates. After a successful call, you can immediately log in on a local server, but will not be able to log in back to the cloud Bot API server for 10 minutes. Returns True on success. Requires no parameters.

    +

    close

    +

    Use this method to close the bot instance before moving it from one local server to another. You need to delete the webhook before calling this method to ensure that the bot isn't launched again after server restart. The method will return error 429 in the first 10 minutes after the bot is launched. Returns True on success. Requires no parameters.

    +

    sendMessage

    +

    Use this method to send text messages. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    textStringYesText of the message to be sent, 1-4096 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
    entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
    disable_web_page_previewBooleanOptionalDisables link previews for links in this message
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    Formatting options

    +

    The Bot API supports basic formatting for messages. You can use bold, italic, underlined, strikethrough, and spoiler text, as well as inline links and pre-formatted code in your bots' messages. Telegram clients will render them accordingly. You can use either markdown-style or HTML-style formatting.

    +

    Note that Telegram clients will display an alert to the user before opening an inline link ('Open this link?' together with the full URL).

    +

    Message entities can be nested, providing following restrictions are met:
    - If two entities have common characters then one of them is fully contained inside another.
    - bold, italic, underline, strikethrough, and spoiler entities can contain and can be part of any other entities, except pre and code.
    - All other entities can't contain each other.

    +

    Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username. Please note:

    +
      +
    • These links will work only if they are used inside an inline link or in an inline keyboard button. For example, they will not work, when used in a message text.
      • +
    • These mentions are only guaranteed to work if the user has contacted the bot in the past, has sent a callback query to the bot via an inline button or is a member in the group where he was mentioned.
      • +
    +
    MarkdownV2 style
    +

    To use this mode, pass MarkdownV2 in the parse_mode field. Use the following syntax in your message:

    +
    *bold \*text*
+_italic \*text_
+__underline__
+~strikethrough~
+||spoiler||
+*bold _italic bold ~italic bold strikethrough ||italic bold strikethrough spoiler||~ __underline italic bold___ bold*
+[inline URL](http://www.example.com/)
+[inline mention of a user](tg://user?id=123456789)
+`inline fixed-width code`
+```
+pre-formatted fixed-width code block
+```
+```python
+pre-formatted fixed-width code block written in the Python programming language
+```
    +

    Please note:

    +
      +
    • Any character with code between 1 and 126 inclusively can be escaped anywhere with a preceding '\' character, in which case it is treated as an ordinary character and not a part of the markup. This implies that '\' character usually must be escaped with a preceding '\' character.
      • +
    • Inside pre and code entities, all '`' and '\' characters must be escaped with a preceding '\' character.
      • +
    • Inside (...) part of inline link definition, all ')' and '\' must be escaped with a preceding '\' character.
      • +
    • In all other places characters '_', '*', '[', ']', '(', ')', '~', '`', '>', '#', '+', '-', '=', '|', '{', '}', '.', '!' must be escaped with the preceding character '\'.
      • +
    • In case of ambiguity between italic and underline entities __ is always greadily treated from left to right as beginning or end of underline entity, so instead of ___italic underline___ use ___italic underline_\r__, where \r is a character with code 13, which will be ignored.
      • +
    +
    HTML style
    +

    To use this mode, pass HTML in the parse_mode field. The following tags are currently supported:

    +
    <b>bold</b>, <strong>bold</strong>
+<i>italic</i>, <em>italic</em>
+<u>underline</u>, <ins>underline</ins>
+<s>strikethrough</s>, <strike>strikethrough</strike>, <del>strikethrough</del>
+<span class="tg-spoiler">spoiler</span>, <tg-spoiler>spoiler</tg-spoiler>
+<b>bold <i>italic bold <s>italic bold strikethrough <span class="tg-spoiler">italic bold strikethrough spoiler</span></s> <u>underline italic bold</u></i> bold</b>
+<a href="http://www.example.com/">inline URL</a>
+<a href="tg://user?id=123456789">inline mention of a user</a>
+<code>inline fixed-width code</code>
+<pre>pre-formatted fixed-width code block</pre>
+<pre><code class="language-python">pre-formatted fixed-width code block written in the Python programming language</code></pre>
    +

    Please note:

    +
      +
    • Only the tags mentioned above are currently supported.
      • +
    • All <, > and & symbols that are not a part of a tag or an HTML entity must be replaced with the corresponding HTML entities (< with &lt;, > with &gt; and & with &amp;).
      • +
    • All numerical HTML entities are supported.
      • +
    • The API currently supports only the following named HTML entities: &lt;, &gt;, &amp; and &quot;.
      • +
    • Use nested pre and code tags, to define programming language for pre entity.
      • +
    • Programming language can't be specified for standalone code tags.
      • +
    +
    Markdown style
    +

    This is a legacy mode, retained for backward compatibility. To use this mode, pass Markdown in the parse_mode field. Use the following syntax in your message:

    +
    *bold text*
+_italic text_
+[inline URL](http://www.example.com/)
+[inline mention of a user](tg://user?id=123456789)
+`inline fixed-width code`
+```
+pre-formatted fixed-width code block
+```
+```python
+pre-formatted fixed-width code block written in the Python programming language
+```
    +

    Please note:

    +
      +
    • Entities must not be nested, use parse mode MarkdownV2 instead.
      • +
    • There is no way to specify underline and strikethrough entities, use parse mode MarkdownV2 instead.
      • +
    • To escape characters '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
      • +
    • Escaping inside entities is not allowed, so entity must be closed first and reopened again: use _snake_\__case_ for italic snake_case and *2*\**2=4* for bold 2*2=4.
      • +
    +

    forwardMessage

    +

    Use this method to forward messages of any kind. Service messages can't be forwarded. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the forwarded message from forwarding and saving
    message_idIntegerYesMessage identifier in the chat specified in from_chat_id
    +

    copyMessage

    +

    Use this method to copy messages of any kind. Service messages and invoice messages can't be copied. The method is analogous to the method forwardMessage, but the copied message doesn't have a link to the original message. Returns the MessageId of the sent message on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
    message_idIntegerYesMessage identifier in the chat specified in from_chat_id
    captionStringOptionalNew caption for media, 0-1024 characters after entities parsing. If not specified, the original caption is kept
    parse_modeStringOptionalMode for parsing entities in the new caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the new caption, which can be specified instead of parse_mode
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendPhoto

    +

    Use this method to send photos. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    photoInputFile or StringYesPhoto to send. Pass a file_id as String to send a photo that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a photo from the Internet, or upload a new photo using multipart/form-data. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. More info on Sending Files »
    captionStringOptionalPhoto caption (may also be used when resending photos by file_id), 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the photo caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendAudio

    +

    Use this method to send audio files, if you want Telegram clients to display them in the music player. Your audio must be in the .MP3 or .M4A format. On success, the sent Message is returned. Bots can currently send audio files of up to 50 MB in size, this limit may be changed in the future.

    +

    For sending voice messages, use the sendVoice method instead.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    audioInputFile or StringYesAudio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
    captionStringOptionalAudio caption, 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the audio caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    durationIntegerOptionalDuration of the audio in seconds
    performerStringOptionalPerformer
    titleStringOptionalTrack name
    thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendDocument

    +

    Use this method to send general files. On success, the sent Message is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    documentInputFile or StringYesFile to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
    thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptionalDocument caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the document caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    disable_content_type_detectionBooleanOptionalDisables automatic server-side content type detection for files uploaded using multipart/form-data
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendVideo

    +

    Use this method to send video files, Telegram clients support mp4 videos (other formats may be sent as Document). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    videoInputFile or StringYesVideo to send. Pass a file_id as String to send a video that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »
    durationIntegerOptionalDuration of sent video in seconds
    widthIntegerOptionalVideo width
    heightIntegerOptionalVideo height
    thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptionalVideo caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the video caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    supports_streamingBooleanOptionalPass True, if the uploaded video is suitable for streaming
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendAnimation

    +

    Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound). On success, the sent Message is returned. Bots can currently send animation files of up to 50 MB in size, this limit may be changed in the future.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    animationInputFile or StringYesAnimation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. More info on Sending Files »
    durationIntegerOptionalDuration of sent animation in seconds
    widthIntegerOptionalAnimation width
    heightIntegerOptionalAnimation height
    thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    captionStringOptionalAnimation caption (may also be used when resending animation by file_id), 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the animation caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendVoice

    +

    Use this method to send audio files, if you want Telegram clients to display the file as a playable voice message. For this to work, your audio must be in an .OGG file encoded with OPUS (other formats may be sent as Audio or Document). On success, the sent Message is returned. Bots can currently send voice messages of up to 50 MB in size, this limit may be changed in the future.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    voiceInputFile or StringYesAudio file to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
    captionStringOptionalVoice message caption, 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the voice message caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    durationIntegerOptionalDuration of the voice message in seconds
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendVideoNote

    +

    As of v.4.0, Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    video_noteInputFile or StringYesVideo note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. More info on Sending Files ». Sending video notes by a URL is currently unsupported
    durationIntegerOptionalDuration of sent video in seconds
    lengthIntegerOptionalVideo width and height, i.e. diameter of the video message
    thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendMediaGroup

    +

    Use this method to send a group of photos, videos, documents or audios as an album. Documents and audio files can be only grouped in an album with messages of the same type. On success, an array of Messages that were sent is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    mediaArray of InputMediaAudio, InputMediaDocument, InputMediaPhoto and InputMediaVideoYesA JSON-serialized array describing messages to be sent, must include 2-10 items
    disable_notificationBooleanOptionalSends messages silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent messages from forwarding and saving
    reply_to_message_idIntegerOptionalIf the messages are a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    +

    sendLocation

    +

    Use this method to send point on the map. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    latitudeFloat numberYesLatitude of the location
    longitudeFloat numberYesLongitude of the location
    horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
    live_periodIntegerOptionalPeriod in seconds for which the location will be updated (see Live Locations, should be between 60 and 86400.
    headingIntegerOptionalFor live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
    proximity_alert_radiusIntegerOptionalFor live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    editMessageLiveLocation

    +

    Use this method to edit live location messages. A location can be edited until its live_period expires or editing is explicitly disabled by a call to stopMessageLiveLocation. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    latitudeFloat numberYesLatitude of new location
    longitudeFloat numberYesLongitude of new location
    horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
    headingIntegerOptionalDirection in which the user is moving, in degrees. Must be between 1 and 360 if specified.
    proximity_alert_radiusIntegerOptionalMaximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
    +

    stopMessageLiveLocation

    +

    Use this method to stop updating a live location message before live_period expires. On success, if the message is not an inline message, the edited Message is returned, otherwise True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message with live location to stop
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
    +

    sendVenue

    +

    Use this method to send information about a venue. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    latitudeFloat numberYesLatitude of the venue
    longitudeFloat numberYesLongitude of the venue
    titleStringYesName of the venue
    addressStringYesAddress of the venue
    foursquare_idStringOptionalFoursquare identifier of the venue
    foursquare_typeStringOptionalFoursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
    google_place_idStringOptionalGoogle Places identifier of the venue
    google_place_typeStringOptionalGoogle Places type of the venue. (See supported types.)
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendContact

    +

    Use this method to send phone contacts. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    phone_numberStringYesContact's phone number
    first_nameStringYesContact's first name
    last_nameStringOptionalContact's last name
    vcardStringOptionalAdditional data about the contact in the form of a vCard, 0-2048 bytes
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove keyboard or to force a reply from the user.
    +

    sendPoll

    +

    Use this method to send a native poll. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    questionStringYesPoll question, 1-300 characters
    optionsArray of StringYesA JSON-serialized list of answer options, 2-10 strings 1-100 characters each
    is_anonymousBooleanOptionalTrue, if the poll needs to be anonymous, defaults to True
    typeStringOptionalPoll type, “quiz” or “regular”, defaults to “regular”
    allows_multiple_answersBooleanOptionalTrue, if the poll allows multiple answers, ignored for polls in quiz mode, defaults to False
    correct_option_idIntegerOptional0-based identifier of the correct answer option, required for polls in quiz mode
    explanationStringOptionalText 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 after entities parsing
    explanation_parse_modeStringOptionalMode for parsing entities in the explanation. See formatting options for more details.
    explanation_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the poll explanation, which can be specified instead of parse_mode
    open_periodIntegerOptionalAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
    close_dateIntegerOptionalPoint 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 open_period.
    is_closedBooleanOptionalPass True, if the poll needs to be immediately closed. This can be useful for poll preview.
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendDice

    +

    Use this method to send an animated emoji that will display a random value. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    emojiStringOptionalEmoji on which the dice throw animation is based. Currently, must be one of “🎲”, “🎯”, “🏀”, “⚽”, “🎳”, or “🎰”. Dice can have values 1-6 for “🎲”, “🎯” and “🎳”, values 1-5 for “🏀” and “⚽”, and values 1-64 for “🎰”. Defaults to “🎲”
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    sendChatAction

    +

    Use this method when you need to tell the user that something is happening on the bot's side. The status is set for 5 seconds or less (when a message arrives from your bot, Telegram clients clear its typing status). Returns True on success.

    +
    +

    Example: The ImageBot needs some time to process a request and upload the image. Instead of sending a text message along the lines of “Retrieving image, please wait…”, the bot may use sendChatAction with action = upload_photo. The user will see a “sending photo” status for the bot.

    +
    +

    We only recommend using this method when a response from the bot will take a noticeable amount of time to arrive.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    actionStringYesType of action to broadcast. Choose one, depending on what the user is about to receive: typing for text messages, upload_photo for photos, record_video or upload_video for videos, record_voice or upload_voice for voice notes, upload_document for general files, choose_sticker for stickers, find_location for location data, record_video_note or upload_video_note for video notes.
    +

    getUserProfilePhotos

    +

    Use this method to get a list of profile pictures for a user. Returns a UserProfilePhotos object.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesUnique identifier of the target user
    offsetIntegerOptionalSequential number of the first photo to be returned. By default, all photos are returned.
    limitIntegerOptionalLimits the number of photos to be retrieved. Values between 1-100 are accepted. Defaults to 100.
    +

    getFile

    +

    Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download files of up to 20MB in size. On success, a File object is returned. The file can then be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>, where <file_path> is taken from the response. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile again.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    file_idStringYesFile identifier to get info about
    +

    Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type and name (if available) when the File object is received.

    +

    banChatMember

    +

    Use this method to ban a user in a group, a supergroup or a channel. In the case of supergroups and channels, the user will not be able to return to the chat on their own using invite links, etc., unless unbanned first. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
    user_idIntegerYesUnique identifier of the target user
    until_dateIntegerOptionalDate when the user will be unbanned, unix time. If user is banned for more than 366 days or less than 30 seconds from the current time they are considered to be banned forever. Applied for supergroups and channels only.
    revoke_messagesBooleanOptionalPass True to delete all messages from the chat for the user that is being removed. If False, the user will be able to see messages in the group that were sent before the user was removed. Always True for supergroups and channels.
    +

    unbanChatMember

    +

    Use this method to unban a previously banned user in a supergroup or channel. The user will not return to the group or channel automatically, but will be able to join via link, etc. The bot must be an administrator for this to work. By default, this method guarantees that after the call the user is not a member of the chat, but will be able to join it. So if the user is a member of the chat they will also be removed from the chat. If you don't want this, use the parameter only_if_banned. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
    user_idIntegerYesUnique identifier of the target user
    only_if_bannedBooleanOptionalDo nothing if the user is not banned
    +

    restrictChatMember

    +

    Use this method to restrict a user in a supergroup. The bot must be an administrator in the supergroup for this to work and must have the appropriate administrator rights. Pass True for all permissions to lift restrictions from a user. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    user_idIntegerYesUnique identifier of the target user
    permissionsChatPermissionsYesA JSON-serialized object for new user permissions
    until_dateIntegerOptionalDate when restrictions will be lifted for the user, unix time. If user is restricted for more than 366 days or less than 30 seconds from the current time, they are considered to be restricted forever
    +

    promoteChatMember

    +

    Use this method to promote or demote a user in a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Pass False for all boolean parameters to demote a user. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    user_idIntegerYesUnique identifier of the target user
    is_anonymousBooleanOptionalPass True, if the administrator's presence in the chat is hidden
    can_manage_chatBooleanOptionalPass True, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
    can_post_messagesBooleanOptionalPass True, if the administrator can create channel posts, channels only
    can_edit_messagesBooleanOptionalPass True, if the administrator can edit messages of other users and can pin messages, channels only
    can_delete_messagesBooleanOptionalPass True, if the administrator can delete messages of other users
    can_manage_voice_chatsBooleanOptionalPass True, if the administrator can manage voice chats
    can_restrict_membersBooleanOptionalPass True, if the administrator can restrict, ban or unban chat members
    can_promote_membersBooleanOptionalPass True, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by him)
    can_change_infoBooleanOptionalPass True, if the administrator can change chat title, photo and other settings
    can_invite_usersBooleanOptionalPass True, if the administrator can invite new users to the chat
    can_pin_messagesBooleanOptionalPass True, if the administrator can pin messages, supergroups only
    +

    setChatAdministratorCustomTitle

    +

    Use this method to set a custom title for an administrator in a supergroup promoted by the bot. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    user_idIntegerYesUnique identifier of the target user
    custom_titleStringYesNew custom title for the administrator; 0-16 characters, emoji are not allowed
    +

    banChatSenderChat

    +

    Use this method to ban a channel chat in a supergroup or a channel. Until the chat is unbanned, the owner of the banned chat won't be able to send messages on behalf of any of their channels. The bot must be an administrator in the supergroup or channel for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    sender_chat_idIntegerYesUnique identifier of the target sender chat
    +

    unbanChatSenderChat

    +

    Use this method to unban a previously banned channel chat in a supergroup or channel. The bot must be an administrator for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    sender_chat_idIntegerYesUnique identifier of the target sender chat
    +

    setChatPermissions

    +

    Use this method to set default chat permissions for all members. The bot must be an administrator in the group or a supergroup for this to work and must have the can_restrict_members administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    permissionsChatPermissionsYesA JSON-serialized object for new default chat permissions
    +

    exportChatInviteLink

    +

    Use this method to generate a new primary invite link for a chat; any previously generated primary link is revoked. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the new invite link as String on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    +
    +

    Note: Each administrator in a chat generates their own invite links. Bots can't use invite links generated by other administrators. If you want your bot to work with invite links, it will need to generate its own link using exportChatInviteLink or by calling the getChat method. If your bot needs to generate a new primary invite link replacing its previous one, use exportChatInviteLink again.

    +
    +

    createChatInviteLink

    +

    Use this method to create an additional invite link for a chat. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. The link can be revoked using the method revokeChatInviteLink. Returns the new invite link as ChatInviteLink object.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    nameStringOptionalInvite link name; 0-32 characters
    expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
    member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
    creates_join_requestBooleanOptionalTrue, if users joining the chat via the link need to be approved by chat administrators. If True, member_limit can't be specified
    +

    editChatInviteLink

    +

    Use this method to edit a non-primary invite link created by the bot. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the edited invite link as a ChatInviteLink object.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    invite_linkStringYesThe invite link to edit
    nameStringOptionalInvite link name; 0-32 characters
    expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
    member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
    creates_join_requestBooleanOptionalTrue, if users joining the chat via the link need to be approved by chat administrators. If True, member_limit can't be specified
    +

    revokeChatInviteLink

    +

    Use this method to revoke an invite link created by the bot. If the primary link is revoked, a new link is automatically generated. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the revoked invite link as ChatInviteLink object.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier of the target chat or username of the target channel (in the format @channelusername)
    invite_linkStringYesThe invite link to revoke
    +

    approveChatJoinRequest

    +

    Use this method to approve a chat join request. The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    user_idIntegerYesUnique identifier of the target user
    +

    declineChatJoinRequest

    +

    Use this method to decline a chat join request. The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    user_idIntegerYesUnique identifier of the target user
    +

    setChatPhoto

    +

    Use this method to set a new profile photo for the chat. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    photoInputFileYesNew chat photo, uploaded using multipart/form-data
    +

    deleteChatPhoto

    +

    Use this method to delete a chat photo. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    +

    setChatTitle

    +

    Use this method to change the title of a chat. Titles can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    titleStringYesNew chat title, 1-255 characters
    +

    setChatDescription

    +

    Use this method to change the description of a group, a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    descriptionStringOptionalNew chat description, 0-255 characters
    +

    pinChatMessage

    +

    Use this method to add a message to the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerYesIdentifier of a message to pin
    disable_notificationBooleanOptionalPass True, if it is not necessary to send a notification to all chat members about the new pinned message. Notifications are always disabled in channels and private chats.
    +

    unpinChatMessage

    +

    Use this method to remove a message from the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalIdentifier of a message to unpin. If not specified, the most recent pinned message (by sending date) will be unpinned.
    +

    unpinAllChatMessages

    +

    Use this method to clear the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    +

    leaveChat

    +

    Use this method for your bot to leave a group, supergroup or channel. Returns True on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
    +

    getChat

    +

    Use this method to get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). Returns a Chat object on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
    +

    getChatAdministrators

    +

    Use this method to get a list of administrators in a chat. On success, returns an Array of ChatMember objects that contains information about all chat administrators except other bots. If the chat is a group or a supergroup and no administrators were appointed, only the creator will be returned.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
    +

    getChatMemberCount

    +

    Use this method to get the number of members in a chat. Returns Int on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
    +

    getChatMember

    +

    Use this method to get information about a member of a chat. Returns a ChatMember object on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
    user_idIntegerYesUnique identifier of the target user
    +

    setChatStickerSet

    +

    Use this method to set a new group sticker set for a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    sticker_set_nameStringYesName of the sticker set to be set as the group sticker set
    +

    deleteChatStickerSet

    +

    Use this method to delete a group sticker set from a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
    +

    answerCallbackQuery

    +

    Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, True is returned.

    +
    +

    Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via @Botfather and accept the terms. Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    callback_query_idStringYesUnique identifier for the query to be answered
    textStringOptionalText of the notification. If not specified, nothing will be shown to the user, 0-200 characters
    show_alertBooleanOptionalIf True, an alert will be shown by the client instead of a notification at the top of the chat screen. Defaults to false.
    urlStringOptionalURL that will be opened by the user's client. If you have created a Game and accepted the conditions via @Botfather, specify the URL that opens your game — note that this will only work if the query comes from a callback_game button.

    Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.
    cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
    +

    setMyCommands

    +

    Use this method to change the list of the bot's commands. See https://core.telegram.org/bots#commands for more details about bot commands. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    commandsArray of BotCommandYesA JSON-serialized list of bot commands to be set as the list of the bot's commands. At most 100 commands can be specified.
    scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
    language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
    +

    deleteMyCommands

    +

    Use this method to delete the list of the bot's commands for the given scope and user language. After deletion, higher level commands will be shown to affected users. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
    language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
    +

    getMyCommands

    +

    Use this method to get the current list of the bot's commands for the given scope and user language. Returns Array of BotCommand on success. If commands aren't set, an empty list is returned.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users. Defaults to BotCommandScopeDefault.
    language_codeStringOptionalA two-letter ISO 639-1 language code or an empty string
    +

    Inline mode methods

    +

    Methods and objects used in the inline mode are described in the Inline mode section.

    +

    Updating messages

    +

    The following methods allow you to change an existing message in the message history instead of sending a new one with a result of an action. This is most useful for messages with inline keyboards using callback queries, but can also help reduce clutter in conversations with regular chat bots.

    +

    Please note, that it is currently only possible to edit messages without reply_markup or with inline keyboards.

    +

    editMessageText

    +

    Use this method to edit text and game messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    textStringYesNew text of the message, 1-4096 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
    entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
    disable_web_page_previewBooleanOptionalDisables link previews for links in this message
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
    +

    editMessageCaption

    +

    Use this method to edit captions of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    captionStringOptionalNew caption of the message, 0-1024 characters after entities parsing
    parse_modeStringOptionalMode for parsing entities in the message caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
    +

    editMessageMedia

    +

    Use this method to edit animation, audio, document, photo, or video messages. If a message is part of a message album, then it can be edited only to an audio for audio albums, only to a document for document albums and to a photo or a video otherwise. When an inline message is edited, a new file can't be uploaded; use a previously uploaded file via its file_id or specify a URL. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    mediaInputMediaYesA JSON-serialized object for a new media content of the message
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
    +

    editMessageReplyMarkup

    +

    Use this method to edit only the reply markup of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
    +

    stopPoll

    +

    Use this method to stop a poll which was sent by the bot. On success, the stopped Poll is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerYesIdentifier of the original message with the poll
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new message inline keyboard.
    +

    deleteMessage

    +

    Use this method to delete a message, including service messages, with the following limitations:
    - A message can only be deleted if it was sent less than 48 hours ago.
    - A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.
    - Bots can delete outgoing messages in private chats, groups, and supergroups.
    - Bots can delete incoming messages in private chats.
    - Bots granted can_post_messages permissions can delete outgoing messages in channels.
    - If the bot is an administrator of a group, it can delete any message there.
    - If the bot has can_delete_messages permission in a supergroup or a channel, it can delete any message there.
    Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    message_idIntegerYesIdentifier of the message to delete
    +

    Stickers

    +

    The following methods and objects allow your bot to handle stickers and sticker sets.

    +

    Sticker

    +

    This object represents a sticker.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    widthIntegerSticker width
    heightIntegerSticker height
    is_animatedBooleanTrue, if the sticker is animated
    is_videoBooleanTrue, if the sticker is a video sticker
    thumbPhotoSizeOptional. Sticker thumbnail in the .WEBP or .JPG format
    emojiStringOptional. Emoji associated with the sticker
    set_nameStringOptional. Name of the sticker set to which the sticker belongs
    mask_positionMaskPositionOptional. For mask stickers, the position where the mask should be placed
    file_sizeIntegerOptional. File size in bytes
    +

    StickerSet

    +

    This object represents a sticker set.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    nameStringSticker set name
    titleStringSticker set title
    is_animatedBooleanTrue, if the sticker set contains animated stickers
    is_videoBooleanTrue, if the sticker set contains video stickers
    contains_masksBooleanTrue, if the sticker set contains masks
    stickersArray of StickerList of all set stickers
    thumbPhotoSizeOptional. Sticker set thumbnail in the .WEBP, .TGS, or .WEBM format
    +

    MaskPosition

    +

    This object describes the position on faces where a mask should be placed by default.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    pointStringThe part of the face relative to which the mask should be placed. One of “forehead”, “eyes”, “mouth”, or “chin”.
    x_shiftFloat numberShift by X-axis measured in widths of the mask scaled to the face size, from left to right. For example, choosing -1.0 will place mask just to the left of the default mask position.
    y_shiftFloat numberShift by Y-axis measured in heights of the mask scaled to the face size, from top to bottom. For example, 1.0 will place the mask just below the default mask position.
    scaleFloat numberMask scaling coefficient. For example, 2.0 means double size.
    +

    sendSticker

    +

    Use this method to send static .WEBP, animated .TGS, or video .WEBM stickers. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    stickerInputFile or StringYesSticker to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a .WEBP file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
    +

    getStickerSet

    +

    Use this method to get a sticker set. On success, a StickerSet object is returned.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    nameStringYesName of the sticker set
    +

    uploadStickerFile

    +

    Use this method to upload a .PNG file with a sticker for later use in createNewStickerSet and addStickerToSet methods (can be used multiple times). Returns the uploaded File on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesUser identifier of sticker file owner
    png_stickerInputFileYesPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. More info on Sending Files »
    +

    createNewStickerSet

    +

    Use this method to create a new sticker set owned by a user. The bot will be able to edit the sticker set thus created. You must use exactly one of the fields png_sticker, tgs_sticker, or webm_sticker. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesUser identifier of created sticker set owner
    nameStringYesShort name of sticker set, to be used in t.me/addstickers/ URLs (e.g., animals). Can contain only english letters, digits and underscores. Must begin with a letter, can't contain consecutive underscores and must end in “_by_<bot username>”. <bot_username> is case insensitive. 1-64 characters.
    titleStringYesSticker set title, 1-64 characters
    png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
    tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#animated-sticker-requirements for technical requirements
    webm_stickerInputFileOptionalWEBM video with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#video-sticker-requirements for technical requirements
    emojisStringYesOne or more emoji corresponding to the sticker
    contains_masksBooleanOptionalPass True, if a set of mask stickers should be created
    mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
    +

    addStickerToSet

    +

    Use this method to add a new sticker to a set created by the bot. You must use exactly one of the fields png_sticker, tgs_sticker, or webm_sticker. Animated stickers can be added to animated sticker sets and only to them. Animated sticker sets can have up to 50 stickers. Static sticker sets can have up to 120 stickers. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesUser identifier of sticker set owner
    nameStringYesSticker set name
    png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
    tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#animated-sticker-requirements for technical requirements
    webm_stickerInputFileOptionalWEBM video with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#video-sticker-requirements for technical requirements
    emojisStringYesOne or more emoji corresponding to the sticker
    mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
    +

    setStickerPositionInSet

    +

    Use this method to move a sticker in a set created by the bot to a specific position. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    stickerStringYesFile identifier of the sticker
    positionIntegerYesNew sticker position in the set, zero-based
    +

    deleteStickerFromSet

    +

    Use this method to delete a sticker from a set created by the bot. Returns True on success.

    + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    stickerStringYesFile identifier of the sticker
    +

    setStickerSetThumb

    +

    Use this method to set the thumbnail of a sticker set. Animated thumbnails can be set for animated sticker sets only. Video thumbnails can be set only for video sticker sets only. Returns True on success.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    nameStringYesSticker set name
    user_idIntegerYesUser identifier of the sticker set owner
    thumbInputFile or StringOptionalA PNG image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a TGS animation with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/stickers#animated-sticker-requirements for animated sticker technical requirements, or a WEBM video with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/stickers#video-sticker-requirements for video sticker technical requirements. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files ». Animated sticker set thumbnails can't be uploaded via HTTP URL.
    +

    Inline mode

    +

    The following methods and objects allow your bot to work in inline mode.
    Please see our Introduction to Inline bots for more details.

    +

    To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot's name.

    +

    InlineQuery

    +

    This object represents an incoming inline query. When the user sends an empty query, your bot could return some default or trending results.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idStringUnique identifier for this query
    fromUserSender
    queryStringText of the query (up to 256 characters)
    offsetStringOffset of the results to be returned, can be controlled by the bot
    chat_typeStringOptional. Type of the chat, from which the inline query was sent. Can be either “sender” for a private chat with the inline query sender, “private”, “group”, “supergroup”, or “channel”. The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
    locationLocationOptional. Sender location, only for bots that request user location
    +

    answerInlineQuery

    +

    Use this method to send answers to an inline query. On success, True is returned.
    No more than 50 results per query are allowed.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    inline_query_idStringYesUnique identifier for the answered query
    resultsArray of InlineQueryResultYesA JSON-serialized array of results for the inline query
    cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
    is_personalBooleanOptionalPass True, 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
    next_offsetStringOptionalPass 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_pm_textStringOptionalIf 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 the parameter switch_pm_parameter
    switch_pm_parameterStringOptionalDeep-linking parameter for the /start message sent to the bot when user presses the switch button. 1-64 characters, only A-Z, a-z, 0-9, _ and - are allowed.

    Example: An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities.
    +

    InlineQueryResult

    +

    This object represents one result of an inline query. Telegram clients currently support results of the following 20 types:

    + +

    Note: All URLs passed in inline query results will be available to end users and therefore must be assumed to be public.

    +

    InlineQueryResultArticle

    +

    Represents a link to an article or web page.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be article
    idStringUnique identifier for this result, 1-64 Bytes
    titleStringTitle of the result
    input_message_contentInputMessageContentContent of the message to be sent
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    urlStringOptional. URL of the result
    hide_urlBooleanOptional. Pass True, if you don't want the URL to be shown in the message
    descriptionStringOptional. Short description of the result
    thumb_urlStringOptional. Url of the thumbnail for the result
    thumb_widthIntegerOptional. Thumbnail width
    thumb_heightIntegerOptional. Thumbnail height
    +

    InlineQueryResultPhoto

    +

    Represents a link to a photo. By default, this photo will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be photo
    idStringUnique identifier for this result, 1-64 bytes
    photo_urlStringA valid URL of the photo. Photo must be in JPEG format. Photo size must not exceed 5MB
    thumb_urlStringURL of the thumbnail for the photo
    photo_widthIntegerOptional. Width of the photo
    photo_heightIntegerOptional. Height of the photo
    titleStringOptional. Title for the result
    descriptionStringOptional. Short description of the result
    captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
    +

    InlineQueryResultGif

    +

    Represents a link to an animated GIF file. By default, this animated GIF file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be gif
    idStringUnique identifier for this result, 1-64 bytes
    gif_urlStringA valid URL for the GIF file. File size must not exceed 1MB
    gif_widthIntegerOptional. Width of the GIF
    gif_heightIntegerOptional. Height of the GIF
    gif_durationIntegerOptional. Duration of the GIF in seconds
    thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
    thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of “image/jpeg”, “image/gif”, or “video/mp4”. Defaults to “image/jpeg”
    titleStringOptional. Title for the result
    captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
    +

    InlineQueryResultMpeg4Gif

    +

    Represents a link to a video animation (H.264/MPEG-4 AVC video without sound). By default, this animated MPEG-4 file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be mpeg4_gif
    idStringUnique identifier for this result, 1-64 bytes
    mpeg4_urlStringA valid URL for the MP4 file. File size must not exceed 1MB
    mpeg4_widthIntegerOptional. Video width
    mpeg4_heightIntegerOptional. Video height
    mpeg4_durationIntegerOptional. Video duration in seconds
    thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
    thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of “image/jpeg”, “image/gif”, or “video/mp4”. Defaults to “image/jpeg”
    titleStringOptional. Title for the result
    captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
    +

    InlineQueryResultVideo

    +

    Represents a link to a page containing an embedded video player or a video file. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

    +
    +

    If an InlineQueryResultVideo message contains an embedded video (e.g., YouTube), you must replace its content using input_message_content.

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be video
    idStringUnique identifier for this result, 1-64 bytes
    video_urlStringA valid URL for the embedded video player or video file
    mime_typeStringMime type of the content of video url, “text/html” or “video/mp4”
    thumb_urlStringURL of the thumbnail (JPEG only) for the video
    titleStringTitle for the result
    captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    video_widthIntegerOptional. Video width
    video_heightIntegerOptional. Video height
    video_durationIntegerOptional. Video duration in seconds
    descriptionStringOptional. Short description of the result
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video. This field is required if InlineQueryResultVideo is used to send an HTML-page as a result (e.g., a YouTube video).
    +

    InlineQueryResultAudio

    +

    Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be audio
    idStringUnique identifier for this result, 1-64 bytes
    audio_urlStringA valid URL for the audio file
    titleStringTitle
    captionStringOptional. Caption, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    performerStringOptional. Performer
    audio_durationIntegerOptional. Audio duration in seconds
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultVoice

    +

    Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be voice
    idStringUnique identifier for this result, 1-64 bytes
    voice_urlStringA valid URL for the voice recording
    titleStringRecording title
    captionStringOptional. Caption, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    voice_durationIntegerOptional. Recording duration in seconds
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice recording
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultDocument

    +

    Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be document
    idStringUnique identifier for this result, 1-64 bytes
    titleStringTitle for the result
    captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    document_urlStringA valid URL for the file
    mime_typeStringMime type of the content of the file, either “application/pdf” or “application/zip”
    descriptionStringOptional. Short description of the result
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
    thumb_urlStringOptional. URL of the thumbnail (JPEG only) for the file
    thumb_widthIntegerOptional. Thumbnail width
    thumb_heightIntegerOptional. Thumbnail height
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultLocation

    +

    Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be location
    idStringUnique identifier for this result, 1-64 Bytes
    latitudeFloat numberLocation latitude in degrees
    longitudeFloat numberLocation longitude in degrees
    titleStringLocation title
    horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
    live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
    headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
    proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the location
    thumb_urlStringOptional. Url of the thumbnail for the result
    thumb_widthIntegerOptional. Thumbnail width
    thumb_heightIntegerOptional. Thumbnail height
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultVenue

    +

    Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be venue
    idStringUnique identifier for this result, 1-64 Bytes
    latitudeFloatLatitude of the venue location in degrees
    longitudeFloatLongitude of the venue location in degrees
    titleStringTitle of the venue
    addressStringAddress of the venue
    foursquare_idStringOptional. Foursquare identifier of the venue if known
    foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
    google_place_idStringOptional. Google Places identifier of the venue
    google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the venue
    thumb_urlStringOptional. Url of the thumbnail for the result
    thumb_widthIntegerOptional. Thumbnail width
    thumb_heightIntegerOptional. Thumbnail height
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultContact

    +

    Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be contact
    idStringUnique identifier for this result, 1-64 Bytes
    phone_numberStringContact's phone number
    first_nameStringContact's first name
    last_nameStringOptional. Contact's last name
    vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the contact
    thumb_urlStringOptional. Url of the thumbnail for the result
    thumb_widthIntegerOptional. Thumbnail width
    thumb_heightIntegerOptional. Thumbnail height
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultGame

    +

    Represents a Game.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be game
    idStringUnique identifier for this result, 1-64 bytes
    game_short_nameStringShort name of the game
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    +

    Note: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them.

    +

    InlineQueryResultCachedPhoto

    +

    Represents a link to a photo stored on the Telegram servers. By default, this photo will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be photo
    idStringUnique identifier for this result, 1-64 bytes
    photo_file_idStringA valid file identifier of the photo
    titleStringOptional. Title for the result
    descriptionStringOptional. Short description of the result
    captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
    +

    InlineQueryResultCachedGif

    +

    Represents a link to an animated GIF file stored on the Telegram servers. By default, this animated GIF file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with specified content instead of the animation.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be gif
    idStringUnique identifier for this result, 1-64 bytes
    gif_file_idStringA valid file identifier for the GIF file
    titleStringOptional. Title for the result
    captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
    +

    InlineQueryResultCachedMpeg4Gif

    +

    Represents a link to a video animation (H.264/MPEG-4 AVC video without sound) stored on the Telegram servers. By default, this animated MPEG-4 file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be mpeg4_gif
    idStringUnique identifier for this result, 1-64 bytes
    mpeg4_file_idStringA valid file identifier for the MP4 file
    titleStringOptional. Title for the result
    captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
    +

    InlineQueryResultCachedSticker

    +

    Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be sticker
    idStringUnique identifier for this result, 1-64 bytes
    sticker_file_idStringA valid file identifier of the sticker
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the sticker
    +

    Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.

    +

    InlineQueryResultCachedDocument

    +

    Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be document
    idStringUnique identifier for this result, 1-64 bytes
    titleStringTitle for the result
    document_file_idStringA valid file identifier for the file
    descriptionStringOptional. Short description of the result
    captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultCachedVideo

    +

    Represents a link to a video file stored on the Telegram servers. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be video
    idStringUnique identifier for this result, 1-64 bytes
    video_file_idStringA valid file identifier for the video file
    titleStringTitle for the result
    descriptionStringOptional. Short description of the result
    captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video
    +

    InlineQueryResultCachedVoice

    +

    Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be voice
    idStringUnique identifier for this result, 1-64 bytes
    voice_file_idStringA valid file identifier for the voice message
    titleStringVoice message title
    captionStringOptional. Caption, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice message
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InlineQueryResultCachedAudio

    +

    Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringType of the result, must be audio
    idStringUnique identifier for this result, 1-64 bytes
    audio_file_idStringA valid file identifier for the audio file
    captionStringOptional. Caption, 0-1024 characters after entities parsing
    parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
    caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
    reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
    input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
    +

    Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

    +

    InputMessageContent

    +

    This object represents the content of a message to be sent as a result of an inline query. Telegram clients currently support the following 5 types:

    + +

    InputTextMessageContent

    +

    Represents the content of a text message to be sent as the result of an inline query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    message_textStringText of the message to be sent, 1-4096 characters
    parse_modeStringOptional. Mode for parsing entities in the message text. See formatting options for more details.
    entitiesArray of MessageEntityOptional. List of special entities that appear in message text, which can be specified instead of parse_mode
    disable_web_page_previewBooleanOptional. Disables link previews for links in the sent message
    +

    InputLocationMessageContent

    +

    Represents the content of a location message to be sent as the result of an inline query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    latitudeFloatLatitude of the location in degrees
    longitudeFloatLongitude of the location in degrees
    horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
    live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
    headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
    proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
    +

    InputVenueMessageContent

    +

    Represents the content of a venue message to be sent as the result of an inline query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    latitudeFloatLatitude of the venue in degrees
    longitudeFloatLongitude of the venue in degrees
    titleStringName of the venue
    addressStringAddress of the venue
    foursquare_idStringOptional. Foursquare identifier of the venue, if known
    foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
    google_place_idStringOptional. Google Places identifier of the venue
    google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
    +

    InputContactMessageContent

    +

    Represents the content of a contact message to be sent as the result of an inline query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    phone_numberStringContact's phone number
    first_nameStringContact's first name
    last_nameStringOptional. Contact's last name
    vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
    +

    InputInvoiceMessageContent

    +

    Represents the content of an invoice message to be sent as the result of an inline query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    titleStringProduct name, 1-32 characters
    descriptionStringProduct description, 1-255 characters
    payloadStringBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
    provider_tokenStringPayment provider token, obtained via Botfather
    currencyStringThree-letter ISO 4217 currency code, see more on currencies
    pricesArray of LabeledPricePrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
    max_tip_amountIntegerOptional. The maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_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). Defaults to 0
    suggested_tip_amountsArray of IntegerOptional. A JSON-serialized array of suggested amounts of tip in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
    provider_dataStringOptional. A JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
    photo_urlStringOptional. URL 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.
    photo_sizeIntegerOptional. Photo size
    photo_widthIntegerOptional. Photo width
    photo_heightIntegerOptional. Photo height
    need_nameBooleanOptional. Pass True, if you require the user's full name to complete the order
    need_phone_numberBooleanOptional. Pass True, if you require the user's phone number to complete the order
    need_emailBooleanOptional. Pass True, if you require the user's email address to complete the order
    need_shipping_addressBooleanOptional. Pass True, if you require the user's shipping address to complete the order
    send_phone_number_to_providerBooleanOptional. Pass True, if user's phone number should be sent to provider
    send_email_to_providerBooleanOptional. Pass True, if user's email address should be sent to provider
    is_flexibleBooleanOptional. Pass True, if the final price depends on the shipping method
    +

    ChosenInlineResult

    +

    Represents a result of an inline query that was chosen by the user and sent to their chat partner.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    result_idStringThe unique identifier for the result that was chosen
    fromUserThe user that chose the result
    locationLocationOptional. Sender location, only for bots that require user location
    inline_message_idStringOptional. Identifier 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.
    queryStringThe query that was used to obtain the result
    +

    Note: It is necessary to enable inline feedback via @Botfather in order to receive these objects in updates.

    +

    Payments

    +

    Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017).

    +

    sendInvoice

    +

    Use this method to send invoices. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
    titleStringYesProduct name, 1-32 characters
    descriptionStringYesProduct description, 1-255 characters
    payloadStringYesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
    provider_tokenStringYesPayments provider token, obtained via Botfather
    currencyStringYesThree-letter ISO 4217 currency code, see more on currencies
    pricesArray of LabeledPriceYesPrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
    max_tip_amountIntegerOptionalThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_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). Defaults to 0
    suggested_tip_amountsArray of IntegerOptionalA JSON-serialized array of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
    start_parameterStringOptionalUnique deep-linking parameter. If left empty, forwarded copies of the sent message will have a Pay button, allowing multiple users to pay directly from the forwarded message, using the same invoice. If non-empty, forwarded copies of the sent message will have a URL button with a deep link to the bot (instead of a Pay button), with the value used as the start parameter
    provider_dataStringOptionalA JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
    photo_urlStringOptionalURL 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.
    photo_sizeIntegerOptionalPhoto size
    photo_widthIntegerOptionalPhoto width
    photo_heightIntegerOptionalPhoto height
    need_nameBooleanOptionalPass True, if you require the user's full name to complete the order
    need_phone_numberBooleanOptionalPass True, if you require the user's phone number to complete the order
    need_emailBooleanOptionalPass True, if you require the user's email address to complete the order
    need_shipping_addressBooleanOptionalPass True, if you require the user's shipping address to complete the order
    send_phone_number_to_providerBooleanOptionalPass True, if user's phone number should be sent to provider
    send_email_to_providerBooleanOptionalPass True, if user's email address should be sent to provider
    is_flexibleBooleanOptionalPass True, if the final price depends on the shipping method
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Pay total price' button will be shown. If not empty, the first button must be a Pay button.
    +

    answerShippingQuery

    +

    If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the Bot API will send an Update with a shipping_query field to the bot. Use this method to reply to shipping queries. On success, True is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    shipping_query_idStringYesUnique identifier for the query to be answered
    okBooleanYesSpecify True if delivery to the specified address is possible and False if there are any problems (for example, if delivery to the specified address is not possible)
    shipping_optionsArray of ShippingOptionOptionalRequired if ok is True. A JSON-serialized array of available shipping options.
    error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
    +

    answerPreCheckoutQuery

    +

    Once the user has confirmed their payment and shipping details, the Bot API sends the final confirmation in the form of an Update with the field pre_checkout_query. Use this method to respond to such pre-checkout queries. On success, True is returned. Note: The Bot API must receive an answer within 10 seconds after the pre-checkout query was sent.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    pre_checkout_query_idStringYesUnique identifier for the query to be answered
    okBooleanYesSpecify True if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order. Use False if there are any problems.
    error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
    +

    LabeledPrice

    +

    This object represents a portion of the price for goods or services.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    labelStringPortion label
    amountIntegerPrice of the product 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).
    +

    Invoice

    +

    This object contains basic information about an invoice.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    titleStringProduct name
    descriptionStringProduct description
    start_parameterStringUnique bot deep-linking parameter that can be used to generate this invoice
    currencyStringThree-letter ISO 4217 currency code
    total_amountIntegerTotal 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).
    +

    ShippingAddress

    +

    This object represents a shipping address.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    country_codeStringISO 3166-1 alpha-2 country code
    stateStringState, if applicable
    cityStringCity
    street_line1StringFirst line for the address
    street_line2StringSecond line for the address
    post_codeStringAddress post code
    +

    OrderInfo

    +

    This object represents information about an order.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    nameStringOptional. User name
    phone_numberStringOptional. User's phone number
    emailStringOptional. User email
    shipping_addressShippingAddressOptional. User shipping address
    +

    ShippingOption

    +

    This object represents one shipping option.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idStringShipping option identifier
    titleStringOption title
    pricesArray of LabeledPriceList of price portions
    +

    SuccessfulPayment

    +

    This object contains basic information about a successful payment.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    currencyStringThree-letter ISO 4217 currency code
    total_amountIntegerTotal 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).
    invoice_payloadStringBot specified invoice payload
    shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
    order_infoOrderInfoOptional. Order info provided by the user
    telegram_payment_charge_idStringTelegram payment identifier
    provider_payment_charge_idStringProvider payment identifier
    +

    ShippingQuery

    +

    This object contains information about an incoming shipping query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idStringUnique query identifier
    fromUserUser who sent the query
    invoice_payloadStringBot specified invoice payload
    shipping_addressShippingAddressUser specified shipping address
    +

    PreCheckoutQuery

    +

    This object contains information about an incoming pre-checkout query.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    idStringUnique query identifier
    fromUserUser who sent the query
    currencyStringThree-letter ISO 4217 currency code
    total_amountIntegerTotal 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).
    invoice_payloadStringBot specified invoice payload
    shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
    order_infoOrderInfoOptional. Order info provided by the user
    +

    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.). Please see the manual for details.

    +

    PassportData

    +

    Contains information about Telegram Passport data shared with the bot by the user.

    + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    dataArray of EncryptedPassportElementArray with information about documents and other Telegram Passport elements that was shared with the bot
    credentialsEncryptedCredentialsEncrypted credentials required to decrypt the data
    +

    PassportFile

    +

    This object represents a file uploaded to Telegram Passport. Currently all Telegram Passport files are in JPEG format when decrypted and don't exceed 10MB.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    file_idStringIdentifier for this file, which can be used to download or reuse the file
    file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
    file_sizeIntegerFile size in bytes
    file_dateIntegerUnix time when the file was uploaded
    +

    EncryptedPassportElement

    +

    Contains information about documents or other Telegram Passport elements shared with the bot by the user.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    typeStringElement type. One of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”, “phone_number”, “email”.
    dataStringOptional. Base64-encoded encrypted Telegram Passport element data provided by the user, available for “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport” and “address” types. Can be decrypted and verified using the accompanying EncryptedCredentials.
    phone_numberStringOptional. User's verified phone number, available only for “phone_number” type
    emailStringOptional. User's verified email address, available only for “email” type
    filesArray of PassportFileOptional. Array of encrypted files with documents provided by the user, available for “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration” and “temporary_registration” types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
    front_sidePassportFileOptional. Encrypted file with the front side of the document, provided by the user. Available for “passport”, “driver_license”, “identity_card” and “internal_passport”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
    reverse_sidePassportFileOptional. Encrypted file with the reverse side of the document, provided by the user. Available for “driver_license” and “identity_card”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
    selfiePassportFileOptional. Encrypted file with the selfie of the user holding a document, provided by the user; available for “passport”, “driver_license”, “identity_card” and “internal_passport”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
    translationArray of PassportFileOptional. Array of encrypted files with translated versions of documents provided by the user. Available if requested for “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration” and “temporary_registration” types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
    hashStringBase64-encoded element hash for using in PassportElementErrorUnspecified
    +

    EncryptedCredentials

    +

    Contains data required for decrypting and authenticating EncryptedPassportElement. See the Telegram Passport Documentation for a complete description of the data decryption and authentication processes.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    dataStringBase64-encoded encrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication
    hashStringBase64-encoded data hash for data authentication
    secretStringBase64-encoded secret, encrypted with the bot's public RSA key, required for data decryption
    +

    setPassportDataErrors

    +

    Informs a user that some of the Telegram Passport elements they provided contains errors. The user will not be able to re-submit their Passport to you until the errors are fixed (the contents of the field for which you returned the error must change). Returns True on success.

    +

    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.

    + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesUser identifier
    errorsArray of PassportElementErrorYesA JSON-serialized array describing the errors
    +

    PassportElementError

    +

    This object represents an error in the Telegram Passport element which was submitted that should be resolved by the user. It should be one of:

    + +

    PassportElementErrorDataField

    +

    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.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be data
    typeStringThe section of the user's Telegram Passport which has the error, one of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”
    field_nameStringName of the data field which has the error
    data_hashStringBase64-encoded data hash
    messageStringError message
    +

    PassportElementErrorFrontSide

    +

    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.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be front_side
    typeStringThe section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
    file_hashStringBase64-encoded hash of the file with the front side of the document
    messageStringError message
    +

    PassportElementErrorReverseSide

    +

    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.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be reverse_side
    typeStringThe section of the user's Telegram Passport which has the issue, one of “driver_license”, “identity_card”
    file_hashStringBase64-encoded hash of the file with the reverse side of the document
    messageStringError message
    +

    PassportElementErrorSelfie

    +

    Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be selfie
    typeStringThe section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
    file_hashStringBase64-encoded hash of the file with the selfie
    messageStringError message
    +

    PassportElementErrorFile

    +

    Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be file
    typeStringThe section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
    file_hashStringBase64-encoded file hash
    messageStringError message
    +

    PassportElementErrorFiles

    +

    Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be files
    typeStringThe section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
    file_hashesArray of StringList of base64-encoded file hashes
    messageStringError message
    +

    PassportElementErrorTranslationFile

    +

    Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be translation_file
    typeStringType of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
    file_hashStringBase64-encoded file hash
    messageStringError message
    +

    PassportElementErrorTranslationFiles

    +

    Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation change.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be translation_files
    typeStringType of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
    file_hashesArray of StringList of base64-encoded file hashes
    messageStringError message
    +

    PassportElementErrorUnspecified

    +

    Represents an issue in an unspecified place. The error is considered resolved when new data is added.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sourceStringError source, must be unspecified
    typeStringType of element of the user's Telegram Passport which has the issue
    element_hashStringBase64-encoded element hash
    messageStringError message
    +

    Games

    +

    Your bot can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Create games via @BotFather using the /newgame command. Please note that this kind of power requires responsibility: you will need to accept the terms for each game that your bots will be offering.

    +
      +
    • Games are a new type of content on Telegram, represented by the Game and InlineQueryResultGame objects.
      • +
    • Once you've created a game via BotFather, you can send games to chats as regular messages using the sendGame method, or use inline mode with InlineQueryResultGame.
      • +
    • If you send the game message without any buttons, it will automatically have a 'Play GameName' button. When this button is pressed, your bot gets a CallbackQuery with the game_short_name of the requested game. You provide the correct URL for this particular user and the app opens the game in the in-app browser.
      • +
    • You can manually add multiple buttons to your game message. Please note that the first button in the first row must always launch the game, using the field callback_game in InlineKeyboardButton. You can add extra buttons according to taste: e.g., for a description of the rules, or to open the game's official community.
      • +
    • To make your game more attractive, you can upload a GIF animation that demostrates the game to the users via BotFather (see Lumberjack for example).
      • +
    • A game message will also display high scores for the current chat. Use setGameScore to post high scores to the chat with the game, add the edit_message parameter to automatically update the message with the current scoreboard.
      • +
    • Use getGameHighScores to get data for in-game high score tables.
      • +
    • You can also add an extra sharing button for users to share their best score to different chats.
      • +
    • For examples of what can be done using this new stuff, check the @gamebot and @gamee bots.
      • +
    +

    sendGame

    +

    Use this method to send a game. On success, the sent Message is returned.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    chat_idIntegerYesUnique identifier for the target chat
    game_short_nameStringYesShort name of the game, serves as the unique identifier for the game. Set up your games via Botfather.
    disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
    protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
    reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
    allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
    reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Play game_title' button will be shown. If not empty, the first button must launch the game.
    +

    Game

    +

    This object represents a game. Use BotFather to create and edit games, their short names will act as unique identifiers.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    titleStringTitle of the game
    descriptionStringDescription of the game
    photoArray of PhotoSizePhoto that will be displayed in the game message in chats.
    textStringOptional. Brief description of the game or high scores included in the game message. Can be automatically edited to include current high scores for the game when the bot calls setGameScore, or manually edited using editMessageText. 0-4096 characters.
    text_entitiesArray of MessageEntityOptional. Special entities that appear in text, such as usernames, URLs, bot commands, etc.
    animationAnimationOptional. Animation that will be displayed in the game message in chats. Upload via BotFather
    +

    CallbackGame

    +

    A placeholder, currently holds no information. Use BotFather to set up your game.

    +

    setGameScore

    +

    Use this method to set the score of the specified user in a game message. On success, if the message is not an inline message, the Message is returned, otherwise True is returned. Returns an error, if the new score is not greater than the user's current score in the chat and force is False.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesUser identifier
    scoreIntegerYesNew score, must be non-negative
    forceBooleanOptionalPass True, if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
    disable_edit_messageBooleanOptionalPass True, if the game message should not be automatically edited to include the current scoreboard
    chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    +

    getGameHighScores

    +

    Use this method to get data for high score tables. Will return the score of the specified user and several of their neighbors in a game. On success, returns an Array of GameHighScore objects.

    +
    +

    This method will currently return scores for the target user, plus two of their closest neighbors on each side. Will also return the top three users if the user and his neighbors are not among them. Please note that this behavior is subject to change.

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterTypeRequiredDescription
    user_idIntegerYesTarget user id
    chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
    message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
    inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
    +

    GameHighScore

    +

    This object represents one row of the high scores table for a game.

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    positionIntegerPosition in high score table for the game
    userUserUser
    scoreIntegerScore
    +
    +

    And that's about all we've got for now.
    If you've got any questions, please check out our Bot FAQ »

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/core.telegram.org/bots/inline.html b/data/core.telegram.org/bots/inline.html new file mode 100644 index 0000000000..3bf2192115 --- /dev/null +++ b/data/core.telegram.org/bots/inline.html @@ -0,0 +1,182 @@ + + + + + Inline Bots + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Inline Bots

    + +
    + +
    + +
    + +

    Beyond sending commands in private messages or groups, users can interact with your bot via inline queries. If inline queries are enabled, users can call your bot by typing its username and a query in the text input field in any chat. The query is sent to your bot in an update. This way, people can request content from your bot in any of their chats, groups, or channels without sending any messages at all.

    +
    +
    +
    + + +

    To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot’s name.

    +
    +

    See the Bot API Manual for the relevant methods and objects.

    +
    +

    Inline results

    +

    Inline bots support all types of content available in Telegram (20 in all). They are capable of sending stickers, videos, music, locations, documents and more.

    +
    +

    +
    + +

    Clients can display the results with vertical or horizontal scrolling, depending on the type of content:

    +
    + + + + + +
    +
    + +

    As soon as the user taps on an item, it's immediately sent to the recipient, and the input field is cleared.

    +

    Switching inline/PM modes

    +

    Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

    +
    +

    +
    + +

    You can display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

    +

    Sample bots
    @youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

    +
    +

    Manual: Switch to PM

    +
    +

    Location-based results

    +

    Inline bots can request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

    +

    Sample bot
    @foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

    +

    Spreading virally

    +

    Messages sent with the help of your bot will show its username next to the sender's name.

    +
    + + + + + +

    + +

    When a user taps on the bot username in the message header, the mention is automatically inserted into the input field. Entering the @ symbol in the input field brings up a list of suggestions, featuring recently used inline bots.

    +

    Collecting feedback

    +

    To know which of the provided results your users are sending to their chat partners, send @Botfather the /setinlinefeedback command. With this enabled, you will receive updates on the results chosen by your users.

    +

    Please note that this can create load issues for popular bots – you may receive more results than actual requests due to caching (see the cache_time parameter in answerInlineQuery). For these cases, we recommend adjusting the probability setting to receive 1/10, 1/100 or 1/1000 of the results.

    +

    Inline bot samples

    +

    Here are some sample inline bots, in case you’re curious to see one in action. Try any of these:
    @gif – GIF search
    @vid – Video search
    @pic – Yandex image search
    @bing – Bing image search
    @wiki – Wikipedia search
    @imdb – IMDB search
    @bold – Make bold, italic or fixed sys text

    +

    NEW
    @youtube - Connect your account for personalized results
    @music - Search and send classical music
    @foursquare – Find and send venue addresses
    @sticker – Find and send stickers based on emoji

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/core.telegram.org/constructor/account.authorizationForm b/data/core.telegram.org/constructor/account.authorizationForm deleted file mode 100644 index f12161fe65..0000000000 --- a/data/core.telegram.org/constructor/account.authorizationForm +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.authorizationForm - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    account.authorizationForm

    - -

    Telegram Passport authorization 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;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    flags#Flags, see TL conditional fields
    required_typesVector<SecureRequiredType>Required Telegram Passport documents
    valuesVector<SecureValue>Already submitted Telegram Passport documents
    errorsVector<SecureValueError>Telegram Passport errors
    usersVector<User>Info about the bot to which the form will be submitted
    privacy_policy_urlflags.0?stringURL of the service's privacy policy
    -

    Type

    -

    account.AuthorizationForm

    -

    Related pages

    -

    Telegram Passport Manual

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeCall b/data/core.telegram.org/constructor/auth.codeTypeCall deleted file mode 100644 index bceaa717e7..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/auth.passwordRecovery b/data/core.telegram.org/constructor/auth.passwordRecovery deleted file mode 100644 index be4437c0a7..0000000000 --- a/data/core.telegram.org/constructor/auth.passwordRecovery +++ /dev/null @@ -1,152 +0,0 @@ - - - - - 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;

    -

    Parameters

    - - - - - - - - - - - - - - - -
    NameTypeDescription
    email_patternstringThe email to which the recovery code was sent must match this pattern.
    -

    Type

    -

    auth.PasswordRecovery

    -

    Related pages

    -

    Pattern matching

    -

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

    -

    Two-factor authentication

    -

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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeTinted.html b/data/core.telegram.org/constructor/baseThemeTinted.html deleted file mode 100644 index bc4dea5385..0000000000 --- a/data/core.telegram.org/constructor/baseThemeTinted.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeTinted - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    baseThemeTinted

    - -

    Tinted theme

    -

    - -
    -
    baseThemeTinted#6d5f77ee = BaseTheme;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    BaseTheme

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/boolTrue.html b/data/core.telegram.org/constructor/boolTrue.html deleted file mode 100644 index 76b69b97b1..0000000000 --- a/data/core.telegram.org/constructor/boolTrue.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolTrue - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    boolTrue

    - -

    The constructor can be interpreted as a booleantrue value.

    -

    - -
    -
    boolTrue#997275b5 = Bool;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    Bool

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html b/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html deleted file mode 100644 index 09ed3db8d4..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - botCommandScopePeerAdmins - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    botCommandScopePeerAdmins

    - -

    The specified bot commands will be valid for all admins of the specified group or supergroup.

    -

    - -
    -
    botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;

    -

    Parameters

    - - - - - - - - - - - - - - - -
    NameTypeDescription
    peerInputPeerThe chat
    -

    Type

    -

    BotCommandScope

    -

    Related pages

    -

    Channels

    -

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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/channel.html b/data/core.telegram.org/constructor/channel.html deleted file mode 100644 index 73ec97d243..0000000000 --- a/data/core.telegram.org/constructor/channel.html +++ /dev/null @@ -1,289 +0,0 @@ - - - - - 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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html deleted file mode 100644 index 827058690a..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/contacts.contactsNotModified b/data/core.telegram.org/constructor/contacts.contactsNotModified deleted file mode 100644 index bb513a2e67..0000000000 --- a/data/core.telegram.org/constructor/contacts.contactsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.contactsNotModified - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    contacts.contactsNotModified

    - -

    Contact list on the server is the same as the list on the client.

    -

    - -
    -
    contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    contacts.Contacts

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html b/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html deleted file mode 100644 index 8bd08c313d..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - decryptedMessageMediaAudio - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    decryptedMessageMediaAudio

    - -

    Audio file attached to a secret chat message.

    -

    - -
    -
    ===8===
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    durationintAudio duration in seconds
    mime_typestringMIME-type of the audio file
    Parameter added in Layer 13.
    sizeintFile size
    keybytesKey to decrypt the attached media file
    ivbytesInitialization vector
    -

    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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypePM.html b/data/core.telegram.org/constructor/inlineQueryPeerTypePM.html deleted file mode 100644 index fde1ebb46c..0000000000 --- a/data/core.telegram.org/constructor/inlineQueryPeerTypePM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inlineQueryPeerTypePM - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    inlineQueryPeerTypePM

    - -

    The inline query was sent in a private chat

    -

    - -
    -
    inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    InlineQueryPeerType

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/inputFileLocation.html b/data/core.telegram.org/constructor/inputFileLocation.html deleted file mode 100644 index 80d6f2e22e..0000000000 --- a/data/core.telegram.org/constructor/inputFileLocation.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputFileLocation - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    inputFileLocation

    - -

    DEPRECATED location of a photo

    -

    - -
    -
    inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    volume_idlongServer volume
    local_idintFile identifier
    secretlongCheck sum to access the file
    file_referencebytesFile reference
    -

    Type

    -

    InputFileLocation

    -

    Related pages

    -

    File references

    -

    How to handle file references.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html deleted file mode 100644 index 2de7853f5c..0000000000 --- a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - 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 »

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/userEmpty.html b/data/core.telegram.org/constructor/inputMediaGeoPoint.html similarity index 91% rename from data/core.telegram.org/constructor/userEmpty.html rename to data/core.telegram.org/constructor/inputMediaGeoPoint.html index 191eeda7c8..5a5dc83319 100644 --- a/data/core.telegram.org/constructor/userEmpty.html +++ b/data/core.telegram.org/constructor/inputMediaGeoPoint.html @@ -2,12 +2,12 @@ - userEmpty + inputMediaGeoPoint - - + + - + @@ -36,10 +36,10 @@
    -
    -

    userEmpty

    +
    +

    inputMediaGeoPoint

    -

    Empty constructor, non-existent user.

    +

    Map.

    • @@ -52,7 +52,7 @@
    -
    userEmpty#d3bc4b7a id:long = User;

    +
    inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;

    Parameters

    @@ -64,14 +64,14 @@ - - - + + +
    idlongUser identifier or 0geo_pointInputGeoPointGeoPoint

    Type

    -

    User

    +

    InputMedia

    diff --git a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html b/data/core.telegram.org/constructor/inputReportReasonPornography.html similarity index 91% rename from data/core.telegram.org/constructor/privacyValueDisallowContacts.html rename to data/core.telegram.org/constructor/inputReportReasonPornography.html index 40cb335dcd..daa10d7d5c 100644 --- a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html +++ b/data/core.telegram.org/constructor/inputReportReasonPornography.html @@ -2,12 +2,12 @@ - privacyValueDisallowContacts + inputReportReasonPornography - - + + - + @@ -36,10 +36,10 @@
    -
    -

    privacyValueDisallowContacts

    +
    +

    inputReportReasonPornography

    -

    Disallow only contacts

    +

    Report for pornography

    • @@ -52,11 +52,11 @@
    -
    privacyValueDisallowContacts#f888fa1a = PrivacyRule;

    +
    inputReportReasonPornography#2e59d922 = ReportReason;

    Parameters

    This constructor does not require any parameters.

    Type

    -

    PrivacyRule

    +

    ReportReason

    diff --git a/data/core.telegram.org/constructor/messageActionInviteToGroupCall.html b/data/core.telegram.org/constructor/messageActionInviteToGroupCall.html deleted file mode 100644 index 84c058c54f..0000000000 --- a/data/core.telegram.org/constructor/messageActionInviteToGroupCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html b/data/core.telegram.org/constructor/messageActionPaymentSentMe.html deleted file mode 100644 index ad0a6554e0..0000000000 --- a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messageActionPaymentSentMe - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    messageActionPaymentSentMe

    - -

    A user just sent a payment to me (a bot)

    -

    - -
    -
    messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    flags#Flags, see TL conditional fields
    currencystringThree-letter ISO 4217 currency code
    total_amountlongPrice of the product 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).
    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
    chargePaymentChargeProvider payment identifier
    -

    Type

    -

    MessageAction

    -

    Related pages

    -

    Bot Payments API

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/messages.allStickersNotModified b/data/core.telegram.org/constructor/messages.allStickersNotModified deleted file mode 100644 index 180d8a43b8..0000000000 --- a/data/core.telegram.org/constructor/messages.allStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/messages.exportedChatInvite b/data/core.telegram.org/constructor/messages.exportedChatInvite deleted file mode 100644 index 8d965aabd0..0000000000 --- a/data/core.telegram.org/constructor/messages.exportedChatInvite +++ /dev/null @@ -1,152 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/peerNotifySettings.html b/data/core.telegram.org/constructor/peerNotifySettings.html deleted file mode 100644 index 1a8febde59..0000000000 --- a/data/core.telegram.org/constructor/peerNotifySettings.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - 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
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeAddress.html b/data/core.telegram.org/constructor/secureValueTypeAddress.html deleted file mode 100644 index d83a0b1593..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeAddress.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeAddress - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    secureValueTypeAddress

    - -

    Address

    -

    - -
    -
    secureValueTypeAddress#cbe31e26 = SecureValueType;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    SecureValueType

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html deleted file mode 100644 index 7312f9e65f..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeTemporaryRegistration - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    secureValueTypeTemporaryRegistration

    - -

    Temporary registration

    -

    - -
    -
    secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    SecureValueType

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/textUnderline.html b/data/core.telegram.org/constructor/statsURL.html similarity index 91% rename from data/core.telegram.org/constructor/textUnderline.html rename to data/core.telegram.org/constructor/statsURL.html index 3ad40497c0..896601ca9f 100644 --- a/data/core.telegram.org/constructor/textUnderline.html +++ b/data/core.telegram.org/constructor/statsURL.html @@ -2,12 +2,12 @@ - textUnderline + statsURL - - + + - + @@ -36,10 +36,10 @@
    -
    -

    textUnderline

    +
    +

    statsURL

    -

    Underlined text

    +

    URL with chat statistics

    • @@ -52,7 +52,7 @@
    -
    textUnderline#c12622c4 text:RichText = RichText;

    +
    statsURL#47a971e0 url:string = StatsURL;

    Parameters

    @@ -64,14 +64,14 @@ - - - + + +
    textRichTextTexturlstringChat statistics

    Type

    -

    RichText

    +

    StatsURL

    diff --git a/data/corefork.telegram.org/constructor/langPackLanguage.html b/data/core.telegram.org/constructor/stickerSet.html similarity index 73% rename from data/corefork.telegram.org/constructor/langPackLanguage.html rename to data/core.telegram.org/constructor/stickerSet.html index 4494b0d4a7..df7e9e3c08 100644 --- a/data/corefork.telegram.org/constructor/langPackLanguage.html +++ b/data/core.telegram.org/constructor/stickerSet.html @@ -2,12 +2,12 @@ - langPackLanguage + stickerSet - - + + - + @@ -36,10 +36,10 @@
    -
    -

    langPackLanguage

    +
    +

    stickerSet

    -

    Identifies a localization pack

    +

    Represents a stickerset (stickerpack)

    • @@ -52,7 +52,7 @@
    -
    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;

    +
    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

    @@ -69,64 +69,79 @@ + + + + + - - - - - - + - + - + - + + + + + + + + + + + + + + + + + + + + + - + - + - + - - - + + + - - - + + + - - - + + + - + - + - + - - - - - - +
    Flags, see TL conditional fields
    archivedflags.1?trueWhether this stickerset was archived (due to too many saved stickers in the current account)
    officialflags.0?trueWhether the language pack is official
    rtl flags.2?trueIs this a localization pack for an RTL languageIs this stickerset official
    betamasks flags.3?trueIs this a beta localization pack?Is this a mask stickerset
    nameanimatedflags.5?trueIs this an animated stickerpack
    installed_dateflags.0?intWhen was this stickerset installed
    idlongID of the stickerset
    access_hashlongAccess hash of stickerset
    title stringLanguage nameTitle of stickerset
    native_nameshort_name stringLanguage name in the language itselfShort name of stickerset to use in tg://addstickers?set=short_name
    lang_codestringLanguage code (pack identifier)thumbsflags.4?Vector<PhotoSize>Stickerset thumbnail
    base_lang_codeflags.1?stringIdentifier of a base language pack; may be empty. If a string is missed in the language pack, then it should be fetched from base language pack. Unsupported in custom language packsthumb_dc_idflags.4?intDC ID of thumbnail
    plural_codestringA language code to be used to apply plural forms. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more infothumb_versionflags.4?intThumbnail version
    strings_countcount intTotal number of non-deleted strings from the language packNumber of stickers in pack
    translated_counthash intTotal number of translated strings from the language pack
    translations_urlstringLink to language translation interface; empty for custom local language packsHash

    Type

    -

    LangPackLanguage

    +

    StickerSet

    @@ -165,9 +180,9 @@
    -
    Platform
    +
    Platform
    @@ -184,7 +199,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html similarity index 92% rename from data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html rename to data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html index fcb286ba72..426095f2a6 100644 --- a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html +++ b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html @@ -2,12 +2,12 @@ - topPeerCategoryForwardUsers + topPeerCategoryCorrespondents - - + + - + @@ -36,10 +36,10 @@
    -
    -

    topPeerCategoryForwardUsers

    +
    +

    topPeerCategoryCorrespondents

    -

    Users to which the users often forwards messages to

    +

    Users we've chatted most frequently with

    • @@ -52,7 +52,7 @@
    -
    topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

    +
    topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;

    Parameters

    This constructor does not require any parameters.

    Type

    diff --git a/data/core.telegram.org/constructor/updateChannelTooLong.html b/data/core.telegram.org/constructor/updateChannelTooLong.html deleted file mode 100644 index 7e001417d8..0000000000 --- a/data/core.telegram.org/constructor/updateChannelTooLong.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - updateChannelTooLong - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    updateChannelTooLong

    - -

    There are new updates in the specified channel, the client must fetch them.
    -If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.

    -

    - -
    -
    updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    flags#Flags, see TL conditional fields
    channel_idlongThe channel
    ptsflags.0?intThe PTS.
    -

    Type

    -

    Update

    -

    Related pages

    -

    Working with Updates

    -

    How to subscribe to updates and handle them properly.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/photoSizeEmpty.html b/data/core.telegram.org/constructor/updateDialogFilterOrder.html similarity index 86% rename from data/core.telegram.org/constructor/photoSizeEmpty.html rename to data/core.telegram.org/constructor/updateDialogFilterOrder.html index f32028a6ae..0cec4f5e97 100644 --- a/data/core.telegram.org/constructor/photoSizeEmpty.html +++ b/data/core.telegram.org/constructor/updateDialogFilterOrder.html @@ -2,12 +2,12 @@ - photoSizeEmpty + updateDialogFilterOrder - - + + - + @@ -36,10 +36,10 @@
    -
    -

    photoSizeEmpty

    +
    +

    updateDialogFilterOrder

    -

    Empty constructor. Image with this thumbnail is unavailable.

    +

    New folder order

    • @@ -52,7 +52,7 @@
    -
    photoSizeEmpty#e17e23c type:string = PhotoSize;

    +
    updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

    Parameters

    @@ -64,17 +64,17 @@ - - - + + +
    typestringThumbnail type (see. photoSize)orderVector<int>Ordered folder IDs

    Type

    -

    PhotoSize

    +

    Update

    Related pages

    -

    photoSize

    -

    Image description.

    +

    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/decryptedMessageActionDeleteMessages.html b/data/core.telegram.org/constructor/upload.file similarity index 87% rename from data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html rename to data/core.telegram.org/constructor/upload.file index 694a95b7da..aff8630cd4 100644 --- a/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html +++ b/data/core.telegram.org/constructor/upload.file @@ -2,12 +2,12 @@ - decryptedMessageActionDeleteMessages + upload.file - - + + - + @@ -36,10 +36,10 @@
    -
    -

    decryptedMessageActionDeleteMessages

    +
    +

    upload.file

    -

    Deleted messages.

    +

    File content.

    • @@ -52,8 +52,7 @@
    -
    ===8===
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;

    +
    upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

    Parameters

    @@ -65,14 +64,24 @@ - - - + + + + + + + + + + + + +
    random_idsVector<long>List of deleted message IDstypestorage.FileTypeFile type
    mtimeintModification type
    bytesbytesBinary data, file content

    Type

    -

    DecryptedMessageAction

    +

    upload.File

    diff --git a/data/core.telegram.org/contest300K.html b/data/core.telegram.org/contest300K.html deleted file mode 100644 index 86ddea9c34..0000000000 --- a/data/core.telegram.org/contest300K.html +++ /dev/null @@ -1,237 +0,0 @@ - - - - - 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.

    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/css/bootstrap-extra.css b/data/core.telegram.org/css/bootstrap-extra.css deleted file mode 100644 index 8a35b6069b..0000000000 --- a/data/core.telegram.org/css/bootstrap-extra.css +++ /dev/null @@ -1,3274 +0,0 @@ -/* glyph */ -@font-face { - font-family: 'Glyphicons Halflings'; - src: url('../fonts/glyphicons-halflings-regular.eot'); - src: url('../fonts/glyphicons-halflings-regular.eot?#iefix') format('embedded-opentype'), url('../fonts/glyphicons-halflings-regular.woff') format('woff'), url('../fonts/glyphicons-halflings-regular.ttf') format('truetype'), url('../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular') format('svg'); -} -.glyphicon { - position: relative; - top: 1px; - display: inline-block; - font-family: 'Glyphicons Halflings'; - font-style: normal; - font-weight: normal; - line-height: 1; - -webkit-font-smoothing: antialiased; - -moz-osx-font-smoothing: grayscale; -} -.glyphicon-asterisk:before { - content: "\2a"; -} -.glyphicon-plus:before { - content: "\2b"; -} -.glyphicon-euro:before { - content: "\20ac"; -} -.glyphicon-minus:before { - content: "\2212"; -} -.glyphicon-cloud:before { - content: "\2601"; -} -.glyphicon-envelope:before { - content: "\2709"; -} -.glyphicon-pencil:before { - content: "\270f"; -} -.glyphicon-glass:before { - content: "\e001"; -} -.glyphicon-music:before { - content: "\e002"; -} -.glyphicon-search:before { - content: "\e003"; -} -.glyphicon-heart:before { - content: "\e005"; -} -.glyphicon-star:before { - content: "\e006"; -} -.glyphicon-star-empty:before { - content: "\e007"; -} -.glyphicon-user:before { - content: "\e008"; -} -.glyphicon-film:before { - content: "\e009"; -} -.glyphicon-th-large:before { - content: "\e010"; -} -.glyphicon-th:before { - content: "\e011"; -} -.glyphicon-th-list:before { - content: "\e012"; -} -.glyphicon-ok:before { - content: "\e013"; -} -.glyphicon-remove:before { - content: "\e014"; -} -.glyphicon-zoom-in:before { - content: "\e015"; -} -.glyphicon-zoom-out:before { - content: "\e016"; -} -.glyphicon-off:before { - content: "\e017"; -} -.glyphicon-signal:before { - content: "\e018"; -} -.glyphicon-cog:before { - content: "\e019"; -} -.glyphicon-trash:before { - content: "\e020"; -} -.glyphicon-home:before { - content: "\e021"; -} -.glyphicon-file:before { - content: "\e022"; -} -.glyphicon-time:before { - content: "\e023"; -} -.glyphicon-road:before { - content: "\e024"; -} -.glyphicon-download-alt:before { - content: "\e025"; -} -.glyphicon-download:before { - content: "\e026"; -} -.glyphicon-upload:before { - content: "\e027"; -} -.glyphicon-inbox:before { - content: "\e028"; -} -.glyphicon-play-circle:before { - content: "\e029"; -} -.glyphicon-repeat:before { - content: "\e030"; -} -.glyphicon-refresh:before { - content: "\e031"; -} -.glyphicon-list-alt:before { - content: "\e032"; -} -.glyphicon-lock:before { - content: "\e033"; -} -.glyphicon-flag:before { - content: "\e034"; -} -.glyphicon-headphones:before { - content: "\e035"; -} -.glyphicon-volume-off:before { - content: "\e036"; -} -.glyphicon-volume-down:before { - content: "\e037"; -} -.glyphicon-volume-up:before { - content: "\e038"; -} -.glyphicon-qrcode:before { - content: "\e039"; -} -.glyphicon-barcode:before { - content: "\e040"; -} -.glyphicon-tag:before { - content: "\e041"; -} -.glyphicon-tags:before { - content: "\e042"; -} -.glyphicon-book:before { - content: "\e043"; -} -.glyphicon-bookmark:before { - content: "\e044"; -} -.glyphicon-print:before { - content: "\e045"; -} -.glyphicon-camera:before { - content: "\e046"; -} -.glyphicon-font:before { - content: "\e047"; -} -.glyphicon-bold:before { - content: "\e048"; -} -.glyphicon-italic:before { - content: "\e049"; -} -.glyphicon-text-height:before { - content: "\e050"; -} -.glyphicon-text-width:before { - content: "\e051"; -} -.glyphicon-align-left:before { - content: "\e052"; -} -.glyphicon-align-center:before { - content: "\e053"; -} -.glyphicon-align-right:before { - content: "\e054"; -} -.glyphicon-align-justify:before { - content: "\e055"; -} -.glyphicon-list:before { - content: "\e056"; -} -.glyphicon-indent-left:before { - content: "\e057"; -} -.glyphicon-indent-right:before { - content: "\e058"; -} -.glyphicon-facetime-video:before { - content: "\e059"; -} -.glyphicon-picture:before { - content: "\e060"; -} -.glyphicon-map-marker:before { - content: "\e062"; -} -.glyphicon-adjust:before { - content: "\e063"; -} -.glyphicon-tint:before { - content: "\e064"; -} -.glyphicon-edit:before { - content: "\e065"; -} -.glyphicon-share:before { - content: "\e066"; -} -.glyphicon-check:before { - content: "\e067"; -} -.glyphicon-move:before { - content: "\e068"; -} -.glyphicon-step-backward:before { - content: "\e069"; -} -.glyphicon-fast-backward:before { - content: "\e070"; -} -.glyphicon-backward:before { - content: "\e071"; -} -.glyphicon-play:before { - content: "\e072"; -} -.glyphicon-pause:before { - content: "\e073"; -} -.glyphicon-stop:before { - content: "\e074"; -} -.glyphicon-forward:before { - content: "\e075"; -} -.glyphicon-fast-forward:before { - content: "\e076"; -} -.glyphicon-step-forward:before { - content: "\e077"; -} -.glyphicon-eject:before { - content: "\e078"; -} -.glyphicon-chevron-left:before { - content: "\e079"; -} -.glyphicon-chevron-right:before { - content: "\e080"; -} -.glyphicon-plus-sign:before { - content: "\e081"; -} -.glyphicon-minus-sign:before { - content: "\e082"; -} -.glyphicon-remove-sign:before { - content: "\e083"; -} -.glyphicon-ok-sign:before { - content: "\e084"; -} -.glyphicon-question-sign:before { - content: "\e085"; -} -.glyphicon-info-sign:before { - content: "\e086"; -} -.glyphicon-screenshot:before { - content: "\e087"; -} -.glyphicon-remove-circle:before { - content: "\e088"; -} -.glyphicon-ok-circle:before { - content: "\e089"; -} -.glyphicon-ban-circle:before { - content: "\e090"; -} -.glyphicon-arrow-left:before { - content: "\e091"; -} -.glyphicon-arrow-right:before { - content: "\e092"; -} -.glyphicon-arrow-up:before { - content: "\e093"; -} -.glyphicon-arrow-down:before { - content: "\e094"; -} -.glyphicon-share-alt:before { - content: "\e095"; -} -.glyphicon-resize-full:before { - content: "\e096"; -} -.glyphicon-resize-small:before { - content: "\e097"; -} -.glyphicon-exclamation-sign:before { - content: "\e101"; -} -.glyphicon-gift:before { - content: "\e102"; -} -.glyphicon-leaf:before { - content: "\e103"; -} -.glyphicon-fire:before { - content: "\e104"; -} -.glyphicon-eye-open:before { - content: "\e105"; -} -.glyphicon-eye-close:before { - content: "\e106"; -} -.glyphicon-warning-sign:before { - content: "\e107"; -} -.glyphicon-plane:before { - content: "\e108"; -} -.glyphicon-calendar:before { - content: "\e109"; -} -.glyphicon-random:before { - content: "\e110"; -} -.glyphicon-comment:before { - content: "\e111"; -} -.glyphicon-magnet:before { - content: "\e112"; -} -.glyphicon-chevron-up:before { - content: "\e113"; -} -.glyphicon-chevron-down:before { - content: "\e114"; -} -.glyphicon-retweet:before { - content: "\e115"; -} -.glyphicon-shopping-cart:before { - content: "\e116"; -} -.glyphicon-folder-close:before { - content: "\e117"; -} -.glyphicon-folder-open:before { - content: "\e118"; -} -.glyphicon-resize-vertical:before { - content: "\e119"; -} -.glyphicon-resize-horizontal:before { - content: "\e120"; -} -.glyphicon-hdd:before { - content: "\e121"; -} -.glyphicon-bullhorn:before { - content: "\e122"; -} -.glyphicon-bell:before { - content: "\e123"; -} -.glyphicon-certificate:before { - content: "\e124"; -} -.glyphicon-thumbs-up:before { - content: "\e125"; -} -.glyphicon-thumbs-down:before { - content: "\e126"; -} -.glyphicon-hand-right:before { - content: "\e127"; -} -.glyphicon-hand-left:before { - content: "\e128"; -} -.glyphicon-hand-up:before { - content: "\e129"; -} -.glyphicon-hand-down:before { - content: "\e130"; -} -.glyphicon-circle-arrow-right:before { - content: "\e131"; -} -.glyphicon-circle-arrow-left:before { - content: "\e132"; -} -.glyphicon-circle-arrow-up:before { - content: "\e133"; -} -.glyphicon-circle-arrow-down:before { - content: "\e134"; -} -.glyphicon-globe:before { - content: "\e135"; -} -.glyphicon-wrench:before { - content: "\e136"; -} -.glyphicon-tasks:before { - content: "\e137"; -} -.glyphicon-filter:before { - content: "\e138"; -} -.glyphicon-briefcase:before { - content: "\e139"; -} -.glyphicon-fullscreen:before { - content: "\e140"; -} -.glyphicon-dashboard:before { - content: "\e141"; -} -.glyphicon-paperclip:before { - content: "\e142"; -} -.glyphicon-heart-empty:before { - content: "\e143"; -} -.glyphicon-link:before { - content: "\e144"; -} -.glyphicon-phone:before { - content: "\e145"; -} -.glyphicon-pushpin:before { - content: "\e146"; -} -.glyphicon-usd:before { - content: "\e148"; -} -.glyphicon-gbp:before { - content: "\e149"; -} -.glyphicon-sort:before { - content: "\e150"; -} -.glyphicon-sort-by-alphabet:before { - content: "\e151"; -} -.glyphicon-sort-by-alphabet-alt:before { - content: "\e152"; -} -.glyphicon-sort-by-order:before { - content: "\e153"; -} -.glyphicon-sort-by-order-alt:before { - content: "\e154"; -} -.glyphicon-sort-by-attributes:before { - content: "\e155"; -} -.glyphicon-sort-by-attributes-alt:before { - content: "\e156"; -} -.glyphicon-unchecked:before { - content: "\e157"; -} -.glyphicon-expand:before { - content: "\e158"; -} -.glyphicon-collapse-down:before { - content: "\e159"; -} -.glyphicon-collapse-up:before { - content: "\e160"; -} -.glyphicon-log-in:before { - content: "\e161"; -} -.glyphicon-flash:before { - content: "\e162"; -} -.glyphicon-log-out:before { - content: "\e163"; -} -.glyphicon-new-window:before { - content: "\e164"; -} -.glyphicon-record:before { - content: "\e165"; -} -.glyphicon-save:before { - content: "\e166"; -} -.glyphicon-open:before { - content: "\e167"; -} -.glyphicon-saved:before { - content: "\e168"; -} -.glyphicon-import:before { - content: "\e169"; -} -.glyphicon-export:before { - content: "\e170"; -} -.glyphicon-send:before { - content: "\e171"; -} -.glyphicon-floppy-disk:before { - content: "\e172"; -} -.glyphicon-floppy-saved:before { - content: "\e173"; -} -.glyphicon-floppy-remove:before { - content: "\e174"; -} -.glyphicon-floppy-save:before { - content: "\e175"; -} -.glyphicon-floppy-open:before { - content: "\e176"; -} -.glyphicon-credit-card:before { - content: "\e177"; -} -.glyphicon-transfer:before { - content: "\e178"; -} -.glyphicon-cutlery:before { - content: "\e179"; -} -.glyphicon-header:before { - content: "\e180"; -} -.glyphicon-compressed:before { - content: "\e181"; -} -.glyphicon-earphone:before { - content: "\e182"; -} -.glyphicon-phone-alt:before { - content: "\e183"; -} -.glyphicon-tower:before { - content: "\e184"; -} -.glyphicon-stats:before { - content: "\e185"; -} -.glyphicon-sd-video:before { - content: "\e186"; -} -.glyphicon-hd-video:before { - content: "\e187"; -} -.glyphicon-subtitles:before { - content: "\e188"; -} -.glyphicon-sound-stereo:before { - content: "\e189"; -} -.glyphicon-sound-dolby:before { - content: "\e190"; -} -.glyphicon-sound-5-1:before { - content: "\e191"; -} -.glyphicon-sound-6-1:before { - content: "\e192"; -} -.glyphicon-sound-7-1:before { - content: "\e193"; -} -.glyphicon-copyright-mark:before { - content: "\e194"; -} -.glyphicon-registration-mark:before { - content: "\e195"; -} -.glyphicon-cloud-download:before { - content: "\e197"; -} -.glyphicon-cloud-upload:before { - content: "\e198"; -} -.glyphicon-tree-conifer:before { - content: "\e199"; -} -.glyphicon-tree-deciduous:before { - content: "\e200"; -} - - -/*btn*/ -.btn { - display: inline-block; - margin-bottom: 0; - font-weight: normal; - text-align: center; - vertical-align: middle; - cursor: pointer; - background-image: none; - border: 1px solid transparent; - white-space: nowrap; - padding: 6px 12px; - font-size: 12px; - line-height: 1.42857143; - border-radius: 4px; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - user-select: none; -} -.btn:focus, -.btn:active:focus, -.btn.active:focus { - outline: thin dotted; - outline: 5px auto -webkit-focus-ring-color; - outline-offset: -2px; -} -.btn:hover, -.btn:focus { - color: #333333; - text-decoration: none; -} -.btn:active, -.btn.active { - outline: 0; - background-image: none; - -webkit-box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); - box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); -} -.btn.disabled, -.btn[disabled], -fieldset[disabled] .btn { - cursor: not-allowed; - pointer-events: none; - opacity: 0.65; - filter: alpha(opacity=65); - -webkit-box-shadow: none; - box-shadow: none; -} -.btn-default { - color: #333333; - background-color: #ffffff; - border-color: #cccccc; -} -.btn-default:hover, -.btn-default:focus, -.btn-default:active, -.btn-default.active, -.open > .dropdown-toggle.btn-default { - color: #333333; - background-color: #e6e6e6; - border-color: #adadad; -} -.btn-default:active, -.btn-default.active, -.open > .dropdown-toggle.btn-default { - background-image: none; -} -.btn-default.disabled, -.btn-default[disabled], -fieldset[disabled] .btn-default, -.btn-default.disabled:hover, -.btn-default[disabled]:hover, -fieldset[disabled] .btn-default:hover, -.btn-default.disabled:focus, -.btn-default[disabled]:focus, -fieldset[disabled] .btn-default:focus, -.btn-default.disabled:active, -.btn-default[disabled]:active, -fieldset[disabled] .btn-default:active, -.btn-default.disabled.active, -.btn-default[disabled].active, -fieldset[disabled] .btn-default.active { - background-color: #ffffff; - border-color: #cccccc; -} -.btn-default .badge { - color: #ffffff; - background-color: #333333; -} -.btn-primary { - color: #ffffff; - background-color: #428bca; - border-color: #357ebd; -} -.btn-primary:hover, -.btn-primary:focus, -.btn-primary:active, -.btn-primary.active, -.open > .dropdown-toggle.btn-primary { - color: #ffffff; - background-color: #3071a9; - border-color: #285e8e; -} -.btn-primary:active, -.btn-primary.active, -.open > .dropdown-toggle.btn-primary { - background-image: none; -} -.btn-primary.disabled, -.btn-primary[disabled], -fieldset[disabled] .btn-primary, -.btn-primary.disabled:hover, -.btn-primary[disabled]:hover, -fieldset[disabled] .btn-primary:hover, -.btn-primary.disabled:focus, -.btn-primary[disabled]:focus, -fieldset[disabled] .btn-primary:focus, -.btn-primary.disabled:active, -.btn-primary[disabled]:active, -fieldset[disabled] .btn-primary:active, -.btn-primary.disabled.active, -.btn-primary[disabled].active, -fieldset[disabled] .btn-primary.active { - background-color: #428bca; - border-color: #357ebd; -} -.btn-primary .badge { - color: #428bca; - background-color: #ffffff; -} -.btn-success { - color: #ffffff; - background-color: #5cb85c; - border-color: #4cae4c; -} -.btn-success:hover, -.btn-success:focus, -.btn-success:active, -.btn-success.active, -.open > .dropdown-toggle.btn-success { - color: #ffffff; - background-color: #449d44; - border-color: #398439; -} -.btn-success:active, -.btn-success.active, -.open > .dropdown-toggle.btn-success { - background-image: none; -} -.btn-success.disabled, -.btn-success[disabled], -fieldset[disabled] .btn-success, -.btn-success.disabled:hover, -.btn-success[disabled]:hover, -fieldset[disabled] .btn-success:hover, -.btn-success.disabled:focus, -.btn-success[disabled]:focus, -fieldset[disabled] .btn-success:focus, -.btn-success.disabled:active, -.btn-success[disabled]:active, -fieldset[disabled] .btn-success:active, -.btn-success.disabled.active, -.btn-success[disabled].active, -fieldset[disabled] .btn-success.active { - background-color: #5cb85c; - border-color: #4cae4c; -} -.btn-success .badge { - color: #5cb85c; - background-color: #ffffff; -} -.btn-info { - color: #ffffff; - background-color: #5bc0de; - border-color: #46b8da; -} -.btn-info:hover, -.btn-info:focus, -.btn-info:active, -.btn-info.active, -.open > .dropdown-toggle.btn-info { - color: #ffffff; - background-color: #31b0d5; - border-color: #269abc; -} -.btn-info:active, -.btn-info.active, -.open > .dropdown-toggle.btn-info { - background-image: none; -} -.btn-info.disabled, -.btn-info[disabled], -fieldset[disabled] .btn-info, -.btn-info.disabled:hover, -.btn-info[disabled]:hover, -fieldset[disabled] .btn-info:hover, -.btn-info.disabled:focus, -.btn-info[disabled]:focus, -fieldset[disabled] .btn-info:focus, -.btn-info.disabled:active, -.btn-info[disabled]:active, -fieldset[disabled] .btn-info:active, -.btn-info.disabled.active, -.btn-info[disabled].active, -fieldset[disabled] .btn-info.active { - background-color: #5bc0de; - border-color: #46b8da; -} -.btn-info .badge { - color: #5bc0de; - background-color: #ffffff; -} -.btn-warning { - color: #ffffff; - background-color: #f0ad4e; - border-color: #eea236; -} -.btn-warning:hover, -.btn-warning:focus, -.btn-warning:active, -.btn-warning.active, -.open > .dropdown-toggle.btn-warning { - color: #ffffff; - background-color: #ec971f; - border-color: #d58512; -} -.btn-warning:active, -.btn-warning.active, -.open > .dropdown-toggle.btn-warning { - background-image: none; -} -.btn-warning.disabled, -.btn-warning[disabled], -fieldset[disabled] .btn-warning, -.btn-warning.disabled:hover, -.btn-warning[disabled]:hover, -fieldset[disabled] .btn-warning:hover, -.btn-warning.disabled:focus, -.btn-warning[disabled]:focus, -fieldset[disabled] .btn-warning:focus, -.btn-warning.disabled:active, -.btn-warning[disabled]:active, -fieldset[disabled] .btn-warning:active, -.btn-warning.disabled.active, -.btn-warning[disabled].active, -fieldset[disabled] .btn-warning.active { - background-color: #f0ad4e; - border-color: #eea236; -} -.btn-warning .badge { - color: #f0ad4e; - background-color: #ffffff; -} -.btn-danger { - color: #ffffff; - background-color: #d9534f; - border-color: #d43f3a; -} -.btn-danger:hover, -.btn-danger:focus, -.btn-danger:active, -.btn-danger.active, -.open > .dropdown-toggle.btn-danger { - color: #ffffff; - background-color: #c9302c; - border-color: #ac2925; -} -.btn-danger:active, -.btn-danger.active, -.open > .dropdown-toggle.btn-danger { - background-image: none; -} -.btn-danger.disabled, -.btn-danger[disabled], -fieldset[disabled] .btn-danger, -.btn-danger.disabled:hover, -.btn-danger[disabled]:hover, -fieldset[disabled] .btn-danger:hover, -.btn-danger.disabled:focus, -.btn-danger[disabled]:focus, -fieldset[disabled] .btn-danger:focus, -.btn-danger.disabled:active, -.btn-danger[disabled]:active, -fieldset[disabled] .btn-danger:active, -.btn-danger.disabled.active, -.btn-danger[disabled].active, -fieldset[disabled] .btn-danger.active { - background-color: #d9534f; - border-color: #d43f3a; -} -.btn-danger .badge { - color: #d9534f; - background-color: #ffffff; -} -.btn-link { - color: #0088cc; - font-weight: normal; - cursor: pointer; - border-radius: 0; -} -.btn-link, -.btn-link:active, -.btn-link[disabled], -fieldset[disabled] .btn-link { - background-color: transparent; - -webkit-box-shadow: none; - box-shadow: none; -} -.btn-link, -.btn-link:hover, -.btn-link:focus, -.btn-link:active { - border-color: transparent; -} -.btn-link:hover, -.btn-link:focus { - color: #0088cc; - text-decoration: underline; - background-color: transparent; -} -.btn-link[disabled]:hover, -fieldset[disabled] .btn-link:hover, -.btn-link[disabled]:focus, -fieldset[disabled] .btn-link:focus { - color: #777777; - text-decoration: none; -} -.btn-lg { - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - border-radius: 6px; -} -.btn-sm { - padding: 5px 10px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -.btn-xs { - padding: 1px 5px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -.btn-block { - display: block; - width: 100%; -} -.btn-block + .btn-block { - margin-top: 5px; -} -input[type="submit"].btn-block, -input[type="reset"].btn-block, -input[type="button"].btn-block { - width: 100%; -} - -.img-responsive { - display: block; - width: 100% \9; - max-width: 100%; - height: auto; -} -.img-rounded { - border-radius: 6px; -} -.img-thumbnail { - padding: 4px; - line-height: 1.42857143; - background-color: #ffffff; - border: 1px solid #dddddd; - border-radius: 0; - -webkit-transition: all 0.2s ease-in-out; - -o-transition: all 0.2s ease-in-out; - transition: all 0.2s ease-in-out; - display: inline-block; - width: 100% \9; - max-width: 100%; - height: auto; -} -.img-circle { - border-radius: 50%; -} - - - -.row { - margin-left: -15px; - margin-right: -15px; -} -.col-xs-1, .col-sm-1, .col-md-1, .col-lg-1, .col-xs-2, .col-sm-2, .col-md-2, .col-lg-2, .col-xs-3, .col-sm-3, .col-md-3, .col-lg-3, .col-xs-4, .col-sm-4, .col-md-4, .col-lg-4, .col-xs-5, .col-sm-5, .col-md-5, .col-lg-5, .col-xs-6, .col-sm-6, .col-md-6, .col-lg-6, .col-xs-7, .col-sm-7, .col-md-7, .col-lg-7, .col-xs-8, .col-sm-8, .col-md-8, .col-lg-8, .col-xs-9, .col-sm-9, .col-md-9, .col-lg-9, .col-xs-10, .col-sm-10, .col-md-10, .col-lg-10, .col-xs-11, .col-sm-11, .col-md-11, .col-lg-11, .col-xs-12, .col-sm-12, .col-md-12, .col-lg-12 { - position: relative; - min-height: 1px; - padding-left: 15px; - padding-right: 15px; -} -.col-xs-1, .col-xs-2, .col-xs-3, .col-xs-4, .col-xs-5, .col-xs-6, .col-xs-7, .col-xs-8, .col-xs-9, .col-xs-10, .col-xs-11, .col-xs-12 { - float: left; -} -.col-xs-12 { - width: 100%; -} -.col-xs-11 { - width: 91.66666667%; -} -.col-xs-10 { - width: 83.33333333%; -} -.col-xs-9 { - width: 75%; -} -.col-xs-8 { - width: 66.66666667%; -} -.col-xs-7 { - width: 58.33333333%; -} -.col-xs-6 { - width: 50%; -} -.col-xs-5 { - width: 41.66666667%; -} -.col-xs-4 { - width: 33.33333333%; -} -.col-xs-3 { - width: 25%; -} -.col-xs-2 { - width: 16.66666667%; -} -.col-xs-1 { - width: 8.33333333%; -} -.col-xs-pull-12 { - right: 100%; -} -.col-xs-pull-11 { - right: 91.66666667%; -} -.col-xs-pull-10 { - right: 83.33333333%; -} -.col-xs-pull-9 { - right: 75%; -} -.col-xs-pull-8 { - right: 66.66666667%; -} -.col-xs-pull-7 { - right: 58.33333333%; -} -.col-xs-pull-6 { - right: 50%; -} -.col-xs-pull-5 { - right: 41.66666667%; -} -.col-xs-pull-4 { - right: 33.33333333%; -} -.col-xs-pull-3 { - right: 25%; -} -.col-xs-pull-2 { - right: 16.66666667%; -} -.col-xs-pull-1 { - right: 8.33333333%; -} -.col-xs-pull-0 { - right: auto; -} -.col-xs-push-12 { - left: 100%; -} -.col-xs-push-11 { - left: 91.66666667%; -} -.col-xs-push-10 { - left: 83.33333333%; -} -.col-xs-push-9 { - left: 75%; -} -.col-xs-push-8 { - left: 66.66666667%; -} -.col-xs-push-7 { - left: 58.33333333%; -} -.col-xs-push-6 { - left: 50%; -} -.col-xs-push-5 { - left: 41.66666667%; -} -.col-xs-push-4 { - left: 33.33333333%; -} -.col-xs-push-3 { - left: 25%; -} -.col-xs-push-2 { - left: 16.66666667%; -} -.col-xs-push-1 { - left: 8.33333333%; -} -.col-xs-push-0 { - left: auto; -} -.col-xs-offset-12 { - margin-left: 100%; -} -.col-xs-offset-11 { - margin-left: 91.66666667%; -} -.col-xs-offset-10 { - margin-left: 83.33333333%; -} -.col-xs-offset-9 { - margin-left: 75%; -} -.col-xs-offset-8 { - margin-left: 66.66666667%; -} -.col-xs-offset-7 { - margin-left: 58.33333333%; -} -.col-xs-offset-6 { - margin-left: 50%; -} -.col-xs-offset-5 { - margin-left: 41.66666667%; -} -.col-xs-offset-4 { - margin-left: 33.33333333%; -} -.col-xs-offset-3 { - margin-left: 25%; -} -.col-xs-offset-2 { - margin-left: 16.66666667%; -} -.col-xs-offset-1 { - margin-left: 8.33333333%; -} -.col-xs-offset-0 { - margin-left: 0%; -} -@media (min-width: 768px) { - .col-sm-1, .col-sm-2, .col-sm-3, .col-sm-4, .col-sm-5, .col-sm-6, .col-sm-7, .col-sm-8, .col-sm-9, .col-sm-10, .col-sm-11, .col-sm-12 { - float: left; - } - .col-sm-12 { - width: 100%; - } - .col-sm-11 { - width: 91.66666667%; - } - .col-sm-10 { - width: 83.33333333%; - } - .col-sm-9 { - width: 75%; - } - .col-sm-8 { - width: 66.66666667%; - } - .col-sm-7 { - width: 58.33333333%; - } - .col-sm-6 { - width: 50%; - } - .col-sm-5 { - width: 41.66666667%; - } - .col-sm-4 { - width: 33.33333333%; - } - .col-sm-3 { - width: 25%; - } - .col-sm-2 { - width: 16.66666667%; - } - .col-sm-1 { - width: 8.33333333%; - } - .col-sm-pull-12 { - right: 100%; - } - .col-sm-pull-11 { - right: 91.66666667%; - } - .col-sm-pull-10 { - right: 83.33333333%; - } - .col-sm-pull-9 { - right: 75%; - } - .col-sm-pull-8 { - right: 66.66666667%; - } - .col-sm-pull-7 { - right: 58.33333333%; - } - .col-sm-pull-6 { - right: 50%; - } - .col-sm-pull-5 { - right: 41.66666667%; - } - .col-sm-pull-4 { - right: 33.33333333%; - } - .col-sm-pull-3 { - right: 25%; - } - .col-sm-pull-2 { - right: 16.66666667%; - } - .col-sm-pull-1 { - right: 8.33333333%; - } - .col-sm-pull-0 { - right: auto; - } - .col-sm-push-12 { - left: 100%; - } - .col-sm-push-11 { - left: 91.66666667%; - } - .col-sm-push-10 { - left: 83.33333333%; - } - .col-sm-push-9 { - left: 75%; - } - .col-sm-push-8 { - left: 66.66666667%; - } - .col-sm-push-7 { - left: 58.33333333%; - } - .col-sm-push-6 { - left: 50%; - } - .col-sm-push-5 { - left: 41.66666667%; - } - .col-sm-push-4 { - left: 33.33333333%; - } - .col-sm-push-3 { - left: 25%; - } - .col-sm-push-2 { - left: 16.66666667%; - } - .col-sm-push-1 { - left: 8.33333333%; - } - .col-sm-push-0 { - left: auto; - } - .col-sm-offset-12 { - margin-left: 100%; - } - .col-sm-offset-11 { - margin-left: 91.66666667%; - } - .col-sm-offset-10 { - margin-left: 83.33333333%; - } - .col-sm-offset-9 { - margin-left: 75%; - } - .col-sm-offset-8 { - margin-left: 66.66666667%; - } - .col-sm-offset-7 { - margin-left: 58.33333333%; - } - .col-sm-offset-6 { - margin-left: 50%; - } - .col-sm-offset-5 { - margin-left: 41.66666667%; - } - .col-sm-offset-4 { - margin-left: 33.33333333%; - } - .col-sm-offset-3 { - margin-left: 25%; - } - .col-sm-offset-2 { - margin-left: 16.66666667%; - } - .col-sm-offset-1 { - margin-left: 8.33333333%; - } - .col-sm-offset-0 { - margin-left: 0%; - } -} -@media (min-width: 992px) { - .col-md-1, .col-md-2, .col-md-3, .col-md-4, .col-md-5, .col-md-6, .col-md-7, .col-md-8, .col-md-9, .col-md-10, .col-md-11, .col-md-12 { - float: left; - } - .col-md-12 { - width: 100%; - } - .col-md-11 { - width: 91.66666667%; - } - .col-md-10 { - width: 83.33333333%; - } - .col-md-9 { - width: 75%; - } - .col-md-8 { - width: 66.66666667%; - } - .col-md-7 { - width: 58.33333333%; - } - .col-md-6 { - width: 50%; - } - .col-md-5 { - width: 41.66666667%; - } - .col-md-4 { - width: 33.33333333%; - } - .col-md-3 { - width: 25%; - } - .col-md-2 { - width: 16.66666667%; - } - .col-md-1 { - width: 8.33333333%; - } - .col-md-pull-12 { - right: 100%; - } - .col-md-pull-11 { - right: 91.66666667%; - } - .col-md-pull-10 { - right: 83.33333333%; - } - .col-md-pull-9 { - right: 75%; - } - .col-md-pull-8 { - right: 66.66666667%; - } - .col-md-pull-7 { - right: 58.33333333%; - } - .col-md-pull-6 { - right: 50%; - } - .col-md-pull-5 { - right: 41.66666667%; - } - .col-md-pull-4 { - right: 33.33333333%; - } - .col-md-pull-3 { - right: 25%; - } - .col-md-pull-2 { - right: 16.66666667%; - } - .col-md-pull-1 { - right: 8.33333333%; - } - .col-md-pull-0 { - right: auto; - } - .col-md-push-12 { - left: 100%; - } - .col-md-push-11 { - left: 91.66666667%; - } - .col-md-push-10 { - left: 83.33333333%; - } - .col-md-push-9 { - left: 75%; - } - .col-md-push-8 { - left: 66.66666667%; - } - .col-md-push-7 { - left: 58.33333333%; - } - .col-md-push-6 { - left: 50%; - } - .col-md-push-5 { - left: 41.66666667%; - } - .col-md-push-4 { - left: 33.33333333%; - } - .col-md-push-3 { - left: 25%; - } - .col-md-push-2 { - left: 16.66666667%; - } - .col-md-push-1 { - left: 8.33333333%; - } - .col-md-push-0 { - left: auto; - } - .col-md-offset-12 { - margin-left: 100%; - } - .col-md-offset-11 { - margin-left: 91.66666667%; - } - .col-md-offset-10 { - margin-left: 83.33333333%; - } - .col-md-offset-9 { - margin-left: 75%; - } - .col-md-offset-8 { - margin-left: 66.66666667%; - } - .col-md-offset-7 { - margin-left: 58.33333333%; - } - .col-md-offset-6 { - margin-left: 50%; - } - .col-md-offset-5 { - margin-left: 41.66666667%; - } - .col-md-offset-4 { - margin-left: 33.33333333%; - } - .col-md-offset-3 { - margin-left: 25%; - } - .col-md-offset-2 { - margin-left: 16.66666667%; - } - .col-md-offset-1 { - margin-left: 8.33333333%; - } - .col-md-offset-0 { - margin-left: 0%; - } -} -@media (min-width: 1200px) { - .col-lg-1, .col-lg-2, .col-lg-3, .col-lg-4, .col-lg-5, .col-lg-6, .col-lg-7, .col-lg-8, .col-lg-9, .col-lg-10, .col-lg-11, .col-lg-12 { - float: left; - } - .col-lg-12 { - width: 100%; - } - .col-lg-11 { - width: 91.66666667%; - } - .col-lg-10 { - width: 83.33333333%; - } - .col-lg-9 { - width: 75%; - } - .col-lg-8 { - width: 66.66666667%; - } - .col-lg-7 { - width: 58.33333333%; - } - .col-lg-6 { - width: 50%; - } - .col-lg-5 { - width: 41.66666667%; - } - .col-lg-4 { - width: 33.33333333%; - } - .col-lg-3 { - width: 25%; - } - .col-lg-2 { - width: 16.66666667%; - } - .col-lg-1 { - width: 8.33333333%; - } - .col-lg-pull-12 { - right: 100%; - } - .col-lg-pull-11 { - right: 91.66666667%; - } - .col-lg-pull-10 { - right: 83.33333333%; - } - .col-lg-pull-9 { - right: 75%; - } - .col-lg-pull-8 { - right: 66.66666667%; - } - .col-lg-pull-7 { - right: 58.33333333%; - } - .col-lg-pull-6 { - right: 50%; - } - .col-lg-pull-5 { - right: 41.66666667%; - } - .col-lg-pull-4 { - right: 33.33333333%; - } - .col-lg-pull-3 { - right: 25%; - } - .col-lg-pull-2 { - right: 16.66666667%; - } - .col-lg-pull-1 { - right: 8.33333333%; - } - .col-lg-pull-0 { - right: auto; - } - .col-lg-push-12 { - left: 100%; - } - .col-lg-push-11 { - left: 91.66666667%; - } - .col-lg-push-10 { - left: 83.33333333%; - } - .col-lg-push-9 { - left: 75%; - } - .col-lg-push-8 { - left: 66.66666667%; - } - .col-lg-push-7 { - left: 58.33333333%; - } - .col-lg-push-6 { - left: 50%; - } - .col-lg-push-5 { - left: 41.66666667%; - } - .col-lg-push-4 { - left: 33.33333333%; - } - .col-lg-push-3 { - left: 25%; - } - .col-lg-push-2 { - left: 16.66666667%; - } - .col-lg-push-1 { - left: 8.33333333%; - } - .col-lg-push-0 { - left: auto; - } - .col-lg-offset-12 { - margin-left: 100%; - } - .col-lg-offset-11 { - margin-left: 91.66666667%; - } - .col-lg-offset-10 { - margin-left: 83.33333333%; - } - .col-lg-offset-9 { - margin-left: 75%; - } - .col-lg-offset-8 { - margin-left: 66.66666667%; - } - .col-lg-offset-7 { - margin-left: 58.33333333%; - } - .col-lg-offset-6 { - margin-left: 50%; - } - .col-lg-offset-5 { - margin-left: 41.66666667%; - } - .col-lg-offset-4 { - margin-left: 33.33333333%; - } - .col-lg-offset-3 { - margin-left: 25%; - } - .col-lg-offset-2 { - margin-left: 16.66666667%; - } - .col-lg-offset-1 { - margin-left: 8.33333333%; - } - .col-lg-offset-0 { - margin-left: 0%; - } -} - - - - -.form-control { - display: block; - width: 100%; - height: 31px; - padding: 6px 12px; - font-size: 12px; - line-height: 1.42857143; - color: #555555; - background-color: #ffffff; - background-image: none; - border: 1px solid #cccccc; - border-radius: 0; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - -webkit-transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; - -o-transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; - transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; -} -.form-control:focus { - border-color: #66afe9; - outline: 0; - -webkit-box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); - box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); -} -.form-control::-moz-placeholder { - color: #777777; - opacity: 1; -} -.form-control:-ms-input-placeholder { - color: #777777; -} -.form-control::-webkit-input-placeholder { - color: #777777; -} -.form-control[disabled], -.form-control[readonly], -fieldset[disabled] .form-control { - cursor: not-allowed; - background-color: #eeeeee; - opacity: 1; -} -textarea.form-control { - height: auto; -} -input[type="search"] { - -webkit-appearance: none; -} -input[type="date"], -input[type="time"], -input[type="datetime-local"], -input[type="month"] { - line-height: 31px; - line-height: 1.42857143 \0; -} -input[type="date"].input-sm, -input[type="time"].input-sm, -input[type="datetime-local"].input-sm, -input[type="month"].input-sm { - line-height: 28px; -} -input[type="date"].input-lg, -input[type="time"].input-lg, -input[type="datetime-local"].input-lg, -input[type="month"].input-lg { - line-height: 42px; -} -.form-group { - margin-bottom: 15px; -} -.radio, -.checkbox { - position: relative; - display: block; - min-height: 17px; - margin-top: 10px; - margin-bottom: 10px; -} -.radio label, -.checkbox label { - padding-left: 20px; - margin-bottom: 0; - font-weight: normal; - cursor: pointer; -} -.radio input[type="radio"], -.radio-inline input[type="radio"], -.checkbox input[type="checkbox"], -.checkbox-inline input[type="checkbox"] { - position: absolute; - margin-left: -20px; - margin-top: 4px \9; -} -.radio + .radio, -.checkbox + .checkbox { - margin-top: -5px; -} -.radio-inline, -.checkbox-inline { - display: inline-block; - padding-left: 20px; - margin-bottom: 0; - vertical-align: middle; - font-weight: normal; - cursor: pointer; -} -.radio-inline + .radio-inline, -.checkbox-inline + .checkbox-inline { - margin-top: 0; - margin-left: 10px; -} -input[type="radio"][disabled], -input[type="checkbox"][disabled], -input[type="radio"].disabled, -input[type="checkbox"].disabled, -fieldset[disabled] input[type="radio"], -fieldset[disabled] input[type="checkbox"] { - cursor: not-allowed; -} -.radio-inline.disabled, -.checkbox-inline.disabled, -fieldset[disabled] .radio-inline, -fieldset[disabled] .checkbox-inline { - cursor: not-allowed; -} -.radio.disabled label, -.checkbox.disabled label, -fieldset[disabled] .radio label, -fieldset[disabled] .checkbox label { - cursor: not-allowed; -} -.form-control-static { - padding-top: 7px; - padding-bottom: 7px; - margin-bottom: 0; -} -.form-control-static.input-lg, -.form-control-static.input-sm { - padding-left: 0; - padding-right: 0; -} -.input-sm, -.form-horizontal .form-group-sm .form-control { - height: 28px; - padding: 5px 10px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -select.input-sm { - height: 28px; - line-height: 28px; -} -textarea.input-sm, -select[multiple].input-sm { - height: auto; -} -.input-lg, -.form-horizontal .form-group-lg .form-control { - height: 42px; - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - border-radius: 6px; -} -select.input-lg { - height: 42px; - line-height: 42px; -} -textarea.input-lg, -select[multiple].input-lg { - height: auto; -} -.has-feedback { - position: relative; -} -.has-feedback .form-control { - padding-right: 38.75px; -} -.form-control-feedback { - position: absolute; - top: 22px; - right: 0; - z-index: 2; - display: block; - width: 31px; - height: 31px; - line-height: 31px; - text-align: center; -} -.input-lg + .form-control-feedback { - width: 42px; - height: 42px; - line-height: 42px; -} -.input-sm + .form-control-feedback { - width: 28px; - height: 28px; - line-height: 28px; -} -.has-success .help-block, -.has-success .control-label, -.has-success .radio, -.has-success .checkbox, -.has-success .radio-inline, -.has-success .checkbox-inline { - color: #3c763d; -} -.has-success .form-control { - border-color: #3c763d; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-success .form-control:focus { - border-color: #2b542c; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #67b168; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #67b168; -} -.has-success .input-group-addon { - color: #3c763d; - border-color: #3c763d; - background-color: #dff0d8; -} -.has-success .form-control-feedback { - color: #3c763d; -} -.has-warning .help-block, -.has-warning .control-label, -.has-warning .radio, -.has-warning .checkbox, -.has-warning .radio-inline, -.has-warning .checkbox-inline { - color: #8a6d3b; -} -.has-warning .form-control { - border-color: #8a6d3b; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-warning .form-control:focus { - border-color: #66512c; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #c0a16b; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #c0a16b; -} -.has-warning .input-group-addon { - color: #8a6d3b; - border-color: #8a6d3b; - background-color: #fcf8e3; -} -.has-warning .form-control-feedback { - color: #8a6d3b; -} -.has-error .help-block, -.has-error .control-label, -.has-error .radio, -.has-error .checkbox, -.has-error .radio-inline, -.has-error .checkbox-inline { - color: #a94442; -} -.has-error .form-control { - border-color: #a94442; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-error .form-control:focus { - border-color: #843534; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #ce8483; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #ce8483; -} -.has-error .input-group-addon { - color: #a94442; - border-color: #a94442; - background-color: #f2dede; -} -.has-error .form-control-feedback { - color: #a94442; -} -.has-feedback label.sr-only ~ .form-control-feedback { - top: 0; -} -.help-block { - display: block; - margin-top: 5px; - margin-bottom: 10px; - color: #737373; -} -@media (min-width: 768px) { - .form-inline .form-group { - display: inline-block; - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .form-control { - display: inline-block; - width: auto; - vertical-align: middle; - } - .form-inline .input-group { - display: inline-table; - vertical-align: middle; - } - .form-inline .input-group .input-group-addon, - .form-inline .input-group .input-group-btn, - .form-inline .input-group .form-control { - width: auto; - } - .form-inline .input-group > .form-control { - width: 100%; - } - .form-inline .control-label { - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .radio, - .form-inline .checkbox { - display: inline-block; - margin-top: 0; - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .radio label, - .form-inline .checkbox label { - padding-left: 0; - } - .form-inline .radio input[type="radio"], - .form-inline .checkbox input[type="checkbox"] { - position: relative; - margin-left: 0; - } - .form-inline .has-feedback .form-control-feedback { - top: 0; - } -} -.form-horizontal .radio, -.form-horizontal .checkbox, -.form-horizontal .radio-inline, -.form-horizontal .checkbox-inline { - margin-top: 0; - margin-bottom: 0; - padding-top: 7px; -} -.form-horizontal .radio, -.form-horizontal .checkbox { - min-height: 24px; -} -.form-horizontal .form-group { - margin-left: -15px; - margin-right: -15px; -} -@media (min-width: 768px) { - .form-horizontal .control-label { - text-align: right; - margin-bottom: 0; - padding-top: 7px; - } -} -.form-horizontal .has-feedback .form-control-feedback { - top: 0; - right: 15px; -} -@media (min-width: 768px) { - .form-horizontal .form-group-lg .control-label { - padding-top: 14.3px; - } -} -@media (min-width: 768px) { - .form-horizontal .form-group-sm .control-label { - padding-top: 6px; - } -} - -.tooltip { - position: absolute; - z-index: 1070; - display: block; - visibility: visible; - font-size: 11px; - line-height: 1.4; - opacity: 0; - filter: alpha(opacity=0); -} -.tooltip.in { - opacity: 0.9; - filter: alpha(opacity=90); -} -.tooltip.top { - margin-top: -3px; - padding: 5px 0; -} -.tooltip.right { - margin-left: 3px; - padding: 0 5px; -} -.tooltip.bottom { - margin-top: 3px; - padding: 5px 0; -} -.tooltip.left { - margin-left: -3px; - padding: 0 5px; -} -.tooltip-inner { - max-width: 200px; - padding: 3px 8px; - color: #ffffff; - text-align: center; - text-decoration: none; - background-color: #000000; - border-radius: 4px; -} -.tooltip-arrow { - position: absolute; - width: 0; - height: 0; - border-color: transparent; - border-style: solid; -} -.tooltip.top .tooltip-arrow { - bottom: 0; - left: 50%; - margin-left: -5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.top-left .tooltip-arrow { - bottom: 0; - left: 5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.top-right .tooltip-arrow { - bottom: 0; - right: 5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.right .tooltip-arrow { - top: 50%; - left: 0; - margin-top: -5px; - border-width: 5px 5px 5px 0; - border-right-color: #000000; -} -.tooltip.left .tooltip-arrow { - top: 50%; - right: 0; - margin-top: -5px; - border-width: 5px 0 5px 5px; - border-left-color: #000000; -} -.tooltip.bottom .tooltip-arrow { - top: 0; - left: 50%; - margin-left: -5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} -.tooltip.bottom-left .tooltip-arrow { - top: 0; - left: 5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} -.tooltip.bottom-right .tooltip-arrow { - top: 0; - right: 5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} - -.modal-open { - overflow: hidden; -} -.modal { - display: none; - overflow: hidden; - position: fixed; - top: 0; - right: 0; - bottom: 0; - left: 0; - z-index: 1050; - -webkit-overflow-scrolling: touch; - outline: 0; -} -.modal.fade .modal-dialog { - -webkit-transform: translate3d(0, -25%, 0); - transform: translate3d(0, -25%, 0); - -webkit-transition: -webkit-transform 0.3s ease-out; - -moz-transition: -moz-transform 0.3s ease-out; - -o-transition: -o-transform 0.3s ease-out; - transition: transform 0.3s ease-out; -} -.modal.in .modal-dialog { - -webkit-transform: translate3d(0, 0, 0); - transform: translate3d(0, 0, 0); -} -.modal-open .modal { - overflow-x: hidden; - overflow-y: auto; -} -.modal-dialog { - position: relative; - width: auto; - margin: 10px; -} -.modal-content { - position: relative; - background-color: #ffffff; - border: 1px solid #999999; - border: 1px solid rgba(0, 0, 0, 0.2); - border-radius: 6px; - -webkit-box-shadow: 0 3px 9px rgba(0, 0, 0, 0.5); - box-shadow: 0 3px 9px rgba(0, 0, 0, 0.5); - background-clip: padding-box; - outline: 0; -} -.modal-backdrop { - position: fixed; - top: 0; - right: 0; - bottom: 0; - left: 0; - z-index: 1040; - background-color: #000000; -} -.modal-backdrop.fade { - opacity: 0; - filter: alpha(opacity=0); -} -.modal-backdrop.in { - opacity: 0.5; - filter: alpha(opacity=50); -} -.modal-header { - padding: 15px; - border-bottom: 1px solid #e5e5e5; - min-height: 16.42857143px; -} -.modal-header .close { - margin-top: -2px; -} -.modal-title { - margin: 0; - line-height: 1.42857143; -} -.modal-body { - position: relative; - padding: 15px; -} -.modal-footer { - padding: 15px; - text-align: right; - border-top: 1px solid #e5e5e5; -} -.modal-footer .btn + .btn { - margin-left: 5px; - margin-bottom: 0; -} -.modal-footer .btn-group .btn + .btn { - margin-left: -1px; -} -.modal-footer .btn-block + .btn-block { - margin-left: 0; -} -.modal-scrollbar-measure { - position: absolute; - top: -9999px; - width: 50px; - height: 50px; - overflow: scroll; -} -@media (min-width: 768px) { - .modal-dialog { - width: 600px; - margin: 30px auto; - } - .modal-content { - -webkit-box-shadow: 0 5px 15px rgba(0, 0, 0, 0.5); - box-shadow: 0 5px 15px rgba(0, 0, 0, 0.5); - } - .modal-sm { - width: 300px; - } -} -@media (min-width: 992px) { - .modal-lg { - width: 900px; - } -} - -.modal-footer:before, -.modal-footer:after { - content: " "; - display: table; -} -.navbar-collapse:after, -.modal-footer:after { - clear: both; -} - - -.alert { - padding: 15px; - margin-bottom: 17px; - border: 1px solid transparent; - border-radius: 0; -} -.alert h4 { - margin-top: 0; - color: inherit; -} -.alert .alert-link { - font-weight: bold; -} -.alert > p, -.alert > ul { - margin-bottom: 0; -} -.alert > p + p { - margin-top: 5px; -} -.alert-dismissable, -.alert-dismissible { - padding-right: 35px; -} -.alert-dismissable .close, -.alert-dismissible .close { - position: relative; - top: -2px; - right: -21px; - color: inherit; -} -.alert-success { - background-color: #dff0d8; - border-color: #d6e9c6; - color: #3c763d; -} -.alert-success hr { - border-top-color: #c9e2b3; -} -.alert-success .alert-link { - color: #2b542c; -} -.alert-info { - background-color: #d9edf7; - border-color: #bce8f1; - color: #31708f; -} -.alert-info hr { - border-top-color: #a6e1ec; -} -.alert-info .alert-link { - color: #245269; -} -.alert-warning { - background-color: #fcf8e3; - border-color: #faebcc; - color: #8a6d3b; -} -.alert-warning hr { - border-top-color: #f7e1b5; -} -.alert-warning .alert-link { - color: #66512c; -} -.alert-danger { - background-color: #f2dede; - border-color: #ebccd1; - color: #a94442; -} -.alert-danger hr { - border-top-color: #e4b9c0; -} - -.well { - min-height: 20px; - padding: 19px; - margin-bottom: 20px; - background-color: #f5f5f5; - border: 1px solid #e3e3e3; - border-radius: 4px; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); -} -.well blockquote { - border-color: #ddd; - border-color: rgba(0, 0, 0, 0.15); -} -.well-lg { - padding: 24px; - border-radius: 6px; -} -.well-sm { - padding: 9px; - border-radius: 3px; -} -.close { - float: right; - font-size: 18px; - font-weight: bold; - line-height: 1; - color: #000000; - text-shadow: 0 1px 0 #ffffff; - opacity: 0.2; - filter: alpha(opacity=20); -} -.close:hover, -.close:focus { - color: #000000; - text-decoration: none; - cursor: pointer; - opacity: 0.5; - filter: alpha(opacity=50); -} -button.close { - padding: 0; - cursor: pointer; - background: transparent; - border: 0; - -webkit-appearance: none; -} - - -/* Manually added pager */ -.pagination { - display: inline-block; - padding-left: 0; - margin: 20px 0; - border-radius: 4px; -} -.pagination > li { - display: inline; -} -.pagination > li > a, -.pagination > li > span { - position: relative; - float: left; - padding: 6px 12px; - line-height: 1.42857143; - text-decoration: none; - color: #337ab7; - background-color: #ffffff; - border: 1px solid #dddddd; - margin-left: -1px; -} -.pagination > li:first-child > a, -.pagination > li:first-child > span { - margin-left: 0; - border-bottom-left-radius: 4px; - border-top-left-radius: 4px; -} -.pagination > li:last-child > a, -.pagination > li:last-child > span { - border-bottom-right-radius: 4px; - border-top-right-radius: 4px; -} -.pagination > li > a:hover, -.pagination > li > span:hover, -.pagination > li > a:focus, -.pagination > li > span:focus { - z-index: 2; - color: #23527c; - background-color: #eeeeee; - border-color: #dddddd; -} -.pagination > .active > a, -.pagination > .active > span, -.pagination > .active > a:hover, -.pagination > .active > span:hover, -.pagination > .active > a:focus, -.pagination > .active > span:focus { - z-index: 3; - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; - cursor: default; -} -.pagination > .disabled > span, -.pagination > .disabled > span:hover, -.pagination > .disabled > span:focus, -.pagination > .disabled > a, -.pagination > .disabled > a:hover, -.pagination > .disabled > a:focus { - color: #777777; - background-color: #ffffff; - border-color: #dddddd; - cursor: not-allowed; -} -.pagination-lg > li > a, -.pagination-lg > li > span { - padding: 10px 16px; - font-size: 18px; - line-height: 1.3333333; -} -.pagination-lg > li:first-child > a, -.pagination-lg > li:first-child > span { - border-bottom-left-radius: 6px; - border-top-left-radius: 6px; -} -.pagination-lg > li:last-child > a, -.pagination-lg > li:last-child > span { - border-bottom-right-radius: 6px; - border-top-right-radius: 6px; -} -.pagination-sm > li > a, -.pagination-sm > li > span { - padding: 5px 10px; - font-size: 12px; - line-height: 1.5; -} -.pagination-sm > li:first-child > a, -.pagination-sm > li:first-child > span { - border-bottom-left-radius: 3px; - border-top-left-radius: 3px; -} -.pagination-sm > li:last-child > a, -.pagination-sm > li:last-child > span { - border-bottom-right-radius: 3px; - border-top-right-radius: 3px; -} -.pager { - padding-left: 0; - margin: 20px 0; - list-style: none; - text-align: center; -} -.pager li { - display: inline; -} -.pager li > a, -.pager li > span { - display: inline-block; - padding: 5px 14px; - background-color: #ffffff; - border: 1px solid #dddddd; - border-radius: 15px; -} -.pager li > a:hover, -.pager li > a:focus { - text-decoration: none; - background-color: #eeeeee; -} -.pager .next > a, -.pager .next > span { - float: right; -} -.pager .previous > a, -.pager .previous > span { - float: left; -} -.pager .disabled > a, -.pager .disabled > a:hover, -.pager .disabled > a:focus, -.pager .disabled > span { - color: #777777; - background-color: #ffffff; - cursor: not-allowed; -} -.pager:before, -.pager:after { - content: " "; - display: table; -} -.pager:after { - clear: both; -} - -/* List and panel */ -.list-group { - margin-bottom: 20px; - padding-left: 0; -} -.list-group-item { - position: relative; - display: block; - padding: 10px 15px; - margin-bottom: -1px; - background-color: #ffffff; - border: 1px solid #dddddd; -} -.list-group-item:first-child { - border-top-right-radius: 4px; - border-top-left-radius: 4px; -} -.list-group-item:last-child { - margin-bottom: 0; - border-bottom-right-radius: 4px; - border-bottom-left-radius: 4px; -} -a.list-group-item, -button.list-group-item { - color: #555555; -} -a.list-group-item .list-group-item-heading, -button.list-group-item .list-group-item-heading { - color: #333333; -} -a.list-group-item:hover, -button.list-group-item:hover, -a.list-group-item:focus, -button.list-group-item:focus { - text-decoration: none; - color: #555555; - background-color: #f5f5f5; -} -button.list-group-item { - width: 100%; - text-align: left; -} -.list-group-item.disabled, -.list-group-item.disabled:hover, -.list-group-item.disabled:focus { - background-color: #eeeeee; - color: #777777; - cursor: not-allowed; -} -.list-group-item.disabled .list-group-item-heading, -.list-group-item.disabled:hover .list-group-item-heading, -.list-group-item.disabled:focus .list-group-item-heading { - color: inherit; -} -.list-group-item.disabled .list-group-item-text, -.list-group-item.disabled:hover .list-group-item-text, -.list-group-item.disabled:focus .list-group-item-text { - color: #777777; -} -.list-group-item.active, -.list-group-item.active:hover, -.list-group-item.active:focus { - z-index: 2; - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; -} -.list-group-item.active .list-group-item-heading, -.list-group-item.active:hover .list-group-item-heading, -.list-group-item.active:focus .list-group-item-heading, -.list-group-item.active .list-group-item-heading > small, -.list-group-item.active:hover .list-group-item-heading > small, -.list-group-item.active:focus .list-group-item-heading > small, -.list-group-item.active .list-group-item-heading > .small, -.list-group-item.active:hover .list-group-item-heading > .small, -.list-group-item.active:focus .list-group-item-heading > .small { - color: inherit; -} -.list-group-item.active .list-group-item-text, -.list-group-item.active:hover .list-group-item-text, -.list-group-item.active:focus .list-group-item-text { - color: #c7ddef; -} -.list-group-item-success { - color: #3c763d; - background-color: #dff0d8; -} -a.list-group-item-success, -button.list-group-item-success { - color: #3c763d; -} -a.list-group-item-success .list-group-item-heading, -button.list-group-item-success .list-group-item-heading { - color: inherit; -} -a.list-group-item-success:hover, -button.list-group-item-success:hover, -a.list-group-item-success:focus, -button.list-group-item-success:focus { - color: #3c763d; - background-color: #d0e9c6; -} -a.list-group-item-success.active, -button.list-group-item-success.active, -a.list-group-item-success.active:hover, -button.list-group-item-success.active:hover, -a.list-group-item-success.active:focus, -button.list-group-item-success.active:focus { - color: #fff; - background-color: #3c763d; - border-color: #3c763d; -} -.list-group-item-info { - color: #31708f; - background-color: #d9edf7; -} -a.list-group-item-info, -button.list-group-item-info { - color: #31708f; -} -a.list-group-item-info .list-group-item-heading, -button.list-group-item-info .list-group-item-heading { - color: inherit; -} -a.list-group-item-info:hover, -button.list-group-item-info:hover, -a.list-group-item-info:focus, -button.list-group-item-info:focus { - color: #31708f; - background-color: #c4e3f3; -} -a.list-group-item-info.active, -button.list-group-item-info.active, -a.list-group-item-info.active:hover, -button.list-group-item-info.active:hover, -a.list-group-item-info.active:focus, -button.list-group-item-info.active:focus { - color: #fff; - background-color: #31708f; - border-color: #31708f; -} -.list-group-item-warning { - color: #8a6d3b; - background-color: #fcf8e3; -} -a.list-group-item-warning, -button.list-group-item-warning { - color: #8a6d3b; -} -a.list-group-item-warning .list-group-item-heading, -button.list-group-item-warning .list-group-item-heading { - color: inherit; -} -a.list-group-item-warning:hover, -button.list-group-item-warning:hover, -a.list-group-item-warning:focus, -button.list-group-item-warning:focus { - color: #8a6d3b; - background-color: #faf2cc; -} -a.list-group-item-warning.active, -button.list-group-item-warning.active, -a.list-group-item-warning.active:hover, -button.list-group-item-warning.active:hover, -a.list-group-item-warning.active:focus, -button.list-group-item-warning.active:focus { - color: #fff; - background-color: #8a6d3b; - border-color: #8a6d3b; -} -.list-group-item-danger { - color: #a94442; - background-color: #f2dede; -} -a.list-group-item-danger, -button.list-group-item-danger { - color: #a94442; -} -a.list-group-item-danger .list-group-item-heading, -button.list-group-item-danger .list-group-item-heading { - color: inherit; -} -a.list-group-item-danger:hover, -button.list-group-item-danger:hover, -a.list-group-item-danger:focus, -button.list-group-item-danger:focus { - color: #a94442; - background-color: #ebcccc; -} -a.list-group-item-danger.active, -button.list-group-item-danger.active, -a.list-group-item-danger.active:hover, -button.list-group-item-danger.active:hover, -a.list-group-item-danger.active:focus, -button.list-group-item-danger.active:focus { - color: #fff; - background-color: #a94442; - border-color: #a94442; -} -.list-group-item-muted { - color: #777777; - background-color: #f7f7f7; -} -a.list-group-item-muted, -button.list-group-item-muted { - color: #777777; -} -a.list-group-item-muted .list-group-item-heading, -button.list-group-item-muted .list-group-item-heading { - color: inherit; -} -a.list-group-item-muted:hover, -button.list-group-item-muted:hover, -a.list-group-item-muted:focus, -button.list-group-item-muted:focus { - color: #777777; - background-color: #f1f1f1; -} -a.list-group-item-muted.active, -button.list-group-item-muted.active, -a.list-group-item-muted.active:hover, -button.list-group-item-muted.active:hover, -a.list-group-item-muted.active:focus, -button.list-group-item-muted.active:focus { - color: #fff; - background-color: #777777; - border-color: #777777; -} -.list-group-item-heading { - margin-top: 0; - margin-bottom: 0; -} -.list-group-item-text { - margin-top: 5px; - margin-bottom: 0; - line-height: 1.3; -} -.list-group-item-text:empty { - margin-top: 0; -} -.panel { - margin-bottom: 20px; - background-color: #ffffff; - border: 1px solid transparent; - border-radius: 4px; - -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05); - box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05); -} -.panel-body { - padding: 15px; -} -.panel-heading { - padding: 10px 15px; - border-bottom: 1px solid transparent; - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel-heading > .dropdown .dropdown-toggle { - color: inherit; -} -.panel-title { - margin-top: 0; - margin-bottom: 0; - font-size: 16px; - color: inherit; -} -.panel-title > a, -.panel-title > small, -.panel-title > .small, -.panel-title > small > a, -.panel-title > .small > a { - color: inherit; -} -.panel-footer { - padding: 10px 15px; - background-color: #f5f5f5; - border-top: 1px solid #dddddd; - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .list-group, -.panel > .panel-collapse > .list-group { - margin-bottom: 0; -} -.panel > .list-group .list-group-item, -.panel > .panel-collapse > .list-group .list-group-item { - border-width: 1px 0; - border-radius: 0; -} -.panel > .list-group:first-child .list-group-item:first-child, -.panel > .panel-collapse > .list-group:first-child .list-group-item:first-child { - border-top: 0; - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel > .list-group:last-child .list-group-item:last-child, -.panel > .panel-collapse > .list-group:last-child .list-group-item:last-child { - border-bottom: 0; - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .panel-heading + .panel-collapse > .list-group .list-group-item:first-child { - border-top-right-radius: 0; - border-top-left-radius: 0; -} -.panel-heading + .list-group .list-group-item:first-child { - border-top-width: 0; -} -.list-group + .panel-footer { - border-top-width: 0; -} -.panel > .table, -.panel > .table-responsive > .table, -.panel > .panel-collapse > .table { - margin-bottom: 0; -} -.panel > .table caption, -.panel > .table-responsive > .table caption, -.panel > .panel-collapse > .table caption { - padding-left: 15px; - padding-right: 15px; -} -.panel > .table:first-child, -.panel > .table-responsive:first-child > .table:first-child { - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child { - border-top-left-radius: 3px; - border-top-right-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child td:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child td:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child td:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child td:first-child, -.panel > .table:first-child > thead:first-child > tr:first-child th:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child th:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child th:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child th:first-child { - border-top-left-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child td:last-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child td:last-child, -.panel > .table:first-child > tbody:first-child > tr:first-child td:last-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child td:last-child, -.panel > .table:first-child > thead:first-child > tr:first-child th:last-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child th:last-child, -.panel > .table:first-child > tbody:first-child > tr:first-child th:last-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child th:last-child { - border-top-right-radius: 3px; -} -.panel > .table:last-child, -.panel > .table-responsive:last-child > .table:last-child { - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child { - border-bottom-left-radius: 3px; - border-bottom-right-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child td:first-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child td:first-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child td:first-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child td:first-child, -.panel > .table:last-child > tbody:last-child > tr:last-child th:first-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child th:first-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child th:first-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child th:first-child { - border-bottom-left-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child td:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child td:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child td:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child td:last-child, -.panel > .table:last-child > tbody:last-child > tr:last-child th:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child th:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child th:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child th:last-child { - border-bottom-right-radius: 3px; -} -.panel > .panel-body + .table, -.panel > .panel-body + .table-responsive, -.panel > .table + .panel-body, -.panel > .table-responsive + .panel-body { - border-top: 1px solid #dddddd; -} -.panel > .table > tbody:first-child > tr:first-child th, -.panel > .table > tbody:first-child > tr:first-child td { - border-top: 0; -} -.panel > .table-bordered, -.panel > .table-responsive > .table-bordered { - border: 0; -} -.panel > .table-bordered > thead > tr > th:first-child, -.panel > .table-responsive > .table-bordered > thead > tr > th:first-child, -.panel > .table-bordered > tbody > tr > th:first-child, -.panel > .table-responsive > .table-bordered > tbody > tr > th:first-child, -.panel > .table-bordered > tfoot > tr > th:first-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > th:first-child, -.panel > .table-bordered > thead > tr > td:first-child, -.panel > .table-responsive > .table-bordered > thead > tr > td:first-child, -.panel > .table-bordered > tbody > tr > td:first-child, -.panel > .table-responsive > .table-bordered > tbody > tr > td:first-child, -.panel > .table-bordered > tfoot > tr > td:first-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > td:first-child { - border-left: 0; -} -.panel > .table-bordered > thead > tr > th:last-child, -.panel > .table-responsive > .table-bordered > thead > tr > th:last-child, -.panel > .table-bordered > tbody > tr > th:last-child, -.panel > .table-responsive > .table-bordered > tbody > tr > th:last-child, -.panel > .table-bordered > tfoot > tr > th:last-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > th:last-child, -.panel > .table-bordered > thead > tr > td:last-child, -.panel > .table-responsive > .table-bordered > thead > tr > td:last-child, -.panel > .table-bordered > tbody > tr > td:last-child, -.panel > .table-responsive > .table-bordered > tbody > tr > td:last-child, -.panel > .table-bordered > tfoot > tr > td:last-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > td:last-child { - border-right: 0; -} -.panel > .table-bordered > thead > tr:first-child > td, -.panel > .table-responsive > .table-bordered > thead > tr:first-child > td, -.panel > .table-bordered > tbody > tr:first-child > td, -.panel > .table-responsive > .table-bordered > tbody > tr:first-child > td, -.panel > .table-bordered > thead > tr:first-child > th, -.panel > .table-responsive > .table-bordered > thead > tr:first-child > th, -.panel > .table-bordered > tbody > tr:first-child > th, -.panel > .table-responsive > .table-bordered > tbody > tr:first-child > th { - border-bottom: 0; -} -.panel > .table-bordered > tbody > tr:last-child > td, -.panel > .table-responsive > .table-bordered > tbody > tr:last-child > td, -.panel > .table-bordered > tfoot > tr:last-child > td, -.panel > .table-responsive > .table-bordered > tfoot > tr:last-child > td, -.panel > .table-bordered > tbody > tr:last-child > th, -.panel > .table-responsive > .table-bordered > tbody > tr:last-child > th, -.panel > .table-bordered > tfoot > tr:last-child > th, -.panel > .table-responsive > .table-bordered > tfoot > tr:last-child > th { - border-bottom: 0; -} -.panel > .table-responsive { - border: 0; - margin-bottom: 0; -} -.panel-group { - margin-bottom: 20px; -} -.panel-group .panel { - margin-bottom: 0; - border-radius: 4px; -} -.panel-group .panel + .panel { - margin-top: 5px; -} -.panel-group .panel-heading { - border-bottom: 0; -} -.panel-group .panel-heading + .panel-collapse > .panel-body, -.panel-group .panel-heading + .panel-collapse > .list-group { - border-top: 1px solid #dddddd; -} -.panel-group .panel-footer { - border-top: 0; -} -.panel-group .panel-footer + .panel-collapse .panel-body { - border-bottom: 1px solid #dddddd; -} -.panel-default { - border-color: #dddddd; -} -.panel-default > .panel-heading { - color: #333333; - background-color: #f5f5f5; - border-color: #dddddd; -} -.panel-default > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #dddddd; -} -.panel-default > .panel-heading .badge { - color: #f5f5f5; - background-color: #333333; -} -.panel-default > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #dddddd; -} -.panel-primary { - border-color: #337ab7; -} -.panel-primary > .panel-heading { - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; -} -.panel-primary > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #337ab7; -} -.panel-primary > .panel-heading .badge { - color: #337ab7; - background-color: #ffffff; -} -.panel-primary > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #337ab7; -} -.panel-success { - border-color: #d6e9c6; -} -.panel-success > .panel-heading { - color: #3c763d; - background-color: #dff0d8; - border-color: #d6e9c6; -} -.panel-success > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #d6e9c6; -} -.panel-success > .panel-heading .badge { - color: #dff0d8; - background-color: #3c763d; -} -.panel-success > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #d6e9c6; -} -.panel-info { - border-color: #bce8f1; -} -.panel-info > .panel-heading { - color: #31708f; - background-color: #d9edf7; - border-color: #bce8f1; -} -.panel-info > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #bce8f1; -} -.panel-info > .panel-heading .badge { - color: #d9edf7; - background-color: #31708f; -} -.panel-info > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #bce8f1; -} -.panel-warning { - border-color: #faebcc; -} -.panel-warning > .panel-heading { - color: #8a6d3b; - background-color: #fcf8e3; - border-color: #faebcc; -} -.panel-warning > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #faebcc; -} -.panel-warning > .panel-heading .badge { - color: #fcf8e3; - background-color: #8a6d3b; -} -.panel-warning > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #faebcc; -} -.panel-danger { - border-color: #ebccd1; -} -.panel-danger > .panel-heading { - color: #a94442; - background-color: #f2dede; - border-color: #ebccd1; -} -.panel-danger > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #ebccd1; -} -.panel-danger > .panel-heading .badge { - color: #f2dede; - background-color: #a94442; -} -.panel-danger > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #ebccd1; -} - -/* Inline Group */ - -.input-group { - position: relative; - display: table; - border-collapse: separate; -} -.input-group[class*="col-"] { - float: none; - padding-left: 0; - padding-right: 0; -} -.input-group .form-control { - position: relative; - z-index: 2; - float: left; - width: 100%; - margin-bottom: 0; -} -.input-group .form-control:focus { - z-index: 3; -} -.input-group-lg > .form-control, -.input-group-lg > .input-group-addon, -.input-group-lg > .input-group-btn > .btn { - height: 41px; - padding: 10px 16px; - font-size: 15px; - line-height: 1.3333333; - border-radius: 6px; -} -select.input-group-lg > .form-control, -select.input-group-lg > .input-group-addon, -select.input-group-lg > .input-group-btn > .btn { - height: 41px; - line-height: 41px; -} -textarea.input-group-lg > .form-control, -textarea.input-group-lg > .input-group-addon, -textarea.input-group-lg > .input-group-btn > .btn, -select[multiple].input-group-lg > .form-control, -select[multiple].input-group-lg > .input-group-addon, -select[multiple].input-group-lg > .input-group-btn > .btn { - height: auto; -} -.input-group-sm > .form-control, -.input-group-sm > .input-group-addon, -.input-group-sm > .input-group-btn > .btn { - height: 30px; - padding: 5px 10px; - font-size: 12px; - line-height: 1.5; - border-radius: 3px; -} -select.input-group-sm > .form-control, -select.input-group-sm > .input-group-addon, -select.input-group-sm > .input-group-btn > .btn { - height: 30px; - line-height: 30px; -} -textarea.input-group-sm > .form-control, -textarea.input-group-sm > .input-group-addon, -textarea.input-group-sm > .input-group-btn > .btn, -select[multiple].input-group-sm > .form-control, -select[multiple].input-group-sm > .input-group-addon, -select[multiple].input-group-sm > .input-group-btn > .btn { - height: auto; -} -.input-group-addon, -.input-group-btn, -.input-group .form-control { - display: table-cell; -} -.input-group-addon:not(:first-child):not(:last-child), -.input-group-btn:not(:first-child):not(:last-child), -.input-group .form-control:not(:first-child):not(:last-child) { - border-radius: 0; -} -.input-group-addon, -.input-group-btn { - width: 1%; - white-space: nowrap; - vertical-align: middle; -} -.input-group-addon { - padding: 6px 12px; - font-size: 14px; - font-weight: normal; - line-height: 1; - color: #555555; - text-align: center; - background-color: #eeeeee; - border: 1px solid #cccccc; - border-radius: 4px; -} -.input-group-addon.input-sm { - padding: 5px 10px; - font-size: 12px; - border-radius: 3px; -} -.input-group-addon.input-lg { - padding: 10px 16px; - font-size: 15px; - border-radius: 6px; -} -.input-group-addon input[type="radio"], -.input-group-addon input[type="checkbox"] { - margin-top: 0; -} -.input-group .form-control:first-child, -.input-group-addon:first-child, -.input-group-btn:first-child > .btn, -.input-group-btn:first-child > .btn-group > .btn, -.input-group-btn:first-child > .dropdown-toggle, -.input-group-btn:last-child > .btn:not(:last-child):not(.dropdown-toggle), -.input-group-btn:last-child > .btn-group:not(:last-child) > .btn { - border-bottom-right-radius: 0; - border-top-right-radius: 0; -} -.input-group-addon:first-child { - border-right: 0; -} -.input-group .form-control:last-child, -.input-group-addon:last-child, -.input-group-btn:last-child > .btn, -.input-group-btn:last-child > .btn-group > .btn, -.input-group-btn:last-child > .dropdown-toggle, -.input-group-btn:first-child > .btn:not(:first-child), -.input-group-btn:first-child > .btn-group:not(:first-child) > .btn { - border-bottom-left-radius: 0; - border-top-left-radius: 0; -} -.input-group-addon:last-child { - border-left: 0; -} -.input-group-btn { - position: relative; - font-size: 0; - white-space: nowrap; -} -.input-group-btn > .btn { - position: relative; -} -.input-group-btn > .btn + .btn { - margin-left: -1px; -} -.input-group-btn > .btn:hover, -.input-group-btn > .btn:focus, -.input-group-btn > .btn:active { - z-index: 2; -} -.input-group-btn:first-child > .btn, -.input-group-btn:first-child > .btn-group { - margin-right: -1px; -} -.input-group-btn:last-child > .btn, -.input-group-btn:last-child > .btn-group { - z-index: 2; - margin-left: -1px; -} -.clearfix:before, -.clearfix:after, -.form-horizontal .form-group:before, -.form-horizontal .form-group:after { - content: " "; - display: table; -} -.clearfix:after, -.form-horizontal .form-group:after { - clear: both; -} diff --git a/data/core.telegram.org/css/core-widgets.css b/data/core.telegram.org/css/core-widgets.css deleted file mode 100644 index 6b86cfbf74..0000000000 --- a/data/core.telegram.org/css/core-widgets.css +++ /dev/null @@ -1,105 +0,0 @@ -.widget-accent-colors { - display: flex; - flex-wrap: nowrap; - justify-content: space-between; - max-width: 480px; - margin: 3px 0 0; -} -.widget-accent-colors .widget-accent-color-item { - position: relative; - flex-basis: 42px; - font-weight: normal; - text-align: center; - cursor: pointer; -} -.widget-accent-color-item input.radio { - position: absolute; - left: -5000px; -} -.widget-accent-color-item input.radio + .widget-color-circle:after { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - border-radius: 50%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%23fff" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E') no-repeat center 11px; - transition: transform 0.12s linear; - transform: scale3d(0, 0, 1); -} -.widget-accent-color-item input.radio + .widget-color-circle.bordered, -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom.bordered { - box-shadow: inset 0 0 0 1px #eaeaea; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom.bordered { - border: none; -} -.widget-accent-color-item input.radio + .widget-color-circle.light:after { - background-image: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%2315202b" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E'); -} -.widget-accent-color-item input.radio:checked + .widget-color-circle:after { - transform: scale3d(1, 1, 1); -} -.widget-color-circle { - position: relative; - display: inline-block; - vertical-align: top; - width: 36px; - height: 36px; - border-radius: 50%; - background-color: #319BE6; - transition: background-color 0.12s ease, box-shadow 0.12s ease; -} -.widget-color-circle-custom { - background-color: #F5F5F5; - color: #F5F5F5; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom:before { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="14" viewBox="0 0 15 14" width="15" xmlns="http://www.w3.org/2000/svg"%3E%3Cpath d="m3.9468491 8.55631162c-1.3103539 0-2.36810946 1.04207749-2.36810946 2.33300928 0 1.0187474-.91566899 1.5553396-1.57873964 1.5553396.72622023.9487571 1.96553085 1.5553395 3.15747928 1.5553395 1.7445073 0 3.15747928-1.3920289 3.15747928-3.1106791 0-1.29093179-1.05775556-2.33300928-2.36810946-2.33300928zm10.8222602-7.28676572-1.0577555-1.04207749c-.3078543-.30329121-.8051572-.30329121-1.1130115 0l-7.07275356 6.96792112 2.170767 2.13859186 7.07275356-6.96792112c.3078543-.30329121.3078543-.79322316 0-1.09651437z" fill="%23bdbdbd"/%3E%3C/svg%3E') no-repeat center; - transition: opacity 0.12s ease; -} -.widget-color-label { - font-size: 12px; - line-height: 14px; - margin-top: 8px; - color: #333; -} -.widget-color-label-custom { - transition: opacity 0.12s ease; - position: absolute; - width: 100%; -} -.widget-accent-color-field-item { - transition: all .2s ease; - opacity: 0; -} -.widget-accent-color-field-item input.widget-accent-color-field { - font-size: 12px !important; - line-height: 14px !important; - text-transform: uppercase; - position: relative; - text-align: center; - margin-top: 3px !important; - padding: 5px 0 !important; - color: #222 !important; - width: 52px !important; -} -.widget-accent-color-item input.radio:checked ~ .widget-accent-color-field-item { - opacity: 1; -} -.widget-accent-color-item input.radio:checked ~ .widget-color-circle-custom { - background-color: currentColor !important; -} -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom:before, -.widget-accent-color-item input.radio:checked ~ .widget-color-label-custom { - opacity: 0; -} diff --git a/data/core.telegram.org/css/telegram-extra.css b/data/core.telegram.org/css/telegram-extra.css deleted file mode 100644 index 6b408d1ae4..0000000000 --- a/data/core.telegram.org/css/telegram-extra.css +++ /dev/null @@ -1,246 +0,0 @@ -.telegram-passport-wrap { - overflow: hidden; -} -.telegram-passport-form { - position: relative; -} -.telegram-passport-form .control-label { - line-height: 20px; - padding-top: 11px; -} -.telegram-passport-header { - font-size: 18px; - line-height: 27px; -} -.telegram-passport-greeting { - margin-right: 10px; -} -.telegram-passport-greeting a, -.telegram-passport-greeting a:hover { - color: inherit; -} -.telegram-passport-logout { - font-size: 16px; - font-weight: normal; -} -.telegram-passport-login-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-relogin-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-pending { - padding: 20px 0 40px; - text-align: center; -} -.telegram-passport-block-header, -.telegram-passport-item { - border-bottom: 1px solid #e7e7e7; -} -.telegram-passport-block-header, -.telegram-passport-item-name, -.telegram-passport-item-value { - padding: 15px 0; - line-height: 20px; -} -.telegram-passport-block-header { - margin: 25px 0 0; -} -.telegram-passport-item-name { - margin-right: 15px; - margin-bottom: -5px; - padding-bottom: 0; - float: left; -} -.telegram-passport-item-files, -.telegram-passport-item-value { - clear: left; - font-weight: bold; -} -.telegram-passport-item-value { - transition: color .12s linear; -} -.telegram-passport-item-files { - padding: 6px 0; -} -.telegram-passport-item-file { - padding: 6px 0; - min-height: 60px; -} -.telegram-passport-item .telegram-passport-checkbox-right .checkbox-input { - margin: 0; -} -.telegram-passport-item .telegram-passport-checkbox-right { - float: right; - margin: 40px -5px 10px; - padding: 5px; -} -.telegram-passport-item-files .checkbox-item-block { - margin: 6px 0; -} -.telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; -} -.telegram-passport-scan-thumb { - display: inline-block; - width: 64px; - height: 48px; - background: #f7f7f7 no-repeat center; - background-size: cover; - float: left; - border-radius: 3px; - margin-right: 15px; -} -.telegram-passport-scan-name { - display: inline-block; - font-size: 14px; - padding: 3px 0 0; - transition: color .12s linear; - color: #2e87ca; -} -.telegram-passport-scan-size { - font-size: 13px; - padding: 1px 0 0; - font-weight: normal; - transition: color .12s linear; - color: #999; -} -.telegram-passport-item-value, -.telegram-passport-scan-info { - margin-right: 42px; -} -.telegram-passport-item .checkbox-item-block .checkbox-label { - transition: color .12s linear; -} -.telegram-passport-item.item-rejected .telegram-passport-item-value, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-name, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-size, -.telegram-passport-item .checkbox-item-block.item-rejected .checkbox-label { - color: #c93c3c; -} - -.telegram-passport-item .checkbox-item-block .checkbox-input-icon:before { - border-color: #eb5454; - background-color: #eb5454; - background-position: -3px -119px; -} -.telegram-passport-item .checkbox-item-block input.checkbox:checked + .checkbox-input .ripple { - background-color: rgba(235, 84, 84, .2); -} -.telegram-passport-errors-wrap { - text-align: right; - margin: 20px 16px 0; -} -.btn.telegram-passport-errors { - font-size: 15px; - font-weight: 500; - line-height: 20px; - border-radius: 6px; - background-color: transparent; - padding: 8px 16px 10px; - margin: 4px -16px; - border: none; - color: #c93c3c; - position: relative; - z-index: 1; -} -.btn.telegram-passport-errors:hover { - background-color: #f7e3e3; -} -.btn.telegram-passport-errors:focus { - outline: none; -} -.btn.telegram-passport-errors:active { - box-shadow: none; -} -.telegram-passport-errors-icon { - display: inline-block; - vertical-align: top; - width: 18px; - height: 19px; - margin: 1px 12px 0 0; - background: url(/img/passport_bug.png) no-repeat 0 0; -} -@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi) { - .telegram-passport-errors-icon { - background-image: url(/img/passport_bug_2x.png); - background-size: 18px 19px; - } -} -.telegram-passport-errors-sent { - font-size: 14px; - line-height: 20px; - padding: 13px 24px 0 0; - color: #999; - transition: opacity .12s linear; - opacity: 0; -} -.telegram-passport-errors-sent.shown { - opacity: 1; -} - -@media (min-width: 768px) { - .telegram-passport-login-wrap { - text-align: left; - } - .telegram-passport-relogin-wrap { - text-align: left; - margin: 50px 0 50px 240px; - } - .telegram-passport-item-files, - .telegram-passport-item-value { - clear: none; - margin-left: 240px; - } - .telegram-passport-item .telegram-passport-checkbox-right { - margin-top: 10px; - } - .telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; - } - .telegram-passport-errors-wrap { - position: absolute; - right: 0; - margin: 50px 0 0; - } -} - -.telegram-passport-form .sub-control-label { - text-align: left; - margin: 11px 0 6px; -} -.telegram-passport-form .sub-control-label .radio-label { - font-weight: bold; -} -.telegram-passport-form .sub-control-label .radio-item + .radio-item, -.telegram-passport-form .sub-control-label .checkbox-item + .checkbox-item { - margin-left: 25px; -} -.telegram-passport-form label.control-label .radio-label { - font-weight: bold; -} -.passport-opt, -.passport-opt-col { - display: inline-block; - margin-left: 31px; - margin-top: -10px; -} -.passport-opt + .passport-opt, -.passport-opt-col + .passport-opt-col { - margin-left: 0; -} -@media (min-width: 992px) { - .passport-opt-col { - margin-left: 0; - margin-top: 0; - text-align: center; - } - .passport-opt-col .checkbox-label { - text-align: left; - } - .passport-opt-col .checkbox-item input.checkbox ~ .checkbox-label { - display: none; - } -} 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.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/js/core-widgets.js b/data/core.telegram.org/js/core-widgets.js deleted file mode 100644 index 67bf4c7d05..0000000000 --- a/data/core.telegram.org/js/core-widgets.js +++ /dev/null @@ -1,279 +0,0 @@ -function fixColor(color) { - color = color.toUpperCase(); - if (color.length == 1 || color.length == 2) { - color = color + color + color; - } else if (color.length > 3 && color.length < 6) { - color = color.substr(0, 3); - } else if (color.length > 6) { - color = color.substr(0, 6); - } - return color; -} - -function isColorLight(color, k) { - var hsl = rgb2hsl(color); - if (typeof k === 'undefined') k = 0.8; - if (k > 0) return (hsl.l > k); - return (hsl.l < (1 + k)); -} - -function rgb2hsl(rgb) { - rgb = fixColor(rgb); - if (rgb.length == 3) { - rgb = rgb[0] + rgb[0] + rgb[1] + rgb[1] + rgb[2] + rgb[2]; - } - var r = parseInt(rgb.substr(0, 2), 16); - var g = parseInt(rgb.substr(2, 2), 16); - var b = parseInt(rgb.substr(4, 2), 16); - r /= 255; g /= 255; b /= 255; - var max = Math.max(r, g, b), - min = Math.min(r, g, b); - var h, s, l = (max + min) / 2; - if (max == min) { - h = s = 0; // achromatic - } else { - var d = max - min; - s = l > 0.5 ? d / (2 - max - min) : d / (max + min); - switch (max) { - case r: h = (g - b) / d + (g < b ? 6 : 0); break; - case g: h = (b - r) / d + 2; break; - case b: h = (r - g) / d + 4; break; - } - h /= 6; - } - return {h: h, s: s, l: l}; -} - -var PostWidget = { - options: {}, - init: function(options) { - var form = $('#post_widget_config').get(0); - if (!form) return; - PostWidget.options = options || {}; - $('.form-telegram input.form-control[type="text"]').on('change blur', function() { - PostWidget.update(); - }); - $('.form-telegram input.radio, .form-telegram input.checkbox').on('change', function() { - var is_dark = (this.getAttribute('name') == 'dark'); - PostWidget.update(is_dark); - }); - $('.widget-accent-color-item input.radio').on('change', function() { - if (this.value == 'custom') { - $('.widget-accent-color-field').select(); - } - PostWidget.update(); - }); - $('.widget-accent-color-field').on('input', function() { - var val = this.value; - this.value = val.toUpperCase().replace(/[^0-9A-F]+/g, ''); - var color = fixColor(this.value); - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - }); - $('.widget-accent-color-field').on('focus', function() { - $('.widget-accent-color-item .radio[value="custom"]').prop('checked', true); - PostWidget.update(); - }); - PostWidget.update(); - initRipple(); - }, - update: function(toggle_dark) { - var options = PostWidget.options || {}; - var form = $('#post_widget_config').get(0); - if (!form) return; - var tfi = $('#post_link').parents('.textfield-item'); - var post_link = $('#post_link').val() || options.default_link, - match; - if (match = post_link.match(/^(?:(?:https?):\/\/)?(?:t\.me|telegram\.me|telegram\.dog)\/([a-zA-Z0-9_]+\/\d+)(?:\?(.*))?$/i)) { - var post_id = match[1], suffix = match[2] || ''; - var querystring = suffix.split('#')[0]; - var str_values = querystring.split('&'); - var query = {}; - for (var i = 0; i < str_values.length; i++) { - var key_value = str_values[i].split('='); - var key = decodeURIComponent(key_value[0]); - var value = key_value.length > 1 ? decodeURIComponent(key_value[1]) : null; - query[key] = value; - } - var single = typeof query.single !== 'undefined'; - var comment_id = parseInt(query.comment); - } else { - tfi.addClass('is-invalid'); - $('#post_link_error').html(options.link_error); - $('#post_link').one('input', function() { - tfi.removeClass('is-invalid'); - }); - return; - } - tfi.removeClass('is-invalid'); - var width = form.width.value; - if (!width) width = '100%'; - var author_photo = form.author_photo.value; - var dark = form.dark.checked; - var dark_colors = {}; - $('.widget-accent-color-item[data-color]').each(function() { - var color = $(this).attr('data-color'); - var dark_color = $(this).attr('data-dark-color'); - var bg_color = $(this).attr(dark ? 'data-dark-color' : 'data-bg-color'); - var text = $(this).attr(dark ? 'data-dark-text' : 'data-text'); - var cur_color = dark && dark_color ? dark_color : color; - dark_colors[color] = dark_color; - $('.widget-color-circle', this).css('backgroundColor', '#' + bg_color).toggleClass('light', isColorLight(cur_color)).toggleClass('bordered', isColorLight(cur_color, 0.95)); - if (text) { - $('.widget-color-label', this).text(text); - } - }); - var color = form.color.value; - var dark_color = ''; - var customcolor = form.customcolor.value; - if (color == 'default') { - color = ''; - dark_color = ''; - } else if (color == 'custom') { - color = fixColor(customcolor); - if (color != customcolor) { - form.customcolor.value = color; - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - } - dark_color = color; - } else { - dark_color = dark_colors[color] || color; - } - if (!color) { - color = ''; - dark_color = ''; - $('.widget-accent-color-item .radio[value="default"]').prop('checked', true); - var custom_default = form.customcolor.defaultValue; - form.customcolor.value = custom_default; - $('.widget-color-circle-custom').css('color', custom_default ? '#' + custom_default : '').toggleClass('light', isColorLight(custom_default)).toggleClass('bordered', isColorLight(custom_default, 0.95)); - } - var code = ''; - $('#embed_code').val(code); - $('#embed_code').height(0); - $('#embed_code').height($('#embed_code').get(0).scrollHeight); - if (PostWidget.lastCode != code) { - PostWidget.lastCode = code; - $('#widget_container').toggleClass('dark', !!dark); - if (toggle_dark) { - var frame = $('#widget_container iframe').get(0); - Telegram.setWidgetOptions({dark: dark}, frame); - } else { - $('#widget_container').html(code); - } - } - } -}; - -var DiscussionWidget = { - options: {}, - init: function(options) { - var form = $('#discussion_widget_config').get(0); - if (!form) return; - DiscussionWidget.options = options || {}; - $('.form-telegram input.form-control[type="text"]').on('change blur', function() { - DiscussionWidget.update(); - }); - $('.form-telegram input.checkbox').on('change', function() { - var is_dark = (this.getAttribute('name') == 'dark'); - DiscussionWidget.update(is_dark); - }); - $('.widget-accent-color-item input.radio').on('change', function() { - if (this.value == 'custom') { - $('.widget-accent-color-field').select(); - } - DiscussionWidget.update(); - }); - $('.widget-accent-color-field').on('input', function() { - var val = this.value; - this.value = val.toUpperCase().replace(/[^0-9A-F]+/g, ''); - var color = fixColor(this.value); - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - }); - $('.widget-accent-color-field').on('focus', function() { - $('.widget-accent-color-item .radio[value="custom"]').prop('checked', true); - DiscussionWidget.update(); - }); - DiscussionWidget.update(); - initRipple(); - }, - update: function(toggle_dark) { - var options = DiscussionWidget.options || {}; - var form = $('#discussion_widget_config').get(0); - if (!form) return; - var tfi = $('#post_link').parents('.textfield-item'); - var post_link = $('#post_link').val() || options.default_link, - match; - var post_full_id = '', post_id = 0; - if (match = post_link.match(/^(?:(?:https?):\/\/)?(?:t\.me|telegram\.me|telegram\.dog)\/([a-zA-Z0-9_]+(\/\d+)?)/i)) { - post_full_id = match[1]; - post_id = match[2] || 0; - } else { - tfi.addClass('is-invalid'); - $('#post_link_error').html(options.link_error); - $('#post_link').one('input', function() { - tfi.removeClass('is-invalid'); - }); - return; - } - $('.canonical-helper', form).toggleClass('hide', !!post_id); - tfi.removeClass('is-invalid'); - var limit = parseInt(form.comments_limit.value) || 5; - var real_limit = Math.max(3, Math.min(50, limit)); - form.comments_limit.value = real_limit; - var height = parseInt(form.height.value) || 0; - var real_height = height > 0 ? Math.max(300, height) : 0; - form.height.value = real_height || ''; - var dark = form.dark.checked; - var dark_colors = {}; - $('.widget-accent-color-item[data-color]').each(function() { - var color = $(this).attr('data-color'); - var dark_color = $(this).attr('data-dark-color'); - var bg_color = $(this).attr(dark ? 'data-dark-color' : 'data-bg-color'); - var text = $(this).attr(dark ? 'data-dark-text' : 'data-text'); - var cur_color = dark && dark_color ? dark_color : color; - dark_colors[color] = dark_color; - $('.widget-color-circle', this).css('backgroundColor', '#' + bg_color).toggleClass('light', isColorLight(cur_color)).toggleClass('bordered', isColorLight(cur_color, 0.95)); - if (text) { - $('.widget-color-label', this).text(text); - } - }); - var color = form.color.value; - var dark_color = ''; - var customcolor = form.customcolor.value; - if (color == 'default') { - color = ''; - dark_color = ''; - } else if (color == 'custom') { - color = fixColor(customcolor); - if (color != customcolor) { - form.customcolor.value = color; - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - } - dark_color = color; - } else { - dark_color = dark_colors[color] || color; - } - if (!color) { - color = ''; - dark_color = ''; - $('.widget-accent-color-item .radio[value="default"]').prop('checked', true); - var custom_default = form.customcolor.defaultValue; - form.customcolor.value = custom_default; - $('.widget-color-circle-custom').css('color', custom_default ? '#' + custom_default : '').toggleClass('light', isColorLight(custom_default)).toggleClass('bordered', isColorLight(custom_default, 0.95)); - } - var colorful = form.colorful.checked; - var code = ''; - $('#embed_code').val(code); - $('#embed_code').height(0); - $('#embed_code').height($('#embed_code').get(0).scrollHeight); - if (DiscussionWidget.lastCode != code) { - DiscussionWidget.lastCode = code; - $('#widget_container').toggleClass('dark', !!dark); - if (toggle_dark) { - var frame = $('#widget_container iframe').get(0); - Telegram.setWidgetOptions({dark: dark}, frame); - } else { - $('#widget_container').html(code); - } - } - } -}; diff --git a/data/core.telegram.org/js/jquery-ui.min.js b/data/core.telegram.org/js/jquery-ui.min.js deleted file mode 100644 index a47c061a05..0000000000 --- a/data/core.telegram.org/js/jquery-ui.min.js +++ /dev/null @@ -1,9 +0,0 @@ -/*! jQuery UI - v1.11.4 - 2017-08-30 -* http://jqueryui.com -* Includes: core.js, widget.js, mouse.js, draggable.js, resizable.js, sortable.js, slider.js, effect.js, effect-slide.js -* Copyright jQuery Foundation and other contributors; Licensed MIT */ - -(function(t){"function"==typeof define&&define.amd?define(["jquery"],t):t(jQuery)})(function(t){function e(e,s){var n,o,a,r=e.nodeName.toLowerCase();return"area"===r?(n=e.parentNode,o=n.name,e.href&&o&&"map"===n.nodeName.toLowerCase()?(a=t("img[usemap='#"+o+"']")[0],!!a&&i(a)):!1):(/^(input|select|textarea|button|object)$/.test(r)?!e.disabled:"a"===r?e.href||s:s)&&i(e)}function i(e){return t.expr.filters.visible(e)&&!t(e).parents().addBack().filter(function(){return"hidden"===t.css(this,"visibility")}).length}t.ui=t.ui||{},t.extend(t.ui,{version:"1.11.4",keyCode:{BACKSPACE:8,COMMA:188,DELETE:46,DOWN:40,END:35,ENTER:13,ESCAPE:27,HOME:36,LEFT:37,PAGE_DOWN:34,PAGE_UP:33,PERIOD:190,RIGHT:39,SPACE:32,TAB:9,UP:38}}),t.fn.extend({scrollParent:function(e){var i=this.css("position"),s="absolute"===i,n=e?/(auto|scroll|hidden)/:/(auto|scroll)/,o=this.parents().filter(function(){var e=t(this);return s&&"static"===e.css("position")?!1:n.test(e.css("overflow")+e.css("overflow-y")+e.css("overflow-x"))}).eq(0);return"fixed"!==i&&o.length?o:t(this[0].ownerDocument||document)},uniqueId:function(){var t=0;return function(){return this.each(function(){this.id||(this.id="ui-id-"+ ++t)})}}(),removeUniqueId:function(){return this.each(function(){/^ui-id-\d+$/.test(this.id)&&t(this).removeAttr("id")})}}),t.extend(t.expr[":"],{data:t.expr.createPseudo?t.expr.createPseudo(function(e){return function(i){return!!t.data(i,e)}}):function(e,i,s){return!!t.data(e,s[3])},focusable:function(i){return e(i,!isNaN(t.attr(i,"tabindex")))},tabbable:function(i){var s=t.attr(i,"tabindex"),n=isNaN(s);return(n||s>=0)&&e(i,!n)}}),t("").outerWidth(1).jquery||t.each(["Width","Height"],function(e,i){function s(e,i,s,o){return t.each(n,function(){i-=parseFloat(t.css(e,"padding"+this))||0,s&&(i-=parseFloat(t.css(e,"border"+this+"Width"))||0),o&&(i-=parseFloat(t.css(e,"margin"+this))||0)}),i}var n="Width"===i?["Left","Right"]:["Top","Bottom"],o=i.toLowerCase(),a={innerWidth:t.fn.innerWidth,innerHeight:t.fn.innerHeight,outerWidth:t.fn.outerWidth,outerHeight:t.fn.outerHeight};t.fn["inner"+i]=function(e){return void 0===e?a["inner"+i].call(this):this.each(function(){t(this).css(o,s(this,e)+"px")})},t.fn["outer"+i]=function(e,n){return"number"!=typeof e?a["outer"+i].call(this,e):this.each(function(){t(this).css(o,s(this,e,!0,n)+"px")})}}),t.fn.addBack||(t.fn.addBack=function(t){return this.add(null==t?this.prevObject:this.prevObject.filter(t))}),t("").data("a-b","a").removeData("a-b").data("a-b")&&(t.fn.removeData=function(e){return function(i){return arguments.length?e.call(this,t.camelCase(i)):e.call(this)}}(t.fn.removeData)),t.ui.ie=!!/msie [\w.]+/.exec(navigator.userAgent.toLowerCase()),t.fn.extend({focus:function(e){return function(i,s){return"number"==typeof i?this.each(function(){var e=this;setTimeout(function(){t(e).focus(),s&&s.call(e)},i)}):e.apply(this,arguments)}}(t.fn.focus),disableSelection:function(){var t="onselectstart"in document.createElement("div")?"selectstart":"mousedown";return function(){return this.bind(t+".ui-disableSelection",function(t){t.preventDefault()})}}(),enableSelection:function(){return this.unbind(".ui-disableSelection")},zIndex:function(e){if(void 0!==e)return this.css("zIndex",e);if(this.length)for(var i,s,n=t(this[0]);n.length&&n[0]!==document;){if(i=n.css("position"),("absolute"===i||"relative"===i||"fixed"===i)&&(s=parseInt(n.css("zIndex"),10),!isNaN(s)&&0!==s))return s;n=n.parent()}return 0}}),t.ui.plugin={add:function(e,i,s){var n,o=t.ui[e].prototype;for(n in s)o.plugins[n]=o.plugins[n]||[],o.plugins[n].push([i,s[n]])},call:function(t,e,i,s){var n,o=t.plugins[e];if(o&&(s||t.element[0].parentNode&&11!==t.element[0].parentNode.nodeType))for(n=0;o.length>n;n++)t.options[o[n][0]]&&o[n][1].apply(t.element,i)}};var s=0,n=Array.prototype.slice;t.cleanData=function(e){return function(i){var s,n,o;for(o=0;null!=(n=i[o]);o++)try{s=t._data(n,"events"),s&&s.remove&&t(n).triggerHandler("remove")}catch(a){}e(i)}}(t.cleanData),t.widget=function(e,i,s){var n,o,a,r,l={},h=e.split(".")[0];return e=e.split(".")[1],n=h+"-"+e,s||(s=i,i=t.Widget),t.expr[":"][n.toLowerCase()]=function(e){return!!t.data(e,n)},t[h]=t[h]||{},o=t[h][e],a=t[h][e]=function(t,e){return this._createWidget?(arguments.length&&this._createWidget(t,e),void 0):new a(t,e)},t.extend(a,o,{version:s.version,_proto:t.extend({},s),_childConstructors:[]}),r=new i,r.options=t.widget.extend({},r.options),t.each(s,function(e,s){return t.isFunction(s)?(l[e]=function(){var t=function(){return i.prototype[e].apply(this,arguments)},n=function(t){return i.prototype[e].apply(this,t)};return function(){var e,i=this._super,o=this._superApply;return this._super=t,this._superApply=n,e=s.apply(this,arguments),this._super=i,this._superApply=o,e}}(),void 0):(l[e]=s,void 0)}),a.prototype=t.widget.extend(r,{widgetEventPrefix:o?r.widgetEventPrefix||e:e},l,{constructor:a,namespace:h,widgetName:e,widgetFullName:n}),o?(t.each(o._childConstructors,function(e,i){var s=i.prototype;t.widget(s.namespace+"."+s.widgetName,a,i._proto)}),delete o._childConstructors):i._childConstructors.push(a),t.widget.bridge(e,a),a},t.widget.extend=function(e){for(var i,s,o=n.call(arguments,1),a=0,r=o.length;r>a;a++)for(i in o[a])s=o[a][i],o[a].hasOwnProperty(i)&&void 0!==s&&(e[i]=t.isPlainObject(s)?t.isPlainObject(e[i])?t.widget.extend({},e[i],s):t.widget.extend({},s):s);return e},t.widget.bridge=function(e,i){var s=i.prototype.widgetFullName||e;t.fn[e]=function(o){var a="string"==typeof o,r=n.call(arguments,1),l=this;return a?this.each(function(){var i,n=t.data(this,s);return"instance"===o?(l=n,!1):n?t.isFunction(n[o])&&"_"!==o.charAt(0)?(i=n[o].apply(n,r),i!==n&&void 0!==i?(l=i&&i.jquery?l.pushStack(i.get()):i,!1):void 0):t.error("no such method '"+o+"' for "+e+" widget instance"):t.error("cannot call methods on "+e+" prior to initialization; "+"attempted to call method '"+o+"'")}):(r.length&&(o=t.widget.extend.apply(null,[o].concat(r))),this.each(function(){var e=t.data(this,s);e?(e.option(o||{}),e._init&&e._init()):t.data(this,s,new i(o,this))})),l}},t.Widget=function(){},t.Widget._childConstructors=[],t.Widget.prototype={widgetName:"widget",widgetEventPrefix:"",defaultElement:"
    ",options:{disabled:!1,create:null},_createWidget:function(e,i){i=t(i||this.defaultElement||this)[0],this.element=t(i),this.uuid=s++,this.eventNamespace="."+this.widgetName+this.uuid,this.bindings=t(),this.hoverable=t(),this.focusable=t(),i!==this&&(t.data(i,this.widgetFullName,this),this._on(!0,this.element,{remove:function(t){t.target===i&&this.destroy()}}),this.document=t(i.style?i.ownerDocument:i.document||i),this.window=t(this.document[0].defaultView||this.document[0].parentWindow)),this.options=t.widget.extend({},this.options,this._getCreateOptions(),e),this._create(),this._trigger("create",null,this._getCreateEventData()),this._init()},_getCreateOptions:t.noop,_getCreateEventData:t.noop,_create:t.noop,_init:t.noop,destroy:function(){this._destroy(),this.element.unbind(this.eventNamespace).removeData(this.widgetFullName).removeData(t.camelCase(this.widgetFullName)),this.widget().unbind(this.eventNamespace).removeAttr("aria-disabled").removeClass(this.widgetFullName+"-disabled "+"ui-state-disabled"),this.bindings.unbind(this.eventNamespace),this.hoverable.removeClass("ui-state-hover"),this.focusable.removeClass("ui-state-focus")},_destroy:t.noop,widget:function(){return this.element},option:function(e,i){var s,n,o,a=e;if(0===arguments.length)return t.widget.extend({},this.options);if("string"==typeof e)if(a={},s=e.split("."),e=s.shift(),s.length){for(n=a[e]=t.widget.extend({},this.options[e]),o=0;s.length-1>o;o++)n[s[o]]=n[s[o]]||{},n=n[s[o]];if(e=s.pop(),1===arguments.length)return void 0===n[e]?null:n[e];n[e]=i}else{if(1===arguments.length)return void 0===this.options[e]?null:this.options[e];a[e]=i}return this._setOptions(a),this},_setOptions:function(t){var e;for(e in t)this._setOption(e,t[e]);return this},_setOption:function(t,e){return this.options[t]=e,"disabled"===t&&(this.widget().toggleClass(this.widgetFullName+"-disabled",!!e),e&&(this.hoverable.removeClass("ui-state-hover"),this.focusable.removeClass("ui-state-focus"))),this},enable:function(){return this._setOptions({disabled:!1})},disable:function(){return this._setOptions({disabled:!0})},_on:function(e,i,s){var n,o=this;"boolean"!=typeof e&&(s=i,i=e,e=!1),s?(i=n=t(i),this.bindings=this.bindings.add(i)):(s=i,i=this.element,n=this.widget()),t.each(s,function(s,a){function r(){return e||o.options.disabled!==!0&&!t(this).hasClass("ui-state-disabled")?("string"==typeof a?o[a]:a).apply(o,arguments):void 0}"string"!=typeof a&&(r.guid=a.guid=a.guid||r.guid||t.guid++);var l=s.match(/^([\w:-]*)\s*(.*)$/),h=l[1]+o.eventNamespace,c=l[2];c?n.delegate(c,h,r):i.bind(h,r)})},_off:function(e,i){i=(i||"").split(" ").join(this.eventNamespace+" ")+this.eventNamespace,e.unbind(i).undelegate(i),this.bindings=t(this.bindings.not(e).get()),this.focusable=t(this.focusable.not(e).get()),this.hoverable=t(this.hoverable.not(e).get())},_delay:function(t,e){function i(){return("string"==typeof t?s[t]:t).apply(s,arguments)}var s=this;return setTimeout(i,e||0)},_hoverable:function(e){this.hoverable=this.hoverable.add(e),this._on(e,{mouseenter:function(e){t(e.currentTarget).addClass("ui-state-hover")},mouseleave:function(e){t(e.currentTarget).removeClass("ui-state-hover")}})},_focusable:function(e){this.focusable=this.focusable.add(e),this._on(e,{focusin:function(e){t(e.currentTarget).addClass("ui-state-focus")},focusout:function(e){t(e.currentTarget).removeClass("ui-state-focus")}})},_trigger:function(e,i,s){var n,o,a=this.options[e];if(s=s||{},i=t.Event(i),i.type=(e===this.widgetEventPrefix?e:this.widgetEventPrefix+e).toLowerCase(),i.target=this.element[0],o=i.originalEvent)for(n in o)n in i||(i[n]=o[n]);return this.element.trigger(i,s),!(t.isFunction(a)&&a.apply(this.element[0],[i].concat(s))===!1||i.isDefaultPrevented())}},t.each({show:"fadeIn",hide:"fadeOut"},function(e,i){t.Widget.prototype["_"+e]=function(s,n,o){"string"==typeof n&&(n={effect:n});var a,r=n?n===!0||"number"==typeof n?i:n.effect||i:e;n=n||{},"number"==typeof n&&(n={duration:n}),a=!t.isEmptyObject(n),n.complete=o,n.delay&&s.delay(n.delay),a&&t.effects&&t.effects.effect[r]?s[e](n):r!==e&&s[r]?s[r](n.duration,n.easing,o):s.queue(function(i){t(this)[e](),o&&o.call(s[0]),i()})}}),t.widget;var o=!1;t(document).mouseup(function(){o=!1}),t.widget("ui.mouse",{version:"1.11.4",options:{cancel:"input,textarea,button,select,option",distance:1,delay:0},_mouseInit:function(){var e=this;this.element.bind("mousedown."+this.widgetName,function(t){return e._mouseDown(t)}).bind("click."+this.widgetName,function(i){return!0===t.data(i.target,e.widgetName+".preventClickEvent")?(t.removeData(i.target,e.widgetName+".preventClickEvent"),i.stopImmediatePropagation(),!1):void 0}),this.started=!1},_mouseDestroy:function(){this.element.unbind("."+this.widgetName),this._mouseMoveDelegate&&this.document.unbind("mousemove."+this.widgetName,this._mouseMoveDelegate).unbind("mouseup."+this.widgetName,this._mouseUpDelegate)},_mouseDown:function(e){if(!o){this._mouseMoved=!1,this._mouseStarted&&this._mouseUp(e),this._mouseDownEvent=e;var i=this,s=1===e.which,n="string"==typeof this.options.cancel&&e.target.nodeName?t(e.target).closest(this.options.cancel).length:!1;return s&&!n&&this._mouseCapture(e)?(this.mouseDelayMet=!this.options.delay,this.mouseDelayMet||(this._mouseDelayTimer=setTimeout(function(){i.mouseDelayMet=!0},this.options.delay)),this._mouseDistanceMet(e)&&this._mouseDelayMet(e)&&(this._mouseStarted=this._mouseStart(e)!==!1,!this._mouseStarted)?(e.preventDefault(),!0):(!0===t.data(e.target,this.widgetName+".preventClickEvent")&&t.removeData(e.target,this.widgetName+".preventClickEvent"),this._mouseMoveDelegate=function(t){return i._mouseMove(t)},this._mouseUpDelegate=function(t){return i._mouseUp(t)},this.document.bind("mousemove."+this.widgetName,this._mouseMoveDelegate).bind("mouseup."+this.widgetName,this._mouseUpDelegate),e.preventDefault(),o=!0,!0)):!0}},_mouseMove:function(e){if(this._mouseMoved){if(t.ui.ie&&(!document.documentMode||9>document.documentMode)&&!e.button)return this._mouseUp(e);if(!e.which)return this._mouseUp(e)}return(e.which||e.button)&&(this._mouseMoved=!0),this._mouseStarted?(this._mouseDrag(e),e.preventDefault()):(this._mouseDistanceMet(e)&&this._mouseDelayMet(e)&&(this._mouseStarted=this._mouseStart(this._mouseDownEvent,e)!==!1,this._mouseStarted?this._mouseDrag(e):this._mouseUp(e)),!this._mouseStarted)},_mouseUp:function(e){return this.document.unbind("mousemove."+this.widgetName,this._mouseMoveDelegate).unbind("mouseup."+this.widgetName,this._mouseUpDelegate),this._mouseStarted&&(this._mouseStarted=!1,e.target===this._mouseDownEvent.target&&t.data(e.target,this.widgetName+".preventClickEvent",!0),this._mouseStop(e)),o=!1,!1},_mouseDistanceMet:function(t){return Math.max(Math.abs(this._mouseDownEvent.pageX-t.pageX),Math.abs(this._mouseDownEvent.pageY-t.pageY))>=this.options.distance},_mouseDelayMet:function(){return this.mouseDelayMet},_mouseStart:function(){},_mouseDrag:function(){},_mouseStop:function(){},_mouseCapture:function(){return!0}}),t.widget("ui.draggable",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"drag",options:{addClasses:!0,appendTo:"parent",axis:!1,connectToSortable:!1,containment:!1,cursor:"auto",cursorAt:!1,grid:!1,handle:!1,helper:"original",iframeFix:!1,opacity:!1,refreshPositions:!1,revert:!1,revertDuration:500,scope:"default",scroll:!0,scrollSensitivity:20,scrollSpeed:20,snap:!1,snapMode:"both",snapTolerance:20,stack:!1,zIndex:!1,drag:null,start:null,stop:null},_create:function(){"original"===this.options.helper&&this._setPositionRelative(),this.options.addClasses&&this.element.addClass("ui-draggable"),this.options.disabled&&this.element.addClass("ui-draggable-disabled"),this._setHandleClassName(),this._mouseInit()},_setOption:function(t,e){this._super(t,e),"handle"===t&&(this._removeHandleClassName(),this._setHandleClassName())},_destroy:function(){return(this.helper||this.element).is(".ui-draggable-dragging")?(this.destroyOnClear=!0,void 0):(this.element.removeClass("ui-draggable ui-draggable-dragging ui-draggable-disabled"),this._removeHandleClassName(),this._mouseDestroy(),void 0)},_mouseCapture:function(e){var i=this.options;return this._blurActiveElement(e),this.helper||i.disabled||t(e.target).closest(".ui-resizable-handle").length>0?!1:(this.handle=this._getHandle(e),this.handle?(this._blockFrames(i.iframeFix===!0?"iframe":i.iframeFix),!0):!1)},_blockFrames:function(e){this.iframeBlocks=this.document.find(e).map(function(){var e=t(this);return t("
    ").css("position","absolute").appendTo(e.parent()).outerWidth(e.outerWidth()).outerHeight(e.outerHeight()).offset(e.offset())[0]})},_unblockFrames:function(){this.iframeBlocks&&(this.iframeBlocks.remove(),delete this.iframeBlocks)},_blurActiveElement:function(e){var i=this.document[0];if(this.handleElement.is(e.target))try{i.activeElement&&"body"!==i.activeElement.nodeName.toLowerCase()&&t(i.activeElement).blur()}catch(s){}},_mouseStart:function(e){var i=this.options;return this.helper=this._createHelper(e),this.helper.addClass("ui-draggable-dragging"),this._cacheHelperProportions(),t.ui.ddmanager&&(t.ui.ddmanager.current=this),this._cacheMargins(),this.cssPosition=this.helper.css("position"),this.scrollParent=this.helper.scrollParent(!0),this.offsetParent=this.helper.offsetParent(),this.hasFixedAncestor=this.helper.parents().filter(function(){return"fixed"===t(this).css("position")}).length>0,this.positionAbs=this.element.offset(),this._refreshOffsets(e),this.originalPosition=this.position=this._generatePosition(e,!1),this.originalPageX=e.pageX,this.originalPageY=e.pageY,i.cursorAt&&this._adjustOffsetFromHelper(i.cursorAt),this._setContainment(),this._trigger("start",e)===!1?(this._clear(),!1):(this._cacheHelperProportions(),t.ui.ddmanager&&!i.dropBehaviour&&t.ui.ddmanager.prepareOffsets(this,e),this._normalizeRightBottom(),this._mouseDrag(e,!0),t.ui.ddmanager&&t.ui.ddmanager.dragStart(this,e),!0)},_refreshOffsets:function(t){this.offset={top:this.positionAbs.top-this.margins.top,left:this.positionAbs.left-this.margins.left,scroll:!1,parent:this._getParentOffset(),relative:this._getRelativeOffset()},this.offset.click={left:t.pageX-this.offset.left,top:t.pageY-this.offset.top}},_mouseDrag:function(e,i){if(this.hasFixedAncestor&&(this.offset.parent=this._getParentOffset()),this.position=this._generatePosition(e,!0),this.positionAbs=this._convertPositionTo("absolute"),!i){var s=this._uiHash();if(this._trigger("drag",e,s)===!1)return this._mouseUp({}),!1;this.position=s.position}return this.helper[0].style.left=this.position.left+"px",this.helper[0].style.top=this.position.top+"px",t.ui.ddmanager&&t.ui.ddmanager.drag(this,e),!1},_mouseStop:function(e){var i=this,s=!1;return t.ui.ddmanager&&!this.options.dropBehaviour&&(s=t.ui.ddmanager.drop(this,e)),this.dropped&&(s=this.dropped,this.dropped=!1),"invalid"===this.options.revert&&!s||"valid"===this.options.revert&&s||this.options.revert===!0||t.isFunction(this.options.revert)&&this.options.revert.call(this.element,s)?t(this.helper).animate(this.originalPosition,parseInt(this.options.revertDuration,10),function(){i._trigger("stop",e)!==!1&&i._clear()}):this._trigger("stop",e)!==!1&&this._clear(),!1},_mouseUp:function(e){return this._unblockFrames(),t.ui.ddmanager&&t.ui.ddmanager.dragStop(this,e),this.handleElement.is(e.target)&&this.element.focus(),t.ui.mouse.prototype._mouseUp.call(this,e)},cancel:function(){return this.helper.is(".ui-draggable-dragging")?this._mouseUp({}):this._clear(),this},_getHandle:function(e){return this.options.handle?!!t(e.target).closest(this.element.find(this.options.handle)).length:!0},_setHandleClassName:function(){this.handleElement=this.options.handle?this.element.find(this.options.handle):this.element,this.handleElement.addClass("ui-draggable-handle")},_removeHandleClassName:function(){this.handleElement.removeClass("ui-draggable-handle")},_createHelper:function(e){var i=this.options,s=t.isFunction(i.helper),n=s?t(i.helper.apply(this.element[0],[e])):"clone"===i.helper?this.element.clone().removeAttr("id"):this.element;return n.parents("body").length||n.appendTo("parent"===i.appendTo?this.element[0].parentNode:i.appendTo),s&&n[0]===this.element[0]&&this._setPositionRelative(),n[0]===this.element[0]||/(fixed|absolute)/.test(n.css("position"))||n.css("position","absolute"),n},_setPositionRelative:function(){/^(?:r|a|f)/.test(this.element.css("position"))||(this.element[0].style.position="relative")},_adjustOffsetFromHelper:function(e){"string"==typeof e&&(e=e.split(" ")),t.isArray(e)&&(e={left:+e[0],top:+e[1]||0}),"left"in e&&(this.offset.click.left=e.left+this.margins.left),"right"in e&&(this.offset.click.left=this.helperProportions.width-e.right+this.margins.left),"top"in e&&(this.offset.click.top=e.top+this.margins.top),"bottom"in e&&(this.offset.click.top=this.helperProportions.height-e.bottom+this.margins.top)},_isRootNode:function(t){return/(html|body)/i.test(t.tagName)||t===this.document[0]},_getParentOffset:function(){var e=this.offsetParent.offset(),i=this.document[0];return"absolute"===this.cssPosition&&this.scrollParent[0]!==i&&t.contains(this.scrollParent[0],this.offsetParent[0])&&(e.left+=this.scrollParent.scrollLeft(),e.top+=this.scrollParent.scrollTop()),this._isRootNode(this.offsetParent[0])&&(e={top:0,left:0}),{top:e.top+(parseInt(this.offsetParent.css("borderTopWidth"),10)||0),left:e.left+(parseInt(this.offsetParent.css("borderLeftWidth"),10)||0)}},_getRelativeOffset:function(){if("relative"!==this.cssPosition)return{top:0,left:0};var t=this.element.position(),e=this._isRootNode(this.scrollParent[0]);return{top:t.top-(parseInt(this.helper.css("top"),10)||0)+(e?0:this.scrollParent.scrollTop()),left:t.left-(parseInt(this.helper.css("left"),10)||0)+(e?0:this.scrollParent.scrollLeft())}},_cacheMargins:function(){this.margins={left:parseInt(this.element.css("marginLeft"),10)||0,top:parseInt(this.element.css("marginTop"),10)||0,right:parseInt(this.element.css("marginRight"),10)||0,bottom:parseInt(this.element.css("marginBottom"),10)||0}},_cacheHelperProportions:function(){this.helperProportions={width:this.helper.outerWidth(),height:this.helper.outerHeight()}},_setContainment:function(){var e,i,s,n=this.options,o=this.document[0];return this.relativeContainer=null,n.containment?"window"===n.containment?(this.containment=[t(window).scrollLeft()-this.offset.relative.left-this.offset.parent.left,t(window).scrollTop()-this.offset.relative.top-this.offset.parent.top,t(window).scrollLeft()+t(window).width()-this.helperProportions.width-this.margins.left,t(window).scrollTop()+(t(window).height()||o.body.parentNode.scrollHeight)-this.helperProportions.height-this.margins.top],void 0):"document"===n.containment?(this.containment=[0,0,t(o).width()-this.helperProportions.width-this.margins.left,(t(o).height()||o.body.parentNode.scrollHeight)-this.helperProportions.height-this.margins.top],void 0):n.containment.constructor===Array?(this.containment=n.containment,void 0):("parent"===n.containment&&(n.containment=this.helper[0].parentNode),i=t(n.containment),s=i[0],s&&(e=/(scroll|auto)/.test(i.css("overflow")),this.containment=[(parseInt(i.css("borderLeftWidth"),10)||0)+(parseInt(i.css("paddingLeft"),10)||0),(parseInt(i.css("borderTopWidth"),10)||0)+(parseInt(i.css("paddingTop"),10)||0),(e?Math.max(s.scrollWidth,s.offsetWidth):s.offsetWidth)-(parseInt(i.css("borderRightWidth"),10)||0)-(parseInt(i.css("paddingRight"),10)||0)-this.helperProportions.width-this.margins.left-this.margins.right,(e?Math.max(s.scrollHeight,s.offsetHeight):s.offsetHeight)-(parseInt(i.css("borderBottomWidth"),10)||0)-(parseInt(i.css("paddingBottom"),10)||0)-this.helperProportions.height-this.margins.top-this.margins.bottom],this.relativeContainer=i),void 0):(this.containment=null,void 0)},_convertPositionTo:function(t,e){e||(e=this.position);var i="absolute"===t?1:-1,s=this._isRootNode(this.scrollParent[0]);return{top:e.top+this.offset.relative.top*i+this.offset.parent.top*i-("fixed"===this.cssPosition?-this.offset.scroll.top:s?0:this.offset.scroll.top)*i,left:e.left+this.offset.relative.left*i+this.offset.parent.left*i-("fixed"===this.cssPosition?-this.offset.scroll.left:s?0:this.offset.scroll.left)*i}},_generatePosition:function(t,e){var i,s,n,o,a=this.options,r=this._isRootNode(this.scrollParent[0]),l=t.pageX,h=t.pageY;return r&&this.offset.scroll||(this.offset.scroll={top:this.scrollParent.scrollTop(),left:this.scrollParent.scrollLeft()}),e&&(this.containment&&(this.relativeContainer?(s=this.relativeContainer.offset(),i=[this.containment[0]+s.left,this.containment[1]+s.top,this.containment[2]+s.left,this.containment[3]+s.top]):i=this.containment,t.pageX-this.offset.click.lefti[2]&&(l=i[2]+this.offset.click.left),t.pageY-this.offset.click.top>i[3]&&(h=i[3]+this.offset.click.top)),a.grid&&(n=a.grid[1]?this.originalPageY+Math.round((h-this.originalPageY)/a.grid[1])*a.grid[1]:this.originalPageY,h=i?n-this.offset.click.top>=i[1]||n-this.offset.click.top>i[3]?n:n-this.offset.click.top>=i[1]?n-a.grid[1]:n+a.grid[1]:n,o=a.grid[0]?this.originalPageX+Math.round((l-this.originalPageX)/a.grid[0])*a.grid[0]:this.originalPageX,l=i?o-this.offset.click.left>=i[0]||o-this.offset.click.left>i[2]?o:o-this.offset.click.left>=i[0]?o-a.grid[0]:o+a.grid[0]:o),"y"===a.axis&&(l=this.originalPageX),"x"===a.axis&&(h=this.originalPageY)),{top:h-this.offset.click.top-this.offset.relative.top-this.offset.parent.top+("fixed"===this.cssPosition?-this.offset.scroll.top:r?0:this.offset.scroll.top),left:l-this.offset.click.left-this.offset.relative.left-this.offset.parent.left+("fixed"===this.cssPosition?-this.offset.scroll.left:r?0:this.offset.scroll.left)}},_clear:function(){this.helper.removeClass("ui-draggable-dragging"),this.helper[0]===this.element[0]||this.cancelHelperRemoval||this.helper.remove(),this.helper=null,this.cancelHelperRemoval=!1,this.destroyOnClear&&this.destroy()},_normalizeRightBottom:function(){"y"!==this.options.axis&&"auto"!==this.helper.css("right")&&(this.helper.width(this.helper.width()),this.helper.css("right","auto")),"x"!==this.options.axis&&"auto"!==this.helper.css("bottom")&&(this.helper.height(this.helper.height()),this.helper.css("bottom","auto"))},_trigger:function(e,i,s){return s=s||this._uiHash(),t.ui.plugin.call(this,e,[i,s,this],!0),/^(drag|start|stop)/.test(e)&&(this.positionAbs=this._convertPositionTo("absolute"),s.offset=this.positionAbs),t.Widget.prototype._trigger.call(this,e,i,s)},plugins:{},_uiHash:function(){return{helper:this.helper,position:this.position,originalPosition:this.originalPosition,offset:this.positionAbs}}}),t.ui.plugin.add("draggable","connectToSortable",{start:function(e,i,s){var n=t.extend({},i,{item:s.element});s.sortables=[],t(s.options.connectToSortable).each(function(){var i=t(this).sortable("instance");i&&!i.options.disabled&&(s.sortables.push(i),i.refreshPositions(),i._trigger("activate",e,n))})},stop:function(e,i,s){var n=t.extend({},i,{item:s.element});s.cancelHelperRemoval=!1,t.each(s.sortables,function(){var t=this;t.isOver?(t.isOver=0,s.cancelHelperRemoval=!0,t.cancelHelperRemoval=!1,t._storedCSS={position:t.placeholder.css("position"),top:t.placeholder.css("top"),left:t.placeholder.css("left")},t._mouseStop(e),t.options.helper=t.options._helper):(t.cancelHelperRemoval=!0,t._trigger("deactivate",e,n))})},drag:function(e,i,s){t.each(s.sortables,function(){var n=!1,o=this;o.positionAbs=s.positionAbs,o.helperProportions=s.helperProportions,o.offset.click=s.offset.click,o._intersectsWith(o.containerCache)&&(n=!0,t.each(s.sortables,function(){return this.positionAbs=s.positionAbs,this.helperProportions=s.helperProportions,this.offset.click=s.offset.click,this!==o&&this._intersectsWith(this.containerCache)&&t.contains(o.element[0],this.element[0])&&(n=!1),n})),n?(o.isOver||(o.isOver=1,s._parent=i.helper.parent(),o.currentItem=i.helper.appendTo(o.element).data("ui-sortable-item",!0),o.options._helper=o.options.helper,o.options.helper=function(){return i.helper[0]},e.target=o.currentItem[0],o._mouseCapture(e,!0),o._mouseStart(e,!0,!0),o.offset.click.top=s.offset.click.top,o.offset.click.left=s.offset.click.left,o.offset.parent.left-=s.offset.parent.left-o.offset.parent.left,o.offset.parent.top-=s.offset.parent.top-o.offset.parent.top,s._trigger("toSortable",e),s.dropped=o.element,t.each(s.sortables,function(){this.refreshPositions()}),s.currentItem=s.element,o.fromOutside=s),o.currentItem&&(o._mouseDrag(e),i.position=o.position)):o.isOver&&(o.isOver=0,o.cancelHelperRemoval=!0,o.options._revert=o.options.revert,o.options.revert=!1,o._trigger("out",e,o._uiHash(o)),o._mouseStop(e,!0),o.options.revert=o.options._revert,o.options.helper=o.options._helper,o.placeholder&&o.placeholder.remove(),i.helper.appendTo(s._parent),s._refreshOffsets(e),i.position=s._generatePosition(e,!0),s._trigger("fromSortable",e),s.dropped=!1,t.each(s.sortables,function(){this.refreshPositions()}))})}}),t.ui.plugin.add("draggable","cursor",{start:function(e,i,s){var n=t("body"),o=s.options;n.css("cursor")&&(o._cursor=n.css("cursor")),n.css("cursor",o.cursor)},stop:function(e,i,s){var n=s.options;n._cursor&&t("body").css("cursor",n._cursor)}}),t.ui.plugin.add("draggable","opacity",{start:function(e,i,s){var n=t(i.helper),o=s.options;n.css("opacity")&&(o._opacity=n.css("opacity")),n.css("opacity",o.opacity)},stop:function(e,i,s){var n=s.options;n._opacity&&t(i.helper).css("opacity",n._opacity)}}),t.ui.plugin.add("draggable","scroll",{start:function(t,e,i){i.scrollParentNotHidden||(i.scrollParentNotHidden=i.helper.scrollParent(!1)),i.scrollParentNotHidden[0]!==i.document[0]&&"HTML"!==i.scrollParentNotHidden[0].tagName&&(i.overflowOffset=i.scrollParentNotHidden.offset())},drag:function(e,i,s){var n=s.options,o=!1,a=s.scrollParentNotHidden[0],r=s.document[0];a!==r&&"HTML"!==a.tagName?(n.axis&&"x"===n.axis||(s.overflowOffset.top+a.offsetHeight-e.pageY=0;d--)l=s.snapElements[d].left-s.margins.left,h=l+s.snapElements[d].width,c=s.snapElements[d].top-s.margins.top,u=c+s.snapElements[d].height,l-g>_||m>h+g||c-g>b||v>u+g||!t.contains(s.snapElements[d].item.ownerDocument,s.snapElements[d].item)?(s.snapElements[d].snapping&&s.options.snap.release&&s.options.snap.release.call(s.element,e,t.extend(s._uiHash(),{snapItem:s.snapElements[d].item})),s.snapElements[d].snapping=!1):("inner"!==f.snapMode&&(n=g>=Math.abs(c-b),o=g>=Math.abs(u-v),a=g>=Math.abs(l-_),r=g>=Math.abs(h-m),n&&(i.position.top=s._convertPositionTo("relative",{top:c-s.helperProportions.height,left:0}).top),o&&(i.position.top=s._convertPositionTo("relative",{top:u,left:0}).top),a&&(i.position.left=s._convertPositionTo("relative",{top:0,left:l-s.helperProportions.width}).left),r&&(i.position.left=s._convertPositionTo("relative",{top:0,left:h}).left)),p=n||o||a||r,"outer"!==f.snapMode&&(n=g>=Math.abs(c-v),o=g>=Math.abs(u-b),a=g>=Math.abs(l-m),r=g>=Math.abs(h-_),n&&(i.position.top=s._convertPositionTo("relative",{top:c,left:0}).top),o&&(i.position.top=s._convertPositionTo("relative",{top:u-s.helperProportions.height,left:0}).top),a&&(i.position.left=s._convertPositionTo("relative",{top:0,left:l}).left),r&&(i.position.left=s._convertPositionTo("relative",{top:0,left:h-s.helperProportions.width}).left)),!s.snapElements[d].snapping&&(n||o||a||r||p)&&s.options.snap.snap&&s.options.snap.snap.call(s.element,e,t.extend(s._uiHash(),{snapItem:s.snapElements[d].item})),s.snapElements[d].snapping=n||o||a||r||p)}}),t.ui.plugin.add("draggable","stack",{start:function(e,i,s){var n,o=s.options,a=t.makeArray(t(o.stack)).sort(function(e,i){return(parseInt(t(e).css("zIndex"),10)||0)-(parseInt(t(i).css("zIndex"),10)||0)});a.length&&(n=parseInt(t(a[0]).css("zIndex"),10)||0,t(a).each(function(e){t(this).css("zIndex",n+e)}),this.css("zIndex",n+a.length))}}),t.ui.plugin.add("draggable","zIndex",{start:function(e,i,s){var n=t(i.helper),o=s.options;n.css("zIndex")&&(o._zIndex=n.css("zIndex")),n.css("zIndex",o.zIndex)},stop:function(e,i,s){var n=s.options;n._zIndex&&t(i.helper).css("zIndex",n._zIndex)}}),t.ui.draggable,t.widget("ui.resizable",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"resize",options:{alsoResize:!1,animate:!1,animateDuration:"slow",animateEasing:"swing",aspectRatio:!1,autoHide:!1,containment:!1,ghost:!1,grid:!1,handles:"e,s,se",helper:!1,maxHeight:null,maxWidth:null,minHeight:10,minWidth:10,zIndex:90,resize:null,start:null,stop:null},_num:function(t){return parseInt(t,10)||0 -},_isNumber:function(t){return!isNaN(parseInt(t,10))},_hasScroll:function(e,i){if("hidden"===t(e).css("overflow"))return!1;var s=i&&"left"===i?"scrollLeft":"scrollTop",n=!1;return e[s]>0?!0:(e[s]=1,n=e[s]>0,e[s]=0,n)},_create:function(){var e,i,s,n,o,a=this,r=this.options;if(this.element.addClass("ui-resizable"),t.extend(this,{_aspectRatio:!!r.aspectRatio,aspectRatio:r.aspectRatio,originalElement:this.element,_proportionallyResizeElements:[],_helper:r.helper||r.ghost||r.animate?r.helper||"ui-resizable-helper":null}),this.element[0].nodeName.match(/^(canvas|textarea|input|select|button|img)$/i)&&(this.element.wrap(t("
    ").css({position:this.element.css("position"),width:this.element.outerWidth(),height:this.element.outerHeight(),top:this.element.css("top"),left:this.element.css("left")})),this.element=this.element.parent().data("ui-resizable",this.element.resizable("instance")),this.elementIsWrapper=!0,this.element.css({marginLeft:this.originalElement.css("marginLeft"),marginTop:this.originalElement.css("marginTop"),marginRight:this.originalElement.css("marginRight"),marginBottom:this.originalElement.css("marginBottom")}),this.originalElement.css({marginLeft:0,marginTop:0,marginRight:0,marginBottom:0}),this.originalResizeStyle=this.originalElement.css("resize"),this.originalElement.css("resize","none"),this._proportionallyResizeElements.push(this.originalElement.css({position:"static",zoom:1,display:"block"})),this.originalElement.css({margin:this.originalElement.css("margin")}),this._proportionallyResize()),this.handles=r.handles||(t(".ui-resizable-handle",this.element).length?{n:".ui-resizable-n",e:".ui-resizable-e",s:".ui-resizable-s",w:".ui-resizable-w",se:".ui-resizable-se",sw:".ui-resizable-sw",ne:".ui-resizable-ne",nw:".ui-resizable-nw"}:"e,s,se"),this._handles=t(),this.handles.constructor===String)for("all"===this.handles&&(this.handles="n,e,s,w,se,sw,ne,nw"),e=this.handles.split(","),this.handles={},i=0;e.length>i;i++)s=t.trim(e[i]),o="ui-resizable-"+s,n=t("
    "),n.css({zIndex:r.zIndex}),"se"===s&&n.addClass("ui-icon ui-icon-gripsmall-diagonal-se"),this.handles[s]=".ui-resizable-"+s,this.element.append(n);this._renderAxis=function(e){var i,s,n,o;e=e||this.element;for(i in this.handles)this.handles[i].constructor===String?this.handles[i]=this.element.children(this.handles[i]).first().show():(this.handles[i].jquery||this.handles[i].nodeType)&&(this.handles[i]=t(this.handles[i]),this._on(this.handles[i],{mousedown:a._mouseDown})),this.elementIsWrapper&&this.originalElement[0].nodeName.match(/^(textarea|input|select|button)$/i)&&(s=t(this.handles[i],this.element),o=/sw|ne|nw|se|n|s/.test(i)?s.outerHeight():s.outerWidth(),n=["padding",/ne|nw|n/.test(i)?"Top":/se|sw|s/.test(i)?"Bottom":/^e$/.test(i)?"Right":"Left"].join(""),e.css(n,o),this._proportionallyResize()),this._handles=this._handles.add(this.handles[i])},this._renderAxis(this.element),this._handles=this._handles.add(this.element.find(".ui-resizable-handle")),this._handles.disableSelection(),this._handles.mouseover(function(){a.resizing||(this.className&&(n=this.className.match(/ui-resizable-(se|sw|ne|nw|n|e|s|w)/i)),a.axis=n&&n[1]?n[1]:"se")}),r.autoHide&&(this._handles.hide(),t(this.element).addClass("ui-resizable-autohide").mouseenter(function(){r.disabled||(t(this).removeClass("ui-resizable-autohide"),a._handles.show())}).mouseleave(function(){r.disabled||a.resizing||(t(this).addClass("ui-resizable-autohide"),a._handles.hide())})),this._mouseInit()},_destroy:function(){this._mouseDestroy();var e,i=function(e){t(e).removeClass("ui-resizable ui-resizable-disabled ui-resizable-resizing").removeData("resizable").removeData("ui-resizable").unbind(".resizable").find(".ui-resizable-handle").remove()};return this.elementIsWrapper&&(i(this.element),e=this.element,this.originalElement.css({position:e.css("position"),width:e.outerWidth(),height:e.outerHeight(),top:e.css("top"),left:e.css("left")}).insertAfter(e),e.remove()),this.originalElement.css("resize",this.originalResizeStyle),i(this.originalElement),this},_mouseCapture:function(e){var i,s,n=!1;for(i in this.handles)s=t(this.handles[i])[0],(s===e.target||t.contains(s,e.target))&&(n=!0);return!this.options.disabled&&n},_mouseStart:function(e){var i,s,n,o=this.options,a=this.element;return this.resizing=!0,this._renderProxy(),i=this._num(this.helper.css("left")),s=this._num(this.helper.css("top")),o.containment&&(i+=t(o.containment).scrollLeft()||0,s+=t(o.containment).scrollTop()||0),this.offset=this.helper.offset(),this.position={left:i,top:s},this.size=this._helper?{width:this.helper.width(),height:this.helper.height()}:{width:a.width(),height:a.height()},this.originalSize=this._helper?{width:a.outerWidth(),height:a.outerHeight()}:{width:a.width(),height:a.height()},this.sizeDiff={width:a.outerWidth()-a.width(),height:a.outerHeight()-a.height()},this.originalPosition={left:i,top:s},this.originalMousePosition={left:e.pageX,top:e.pageY},this.aspectRatio="number"==typeof o.aspectRatio?o.aspectRatio:this.originalSize.width/this.originalSize.height||1,n=t(".ui-resizable-"+this.axis).css("cursor"),t("body").css("cursor","auto"===n?this.axis+"-resize":n),a.addClass("ui-resizable-resizing"),this._propagate("start",e),!0},_mouseDrag:function(e){var i,s,n=this.originalMousePosition,o=this.axis,a=e.pageX-n.left||0,r=e.pageY-n.top||0,l=this._change[o];return this._updatePrevProperties(),l?(i=l.apply(this,[e,a,r]),this._updateVirtualBoundaries(e.shiftKey),(this._aspectRatio||e.shiftKey)&&(i=this._updateRatio(i,e)),i=this._respectSize(i,e),this._updateCache(i),this._propagate("resize",e),s=this._applyChanges(),!this._helper&&this._proportionallyResizeElements.length&&this._proportionallyResize(),t.isEmptyObject(s)||(this._updatePrevProperties(),this._trigger("resize",e,this.ui()),this._applyChanges()),!1):!1},_mouseStop:function(e){this.resizing=!1;var i,s,n,o,a,r,l,h=this.options,c=this;return this._helper&&(i=this._proportionallyResizeElements,s=i.length&&/textarea/i.test(i[0].nodeName),n=s&&this._hasScroll(i[0],"left")?0:c.sizeDiff.height,o=s?0:c.sizeDiff.width,a={width:c.helper.width()-o,height:c.helper.height()-n},r=parseInt(c.element.css("left"),10)+(c.position.left-c.originalPosition.left)||null,l=parseInt(c.element.css("top"),10)+(c.position.top-c.originalPosition.top)||null,h.animate||this.element.css(t.extend(a,{top:l,left:r})),c.helper.height(c.size.height),c.helper.width(c.size.width),this._helper&&!h.animate&&this._proportionallyResize()),t("body").css("cursor","auto"),this.element.removeClass("ui-resizable-resizing"),this._propagate("stop",e),this._helper&&this.helper.remove(),!1},_updatePrevProperties:function(){this.prevPosition={top:this.position.top,left:this.position.left},this.prevSize={width:this.size.width,height:this.size.height}},_applyChanges:function(){var t={};return this.position.top!==this.prevPosition.top&&(t.top=this.position.top+"px"),this.position.left!==this.prevPosition.left&&(t.left=this.position.left+"px"),this.size.width!==this.prevSize.width&&(t.width=this.size.width+"px"),this.size.height!==this.prevSize.height&&(t.height=this.size.height+"px"),this.helper.css(t),t},_updateVirtualBoundaries:function(t){var e,i,s,n,o,a=this.options;o={minWidth:this._isNumber(a.minWidth)?a.minWidth:0,maxWidth:this._isNumber(a.maxWidth)?a.maxWidth:1/0,minHeight:this._isNumber(a.minHeight)?a.minHeight:0,maxHeight:this._isNumber(a.maxHeight)?a.maxHeight:1/0},(this._aspectRatio||t)&&(e=o.minHeight*this.aspectRatio,s=o.minWidth/this.aspectRatio,i=o.maxHeight*this.aspectRatio,n=o.maxWidth/this.aspectRatio,e>o.minWidth&&(o.minWidth=e),s>o.minHeight&&(o.minHeight=s),o.maxWidth>i&&(o.maxWidth=i),o.maxHeight>n&&(o.maxHeight=n)),this._vBoundaries=o},_updateCache:function(t){this.offset=this.helper.offset(),this._isNumber(t.left)&&(this.position.left=t.left),this._isNumber(t.top)&&(this.position.top=t.top),this._isNumber(t.height)&&(this.size.height=t.height),this._isNumber(t.width)&&(this.size.width=t.width)},_updateRatio:function(t){var e=this.position,i=this.size,s=this.axis;return this._isNumber(t.height)?t.width=t.height*this.aspectRatio:this._isNumber(t.width)&&(t.height=t.width/this.aspectRatio),"sw"===s&&(t.left=e.left+(i.width-t.width),t.top=null),"nw"===s&&(t.top=e.top+(i.height-t.height),t.left=e.left+(i.width-t.width)),t},_respectSize:function(t){var e=this._vBoundaries,i=this.axis,s=this._isNumber(t.width)&&e.maxWidth&&e.maxWidtht.width,a=this._isNumber(t.height)&&e.minHeight&&e.minHeight>t.height,r=this.originalPosition.left+this.originalSize.width,l=this.position.top+this.size.height,h=/sw|nw|w/.test(i),c=/nw|ne|n/.test(i);return o&&(t.width=e.minWidth),a&&(t.height=e.minHeight),s&&(t.width=e.maxWidth),n&&(t.height=e.maxHeight),o&&h&&(t.left=r-e.minWidth),s&&h&&(t.left=r-e.maxWidth),a&&c&&(t.top=l-e.minHeight),n&&c&&(t.top=l-e.maxHeight),t.width||t.height||t.left||!t.top?t.width||t.height||t.top||!t.left||(t.left=null):t.top=null,t},_getPaddingPlusBorderDimensions:function(t){for(var e=0,i=[],s=[t.css("borderTopWidth"),t.css("borderRightWidth"),t.css("borderBottomWidth"),t.css("borderLeftWidth")],n=[t.css("paddingTop"),t.css("paddingRight"),t.css("paddingBottom"),t.css("paddingLeft")];4>e;e++)i[e]=parseInt(s[e],10)||0,i[e]+=parseInt(n[e],10)||0;return{height:i[0]+i[2],width:i[1]+i[3]}},_proportionallyResize:function(){if(this._proportionallyResizeElements.length)for(var t,e=0,i=this.helper||this.element;this._proportionallyResizeElements.length>e;e++)t=this._proportionallyResizeElements[e],this.outerDimensions||(this.outerDimensions=this._getPaddingPlusBorderDimensions(t)),t.css({height:i.height()-this.outerDimensions.height||0,width:i.width()-this.outerDimensions.width||0})},_renderProxy:function(){var e=this.element,i=this.options;this.elementOffset=e.offset(),this._helper?(this.helper=this.helper||t("
    "),this.helper.addClass(this._helper).css({width:this.element.outerWidth()-1,height:this.element.outerHeight()-1,position:"absolute",left:this.elementOffset.left+"px",top:this.elementOffset.top+"px",zIndex:++i.zIndex}),this.helper.appendTo("body").disableSelection()):this.helper=this.element},_change:{e:function(t,e){return{width:this.originalSize.width+e}},w:function(t,e){var i=this.originalSize,s=this.originalPosition;return{left:s.left+e,width:i.width-e}},n:function(t,e,i){var s=this.originalSize,n=this.originalPosition;return{top:n.top+i,height:s.height-i}},s:function(t,e,i){return{height:this.originalSize.height+i}},se:function(e,i,s){return t.extend(this._change.s.apply(this,arguments),this._change.e.apply(this,[e,i,s]))},sw:function(e,i,s){return t.extend(this._change.s.apply(this,arguments),this._change.w.apply(this,[e,i,s]))},ne:function(e,i,s){return t.extend(this._change.n.apply(this,arguments),this._change.e.apply(this,[e,i,s]))},nw:function(e,i,s){return t.extend(this._change.n.apply(this,arguments),this._change.w.apply(this,[e,i,s]))}},_propagate:function(e,i){t.ui.plugin.call(this,e,[i,this.ui()]),"resize"!==e&&this._trigger(e,i,this.ui())},plugins:{},ui:function(){return{originalElement:this.originalElement,element:this.element,helper:this.helper,position:this.position,size:this.size,originalSize:this.originalSize,originalPosition:this.originalPosition}}}),t.ui.plugin.add("resizable","animate",{stop:function(e){var i=t(this).resizable("instance"),s=i.options,n=i._proportionallyResizeElements,o=n.length&&/textarea/i.test(n[0].nodeName),a=o&&i._hasScroll(n[0],"left")?0:i.sizeDiff.height,r=o?0:i.sizeDiff.width,l={width:i.size.width-r,height:i.size.height-a},h=parseInt(i.element.css("left"),10)+(i.position.left-i.originalPosition.left)||null,c=parseInt(i.element.css("top"),10)+(i.position.top-i.originalPosition.top)||null;i.element.animate(t.extend(l,c&&h?{top:c,left:h}:{}),{duration:s.animateDuration,easing:s.animateEasing,step:function(){var s={width:parseInt(i.element.css("width"),10),height:parseInt(i.element.css("height"),10),top:parseInt(i.element.css("top"),10),left:parseInt(i.element.css("left"),10)};n&&n.length&&t(n[0]).css({width:s.width,height:s.height}),i._updateCache(s),i._propagate("resize",e)}})}}),t.ui.plugin.add("resizable","containment",{start:function(){var e,i,s,n,o,a,r,l=t(this).resizable("instance"),h=l.options,c=l.element,u=h.containment,d=u instanceof t?u.get(0):/parent/.test(u)?c.parent().get(0):u;d&&(l.containerElement=t(d),/document/.test(u)||u===document?(l.containerOffset={left:0,top:0},l.containerPosition={left:0,top:0},l.parentData={element:t(document),left:0,top:0,width:t(document).width(),height:t(document).height()||document.body.parentNode.scrollHeight}):(e=t(d),i=[],t(["Top","Right","Left","Bottom"]).each(function(t,s){i[t]=l._num(e.css("padding"+s))}),l.containerOffset=e.offset(),l.containerPosition=e.position(),l.containerSize={height:e.innerHeight()-i[3],width:e.innerWidth()-i[1]},s=l.containerOffset,n=l.containerSize.height,o=l.containerSize.width,a=l._hasScroll(d,"left")?d.scrollWidth:o,r=l._hasScroll(d)?d.scrollHeight:n,l.parentData={element:d,left:s.left,top:s.top,width:a,height:r}))},resize:function(e){var i,s,n,o,a=t(this).resizable("instance"),r=a.options,l=a.containerOffset,h=a.position,c=a._aspectRatio||e.shiftKey,u={top:0,left:0},d=a.containerElement,p=!0;d[0]!==document&&/static/.test(d.css("position"))&&(u=l),h.left<(a._helper?l.left:0)&&(a.size.width=a.size.width+(a._helper?a.position.left-l.left:a.position.left-u.left),c&&(a.size.height=a.size.width/a.aspectRatio,p=!1),a.position.left=r.helper?l.left:0),h.top<(a._helper?l.top:0)&&(a.size.height=a.size.height+(a._helper?a.position.top-l.top:a.position.top),c&&(a.size.width=a.size.height*a.aspectRatio,p=!1),a.position.top=a._helper?l.top:0),n=a.containerElement.get(0)===a.element.parent().get(0),o=/relative|absolute/.test(a.containerElement.css("position")),n&&o?(a.offset.left=a.parentData.left+a.position.left,a.offset.top=a.parentData.top+a.position.top):(a.offset.left=a.element.offset().left,a.offset.top=a.element.offset().top),i=Math.abs(a.sizeDiff.width+(a._helper?a.offset.left-u.left:a.offset.left-l.left)),s=Math.abs(a.sizeDiff.height+(a._helper?a.offset.top-u.top:a.offset.top-l.top)),i+a.size.width>=a.parentData.width&&(a.size.width=a.parentData.width-i,c&&(a.size.height=a.size.width/a.aspectRatio,p=!1)),s+a.size.height>=a.parentData.height&&(a.size.height=a.parentData.height-s,c&&(a.size.width=a.size.height*a.aspectRatio,p=!1)),p||(a.position.left=a.prevPosition.left,a.position.top=a.prevPosition.top,a.size.width=a.prevSize.width,a.size.height=a.prevSize.height)},stop:function(){var e=t(this).resizable("instance"),i=e.options,s=e.containerOffset,n=e.containerPosition,o=e.containerElement,a=t(e.helper),r=a.offset(),l=a.outerWidth()-e.sizeDiff.width,h=a.outerHeight()-e.sizeDiff.height;e._helper&&!i.animate&&/relative/.test(o.css("position"))&&t(this).css({left:r.left-n.left-s.left,width:l,height:h}),e._helper&&!i.animate&&/static/.test(o.css("position"))&&t(this).css({left:r.left-n.left-s.left,width:l,height:h})}}),t.ui.plugin.add("resizable","alsoResize",{start:function(){var e=t(this).resizable("instance"),i=e.options;t(i.alsoResize).each(function(){var e=t(this);e.data("ui-resizable-alsoresize",{width:parseInt(e.width(),10),height:parseInt(e.height(),10),left:parseInt(e.css("left"),10),top:parseInt(e.css("top"),10)})})},resize:function(e,i){var s=t(this).resizable("instance"),n=s.options,o=s.originalSize,a=s.originalPosition,r={height:s.size.height-o.height||0,width:s.size.width-o.width||0,top:s.position.top-a.top||0,left:s.position.left-a.left||0};t(n.alsoResize).each(function(){var e=t(this),s=t(this).data("ui-resizable-alsoresize"),n={},o=e.parents(i.originalElement[0]).length?["width","height"]:["width","height","top","left"];t.each(o,function(t,e){var i=(s[e]||0)+(r[e]||0);i&&i>=0&&(n[e]=i||null)}),e.css(n)})},stop:function(){t(this).removeData("resizable-alsoresize")}}),t.ui.plugin.add("resizable","ghost",{start:function(){var e=t(this).resizable("instance"),i=e.options,s=e.size;e.ghost=e.originalElement.clone(),e.ghost.css({opacity:.25,display:"block",position:"relative",height:s.height,width:s.width,margin:0,left:0,top:0}).addClass("ui-resizable-ghost").addClass("string"==typeof i.ghost?i.ghost:""),e.ghost.appendTo(e.helper)},resize:function(){var e=t(this).resizable("instance");e.ghost&&e.ghost.css({position:"relative",height:e.size.height,width:e.size.width})},stop:function(){var e=t(this).resizable("instance");e.ghost&&e.helper&&e.helper.get(0).removeChild(e.ghost.get(0))}}),t.ui.plugin.add("resizable","grid",{resize:function(){var e,i=t(this).resizable("instance"),s=i.options,n=i.size,o=i.originalSize,a=i.originalPosition,r=i.axis,l="number"==typeof s.grid?[s.grid,s.grid]:s.grid,h=l[0]||1,c=l[1]||1,u=Math.round((n.width-o.width)/h)*h,d=Math.round((n.height-o.height)/c)*c,p=o.width+u,f=o.height+d,g=s.maxWidth&&p>s.maxWidth,m=s.maxHeight&&f>s.maxHeight,_=s.minWidth&&s.minWidth>p,v=s.minHeight&&s.minHeight>f;s.grid=l,_&&(p+=h),v&&(f+=c),g&&(p-=h),m&&(f-=c),/^(se|s|e)$/.test(r)?(i.size.width=p,i.size.height=f):/^(ne)$/.test(r)?(i.size.width=p,i.size.height=f,i.position.top=a.top-d):/^(sw)$/.test(r)?(i.size.width=p,i.size.height=f,i.position.left=a.left-u):((0>=f-c||0>=p-h)&&(e=i._getPaddingPlusBorderDimensions(this)),f-c>0?(i.size.height=f,i.position.top=a.top-d):(f=c-e.height,i.size.height=f,i.position.top=a.top+o.height-f),p-h>0?(i.size.width=p,i.position.left=a.left-u):(p=h-e.width,i.size.width=p,i.position.left=a.left+o.width-p))}}),t.ui.resizable,t.widget("ui.sortable",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"sort",ready:!1,options:{appendTo:"parent",axis:!1,connectWith:!1,containment:!1,cursor:"auto",cursorAt:!1,dropOnEmpty:!0,forcePlaceholderSize:!1,forceHelperSize:!1,grid:!1,handle:!1,helper:"original",items:"> *",opacity:!1,placeholder:!1,revert:!1,scroll:!0,scrollSensitivity:20,scrollSpeed:20,scope:"default",tolerance:"intersect",zIndex:1e3,activate:null,beforeStop:null,change:null,deactivate:null,out:null,over:null,receive:null,remove:null,sort:null,start:null,stop:null,update:null},_isOverAxis:function(t,e,i){return t>=e&&e+i>t},_isFloating:function(t){return/left|right/.test(t.css("float"))||/inline|table-cell/.test(t.css("display"))},_create:function(){this.containerCache={},this.element.addClass("ui-sortable"),this.refresh(),this.offset=this.element.offset(),this._mouseInit(),this._setHandleClassName(),this.ready=!0},_setOption:function(t,e){this._super(t,e),"handle"===t&&this._setHandleClassName()},_setHandleClassName:function(){this.element.find(".ui-sortable-handle").removeClass("ui-sortable-handle"),t.each(this.items,function(){(this.instance.options.handle?this.item.find(this.instance.options.handle):this.item).addClass("ui-sortable-handle")})},_destroy:function(){this.element.removeClass("ui-sortable ui-sortable-disabled").find(".ui-sortable-handle").removeClass("ui-sortable-handle"),this._mouseDestroy();for(var t=this.items.length-1;t>=0;t--)this.items[t].item.removeData(this.widgetName+"-item");return this},_mouseCapture:function(e,i){var s=null,n=!1,o=this;return this.reverting?!1:this.options.disabled||"static"===this.options.type?!1:(this._refreshItems(e),t(e.target).parents().each(function(){return t.data(this,o.widgetName+"-item")===o?(s=t(this),!1):void 0}),t.data(e.target,o.widgetName+"-item")===o&&(s=t(e.target)),s?!this.options.handle||i||(t(this.options.handle,s).find("*").addBack().each(function(){this===e.target&&(n=!0)}),n)?(this.currentItem=s,this._removeCurrentsFromItems(),!0):!1:!1)},_mouseStart:function(e,i,s){var n,o,a=this.options;if(this.currentContainer=this,this.refreshPositions(),this.helper=this._createHelper(e),this._cacheHelperProportions(),this._cacheMargins(),this.scrollParent=this.helper.scrollParent(),this.offset=this.currentItem.offset(),this.offset={top:this.offset.top-this.margins.top,left:this.offset.left-this.margins.left},t.extend(this.offset,{click:{left:e.pageX-this.offset.left,top:e.pageY-this.offset.top},parent:this._getParentOffset(),relative:this._getRelativeOffset()}),this.helper.css("position","absolute"),this.cssPosition=this.helper.css("position"),this.originalPosition=this._generatePosition(e),this.originalPageX=e.pageX,this.originalPageY=e.pageY,a.cursorAt&&this._adjustOffsetFromHelper(a.cursorAt),this.domPosition={prev:this.currentItem.prev()[0],parent:this.currentItem.parent()[0]},this.helper[0]!==this.currentItem[0]&&this.currentItem.hide(),this._createPlaceholder(),a.containment&&this._setContainment(),a.cursor&&"auto"!==a.cursor&&(o=this.document.find("body"),this.storedCursor=o.css("cursor"),o.css("cursor",a.cursor),this.storedStylesheet=t("").appendTo(o)),a.opacity&&(this.helper.css("opacity")&&(this._storedOpacity=this.helper.css("opacity")),this.helper.css("opacity",a.opacity)),a.zIndex&&(this.helper.css("zIndex")&&(this._storedZIndex=this.helper.css("zIndex")),this.helper.css("zIndex",a.zIndex)),this.scrollParent[0]!==this.document[0]&&"HTML"!==this.scrollParent[0].tagName&&(this.overflowOffset=this.scrollParent.offset()),this._trigger("start",e,this._uiHash()),this._preserveHelperProportions||this._cacheHelperProportions(),!s)for(n=this.containers.length-1;n>=0;n--)this.containers[n]._trigger("activate",e,this._uiHash(this));return t.ui.ddmanager&&(t.ui.ddmanager.current=this),t.ui.ddmanager&&!a.dropBehaviour&&t.ui.ddmanager.prepareOffsets(this,e),this.dragging=!0,this.helper.addClass("ui-sortable-helper"),this._mouseDrag(e),!0},_mouseDrag:function(e){var i,s,n,o,a=this.options,r=!1;for(this.position=this._generatePosition(e),this.positionAbs=this._convertPositionTo("absolute"),this.lastPositionAbs||(this.lastPositionAbs=this.positionAbs),this.options.scroll&&(this.scrollParent[0]!==this.document[0]&&"HTML"!==this.scrollParent[0].tagName?(this.overflowOffset.top+this.scrollParent[0].offsetHeight-e.pageY=0;i--)if(s=this.items[i],n=s.item[0],o=this._intersectsWithPointer(s),o&&s.instance===this.currentContainer&&n!==this.currentItem[0]&&this.placeholder[1===o?"next":"prev"]()[0]!==n&&!t.contains(this.placeholder[0],n)&&("semi-dynamic"===this.options.type?!t.contains(this.element[0],n):!0)){if(this.direction=1===o?"down":"up","pointer"!==this.options.tolerance&&!this._intersectsWithSides(s))break;this._rearrange(e,s),this._trigger("change",e,this._uiHash());break}return this._contactContainers(e),t.ui.ddmanager&&t.ui.ddmanager.drag(this,e),this._trigger("sort",e,this._uiHash()),this.lastPositionAbs=this.positionAbs,!1},_mouseStop:function(e,i){if(e){if(t.ui.ddmanager&&!this.options.dropBehaviour&&t.ui.ddmanager.drop(this,e),this.options.revert){var s=this,n=this.placeholder.offset(),o=this.options.axis,a={};o&&"x"!==o||(a.left=n.left-this.offset.parent.left-this.margins.left+(this.offsetParent[0]===this.document[0].body?0:this.offsetParent[0].scrollLeft)),o&&"y"!==o||(a.top=n.top-this.offset.parent.top-this.margins.top+(this.offsetParent[0]===this.document[0].body?0:this.offsetParent[0].scrollTop)),this.reverting=!0,t(this.helper).animate(a,parseInt(this.options.revert,10)||500,function(){s._clear(e)})}else this._clear(e,i);return!1}},cancel:function(){if(this.dragging){this._mouseUp({target:null}),"original"===this.options.helper?this.currentItem.css(this._storedCSS).removeClass("ui-sortable-helper"):this.currentItem.show();for(var e=this.containers.length-1;e>=0;e--)this.containers[e]._trigger("deactivate",null,this._uiHash(this)),this.containers[e].containerCache.over&&(this.containers[e]._trigger("out",null,this._uiHash(this)),this.containers[e].containerCache.over=0)}return this.placeholder&&(this.placeholder[0].parentNode&&this.placeholder[0].parentNode.removeChild(this.placeholder[0]),"original"!==this.options.helper&&this.helper&&this.helper[0].parentNode&&this.helper.remove(),t.extend(this,{helper:null,dragging:!1,reverting:!1,_noFinalSort:null}),this.domPosition.prev?t(this.domPosition.prev).after(this.currentItem):t(this.domPosition.parent).prepend(this.currentItem)),this},serialize:function(e){var i=this._getItemsAsjQuery(e&&e.connected),s=[];return e=e||{},t(i).each(function(){var i=(t(e.item||this).attr(e.attribute||"id")||"").match(e.expression||/(.+)[\-=_](.+)/);i&&s.push((e.key||i[1]+"[]")+"="+(e.key&&e.expression?i[1]:i[2]))}),!s.length&&e.key&&s.push(e.key+"="),s.join("&")},toArray:function(e){var i=this._getItemsAsjQuery(e&&e.connected),s=[];return e=e||{},i.each(function(){s.push(t(e.item||this).attr(e.attribute||"id")||"")}),s},_intersectsWith:function(t){var e=this.positionAbs.left,i=e+this.helperProportions.width,s=this.positionAbs.top,n=s+this.helperProportions.height,o=t.left,a=o+t.width,r=t.top,l=r+t.height,h=this.offset.click.top,c=this.offset.click.left,u="x"===this.options.axis||s+h>r&&l>s+h,d="y"===this.options.axis||e+c>o&&a>e+c,p=u&&d;return"pointer"===this.options.tolerance||this.options.forcePointerForContainers||"pointer"!==this.options.tolerance&&this.helperProportions[this.floating?"width":"height"]>t[this.floating?"width":"height"]?p:e+this.helperProportions.width/2>o&&a>i-this.helperProportions.width/2&&s+this.helperProportions.height/2>r&&l>n-this.helperProportions.height/2},_intersectsWithPointer:function(t){var e="x"===this.options.axis||this._isOverAxis(this.positionAbs.top+this.offset.click.top,t.top,t.height),i="y"===this.options.axis||this._isOverAxis(this.positionAbs.left+this.offset.click.left,t.left,t.width),s=e&&i,n=this._getDragVerticalDirection(),o=this._getDragHorizontalDirection();return s?this.floating?o&&"right"===o||"down"===n?2:1:n&&("down"===n?2:1):!1},_intersectsWithSides:function(t){var e=this._isOverAxis(this.positionAbs.top+this.offset.click.top,t.top+t.height/2,t.height),i=this._isOverAxis(this.positionAbs.left+this.offset.click.left,t.left+t.width/2,t.width),s=this._getDragVerticalDirection(),n=this._getDragHorizontalDirection();return this.floating&&n?"right"===n&&i||"left"===n&&!i:s&&("down"===s&&e||"up"===s&&!e)},_getDragVerticalDirection:function(){var t=this.positionAbs.top-this.lastPositionAbs.top;return 0!==t&&(t>0?"down":"up")},_getDragHorizontalDirection:function(){var t=this.positionAbs.left-this.lastPositionAbs.left;return 0!==t&&(t>0?"right":"left")},refresh:function(t){return this._refreshItems(t),this._setHandleClassName(),this.refreshPositions(),this},_connectWith:function(){var t=this.options;return t.connectWith.constructor===String?[t.connectWith]:t.connectWith},_getItemsAsjQuery:function(e){function i(){r.push(this)}var s,n,o,a,r=[],l=[],h=this._connectWith();if(h&&e)for(s=h.length-1;s>=0;s--)for(o=t(h[s],this.document[0]),n=o.length-1;n>=0;n--)a=t.data(o[n],this.widgetFullName),a&&a!==this&&!a.options.disabled&&l.push([t.isFunction(a.options.items)?a.options.items.call(a.element):t(a.options.items,a.element).not(".ui-sortable-helper").not(".ui-sortable-placeholder"),a]);for(l.push([t.isFunction(this.options.items)?this.options.items.call(this.element,null,{options:this.options,item:this.currentItem}):t(this.options.items,this.element).not(".ui-sortable-helper").not(".ui-sortable-placeholder"),this]),s=l.length-1;s>=0;s--)l[s][0].each(i);return t(r)},_removeCurrentsFromItems:function(){var e=this.currentItem.find(":data("+this.widgetName+"-item)");this.items=t.grep(this.items,function(t){for(var i=0;e.length>i;i++)if(e[i]===t.item[0])return!1;return!0})},_refreshItems:function(e){this.items=[],this.containers=[this];var i,s,n,o,a,r,l,h,c=this.items,u=[[t.isFunction(this.options.items)?this.options.items.call(this.element[0],e,{item:this.currentItem}):t(this.options.items,this.element),this]],d=this._connectWith();if(d&&this.ready)for(i=d.length-1;i>=0;i--)for(n=t(d[i],this.document[0]),s=n.length-1;s>=0;s--)o=t.data(n[s],this.widgetFullName),o&&o!==this&&!o.options.disabled&&(u.push([t.isFunction(o.options.items)?o.options.items.call(o.element[0],e,{item:this.currentItem}):t(o.options.items,o.element),o]),this.containers.push(o));for(i=u.length-1;i>=0;i--)for(a=u[i][1],r=u[i][0],s=0,h=r.length;h>s;s++)l=t(r[s]),l.data(this.widgetName+"-item",a),c.push({item:l,instance:a,width:0,height:0,left:0,top:0})},refreshPositions:function(e){this.floating=this.items.length?"x"===this.options.axis||this._isFloating(this.items[0].item):!1,this.offsetParent&&this.helper&&(this.offset.parent=this._getParentOffset());var i,s,n,o;for(i=this.items.length-1;i>=0;i--)s=this.items[i],s.instance!==this.currentContainer&&this.currentContainer&&s.item[0]!==this.currentItem[0]||(n=this.options.toleranceElement?t(this.options.toleranceElement,s.item):s.item,e||(s.width=n.outerWidth(),s.height=n.outerHeight()),o=n.offset(),s.left=o.left,s.top=o.top);if(this.options.custom&&this.options.custom.refreshContainers)this.options.custom.refreshContainers.call(this);else for(i=this.containers.length-1;i>=0;i--)o=this.containers[i].element.offset(),this.containers[i].containerCache.left=o.left,this.containers[i].containerCache.top=o.top,this.containers[i].containerCache.width=this.containers[i].element.outerWidth(),this.containers[i].containerCache.height=this.containers[i].element.outerHeight();return this},_createPlaceholder:function(e){e=e||this;var i,s=e.options;s.placeholder&&s.placeholder.constructor!==String||(i=s.placeholder,s.placeholder={element:function(){var s=e.currentItem[0].nodeName.toLowerCase(),n=t("<"+s+">",e.document[0]).addClass(i||e.currentItem[0].className+" ui-sortable-placeholder").removeClass("ui-sortable-helper");return"tbody"===s?e._createTrPlaceholder(e.currentItem.find("tr").eq(0),t("",e.document[0]).appendTo(n)):"tr"===s?e._createTrPlaceholder(e.currentItem,n):"img"===s&&n.attr("src",e.currentItem.attr("src")),i||n.css("visibility","hidden"),n},update:function(t,n){(!i||s.forcePlaceholderSize)&&(n.height()||n.height(e.currentItem.innerHeight()-parseInt(e.currentItem.css("paddingTop")||0,10)-parseInt(e.currentItem.css("paddingBottom")||0,10)),n.width()||n.width(e.currentItem.innerWidth()-parseInt(e.currentItem.css("paddingLeft")||0,10)-parseInt(e.currentItem.css("paddingRight")||0,10)))}}),e.placeholder=t(s.placeholder.element.call(e.element,e.currentItem)),e.currentItem.after(e.placeholder),s.placeholder.update(e,e.placeholder)},_createTrPlaceholder:function(e,i){var s=this;e.children().each(function(){t(" ",s.document[0]).attr("colspan",t(this).attr("colspan")||1).appendTo(i)})},_contactContainers:function(e){var i,s,n,o,a,r,l,h,c,u,d=null,p=null;for(i=this.containers.length-1;i>=0;i--)if(!t.contains(this.currentItem[0],this.containers[i].element[0]))if(this._intersectsWith(this.containers[i].containerCache)){if(d&&t.contains(this.containers[i].element[0],d.element[0]))continue; -d=this.containers[i],p=i}else this.containers[i].containerCache.over&&(this.containers[i]._trigger("out",e,this._uiHash(this)),this.containers[i].containerCache.over=0);if(d)if(1===this.containers.length)this.containers[p].containerCache.over||(this.containers[p]._trigger("over",e,this._uiHash(this)),this.containers[p].containerCache.over=1);else{for(n=1e4,o=null,c=d.floating||this._isFloating(this.currentItem),a=c?"left":"top",r=c?"width":"height",u=c?"clientX":"clientY",s=this.items.length-1;s>=0;s--)t.contains(this.containers[p].element[0],this.items[s].item[0])&&this.items[s].item[0]!==this.currentItem[0]&&(l=this.items[s].item.offset()[a],h=!1,e[u]-l>this.items[s][r]/2&&(h=!0),n>Math.abs(e[u]-l)&&(n=Math.abs(e[u]-l),o=this.items[s],this.direction=h?"up":"down"));if(!o&&!this.options.dropOnEmpty)return;if(this.currentContainer===this.containers[p])return this.currentContainer.containerCache.over||(this.containers[p]._trigger("over",e,this._uiHash()),this.currentContainer.containerCache.over=1),void 0;o?this._rearrange(e,o,null,!0):this._rearrange(e,null,this.containers[p].element,!0),this._trigger("change",e,this._uiHash()),this.containers[p]._trigger("change",e,this._uiHash(this)),this.currentContainer=this.containers[p],this.options.placeholder.update(this.currentContainer,this.placeholder),this.containers[p]._trigger("over",e,this._uiHash(this)),this.containers[p].containerCache.over=1}},_createHelper:function(e){var i=this.options,s=t.isFunction(i.helper)?t(i.helper.apply(this.element[0],[e,this.currentItem])):"clone"===i.helper?this.currentItem.clone():this.currentItem;return s.parents("body").length||t("parent"!==i.appendTo?i.appendTo:this.currentItem[0].parentNode)[0].appendChild(s[0]),s[0]===this.currentItem[0]&&(this._storedCSS={width:this.currentItem[0].style.width,height:this.currentItem[0].style.height,position:this.currentItem.css("position"),top:this.currentItem.css("top"),left:this.currentItem.css("left")}),(!s[0].style.width||i.forceHelperSize)&&s.width(this.currentItem.width()),(!s[0].style.height||i.forceHelperSize)&&s.height(this.currentItem.height()),s},_adjustOffsetFromHelper:function(e){"string"==typeof e&&(e=e.split(" ")),t.isArray(e)&&(e={left:+e[0],top:+e[1]||0}),"left"in e&&(this.offset.click.left=e.left+this.margins.left),"right"in e&&(this.offset.click.left=this.helperProportions.width-e.right+this.margins.left),"top"in e&&(this.offset.click.top=e.top+this.margins.top),"bottom"in e&&(this.offset.click.top=this.helperProportions.height-e.bottom+this.margins.top)},_getParentOffset:function(){this.offsetParent=this.helper.offsetParent();var e=this.offsetParent.offset();return"absolute"===this.cssPosition&&this.scrollParent[0]!==this.document[0]&&t.contains(this.scrollParent[0],this.offsetParent[0])&&(e.left+=this.scrollParent.scrollLeft(),e.top+=this.scrollParent.scrollTop()),(this.offsetParent[0]===this.document[0].body||this.offsetParent[0].tagName&&"html"===this.offsetParent[0].tagName.toLowerCase()&&t.ui.ie)&&(e={top:0,left:0}),{top:e.top+(parseInt(this.offsetParent.css("borderTopWidth"),10)||0),left:e.left+(parseInt(this.offsetParent.css("borderLeftWidth"),10)||0)}},_getRelativeOffset:function(){if("relative"===this.cssPosition){var t=this.currentItem.position();return{top:t.top-(parseInt(this.helper.css("top"),10)||0)+this.scrollParent.scrollTop(),left:t.left-(parseInt(this.helper.css("left"),10)||0)+this.scrollParent.scrollLeft()}}return{top:0,left:0}},_cacheMargins:function(){this.margins={left:parseInt(this.currentItem.css("marginLeft"),10)||0,top:parseInt(this.currentItem.css("marginTop"),10)||0}},_cacheHelperProportions:function(){this.helperProportions={width:this.helper.outerWidth(),height:this.helper.outerHeight()}},_setContainment:function(){var e,i,s,n=this.options;"parent"===n.containment&&(n.containment=this.helper[0].parentNode),("document"===n.containment||"window"===n.containment)&&(this.containment=[0-this.offset.relative.left-this.offset.parent.left,0-this.offset.relative.top-this.offset.parent.top,"document"===n.containment?this.document.width():this.window.width()-this.helperProportions.width-this.margins.left,("document"===n.containment?this.document.width():this.window.height()||this.document[0].body.parentNode.scrollHeight)-this.helperProportions.height-this.margins.top]),/^(document|window|parent)$/.test(n.containment)||(e=t(n.containment)[0],i=t(n.containment).offset(),s="hidden"!==t(e).css("overflow"),this.containment=[i.left+(parseInt(t(e).css("borderLeftWidth"),10)||0)+(parseInt(t(e).css("paddingLeft"),10)||0)-this.margins.left,i.top+(parseInt(t(e).css("borderTopWidth"),10)||0)+(parseInt(t(e).css("paddingTop"),10)||0)-this.margins.top,i.left+(s?Math.max(e.scrollWidth,e.offsetWidth):e.offsetWidth)-(parseInt(t(e).css("borderLeftWidth"),10)||0)-(parseInt(t(e).css("paddingRight"),10)||0)-this.helperProportions.width-this.margins.left,i.top+(s?Math.max(e.scrollHeight,e.offsetHeight):e.offsetHeight)-(parseInt(t(e).css("borderTopWidth"),10)||0)-(parseInt(t(e).css("paddingBottom"),10)||0)-this.helperProportions.height-this.margins.top])},_convertPositionTo:function(e,i){i||(i=this.position);var s="absolute"===e?1:-1,n="absolute"!==this.cssPosition||this.scrollParent[0]!==this.document[0]&&t.contains(this.scrollParent[0],this.offsetParent[0])?this.scrollParent:this.offsetParent,o=/(html|body)/i.test(n[0].tagName);return{top:i.top+this.offset.relative.top*s+this.offset.parent.top*s-("fixed"===this.cssPosition?-this.scrollParent.scrollTop():o?0:n.scrollTop())*s,left:i.left+this.offset.relative.left*s+this.offset.parent.left*s-("fixed"===this.cssPosition?-this.scrollParent.scrollLeft():o?0:n.scrollLeft())*s}},_generatePosition:function(e){var i,s,n=this.options,o=e.pageX,a=e.pageY,r="absolute"!==this.cssPosition||this.scrollParent[0]!==this.document[0]&&t.contains(this.scrollParent[0],this.offsetParent[0])?this.scrollParent:this.offsetParent,l=/(html|body)/i.test(r[0].tagName);return"relative"!==this.cssPosition||this.scrollParent[0]!==this.document[0]&&this.scrollParent[0]!==this.offsetParent[0]||(this.offset.relative=this._getRelativeOffset()),this.originalPosition&&(this.containment&&(e.pageX-this.offset.click.leftthis.containment[2]&&(o=this.containment[2]+this.offset.click.left),e.pageY-this.offset.click.top>this.containment[3]&&(a=this.containment[3]+this.offset.click.top)),n.grid&&(i=this.originalPageY+Math.round((a-this.originalPageY)/n.grid[1])*n.grid[1],a=this.containment?i-this.offset.click.top>=this.containment[1]&&i-this.offset.click.top<=this.containment[3]?i:i-this.offset.click.top>=this.containment[1]?i-n.grid[1]:i+n.grid[1]:i,s=this.originalPageX+Math.round((o-this.originalPageX)/n.grid[0])*n.grid[0],o=this.containment?s-this.offset.click.left>=this.containment[0]&&s-this.offset.click.left<=this.containment[2]?s:s-this.offset.click.left>=this.containment[0]?s-n.grid[0]:s+n.grid[0]:s)),{top:a-this.offset.click.top-this.offset.relative.top-this.offset.parent.top+("fixed"===this.cssPosition?-this.scrollParent.scrollTop():l?0:r.scrollTop()),left:o-this.offset.click.left-this.offset.relative.left-this.offset.parent.left+("fixed"===this.cssPosition?-this.scrollParent.scrollLeft():l?0:r.scrollLeft())}},_rearrange:function(t,e,i,s){i?i[0].appendChild(this.placeholder[0]):e.item[0].parentNode.insertBefore(this.placeholder[0],"down"===this.direction?e.item[0]:e.item[0].nextSibling),this.counter=this.counter?++this.counter:1;var n=this.counter;this._delay(function(){n===this.counter&&this.refreshPositions(!s)})},_clear:function(t,e){function i(t,e,i){return function(s){i._trigger(t,s,e._uiHash(e))}}this.reverting=!1;var s,n=[];if(!this._noFinalSort&&this.currentItem.parent().length&&this.placeholder.before(this.currentItem),this._noFinalSort=null,this.helper[0]===this.currentItem[0]){for(s in this._storedCSS)("auto"===this._storedCSS[s]||"static"===this._storedCSS[s])&&(this._storedCSS[s]="");this.currentItem.css(this._storedCSS).removeClass("ui-sortable-helper")}else this.currentItem.show();for(this.fromOutside&&!e&&n.push(function(t){this._trigger("receive",t,this._uiHash(this.fromOutside))}),!this.fromOutside&&this.domPosition.prev===this.currentItem.prev().not(".ui-sortable-helper")[0]&&this.domPosition.parent===this.currentItem.parent()[0]||e||n.push(function(t){this._trigger("update",t,this._uiHash())}),this!==this.currentContainer&&(e||(n.push(function(t){this._trigger("remove",t,this._uiHash())}),n.push(function(t){return function(e){t._trigger("receive",e,this._uiHash(this))}}.call(this,this.currentContainer)),n.push(function(t){return function(e){t._trigger("update",e,this._uiHash(this))}}.call(this,this.currentContainer)))),s=this.containers.length-1;s>=0;s--)e||n.push(i("deactivate",this,this.containers[s])),this.containers[s].containerCache.over&&(n.push(i("out",this,this.containers[s])),this.containers[s].containerCache.over=0);if(this.storedCursor&&(this.document.find("body").css("cursor",this.storedCursor),this.storedStylesheet.remove()),this._storedOpacity&&this.helper.css("opacity",this._storedOpacity),this._storedZIndex&&this.helper.css("zIndex","auto"===this._storedZIndex?"":this._storedZIndex),this.dragging=!1,e||this._trigger("beforeStop",t,this._uiHash()),this.placeholder[0].parentNode.removeChild(this.placeholder[0]),this.cancelHelperRemoval||(this.helper[0]!==this.currentItem[0]&&this.helper.remove(),this.helper=null),!e){for(s=0;n.length>s;s++)n[s].call(this,t);this._trigger("stop",t,this._uiHash())}return this.fromOutside=!1,!this.cancelHelperRemoval},_trigger:function(){t.Widget.prototype._trigger.apply(this,arguments)===!1&&this.cancel()},_uiHash:function(e){var i=e||this;return{helper:i.helper,placeholder:i.placeholder||t([]),position:i.position,originalPosition:i.originalPosition,offset:i.positionAbs,item:i.currentItem,sender:e?e.element:null}}}),t.widget("ui.slider",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"slide",options:{animate:!1,distance:0,max:100,min:0,orientation:"horizontal",range:!1,step:1,value:0,values:null,change:null,slide:null,start:null,stop:null},numPages:5,_create:function(){this._keySliding=!1,this._mouseSliding=!1,this._animateOff=!0,this._handleIndex=null,this._detectOrientation(),this._mouseInit(),this._calculateNewMax(),this.element.addClass("ui-slider ui-slider-"+this.orientation+" ui-widget"+" ui-widget-content"+" ui-corner-all"),this._refresh(),this._setOption("disabled",this.options.disabled),this._animateOff=!1},_refresh:function(){this._createRange(),this._createHandles(),this._setupEvents(),this._refreshValue()},_createHandles:function(){var e,i,s=this.options,n=this.element.find(".ui-slider-handle").addClass("ui-state-default ui-corner-all"),o="",a=[];for(i=s.values&&s.values.length||1,n.length>i&&(n.slice(i).remove(),n=n.slice(0,i)),e=n.length;i>e;e++)a.push(o);this.handles=n.add(t(a.join("")).appendTo(this.element)),this.handle=this.handles.eq(0),this.handles.each(function(e){t(this).data("ui-slider-handle-index",e)})},_createRange:function(){var e=this.options,i="";e.range?(e.range===!0&&(e.values?e.values.length&&2!==e.values.length?e.values=[e.values[0],e.values[0]]:t.isArray(e.values)&&(e.values=e.values.slice(0)):e.values=[this._valueMin(),this._valueMin()]),this.range&&this.range.length?this.range.removeClass("ui-slider-range-min ui-slider-range-max").css({left:"",bottom:""}):(this.range=t("
    ").appendTo(this.element),i="ui-slider-range ui-widget-header ui-corner-all"),this.range.addClass(i+("min"===e.range||"max"===e.range?" ui-slider-range-"+e.range:""))):(this.range&&this.range.remove(),this.range=null)},_setupEvents:function(){this._off(this.handles),this._on(this.handles,this._handleEvents),this._hoverable(this.handles),this._focusable(this.handles)},_destroy:function(){this.handles.remove(),this.range&&this.range.remove(),this.element.removeClass("ui-slider ui-slider-horizontal ui-slider-vertical ui-widget ui-widget-content ui-corner-all"),this._mouseDestroy()},_mouseCapture:function(e){var i,s,n,o,a,r,l,h,c=this,u=this.options;return u.disabled?!1:(this.elementSize={width:this.element.outerWidth(),height:this.element.outerHeight()},this.elementOffset=this.element.offset(),i={x:e.pageX,y:e.pageY},s=this._normValueFromMouse(i),n=this._valueMax()-this._valueMin()+1,this.handles.each(function(e){var i=Math.abs(s-c.values(e));(n>i||n===i&&(e===c._lastChangedValue||c.values(e)===u.min))&&(n=i,o=t(this),a=e)}),r=this._start(e,a),r===!1?!1:(this._mouseSliding=!0,this._handleIndex=a,o.addClass("ui-state-active").focus(),l=o.offset(),h=!t(e.target).parents().addBack().is(".ui-slider-handle"),this._clickOffset=h?{left:0,top:0}:{left:e.pageX-l.left-o.width()/2,top:e.pageY-l.top-o.height()/2-(parseInt(o.css("borderTopWidth"),10)||0)-(parseInt(o.css("borderBottomWidth"),10)||0)+(parseInt(o.css("marginTop"),10)||0)},this.handles.hasClass("ui-state-hover")||this._slide(e,a,s),this._animateOff=!0,!0))},_mouseStart:function(){return!0},_mouseDrag:function(t){var e={x:t.pageX,y:t.pageY},i=this._normValueFromMouse(e);return this._slide(t,this._handleIndex,i),!1},_mouseStop:function(t){return this.handles.removeClass("ui-state-active"),this._mouseSliding=!1,this._stop(t,this._handleIndex),this._change(t,this._handleIndex),this._handleIndex=null,this._clickOffset=null,this._animateOff=!1,!1},_detectOrientation:function(){this.orientation="vertical"===this.options.orientation?"vertical":"horizontal"},_normValueFromMouse:function(t){var e,i,s,n,o;return"horizontal"===this.orientation?(e=this.elementSize.width,i=t.x-this.elementOffset.left-(this._clickOffset?this._clickOffset.left:0)):(e=this.elementSize.height,i=t.y-this.elementOffset.top-(this._clickOffset?this._clickOffset.top:0)),s=i/e,s>1&&(s=1),0>s&&(s=0),"vertical"===this.orientation&&(s=1-s),n=this._valueMax()-this._valueMin(),o=this._valueMin()+s*n,this._trimAlignValue(o)},_start:function(t,e){var i={handle:this.handles[e],value:this.value()};return this.options.values&&this.options.values.length&&(i.value=this.values(e),i.values=this.values()),this._trigger("start",t,i)},_slide:function(t,e,i){var s,n,o;this.options.values&&this.options.values.length?(s=this.values(e?0:1),2===this.options.values.length&&this.options.range===!0&&(0===e&&i>s||1===e&&s>i)&&(i=s),i!==this.values(e)&&(n=this.values(),n[e]=i,o=this._trigger("slide",t,{handle:this.handles[e],value:i,values:n}),s=this.values(e?0:1),o!==!1&&this.values(e,i))):i!==this.value()&&(o=this._trigger("slide",t,{handle:this.handles[e],value:i}),o!==!1&&this.value(i))},_stop:function(t,e){var i={handle:this.handles[e],value:this.value()};this.options.values&&this.options.values.length&&(i.value=this.values(e),i.values=this.values()),this._trigger("stop",t,i)},_change:function(t,e){if(!this._keySliding&&!this._mouseSliding){var i={handle:this.handles[e],value:this.value()};this.options.values&&this.options.values.length&&(i.value=this.values(e),i.values=this.values()),this._lastChangedValue=e,this._trigger("change",t,i)}},value:function(t){return arguments.length?(this.options.value=this._trimAlignValue(t),this._refreshValue(),this._change(null,0),void 0):this._value()},values:function(e,i){var s,n,o;if(arguments.length>1)return this.options.values[e]=this._trimAlignValue(i),this._refreshValue(),this._change(null,e),void 0;if(!arguments.length)return this._values();if(!t.isArray(arguments[0]))return this.options.values&&this.options.values.length?this._values(e):this.value();for(s=this.options.values,n=arguments[0],o=0;s.length>o;o+=1)s[o]=this._trimAlignValue(n[o]),this._change(null,o);this._refreshValue()},_setOption:function(e,i){var s,n=0;switch("range"===e&&this.options.range===!0&&("min"===i?(this.options.value=this._values(0),this.options.values=null):"max"===i&&(this.options.value=this._values(this.options.values.length-1),this.options.values=null)),t.isArray(this.options.values)&&(n=this.options.values.length),"disabled"===e&&this.element.toggleClass("ui-state-disabled",!!i),this._super(e,i),e){case"orientation":this._detectOrientation(),this.element.removeClass("ui-slider-horizontal ui-slider-vertical").addClass("ui-slider-"+this.orientation),this._refreshValue(),this.handles.css("horizontal"===i?"bottom":"left","");break;case"value":this._animateOff=!0,this._refreshValue(),this._change(null,0),this._animateOff=!1;break;case"values":for(this._animateOff=!0,this._refreshValue(),s=0;n>s;s+=1)this._change(null,s);this._animateOff=!1;break;case"step":case"min":case"max":this._animateOff=!0,this._calculateNewMax(),this._refreshValue(),this._animateOff=!1;break;case"range":this._animateOff=!0,this._refresh(),this._animateOff=!1}},_value:function(){var t=this.options.value;return t=this._trimAlignValue(t)},_values:function(t){var e,i,s;if(arguments.length)return e=this.options.values[t],e=this._trimAlignValue(e);if(this.options.values&&this.options.values.length){for(i=this.options.values.slice(),s=0;i.length>s;s+=1)i[s]=this._trimAlignValue(i[s]);return i}return[]},_trimAlignValue:function(t){if(this._valueMin()>=t)return this._valueMin();if(t>=this._valueMax())return this._valueMax();var e=this.options.step>0?this.options.step:1,i=(t-this._valueMin())%e,s=t-i;return 2*Math.abs(i)>=e&&(s+=i>0?e:-e),parseFloat(s.toFixed(5))},_calculateNewMax:function(){var t=this.options.max,e=this._valueMin(),i=this.options.step,s=Math.floor(+(t-e).toFixed(this._precision())/i)*i;t=s+e,this.max=parseFloat(t.toFixed(this._precision()))},_precision:function(){var t=this._precisionOf(this.options.step);return null!==this.options.min&&(t=Math.max(t,this._precisionOf(this.options.min))),t},_precisionOf:function(t){var e=""+t,i=e.indexOf(".");return-1===i?0:e.length-i-1},_valueMin:function(){return this.options.min},_valueMax:function(){return this.max},_refreshValue:function(){var e,i,s,n,o,a=this.options.range,r=this.options,l=this,h=this._animateOff?!1:r.animate,c={};this.options.values&&this.options.values.length?this.handles.each(function(s){i=100*((l.values(s)-l._valueMin())/(l._valueMax()-l._valueMin())),c["horizontal"===l.orientation?"left":"bottom"]=i+"%",t(this).stop(1,1)[h?"animate":"css"](c,r.animate),l.options.range===!0&&("horizontal"===l.orientation?(0===s&&l.range.stop(1,1)[h?"animate":"css"]({left:i+"%"},r.animate),1===s&&l.range[h?"animate":"css"]({width:i-e+"%"},{queue:!1,duration:r.animate})):(0===s&&l.range.stop(1,1)[h?"animate":"css"]({bottom:i+"%"},r.animate),1===s&&l.range[h?"animate":"css"]({height:i-e+"%"},{queue:!1,duration:r.animate}))),e=i}):(s=this.value(),n=this._valueMin(),o=this._valueMax(),i=o!==n?100*((s-n)/(o-n)):0,c["horizontal"===this.orientation?"left":"bottom"]=i+"%",this.handle.stop(1,1)[h?"animate":"css"](c,r.animate),"min"===a&&"horizontal"===this.orientation&&this.range.stop(1,1)[h?"animate":"css"]({width:i+"%"},r.animate),"max"===a&&"horizontal"===this.orientation&&this.range[h?"animate":"css"]({width:100-i+"%"},{queue:!1,duration:r.animate}),"min"===a&&"vertical"===this.orientation&&this.range.stop(1,1)[h?"animate":"css"]({height:i+"%"},r.animate),"max"===a&&"vertical"===this.orientation&&this.range[h?"animate":"css"]({height:100-i+"%"},{queue:!1,duration:r.animate}))},_handleEvents:{keydown:function(e){var i,s,n,o,a=t(e.target).data("ui-slider-handle-index");switch(e.keyCode){case t.ui.keyCode.HOME:case t.ui.keyCode.END:case t.ui.keyCode.PAGE_UP:case t.ui.keyCode.PAGE_DOWN:case t.ui.keyCode.UP:case t.ui.keyCode.RIGHT:case t.ui.keyCode.DOWN:case t.ui.keyCode.LEFT:if(e.preventDefault(),!this._keySliding&&(this._keySliding=!0,t(e.target).addClass("ui-state-active"),i=this._start(e,a),i===!1))return}switch(o=this.options.step,s=n=this.options.values&&this.options.values.length?this.values(a):this.value(),e.keyCode){case t.ui.keyCode.HOME:n=this._valueMin();break;case t.ui.keyCode.END:n=this._valueMax();break;case t.ui.keyCode.PAGE_UP:n=this._trimAlignValue(s+(this._valueMax()-this._valueMin())/this.numPages);break;case t.ui.keyCode.PAGE_DOWN:n=this._trimAlignValue(s-(this._valueMax()-this._valueMin())/this.numPages);break;case t.ui.keyCode.UP:case t.ui.keyCode.RIGHT:if(s===this._valueMax())return;n=this._trimAlignValue(s+o);break;case t.ui.keyCode.DOWN:case t.ui.keyCode.LEFT:if(s===this._valueMin())return;n=this._trimAlignValue(s-o)}this._slide(e,a,n)},keyup:function(e){var i=t(e.target).data("ui-slider-handle-index");this._keySliding&&(this._keySliding=!1,this._stop(e,i),this._change(e,i),t(e.target).removeClass("ui-state-active"))}}});var a="ui-effects-",r=t;t.effects={effect:{}},function(t,e){function i(t,e,i){var s=u[e.type]||{};return null==t?i||!e.def?null:e.def:(t=s.floor?~~t:parseFloat(t),isNaN(t)?e.def:s.mod?(t+s.mod)%s.mod:0>t?0:t>s.max?s.max:t)}function s(i){var s=h(),n=s._rgba=[];return i=i.toLowerCase(),f(l,function(t,o){var a,r=o.re.exec(i),l=r&&o.parse(r),h=o.space||"rgba";return l?(a=s[h](l),s[c[h].cache]=a[c[h].cache],n=s._rgba=a._rgba,!1):e}),n.length?("0,0,0,0"===n.join()&&t.extend(n,o.transparent),s):o[i]}function n(t,e,i){return i=(i+1)%1,1>6*i?t+6*(e-t)*i:1>2*i?e:2>3*i?t+6*(e-t)*(2/3-i):t}var o,a="backgroundColor borderBottomColor borderLeftColor borderRightColor borderTopColor color columnRuleColor outlineColor textDecorationColor textEmphasisColor",r=/^([\-+])=\s*(\d+\.?\d*)/,l=[{re:/rgba?\(\s*(\d{1,3})\s*,\s*(\d{1,3})\s*,\s*(\d{1,3})\s*(?:,\s*(\d?(?:\.\d+)?)\s*)?\)/,parse:function(t){return[t[1],t[2],t[3],t[4]]}},{re:/rgba?\(\s*(\d+(?:\.\d+)?)\%\s*,\s*(\d+(?:\.\d+)?)\%\s*,\s*(\d+(?:\.\d+)?)\%\s*(?:,\s*(\d?(?:\.\d+)?)\s*)?\)/,parse:function(t){return[2.55*t[1],2.55*t[2],2.55*t[3],t[4]]}},{re:/#([a-f0-9]{2})([a-f0-9]{2})([a-f0-9]{2})/,parse:function(t){return[parseInt(t[1],16),parseInt(t[2],16),parseInt(t[3],16)]}},{re:/#([a-f0-9])([a-f0-9])([a-f0-9])/,parse:function(t){return[parseInt(t[1]+t[1],16),parseInt(t[2]+t[2],16),parseInt(t[3]+t[3],16)]}},{re:/hsla?\(\s*(\d+(?:\.\d+)?)\s*,\s*(\d+(?:\.\d+)?)\%\s*,\s*(\d+(?:\.\d+)?)\%\s*(?:,\s*(\d?(?:\.\d+)?)\s*)?\)/,space:"hsla",parse:function(t){return[t[1],t[2]/100,t[3]/100,t[4]]}}],h=t.Color=function(e,i,s,n){return new t.Color.fn.parse(e,i,s,n)},c={rgba:{props:{red:{idx:0,type:"byte"},green:{idx:1,type:"byte"},blue:{idx:2,type:"byte"}}},hsla:{props:{hue:{idx:0,type:"degrees"},saturation:{idx:1,type:"percent"},lightness:{idx:2,type:"percent"}}}},u={"byte":{floor:!0,max:255},percent:{max:1},degrees:{mod:360,floor:!0}},d=h.support={},p=t("

    ")[0],f=t.each;p.style.cssText="background-color:rgba(1,1,1,.5)",d.rgba=p.style.backgroundColor.indexOf("rgba")>-1,f(c,function(t,e){e.cache="_"+t,e.props.alpha={idx:3,type:"percent",def:1}}),h.fn=t.extend(h.prototype,{parse:function(n,a,r,l){if(n===e)return this._rgba=[null,null,null,null],this;(n.jquery||n.nodeType)&&(n=t(n).css(a),a=e);var u=this,d=t.type(n),p=this._rgba=[];return a!==e&&(n=[n,a,r,l],d="array"),"string"===d?this.parse(s(n)||o._default):"array"===d?(f(c.rgba.props,function(t,e){p[e.idx]=i(n[e.idx],e)}),this):"object"===d?(n instanceof h?f(c,function(t,e){n[e.cache]&&(u[e.cache]=n[e.cache].slice())}):f(c,function(e,s){var o=s.cache;f(s.props,function(t,e){if(!u[o]&&s.to){if("alpha"===t||null==n[t])return;u[o]=s.to(u._rgba)}u[o][e.idx]=i(n[t],e,!0)}),u[o]&&0>t.inArray(null,u[o].slice(0,3))&&(u[o][3]=1,s.from&&(u._rgba=s.from(u[o])))}),this):e},is:function(t){var i=h(t),s=!0,n=this;return f(c,function(t,o){var a,r=i[o.cache];return r&&(a=n[o.cache]||o.to&&o.to(n._rgba)||[],f(o.props,function(t,i){return null!=r[i.idx]?s=r[i.idx]===a[i.idx]:e})),s}),s},_space:function(){var t=[],e=this;return f(c,function(i,s){e[s.cache]&&t.push(i)}),t.pop()},transition:function(t,e){var s=h(t),n=s._space(),o=c[n],a=0===this.alpha()?h("transparent"):this,r=a[o.cache]||o.to(a._rgba),l=r.slice();return s=s[o.cache],f(o.props,function(t,n){var o=n.idx,a=r[o],h=s[o],c=u[n.type]||{};null!==h&&(null===a?l[o]=h:(c.mod&&(h-a>c.mod/2?a+=c.mod:a-h>c.mod/2&&(a-=c.mod)),l[o]=i((h-a)*e+a,n)))}),this[n](l)},blend:function(e){if(1===this._rgba[3])return this;var i=this._rgba.slice(),s=i.pop(),n=h(e)._rgba;return h(t.map(i,function(t,e){return(1-s)*n[e]+s*t}))},toRgbaString:function(){var e="rgba(",i=t.map(this._rgba,function(t,e){return null==t?e>2?1:0:t});return 1===i[3]&&(i.pop(),e="rgb("),e+i.join()+")"},toHslaString:function(){var e="hsla(",i=t.map(this.hsla(),function(t,e){return null==t&&(t=e>2?1:0),e&&3>e&&(t=Math.round(100*t)+"%"),t});return 1===i[3]&&(i.pop(),e="hsl("),e+i.join()+")"},toHexString:function(e){var i=this._rgba.slice(),s=i.pop();return e&&i.push(~~(255*s)),"#"+t.map(i,function(t){return t=(t||0).toString(16),1===t.length?"0"+t:t}).join("")},toString:function(){return 0===this._rgba[3]?"transparent":this.toRgbaString()}}),h.fn.parse.prototype=h.fn,c.hsla.to=function(t){if(null==t[0]||null==t[1]||null==t[2])return[null,null,null,t[3]];var e,i,s=t[0]/255,n=t[1]/255,o=t[2]/255,a=t[3],r=Math.max(s,n,o),l=Math.min(s,n,o),h=r-l,c=r+l,u=.5*c;return e=l===r?0:s===r?60*(n-o)/h+360:n===r?60*(o-s)/h+120:60*(s-n)/h+240,i=0===h?0:.5>=u?h/c:h/(2-c),[Math.round(e)%360,i,u,null==a?1:a]},c.hsla.from=function(t){if(null==t[0]||null==t[1]||null==t[2])return[null,null,null,t[3]];var e=t[0]/360,i=t[1],s=t[2],o=t[3],a=.5>=s?s*(1+i):s+i-s*i,r=2*s-a;return[Math.round(255*n(r,a,e+1/3)),Math.round(255*n(r,a,e)),Math.round(255*n(r,a,e-1/3)),o]},f(c,function(s,n){var o=n.props,a=n.cache,l=n.to,c=n.from;h.fn[s]=function(s){if(l&&!this[a]&&(this[a]=l(this._rgba)),s===e)return this[a].slice();var n,r=t.type(s),u="array"===r||"object"===r?s:arguments,d=this[a].slice();return f(o,function(t,e){var s=u["object"===r?t:e.idx];null==s&&(s=d[e.idx]),d[e.idx]=i(s,e)}),c?(n=h(c(d)),n[a]=d,n):h(d)},f(o,function(e,i){h.fn[e]||(h.fn[e]=function(n){var o,a=t.type(n),l="alpha"===e?this._hsla?"hsla":"rgba":s,h=this[l](),c=h[i.idx];return"undefined"===a?c:("function"===a&&(n=n.call(this,c),a=t.type(n)),null==n&&i.empty?this:("string"===a&&(o=r.exec(n),o&&(n=c+parseFloat(o[2])*("+"===o[1]?1:-1))),h[i.idx]=n,this[l](h)))})})}),h.hook=function(e){var i=e.split(" ");f(i,function(e,i){t.cssHooks[i]={set:function(e,n){var o,a,r="";if("transparent"!==n&&("string"!==t.type(n)||(o=s(n)))){if(n=h(o||n),!d.rgba&&1!==n._rgba[3]){for(a="backgroundColor"===i?e.parentNode:e;(""===r||"transparent"===r)&&a&&a.style;)try{r=t.css(a,"backgroundColor"),a=a.parentNode}catch(l){}n=n.blend(r&&"transparent"!==r?r:"_default")}n=n.toRgbaString()}try{e.style[i]=n}catch(l){}}},t.fx.step[i]=function(e){e.colorInit||(e.start=h(e.elem,i),e.end=h(e.end),e.colorInit=!0),t.cssHooks[i].set(e.elem,e.start.transition(e.end,e.pos))}})},h.hook(a),t.cssHooks.borderColor={expand:function(t){var e={};return f(["Top","Right","Bottom","Left"],function(i,s){e["border"+s+"Color"]=t}),e}},o=t.Color.names={aqua:"#00ffff",black:"#000000",blue:"#0000ff",fuchsia:"#ff00ff",gray:"#808080",green:"#008000",lime:"#00ff00",maroon:"#800000",navy:"#000080",olive:"#808000",purple:"#800080",red:"#ff0000",silver:"#c0c0c0",teal:"#008080",white:"#ffffff",yellow:"#ffff00",transparent:[null,null,null,0],_default:"#ffffff"}}(r),function(){function e(e){var i,s,n=e.ownerDocument.defaultView?e.ownerDocument.defaultView.getComputedStyle(e,null):e.currentStyle,o={};if(n&&n.length&&n[0]&&n[n[0]])for(s=n.length;s--;)i=n[s],"string"==typeof n[i]&&(o[t.camelCase(i)]=n[i]);else for(i in n)"string"==typeof n[i]&&(o[i]=n[i]);return o}function i(e,i){var s,o,a={};for(s in i)o=i[s],e[s]!==o&&(n[s]||(t.fx.step[s]||!isNaN(parseFloat(o)))&&(a[s]=o));return a}var s=["add","remove","toggle"],n={border:1,borderBottom:1,borderColor:1,borderLeft:1,borderRight:1,borderTop:1,borderWidth:1,margin:1,padding:1};t.each(["borderLeftStyle","borderRightStyle","borderBottomStyle","borderTopStyle"],function(e,i){t.fx.step[i]=function(t){("none"!==t.end&&!t.setAttr||1===t.pos&&!t.setAttr)&&(r.style(t.elem,i,t.end),t.setAttr=!0)}}),t.fn.addBack||(t.fn.addBack=function(t){return this.add(null==t?this.prevObject:this.prevObject.filter(t))}),t.effects.animateClass=function(n,o,a,r){var l=t.speed(o,a,r);return this.queue(function(){var o,a=t(this),r=a.attr("class")||"",h=l.children?a.find("*").addBack():a;h=h.map(function(){var i=t(this);return{el:i,start:e(this)}}),o=function(){t.each(s,function(t,e){n[e]&&a[e+"Class"](n[e])})},o(),h=h.map(function(){return this.end=e(this.el[0]),this.diff=i(this.start,this.end),this}),a.attr("class",r),h=h.map(function(){var e=this,i=t.Deferred(),s=t.extend({},l,{queue:!1,complete:function(){i.resolve(e)}});return this.el.animate(this.diff,s),i.promise()}),t.when.apply(t,h.get()).done(function(){o(),t.each(arguments,function(){var e=this.el;t.each(this.diff,function(t){e.css(t,"")})}),l.complete.call(a[0])})})},t.fn.extend({addClass:function(e){return function(i,s,n,o){return s?t.effects.animateClass.call(this,{add:i},s,n,o):e.apply(this,arguments)}}(t.fn.addClass),removeClass:function(e){return function(i,s,n,o){return arguments.length>1?t.effects.animateClass.call(this,{remove:i},s,n,o):e.apply(this,arguments)}}(t.fn.removeClass),toggleClass:function(e){return function(i,s,n,o,a){return"boolean"==typeof s||void 0===s?n?t.effects.animateClass.call(this,s?{add:i}:{remove:i},n,o,a):e.apply(this,arguments):t.effects.animateClass.call(this,{toggle:i},s,n,o)}}(t.fn.toggleClass),switchClass:function(e,i,s,n,o){return t.effects.animateClass.call(this,{add:i,remove:e},s,n,o)}})}(),function(){function e(e,i,s,n){return t.isPlainObject(e)&&(i=e,e=e.effect),e={effect:e},null==i&&(i={}),t.isFunction(i)&&(n=i,s=null,i={}),("number"==typeof i||t.fx.speeds[i])&&(n=s,s=i,i={}),t.isFunction(s)&&(n=s,s=null),i&&t.extend(e,i),s=s||i.duration,e.duration=t.fx.off?0:"number"==typeof s?s:s in t.fx.speeds?t.fx.speeds[s]:t.fx.speeds._default,e.complete=n||i.complete,e}function i(e){return!e||"number"==typeof e||t.fx.speeds[e]?!0:"string"!=typeof e||t.effects.effect[e]?t.isFunction(e)?!0:"object"!=typeof e||e.effect?!1:!0:!0}t.extend(t.effects,{version:"1.11.4",save:function(t,e){for(var i=0;e.length>i;i++)null!==e[i]&&t.data(a+e[i],t[0].style[e[i]])},restore:function(t,e){var i,s;for(s=0;e.length>s;s++)null!==e[s]&&(i=t.data(a+e[s]),void 0===i&&(i=""),t.css(e[s],i))},setMode:function(t,e){return"toggle"===e&&(e=t.is(":hidden")?"show":"hide"),e},getBaseline:function(t,e){var i,s;switch(t[0]){case"top":i=0;break;case"middle":i=.5;break;case"bottom":i=1;break;default:i=t[0]/e.height}switch(t[1]){case"left":s=0;break;case"center":s=.5;break;case"right":s=1;break;default:s=t[1]/e.width}return{x:s,y:i}},createWrapper:function(e){if(e.parent().is(".ui-effects-wrapper"))return e.parent();var i={width:e.outerWidth(!0),height:e.outerHeight(!0),"float":e.css("float")},s=t("

    ").addClass("ui-effects-wrapper").css({fontSize:"100%",background:"transparent",border:"none",margin:0,padding:0}),n={width:e.width(),height:e.height()},o=document.activeElement;try{o.id}catch(a){o=document.body}return e.wrap(s),(e[0]===o||t.contains(e[0],o))&&t(o).focus(),s=e.parent(),"static"===e.css("position")?(s.css({position:"relative"}),e.css({position:"relative"})):(t.extend(i,{position:e.css("position"),zIndex:e.css("z-index")}),t.each(["top","left","bottom","right"],function(t,s){i[s]=e.css(s),isNaN(parseInt(i[s],10))&&(i[s]="auto")}),e.css({position:"relative",top:0,left:0,right:"auto",bottom:"auto"})),e.css(n),s.css(i).show()},removeWrapper:function(e){var i=document.activeElement;return e.parent().is(".ui-effects-wrapper")&&(e.parent().replaceWith(e),(e[0]===i||t.contains(e[0],i))&&t(i).focus()),e},setTransition:function(e,i,s,n){return n=n||{},t.each(i,function(t,i){var o=e.cssUnit(i);o[0]>0&&(n[i]=o[0]*s+o[1])}),n}}),t.fn.extend({effect:function(){function i(e){function i(){t.isFunction(o)&&o.call(n[0]),t.isFunction(e)&&e()}var n=t(this),o=s.complete,r=s.mode;(n.is(":hidden")?"hide"===r:"show"===r)?(n[r](),i()):a.call(n[0],s,i)}var s=e.apply(this,arguments),n=s.mode,o=s.queue,a=t.effects.effect[s.effect]; -return t.fx.off||!a?n?this[n](s.duration,s.complete):this.each(function(){s.complete&&s.complete.call(this)}):o===!1?this.each(i):this.queue(o||"fx",i)},show:function(t){return function(s){if(i(s))return t.apply(this,arguments);var n=e.apply(this,arguments);return n.mode="show",this.effect.call(this,n)}}(t.fn.show),hide:function(t){return function(s){if(i(s))return t.apply(this,arguments);var n=e.apply(this,arguments);return n.mode="hide",this.effect.call(this,n)}}(t.fn.hide),toggle:function(t){return function(s){if(i(s)||"boolean"==typeof s)return t.apply(this,arguments);var n=e.apply(this,arguments);return n.mode="toggle",this.effect.call(this,n)}}(t.fn.toggle),cssUnit:function(e){var i=this.css(e),s=[];return t.each(["em","px","%","pt"],function(t,e){i.indexOf(e)>0&&(s=[parseFloat(i),e])}),s}})}(),function(){var e={};t.each(["Quad","Cubic","Quart","Quint","Expo"],function(t,i){e[i]=function(e){return Math.pow(e,t+2)}}),t.extend(e,{Sine:function(t){return 1-Math.cos(t*Math.PI/2)},Circ:function(t){return 1-Math.sqrt(1-t*t)},Elastic:function(t){return 0===t||1===t?t:-Math.pow(2,8*(t-1))*Math.sin((80*(t-1)-7.5)*Math.PI/15)},Back:function(t){return t*t*(3*t-2)},Bounce:function(t){for(var e,i=4;((e=Math.pow(2,--i))-1)/11>t;);return 1/Math.pow(4,3-i)-7.5625*Math.pow((3*e-2)/22-t,2)}}),t.each(e,function(e,i){t.easing["easeIn"+e]=i,t.easing["easeOut"+e]=function(t){return 1-i(1-t)},t.easing["easeInOut"+e]=function(t){return.5>t?i(2*t)/2:1-i(-2*t+2)/2}})}(),t.effects,t.effects.effect.slide=function(e,i){var s,n=t(this),o=["position","top","bottom","left","right","width","height"],a=t.effects.setMode(n,e.mode||"show"),r="show"===a,l=e.direction||"left",h="up"===l||"down"===l?"top":"left",c="up"===l||"left"===l,u={};t.effects.save(n,o),n.show(),s=e.distance||n["top"===h?"outerHeight":"outerWidth"](!0),t.effects.createWrapper(n).css({overflow:"hidden"}),r&&n.css(h,c?isNaN(s)?"-"+s:-s:s),u[h]=(r?c?"+=":"-=":c?"-=":"+=")+s,n.animate(u,{queue:!1,duration:e.duration,easing:e.easing,complete:function(){"hide"===a&&n.hide(),t.effects.restore(n,o),t.effects.removeWrapper(n),i()}})}}); \ No newline at end of file diff --git a/data/core.telegram.org/js/telegram-passport2.js b/data/core.telegram.org/js/telegram-passport2.js deleted file mode 100644 index 026006ade7..0000000000 --- a/data/core.telegram.org/js/telegram-passport2.js +++ /dev/null @@ -1,413 +0,0 @@ -(function(window) { - if (!Array.isArray) { - Array.isArray = function(arg) { - return Object.prototype.toString.call(arg) === '[object Array]'; - }; - } - if (!Object.isSimpleObject) { - Object.isSimpleObject = function(arg) { - return arg != null && typeof arg === 'object'; - }; - } - function isFunction(func) { - return func && {}.toString.call(func) === '[object Function]'; - } - function getEl(elOrId) { - if (elOrId.nodeType) return elOrId; - return document.getElementById(elOrId); - } - function preventDefault(event) { - if (window.event) { - window.event.returnValue = false; - } - else if (event.preventDefault) { - event.preventDefault(); - } - else { - event.returnValue = false; - } - } - function addEvent(el, event, handler) { - var events = event.split(/\s+/); - for (var i = 0; i < events.length; i++) { - if (el.addEventListener) { - el.addEventListener(events[i], handler, false); - } else { - el.attachEvent('on' + events[i], handler); - } - } - } - - var UA = window.navigator.userAgent || ''; - var ScopeAliases = { - personal_details: 'pd', - passport: 'pp', - driver_license: 'dl', - identity_card: 'ic', - internal_passport: 'ip', - id_document: 'idd', - address: 'ad', - utility_bill: 'ub', - bank_statement: 'bs', - rental_agreement: 'ra', - passport_registration: 'pr', - temporary_registration: 'tr', - address_document: 'add', - phone_number: 'pn', - email: 'em', - }; - - function openDeepLink(url, tooltipToggle) { - var is_ios = /ios|iphone os|iphone|ipod|ipad/i.test(UA); - var is_firefox = /firefox/i.test(UA); - var use_iframe = (is_ios || is_firefox); - var use_once = (!is_ios && is_firefox); - var timeOpen; - var ttNeedHide = false; - var pageShown = true; - var onPageHide = function() { - pageShown = false; - }; - tooltipToggle = tooltipToggle || function(){}; - var onPageShow = function() { - pageShown = true; - if (ttNeedHide && (+(new Date) - timeOpen) > 5000) { - tooltipToggle(false); - } - }; - addEvent(window, 'pagehide', onPageHide); - addEvent(window, 'pageshow', onPageShow); - addEvent(window, 'blur', onPageHide); - addEvent(window, 'focus', onPageShow); - var showTooltip = function() { - tooltipToggle(true); - if (!pageShown) { - ttNeedHide = true; - } - }; - if (use_iframe) { - var iframeEl = document.createElement('iframe'); - iframeEl.style.position = 'absolute'; - iframeEl.style.left = '-10000px'; - iframeEl.style.top = '-10000px'; - document.body.appendChild(iframeEl); - if (iframeEl !== null) { - timeOpen = +(new Date); - iframeEl.src = url; - setTimeout(showTooltip, 2500); - } - if (!use_once) { - setTimeout(function() { - if (pageShown) { - timeOpen = +(new Date); - window.location = url; - } - }, 2000); - } - } - else { - setTimeout(function() { - timeOpen = +(new Date); - window.location = url; - }, 100); - setTimeout(showTooltip, 1500); - } - } - - function packScope(scope) { - if (scope.data) { - scope.d = scope.data; - delete scope.data; - } - if (!scope.d) { - throw new TypeError('scope data is required'); - } - if (!scope.v) { - throw new TypeError('scope version is required'); - } - for (var i = 0; i < scope.d.length; i++) { - scope.d[i] = packScopeField(scope.d[i]); - } - return JSON.stringify(scope); - } - function packScopeField(field) { - if (field.one_of) { - field._ = field.one_of; - delete field.one_of; - } else if (field.type) { - field._ = field.type; - delete field.type; - } - if (Array.isArray(field._)) { - for (var j = 0; j < field._.length; j++) { - field._[j] = packScopeField(field._[j]); - } - field = packScopeOpts(field); - } else if (field._) { - if (ScopeAliases[field._]) { - field._ = ScopeAliases[field._]; - } - field = packScopeOpts(field); - } else if (ScopeAliases[field]) { - field = ScopeAliases[field]; - } - return field; - } - function packScopeOpts(scope) { - if (scope.selfie) { - scope.s = 1; - delete scope.selfie; - } - if (scope.translation) { - scope.t = 1; - delete scope.translation; - } - if (scope.native_names) { - scope.n = 1; - delete scope.native_names; - } - return scope; - } - - function passportAuth(options, tooltipToggle) { - if (!options.bot_id) { - throw new Error('bot_id is required'); - } - if (!options.scope) { - throw new Error('scope is required'); - } - if (!Object.isSimpleObject(options.scope)) { - throw new TypeError('scope should be an object'); - } - if (!options.public_key) { - throw new Error('public_key is required'); - } - if (!options.nonce) { - throw new Error('nonce is required'); - } - if (options.payload) { - throw new Error('payload is deprecated, use nonce instead'); - } - var is_android = /android/i.test(UA); - var url = (is_android ? 'tg:' : 'tg://') + 'resolve?domain=telegrampassport' - + '&bot_id=' + encodeURIComponent(options.bot_id) - + '&scope=' + encodeURIComponent(packScope(options.scope)) - + '&public_key=' + encodeURIComponent(options.public_key) - + '&nonce=' + encodeURIComponent(options.nonce); - if (options.callback_url) { - url += '&callback_url=' + encodeURIComponent(options.callback_url); - } - url += '&payload=nonce'; // legacy for outdated apps - openDeepLink(url, tooltipToggle); - } - - function createAuthButton(contEl, authDataOrFunc, options) { - contEl = getEl(contEl); - if (!contEl) { - return false; - } - options = options || {}; - var btnText = options.text || 'Log In With Telegram'; - var btnRadius = parseInt(options.radius, 10) || 23; - var tooltipText = options.tooltip_text || 'Please install Telegram to use this option.'; - var tooltipForce = options.tooltip_force || false; - var tooltipPos = options.tooltip_position; - if (tooltipPos == 'top') { - var tooltipWrapClass = 'tooltip-top'; - } else if (tooltipPos == 'left') { - var tooltipWrapClass = 'tooltip-left'; - } else if (tooltipPos == 'right') { - var tooltipWrapClass = 'tooltip-right'; - } else { - var tooltipWrapClass = 'tooltip-bottom'; - } - var btnStyle = '' - + '.telegram-passport {' - + 'display: inline-block;' - + 'position: relative;' - + 'max-width: 100%;' - + '}' - + 'button.telegram-passport-button {' - + 'display: inline-block;' - + 'vertical-align: top;' - + 'font-family: "Lucida Grande", Arial, Helvetica, sans-serif;' - + 'font-size: 16px;' - + 'font-weight: 500;' - + 'line-height: 20px;' - + 'text-align: left;' - + 'border-radius: ' + btnRadius + 'px;' - + 'background-color: #54a9eb;' - + 'text-decoration: none;' - + 'padding: 12px 21px 14px;' - + 'margin: 0;' - + 'white-space: nowrap;' - + 'text-overflow: ellipsis;' - + 'overflow: hidden;' - + 'border: none;' - + 'color: #fff;' - + 'cursor: pointer;' - + 'max-width: 100%;' - + '}' - + 'button.telegram-passport-button:focus {' - + 'outline: none;' - + '}' - + '.telegram-passport-tooltip-wrap {' - + 'position: absolute;' - + 'pointer-events: none;' - + 'text-align: center;' - + 'z-index: 100;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom {' - + 'left: -500px;' - + 'right: -500px;' - + 'top: 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top {' - + 'left: -500px;' - + 'right: -500px;' - + 'bottom: 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left {' - + 'right: 100%;' - + 'top: 7px;' - + 'bottom: 7px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right {' - + 'left: 100%;' - + 'top: 7px;' - + 'bottom: 7px;' - + '}' - + '.telegram-passport-tooltip {' - + 'position: relative;' - + 'font-family: "Lucida Grande", Arial, Helvetica, sans-serif;' - + 'background: #949494;' - + 'color: #fff;' - + 'white-space: nowrap;' - + 'border-radius: ' + btnRadius + 'px;' - + 'padding: 7px 16px;' - + 'display: inline-block;' - + 'font-size: 14px;' - + 'line-height: 18px;' - + 'text-decoration: none;' - + 'pointer-events: none;' - + 'visibility: hidden;' - + 'opacity: 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip {' - + 'margin-top: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip {' - + 'margin-bottom: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip {' - + 'margin-right: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip {' - + 'margin-left: 32px;' - + '}' - + '.telegram-passport-tooltip:hover {' - + 'color: #fff;' - + 'text-decoration: none;' - + '}' - + '.telegram-passport-tooltip-shown {' - + 'transition: all .2s ease;' - + 'pointer-events: auto;' - + 'visibility: visible;' - + 'opacity: 1;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip-shown {' - + 'margin-top: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip-shown {' - + 'margin-bottom: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip-shown {' - + 'margin-right: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip-shown {' - + 'margin-left: 16px;' - + '}' - + '.telegram-passport-button-icon {' - + 'display: inline-block;' - + 'vertical-align: top;' - + "background: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADYAAAAsCAYAAAFZD3u2AAAAAXNSR0IArs4c6QAAB+FJREFUaAXVWllsVFUYPndm2qG0Q4EipaWspSJbQRYxDWIUHyBqAgYTjUsTNBqN+qAJLg8+ugTlQeITARNQNERcXlyesAxVhOKSSGhLVyi0dDqdznTWznL9/ts5t2fuNrfTEvFP/p5//89/z52z3TJmArIsOyWtDkKZyxxEgE+SkOBMm5/rxlsSxpPpTFPrEJEqKJ4S4PfOgBSMp1QvkqmMSJCryOto6HuUsFwDwbvkRQDZb0rcLEM2JFRklFP1zJaQ0wm1t+FEmjxzQPUcioyxbPcHcyzsMOhXzhNyaZ1gMAeyYVF+visgskp2CYY0CHNzNGD42GxfWaFVKY4u9D1HQ2NGlkYO2QibdJFIgB5I3/zRLx/xXlUCgM8BQyc7QkQ5YceOerBZTGnpJBr2DkXHOK9zguIcV/JW+2IrTlDu5QZie7bdL1/oCogiorupvzpIpzMpit7ji+h0EBTxTG9yLRkTRuLq75GrlFZXj7fNf4ocMplMjqHI6JxIQE40uGZANurPghgRjjb39YI/IspAv6zhx1lv+/ALR73XJuYHiHlWQ4fpFCLRazwZb6ccH4FKgD/xgFbtpJIh0ENAw5eFksSS6Zs0cCawxTQZHA6aOOWIfaOJGCVoxltuBZRImd5gdAH0ZtPMGsVVf5T1DMUUaUVZ0QyLiYl7vkoETYkz0NJkSa0ptPaH2WAooerXLPSwirJilbcisjM/o2k0DsMSrTE68dZfvcH3Q8JqRzYNK+Ywl9P056INQ/wXXJizSnEhb1ta5KJImX+MeAw+W1sziy2cbfkAuKva8qpIYJmMDM60Dn2ICX8/ree+USUviVljQ03G6ZhYYhWh/k8HktVxcd5kZEhv20BojIUTKSxhLLRv2+JyHgCPeznoTs5rWhom/VquMdKxX52/8YNOqBEg8TtADsc06lvPIvMuYBdw9y3JhsDzgBeBIvRPazJEPiRG19AHppwMAZ8EpjSBjdjqgpIh0lJgh1HEdCYTTiTTOtWkEsHbATyuiyIIWroDcsfNsCCZIG0lg/lLEy7GVCiaDNBv8XogZmwgy17TZPBYDxww8xTlv17xK1uckYi6SxPVnN5DydQZBFI3+K+Bj5AiHwwEE+n2gbCT7LYun83cRQpp6MbnRxeS7ITFj4ZWxsK0t93vxNFEib6tbi5zONQ+G3tkpbSeKRtrS6ussnMwwq4HaEUaBxuLJhnGUNlMImhh+ogIK0hl5DSdL3giKsRmIgr7CY+t1o8Cl0L4LXADV1L7T1+IDUeSqsjtcrCttXQwsg2VqEw5n6nJRFckrh1LpU+c6xy5R5TPKnGxDROri6gypfnLQQaGybgn/XY4XTXbzeoqyzhruxWTWW4mYKgma+kJ2k4gGDYJtPlGn4wk5ribG8eSGXb07DUW1myAuN6kPSjKLR8jGfJH2eGLqn53LSjFLkt3IFb1nBAfIcksH6PiJEkj3Jm3SFwDupTzdtu8yTIOtk4M5nI6NzY2LLqOXkezPT8v6gU6ItAKmTfZA3UVfdxJcjh3NzYs/JPz1CLhVjS7RFmWzhkvA72xyHvZt+mz5qvmpxC44bdJ6516ujWO9D+VorC1wAPAG0AtdN/2ZaHHxcA9wO+Algs09BzO3laFoVfVwP3AS7yHBbaP/WeFocPbgIeBwQI7b+bWQ0Xp7ianu1Jk9yDmXmAjcDsw78QPGw7pgeDYSOdguKIap91ldyjbGK4za5VZazJJzAKpchSxEgwV8AyQFoVCINHti2WuDUeV+4QlFSVsyTxbBVEu2vXNwlSdLGjEUAD50baWingUSPvoggG3jLGOwah7IBin9cdNF/2rqz1snsfeDYuQ+BAVRXzeEUMR82H3FJCKWA+cFsA3jVhbf7hE3IwWYzO6rsbDSt0FPW/qVzUKU87RORFQBK22VMATwEltd2GfF+LJTKK1f9QdiikXrerVFW166Q6saHLXU9p8X/KiSEGHl9fRfqy1mi5+NJ5KY2Sc0TH9/U5VuZutqCyl7ct0pNuMOBd5IBqxnCMDV0ylDUSTcnt/WEqkMhRGdxCtQzFVk7zTy9OfM2JRZKs+KowcfSB6Gkiv4b3ASQFdrdJxFPcehn4uHBvX4PdTXjL+ccPQqHDhbhT2veiuFiYKRRoFrwD/eBbVkwx4uuuQenDIMKlFCTOz2KlMCFY3CIph4X+6UFSt1j1vYVoH4k93d89wJDzj1+tGBpDRZfiqqjLbNxUmYeyIX0Fhn2oNCyqMgjRd9jdg6mnWBqSLii3LrO94tD5T4OlMWo7ClGlWjFNwYRTklzbfYUmWnhcD0ux3Izj+KaMev6mNS8qZY3pmPTENpz9AUW9zRmynVNjJkyedC+p3RGUmq1uEUDzNBkcnvtFQsmL8mwJdoC21vzUS+2hFz0dhPiODKRVGAZs6g3UsmWznwUeiSTYkXG1xObUYuEsP11e9ON/jOgx2lagrgD6Oop4188t7N2DmyOX315ZfcUoO9XXAtY8O0IFBR5F0J77YrK2cVdQMfjWQHiotLSGdgz2B5d3DlEeM+oAlQfK2DffglVzcN5Jg+OcWpWsIHmdOaee+hkVNVn2FPy1u7wHfANrp02k8lwetYtoJYuWv6n7+e6C0pNjV3zEU9eCGOc0kx77n7qs5phrYJFDkAph+Dtxh4kJPrRaF9Zrob38xiqwHngLSf3TQh3X6YGXr++q/M6e7wZMmuzIAAAAASUVORK5CYII=') no-repeat;" - + 'background-size: 27px 22px;' - + 'width: 27px;' - + 'height: 22px;' - + 'margin: 0 15px -2px -5px;' - + '}' - + '.telegram-passport-tooltip:before {' - + "content: '';" - + 'display: inline-block;' - + 'position: absolute;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip:before {' - + 'left: 50%;' - + 'top: 0;' - + 'border: 10px solid;' - + 'border-radius: 4px 0 0;' - + 'border-color: #949494 transparent transparent #949494;' - + 'transform: rotateZ(45deg) translate3d(-3px,5px,0);' - + 'transform-origin: 100% 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip:before {' - + 'left: 50%;' - + 'bottom: 0;' - + 'border: 10px solid;' - + 'border-radius: 0 0 4px;' - + 'border-color: transparent #949494 #949494 transparent;' - + 'transform: rotateZ(45deg) translate3d(-11px,9px,0);' - + 'transform-origin: 0 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip:before {' - + 'top: 50%;' - + 'right: 0;' - + 'border: 8px solid;' - + 'border-radius: 0 2px 0 0;' - + 'border-color: #949494 #949494 transparent transparent;' - + 'transform: rotateZ(45deg) translate3d(4px,-3.5px,0);' - + 'transform-origin: 100% 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip:before {' - + 'top: 50%;' - + 'left: 0;' - + 'border: 8px solid;' - + 'border-radius: 0 0 0 2px;' - + 'border-color: transparent transparent #949494 #949494;' - + 'transform: rotateZ(45deg) translate3d(-15px,-7.5px,0);' - + 'transform-origin: 0 100%;' - + '}'; - var tooltipClass = tooltipForce ? 'telegram-passport-tooltip telegram-passport-tooltip-shown' : 'telegram-passport-tooltip'; - var btnHtml = '' - + '' - + '
    ' + tooltipText + '
    ' - + ''; - var btnContEl = document.createElement('div'); - btnContEl.className = 'telegram-passport'; - btnContEl.innerHTML = btnHtml; - contEl.appendChild(btnContEl); - var buttonEl = btnContEl.getElementsByTagName('button')[0]; - var tooltipEl = btnContEl.getElementsByTagName('a')[0]; - addEvent(buttonEl, 'click', function(e) { - preventDefault(e); - var options = isFunction(authDataOrFunc) ? authDataOrFunc() : authDataOrFunc; - options = options || {}; - var tooltipToggle = function(show) { - if (show) { - tooltipEl.classList.add('telegram-passport-tooltip-shown'); - } else { - tooltipEl.classList.remove('telegram-passport-tooltip-shown'); - } - }; - passportAuth(options, !tooltipForce ? tooltipToggle : null); - }); - } - - if (!window.Telegram) { - window.Telegram = {}; - } - window.Telegram.Passport = { - auth: passportAuth, - createAuthButton: createAuthButton, - }; -})(window); diff --git a/data/core.telegram.org/method/messages.searchGifs b/data/core.telegram.org/method/account.verifyPhone similarity index 77% rename from data/core.telegram.org/method/messages.searchGifs rename to data/core.telegram.org/method/account.verifyPhone index 161693bb23..e2c406a197 100644 --- a/data/core.telegram.org/method/messages.searchGifs +++ b/data/core.telegram.org/method/account.verifyPhone @@ -2,12 +2,12 @@ - messages.searchGifs + account.verifyPhone - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.searchGifs

    +
    +

    account.verifyPhone

    -

    Search for GIFs

    +

    Verify a phone number for telegram passport.

    • @@ -52,7 +52,10 @@
    -
     Method schema is available as of layer 114. Switch »

    +
    boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;

    Parameters

    @@ -64,19 +67,24 @@ - + - + - - - + + + + + + + +
    qphone_number stringText queryPhone number
    offsetintOffset for pagination »phone_code_hashstringPhone code hash received from the call to account.sendVerifyPhoneCode
    phone_codestringCode received after the call to account.sendVerifyPhoneCode

    Result

    -

    messages.FoundGifs

    +

    Bool

    Possible errors

    @@ -89,19 +97,25 @@ - - + + - - + + + + + + +
    400METHOD_INVALIDThe specified method is invalid.PHONE_CODE_EMPTYphone_code is missing.
    400SEARCH_QUERY_EMPTYThe search query is empty.PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
    400PHONE_NUMBER_INVALIDThe phone number is invalid.

    Related pages

    -

    Pagination in the API

    -

    How to fetch results from large lists of objects.

    +

    account.sendVerifyPhoneCode

    +

    Send the verification phone code for telegram passport.

    +

    Telegram Passport Manual

    diff --git a/data/core.telegram.org/method/messages.editChatTitle b/data/core.telegram.org/method/messages.editMessage similarity index 66% rename from data/core.telegram.org/method/messages.editChatTitle rename to data/core.telegram.org/method/messages.editMessage index 1cd755c064..136fbdb7ab 100644 --- a/data/core.telegram.org/method/messages.editChatTitle +++ b/data/core.telegram.org/method/messages.editMessage @@ -2,12 +2,12 @@ - messages.editChatTitle + messages.editMessage - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.editChatTitle

    +
    +

    messages.editMessage

    -

    Chanages chat name and sends a service message on it.

    +

    Edit message

    • @@ -60,7 +60,7 @@ 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;

      +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;

      Parameters

      @@ -72,19 +72,54 @@ - - - + + + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      chat_idlongChat IDflags#Flags, see TL conditional fields
      titlestringNew chat name, different from the old oneno_webpageflags.1?trueDisable webpage preview
      peerInputPeerWhere was the message sent
      idintID of the message to edit
      messageflags.11?stringNew message
      mediaflags.14?InputMediaNew attached media
      reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
      entitiesflags.3?Vector<MessageEntity>Message entities for styled text
      schedule_dateflags.15?intScheduled message date for scheduled messages

      Result

      -

      Returns a messages.StatedMessage object containing a service message sent during an action.

      +

      Updates

      Possible errors

      @@ -97,27 +132,137 @@ - - + + - - + + - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      400CHAT_ID_INVALIDThe provided chat id is invalid.BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
      400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
      400CHAT_TITLE_EMPTYNo chat title provided.BUTTON_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.
      403CHAT_WRITE_FORBIDDENYou can't write in this chat.
      400ENTITIES_TOO_LONGYou provided too many styled message entities.
      403INLINE_BOT_REQUIREDOnly the inline bot can edit message.
      400INPUT_USER_DEACTIVATEDThe specified user was deleted.
      400MEDIA_CAPTION_TOO_LONGThe caption is too long.
      400MEDIA_GROUPED_INVALIDYou tried to send media of different types in an album.
      400MEDIA_NEW_INVALIDThe new media is invalid.
      400MEDIA_PREV_INVALIDPrevious media invalid.
      403MESSAGE_AUTHOR_REQUIREDMessage author required.
      400MESSAGE_EDIT_TIME_EXPIREDYou can't edit this message anymore, too much time has passed since its creation.
      400MESSAGE_EMPTYThe provided message is empty.
      400MESSAGE_ID_INVALIDThe provided message id is invalid.
      400MESSAGE_NOT_MODIFIEDThe message text has not changed.
      400MESSAGE_TOO_LONGThe provided message is too long.
      400MSG_ID_INVALIDInvalid message ID provided.
      400 PEER_ID_INVALID The provided peer id is invalid.
      400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
      400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
      400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
      -

      Bots can use this method

    +

    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/core.telegram.org/method/messages.clearAllDrafts b/data/core.telegram.org/method/messages.getDialogFilters similarity index 88% rename from data/core.telegram.org/method/messages.clearAllDrafts rename to data/core.telegram.org/method/messages.getDialogFilters index ee8ead09eb..cd4956007c 100644 --- a/data/core.telegram.org/method/messages.clearAllDrafts +++ b/data/core.telegram.org/method/messages.getDialogFilters @@ -2,12 +2,12 @@ - messages.clearAllDrafts + messages.getDialogFilters - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.clearAllDrafts

    +
    +

    messages.getDialogFilters

    -

    Clear all drafts.

    +

    Get folders

    • @@ -52,17 +52,15 @@
    -
    boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.clearAllDrafts#7e58ee9c = Bool;

    +
    ---functions---
+messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

    Parameters

    This constructor does not require any parameters.

    Result

    -

    Bool

    +

    Vector<DialogFilter>

    Related pages

    -

    Message drafts

    -

    How to handle message drafts

    +

    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.getHistory b/data/core.telegram.org/method/messages.getHistory deleted file mode 100644 index 6636a694f7..0000000000 --- a/data/core.telegram.org/method/messages.getHistory +++ /dev/null @@ -1,232 +0,0 @@ - - - - - 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
    401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
    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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/account.resetAuthorization b/data/core.telegram.org/method/messages.readDiscussion similarity index 84% rename from data/corefork.telegram.org/method/account.resetAuthorization rename to data/core.telegram.org/method/messages.readDiscussion index 482cdec4e1..48f929fe42 100644 --- a/data/corefork.telegram.org/method/account.resetAuthorization +++ b/data/core.telegram.org/method/messages.readDiscussion @@ -2,12 +2,12 @@ - account.resetAuthorization + messages.readDiscussion - - + + - + @@ -36,10 +36,10 @@
    -
    -

    account.resetAuthorization

    +
    +

    messages.readDiscussion

    -

    Log out an active authorized session by its hash

    +

    Mark a thread as read

    • @@ -55,7 +55,7 @@ 
      boolFalse#bc799737 = Bool;
 boolTrue#997275b5 = Bool;
 ---functions---
-account.resetAuthorization#df77f3bc hash:long = Bool;

      +messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;

      Parameters

      @@ -67,9 +67,19 @@ - - - + + + + + + + + + + + + +
      hashlongSession hashpeerInputPeerGroup ID
      msg_idintID of message that started the thread
      read_max_idintID up to which thread messages were read
      @@ -86,20 +96,15 @@ -406 -FRESH_RESET_AUTHORISATION_FORBIDDEN -You can't logout other sessions if less than 24 hours have passed since you logged on the current session. - - 400 -HASH_INVALID -The provided hash is invalid. +PEER_ID_INVALID +The provided peer id is invalid.

      Related pages

      -

      User Authorization

      -

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

    +

    Threads

    +

    Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

    @@ -138,9 +143,9 @@
    -
    Platform
    +
    Platform
    @@ -157,7 +162,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/method/langpack.getLanguages b/data/core.telegram.org/method/messages.uninstallStickerSet similarity index 86% rename from data/corefork.telegram.org/method/langpack.getLanguages rename to data/core.telegram.org/method/messages.uninstallStickerSet index 5269447176..915b78790f 100644 --- a/data/corefork.telegram.org/method/langpack.getLanguages +++ b/data/core.telegram.org/method/messages.uninstallStickerSet @@ -2,12 +2,12 @@ - langpack.getLanguages + messages.uninstallStickerSet - - + + - + @@ -36,10 +36,10 @@
    -
    -

    langpack.getLanguages

    +
    +

    messages.uninstallStickerSet

    -

    Get information about all languages in a localization pack

    +

    Uninstall a stickerset

    • @@ -52,8 +52,10 @@
    -
    ---functions---
-langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;

    +
    boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+---functions---
+messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

    Parameters

    @@ -65,14 +67,14 @@ - - - + + +
    lang_packstringLanguage packstickersetInputStickerSetThe stickerset to uninstall

    Result

    -

    Vector<LangPackLanguage>

    +

    Bool

    Possible errors

    @@ -85,8 +87,8 @@ - - + +
    400LANG_PACK_INVALIDThe provided language pack is invalid.STICKERSET_INVALIDThe provided sticker set is invalid.
    @@ -128,9 +130,9 @@
    -
    Platform
    +
    Platform
    @@ -147,7 +149,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/core.telegram.org/method/payments.clearSavedInfo b/data/core.telegram.org/method/payments.clearSavedInfo deleted file mode 100644 index efb91efb38..0000000000 --- a/data/core.telegram.org/method/payments.clearSavedInfo +++ /dev/null @@ -1,160 +0,0 @@ - - - - - payments.clearSavedInfo - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    payments.clearSavedInfo

    - -

    Clear saved payment information

    -

    - -
    -
    boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    flags#Flags, see TL conditional fields
    credentialsflags.0?trueRemove saved payment credentials
    infoflags.1?trueClear the last order settings saved by the user
    -

    Result

    -

    Bool

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/method/messages.getDiscussionMessage b/data/core.telegram.org/method/stats.getMegagroupStats similarity index 72% rename from data/core.telegram.org/method/messages.getDiscussionMessage rename to data/core.telegram.org/method/stats.getMegagroupStats index cf281a5b58..ddc3e8eefd 100644 --- a/data/core.telegram.org/method/messages.getDiscussionMessage +++ b/data/core.telegram.org/method/stats.getMegagroupStats @@ -2,12 +2,12 @@ - messages.getDiscussionMessage + stats.getMegagroupStats - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.getDiscussionMessage

    +
    +

    stats.getMegagroupStats

    -

    Get discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group

    +

    Get supergroup statistics

    • @@ -52,9 +52,9 @@
    -
    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;
+
    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---
-messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;
    
+stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

    Parameters

    @@ -66,19 +66,24 @@ - - - + + + - - - + + + + + + + +
    peerInputPeerChannel IDflags#Flags, see TL conditional fields
    msg_idintMessage IDdarkflags.0?trueWhether to enable dark theme for graph colors
    channelInputChannelSupergroup ID

    Result

    -

    messages.DiscussionMessage

    +

    stats.MegagroupStats

    Possible errors

    @@ -91,23 +96,26 @@ - - + + - - + + + + + + +
    400MSG_ID_INVALIDInvalid message ID provided.CHANNEL_INVALIDThe provided channel is invalid.
    400PEER_ID_INVALIDThe provided peer id is invalid.CHAT_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.

    -

    Threads

    -

    Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

    -

    Discussion groups

    -

    Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

    +

    Channel statistics

    +

    Telegram offers detailed channel statistics for channels and supergroups.

    diff --git a/data/core.telegram.org/method/stats.getMessagePublicForwards b/data/core.telegram.org/method/stats.getMessagePublicForwards deleted file mode 100644 index 9fcd2812f4..0000000000 --- a/data/core.telegram.org/method/stats.getMessagePublicForwards +++ /dev/null @@ -1,212 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/mtproto.html b/data/core.telegram.org/mtproto.html new file mode 100644 index 0000000000..fc52d378d4 --- /dev/null +++ b/data/core.telegram.org/mtproto.html @@ -0,0 +1,260 @@ + + + + + MTProto Mobile Protocol + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    MTProto Mobile Protocol

    + +
    + +
    +

    Please feel free to check out our FAQ for the Technically Inclined. +Client developers are required to comply with the Security Guidelines.

    +
    +

    Related articles

    +

    + +

    +
    +

    This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

    + +

    General Description

    +

    The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

    +

    The protocol is subdivided into three virtually independent components:

    +
      +
    • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
      • +
    • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
      • +
    • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as HTTP, HTTPS, WS (plain websockets), WSS (websockets over HTTPS), TCP, UDP).
      • +
    + +
    +

    As of version 4.6, major Telegram clients are using MTProto 2.0, described in this article. +MTProto v1.0 (described here for reference) is deprecated and is currently being phased out.

    +
    +

    Brief Component Summary

    +

    High-Level Component (RPC Query Language/API)

    +

    From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific websocket/http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

    +

    Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

    +

    There are several types of messages:

    +
      +
    • RPC calls (client to server): calls to API methods
      • +
    • RPC responses (server to client): results of RPC calls
      • +
    • Message received acknowledgment (or rather, notification of status of a set of messages)
      • +
    • Message status query
      • +
    • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
      • +
    +

    From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

    +

    Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

    +

    A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

    +

    All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is how the OpenSSL library does it.

    +

    Authorization and Encryption

    +

    Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 middle bits of the SHA256 of the message body (including session, message ID, etc.), including the padding bytes, prepended by 32 bytes taken from the authorization key. Multipart messages are encrypted as a single message.

    +
    +

    For a technical specification, see Mobile Protocol: Detailed Description

    +
    +

    The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

    +

    The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

    +
      +
    • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
      • +
    • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
      • +
    • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to that data.
      • +
    +

    Time Synchronization

    +

    If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

    +

    Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

    +

    Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

    +

    MTProto transport

    +

    Before being sent using the selected transport protocol, the payload has to be wrapped in a secondary protocol header, defined by the appropriate MTProto transport protocol.

    + +

    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.

    +

    Transport

    +

    Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. +Multiple transport protocols are defined:

    + +

    (We shall examine only the first five types.)

    +

    Recap

    +

    To recap, using the ISO/OSI stack as comparison:

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + 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. +
    2. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
      3. +
    3. serialize the head of the list (hd) as a value of type X;
      4. +
    4. serialize the tail of the list as a value of the polymorphic type List X.
      5. +
    +

    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
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/mtproto/TL-types.html b/data/core.telegram.org/mtproto/TL-types.html new file mode 100644 index 0000000000..37ec9451ae --- /dev/null +++ b/data/core.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.*
      • +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/mtproto/description_v1.html b/data/core.telegram.org/mtproto/description_v1.html new file mode 100644 index 0000000000..73c7fb0de0 --- /dev/null +++ b/data/core.telegram.org/mtproto/description_v1.html @@ -0,0 +1,205 @@ + + + + + Mobile Protocol: Detailed Description (v.1.0, DEPRECATED) + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Mobile Protocol: Detailed Description (v.1.0, DEPRECATED)

    + +
    +

    This document describes MTProto v.1.0, its status is DEPRECATED. +For information on encryption used in up-to-date Telegram clients, kindly see this document.

    +
    +

    Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key.

    +

    A user key together with the message key define an actual 256-bit key and a 256-bit initialization vector, which is what encrypts the message using AES-256 encryption with infinite garble extension (IGE). Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.) Multipart messages are encrypted as a single message.

    + +

    Terminology

    +

    Authorization Key

    +

    a 2048-bit key shared by the client device and the server, created upon user registration directly on the client device be exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

    +

    Server Key

    +

    a 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

    +

    Key Identifier

    +

    The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key based on a Diffie-Hellman exchange.

    +

    Session

    +

    a (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

    +

    Server Salt

    +

    a (random) 64-bit number periodically (say, every 24 hours) changed (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 300 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

    +

    Message Identifier (msg_id)

    +

    a (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

    +

    Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created. At some point in the nearest future the server will start ignoring messages, in which the lower 32 bits of msg_id contain too many zeroes.

    +

    Content-related Message

    +

    A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

    +

    Message Sequence Number (msg_seqno)

    +

    a 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

    +

    Message Key

    +

    The lower-order 128 bits of the SHA1 hash of the part of the message to be encrypted (including the internal header and excluding the alignment bytes).

    +

    Internal (cryptographic) Header

    +

    A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

    +

    External (cryptographic) Header

    +

    A header (24 bytes) added before an encrypted message or a container. Consists of a key identifier (64 bits) and a message key (128 bits).

    +

    Payload

    +

    External header + encrypted message or container.

    +

    Defining AES Key and Initialization Vector

    +

    The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header which is added later) with AES-256 in infinite garble extension (IGE) mode.

    +

    The algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows:

    +
      +
    • msg_key = substr (SHA1 (plaintext), 4, 16);
      • +
    • sha1_a = SHA1 (msg_key + substr (auth_key, x, 32));
      • +
    • sha1_b = SHA1 (substr (auth_key, 32+x, 16) + msg_key + substr (auth_key, 48+x, 16));
      • +
    • sha1_с = SHA1 (substr (auth_key, 64+x, 32) + msg_key);
      • +
    • sha1_d = SHA1 (msg_key + substr (auth_key, 96+x, 32));
      • +
    • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
      • +
    • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
      • +
    +

    where x = 0 for messages from client to server and x = 8 for those from server to client.

    +

    The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

    +

    When AES is used to encrypt a block of data of a length not divisible by 16 bytes, the data is padded with random bytes to the smallest length divisible by 16 bytes immediately prior to being encrypted.

    +

    Important Tests

    +

    When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 lower-order bits of the SHA1 hash of the previously encrypted portion, and 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 msg_id lower than all or equal to any of the stored values, the 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 forgotten.

    +

    In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. 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 of invalid client time. See Mobile Protocol: Service Messages.

    +

    Storing an Authorization Key on a Client Device

    +

    It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This is accomplished by adding the SHA1 of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by being compared with SHA1. From the user’s standpoint, this is practically the same as using an application or a website password.

    +

    Unencrypted Messages

    +

    Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

    +

    Only a very limited number of messages of special types can be transmitted as plain text.

    +

    Schematic Presentation of Messages

    +

    Encrypted Message

    + + + + +
    auth_key_id
    int64    		msg_key
    int128    		encrypted_data
    bytes
    +

    Encrypted Message: encrypted_data

    +

    Contains the cypher text for the following data:

    + + + + + + + + +
    salt
    int64    		session_id
    int64    		message_id
    int64    		seq_no
    int32    		message_data_length
    int32    		message_data
    bytes    		padding 0..15
    bytes
    +

    Unencrypted Message

    + + + + + +
    auth_key_id = 0
    int64    		message_id
    int64    		message_data_length
    int32    		message_data
    bytes
    +

    Creating an Authorization Key

    +

    An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

    +

    See Creating an Authorization Key.

    +

    During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/mtproto/serialize.html b/data/core.telegram.org/mtproto/serialize.html new file mode 100644 index 0000000000..e014d3aa7c --- /dev/null +++ b/data/core.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

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/passport/example.html b/data/core.telegram.org/passport/example.html deleted file mode 100644 index 68d5d0c84e..0000000000 --- a/data/core.telegram.org/passport/example.html +++ /dev/null @@ -1,585 +0,0 @@ - - - - - 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.

    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - - - - diff --git a/data/core.telegram.org/reproducible-builds.html b/data/core.telegram.org/reproducible-builds.html new file mode 100644 index 0000000000..d0f23db600 --- /dev/null +++ b/data/core.telegram.org/reproducible-builds.html @@ -0,0 +1,488 @@ + + + + + Reproducible Builds for iOS and Android + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Reproducible Builds for iOS and Android

    + +

    This page contains instructions for verifying that Telegram's open source code is exactly the same as the code that is used to build the apps that are available in the App Store, Google Play and directly on the Telegram website.

    +

    Warning: Telegram supports reproducible builds as of version 5.13. Bear in mind that, at this stage, the verification process should be considered experimental. We will be updating our apps and these instructions to make this process as straightforward as possible.

    + +
    +

    Please read the relevant notes and troubleshooting section carefully.

    +
    +
    +
    + Dude in a jacket inspecting the hologram of a mechanical dog to verify it's built according to the blueprints provided. +
    + +

    Reproducible Builds for Android

    +

    Step 1. Install Docker

    +

    Docker can be obtained here. Once the installation is complete, log into your Docker account > Preferences > Advanced and configure the amount of resources Docker may use:

    +
    + +

    Docker Performance

    +
    + +

    We recommend using the maximum amount allowed by your system's hardware, in order to speed up the build time.

    +

    Step 2. Confirm which version you have installed on your Android device

    +

    You can find the version/build number at the bottom of the Settings page. Note that Telegram supports reproducible builds starting with version 5.13.

    +
    + +

    App Version

    +
    + +

    The commit tag to checkout source code for the example above will be release-5.13.0_1821.

    +
    +

    Please make sure that you're using the correct version and build number of the version you want to check (and not the one from this example 😈).

    +
    +

    The part after the version number will help you know in which folder to look for the correct APK when you've finished building the app (Step 4):

    +
      +
    • “Direct” after version number means that the APK will be inside the “afat/standalone” folder.
      • +
    • “Universal” after version number means that the APK will be inside the “afat/release” folder.
      • +
    • If you have Android Version 6.0 or greater, your APK folder will have the “_SDK23” suffix.
      • +
    • “arm64-v8a” - folder name will start with “arm64”.
      • +
    • “armeabi-v7” - folder name will start with “armv7”.
      • +
    • “x86” - folder name will start with “x86”.
      • +
    • “x86_64” - folder name will start with “x64”.
      • +
    +
    + +

    APK Folders

    +
    + + +

    Step 3. Obtain the source code

    +

    Open Terminal, run the commands:
    git clone https://github.com/DrKLO/Telegram.git $HOME/telegram-android
    cd $HOME/telegram-android
    git checkout release-{VERSION AND BUILD NUMBER FROM STEP 2}

    +

    For our example, the command would be:
    git checkout release-5.13.0_1821

    +
    + +
    + +

    Step 4. Build the app

    +

    Open Terminal, run the commands:
    cd $HOME/telegram-android
    docker build -t telegram-build .

    +
    + +
    + +

    docker run --rm -v "$PWD":/home/source telegram-build

    +
    + +
    + +

    These commands will produce 9 different APKs for different target SDK versions and CPU ABIs.

    +

    These APKs can be found in:
    $HOME/telegram-android/TMessagesProj/build/outputs/apk/

    +

    Use the folder name from Step 2 to find the correct folder that holds the same APK as installed on your device. For example, for non-universal Android 9.0 arm64-v8a, the path to your APK will be:
    $HOME/telegram-android/TMessagesProj/build/outputs/apk/arm64_SDK23/release/app.apk
    Copy this APK to the root source directory by running this command in Terminal:
    cp $HOME/telegram-android/TMessagesProj/build/outputs/apk/arm64_SDK23/release/app.apk $HOME/telegram-android/telegram_built.apk

    +
    + +
    + +

    Step 5. The Telegram APK installed on your device

    +

    You will need adb for this step.

    +
    + +

    ADB

    +
    + +
    +

    If you downloaded your APK directly from Telegram's website, use the package name org.telegram.messenger.web in this step. To verify the Google Play APK, use org.telegram.messenger.

    +
    +

    Connect your device to the computer, open Terminal, run the commands:
    adb shell pm path org.telegram.messenger

    +
    + +
    + +

    The output will look something like this:
    package:/data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk
    By using this information, pull the APK from your device to $HOME/telegram-android using command:
    adb pull /data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk $HOME/telegram-android/telegram_store.apk

    +

    Step 6. Compare the APKs

    +

    Open Terminal, run the commands:
    cd $HOME/telegram-android
    python apkdiff.py telegram_store.apk telegram_built.apk
    If the APKs are the same, you will see
    APKs are the same!

    +
    + +
    +Tada! + +Otherwise, something went wrong. +
    + +
    + +

    If your APKs don't match, please make sure that you chose the correct code version and the right SDK.

    +

    Check out the Troubleshooting section first in case you run into trouble.

    +
    +

    Reproducible Builds for iOS

    +

    The verification process for iOS builds is, unfortunately, a lot more complex than for Android. The two main issues with Apple's current policies and infrastructure are as follows:

    +
      +

    1. Apple insists on using FairPlay encryption to “protect” even free apps from “app pirates” which makes obtaining the executable code of apps impossible without a jailbroken device. To solve this issue, Apple would simply need to allow submitting unencryptable binaries to the App Store. This would not affect security since the code would still be signed – and would enable anyone to check the integrity of apps supporting reproducible builds without endangering the integrity and security of their devices.

      +
      2. +

    2. Building your own reproducible binaries is difficult because macOS doesn't support containers like Docker. If Apple followed in the footsteps of Linux (and even Microsoft!) and added container support, it would eliminate the need for steps 1-3 in the guide below.

      +
      3. +
    +
    +

    As things stand now, you'll need a jailbroken device, at least 1,5 hours and approximately 90GB of free space to properly set up a virtual machine for the verification process.

    +
    +

    To provide a stable and easily reproducible environment, Telegram iOS builds are compiled on a virtual machine. Parallels is used to verify the builds.

    +

    Step 1. Install the Parallels virtual machine

    +

    Parallels can be obtained here, it features a fully-functional trial version.

    +

    Step 2. Install the latest version of macOS Big Sur

    +

    To download an image that can be installed on the virtual machine, open the App Store, search for “Catalina” and click “View”.

    +
    + +

    Search for macOS Catalina on App Store > View

    +
    + +
    + +

    macOS Catalina > Get +

    +
    + +

    This will open a system pop-up offering to download the OS:

    +
    + +
    +Choose “Download” and wait for the download to finish. + +> If you were not using the latest version of the OS, your system may start updating instead. Please finish updating to download macOS Catalina. + +When done, open Parallels and choose macOS Catalina: + +
    + +

    Select 'Install Windows or another OS' > Continue

    +
    + +
    + +

    Select a file... > Applications (All files) > Install macOS Сatalina

    +
    + +

    Before starting the installation, configure the virtual machine:

    +
    + +

    Checkbox 'Customize settings before installation'

    +
    + +

    Change the name of the virtual machine to macos11_Xcode12_5_1

    +
    + +

    Name VM as macos10_15_Xcode12_2

    +
    + +

    Hardware > Processors: 2-4
    Memory > 4GB may suffice but 8GB is recommended

    +
    + +

    At least 2 CPUs + 4 (8 recommended) GB Memory.

    +
    + +

    You will get something like this:

    +
    + +

    Click Continue

    +
    + +

    Parallels may request access to your microphone and camera, this is not required – just press Close.

    +
    + +

    Install macOS > Continue

    +
    + +

    Your Apple ID is also not required, you can choose Set Up Later.

    +
    + +

    Skip Apple ID with 'Set Up Later'

    +
    + +

    Use “telegram” for both the account name and password.

    +
    +

    Do not ever use the password “telegram” for anything else, it's cursed.

    +
    +
    + +

    Create a computer account with 'telegram' set both as account name and password

    +
    + +

    Now install Parallels tools from the menu bar:

    +
    + + +

    Install Parallels Tools using menu bar > Parallels icon > Actions > Install (Reinstall) Parallels Tools...

    +
    + +

    After the system restarts, log in.
    Open Terminal and run:
    sudo visudo
    Enter the password “telegram”

    +
    + +
    + +

    Find this line at the end of the file:
    %admin ALL=(ALL) ALL
    Press “i” on your keyboard, add “NOPASSWD:”
    %admin ALL=(ALL) NOPASSWD: ALL
    Press Escape.
    Type in “:wq”
    Press Enter

    +
    + +

    Press i to edit the highlighted string.

    + +

    Enter :wq > press Enter.

    +
    + +

    In the terminal, run:
    sudo systemsetup -setcomputersleep Never

    +
    + +

    sudo systemsetup -setcomputersleep Never > press Enter.

    +
    + +

    Step 3. Install SSH keys on the virtual machine

    +

    In the virtual machine, open System Settings > Sharing and enable Remote Login.

    +
    + +
    + +

    In the virtual machine, open Terminal and run:
    mkdir -p .ssh; nano .ssh/authorized_keys

    +
    + +
    + +

    In your main OS, open Terminal and run:
    if [ ! -e ~/.ssh/id_rsa.pub ]; then ssh-keygen -t rsa -b 4096; fi && cat ~/.ssh/id_rsa.pub | pbcopy

    +
    + +
    + +

    If you see the line “Enter file in which to save the key (/Users/…/.ssh/id_rsa):”, press Enter
    In the virtual machine, press CMD+V
    Then Ctrl+O, Ctrl+X

    +
    + +
    + +

    Step 4. Install Xcode version 12.5.1

    +

    In the virtual machine, open Safari and go to https://developer.apple.com
    Sign in to your Account:

    +
    + +

    developer.apple.com > Account > sign in with your Apple ID

    +
    + +

    Go to Downloads > More
    Enter Xcode in the search field and find the version 12.5.1

    +
    + +

    Downloads > More > Xcode 12.5.1

    +
    + +

    Once the installation is complete, open the file Xcode 12.5.1.xip. The system will unarchive the app into the same folder. Move it to the Applications folder using Finder.

    +
    + +

    Unarchive Xcode > drag the app to Applications folder

    +
    + +
    + +
    + +

    On the virtual machine, run this command from the terminal:
    sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

    +
    + +
    + +

    Shut down the virtual machine.

    +
    + +

    Shut down the virtual machine

    +
    + +

    Step 4.1

    +

    Download the certificates at https://github.com/TelegramMessenger/Telegram-iOS/tree/master/build-system/fake-codesigning/certs/distribution and install them into the virtual machine.

    +

    Launch Keychain Access and double-click the installed certificate. Under “Trust”, change “When using this certificate” to “Always Trust”.

    +

    Step 5. Obtaining the source code

    +

    git clone --recursive https://github.com/TelegramMessenger/telegram-ios.git $HOME/telegram-ios
    cd $HOME/telegram-ios
    git checkout release-${VERSION_NUMBER}

    +

    E.g., git checkout release-7.3. Please note that you need to check out the whole git history as the build version depends on the number of commits in the repository.

    +
    + +
    + +

    Step 6. Downloading Bazel 3.7.0 to $HOME/bazel/bazel

    +

    mkdir -p $HOME/bazel && cd $HOME/bazel
    curl -O -L https://github.com/bazelbuild/bazel/releases/download/3.7.0/bazel-3.7.0-darwin-x86_64
    mv bazel-3.7.0-darwin-x86_64 bazel

    +

    Check that you have downloaded the correct version:
    chmod +x bazel
    ./bazel --version

    +

    Step 7. Building the app

    +

    Open Terminal, run the commands:
    cd $HOME/telegram-ios +BAZEL="$HOME/bazel/bazel" sh buildbox/build-telegram.sh verify

    +
    + +
    + +

    If the environment has been set up correctly, this will start the building process. Note that this step can easily take 30-40 minutes. The average build time on a MacBook Pro (i9 6 core) is 35 minutes.

    +
    + + +
    + +

    Once the process is complete the resulting IPA file can be found in build/artifacts/Telegram.ipa
    All the following steps will be made via Terminal on your main system.

    +

    Step 8. Downloading a decrypted version of the app from the App Store

    +

    This step requires a jailbroken device equipped with tools for decrypting apps. We‘d love to make this process more simple but that’s what you get for using Apple tech.

    +

    Step 9. Comparing the AppStore build and the version built in the virtual machine

    +

    Install the necessary tools:
    if ! type brew > /dev/null; + then /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"; fi && brew install python3

    +
    + +
    + +

    Run
    python3 tools/ipadiff.py build/artifacts/Telegram.ipa PATH-TO-THE-IPA-FILE-FROM-STEP-9

    +
      +
    1. cd telegram-ios > Enter
      2. +
    2. python3 tools/ipadiff.py build/artifacts/Telegram.ipa /path/ > Enter
      3. +
    +
    + +
    + +

    In case of a successful comparison, you will get a text along these lines:

    +
    IPAs are equal, except for the files that can't currently be checked:
+    Excluded files that couldn't be checked due to being encrypted:
+        PlugIns/SiriIntents.appex/SiriIntents
+        PlugIns/Widget.appex/Widget
+        PlugIns/NotificationContent.appex/NotificationContent
+        PlugIns/NotificationService.appex/NotificationService
+        PlugIns/Share.appex/Share
+    IPAs contain Watch directory with a Watch app which can't be checked currently.
+    IPAs contain .car (Asset Catalog) files that are compiled by the App Store and can't currently be checked:
+
+        Frameworks/TelegramUI.framework/Assets.car
+        Assets.car
+    IPAs contain .nib (compiled Interface Builder) files that are compiled by the App Store and can't currently be checked:
+        Base.lproj/LaunchScreen.nib
    +
    + +
    + +

    In case of any mismatches, you'll get a detailed report.

    +
    + +
    + +

    iOS: Notes

    +
      +

    1. You will get a warning if the archive created in Step 7 contains encrypted files. If all these files are in the PlugIns subfolder, they represent various system extensions (e.g. external sharing, Siri, 3D touch). Decrypting such files using existing ways of receiving app archives via Jailbreak is non-trivial (but we're working on resolving this issue). If you do manage to decrypt them, e.g. on iOS 8, they will be matched.

      +
      2. +

    2. You will be notified if the archive includes an Apple Watch app. The watch app will soon no longer be included in the archive.

      +
      3. +

    3. Files with the .car extension are app resource archives (images, sounds) which were compiled and processed specifically for the target device. The App Store processes them in non-trivial ways, we're planning on getting rid of them in future versions.

      +
      4. +

    4. The LaunchScreen.nib file is an empty file containing a description of the interface which is displayed by the system before the app is launched. It is processed by the App Store in a non-trivial way but doesn't contain any code and therefore may be ignored.

      +
      5. +
    +
    +

    Troubleshooting

    +

    If you encounter any issues with obtaining the code, building and comparing the apps, please contact us at @botsupport and include the hashtag #reproducibleBuilds with your message describing the problem.

    +

    Troubleshooting: Android

    +
      +

    1. Make sure that you checkout the correct version of the code.

      +
      2. +

    2. Make sure that you build the app using the right SDK.

      +
      3. +

    3. If the gradle version used in the Dockerfile is not available anymore and building of the Docker image fails, wait for a Dockerfile update or update manually to lastest available version.

      +
      4. +
    +

    …

    +

    We will update this section with information on overcoming other common issues.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/schema.html b/data/core.telegram.org/schema.html new file mode 100644 index 0000000000..0c7574e3c8 --- /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 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:# 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;
    +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/schema/end-to-end-json.html b/data/core.telegram.org/schema/end-to-end-json.html deleted file mode 100644 index 6c3b4f2cbe..0000000000 --- a/data/core.telegram.org/schema/end-to-end-json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"528568095","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":8},{"id":"541931640","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":17},{"id":"917541342","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"}],"type":"DecryptedMessage","layer":45},{"id":"-1848883596","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"},{"name":"grouped_id","type":"flags.17?long"}],"type":"DecryptedMessage","layer":73},{"id":"-1438109059","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":8},{"id":"1930838368","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":17},{"id":"144661578","predicate":"decryptedMessageMediaEmpty","params":[],"type":"DecryptedMessageMedia","layer":8},{"id":"846826124","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-235238024","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1290694387","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1380598109","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"-1760785394","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"893913689","predicate":"decryptedMessageMediaGeoPoint","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1485441687","predicate":"decryptedMessageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"user_id","type":"int"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-1586283796","predicate":"decryptedMessageActionSetMessageTTL","params":[{"name":"ttl_seconds","type":"int"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1332395189","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"2063502050","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"attributes","type":"Vector"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1619031439","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1474341323","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"206520510","predicate":"decryptedMessageActionReadMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1700872964","predicate":"decryptedMessageActionDeleteMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1967000459","predicate":"decryptedMessageActionScreenshotMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1729750108","predicate":"decryptedMessageActionFlushHistory","params":[],"type":"DecryptedMessageAction","layer":8},{"id":"467867529","predicate":"decryptedMessageLayer","params":[{"name":"random_bytes","type":"bytes"},{"name":"layer","type":"int"},{"name":"in_seq_no","type":"int"},{"name":"out_seq_no","type":"int"},{"name":"message","type":"DecryptedMessage"}],"type":"DecryptedMessageLayer","layer":17},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1845219337","predicate":"sendMessageUploadVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-424899985","predicate":"sendMessageUploadAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1727382502","predicate":"sendMessageUploadPhotoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1884362354","predicate":"sendMessageUploadDocumentAction","params":[],"type":"SendMessageAction","layer":17},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1360072880","predicate":"decryptedMessageActionResend","params":[{"name":"start_seq_no","type":"int"},{"name":"end_seq_no","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-217806717","predicate":"decryptedMessageActionNotifyLayer","params":[{"name":"layer","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-860719551","predicate":"decryptedMessageActionTyping","params":[{"name":"action","type":"SendMessageAction"}],"type":"DecryptedMessageAction","layer":17},{"id":"-204906213","predicate":"decryptedMessageActionRequestKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"DecryptedMessageAction","layer":20},{"id":"1877046107","predicate":"decryptedMessageActionAcceptKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-586814357","predicate":"decryptedMessageActionAbortKey","params":[{"name":"exchange_id","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-332526693","predicate":"decryptedMessageActionCommitKey","params":[{"name":"exchange_id","type":"long"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-1473258141","predicate":"decryptedMessageActionNoop","params":[],"type":"DecryptedMessageAction","layer":20},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute","layer":23},{"id":"-83208409","predicate":"documentAttributeSticker","params":[],"type":"DocumentAttribute","layer":23},{"id":"978674434","predicate":"documentAttributeSticker","params":[{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"}],"type":"DocumentAttribute","layer":45},{"id":"1494273227","predicate":"documentAttributeVideo","params":[{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":66},{"id":"85215461","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"-556656416","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"},{"name":"title","type":"string"},{"name":"performer","type":"string"}],"type":"DocumentAttribute","layer":45},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute","layer":46},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute","layer":23},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize","layer":23},{"id":"2009052699","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize","layer":23},{"id":"-374917894","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize","layer":23},{"id":"2086234950","predicate":"fileLocationUnavailable","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"1406570614","predicate":"fileLocation","params":[{"name":"dc_id","type":"int"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"-90853155","predicate":"decryptedMessageMediaExternalDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumb","type":"PhotoSize"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"DecryptedMessageMedia","layer":23},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity","layer":45},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity","layer":45},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet","layer":45},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet","layer":45},{"id":"-1978796689","predicate":"decryptedMessageMediaVenue","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-452652584","predicate":"decryptedMessageMediaWebPage","params":[{"name":"url","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction","layer":66},{"id":"-1150187996","predicate":"sendMessageUploadRoundAction","params":[],"type":"SendMessageAction","layer":66}],"methods":[]} \ No newline at end of file diff --git a/data/core.telegram.org/stickers.html b/data/core.telegram.org/stickers.html new file mode 100644 index 0000000000..b1683a7d5b --- /dev/null +++ b/data/core.telegram.org/stickers.html @@ -0,0 +1,249 @@ + + + + + Telegram Stickers + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Telegram Stickers

    + +

    All users can create, send and share custom artwork using Telegram's open Sticker Platform. Stickers take many forms – from basic images to stunning vector animations.

    +

    To start building your own custom sets, click below:

    + +

    Animated Stickers

    +

    Telegram stickers can move with smooth 60 FPS animations to bring your characters to life in high-resolution.

    +
    +

    Animated stickers use Telegram's unique .TGS format – click here for Video Stickers made in .WEBM format.

    +
    +

    Creating Animated Stickers

    +

    To create vector animated stickers you will need the following:

    +
      +
    1. Any vector graphics editor that allows exporting vector objects to Adobe After Effects to turn them into animations.
      2. +
    2. Adobe After Effects.
      3. +
    3. The Bodymovin-TG plugin, a fork of Bodymovin for Adobe After Effects that can be used to export animations to .TGS, the Telegram animated sticker format.
      4. +
    +
    +

    The Lottie-based .TGS format allows for incredibly detailed stickers that are less than 30 KB in size – six times smaller than the average photo.

    +
    +

    Animated Sticker Requirements

    +
      +
    • Sticker/canvas size must be 512х512 pixels.
      • +
    • Sticker objects must not leave the canvas.
      • +
    • Animation length must not exceed 3 seconds.
      • +
    • All animations must be looped.
      • +
    • Sticker size must not exceed 64 KB after rendering in Bodymovin.
      • +
    • All animations must run at 60 Frames Per Second.
      • +
    • You must not use the following Adobe After Effects functionality when animating your stickers: Auto-bezier keys, Expressions, Masks, Layer Effects, Images, Solids, Texts, 3D Layers, Merge Paths, Star Shapes, Gradient Strokes, Repeaters, Time Stretching, Time Remapping, Auto-Oriented Layers.
      • +
    +

    Uploading Animated Stickers

    +

    When your stickers are ready, send the /newanimated command to the @Stickers bot – then send it the .TGS files.

    +

    Your set will need an icon. Icons for animated sticker sets must be 100x100 pixels, with a looped animation not exceeding 3 seconds.

    +
    +

    Video Stickers

    +

    Video Stickers are built with .WEBM – an open-source format that is compatible with many graphics editors to create high-detail images. Requires Telegram 8.5 or higher.

    + + +

    Creating Video Stickers

    +

    To create Video Stickers, you only need editing software that lets you export your project as a .WEBM video file (alpha channel no longer required).

    +

    Video Sticker Requirements

    +
    +

    See this Encoding .WEBM with VP9 Guide for details

    +
    +
      +
    • One side of the sticker must be exactly 512 pixels in size – the other side can be 512 pixels or less.
      • +
    • Video duration must not exceed 3 seconds.
      • +
    • Frame rate can be up to 30 FPS.
      • +
    • Video must have a transparent layer (this is no longer required).
      • +
    • Video should be looped for optimal user experience.
      • +
    • Video size should not exceed 256 KB.
      • +
    • Video must be in .WEBM format encoded with the VP9 codec.
      • +
    • Video must have no audio stream.
      • +
    +

    Uploading Video Stickers

    +

    Once your stickers are ready, send the /newvideo command to the @Stickers bot – then send it the .WEBM files.

    +

    Your set will need a .WEBM icon. Icons for video sticker sets must be 100x100 pixels, with a looped animation not exceeding 3 seconds.

    +
    +

    Static Stickers

    +

    Turn your favorite drawings and memes into packs of images that are easily accessible on any device – no more digging through your gallery.

    +

    Creating Static Stickers

    +

    To create static stickers for the Telegram platform, you only need an image editor that lets you export in .PNG or .WEBP format.

    +

    Static Sticker Requirements

    +
      +
    • One side of the sticker must be exactly 512 pixels in size – the other side can be 512 pixels or less.
      • +
    • The image file must be in either .PNG or .WEBP format.
      • +
    +
    +

    Tip: a transparent background, white stroke and black shadow effect will make your sticker stand out.

    +
    +

    Uploading Static Stickers

    +

    Once your stickers are ready, start a chat with the @Stickers bot and send the command /newpack. Your sticker set can also have a custom icon – a 100x100 pixel image in .PNG or .WEBP format.

    +
    +

    For more info about using the @Stickers bot, click here.

    +
    +
    +

    Using the @Stickers Bot

    +

    Publishing and editing sticker packs is simple and automated, thanks to the @Stickers bot. It can also show you detailed stats for stickers and packs.

    +

    Publishing a Sticker Pack

    +

    Once you open the bot, press the Start button or send /start. The bot will reply, describing its different commands. It will walk you through step by step, but here's a quick guide:

    +
      +
    • Open the bot menu in the message bar and select the /newpack command to start uploading static stickers. For animated stickers use /newanimated, or /newvideo for video stickers.
      • +
    • Give your sticker pack a name – this name will appear as the title for your pack in the sticker panel.
      • +
    • Send your first sticker file – an image file, .TGS file, or .WEBM file. Using one of the Desktop or Web apps is strongly recommended.
      • +
    • Choose an emoji that corresponds to your sticker – this lets users quickly find it with sticker suggestions.
      • +
    • Continue uploading all your sticker files.
      • +
    • When you're done uploading, send the /publish command.
      • +
    • Set an icon for your pack – static sticker packs can /skip this step, but it is required for animated or video stickers.
      • +
    • Choose a short name for your sticker pack – it will be used to create a shareable link for the pack like t.me/addstickers/HotCherry. Congratulations! Your stickers are ready for the world.
      • +
    +
    +

    After your pack is finished, you can send /start again to see the full list of commands, or use the bot menu to create another pack, edit an existing pack, or see statistics.

    +
    +

    Editing a Sticker Pack

    +

    Once you've created one or more packs, you can add, edit or replace stickers in your existing sets.

    +
      +
    • Use /addsticker if you have more artwork you'd like to add to a set. Choose one of your packs from the list – the upload process is exactly the same as before.
      • +
    • Use /editsticker to change the emoji you assigned to a sticker – select the pack and sticker, or simply send the intended sticker from your panel.
      • +
    • Use /replacesticker if you want to swap out an older sticker for an updated version.
      • +
    • Use /ordersticker to change the order of stickers in your pack. Choose the pack and one of the stickers, then choose another sticker to appear before it (to the left) in the panel.
      • +
    • Use /delsticker to remove a sticker from the pack – you can always use /addsticker to add it again if you change your mind.
      • +
    • Use /seticon to set an icon for your pack or to change the icon. Static sticker packs without a custom icon will use the first sticker as its icon.
      • +
    +
    +

    Edits to your sticker packs may take up to an hour to update for all users.

    +
    +

    Sticker Stats

    +

    There are a number of commands that let you see statistics for your stickers – here's what they all do:

    +
      +
    • /packstats shows how many times your pack was used, installed and removed – both recently and overall.
      • +
    • /stats shows how many times an individual sticker has been sent.
      • +
    • /top shows the most popular stickers from all your packs.
      • +
    • /packtop shows your most popular sticker packs and their individual stats.
      • +
    • /topbypack shows the top stickers from a specific sticker pack.
      • +
    • /packusagetop shows your most popular packs by recent usage.
      • +
    +
    +

    You can filter the results of /top, /packtop, /topbypack and /packusagetop. For example /top 20 would show your top 20 stickers, and /topbypack -5 would show the 5 least popular stickers from a pack.

    +
    +

    Importing Stickers From Other Apps

    +

    Developers can build apps to automate importing stickers using Telegram’s API. With these tools, users can instantly bring their favorite stickers to Telegram.

    +

    For Developers

    +

    As of version 7.8, Telegram apps support a simple API for importing stickers. Developers can use this to build apps or add tools to apps that let users instantly transfer stickers to Telegram – or create custom stickers from photos or videos.

    +
    +

    Click here for more information about developing apps for importing stickers.

    +
    +

    For Users

    +

    Users can find apps that allow them to import stickers or quickly generate their own. They can also easily publish custom stickers with the @Stickers bot using .PNG, .WEBP or .WEBM files for stickers from other apps.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/stickers/webm-vp9-encoding.html b/data/core.telegram.org/stickers/webm-vp9-encoding.html new file mode 100644 index 0000000000..adb9aa235c --- /dev/null +++ b/data/core.telegram.org/stickers/webm-vp9-encoding.html @@ -0,0 +1,159 @@ + + + + + Encoding Video Stickers with .WEBM and VP9 + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Encoding Video Stickers with .WEBM and VP9

    + +

    The Video Sticker format allows anyone to easily create high-detail animations that users can send and share instantly in Telegram.

    +

    Video Sticker Requirements

    +
      +
    • Video must be in .WEBM format, up to 30 FPS.
      • +
    • Video must be encoded with the VP9 codec.
      • +
    • Video must have no audio stream.
      • +
    • One side must be 512 pixels in size – the other side can be 512 pixels or less.
      • +
    • Duration must not exceed 3 seconds.
      • +
    • Video must have a transparent layer (this is no longer required).
      • +
    • Video should be looped for optimal user experience.
      • +
    • Video size should not exceed 256 KB after encoding.
      • +
    +

    Encoding Video Files

    +

    You can design your animation in your preferred app – but depending on the app’s export settings, you may need an encoding program to create the final file.

    +
    +

    Programs like Handbrake or ffmpeg natively support .WEBM encoding with VP9.

    +
    +

    Encoding with Adobe Media Encoder

    +

    Adobe’s Media Encoder requires a plug-in to support .WEBM encoding. Here is a modified version of a plug-in by fnord software that you can install to render your video stickers with Media Encoder.

    + +

    After the plug-in is installed, .WEBM will appear in the list of formats in the Queue tab.

    +
    +

    On macOS, you may need to go to Settings > Security & Privacy to approve installation.

    +
    +

    Render Settings

    +

    If it’s your first time working with encoding software, here are some tips that might help:

    +
      +
    • Make sure to check that VP9 is selected in the codec settings – some apps may default to VP8.
      • +
    • Make sure to remove any audio streams (uncheck ‘Export Audio’ in Adobe programs).
      • +
    • Make sure the frame rate is a constant 30 FPS.
      • +
    • Use Constant Quality and a lower (or lowest) quality setting – size dramatically decreases without affecting fidelity.
      • +
    • In Media Encoder, make sure your Renderer is set to ‘Software Only’.
      • +
    • If your file fails to render, try importing it as a PNG Sequence.
      • +
    +
    +

    After Effects projects integrate directly with Media Encoder via File > Export > Add to Media Encoder Queue.

    +
    +

    Uploading Video Stickers

    +

    The @Stickers bot lets you quickly publish and manage your sticker packs. Start a chat with it on Telegram and it will walk you through the process. For step-by-step instructions and more information, see this guide.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/tdlib.html b/data/core.telegram.org/tdlib.html new file mode 100644 index 0000000000..a48649c3b4 --- /dev/null +++ b/data/core.telegram.org/tdlib.html @@ -0,0 +1,147 @@ + + + + + Telegram Database Library + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Telegram Database Library

    + +
    + +
    + +

    TDLib (Telegram Database Library) is a cross-platform, fully functional Telegram client. We designed it to help third-party developers create their own custom apps using the Telegram platform.

    +
    +

    Read about TDLib on the Telegram blog »

    +
    +

    TDLib Advantages

    +
      +
    • Cross-platform. TDLib can be used on Android, iOS, Windows, macOS, Linux, WebAssembly, FreeBSD, Windows Phone, watchOS, tvOS, Tizen, Cygwin. It should also work on other *nix systems with or without minimal effort.
      • +
    • Multilanguage. TDLib can be easily used with any programming language that is able to execute C functions. Additionally it already has native bindings to Java (using JNI) and C# (using C++/CLI).
      • +
    • Easy to use. TDLib takes care of all network implementation details, encryption and local data storage.
      • +
    • High-performance. In the Telegram Bot API, each TDLib instance handles more than 24,000 active bots simultaneously.
      • +
    • Well-documented. All TDLib API methods and public interfaces are fully documented.
      • +
    • Consistent. TDLib guarantees that all updates will be delivered in the right order.
      • +
    • Reliable. TDLib remains stable on slow and unreliable Internet connections.
      • +
    • Secure: All local data is encrypted using a user-provided encryption key.
      • +
    • Fully-asynchronous. Requests to TDLib don't block each other or anything else, responses will be sent when they are available.
      • +
    +
    +

    Getting started with TDLib »

    +
    +

    Resources

    +

    TDLib is fully open source, all code is available on GitHub.

    +

    See also:

    + +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/tdlib/options.html b/data/core.telegram.org/tdlib/options.html deleted file mode 100644 index b7af629b05..0000000000 --- a/data/core.telegram.org/tdlib/options.html +++ /dev/null @@ -1,501 +0,0 @@ - - - - - TDLib options - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    TDLib options

    - -

    TDLib has many options that affect the behavior of the library. Each option has a name and a value. Value may be of one of the following types:

    - - - - - - - - - - - - - - - - - - - - - - - -
    Type of valueDefault valueValue range
    Integer064-bit integer
    BooleanfalseTrue or false
    StringAny Unicode string
    -

    List of options supported by TDLib

    -

    Options not mentioned in this list may be safely ignored.

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeWritableDescription
    always_parse_markdownBooleanYesIf true, text entities will be automatically parsed in all inputMessageText objects
    archive_and_mute_new_chats_from_unknown_usersBooleanYesIf true, new chats from non-contacts will be automatically archived and muted. The option can be set only if the option “can_archive_and_mute_new_chats_from_unknown_users” is true. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
    disable_animated_emojiBooleanYesIf true, animated emoji will be disabled and shown as plain emoji
    disable_contact_registered_notificationsBooleanYesIf true, notifications about the user's contacts who have joined Telegram will be disabled. User will still receive the corresponding message in the private chat. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
    disable_persistent_network_statisticsBooleanYesIf true, persistent network statistics will be disabled, which significantly reduces disk usage
    disable_sent_scheduled_message_notificationsBooleanYesIf true, notifications about outgoing scheduled messages that were sent will be disabled
    disable_time_adjustment_protectionBooleanYesIf true, protection from external time adjustment will be disabled, which significantly reduces disk usage
    disable_top_chatsBooleanYesIf true, support for top chats and statistics collection is disabled
    ignore_background_updatesBooleanYesIf true, allows to skip all updates received while the TDLib instance was not running. The option does nothing if the database or secret chats are used
    ignore_default_disable_notificationBooleanYesIf true, the disable_notification value specified in the request will be always used instead of the default value
    ignore_inline_thumbnailsBooleanYesIf true, prevents file thumbnails sent by the server along with messages from being saved on the disk
    ignore_platform_restrictionsBooleanYesIf true, chat and message restrictions specific to the currently used operating system will be ignored
    ignore_sensitive_content_restrictionsBooleanYesIf true, sensitive content will be shown on all user devices. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
    is_location_visibleBooleanYesIf true, other users will be allowed to see the current user's location. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
    language_pack_database_pathStringYesPath to a database for storing language pack strings, so that this database can be shared between different accounts. By default, language pack strings are stored only in memory. Changes of value of this option will be applied only after TDLib restart, so it should be set before call to setTdlibParameters.
    language_pack_idStringYesIdentifier of the currently used language pack from the current localization target
    localization_targetStringYesName for the current localization target (currently supported: “android”, “android_x”, “ios”, “macos” and “tdesktop”)
    message_unload_delayIntegerYesThe maximum time messages are stored in memory before they are unloaded, 60-86400; in seconds. Defaults to 60 for users and 1800 for bots
    notification_group_count_maxIntegerYesMaximum number of notification groups to be shown simultaneously, 0-25
    notification_group_size_maxIntegerYesMaximum number of simultaneously shown notifications in a group, 1-25. Defaults to 10
    onlineBooleanYesOnline status of the current user
    prefer_ipv6BooleanYesIf true, IPv6 addresses will be preferred over IPv4 addresses
    use_pfsBooleanYesIf true, Perfect Forward Secrecy will be enabled for interaction with the Telegram servers for cloud chats
    use_quick_ackBooleanYesIf true, quick acknowledgement will be enabled for outgoing messages
    use_storage_optimizerBooleanYesIf true, the background storage optimizer will be enabled
    utc_time_offsetIntegerYesA UTC time offset used for splitting messages by days. The option is reset automatically on each TDLib instance launch, so it needs to be set manually only if the time offset is changed during execution.
    animation_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for animations search
    authentication_tokenStringNoAn authentication token to be used on subsequent authorizations and received when logging out
    authorization_dateIntegerNoPoint in time (Unix timestamp) when authorization was received
    basic_group_size_maxIntegerNoMaximum number of members in a basic group
    call_connect_timeout_msIntegerNoMaximum time to wait for call connection creation to be passed to libtgvoip
    call_packet_timeout_msIntegerNoMaximum time to wait for call packet delivery to be passed to libtgvoip
    can_archive_and_mute_new_chats_from_unknown_usersBooleanNoIf true, the option “archive_and_mute_new_chats_from_unknown_users” can be changed
    can_ignore_sensitive_content_restrictionsBooleanNoIf true, the option “ignore_sensitive_content_restrictions” can be changed
    channel_bot_user_idIntegerNoIdentifier of the bot which is shown as the sender of messages sent on behalf of channels when viewed from an outdated client
    enabled_proxy_idIntegerNoIdentifier of the enabled proxy
    expect_blockingBooleanNoIf true, access to Telegram is likely blocked for the user
    favorite_stickers_limitIntegerNoMaximum number of favorite stickers
    forwarded_message_count_maxIntegerNoMaximum number of forwarded messages per one request
    group_anonymous_bot_user_idIntegerNoIdentifier of the bot which is shown as the sender of anonymous messages in groups when viewed from an outdated client
    message_caption_length_maxIntegerNoMaximum length of a message caption
    message_text_length_maxIntegerNoMaximum length of a message text
    my_idIntegerNoIdentifier of the current user
    pinned_archived_chat_count_maxIntegerNoMaximum number of pinned cloud chats in the Archive chat list. The same amount of secret chats can be pinned locally
    pinned_chat_count_maxIntegerNoMaximum number of pinned cloud chats in the Main chat list. The same amount of secret chats can be pinned locally
    photo_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for photos search
    replies_bot_chat_idIntegerNoIdentifier of the @replies bot
    suggested_language_pack_idStringNoIdentifier of the language pack, suggested for the user by the server
    suggested_video_note_audio_bitrateStringNoSuggested bit rate for audio encoding in video notes
    suggested_video_note_lengthStringNoSuggested width and height of the video in video notes
    suggested_video_note_video_bitrateStringNoSuggested bit rate for video encoding in video notes
    supergroup_size_maxIntegerNoMaximum number of members in a supergroup
    t_me_urlStringNoCurrent value of t.me URL, i.e. https://t.me/
    telegram_service_notifications_chat_idIntegerNoIdentifier of the Telegram Service Notifications chat
    test_modeBooleanNoIf true, the test environment is being used instead of the production environment
    unix_timeIntegerNoAn estimation of the current Unix timestamp. The option will not be updated automatically unless the difference between the previous estimation and the locally available monotonic clocks changes significantly
    venue_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for venues search
    versionStringNoTDLib version. This options is guaranteed to come before all other updates since TDLib 1.4.0
    -

    Additionally any option beginning with 'x' or 'X' is writeable and can be safely used by the application to persistently store some small amount of data.

    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - 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

    + +

    Encryption

    + +

    Authentication

    + +

    Protection against known attacks

    + +

    Encrypted CDNs

    + +
    +

    +

    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.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/type/ChannelAdminLogEventAction.html b/data/core.telegram.org/type/ChannelAdminLogEventAction.html deleted file mode 100644 index dfe31939e3..0000000000 --- a/data/core.telegram.org/type/ChannelAdminLogEventAction.html +++ /dev/null @@ -1,298 +0,0 @@ - - - - - ChannelAdminLogEventAction - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    ChannelAdminLogEventAction

    - -

    Channel admin log event

    -

    - -
    -
    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;

    -

    Constructors

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    channelAdminLogEventActionChangeTitleChannel/supergroup title was changed
    channelAdminLogEventActionChangeAboutThe description was changed
    channelAdminLogEventActionChangeUsernameChannel/supergroup username was changed
    channelAdminLogEventActionChangePhotoThe channel/supergroup's picture was changed
    channelAdminLogEventActionToggleInvitesInvites were enabled/disabled
    channelAdminLogEventActionToggleSignaturesChannel signatures were enabled/disabled
    channelAdminLogEventActionUpdatePinnedA message was pinned
    channelAdminLogEventActionEditMessageA message was edited
    channelAdminLogEventActionDeleteMessageA message was deleted
    channelAdminLogEventActionParticipantJoinA user has joined the group (in the case of big groups, info of the user that has joined isn't shown)
    channelAdminLogEventActionParticipantLeaveA user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)
    channelAdminLogEventActionParticipantInviteA user was invited to the group
    channelAdminLogEventActionParticipantToggleBanThe banned rights of a user were changed
    channelAdminLogEventActionParticipantToggleAdminThe admin rights of a user were changed
    channelAdminLogEventActionChangeStickerSetThe supergroup's stickerset was changed
    channelAdminLogEventActionTogglePreHistoryHiddenThe hidden prehistory setting was changed
    channelAdminLogEventActionDefaultBannedRightsThe default banned rights were modified
    channelAdminLogEventActionStopPollA poll was stopped
    channelAdminLogEventActionChangeLinkedChatThe linked chat was changed
    channelAdminLogEventActionChangeLocationThe geogroup location was changed
    channelAdminLogEventActionToggleSlowModeSlow mode setting for supergroups was changed
    channelAdminLogEventActionStartGroupCallA group call was started
    channelAdminLogEventActionDiscardGroupCallA group call was terminated
    channelAdminLogEventActionParticipantMuteA group call participant was muted
    channelAdminLogEventActionParticipantUnmuteA group call participant was unmuted
    channelAdminLogEventActionToggleGroupCallSettingGroup call settings were changed
    channelAdminLogEventActionParticipantJoinByInviteA user joined the supergroup/channel using a specific invite link
    channelAdminLogEventActionExportedInviteDeleteA chat invite was deleted
    channelAdminLogEventActionExportedInviteRevokeA specific invite link was revoked
    channelAdminLogEventActionExportedInviteEditA chat invite was edited
    channelAdminLogEventActionParticipantVolumechannelAdminLogEvent.user_id has set the volume of participant.peer to participant.volume
    channelAdminLogEventActionChangeHistoryTTLThe Time-To-Live of messages in this chat was changed
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/ChannelLocation.html b/data/core.telegram.org/type/ChannelLocation.html deleted file mode 100644 index 5dd2122123..0000000000 --- a/data/core.telegram.org/type/ChannelLocation.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - 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)
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/ChatParticipant.html b/data/core.telegram.org/type/ChatParticipant.html deleted file mode 100644 index 46c022bc0e..0000000000 --- a/data/core.telegram.org/type/ChatParticipant.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - ChatParticipant - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    ChatParticipant

    - -

    Details of a group member.

    -

    - -
    -
    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;

    -

    Constructors

    - - - - - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    chatParticipantGroup member.
    chatParticipantCreatorRepresents the creator of the group
    chatParticipantAdminChat admin
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/ExportedChatInvite.html b/data/core.telegram.org/type/ExportedChatInvite.html deleted file mode 100644 index aed3752f1b..0000000000 --- a/data/core.telegram.org/type/ExportedChatInvite.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ExportedChatInvite - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    ExportedChatInvite

    - -

    Exported chat invite

    -

    - -
    -
    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;
-
----functions---
-
-messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    chatInviteExportedExported chat invite
    -

    Methods

    - - - - - - - - - - - - - -
    MethodDescription
    messages.exportChatInviteExport an invite link for a chat
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/ExportedMessageLink.html b/data/core.telegram.org/type/ExportedMessageLink.html deleted file mode 100644 index cd7f496ad9..0000000000 --- a/data/core.telegram.org/type/ExportedMessageLink.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - 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
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/InputStickerSetItem.html b/data/core.telegram.org/type/InputStickerSetItem.html deleted file mode 100644 index 67da6bdecb..0000000000 --- a/data/core.telegram.org/type/InputStickerSetItem.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputStickerSetItem - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    InputStickerSetItem

    - -

    Sticker

    -

    - -
    -
    inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    inputStickerSetItemSticker in a stickerset
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/auth.ExportedAuthorization b/data/core.telegram.org/type/LangPackString.html similarity index 79% rename from data/core.telegram.org/type/auth.ExportedAuthorization rename to data/core.telegram.org/type/LangPackString.html index be1bcc28cb..68ef3edc31 100644 --- a/data/core.telegram.org/type/auth.ExportedAuthorization +++ b/data/core.telegram.org/type/LangPackString.html @@ -2,12 +2,12 @@ - Auth.ExportedAuthorization + LangPackString - - + + - + @@ -36,10 +36,10 @@
    -
    -

    Auth.ExportedAuthorization

    +
    +

    LangPackString

    -

    Exported authorization

    +

    Language pack string

    • @@ -52,11 +52,9 @@
    -
    auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
-
----functions---
-
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

    +
    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

    @@ -67,23 +65,16 @@ - - + + - -
    auth.exportedAuthorizationData for copying of authorization between data centres.langPackStringTranslated localization string
    -

    Methods

    - - - - + + - - - - + +
    MethodDescriptionlangPackStringPluralizedA 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
    auth.exportAuthorizationReturns data for copying authorization to another data-centre.langPackStringDeletedDeleted localization string
    diff --git a/data/core.telegram.org/type/Null.html b/data/core.telegram.org/type/Null.html deleted file mode 100644 index 1c82eb47c0..0000000000 --- a/data/core.telegram.org/type/Null.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Null - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    Null

    - -

    Object corresponds to an arbitrary empty object.

    -

    - -
    -
    null#56730bcc = Null;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    nullCorresponds to an arbitrary empty object.
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/PasswordKdfAlgo.html b/data/core.telegram.org/type/PasswordKdfAlgo.html deleted file mode 100644 index e22a7ea56b..0000000000 --- a/data/core.telegram.org/type/PasswordKdfAlgo.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - PasswordKdfAlgo - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    PasswordKdfAlgo

    - -

    Key derivation function to use when generating the password hash for SRP two-factor authorization

    -

    - -
    -
    passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
-passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

    -

    Constructors

    - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    passwordKdfAlgoUnknownUnknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)
    passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPowThis key derivation algorithm defines that SRP 2FA login must be used
    -

    Related pages

    -

    Two-factor authentication

    -

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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/SavedContact.html b/data/core.telegram.org/type/SavedContact.html deleted file mode 100644 index ddbd71d748..0000000000 --- a/data/core.telegram.org/type/SavedContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SavedContact - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    SavedContact

    - -

    Saved contact

    -

    - -
    -
    savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    savedPhoneContactSaved contact
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/SecureFile.html b/data/core.telegram.org/type/SecureFile.html deleted file mode 100644 index bd82e09aee..0000000000 --- a/data/core.telegram.org/type/SecureFile.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - SecureFile - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    SecureFile

    - -

    Secure passport file, for more info see the passport docs »

    -

    - -
    -
    secureFileEmpty#64199744 = SecureFile;
-secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

    -

    Constructors

    - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    secureFileEmptyEmpty constructor
    secureFileSecure file
    -

    Related pages

    -

    Telegram Passport Manual

    -

    Telegram Passport Encryption Details

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/SecureValueType.html b/data/core.telegram.org/type/SecureValueType.html deleted file mode 100644 index f6b8803cab..0000000000 --- a/data/core.telegram.org/type/SecureValueType.html +++ /dev/null @@ -1,203 +0,0 @@ - - - - - SecureValueType - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    SecureValueType

    - -

    Secure value type

    -

    - -
    -
    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;

    -

    Constructors

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    secureValueTypePersonalDetailsPersonal details
    secureValueTypePassportPassport
    secureValueTypeDriverLicenseDriver's license
    secureValueTypeIdentityCardIdentity card
    secureValueTypeInternalPassportInternal passport
    secureValueTypeAddressAddress
    secureValueTypeUtilityBillUtility bill
    secureValueTypeBankStatementBank statement
    secureValueTypeRentalAgreementRental agreement
    secureValueTypePassportRegistrationInternal registration passport
    secureValueTypeTemporaryRegistrationTemporary registration
    secureValueTypePhonePhone
    secureValueTypeEmailEmail
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/core.telegram.org/type/StatsGroupTopAdmin.html similarity index 86% rename from data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html rename to data/core.telegram.org/type/StatsGroupTopAdmin.html index 5b9493c1d7..27488200b1 100644 --- a/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html +++ b/data/core.telegram.org/type/StatsGroupTopAdmin.html @@ -2,12 +2,12 @@ - inlineQueryPeerTypeBroadcast + StatsGroupTopAdmin - - + + - + @@ -36,10 +36,10 @@
    -
    -

    inlineQueryPeerTypeBroadcast

    +
    +

    StatsGroupTopAdmin

    -

    The inline query was sent in a channel

    +

    Most active admin in a supergroup

    • @@ -52,11 +52,22 @@
    -
    inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    InlineQueryPeerType

    +
    statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

    +

    Constructors

    + + + + + + + + + + + + + +
    ConstructorDescription
    statsGroupTopAdminInformation about an active admin in a supergroup

    Related pages

    Channels

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

    diff --git a/data/core.telegram.org/type/Updates.html b/data/core.telegram.org/type/Updates.html deleted file mode 100644 index a5e8ef3a5e..0000000000 --- a/data/core.telegram.org/type/Updates.html +++ /dev/null @@ -1,508 +0,0 @@ - - - - - Updates - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    Updates

    - -

    Object which is perceived by the client without a call on its part when an event occurs.

    -

    - -
    -
    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.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
-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.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.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.importChatInvite#6c50051c hash:string = Updates;
-messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
-messages.migrateChat#a2875319 chat_id:long = Updates;
-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.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.getAllDrafts#6a3f8d65 = Updates;
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
-messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
-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.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.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
-messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
-
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
-
-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.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.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
-channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
-channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
-channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
-channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
-
-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.createGroupCall#48cdc6d8 flags:# 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.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.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
-phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
-phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
-phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
-
-account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
-
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
-folders.deleteFolder#1c295881 folder_id:int = Updates;

    -

    Constructors

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    updatesTooLongToo many updates, it is necessary to execute updates.getDifference.
    updateShortMessageInfo about a message sent to (received from) another user
    updateShortChatMessageShortened constructor containing info on one new incoming text message from a chat
    updateShortShortened constructor containing info on one update not requiring auxiliary data
    updatesCombinedConstructor for a group of updates.
    updatesFull constructor of updates
    updateShortSentMessageShortened 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).
    -

    Methods

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    MethodDescription
    contacts.deleteContactsDeletes several contacts from the list.
    messages.sendMessageSends a message to a chat
    messages.sendMediaSend a media
    messages.forwardMessagesForwards messages by their IDs.
    messages.editChatTitleChanages chat name and sends a service message on it.
    messages.editChatPhotoChanges chat photo and sends a service message on it
    messages.addChatUserAdds a user to a chat and sends a service message on it.
    messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
    messages.createChatCreates a new chat.
    messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
    messages.startBotStart a conversation with a bot using a deep linking parameter
    help.getAppChangelogGet changelog of current app
    channels.createChannelCreate a supergroup/channel.
    channels.editAdminModify the admin rights of a user in a supergroup/channel.
    channels.editTitleEdit the name of a channel/supergroup
    channels.editPhotoChange the photo of a channel/supergroup
    channels.joinChannelJoin a channel/supergroup
    channels.leaveChannelLeave a channel/supergroup
    channels.inviteToChannelInvite users to a channel/supergroup
    channels.deleteChannelDelete a channel/supergroup
    messages.migrateChatTurn a legacy group into a supergroup
    messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
    channels.toggleSignaturesEnable/disable message signatures in channels
    messages.editMessageEdit message
    messages.getAllDraftsSave get all message drafts.
    messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
    phone.discardCallRefuse or end running call
    phone.setCallRatingRate a call
    channels.editBannedBan/unban/kick a user in a supergroup/channel.
    messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
    channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
    messages.sendMultiMediaSend an album of media
    messages.updatePinnedMessagePin a message
    account.getNotifyExceptionsReturns list of chats with non-default notification settings
    messages.sendVoteVote in a poll
    messages.getPollResultsGet poll results
    messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
    folders.editPeerFoldersEdit peers in folder
    folders.deleteFolderDelete a folder
    contacts.addContactAdd an existing telegram user as contact
    contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
    channels.editCreatorTransfer channel ownership
    contacts.getLocatedGet contacts near you
    channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
    messages.sendScheduledMessagesSend scheduled messages
    messages.deleteScheduledMessagesDelete scheduled messages
    contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
    phone.createGroupCallCreate a group call or livestream
    phone.joinGroupCallJoin a group call
    phone.leaveGroupCallLeave a group call
    phone.inviteToGroupCallInvite a set of users to a group call.
    phone.discardGroupCallTerminate a group call
    phone.toggleGroupCallSettingsChange group call settings
    messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
    channels.convertToGigagroupConvert a supergroup to a gigagroup
    phone.toggleGroupCallRecordStart or stop recording a group call
    phone.editGroupCallParticipantEdit information about a given group call participant
    phone.editGroupCallTitleEdit the title of a group call or livestream
    phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
    phone.startScheduledGroupCallStart a scheduled group call.
    phone.joinGroupCallPresentationStart screen sharing in a call
    phone.leaveGroupCallPresentationStop screen sharing in a group call
    messages.setChatThemeChange the chat theme of a certain chat
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/contacts.Found b/data/core.telegram.org/type/WallPaper.html similarity index 79% rename from data/core.telegram.org/type/contacts.Found rename to data/core.telegram.org/type/WallPaper.html index a68139410f..ca67900ae6 100644 --- a/data/core.telegram.org/type/contacts.Found +++ b/data/core.telegram.org/type/WallPaper.html @@ -2,12 +2,12 @@ - contacts.Found + WallPaper - - + + - + @@ -36,10 +36,10 @@
    -
    -

    contacts.Found

    +
    +

    WallPaper

    -

    Object contains info on users found by name substring and auxiliary data.

    +

    Object contains info on a wallpaper.

    • @@ -52,11 +52,13 @@
    -
    contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
+
    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---
 
-contacts.search#11f812d8 q:string limit:int = contacts.Found;
    
+account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
+account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

    Constructors

    @@ -67,8 +69,12 @@ - - + + + + + +
    contacts.foundUsers found by name substring and auxiliary data.wallPaperWallpaper settings.
    wallPaperNoFileNo file wallpaper
    @@ -82,8 +88,12 @@ -contacts.search -Returns users found by username substring. +account.getWallPaper +Get info about a certain wallpaper + + +account.uploadWallPaper +Create and upload a new wallpaper
    diff --git a/data/core.telegram.org/type/auth.PasswordRecovery b/data/core.telegram.org/type/auth.PasswordRecovery deleted file mode 100644 index 94ec06ba24..0000000000 --- a/data/core.telegram.org/type/auth.PasswordRecovery +++ /dev/null @@ -1,165 +0,0 @@ - - - - - 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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/messages.ArchivedStickers b/data/core.telegram.org/type/messages.ArchivedStickers deleted file mode 100644 index 573b9cb6cb..0000000000 --- a/data/core.telegram.org/type/messages.ArchivedStickers +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.ArchivedStickers - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    Messages.ArchivedStickers

    - -

    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;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    messages.archivedStickersArchived stickersets
    -

    Methods

    - - - - - - - - - - - - - -
    MethodDescription
    messages.getArchivedStickersGet all archived stickers
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/type/payments.BankCardData b/data/core.telegram.org/type/payments.BankCardData deleted file mode 100644 index 6268d3ffbb..0000000000 --- a/data/core.telegram.org/type/payments.BankCardData +++ /dev/null @@ -1,162 +0,0 @@ - - - - - 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
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/video_stickers.html b/data/core.telegram.org/video_stickers.html new file mode 100644 index 0000000000..abf48687bc --- /dev/null +++ b/data/core.telegram.org/video_stickers.html @@ -0,0 +1,115 @@ + + + + + Page not found + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Page not found

    + +
    The page has not been saved
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org.html b/data/corefork.telegram.org.html new file mode 100644 index 0000000000..a082817b82 --- /dev/null +++ b/data/corefork.telegram.org.html @@ -0,0 +1,253 @@ + + + + + Telegram APIs + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Telegram APIs

    + +

    We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

    +

    You can also add Telegram Widgets to your website.

    +

    Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

    +
    +

    Bot API

    +
    + +
    +

    This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

    +

    To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle 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.

    +
    +

    Learn more about the Bot API here »

    +
    +

    Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

    +
    +

    TDLib – build your own Telegram

    +

    Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

    +

    TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

    +

    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 open source and compatible with virtually any programming language.

    +
    +

    Learn more about TDLib here »

    +
    +
    +

    Telegram API

    +

    This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

    + +

    Getting started

    +

    Creating an application

    +

    How to get your application identifier and create a new Telegram app.

    +

    User authorization

    +

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

    +

    Two-factor authentication

    +

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

    +

    QR code login

    +

    QR code login flow

    +

    Error handling

    +

    How to handle API return errors correctly.

    +

    Handling different data centers

    +

    How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

    +

    Handling updates

    +

    How to subscribe to updates and handle them properly.

    +

    Handling PUSH-notifications

    +

    How to subscribe and handle them properly.

    +

    Channels, supergroups and groups

    +

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

    +

    Channel statistics

    +

    Telegram offers detailed channel statistics for channels and supergroups.

    +

    Calling methods

    +

    Additional options for calling methods.

    +

    Uploading and Downloading Files

    +

    How to transfer large data batches correctly.

    +

    Pagination

    +

    How to fetch results from large lists of objects.

    +

    Client configuration

    +

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

    +

    Security

    +

    Secret chats, end-to-end encryption

    +

    End-to-end-encrypted messaging.

    +

    Security guidelines

    +

    Important checks required in your client application.

    +

    Perfect Forward Secrecy

    +

    Binding temporary authorization key to permanent ones.

    +

    End-to-End Encryption in Voice and Video Calls

    +

    End-to-end-encrypted calls.

    +

    Optimization

    +

    Client optimization

    +

    Ways to boost API interactions.

    +

    API methods

    +

    Available method list

    +

    A list of available high-level methods.

    +

    API TL-schema, as JSON

    +

    Text and JSON-presentation of types and methods used in API.

    +

    Available layer list

    +

    A list of available schema versions.

    +

    Other articles

    +

    Working with bots, using the MTProto API

    +

    How to work with bots using the MTProto API.

    +

    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.

    +

    Search & filters

    +

    Telegram allows applying detailed message filters while looking for messages in chats. +This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

    +

    Polls

    +

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

    +

    Admin, banned and default rights for channels, supergroups and groups

    +

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

    +

    Discussion groups

    +

    Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

    +

    Channel comments and message threads

    +

    Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

    +

    Admin log

    +

    Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

    +

    Pinned messages

    +

    Telegram allows pinning multiple messages on top of a specific chat.

    +

    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.

    +

    Live geolocations

    +

    Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

    +

    Min constructors

    +

    Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

    +

    Account deletion

    +

    How to reset an account if the 2FA password was forgotten.

    +

    Imported messages

    +

    Telegram allows importing messages and media from foreign chat apps.

    +

    Telegram Passport

    +

    How to work with Telegram Passport directly using the MTProto API.

    +

    Telegram Payments

    +

    How to work with Telegram Payments directly using the MTProto API.

    +

    Styled text with message entities

    +

    How to create styled text with message entities

    +

    Working with animated emojis

    +

    Graphical telegram clients should transform emojis into their respective animated version.

    +

    Working with animated dice

    +

    Telegram supports sending animated dice emojis.

    +

    Message drafts

    +

    How to handle message drafts

    +

    Folders

    +

    Working with folders

    +

    Top peer rating

    +

    If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

    +

    Handling file references

    +

    How to handle file references.

    +

    Seamless Telegram Login

    +

    Handle Seamless Telegram Login URL authorization requests.

    +

    Web events

    +

    When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/api/animated-emojis.html b/data/corefork.telegram.org/api/animated-emojis.html new file mode 100644 index 0000000000..f4c1402574 --- /dev/null +++ b/data/corefork.telegram.org/api/animated-emojis.html @@ -0,0 +1,187 @@ + + + + + Animated Emojis + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Animated Emojis

    + +

    Graphical telegram clients should transform emojis into their respective animated version.

    +
    inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
    +

    On startup, clients should fetch the animated emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmoji to the stickerset field.
    +The returned stickerset will contain a set of animated stickers, one for each of the supported emojis.

    +

    Clients should substitute messages containing only one instance of one of the allowed emojis with the respective animated sticker.

    +

    Animated emojis should loop only once when first sent or received, or when clicked.
    +For supported emojis, clients on both sides of private chats with users are supposed to show a reaction animation when any of the two users clicks on the animated emoji: click here for more info ».

    +

    For special dice emojis like 🎲, 🎯, or 🏀, clients are supposed to behave differently both when sending and receiving such emojis: click here for more info ».

    +

    Emojis with sounds

    +

    Certained animated emojis should play sound when clicked, as specified by server-side configuration.

    +

    The returned JSON object will contain the following map, with a list of file IDs to download:

    +
        "emojies_sounds": {
+        "\ud83c\udf83": {
+            "id": "4956223179606458539",
+            "access_hash": "-2107001400913062971",
+            "file_reference_base64": "AF-4ApC7ukC0UWEPZN0TeSJURe7T"
+        },
+        "\u26b0": {
+            "id": "4956223179606458540",
+            "access_hash": "-1498869544183595185",
+            "file_reference_base64": "AF-4ApCLKMGt96WCvLm58kbqZHd3"
+        },
+        "\ud83e\udddf\u200d\u2642": {
+            "id": "4960929110848176331",
+            "access_hash": "3986395821757915468",
+            "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g"
+        },
+    }
    +

    The file reference field should be base64-decoded before downloading the file.

    +

    Emoji reactions

    +
    inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
+
+messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
+stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
+
+sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
+sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
+
+updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
+
+---functions---
+
+messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
+
+messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
    +

    On startup, clients should fetch the animated reaction emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmojiAnimations to the stickerset field.
    +The returned stickerset will contain a set of animated emoji reactions, one or more for each of the supported emojis.
    +If a set of reactions for the ❤ emoji is returned, the same reactions should also be assigned to the 🧡, 💛, 💚, 💙, 💜, 🖤, 🤍 and 🤎 emojis.

    +

    Clients on both sides of private chats with users should overlay one of the appropriate reaction animations over the animated sticker when any of the two users clicks on a supported animated emoji.
    +The reaction animation for each separate tap should be chosen randomly from all the available reactions for a given emoji, and multiple taps should be aggregated and sent to the other user as follows:

    +

    At each tap, clients should store all occurred taps in a local list.
    +After 1 second has elapsed with no more taps, the local list should be cleared and stored taps should be sent using messages.setTyping, passing a sendMessageEmojiInteraction constructor with the following fields:

    +
      +
    • emoticon - The emoji we're reacting to
      • +
    • msg_id - Message ID of the animated emoji that was clicked
      • +
    • interaction - A JSON object with interaction info, containing the following keys:
        +
      • v - An integer indicating the object version, currently 1
        • +
      • a - An array of JSON objects, each containing the following keys:
          +
        • t - float, number of seconds that passed since the previous tap in the array, the first tap uses a value of 0.0.
          • +
        • i - integer, 1-based index of the randomly chosen animation for the tap (equivalent to the index of a specific emoji-related animation in stickerPack + 1).
          • +
        +
        • +
      +
      • +
    +

    1 second after the receiving user has seen the last reaction animation for a specific emoji, an acknowledgement must be sent using messages.setTyping, passing a sendMessageEmojiInteractionSeen with that emoji.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/api/auth.html b/data/corefork.telegram.org/api/auth.html similarity index 98% rename from data/core.telegram.org/api/auth.html rename to data/corefork.telegram.org/api/auth.html index 43fec5c314..aee36a6995 100644 --- a/data/core.telegram.org/api/auth.html +++ b/data/corefork.telegram.org/api/auth.html @@ -162,9 +162,9 @@
    -
    Platform
    +
    Platform
    @@ -181,7 +181,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/api/bots/commands.html b/data/corefork.telegram.org/api/bots/commands.html new file mode 100644 index 0000000000..4a0e8fd99d --- /dev/null +++ b/data/corefork.telegram.org/api/bots/commands.html @@ -0,0 +1,140 @@ + + + + + Commands + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Commands

    + +
    + +

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

    +

    For a simplified description using the HTTP bot API, see here ».

    +

    Getting commands

    +
    botCommand#c27ac8c7 command:string description:string = BotCommand;
+
+botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
+
+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;
+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;
+
+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;
    +

    The botInfo constructors contained in the userFull, chatFull, channelFull contain a list of commands, and for groups, the ID and a description of each bot.

    +

    In graphical clients, when users begin a message with a /, a list of commands supported by all bots present in the current chat should be shown; the same should be done for one-to-one chats with the bot itself.

    +

    If the command list of a bot changes, the bot_info_version contained in the user constructor received in updates will change; this indicates that the client should refetch full bot information using users.getFullUser.

    +

    Setting commands

    +
    botCommand#c27ac8c7 command:string description:string = BotCommand;
+
+---functions---
+
+bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
    +

    The command list can be changed by the owner of the bot through @botfather, but bots can also change their own command list by invoking bots.setBotCommands.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/datacenter.html b/data/corefork.telegram.org/api/datacenter.html deleted file mode 100644 index b6e3c15dbb..0000000000 --- a/data/corefork.telegram.org/api/datacenter.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - 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 occur 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.

    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/api/discussion.html b/data/corefork.telegram.org/api/discussion.html new file mode 100644 index 0000000000..70271a7f45 --- /dev/null +++ b/data/corefork.telegram.org/api/discussion.html @@ -0,0 +1,151 @@ + + + + + Discussion groups + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Discussion groups

    + +
    + +

    Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

    +
    boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+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;
+
+messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+
+---functions---
+
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
    +

    A discussion group can be associated to a channel using channels.setDiscussionGroup.
    +The discussion group can be accessed in the client by clicking on the discuss button of the channel, or by accessing the comment section of a specific post; the discussion group ID is also present in the linked_chat_id field of the channelFull constructor.

    +

    All messages sent to the channel will also be sent to the linked group (with sender peer from_id equal to the peer of the linked channel); those messages will also be automatically pinned in the group.

    +

    Linking a discussion group

    +

    To obtain a list of admined supergroups that a channel admin can possibly associate to a channel, use channels.getGroupsForDiscussion.
    +Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
    +Before linking a supergroup to a channel, access to the supergroup's old messages must also be enabled using channels.togglePreHistoryHidden.

    +

    To set a returned supergroup as a discussion group use channels.setDiscussionGroup.

    +

    Schema:

    +
    boolFalse#bc799737 = Bool;
+boolTrue#997275b5 = Bool;
+
+messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
+
+---functions---
+
+channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
+channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
+
+channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/drafts.html b/data/corefork.telegram.org/api/drafts.html new file mode 100644 index 0000000000..8770c19a7e --- /dev/null +++ b/data/corefork.telegram.org/api/drafts.html @@ -0,0 +1,131 @@ + + + + + Message drafts + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Message drafts

    + +
    + +

    Message drafts in Telegram allow syncing the text typed into message fields between devices.

    +

    Drafts

    +

    Drafts are represented by the DraftMessage constructors. +The parameters of the peer-specific draft should be used as defaults when composing a message to be sent to a certain peer (in the case of media, the same draft should still be used as base, the message will become the caption). +If the user exits the app before sending the message, the message should be saved as a draft:

    +

    Saving drafts

    +

    Drafts can be saved using the messages.saveDraft method.

    +

    Downloading drafts

    +

    New drafts are automatically sent to all devices via updateDraftMessage updates.

    +

    Dialog objects fetched via the API also contain the draft associated with the dialog.

    +

    Clearing drafts

    +

    Drafts can be cleared by setting the clear_draft flag when sending messages or media using messages.sendMessage, messages.sendMedia, messages.sendMultiMedia, messages.sendInlineBotResult and similar or manually by passing empty values to messages.saveDraft.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/end-to-end/seq_no.html b/data/corefork.telegram.org/api/end-to-end/seq_no.html deleted file mode 100644 index ed84d5f923..0000000000 --- a/data/corefork.telegram.org/api/end-to-end/seq_no.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - 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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/api/errors.html b/data/corefork.telegram.org/api/errors.html new file mode 100644 index 0000000000..a7f8aeec7d --- /dev/null +++ b/data/corefork.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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html new file mode 100644 index 0000000000..5cb328b3b2 --- /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#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.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#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;
    +

    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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/folders.html b/data/corefork.telegram.org/api/folders.html new file mode 100644 index 0000000000..238f3f4636 --- /dev/null +++ b/data/corefork.telegram.org/api/folders.html @@ -0,0 +1,179 @@ + + + + + Folders + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Folders

    + +
    + +

    Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
    +In the API, folders are called "dialog filters"; in the UI, they are typically represented as tabs.

    +

    Schema:

    +
    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;
+
+updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
+updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
+updateDialogFilters#3504914f = Update;
+
+---functions---
+
+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;
+
+help.getAppConfig#98914110 = JSONValue;
    +

    Folders

    +

    On startup, clients call:

    + +

    The boolean under the dialog_filters_tooltip JSON key in the result of help.getAppConfig can be used to determine whether a folder tooltip should be presented to the user right away.
    +The UI should then show a list of suggested folder combinations.

    +

    Once configuration is finished, apps call messages.updateDialogFilter to create or update existing folders.
    +As per the dialogFilter constructor, folders have multiple flags that can be combined to determine which chats should be included in (or excluded from) the folder.
    +Folders can also have unlimited pinned chats, as determined by the pinned_peers field.

    +

    To reorder existing folders, messages.updateDialogFiltersOrder should be used with the IDs of the various dialog filters.

    +

    To delete folders, use messages.updateDialogFilter without populating the filter flag field.

    +

    Clients can receive updateDialogFilter, updateDialogFilterOrder updates with new filter information, generated by other clients when modifying folder info.
    +Clients can also receive updateDialogFilters, in which case folder info should be refetched manually using messages.getDialogFilters.

    +

    Peer folders

    +

    The API also has another method for identifying groups of peers, typically used only by archived chats.

    +

    Schema:

    +
    inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
+
+dialogPeer#e56dbf05 peer:Peer = DialogPeer;
+dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
+
+updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
+
+updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
+
+---functions---
+
+folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
+folders.deleteFolder#1c295881 folder_id:int = Updates;
    +

    API peer folders are typically used only by archived chats, and are really handy for distinguishing groups of peers, since most peer-related constructors (updates, chat info) will contain the folder_id assigned the the specified chat.

    +

    In Telegram apps, API peer folders are used only to implement the chat archive, identified by folder_id 1; all other peers are in folder_id 0 by default; no other folder_id is allowed at the moment.

    +
      +
    • folders.editPeerFolders can be used to add and remove peers from peer folders.
      • +
    • folders.deleteFolder can be used to delete peer folders, moving all peers previously present in that folder to the default 0 folder.
      • +
    +

    Both methods return an updates constructor, containing a single updateFolderPeers with the new folder_id of moved peers.
    +Clients can also receive updateFolderPeers as a normal update, generated by other clients when modifying peer folders.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/import.html b/data/corefork.telegram.org/api/import.html new file mode 100644 index 0000000000..8ebb0f6140 --- /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#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;
+
+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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/invoking.html b/data/corefork.telegram.org/api/invoking.html new file mode 100644 index 0000000000..1095dbc4d0 --- /dev/null +++ b/data/corefork.telegram.org/api/invoking.html @@ -0,0 +1,154 @@ + + + + + Calling API Methods + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Calling API Methods

    + +
    + +

    Layers

    +

    Versioning in the API is supported by so-called TL layers.

    +

    The need to add a new object constructor or to add/remove a field in a constructor creates a backwards compatibility problem for previous versions of API clients. After all, simply changing a constructor in a schema also changes its number. To address this problem, each schema update is separated into a layer.

    +

    A layer is a collection of updated methods or constructors in a TL schema. Each layer is numbered with sequentially increasing numbers starting with 2. The first layer is the base layer -- the TL schema without any changes.

    +

    There is a helper method to let the API know that a client supports the Layer layer:

    +
    invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
    +

    The helper method invokeWithLayer can be used only together with initConnection: the present layer will be saved with all other parameters of the client and any future requests will be using this saved value. See more below.

    +

    List of Available Layers

    +

    Saving Client Info

    +

    It is possible to save information about the current client on the server in conjunction with an authorization key. This may help eliminate client-side problems with certain releases on certain devices or with certain localizations, as well as eliminate the need for sending layer information in each request.

    +

    The helper method initConnection accepts client parameters. This method must be called when first calling the API after the application has restarted or in case the value of one of the parameters could have changed.

    +

    initConnection must also be called after each auth.bindTempAuthKey.

    +

    When calling this method, the current layer used by the client is also saved (the layer in which initConnection was wrapped is used). After a successful call to initConnection it is no longer necessary to wrap each API call in invokeWithLayerN.

    +

    Disabling updates

    +
    invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
    +

    invokeWithoutUpdates can be used to invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

    +

    Sequential Requests

    +

    By default, the server processes parallel requests in arbitrary order. Two helper methods exist for cases when the client needs certain requests to be processed in a certain order and intends to send a new request before the previous one is completed:

    +
    +

    invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
    +invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector query:!X = X;

    +
    +

    They may be used, for example, when a client attempts to send messages that accumulated while waiting for the Internet connection to be restored for a long time. In this case, the 32-bit number 0xcb9f372d must be added before the method number in each request, followed by a 64-bit message identifier, msg_id, which contains the previous request in the queue.

    +

    The second method is similar, except it takes several messages that must be successfully processed before the current one.

    +

    If the waiting period exceeds 0.5 seconds (this value may change in the future) and no result has appeared, the method will return the 400 MSG_WAIT_TIMEOUT error.

    +

    Helper Method Sequence

    +

    Important: if the helper methods invokeAfterMsg / invokeAfterMsgs are used together with invokeWithLayerN or other helper methods, invokeAfterMsg / invokeAfterMsgs must always be the outermost wrapper.

    +

    Data Compression

    +

    We recommend using gzip compression when calling methods to reduce the amount of network traffic.

    +

    The schema and constructor information are given in the protocol documentation.

    +

    Data Compression when Making a Request

    +

    Before transmitting a query, the string containing the entire body of the serialized high-level query (starting with the method number) must be compressed using gzip. If the resulting string is smaller than the original, it makes sense to transmit the gzip_packed constructor.

    +

    There is no point in doing the above when transmitting binary multimedia data (photos, videos) or small messages (up to 255 bytes).

    +

    Uncompressing Data

    +

    By default, the server compresses the response to any request as well as updates, in accordance with the rules stated above. If the gzip_packed constructor is received as a response in rpc_result, then the string that follows must be extracted and uncompressed. Processing then continues on the resulting new string.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/mentions.html b/data/corefork.telegram.org/api/mentions.html new file mode 100644 index 0000000000..b89ac3f48f --- /dev/null +++ b/data/corefork.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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/obtaining_api_id.html b/data/corefork.telegram.org/api/obtaining_api_id.html new file mode 100644 index 0000000000..ed6d7eb7ab --- /dev/null +++ b/data/corefork.telegram.org/api/obtaining_api_id.html @@ -0,0 +1,140 @@ + + + + + Creating your Telegram Application + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Creating your Telegram Application

    + +

    We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge.

    +
    +

    In order to ensure consistency and security across the Telegram ecosystem, +all third-party client apps must comply with the API Terms of Service.

    +
    +

    Obtaining api_id

    +

    In order to obtain an API id and develop your own application using the Telegram API you need to do the following:

    +
      +
    • Sign up for Telegram using any application.
      • +
    • Log in to your Telegram core: https://my.telegram.org.
      • +
    • Go to 'API development tools' and fill out the form.
      • +
    • You will get basic addresses as well as the api_id and api_hash parameters required for user authorization.
      • +
    • For the moment each number can only have one api_id connected to it.
      • +
    +

    We will be sending important developer notifications to the phone number that you use in this process, so please use an up-to-date number connected to your active Telegram account.

    +

    Using the api_id

    +

    Before using the MTProto Telegram API, please note that all API client libraries are strictly monitored to prevent abuse.

    +

    If you use the Telegram API for flooding, spamming, faking subscriber and view counters of channels, you will be banned forever.

    +

    Due to excessive abuse of the Telegram API, all accounts that sign up or log in using unofficial Telegram API clients are automatically put under observation to avoid violations of the Terms of Service.

    +

    If you didn't violate the Terms of Service but your account does get banned after using the API, write to recover@telegram.org explaining what you intend to do with the API, asking to unban your account.
    +Please note that emails are checked by a human, so automatically generated emails will be detected and banned.

    +

    Using Telegram's open source code

    +

    Everyone is welcome to use our open source code. We have included a sample API id with the code. This API id is limited on the server side and is not suitable for apps released to end-users — using it for anything but testing purposes will result in the API_ID_PUBLISHED_FLOOD error for your users. It is necessary that you obtain your own API id before you publish your app.

    +
    +

    Please remember to publish your code as well in order to comply with the GNU GPL licences.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/api/search.html b/data/corefork.telegram.org/api/search.html new file mode 100644 index 0000000000..017d38c3db --- /dev/null +++ b/data/corefork.telegram.org/api/search.html @@ -0,0 +1,179 @@ + + + + + Search + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Search

    + +
    + +

    Telegram allows applying detailed message filters while looking for messages in chats.

    +

    Search filters

    +
    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;
+
+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;
+
+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;
    +

    When using messages.search or messages.searchGlobal, a certain message filter may be applied.
    +This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more. +Available filters:

    + +

    The returned messages.Messages constructors contain parameters for pagination, the messages themselves and two offset_id_offset/count parameters that can be used to display a progress/total counter like photo 134 of 200.
    +For example, when displaying the chat photo gallery, we could display a photo ${offset_id_offset} of ${count} indicator on top.

    +

    Search counters

    +
    messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
+
+---functions---
+
+messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
    +

    Chat counters with filters can also be returned without fetching the actual messages, as seen in the schema above.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/srp.html b/data/corefork.telegram.org/api/srp.html new file mode 100644 index 0000000000..94f2217ee9 --- /dev/null +++ b/data/corefork.telegram.org/api/srp.html @@ -0,0 +1,307 @@ + + + + + Two-factor authentication + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Two-factor authentication

    + +
    + +

    Telegram uses the Secure Remote Password protocol version 6a to implement 2FA.

    +

    Example impementation: tdlib.

    +

    Checking the password with SRP

    +

    To login to an account protected by a 2FA password or to perform some other actions (like changing channel owner), you will need to verify the user's knowledge of the current 2FA account password.

    +

    To do this, first the client needs to obtain SRP parameters and the KDF algorithm to use to check the validity of the password via account.getPassword method. For now, only the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow algorithm is supported, so we'll only explain that.

    +

    Then, after the user provides a password, the client should generate an InputCheckPasswordSRP object using SRP and a specific KDF algorithm as shown below and pass it to appropriate method (e.g. auth.checkPassword in case of authorization).

    +

    This extension of the SRP protocol uses the password-based PBKDF2 with 100000 iterations using sha512 (PBKDF2HMACSHA512iter100000). +PBKDF2 is used to additionally rehash the x parameter, obtained using a method similar to the one described in RFC 2945 (H(s | H ( I | password | I) | s) instead of H(s | H ( I | ":" | password)) (see below).

    +

    Here, | denotes concatenation and + denotes the arithmetical operator +. +In all cases where concatenation of numbers passed to hashing functions is done, the numbers must be used in big-endian form, padded to 2048 bits; all maths is modulo p. +Instead of I, salt1 will be used (see SRP protocol). +Instead of s, salt2 will be used (see SRP protocol).

    +

    The main hashing function H is sha256:

    +
      +
    • H(data) := sha256(data)
      • +
    +

    The salting hashing function SH is defined as follows:

    +
      +
    • SH(data, salt) := H(salt | data | salt)
      • +
    +

    The primary password hashing function is defined as follows:

    +
      +
    • PH1(password, salt1, salt2) := SH(SH(password, salt1), salt2)
      • +
    +

    The secondary password hashing function is defined as follows:

    +
      +
    • PH2(password, salt1, salt2) := SH(pbkdf2(sha512, PH1(password, salt1, salt2), salt1, 100000), salt2)
      • +
    +

    Client-side, the following parameters are extracted from the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow object, contained in the account.password object.

    +
      +
    • +

      g := algo.g

      +
      • +
    • +

      p := algo.p +The client is expected to check whether p 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 to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

      +

      If the client has an inadequate random number generator, it makes sense to use the secure_random of account.password as additional seed.

      +
      • +
    • +

      password := (user-provided password)

      +
      • +
    • +

      salt1 := algo.salt1

      +
      • +
    • +

      salt2 := algo.salt2

      +
      • +
    • +

      g_b := srp_B +srp_B and srp_id are extracted from the account.password object.

      +
      • +
    +

    The k parameter is generated, both on client and server:

    +
      +
    • k := H(p | g)
      • +
    +

    The shared param u is generated: the client does this, and the server does the same with the g_a we will send him later (see below)

    +
      +
    • u := H(g_a | g_b)
      • +
    +

    The final parameters are generated client-side only:

    +
      +
    • x := PH2(password, salt1, salt2)
      • +
    • v := pow(g, x) mod p
      • +
    +

    The server already has v, from when we set the password.

    +

    A final shared param is generated, for commodity:

    +
      +
    • k_v := (k * v) mod p
      • +
    +

    Finally, the key exchange process starts on both parties.

    +

    The client computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and generates:

    +
      +
    • g_a := pow(g, a) mod p.
      • +
    +

    The server computes a 2048-bit number b using sufficient entropy and generates the g_b parameter that was sent to us (see above).

    +
      +
    • g_b := (k_v + (pow(g, b) mod p)) mod p
      • +
    +

    Finally, the SRP session keys are generated:

    +

    Client side:

    +
      +
    • t := (g_b - k_v) mod p (positive modulo, if the result is negative increment by p)
      • +
    • s_a := pow(t, a + u * x) mod p
      • +
    • k_a := H(s_a)
      • +
    +

    Server side:

    +
      +
    • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
      • +
    • k_b := H(s_b)
      • +
    +

    Since:

    +
      +
    • g_b := (k_v + (pow(g, b) mod p)) mod p
      • +
    • t := (g_b - k_v) mod p
      • +
    • t := ((k_v + (pow(g, b) mod p)) - k_v) mod p
      • +
    • t := pow(g, b) mod p
      • +
    • s_a := pow(t, a + u * x) mod p
      • +
    • s_a := pow(pow(g, b) mod p, a + u * x) mod p
      • +
    +

    And:

    +
      +
    • +

      g_a := pow(g, a) mod p

      +
      • +
    • +

      v := pow(g, x) mod p

      +
      • +
    • +

      s_b := pow(g_a * (pow(v, u) mod p), b) mod p

      +
      • +
    • +

      s_b := pow((pow(g, a) mod p) * (pow(pow(g, x) mod p, u) mod p), b) mod p

      +
      • +
    • +

      s_b := pow(pow(g, a + x * u) mod p, b) mod p

      +
      • +
    • +

      s_b := pow(pow(g, b) mod p, a + u * x) mod p

      +
      • +
    • +

      s_a := pow(pow(g, b) mod p, a + u * x) mod p

      +
      • +
    +

    This means:

    +
      +
    • s_b === s_a
      • +
    • k_b === k_a
      • +
    +

    Finally, as per SRP:

    +
      +
    • M1 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_a)
      • +
    +

    M1 is passed to inputCheckPasswordSRP, along with g_a (as A parameter) and the srp_id, extracted from the account.password object.

    +

    The server then computes:

    +
      +
    • M2 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_b)
      • +
    +

    Since we said that:

    +
      +
    • s_b === s_a
      • +
    • k_b === k_a
      • +
    +

    This means, if everything was done correctly,

    +
      +
    • M1 === M2
      • +
    +

    If the password isn't correct, 400 PASSWORD_HASH_INVALID will be returned.

    +

    Setting a new 2FA password

    +

    To set a new 2FA password use the account.updatePasswordSettings method.
    +If a password is already set, generate an InputCheckPasswordSRP object as per checking passwords with SRP, and insert it in the password field of the account.updatePasswordSettings method.
    +To remove the current password, pass an empty new_password_hash in the account.PasswordInputSettings object.

    +

    To set a new password, use the SRP parameters and the KDF algorithm obtained using account.getPassword when generating the password field. +Then generate a new new_password_hash using the KDF algorithm specified in the new_settings, just append 32 sufficiently random bytes to the salt1, first. +Proceed as for checking passwords with SRP, just stop at the generation of the v parameter, and use it as new_password_hash:

    +
      +
    • v := pow(g, x) mod p
      • +
    +

    As usual in big endian form, padded to 2048 bits.

    +

    Email verification

    +

    When setting up two-factor authorization, it is recommended to set up a recovery email, to allow recovery of the password through the user's email address, in case they forget it.

    +

    To set up a recovery email, it must first be verified. +This can be done directly when setting the new password using account.updatePasswordSettings by setting the email parameter and flag in the account.passwordInputSettings constructor. +If the email isn't verified, an EMAIL_UNCONFIRMED_X 400 error will be returned, where X is the length of the verification code that was just sent to the email. +Use account.confirmPasswordEmail to enter the received verification code and enable the recovery email. +Use account.resendPasswordEmail to resend the verification code. +Use account.cancelPasswordEmail to cancel the verification code.

    +

    To get the current recovery email, use account.getPasswordSettings.

    +

    Email recovery

    +

    In order to recover a forgotten 2FA password, an email must be sent to the previously specified address using the auth.requestPasswordRecovery method.
    +Use auth.checkRecoveryPassword to make sure that the user provided a valid code.
    +Then use auth.recoverPassword with the received code to delete the current 2FA password, to set a new one follow these instructions.

    +

    Password reset

    +
    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;
+account.declinePasswordReset#4c9409f6 = Bool;
    +

    If the user is already logged in and has forgotten their 2FA password, account.resetPassword can be used to initiate a password reset.
    +On success, the call will initially return a account.resetPasswordRequestedWait constructor and start a 7-day server-side timer, during which the user can abort the reset process using a button sent by the Telegram service account or directly in-UI using account.declinePasswordReset.

    +

    When the time comes, account.resetPassword is invoked once more, returning a account.resetPasswordOk to indicate that the password was successfully reset.

    +

    If the user recently requested a password reset that was canceled, account.resetPasswordFailedWait will be returned by the initial account.resetPassword call, and they must wait until the specified date before requesting another reset.

    +

    Note that if the user already knows their 2FA password and simply wants to disable 2FA, the same process used to enable the password must also be used to disable it ».

    +

    Related pages

    +

    SRP design

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/api/threads.html b/data/corefork.telegram.org/api/threads.html new file mode 100644 index 0000000000..9cfb6dc8ed --- /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#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;
+
+---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#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;
+
+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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + 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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + diff --git a/data/corefork.telegram.org/cdn.html b/data/corefork.telegram.org/cdn.html deleted file mode 100644 index 0e92683de7..0000000000 --- a/data/corefork.telegram.org/cdn.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - 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.
    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.sentAppCode b/data/corefork.telegram.org/constructor/auth.sentAppCode deleted file mode 100644 index 1286ea89c1..0000000000 --- a/data/corefork.telegram.org/constructor/auth.sentAppCode +++ /dev/null @@ -1,163 +0,0 @@ - - - - - auth.sentAppCode - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    auth.sentAppCode

    - -

    Contains info on a confirmation code message sent via Telegram.

    -

    You can force resending the message via SMS by invoking the method auth.sendSms.

    -

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

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    phone_registeredBoolThe given number corresponds to a registered Telegram user
    phone_code_hashstringMessage identifier
    send_call_timeoutintDelay in seconds before calling auth.sendCall
    is_passwordBoolThe sent code is a text password
    -

    Type

    -

    auth.SentCode

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html deleted file mode 100644 index 2942d29b74..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleAdmin - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    channelAdminLogEventActionParticipantToggleAdmin

    - -

    The admin rights of a user were changed

    -

    - -
    -
    channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    prev_participantChannelParticipantPrevious admin rights
    new_participantChannelParticipantNew admin rights
    -

    Type

    -

    ChannelAdminLogEventAction

    -

    Related pages

    -

    Admin, banned, default rights

    -

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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html deleted file mode 100644 index c7543fb13c..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html b/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html new file mode 100644 index 0000000000..3ccf34c775 --- /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

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/updateDcOptions.html b/data/corefork.telegram.org/constructor/channelParticipantsBanned.html similarity index 89% rename from data/corefork.telegram.org/constructor/updateDcOptions.html rename to data/corefork.telegram.org/constructor/channelParticipantsBanned.html index 2deded5beb..19b3882962 100644 --- a/data/corefork.telegram.org/constructor/updateDcOptions.html +++ b/data/corefork.telegram.org/constructor/channelParticipantsBanned.html @@ -2,12 +2,12 @@ - updateDcOptions + channelParticipantsBanned - - + + - + @@ -36,10 +36,10 @@
    -
    -

    updateDcOptions

    +
    +

    channelParticipantsBanned

    -

    Changes in the data center configuration options.

    +

    Fetch only banned participants

    • @@ -52,7 +52,7 @@
    -
    updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;

    +
    channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;

    Parameters

    @@ -64,14 +64,14 @@ - - - + + +
    dc_optionsVector<DcOption>New connection optionsqstringOptional filter for searching banned participants by name (otherwise empty)

    Type

    -

    Update

    +

    ChannelParticipantsFilter

    diff --git a/data/corefork.telegram.org/constructor/channelParticipantsBots.html b/data/corefork.telegram.org/constructor/channelParticipantsBots.html new file mode 100644 index 0000000000..166869a4d8 --- /dev/null +++ b/data/corefork.telegram.org/constructor/channelParticipantsBots.html @@ -0,0 +1,132 @@ + + + + + channelParticipantsBots + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    channelParticipantsBots

    + +

    Fetch only bot participants

    +

    + +
    +
    channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;

    +

    Parameters

    +

    This constructor does not require any parameters.

    +

    Type

    +

    ChannelParticipantsFilter

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsContacts.html b/data/corefork.telegram.org/constructor/channelParticipantsContacts.html new file mode 100644 index 0000000000..376476d575 --- /dev/null +++ b/data/corefork.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

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantsKicked.html b/data/corefork.telegram.org/constructor/channelParticipantsKicked.html new file mode 100644 index 0000000000..001fe0376f --- /dev/null +++ b/data/corefork.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

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/channelParticipantCreator.html b/data/corefork.telegram.org/constructor/channelParticipantsMentions.html similarity index 79% rename from data/corefork.telegram.org/constructor/channelParticipantCreator.html rename to data/corefork.telegram.org/constructor/channelParticipantsMentions.html index 27585a0886..cc4d465f7a 100644 --- a/data/corefork.telegram.org/constructor/channelParticipantCreator.html +++ b/data/corefork.telegram.org/constructor/channelParticipantsMentions.html @@ -2,12 +2,12 @@ - channelParticipantCreator + channelParticipantsMentions - - + + - + @@ -36,10 +36,11 @@
    -
    -

    channelParticipantCreator

    +
    +

    channelParticipantsMentions

    -

    Channel/supergroup creator

    +

    This filter is used when looking for supergroup members to mention.
    +This filter will automatically remove anonymous admins, and return even non-participant users that replied to a specific thread through the comment section of a channel.

    • @@ -52,7 +53,7 @@
    -
    channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;

    +
    channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

    Parameters

    @@ -69,24 +70,22 @@ - - - - - - - - - - - + - + + + + + +
    Flags, see TL conditional fields
    user_idlongUser ID
    admin_rightsChatAdminRightsCreator admin rights
    rankq flags.0?stringThe role (rank) of the group creator in the group: just an arbitrary string, admin by defaultFilter by user name or username
    top_msg_idflags.1?intLook only for users that posted in this thread

    Type

    -

    ChannelParticipant

    +

    ChannelParticipantsFilter

    +

    Related pages

    +

    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/channelParticipantsRecent.html b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html similarity index 98% rename from data/core.telegram.org/constructor/channelParticipantsRecent.html rename to data/corefork.telegram.org/constructor/channelParticipantsRecent.html index 9bd1b9de9b..bc70ccb0a8 100644 --- a/data/core.telegram.org/constructor/channelParticipantsRecent.html +++ b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html @@ -95,9 +95,9 @@
    -
    Platform
    +
    Platform
    @@ -114,7 +114,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/constructor/textUnderline.html b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html similarity index 89% rename from data/corefork.telegram.org/constructor/textUnderline.html rename to data/corefork.telegram.org/constructor/channelParticipantsSearch.html index ced69f125c..aa42384590 100644 --- a/data/corefork.telegram.org/constructor/textUnderline.html +++ b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html @@ -2,12 +2,12 @@ - textUnderline + channelParticipantsSearch - - + + - + @@ -36,10 +36,10 @@
    -
    -

    textUnderline

    +
    +

    channelParticipantsSearch

    -

    Underlined text

    +

    Query participants by name

    • @@ -52,7 +52,7 @@
    -
    textUnderline#c12622c4 text:RichText = RichText;

    +
    channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;

    Parameters

    @@ -64,14 +64,14 @@ - - - + + +
    textRichTextTextqstringSearch query

    Type

    -

    RichText

    +

    ChannelParticipantsFilter

    diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html b/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html deleted file mode 100644 index 99518e6e15..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.recentStickers b/data/corefork.telegram.org/constructor/help.countriesList similarity index 84% rename from data/corefork.telegram.org/constructor/messages.recentStickers rename to data/corefork.telegram.org/constructor/help.countriesList index b1f08bb9a8..24b6a0db08 100644 --- a/data/corefork.telegram.org/constructor/messages.recentStickers +++ b/data/corefork.telegram.org/constructor/help.countriesList @@ -2,12 +2,12 @@ - messages.recentStickers + help.countriesList - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.recentStickers

    +
    +

    help.countriesList

    -

    Recently used stickers

    +

    Name, ISO code, localized name and phone codes/patterns of all available countries

    • @@ -52,7 +52,7 @@
    -
    messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;

    +
    help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

    Parameters

    @@ -64,29 +64,19 @@ + + + + + - + - - - - - - - - - - - - - - -
    countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
    hashlongint Hash for pagination, for more info click here
    packsVector<StickerPack>Emojis associated to stickers
    stickersVector<Document>Recent stickers
    datesVector<int>When was each sticker last used

    Type

    -

    messages.RecentStickers

    +

    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..9ef15126cb --- /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

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/inputAppEvent.html b/data/corefork.telegram.org/constructor/inputAppEvent.html deleted file mode 100644 index 17f2ab5451..0000000000 --- a/data/corefork.telegram.org/constructor/inputAppEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputAppEvent - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    inputAppEvent

    - -

    Event that occured in the application.

    -

    - -
    -
    inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    timedoubleClient's exact timestamp for the event
    typestringType of event
    peerlongArbitrary numeric value for more convenient selection of certain event types, or events referring to a certain object
    dataJSONValueDetails of the event
    -

    Type

    -

    InputAppEvent

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockAudio.html b/data/corefork.telegram.org/constructor/inputChannel.html similarity index 88% rename from data/corefork.telegram.org/constructor/pageBlockAudio.html rename to data/corefork.telegram.org/constructor/inputChannel.html index b6572ee95f..c00f8a6ef9 100644 --- a/data/corefork.telegram.org/constructor/pageBlockAudio.html +++ b/data/corefork.telegram.org/constructor/inputChannel.html @@ -2,12 +2,12 @@ - pageBlockAudio + inputChannel - - + + - + @@ -36,10 +36,10 @@
    -
    -

    pageBlockAudio

    +
    +

    inputChannel

    -

    Audio

    +

    Represents a channel

    • @@ -52,7 +52,7 @@
    -
    pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;

    +
    inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;

    Parameters

    @@ -64,22 +64,22 @@ - + - + - - - + + +
    audio_idchannel_id longAudio ID (to be fetched from the container page constructorChannel ID
    captionPageCaptionAudio captionaccess_hashlongAccess hash taken from the channel constructor

    Type

    -

    PageBlock

    +

    InputChannel

    Related pages

    -

    page

    -

    Instant view page

    +

    channel

    +

    Channel/supergroup info

    diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html b/data/corefork.telegram.org/constructor/inputChannelEmpty.html similarity index 91% rename from data/corefork.telegram.org/constructor/topPeerCategoryChannels.html rename to data/corefork.telegram.org/constructor/inputChannelEmpty.html index 6e95852db4..742f924b98 100644 --- a/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html +++ b/data/corefork.telegram.org/constructor/inputChannelEmpty.html @@ -2,12 +2,12 @@ - topPeerCategoryChannels + inputChannelEmpty - - + + - + @@ -36,10 +36,10 @@
    -
    -

    topPeerCategoryChannels

    +
    +

    inputChannelEmpty

    -

    Most frequently visited channels

    +

    Represents the absence of a channel

    • @@ -52,11 +52,11 @@
    -
    topPeerCategoryChannels#161d9628 = TopPeerCategory;

    +
    inputChannelEmpty#ee8c1e86 = InputChannel;

    Parameters

    This constructor does not require any parameters.

    Type

    -

    TopPeerCategory

    +

    InputChannel

    diff --git a/data/corefork.telegram.org/constructor/inputChannelFromMessage.html b/data/corefork.telegram.org/constructor/inputChannelFromMessage.html new file mode 100644 index 0000000000..659b02a3ee --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputChannelFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputChannelFromMessage + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    inputChannelFromMessage

    + +

    Defines a min channel that was seen in a certain message of a certain chat.

    +

    + +
    +
    inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

    +

    Parameters

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    NameTypeDescription
    peerInputPeerThe chat where the channel was seen
    msg_idintThe message ID in the chat where the channel was seen
    channel_idlongThe channel ID
    +

    Type

    +

    InputChannel

    +

    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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html b/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html deleted file mode 100644 index 0f8478a7cb..0000000000 --- a/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputDocumentFileLocation - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    inputDocumentFileLocation

    - -

    Document location (video, voice, audio, basically every type except photo)

    -

    - -
    -
    inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    idlongDocument ID
    access_hashlongaccess_hash parameter from the document constructor
    file_referencebytesFile reference
    thumb_sizestringThumbnail size to download the thumbnail
    -

    Type

    -

    InputFileLocation

    -

    Related pages

    -

    document

    -

    Document

    -

    File references

    -

    How to handle file references.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaPhoto.html b/data/corefork.telegram.org/constructor/inputMediaPhoto.html deleted file mode 100644 index 2ee06a9ef7..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html b/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html new file mode 100644 index 0000000000..9eba91f8fe --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputPeerChannelFromMessage + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    inputPeerChannelFromMessage

    + +

    Defines a min channel that was seen in a certain message of a certain chat.

    +

    + +
    +
    inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

    +

    Parameters

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    NameTypeDescription
    peerInputPeerThe chat where the channel's message was seen
    msg_idintThe message ID
    channel_idlongThe identifier of the channel that was seen
    +

    Type

    +

    InputPeer

    +

    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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/peerUser.html b/data/corefork.telegram.org/constructor/inputPeerChat.html similarity index 91% rename from data/corefork.telegram.org/constructor/peerUser.html rename to data/corefork.telegram.org/constructor/inputPeerChat.html index 2949ab048b..10f8531507 100644 --- a/data/corefork.telegram.org/constructor/peerUser.html +++ b/data/corefork.telegram.org/constructor/inputPeerChat.html @@ -2,12 +2,12 @@ - peerUser + inputPeerChat - - + + - + @@ -36,10 +36,10 @@
    -
    -

    peerUser

    +
    +

    inputPeerChat

    -

    Chat partner

    +

    Defines a chat for further interaction.

    • @@ -52,7 +52,7 @@
    -
    peerUser#59511722 user_id:long = Peer;

    +
    inputPeerChat#35a95cb9 chat_id:long = InputPeer;

    Parameters

    @@ -64,14 +64,14 @@ - + - +
    user_idchat_id longUser identifierChat idientifier

    Type

    -

    Peer

    +

    InputPeer

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

    inputPeerEmpty

    + +

    An empty constructor, no user or chat is defined.

    +

    + +
    +
    inputPeerEmpty#7f3b18ea = InputPeer;

    +

    Parameters

    +

    This constructor does not require any parameters.

    +

    Type

    +

    InputPeer

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/constructor/inputPeerSelf.html b/data/corefork.telegram.org/constructor/inputPeerSelf.html similarity index 98% rename from data/core.telegram.org/constructor/inputPeerSelf.html rename to data/corefork.telegram.org/constructor/inputPeerSelf.html index 45a02fe522..415b6c27fc 100644 --- a/data/core.telegram.org/constructor/inputPeerSelf.html +++ b/data/corefork.telegram.org/constructor/inputPeerSelf.html @@ -95,9 +95,9 @@
    -
    Platform
    +
    Platform
    @@ -114,7 +114,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/constructor/updateGroupCall.html b/data/corefork.telegram.org/constructor/inputPeerUser.html similarity index 87% rename from data/corefork.telegram.org/constructor/updateGroupCall.html rename to data/corefork.telegram.org/constructor/inputPeerUser.html index 778494b8d2..9cb02e4c7e 100644 --- a/data/corefork.telegram.org/constructor/updateGroupCall.html +++ b/data/corefork.telegram.org/constructor/inputPeerUser.html @@ -2,12 +2,12 @@ - updateGroupCall + inputPeerUser - - + + - + @@ -36,10 +36,10 @@
    -
    -

    updateGroupCall

    +
    +

    inputPeerUser

    -

    A new groupcall was started

    +

    Defines a user for further interaction.

    • @@ -52,7 +52,7 @@
    -
    updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;

    +
    inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;

    Parameters

    @@ -64,22 +64,22 @@ - + - + - - - + + +
    chat_iduser_id longThe channel/supergroup where this group call or livestream takes placeUser identifier
    callGroupCallInfo about the group call or livestreamaccess_hashlongaccess_hash value from the user constructor

    Type

    -

    Update

    +

    InputPeer

    Related pages

    -

    Channels

    -

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

    +

    user

    +

    Indicates info about a certain user

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

    inputPeerUserFromMessage

    + +

    Defines a min user that was seen in a certain message of a certain chat.

    +

    + +
    +
    inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;

    +

    Parameters

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    NameTypeDescription
    peerInputPeerThe chat where the user was seen
    msg_idintThe message ID
    user_idlongThe identifier of the user that was seen
    +

    Type

    +

    InputPeer

    +

    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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html deleted file mode 100644 index 70ea4bbca8..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyAddedByPhone - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    inputPrivacyKeyAddedByPhone

    - -

    Whether people can add you to their contact list by your phone number

    -

    - -
    -
    inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Type

    -

    InputPrivacyKey

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/photoSizeEmpty.html b/data/corefork.telegram.org/constructor/inputUser.html similarity index 87% rename from data/corefork.telegram.org/constructor/photoSizeEmpty.html rename to data/corefork.telegram.org/constructor/inputUser.html index f8102cb86a..52a3e6c9ba 100644 --- a/data/corefork.telegram.org/constructor/photoSizeEmpty.html +++ b/data/corefork.telegram.org/constructor/inputUser.html @@ -2,12 +2,12 @@ - photoSizeEmpty + inputUser - - + + - + @@ -36,10 +36,10 @@
    -
    -

    photoSizeEmpty

    +
    +

    inputUser

    -

    Empty constructor. Image with this thumbnail is unavailable.

    +

    Defines a user for further interaction.

    • @@ -52,7 +52,7 @@
    -
    photoSizeEmpty#e17e23c type:string = PhotoSize;

    +
    inputUser#f21158c6 user_id:long access_hash:long = InputUser;

    Parameters

    @@ -64,17 +64,22 @@ - - - + + + + + + + +
    typestringThumbnail type (see. photoSize)user_idlongUser identifier
    access_hashlongaccess_hash value from the user constructor

    Type

    -

    PhotoSize

    +

    InputUser

    Related pages

    -

    photoSize

    -

    Image description.

    +

    user

    +

    Indicates info about a certain user

    diff --git a/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html b/data/corefork.telegram.org/constructor/inputUserEmpty.html similarity index 92% rename from data/corefork.telegram.org/constructor/inputStickerSetEmpty.html rename to data/corefork.telegram.org/constructor/inputUserEmpty.html index 82d1dd0ecc..5bd866e5b4 100644 --- a/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html +++ b/data/corefork.telegram.org/constructor/inputUserEmpty.html @@ -2,12 +2,12 @@ - inputStickerSetEmpty + inputUserEmpty - - + + - + @@ -36,10 +36,10 @@
    -
    -

    inputStickerSetEmpty

    +
    +

    inputUserEmpty

    -

    Empty constructor

    +

    Empty constructor, does not define a user.

    • @@ -52,11 +52,11 @@
    -
    inputStickerSetEmpty#ffb62b95 = InputStickerSet;

    +
    inputUserEmpty#b98886cf = InputUser;

    Parameters

    This constructor does not require any parameters.

    Type

    -

    InputStickerSet

    +

    InputUser

    diff --git a/data/corefork.telegram.org/constructor/inputUserFromMessage.html b/data/corefork.telegram.org/constructor/inputUserFromMessage.html new file mode 100644 index 0000000000..28882e2c34 --- /dev/null +++ b/data/corefork.telegram.org/constructor/inputUserFromMessage.html @@ -0,0 +1,160 @@ + + + + + inputUserFromMessage + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    inputUserFromMessage

    + +

    Defines a min user that was seen in a certain message of a certain chat.

    +

    + +
    +
    inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

    +

    Parameters

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    NameTypeDescription
    peerInputPeerThe chat where the user was seen
    msg_idintThe message ID
    user_idlongThe identifier of the user that was seen
    +

    Type

    +

    InputUser

    +

    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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/constructor/pageBlockDivider.html b/data/corefork.telegram.org/constructor/inputUserSelf.html similarity index 92% rename from data/corefork.telegram.org/constructor/pageBlockDivider.html rename to data/corefork.telegram.org/constructor/inputUserSelf.html index 15f4efb3bb..3721eaf005 100644 --- a/data/corefork.telegram.org/constructor/pageBlockDivider.html +++ b/data/corefork.telegram.org/constructor/inputUserSelf.html @@ -2,12 +2,12 @@ - pageBlockDivider + inputUserSelf - - + + - + @@ -36,10 +36,10 @@
    -
    -

    pageBlockDivider

    +
    +

    inputUserSelf

    -

    An empty block separating a page

    +

    Defines the current user.

    • @@ -52,11 +52,11 @@
    -
    pageBlockDivider#db20b188 = PageBlock;

    +
    inputUserSelf#f7c1b13f = InputUser;

    Parameters

    This constructor does not require any parameters.

    Type

    -

    PageBlock

    +

    InputUser

    diff --git a/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html b/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html deleted file mode 100644 index a0cfa41cc8..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.sentMessageLink b/data/corefork.telegram.org/constructor/messages.affectedHistory similarity index 86% rename from data/corefork.telegram.org/constructor/messages.sentMessageLink rename to data/corefork.telegram.org/constructor/messages.affectedHistory index 746af76cc9..ba05fdf2ee 100644 --- a/data/corefork.telegram.org/constructor/messages.sentMessageLink +++ b/data/corefork.telegram.org/constructor/messages.affectedHistory @@ -2,12 +2,12 @@ - messages.sentMessageLink + messages.affectedHistory - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.sentMessageLink

    +
    +

    messages.affectedHistory

    -

    Info on successfully sent message and on changes links.

    +

    Affected part of communication history with the user or in a chat.

    • @@ -52,7 +52,7 @@
    -
    Constructor schema is available as of layer 24. Switch »

    +
    messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

    Parameters

    @@ -64,34 +64,24 @@ - - - - - - - - - - - + - + - + - - - + + +
    idintMessage ID
    dateintDate of sending
    pts intNew value of pts parameter of a current stateNumber of events occured in a text box
    seqpts_count intNew value of seq parameter of a current stateNumber of affected events
    linksVector<contacts.Link>List of changes linksoffsetintIf 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.SentMessage

    +

    messages.AffectedHistory

    diff --git a/data/corefork.telegram.org/constructor/peerLocated.html b/data/corefork.telegram.org/constructor/peerLocated.html deleted file mode 100644 index 7662f27e85..0000000000 --- a/data/corefork.telegram.org/constructor/peerLocated.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/photoPathSize.html b/data/corefork.telegram.org/constructor/photoSize.html similarity index 87% rename from data/corefork.telegram.org/constructor/photoPathSize.html rename to data/corefork.telegram.org/constructor/photoSize.html index 73f9d9cc68..18bf11aba2 100644 --- a/data/corefork.telegram.org/constructor/photoPathSize.html +++ b/data/corefork.telegram.org/constructor/photoSize.html @@ -2,12 +2,12 @@ - photoPathSize + photoSize - - + + - + @@ -36,10 +36,10 @@
    -
    -

    photoPathSize

    +
    +

    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.

    +

    Image description.

    • @@ -52,7 +52,7 @@
    -
    photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

    +
    photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;

    Parameters

    @@ -66,17 +66,29 @@ - + - - - + + + + + + + + + + + + +
    type stringAlways jThumbnail type
    bytesbytesCompressed SVG path payload, see here for decompression instructionswintImage width
    hintImage height
    sizeintFile size

    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/savedPhoneContact.html b/data/corefork.telegram.org/constructor/savedPhoneContact.html deleted file mode 100644 index c8af629587..0000000000 --- a/data/corefork.telegram.org/constructor/savedPhoneContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - savedPhoneContact - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    savedPhoneContact

    - -

    Saved contact

    -

    - -
    -
    savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    phonestringPhone number
    first_namestringFirst name
    last_namestringLast name
    dateintDate added
    -

    Type

    -

    SavedContact

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/secureSecretSettings.html b/data/corefork.telegram.org/constructor/secureSecretSettings.html deleted file mode 100644 index 7f0a5ef253..0000000000 --- a/data/corefork.telegram.org/constructor/secureSecretSettings.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/constructor/chatEmpty.html b/data/corefork.telegram.org/constructor/true.html similarity index 90% rename from data/corefork.telegram.org/constructor/chatEmpty.html rename to data/corefork.telegram.org/constructor/true.html index c3379dfd9d..401f973fb1 100644 --- a/data/corefork.telegram.org/constructor/chatEmpty.html +++ b/data/corefork.telegram.org/constructor/true.html @@ -2,12 +2,12 @@ - chatEmpty + true - - + + - + @@ -36,10 +36,10 @@
    -
    -

    chatEmpty

    +
    +

    true

    -

    Empty constructor, group doesn't exist

    +

    See predefined identifiers.

    • @@ -52,26 +52,13 @@
    -
    chatEmpty#29562865 id:long = Chat;

    +
    true#3fedd339 = True;

    Parameters

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

    This constructor does not require any parameters.

    Type

    -

    Chat

    +

    True

    +

    Related pages

    +

    TL-formal

    diff --git a/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded b/data/corefork.telegram.org/constructor/updateMessageID.html similarity index 85% rename from data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded rename to data/corefork.telegram.org/constructor/updateMessageID.html index 226a04ab94..f5539d8dc5 100644 --- a/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded +++ b/data/corefork.telegram.org/constructor/updateMessageID.html @@ -2,12 +2,12 @@ - upload.cdnFileReuploadNeeded + updateMessageID - - + + - + @@ -36,10 +36,10 @@
    -
    -

    upload.cdnFileReuploadNeeded

    +
    +

    updateMessageID

    -

    The file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.

    +

    Sent message with random_id client identifier was assigned an identifier.

    • @@ -52,7 +52,7 @@
    -
    upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;

    +
    updateMessageID#4e90bfd6 id:int random_id:long = Update;

    Parameters

    @@ -64,16 +64,22 @@ - - - + + + + + + + +
    request_tokenbytesRequest token (see CDN)idintid identifier of a respective Message
    random_idlongPreviuosly transferred client random_id identifier

    Type

    -

    upload.CdnFile

    +

    Update

    Related pages

    -

    Encrypted CDNs for Speed and Security

    +

    Message

    +

    Object describing a message.

    diff --git a/data/corefork.telegram.org/css/telegram-extra.css b/data/corefork.telegram.org/css/telegram-extra.css deleted file mode 100644 index 6b408d1ae4..0000000000 --- a/data/corefork.telegram.org/css/telegram-extra.css +++ /dev/null @@ -1,246 +0,0 @@ -.telegram-passport-wrap { - overflow: hidden; -} -.telegram-passport-form { - position: relative; -} -.telegram-passport-form .control-label { - line-height: 20px; - padding-top: 11px; -} -.telegram-passport-header { - font-size: 18px; - line-height: 27px; -} -.telegram-passport-greeting { - margin-right: 10px; -} -.telegram-passport-greeting a, -.telegram-passport-greeting a:hover { - color: inherit; -} -.telegram-passport-logout { - font-size: 16px; - font-weight: normal; -} -.telegram-passport-login-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-relogin-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-pending { - padding: 20px 0 40px; - text-align: center; -} -.telegram-passport-block-header, -.telegram-passport-item { - border-bottom: 1px solid #e7e7e7; -} -.telegram-passport-block-header, -.telegram-passport-item-name, -.telegram-passport-item-value { - padding: 15px 0; - line-height: 20px; -} -.telegram-passport-block-header { - margin: 25px 0 0; -} -.telegram-passport-item-name { - margin-right: 15px; - margin-bottom: -5px; - padding-bottom: 0; - float: left; -} -.telegram-passport-item-files, -.telegram-passport-item-value { - clear: left; - font-weight: bold; -} -.telegram-passport-item-value { - transition: color .12s linear; -} -.telegram-passport-item-files { - padding: 6px 0; -} -.telegram-passport-item-file { - padding: 6px 0; - min-height: 60px; -} -.telegram-passport-item .telegram-passport-checkbox-right .checkbox-input { - margin: 0; -} -.telegram-passport-item .telegram-passport-checkbox-right { - float: right; - margin: 40px -5px 10px; - padding: 5px; -} -.telegram-passport-item-files .checkbox-item-block { - margin: 6px 0; -} -.telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; -} -.telegram-passport-scan-thumb { - display: inline-block; - width: 64px; - height: 48px; - background: #f7f7f7 no-repeat center; - background-size: cover; - float: left; - border-radius: 3px; - margin-right: 15px; -} -.telegram-passport-scan-name { - display: inline-block; - font-size: 14px; - padding: 3px 0 0; - transition: color .12s linear; - color: #2e87ca; -} -.telegram-passport-scan-size { - font-size: 13px; - padding: 1px 0 0; - font-weight: normal; - transition: color .12s linear; - color: #999; -} -.telegram-passport-item-value, -.telegram-passport-scan-info { - margin-right: 42px; -} -.telegram-passport-item .checkbox-item-block .checkbox-label { - transition: color .12s linear; -} -.telegram-passport-item.item-rejected .telegram-passport-item-value, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-name, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-size, -.telegram-passport-item .checkbox-item-block.item-rejected .checkbox-label { - color: #c93c3c; -} - -.telegram-passport-item .checkbox-item-block .checkbox-input-icon:before { - border-color: #eb5454; - background-color: #eb5454; - background-position: -3px -119px; -} -.telegram-passport-item .checkbox-item-block input.checkbox:checked + .checkbox-input .ripple { - background-color: rgba(235, 84, 84, .2); -} -.telegram-passport-errors-wrap { - text-align: right; - margin: 20px 16px 0; -} -.btn.telegram-passport-errors { - font-size: 15px; - font-weight: 500; - line-height: 20px; - border-radius: 6px; - background-color: transparent; - padding: 8px 16px 10px; - margin: 4px -16px; - border: none; - color: #c93c3c; - position: relative; - z-index: 1; -} -.btn.telegram-passport-errors:hover { - background-color: #f7e3e3; -} -.btn.telegram-passport-errors:focus { - outline: none; -} -.btn.telegram-passport-errors:active { - box-shadow: none; -} -.telegram-passport-errors-icon { - display: inline-block; - vertical-align: top; - width: 18px; - height: 19px; - margin: 1px 12px 0 0; - background: url(/img/passport_bug.png) no-repeat 0 0; -} -@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi) { - .telegram-passport-errors-icon { - background-image: url(/img/passport_bug_2x.png); - background-size: 18px 19px; - } -} -.telegram-passport-errors-sent { - font-size: 14px; - line-height: 20px; - padding: 13px 24px 0 0; - color: #999; - transition: opacity .12s linear; - opacity: 0; -} -.telegram-passport-errors-sent.shown { - opacity: 1; -} - -@media (min-width: 768px) { - .telegram-passport-login-wrap { - text-align: left; - } - .telegram-passport-relogin-wrap { - text-align: left; - margin: 50px 0 50px 240px; - } - .telegram-passport-item-files, - .telegram-passport-item-value { - clear: none; - margin-left: 240px; - } - .telegram-passport-item .telegram-passport-checkbox-right { - margin-top: 10px; - } - .telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; - } - .telegram-passport-errors-wrap { - position: absolute; - right: 0; - margin: 50px 0 0; - } -} - -.telegram-passport-form .sub-control-label { - text-align: left; - margin: 11px 0 6px; -} -.telegram-passport-form .sub-control-label .radio-label { - font-weight: bold; -} -.telegram-passport-form .sub-control-label .radio-item + .radio-item, -.telegram-passport-form .sub-control-label .checkbox-item + .checkbox-item { - margin-left: 25px; -} -.telegram-passport-form label.control-label .radio-label { - font-weight: bold; -} -.passport-opt, -.passport-opt-col { - display: inline-block; - margin-left: 31px; - margin-top: -10px; -} -.passport-opt + .passport-opt, -.passport-opt-col + .passport-opt-col { - margin-left: 0; -} -@media (min-width: 992px) { - .passport-opt-col { - margin-left: 0; - margin-top: 0; - text-align: center; - } - .passport-opt-col .checkbox-label { - text-align: left; - } - .passport-opt-col .checkbox-item input.checkbox ~ .checkbox-label { - display: none; - } -} 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/js/telegram-passport2.js b/data/corefork.telegram.org/js/telegram-passport2.js deleted file mode 100644 index 026006ade7..0000000000 --- a/data/corefork.telegram.org/js/telegram-passport2.js +++ /dev/null @@ -1,413 +0,0 @@ -(function(window) { - if (!Array.isArray) { - Array.isArray = function(arg) { - return Object.prototype.toString.call(arg) === '[object Array]'; - }; - } - if (!Object.isSimpleObject) { - Object.isSimpleObject = function(arg) { - return arg != null && typeof arg === 'object'; - }; - } - function isFunction(func) { - return func && {}.toString.call(func) === '[object Function]'; - } - function getEl(elOrId) { - if (elOrId.nodeType) return elOrId; - return document.getElementById(elOrId); - } - function preventDefault(event) { - if (window.event) { - window.event.returnValue = false; - } - else if (event.preventDefault) { - event.preventDefault(); - } - else { - event.returnValue = false; - } - } - function addEvent(el, event, handler) { - var events = event.split(/\s+/); - for (var i = 0; i < events.length; i++) { - if (el.addEventListener) { - el.addEventListener(events[i], handler, false); - } else { - el.attachEvent('on' + events[i], handler); - } - } - } - - var UA = window.navigator.userAgent || ''; - var ScopeAliases = { - personal_details: 'pd', - passport: 'pp', - driver_license: 'dl', - identity_card: 'ic', - internal_passport: 'ip', - id_document: 'idd', - address: 'ad', - utility_bill: 'ub', - bank_statement: 'bs', - rental_agreement: 'ra', - passport_registration: 'pr', - temporary_registration: 'tr', - address_document: 'add', - phone_number: 'pn', - email: 'em', - }; - - function openDeepLink(url, tooltipToggle) { - var is_ios = /ios|iphone os|iphone|ipod|ipad/i.test(UA); - var is_firefox = /firefox/i.test(UA); - var use_iframe = (is_ios || is_firefox); - var use_once = (!is_ios && is_firefox); - var timeOpen; - var ttNeedHide = false; - var pageShown = true; - var onPageHide = function() { - pageShown = false; - }; - tooltipToggle = tooltipToggle || function(){}; - var onPageShow = function() { - pageShown = true; - if (ttNeedHide && (+(new Date) - timeOpen) > 5000) { - tooltipToggle(false); - } - }; - addEvent(window, 'pagehide', onPageHide); - addEvent(window, 'pageshow', onPageShow); - addEvent(window, 'blur', onPageHide); - addEvent(window, 'focus', onPageShow); - var showTooltip = function() { - tooltipToggle(true); - if (!pageShown) { - ttNeedHide = true; - } - }; - if (use_iframe) { - var iframeEl = document.createElement('iframe'); - iframeEl.style.position = 'absolute'; - iframeEl.style.left = '-10000px'; - iframeEl.style.top = '-10000px'; - document.body.appendChild(iframeEl); - if (iframeEl !== null) { - timeOpen = +(new Date); - iframeEl.src = url; - setTimeout(showTooltip, 2500); - } - if (!use_once) { - setTimeout(function() { - if (pageShown) { - timeOpen = +(new Date); - window.location = url; - } - }, 2000); - } - } - else { - setTimeout(function() { - timeOpen = +(new Date); - window.location = url; - }, 100); - setTimeout(showTooltip, 1500); - } - } - - function packScope(scope) { - if (scope.data) { - scope.d = scope.data; - delete scope.data; - } - if (!scope.d) { - throw new TypeError('scope data is required'); - } - if (!scope.v) { - throw new TypeError('scope version is required'); - } - for (var i = 0; i < scope.d.length; i++) { - scope.d[i] = packScopeField(scope.d[i]); - } - return JSON.stringify(scope); - } - function packScopeField(field) { - if (field.one_of) { - field._ = field.one_of; - delete field.one_of; - } else if (field.type) { - field._ = field.type; - delete field.type; - } - if (Array.isArray(field._)) { - for (var j = 0; j < field._.length; j++) { - field._[j] = packScopeField(field._[j]); - } - field = packScopeOpts(field); - } else if (field._) { - if (ScopeAliases[field._]) { - field._ = ScopeAliases[field._]; - } - field = packScopeOpts(field); - } else if (ScopeAliases[field]) { - field = ScopeAliases[field]; - } - return field; - } - function packScopeOpts(scope) { - if (scope.selfie) { - scope.s = 1; - delete scope.selfie; - } - if (scope.translation) { - scope.t = 1; - delete scope.translation; - } - if (scope.native_names) { - scope.n = 1; - delete scope.native_names; - } - return scope; - } - - function passportAuth(options, tooltipToggle) { - if (!options.bot_id) { - throw new Error('bot_id is required'); - } - if (!options.scope) { - throw new Error('scope is required'); - } - if (!Object.isSimpleObject(options.scope)) { - throw new TypeError('scope should be an object'); - } - if (!options.public_key) { - throw new Error('public_key is required'); - } - if (!options.nonce) { - throw new Error('nonce is required'); - } - if (options.payload) { - throw new Error('payload is deprecated, use nonce instead'); - } - var is_android = /android/i.test(UA); - var url = (is_android ? 'tg:' : 'tg://') + 'resolve?domain=telegrampassport' - + '&bot_id=' + encodeURIComponent(options.bot_id) - + '&scope=' + encodeURIComponent(packScope(options.scope)) - + '&public_key=' + encodeURIComponent(options.public_key) - + '&nonce=' + encodeURIComponent(options.nonce); - if (options.callback_url) { - url += '&callback_url=' + encodeURIComponent(options.callback_url); - } - url += '&payload=nonce'; // legacy for outdated apps - openDeepLink(url, tooltipToggle); - } - - function createAuthButton(contEl, authDataOrFunc, options) { - contEl = getEl(contEl); - if (!contEl) { - return false; - } - options = options || {}; - var btnText = options.text || 'Log In With Telegram'; - var btnRadius = parseInt(options.radius, 10) || 23; - var tooltipText = options.tooltip_text || 'Please install Telegram to use this option.'; - var tooltipForce = options.tooltip_force || false; - var tooltipPos = options.tooltip_position; - if (tooltipPos == 'top') { - var tooltipWrapClass = 'tooltip-top'; - } else if (tooltipPos == 'left') { - var tooltipWrapClass = 'tooltip-left'; - } else if (tooltipPos == 'right') { - var tooltipWrapClass = 'tooltip-right'; - } else { - var tooltipWrapClass = 'tooltip-bottom'; - } - var btnStyle = '' - + '.telegram-passport {' - + 'display: inline-block;' - + 'position: relative;' - + 'max-width: 100%;' - + '}' - + 'button.telegram-passport-button {' - + 'display: inline-block;' - + 'vertical-align: top;' - + 'font-family: "Lucida Grande", Arial, Helvetica, sans-serif;' - + 'font-size: 16px;' - + 'font-weight: 500;' - + 'line-height: 20px;' - + 'text-align: left;' - + 'border-radius: ' + btnRadius + 'px;' - + 'background-color: #54a9eb;' - + 'text-decoration: none;' - + 'padding: 12px 21px 14px;' - + 'margin: 0;' - + 'white-space: nowrap;' - + 'text-overflow: ellipsis;' - + 'overflow: hidden;' - + 'border: none;' - + 'color: #fff;' - + 'cursor: pointer;' - + 'max-width: 100%;' - + '}' - + 'button.telegram-passport-button:focus {' - + 'outline: none;' - + '}' - + '.telegram-passport-tooltip-wrap {' - + 'position: absolute;' - + 'pointer-events: none;' - + 'text-align: center;' - + 'z-index: 100;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom {' - + 'left: -500px;' - + 'right: -500px;' - + 'top: 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top {' - + 'left: -500px;' - + 'right: -500px;' - + 'bottom: 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left {' - + 'right: 100%;' - + 'top: 7px;' - + 'bottom: 7px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right {' - + 'left: 100%;' - + 'top: 7px;' - + 'bottom: 7px;' - + '}' - + '.telegram-passport-tooltip {' - + 'position: relative;' - + 'font-family: "Lucida Grande", Arial, Helvetica, sans-serif;' - + 'background: #949494;' - + 'color: #fff;' - + 'white-space: nowrap;' - + 'border-radius: ' + btnRadius + 'px;' - + 'padding: 7px 16px;' - + 'display: inline-block;' - + 'font-size: 14px;' - + 'line-height: 18px;' - + 'text-decoration: none;' - + 'pointer-events: none;' - + 'visibility: hidden;' - + 'opacity: 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip {' - + 'margin-top: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip {' - + 'margin-bottom: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip {' - + 'margin-right: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip {' - + 'margin-left: 32px;' - + '}' - + '.telegram-passport-tooltip:hover {' - + 'color: #fff;' - + 'text-decoration: none;' - + '}' - + '.telegram-passport-tooltip-shown {' - + 'transition: all .2s ease;' - + 'pointer-events: auto;' - + 'visibility: visible;' - + 'opacity: 1;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip-shown {' - + 'margin-top: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip-shown {' - + 'margin-bottom: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip-shown {' - + 'margin-right: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip-shown {' - + 'margin-left: 16px;' - + '}' - + '.telegram-passport-button-icon {' - + 'display: inline-block;' - + 'vertical-align: top;' - + "background: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADYAAAAsCAYAAAFZD3u2AAAAAXNSR0IArs4c6QAAB+FJREFUaAXVWllsVFUYPndm2qG0Q4EipaWspSJbQRYxDWIUHyBqAgYTjUsTNBqN+qAJLg8+ugTlQeITARNQNERcXlyesAxVhOKSSGhLVyi0dDqdznTWznL9/ts5t2fuNrfTEvFP/p5//89/z52z3TJmArIsOyWtDkKZyxxEgE+SkOBMm5/rxlsSxpPpTFPrEJEqKJ4S4PfOgBSMp1QvkqmMSJCryOto6HuUsFwDwbvkRQDZb0rcLEM2JFRklFP1zJaQ0wm1t+FEmjxzQPUcioyxbPcHcyzsMOhXzhNyaZ1gMAeyYVF+visgskp2CYY0CHNzNGD42GxfWaFVKY4u9D1HQ2NGlkYO2QibdJFIgB5I3/zRLx/xXlUCgM8BQyc7QkQ5YceOerBZTGnpJBr2DkXHOK9zguIcV/JW+2IrTlDu5QZie7bdL1/oCogiorupvzpIpzMpit7ji+h0EBTxTG9yLRkTRuLq75GrlFZXj7fNf4ocMplMjqHI6JxIQE40uGZANurPghgRjjb39YI/IspAv6zhx1lv+/ALR73XJuYHiHlWQ4fpFCLRazwZb6ccH4FKgD/xgFbtpJIh0ENAw5eFksSS6Zs0cCawxTQZHA6aOOWIfaOJGCVoxltuBZRImd5gdAH0ZtPMGsVVf5T1DMUUaUVZ0QyLiYl7vkoETYkz0NJkSa0ptPaH2WAooerXLPSwirJilbcisjM/o2k0DsMSrTE68dZfvcH3Q8JqRzYNK+Ywl9P056INQ/wXXJizSnEhb1ta5KJImX+MeAw+W1sziy2cbfkAuKva8qpIYJmMDM60Dn2ICX8/ree+USUviVljQ03G6ZhYYhWh/k8HktVxcd5kZEhv20BojIUTKSxhLLRv2+JyHgCPeznoTs5rWhom/VquMdKxX52/8YNOqBEg8TtADsc06lvPIvMuYBdw9y3JhsDzgBeBIvRPazJEPiRG19AHppwMAZ8EpjSBjdjqgpIh0lJgh1HEdCYTTiTTOtWkEsHbATyuiyIIWroDcsfNsCCZIG0lg/lLEy7GVCiaDNBv8XogZmwgy17TZPBYDxww8xTlv17xK1uckYi6SxPVnN5DydQZBFI3+K+Bj5AiHwwEE+n2gbCT7LYun83cRQpp6MbnRxeS7ITFj4ZWxsK0t93vxNFEib6tbi5zONQ+G3tkpbSeKRtrS6ussnMwwq4HaEUaBxuLJhnGUNlMImhh+ogIK0hl5DSdL3giKsRmIgr7CY+t1o8Cl0L4LXADV1L7T1+IDUeSqsjtcrCttXQwsg2VqEw5n6nJRFckrh1LpU+c6xy5R5TPKnGxDROri6gypfnLQQaGybgn/XY4XTXbzeoqyzhruxWTWW4mYKgma+kJ2k4gGDYJtPlGn4wk5ribG8eSGXb07DUW1myAuN6kPSjKLR8jGfJH2eGLqn53LSjFLkt3IFb1nBAfIcksH6PiJEkj3Jm3SFwDupTzdtu8yTIOtk4M5nI6NzY2LLqOXkezPT8v6gU6ItAKmTfZA3UVfdxJcjh3NzYs/JPz1CLhVjS7RFmWzhkvA72xyHvZt+mz5qvmpxC44bdJ6516ujWO9D+VorC1wAPAG0AtdN/2ZaHHxcA9wO+Algs09BzO3laFoVfVwP3AS7yHBbaP/WeFocPbgIeBwQI7b+bWQ0Xp7ianu1Jk9yDmXmAjcDsw78QPGw7pgeDYSOdguKIap91ldyjbGK4za5VZazJJzAKpchSxEgwV8AyQFoVCINHti2WuDUeV+4QlFSVsyTxbBVEu2vXNwlSdLGjEUAD50baWingUSPvoggG3jLGOwah7IBin9cdNF/2rqz1snsfeDYuQ+BAVRXzeEUMR82H3FJCKWA+cFsA3jVhbf7hE3IwWYzO6rsbDSt0FPW/qVzUKU87RORFQBK22VMATwEltd2GfF+LJTKK1f9QdiikXrerVFW166Q6saHLXU9p8X/KiSEGHl9fRfqy1mi5+NJ5KY2Sc0TH9/U5VuZutqCyl7ct0pNuMOBd5IBqxnCMDV0ylDUSTcnt/WEqkMhRGdxCtQzFVk7zTy9OfM2JRZKs+KowcfSB6Gkiv4b3ASQFdrdJxFPcehn4uHBvX4PdTXjL+ccPQqHDhbhT2veiuFiYKRRoFrwD/eBbVkwx4uuuQenDIMKlFCTOz2KlMCFY3CIph4X+6UFSt1j1vYVoH4k93d89wJDzj1+tGBpDRZfiqqjLbNxUmYeyIX0Fhn2oNCyqMgjRd9jdg6mnWBqSLii3LrO94tD5T4OlMWo7ClGlWjFNwYRTklzbfYUmWnhcD0ux3Izj+KaMev6mNS8qZY3pmPTENpz9AUW9zRmynVNjJkyedC+p3RGUmq1uEUDzNBkcnvtFQsmL8mwJdoC21vzUS+2hFz0dhPiODKRVGAZs6g3UsmWznwUeiSTYkXG1xObUYuEsP11e9ON/jOgx2lagrgD6Oop4188t7N2DmyOX315ZfcUoO9XXAtY8O0IFBR5F0J77YrK2cVdQMfjWQHiotLSGdgz2B5d3DlEeM+oAlQfK2DffglVzcN5Jg+OcWpWsIHmdOaee+hkVNVn2FPy1u7wHfANrp02k8lwetYtoJYuWv6n7+e6C0pNjV3zEU9eCGOc0kx77n7qs5phrYJFDkAph+Dtxh4kJPrRaF9Zrob38xiqwHngLSf3TQh3X6YGXr++q/M6e7wZMmuzIAAAAASUVORK5CYII=') no-repeat;" - + 'background-size: 27px 22px;' - + 'width: 27px;' - + 'height: 22px;' - + 'margin: 0 15px -2px -5px;' - + '}' - + '.telegram-passport-tooltip:before {' - + "content: '';" - + 'display: inline-block;' - + 'position: absolute;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip:before {' - + 'left: 50%;' - + 'top: 0;' - + 'border: 10px solid;' - + 'border-radius: 4px 0 0;' - + 'border-color: #949494 transparent transparent #949494;' - + 'transform: rotateZ(45deg) translate3d(-3px,5px,0);' - + 'transform-origin: 100% 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip:before {' - + 'left: 50%;' - + 'bottom: 0;' - + 'border: 10px solid;' - + 'border-radius: 0 0 4px;' - + 'border-color: transparent #949494 #949494 transparent;' - + 'transform: rotateZ(45deg) translate3d(-11px,9px,0);' - + 'transform-origin: 0 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip:before {' - + 'top: 50%;' - + 'right: 0;' - + 'border: 8px solid;' - + 'border-radius: 0 2px 0 0;' - + 'border-color: #949494 #949494 transparent transparent;' - + 'transform: rotateZ(45deg) translate3d(4px,-3.5px,0);' - + 'transform-origin: 100% 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip:before {' - + 'top: 50%;' - + 'left: 0;' - + 'border: 8px solid;' - + 'border-radius: 0 0 0 2px;' - + 'border-color: transparent transparent #949494 #949494;' - + 'transform: rotateZ(45deg) translate3d(-15px,-7.5px,0);' - + 'transform-origin: 0 100%;' - + '}'; - var tooltipClass = tooltipForce ? 'telegram-passport-tooltip telegram-passport-tooltip-shown' : 'telegram-passport-tooltip'; - var btnHtml = '' - + '' - + '
    ' + tooltipText + '
    ' - + ''; - var btnContEl = document.createElement('div'); - btnContEl.className = 'telegram-passport'; - btnContEl.innerHTML = btnHtml; - contEl.appendChild(btnContEl); - var buttonEl = btnContEl.getElementsByTagName('button')[0]; - var tooltipEl = btnContEl.getElementsByTagName('a')[0]; - addEvent(buttonEl, 'click', function(e) { - preventDefault(e); - var options = isFunction(authDataOrFunc) ? authDataOrFunc() : authDataOrFunc; - options = options || {}; - var tooltipToggle = function(show) { - if (show) { - tooltipEl.classList.add('telegram-passport-tooltip-shown'); - } else { - tooltipEl.classList.remove('telegram-passport-tooltip-shown'); - } - }; - passportAuth(options, !tooltipForce ? tooltipToggle : null); - }); - } - - if (!window.Telegram) { - window.Telegram = {}; - } - window.Telegram.Passport = { - auth: passportAuth, - createAuthButton: createAuthButton, - }; -})(window); diff --git a/data/corefork.telegram.org/method/account.getWallPapers b/data/corefork.telegram.org/method/account.getWallPapers deleted file mode 100644 index 11acd2d24a..0000000000 --- a/data/corefork.telegram.org/method/account.getWallPapers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.getWallPapers - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    account.getWallPapers

    - -

    Returns a list of available wallpapers.

    -

    - -
    -
    account.wallPapersNotModified#1c199183 = account.WallPapers;
-account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
----functions---
-account.getWallPapers#7967d36 hash:long = account.WallPapers;

    -

    Parameters

    - - - - - - - - - - - - - - - -
    NameTypeDescription
    hashlongHash for pagination, for more info click here
    -

    Result

    -

    Vector<WallPaper>

    -

    Related pages

    -

    Pagination in the API

    -

    How to fetch results from large lists of objects.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/account.getWebAuthorizations b/data/corefork.telegram.org/method/account.getWebAuthorizations deleted file mode 100644 index 839d82e415..0000000000 --- a/data/corefork.telegram.org/method/account.getWebAuthorizations +++ /dev/null @@ -1,136 +0,0 @@ - - - - - account.getWebAuthorizations - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    account.getWebAuthorizations

    - -

    Get web login widget authorizations

    -

    - -
    -
    account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
----functions---
-account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Result

    -

    account.WebAuthorizations

    -

    Related pages

    -

    Telegram Login Widget

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/account.reportProfilePhoto b/data/corefork.telegram.org/method/account.reportProfilePhoto deleted file mode 100644 index d3d2fc589a..0000000000 --- a/data/corefork.telegram.org/method/account.reportProfilePhoto +++ /dev/null @@ -1,165 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/account.updateProfile b/data/corefork.telegram.org/method/account.updateProfile deleted file mode 100644 index f350d7ccde..0000000000 --- a/data/corefork.telegram.org/method/account.updateProfile +++ /dev/null @@ -1,187 +0,0 @@ - - - - - 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.
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/auth.requestPasswordRecovery b/data/corefork.telegram.org/method/auth.requestPasswordRecovery deleted file mode 100644 index 1ba3f369ea..0000000000 --- a/data/corefork.telegram.org/method/auth.requestPasswordRecovery +++ /dev/null @@ -1,159 +0,0 @@ - - - - - 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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/messages.getStickerSet b/data/corefork.telegram.org/method/channels.deleteUserHistory similarity index 77% rename from data/corefork.telegram.org/method/messages.getStickerSet rename to data/corefork.telegram.org/method/channels.deleteUserHistory index e9b99a47f2..44a6375f2f 100644 --- a/data/corefork.telegram.org/method/messages.getStickerSet +++ b/data/corefork.telegram.org/method/channels.deleteUserHistory @@ -2,12 +2,12 @@ - messages.getStickerSet + channels.deleteUserHistory - - + + - + @@ -36,10 +36,10 @@
    -
    -

    messages.getStickerSet

    +
    +

    channels.deleteUserHistory

    -

    Get info about a stickerset

    +

    Delete all messages sent by a certain user in a supergroup

    • @@ -52,9 +52,9 @@
    -
    messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
+
    messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
 ---functions---
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
    
+channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

    Parameters

    @@ -66,14 +66,19 @@ - - - + + + + + + + +
    stickersetInputStickerSetStickersetchannelInputChannelSupergroup
    user_idInputUserUser whose messages should be deleted

    Result

    -

    messages.StickerSet

    +

    messages.AffectedHistory

    Possible errors

    @@ -86,17 +91,39 @@ - - + + - - + + + + + + + + + + + + + + + + + + + + + +
    400EMOTICON_STICKERPACK_MISSING CHANNEL_INVALIDThe provided channel is invalid.
    400STICKERSET_INVALIDThe provided sticker set is invalid.CHANNEL_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.
    -

    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.getAdminedPublicChannels b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels deleted file mode 100644 index a6755b7726..0000000000 --- a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels +++ /dev/null @@ -1,191 +0,0 @@ - - - - - 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_MUCHReturned if both the check_limit and the by_location flags are set and the user has reached the limit of public geogroups.
    400CHANNELS_ADMIN_PUBLIC_TOO_MUCHReturned if the check_limit flag is set and the user has reached the limit of public channels/supergroups.
    -

    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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/channels.getSponsoredMessages b/data/corefork.telegram.org/method/channels.getSponsoredMessages deleted file mode 100644 index ffa01a9eaa..0000000000 --- a/data/corefork.telegram.org/method/channels.getSponsoredMessages +++ /dev/null @@ -1,154 +0,0 @@ - - - - - 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

    -
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getContactIDs b/data/corefork.telegram.org/method/contacts.getContactIDs deleted file mode 100644 index 6df017f54d..0000000000 --- a/data/corefork.telegram.org/method/contacts.getContactIDs +++ /dev/null @@ -1,151 +0,0 @@ - - - - - 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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/account.setContactSignUpNotification b/data/corefork.telegram.org/method/contacts.toggleTopPeers similarity index 87% rename from data/corefork.telegram.org/method/account.setContactSignUpNotification rename to data/corefork.telegram.org/method/contacts.toggleTopPeers index 4e689a9599..ddc92a0947 100644 --- a/data/corefork.telegram.org/method/account.setContactSignUpNotification +++ b/data/corefork.telegram.org/method/contacts.toggleTopPeers @@ -2,12 +2,12 @@ - account.setContactSignUpNotification + contacts.toggleTopPeers - - + + - + @@ -36,10 +36,10 @@
    -
    -

    account.setContactSignUpNotification

    +
    +

    contacts.toggleTopPeers

    -

    Toggle contact sign up notifications

    +

    Enable/disable top peers

    +

    Bool

    +

    Related pages

    +

    Top peer rating

    +

    If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

    diff --git a/data/corefork.telegram.org/method/help.getAppConfig b/data/corefork.telegram.org/method/help.getAppConfig deleted file mode 100644 index 46b7268f49..0000000000 --- a/data/corefork.telegram.org/method/help.getAppConfig +++ /dev/null @@ -1,142 +0,0 @@ - - - - - help.getAppConfig - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    help.getAppConfig

    - -

    Get app-specific configuration, see client configuration for more info on the result.

    -

    - -
    -
    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;
----functions---
-help.getAppConfig#98914110 = JSONValue;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Result

    -

    JSONValue, see client configuration for more info on the result

    -

    Related pages

    -

    Client configuration

    -

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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/help.getAppUpdate b/data/corefork.telegram.org/method/help.getAppUpdate deleted file mode 100644 index bc6bab8e7a..0000000000 --- a/data/corefork.telegram.org/method/help.getAppUpdate +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.getAppUpdate - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    help.getAppUpdate

    - -

    Returns information on update availability for the current 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;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
----functions---
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

    -

    Parameters

    - - - - - - - - - - - - - - - -
    NameTypeDescription
    sourcestringSource
    -

    Result

    -

    help.AppUpdate

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/help.getPromoData b/data/corefork.telegram.org/method/help.getPromoData deleted file mode 100644 index 3778e05b26..0000000000 --- a/data/corefork.telegram.org/method/help.getPromoData +++ /dev/null @@ -1,135 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/help.getSupport b/data/corefork.telegram.org/method/help.getSupport deleted file mode 100644 index 2ac1c12f5f..0000000000 --- a/data/corefork.telegram.org/method/help.getSupport +++ /dev/null @@ -1,134 +0,0 @@ - - - - - help.getSupport - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    help.getSupport

    - -

    Returns the support user for the 'ask a question' feature.

    -

    - -
    -
    help.support#17c6b5f6 phone_number:string user:User = help.Support;
----functions---
-help.getSupport#9cdf08cd = help.Support;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Result

    -

    help.Support

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/help.saveAppLog b/data/corefork.telegram.org/method/help.saveAppLog deleted file mode 100644 index d6ef89fd0c..0000000000 --- a/data/corefork.telegram.org/method/help.saveAppLog +++ /dev/null @@ -1,150 +0,0 @@ - - - - - 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

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/help.setBotUpdatesStatus b/data/corefork.telegram.org/method/help.setBotUpdatesStatus deleted file mode 100644 index cfab355bfd..0000000000 --- a/data/corefork.telegram.org/method/help.setBotUpdatesStatus +++ /dev/null @@ -1,156 +0,0 @@ - - - - - help.setBotUpdatesStatus - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    help.setBotUpdatesStatus

    - -

    Informs the server about the number of pending bot updates if they haven't been processed for a long time; for bots only

    -

    - -
    -
    boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    pending_updates_countintNumber of pending updates
    messagestringError message, if present
    -

    Result

    -

    Bool

    -

    Bots can use this method

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/core.telegram.org/method/payments.getPaymentForm b/data/corefork.telegram.org/method/messages.deleteHistory similarity index 78% rename from data/core.telegram.org/method/payments.getPaymentForm rename to data/corefork.telegram.org/method/messages.deleteHistory index 6eea9d4136..22c7cd9710 100644 --- a/data/core.telegram.org/method/payments.getPaymentForm +++ b/data/corefork.telegram.org/method/messages.deleteHistory @@ -2,12 +2,12 @@ - payments.getPaymentForm + messages.deleteHistory - - + + - + @@ -36,10 +36,10 @@
    -
    -

    payments.getPaymentForm

    +
    +

    messages.deleteHistory

    -

    Get a payment form

    +

    Deletes communication history.

    • @@ -52,9 +52,9 @@
    -
    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;
+
    messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
 ---functions---
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
    
+messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;

    Parameters

    @@ -71,24 +71,29 @@ + + + + + + + + + + - + - + - - - - - - +
    Flags, see TL conditional fields
    just_clearflags.0?trueJust clear history for the current user, without actually removing messages for every chat user
    revokeflags.1?trueWhether to delete the message history for all chat participants
    peer InputPeerThe peer where the payment form was sentUser or chat, communication history of which will be deleted
    msg_idmax_id intMessage 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    		Maximum ID of message to delete

    Result

    -

    payments.PaymentForm

    +

    messages.AffectedHistory

    Possible errors

    @@ -101,9 +106,29 @@ + + + + + + + + + + + + + + + + + + + +
    400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
    400CHAT_ID_INVALIDThe provided chat id is invalid.
    400 MESSAGE_ID_INVALID The provided message id is invalid.
    400MSG_ID_INVALIDInvalid message ID provided.
    400PEER_ID_INVALIDThe provided peer id is invalid.
    @@ -144,9 +169,9 @@
    -
    Platform
    +
    Platform
    @@ -163,7 +188,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/method/messages.getSplitRanges b/data/corefork.telegram.org/method/messages.getSplitRanges deleted file mode 100644 index d685239dbc..0000000000 --- a/data/corefork.telegram.org/method/messages.getSplitRanges +++ /dev/null @@ -1,133 +0,0 @@ - - - - - messages.getSplitRanges - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    messages.getSplitRanges

    - -

    Get message ranges for saving the user's chat history

    -

    - -
    -
    ---functions---
-messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;

    -

    Parameters

    -

    This constructor does not require any parameters.

    -

    Result

    -

    Vector<MessageRange>

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/stickers.suggestShortName b/data/corefork.telegram.org/method/messages.readMentions similarity index 85% rename from data/corefork.telegram.org/method/stickers.suggestShortName rename to data/corefork.telegram.org/method/messages.readMentions index 1ce2b43bb5..d1f2520fd3 100644 --- a/data/corefork.telegram.org/method/stickers.suggestShortName +++ b/data/corefork.telegram.org/method/messages.readMentions @@ -2,12 +2,12 @@ - stickers.suggestShortName + messages.readMentions - - + + - + @@ -36,10 +36,10 @@
    -
    -

    stickers.suggestShortName

    +
    +

    messages.readMentions

    -

    Suggests a short name for a given stickerpack name

    +

    Mark mentions as read

    • @@ -52,9 +52,9 @@
    -
    stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
+
    messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
 ---functions---
-stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;
    
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;

    Parameters

    @@ -66,14 +66,14 @@ - - - + + +
    titlestringSticker pack namepeerInputPeerDialog

    Result

    -

    stickers.SuggestedShortName

    +

    messages.AffectedHistory

    Possible errors

    @@ -86,8 +86,23 @@ - - + + + + + + + + + + + + + + + + +
    400TITLE_INVALIDThe specified stickerpack title is invalid.CHANNEL_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.sendEncryptedService b/data/corefork.telegram.org/method/messages.sendEncryptedService deleted file mode 100644 index aba6a47d0c..0000000000 --- a/data/corefork.telegram.org/method/messages.sendEncryptedService +++ /dev/null @@ -1,205 +0,0 @@ - - - - - messages.sendEncryptedService - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    messages.sendEncryptedService

    - -

    Sends a service message to a secret chat.

    -

    - -
    -
    messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

    -

    Parameters

    - - - - - - - - - - - - - - - - - - - - - - - - - -
    NameTypeDescription
    peerInputEncryptedChatSecret chat ID
    random_idlongUnique client message ID required to prevent message resending
    databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
    -

    Result

    -

    messages.SentEncryptedMessage

    -

    Possible errors

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    CodeTypeDescription
    400DATA_INVALIDEncrypted data invalid.
    400ENCRYPTION_DECLINEDThe secret chat was declined.
    400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
    400MSG_WAIT_FAILEDA waiting call returned an error.
    403USER_DELETEDYou can't send this secret message because the other participant deleted their account.
    403USER_IS_BLOCKEDYou were blocked by this user.
    -

    Related pages

    -

    DecryptedMessage

    -

    Object describes the contents of an encrypted message.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/method/account.getChatThemes b/data/corefork.telegram.org/method/messages.unpinAllMessages similarity index 83% rename from data/corefork.telegram.org/method/account.getChatThemes rename to data/corefork.telegram.org/method/messages.unpinAllMessages index 6ccb5c362c..a12ac989d5 100644 --- a/data/corefork.telegram.org/method/account.getChatThemes +++ b/data/corefork.telegram.org/method/messages.unpinAllMessages @@ -2,12 +2,12 @@ - account.getChatThemes + messages.unpinAllMessages - - + + - + @@ -36,10 +36,10 @@
    -
    -

    account.getChatThemes

    +
    +

    messages.unpinAllMessages

    -

    Get all available chat themes

    +

    Unpin all pinned messages

    • @@ -52,10 +52,9 @@
    -
    account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
-account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
+
    messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
 ---functions---
-account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;
    
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;

    Parameters

    @@ -67,17 +66,18 @@ - - - + + +
    hashintHash for pagination, for more info click herepeerInputPeerChat where to unpin

    Result

    -

    account.ChatThemes

    +

    messages.AffectedHistory

    +

    Bots can use this method

    Related pages

    -

    Pagination in the API

    -

    How to fetch results from large lists of objects.

    +

    Pinned messages

    +

    Telegram allows pinning multiple messages on top of a specific chat.

    diff --git a/data/corefork.telegram.org/method/photos.deletePhotos b/data/corefork.telegram.org/method/photos.deletePhotos deleted file mode 100644 index 99961ac6fa..0000000000 --- a/data/corefork.telegram.org/method/photos.deletePhotos +++ /dev/null @@ -1,148 +0,0 @@ - - - - - photos.deletePhotos - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    photos.deletePhotos

    - -

    Deletes profile photos.

    -

    - -
    -
    ---functions---
-photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;

    -

    Parameters

    - - - - - - - - - - - - - - - -
    NameTypeDescription
    idVector<InputPhoto>Input photos to delete
    -

    Result

    -

    Method returns a list of successfully deleted photos in Vector<long>

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-abstract-types.html b/data/corefork.telegram.org/mtproto/TL-abstract-types.html new file mode 100644 index 0000000000..f23f8d5c88 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-abstract-types.html @@ -0,0 +1,202 @@ + + + + + Binary serialization and abstract TL types + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Binary serialization and abstract TL types

    + +

    TL Language defines abstract data types in the spirit of a general theory of types (more accurately, Martin-Löf’s theories of dependent intuitionistic types) without specifying the values of these types should be represented in memory, when saved to disk, or transmitted over a network. In contrast, the article on binary serialization discusses the problem of effective serialization of values of abstract types. To this end, the concept of a concrete or serialized type has been defined as the sets of serializations of all possible values of the corresponding abstract type. In this case, the serializations take values in the set A of words in the alphabet A*, which consists of 2^32 characters -- 32-bit integers.

    +

    In order to use a TL schema (e.g. “program”) in the TL language to describe the serialization of values of abstract types, we should explain how the concrete type [T] (subset [T] of A^) is associated with the abstract type T (defined in TL), and how the values of the abstract type T correspond to the values of the concrete type [T] (i.e. the elements of [T]*).

    +

    Serialization is the process of constructing an element of [T] based on a value of the abstract type T. The reverse process is deserialization.

    +

    Values of the abstract type T may be represented in a different way. Typically, some sort of trees or graphs are used in memory or, if desired, a set of nodes may be used, each of which contains a certain tag (“node type”) and several pointers to other nodes and/or values of built-in primitive types such as int. However, for general discussions it is useful to write the values of abstract type T as a string, more specifically, an S-expression. Recall that an S-expression is either an atom (the value of a primitive type, for example, an integer or a string constant in quotation marks; or an identifier that corresponds to a built-in or defined function) or a space-delimited list of S-expressions ending in parentheses. In our case, we use S-expressions, the first element of which is a combinator identifier, while the remaining elements (the number of which depends on the combinator’s arity) are S-expressions representing elements of the chosen combinator’s fields (or parameters). Moreover, the type of the arguments’ S-expressions and the type of the S-expressions of the result (e.g. the associated expression) must match.

    +

    For example, for the schema

    +
    pair x:int y:int = Pair;
+pnil = PairList;
+pcons hd:Pair tl:PairList = PairList;
    +

    the following are examples of the abstract type PairList, written as S-expressions:

    +
    (pnil)
+(pcons (pair 2 3) (pcons (pair 9 4) (pnil)))
    +

    We usually write E : T (read "E of type T”) when we want to say that E is a value of type T. We assume there is a built-in type Type whose values are types. Thus, writing T : Type means that T is a type.

    +

    For example, we can write:

    +
    PairList : Type;
+(pcons (pair 2 3) (pcons (pair 9 4) (pnil))) : PairList;
    +

    Converting an abstract value to a serialized value, generally speaking, is straightforward (and, if desired, can be defined by induction):

    +
      +
    • +

      It is the serialization of values n of the primitive type int (as a single-symbol word in the alphabet A)

      +
      • +
    • +

      The serialization of a string constant (a value of the primitive type string) is a sequence of the 32-bit numbers defined in Binary serialization.

      +
      • +
    • +

      The serialization of the S-expression (C E1 ... Er) : T, where C is a combinator with arity r with argument types T1, ..., Tr and result type T (e.g. C : T1->T2->...->Tr->T) is the concatenation of the combinator number C (a 32-bit number that unambiguously identifies the combinator, usually equal to the CRC-32 of the string of its TL description) and the serializations of the values E1 of type T1, E2 of type T2, ..., Er of type Tr.

      +
      • +
    +

    If we use [T] to denote the concrete type corresponding to the abstract T, and [E] to denote an element of [T] corresponding to the value E of type T, then the last rule may be written as:

    +
      +
    • [T] is the combination, for each constructor of type C T1->T2->...->Tr->T (i.e. that returns a value of type T), of direct products {C} x [T1] x [T2] x ... x [Tr], where {C} is a single-element set consisting of the combinator number C. Because {C}<>{C'} when C<>C’, this defines a mutually single-valued mapping of the values of the abstract type T (written using S-expressions) to the set [T].
      • +
    +

    Values of the built-in clothed types Int and String and serialized as if they were defined using int x:int = Int; and string s:string = String;, i.e. the serialization of integer constant or a string is preceded by number of the int or string combinator (constructor). In S-expressions, this may be written as (int 5) or (string "Test").

    +

    However, what has been described above does not account for certain subtleties, such as the existence of naked types, or the difference between functions (active combinators whose application may be reduced, e.g. calculated) and constructors (passive combinators for which there are not and cannot be reduction rules). Furthermore, we have not explained how to handle polymorphic types and optional combinator parameters. We will attempt to explain this now.

    +

    Constants, surface values, and functional values

    +

    By dividing combinators into constructors and functions, we can introduce the following classes of expressions (values) of the abstract type T:

    +
      +
    • +

      Constant expressions: for the types int and string, these are all integer/string constants; for T, these are all expressions like (C E1 ... Er) : T, where the combinator C : T1->T2->...->Tr->T is a constructor, and Ei : Ti is constant expressions of types Ti. In other words, a constant expression is an S-expression consisting of only constructors and constant of primitive types.

      +
      • +
    • +

      Surface expressions are expressions that outwardly contain a functional combinator whose arguments, however, are constant expressions of the appropriate types. In other words, the functional combinator is resolved only at the outer level. (This is not entirely true; see the full explanation below).

      +
      • +
    • +

      Functional expressions: These are expressions that may contain any combinators or constants at all levels.

      +
      • +
    +

    In practice, we most frequently need constant values (for storage and passing any data structures, in particular, responses to RPC queries) and surface expressions (for example, as RPC queries: then the functional combinator of the outer level is the name of the RPC function that we want to call, while its parameters are the arguments, which are constant values, for invoking the function). In some cases, arbitrary functional expressions are helpful (for example, it we want to remotely transmit the result of one RPC query to a different RPC query).

    +

    We will use c(T) to denote a subtype of the abstract type T, whose values are constant expressions of type T. Clearly, c(T) possesses approximately the same constructors as T itself (with the types of all arguments Ti replaced by c(Ti), but it does not have functional combinators.

    +

    Analogously, we will use f(T) to denote a subtype of T, whose values are surface expressions of type T. Clearly, the combinators of f(T) are essentially functional combinators of type T, but c() applies to the types of these combinators’ arguments: The combinator A : T1->...->Tr->T turns into A' : c(T1)->...->c(Tr)->f(T). (See the clarification of this rule below.)

    +

    Thus, we have defined two “functionals” c : Type -> Type and f : Type -> Type, such that forall T : Type, c(T) :- T and forall T : Type, f(T) :- T (writing T :- T' means that T is contained in T', or that T is a subtype of T').

    +

    We will assume that c and f are idempotent.

    +

    Naked types

    +

    From the perspective of abstract type theory, naked types (in contrast to built-in primitive types like int and string are unnecessary. However, they are extremely useful in practice.

    +

    Therefore, TL introduces the (partially defined) idempotent unary operator %, which turns a standard functional (e.g. an expression of type ...->Type or simply Type) into a different standard functional of the same type. If T is a type, then from an abstract theoretical point of view, %T is equivalent to c(T). In other words, the values of %T are the constant values of T. If T is a k-arity standard expression, then T : S1 -> ... -> Sk -> Type, where each Si=Type or #, then by definition %T is a k-arity standard expression with the same arity, which is defined by the equation (%T) a1 ... ak = % (T a1 ... ak).

    +

    When a constant value of type %T is serialized, it is first serialized as a value of type T (assuming that T is not already a naked type itself). Then the first character of the serialization is discarded (e.g. the name of the enclosing combinator). Therefore, %T is a only a valid type expression if there is not more than one constructor for %T. The expression %T, where T : S1 -> ... -> Sk -> Type, is valid, if for any choice of parameters a1 : S1, ... , ak : Sk, the type T a1 ... ak does not have more than one constructor. Using % in other instances is incorrect.

    +

    If for every value of the parameters a1 : S1, ..., ak : Sk, there is exactly one constructor C for T a1 ... ak, then TL allows writing C a1 ... ak instead of %T a1 ... ak or %(T a1 .. ak). In other words, in certain situations the identifier C is a synonym for %T. This is only allowed in the context of a type (when specifying the type of a combinator’s field or result).

    +

    Moreover, it is assumed that %Int = int and %String = string.

    +

    ! modifier

    +

    In TL, the idempotent operator ! can modify any type, actually making surface values be allowed when its constant values are serialized. However, if T is a standard function like S1->..->Sr->Type, then !T is defined using the equation (!T) a1 ... ar = !(T a1 ... ar), for any a1:S1, ..., ar:Sr.

    +

    The ! operator is only allowed in a definition of the types of fields of functional combinators. It is usually used as a type prefix, for example:

    +
    set_timeout {X:Type} timeout:int f:!X = X;
    +

    In this case, the set_timeout “wrapper” is defined. It takes two explicit parameters: the integer timeout and a surface expression of type X. X : Type is itself an implicit parameter (it is not explicitly stated, rather it is inferred from the values of the other parameters and their types). A similar kind of wrapper may be helpful for modifying the action of RPC queries (which are surface expressions of various types). For example, suppose we have the function

    +
    factorial n:int = int;
    +

    then we can wrap the RPC query (factorial 100) as follows: (set_timeout 200 (factorial 100)). This expression is still a surface value of type int, which means it can be passed as an RPC query.

    +

    A consecutive pair of two computations is another example:

    +
    pair {X Y : Type} x:X y:Y = Pair X Y;  // constructor
+seq_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for sequential computation
+par_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for parallel computation
    +

    Now the RPC query (seq_pair (factorial 2) (factorial 3)) : Pair int int first calculates factorial 2, then factorial 3, and returns the pair (pair 2 6). In this case, the sequence of operations isn’t important, because they do not have side effects. It would have been just as well to use (par_pair (factorial 2) (factorial 3)). However, this is not always the case.

    +

    We can also define an analogy to a “comma” operation:

    +
    comma {X Y : Type} x:!X y:!Y = Y;
    +

    For example, this operation could first calculate x, then forget the result, calculate y, and return y.

    +

    Note that the semantics of the seq_pair, par_pair and comma wrappers are indeed defined where they are implemented (like the semantics of all other functional combinators), not by their TL declaration.

    +

    In principle, polymorphic wrappers like set_timeout can also be applied, for example, to “annotate” a RPC response’s constant values. For example, the server might return a response to a query together with the time it was calculated. However, a value of type !X must be constant, because that is what is expected as the enclosing expression’s value. In other words, set_timeout 239 E is a constant/surface value of type X if and only if E is such itself.

    +

    $ modifier

    +

    The idempotent modifier $ permits the use of arbitrary functional values of an appropriate type in contexts where only constants or surface values are usually allowed. It recursively transforms all combinators for all of the types involved, canceling the action of % and affixing $ to the parameter types and result of all combinators ($ is also added to the front of the transformed combinators). Moreover, built-in types are also transformed (in the final stage): $int = Int and $string = String.

    +

    This may be useful to create an RPC query that performs a “deep computation” of the expression passed to it:

    +
    compute {X:Type} expr:$X = X;
    +

    For example, now we can transmit the following as an RPC query:

    +
    (compute ($factorial ($factorial (int 3)))) : int
    +

    (Note that the three has become clothed; the combinator $factorial has type $int -> $int).

    +

    This is very powerful tool. It does not have to be implemented in very simple versions of TL. $ is not encountered in currently used TL schemas.

    +

    More on modifiers

    +

    In fact, at least in terms of its application to serialization, the TL language by default implies the c() modifier around all combinators’ parameter types and results, while ! and $ cancel it (more accurately, ! only cancels, and in some sense $ reverses the meaning). This is why there is no explicit c() modifier in TL and why it is assumed that all functions only accept constant values and return constant results, unless otherwise specified.

    +

    You may think that some functional combinators may have a type such as partial_factorial n:int = $int; and that the RPC query (partial_factorial 3) might then unexpectedly return ($product (int 3) ($product (int 2) ($product (int 1) (int 1)))) : $int ...

    +

    It is probably more correct to think about the ! modifier as follows. All types initially include only constant values (and only constructors). The ! modifier makes a new type (it’s twin) out of each type. This new type has no inherent constructors. Functional combinators differ from constructors in that ! is implicitly added in front of their result’s type. After this, the (local or remote) process of calculating the expression can be represented using the polymorphic function eval : !X -> X.

    +

    Optional combinator parameters and their values

    +

    See Optional combinator parameters and their values.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + 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)

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-dependent.html b/data/corefork.telegram.org/mtproto/TL-dependent.html new file mode 100644 index 0000000000..bb1c22e608 --- /dev/null +++ b/data/corefork.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.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-formal.html b/data/corefork.telegram.org/mtproto/TL-formal.html new file mode 100644 index 0000000000..1bccc7538d --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-formal.html @@ -0,0 +1,319 @@ + + + + + TL-formal + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    TL-formal

    + +

    See also TL Language. +For the syntax of declaring combinators, see in article Formal declaration of TL combinators. +For the syntax of patterns, see in article Formal declaration of TL patterns.

    +

    Tokens

    +

    Comments are the same as in C/C++. They are removed by a lexical parser (for example, being replaced by a single space). Whitespace separates tokens. Except for string constants, tokens cannot contain spaces.

    +

    Character classes:

    +
    +

    lc-letter ::= a | b | ... | z
    +uc-letter ::= A | B | ... | Z
    +digit ::= 0 | 1 | ... | 9
    +hex-digit ::= digit | a | b | c | d | e | f
    +underscore ::= _
    +letter ::= lc-letter | uc-letter
    +ident-char ::= letter | digit | underscore

    +
    +

    Simple identifiers and keywords:

    +
    +

    lc-ident ::= lc-letter { ident-char }
    +uc-ident ::= uc-letter { ident-char }
    +namespace-ident ::= lc-ident
    +lc-ident-ns ::= [ namespace-ident . ] lc-ident
    +uc-ident-ns ::= [ namespace-ident . ] uc-ident
    +lc-ident-full ::= lc-ident-ns [ # hex-digit *8 ]

    +
    +

    Tokens:

    +
    +

    underscore ::= _
    +colon ::= :
    +semicolon ::= ;
    +open-par ::= (
    +close-par ::= )
    +open-bracket ::= [
    +close-bracket ::= ]
    +open-brace ::= {
    +close-brace ::= }
    +triple-minus ::= ---
    +nat-const ::= digit { digit }
    +lc-ident-full
    +lc-ident
    +uc-ident-ns
    +equals ::= =
    +hash ::= #
    +question-mark ::= ?
    +percent ::= %
    +plus ::= +
    +langle ::= <
    +rangle ::= >
    +comma ::= ,
    +dot ::= .
    +asterisk ::= *
    +excl-mark ::= !
    +Final-kw ::= Final
    +New-kw ::= New
    +Empty-kw ::= Empty

    +
    +

    Final is a reserved keyword, e.g. a special token. Words like Type are not keywords, rather they are identifiers with preset values.

    +

    Tokens consisting of one or more constant symbols shall be hereafter denoted using terms in quotation marks (for example, --- replaces triple-minus).

    +

    Syntax

    +

    General syntax of a TL program

    +

    Syntactically, a TL program consists of a stream of tokens (separated by spaces, which are ignored at this stage). General program structure:

    +
    +

    TL-program ::= constr-declarations { --- functions --- fun-declarations | --- types --- constr-declarations }

    +
    +

    Here the constructor- and function declarations are nearly identical in their syntax (they are both combinators):

    +
    +

    constr-declarations ::= { declaration }
    +fun-declarations ::= { declaration }

    +
    +

    There are various declarations:

    +
    +

    declaration ::= combinator-decl | partial-app-decl | final-decl

    +
    +

    Before explaining how declarations of combinators, partial applications, and type finalization are given, we will introduce additional syntactical categories:

    +

    Syntactical categories and constructions

    +

    The concept of an expression (expr) is important. There are type expressions (type-expr) and numeric expressions (nat-expr). However, they are defined the same way. Their correctness as type- or numeric expressions is checked when the type of the analyzed expression is checked.

    +
    +

    type-expr ::= expr
    +nat-expr ::= expr
    +expr ::= { subexpr }
    +subexpr ::= term | nat-const + subexpr | subexpr + nat-const
    +term ::= ( expr ) | type-ident | var-ident | nat-const | % term | type-ident < expr { , expr } >
    +type-ident ::= boxed-type-ident | lc-ident-ns | #
    +boxed-type-ident ::= uc-ident-ns
    +var-ident ::= lc-ident | uc-ident
    +type-term ::= term
    +nat-term ::= term

    +
    +

    Note that writing E = E_1 E_2 ... E_n in the expression for expr means applying the function E_1 to the argument E_2, applying the result to E_3, etc. Specifically, E_1 E_2 E_3 = (E_1 E_2) E_3. A solitary # is included in type-ident, because it is actually the identifier for a built-in type (# alias nat).

    +

    The expression E<E_1,...,E_n> is syntactic sugar for (E (E_1) ... (E_n)), i.e. both expressions are transformed into the same internal representation.

    +

    Combinator declarations

    +
    +

    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-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-def ::= var-ident [ . nat-const ] ?
    +result-type ::= boxed-type-ident { subexpr }
    +result-type ::= boxed-type-ident < subexpr { , subexpr } >

    +
    +

    See Formal declaration of TL combinators for a description of what exactly this means. Here we will only note that when declaring the type of a combinator’s next argument, only the names of previously arranged (more to the left) arguments of the same combinator may be used as variables, but when declaring the result type you can use all of its parameters (of type Type and #).

    +

    Note that the names of combinators declared in this way may be used in TL itself only as the corresponding bare types. The only combinators that appear in declarations are built-in: O : # and S : # -> #.

    +

    There are also “pseudo-declarations” that are allowed only to declare built-in types (such as int ? = Int;):

    +
    +

    builtin-combinator-decl ::= full-combinator-id ? = boxed-type-ident ;

    +
    +

    Partial applications (patterns)

    +
    +

    partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
    +partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
    +partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

    +
    +

    See Formal declaration of TL patterns.

    +

    Type finalization

    +
    +

    final-decl ::= New boxed-type-ident ; | Final boxed-type-ident ; | Empty boxed-type-ident ;

    +
    +

    This type of declaration means that there must not be any constructor for the indicated type: before the declaration for New and after the declaration for Final. The keyword Empty enables both effects.

    +

    Predefined identifiers

    +

    Nearly all predefined identifiers may be given using the following schema (usually located in common.tl):

    +
    +

    /////
    +//
    +// Common Types
    +//
    +/////

    +

    // Built-in types
    +int ? = Int;
    +long ? = Long;
    +double ? = Double;
    +string ? = String;

    +

    // Boolean emulation
    +boolFalse = Bool;
    +boolTrue = Bool;

    +

    // Boolean for diagonal queries
    +boolStat statTrue:int statFalse:int statUnknown:int = BoolStat;

    +

    // Vector
    +vector {t:Type} # [t] = Vector t;
    +tuple {t:Type} {n:#} [t] = Tuple t n;
    +vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;

    +

    /////
    +//
    +// Result- (Maybe-) types
    +//
    +/////

    +

    resultFalse {t:Type} = Maybe t;
    +resultTrue {t:Type} result:t = Maybe t;

    +

    pair {X:Type} {Y:Type} a:X b:Y = Pair X Y;
    +map {X:Type} {Y:Type} key:X value:Y = Map X Y;

    +

    Empty False;
    +true = True;

    +

    unit = Unit;

    +
    +
      +
    • +

      Predefined identifier Type: This type signifies the type of all types. It is usually used to specify the types of optional parameters in the constructors of polymorphic types. If strongly desired, it can be used in its own right, but this is very rarely needed in practice.

      +
      • +
    • +

      Identifier #: This type is used to specify a special type of nonnegative integers in the range from 0 to 2^31-1; its main purpose is the same as that of Type. There are two built-in constructors: O : # and S : # -> # (“null” and “next number”, respectively), which work as if # was defined using the schema

      +
      • +
    +
    +

    O = #;
    +S # = #;

    +
    +
      +
    • +

      Identifier Tuple: Type -> # -> Type denotes a set of the specified number of values of the indicated type. In other words, Tuple X n means “a set of n values of type X".

      +
      • +
    • +

      The typeBool, with two constructors boolTrue and boolFalse, is used to transmit Boolean values.

      +
      • +
    • +

      The constructor-less type False may be used instead of undeclared or invalid types in the construction of a TL schema, because any attempt to (de)serialize a value of type False will produce an error. Usage Example:

      +
      • +
    +
    +

    user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string reserved3:flags.3?False reserved4:flags.4?False = User flags;
    +user_present {flags:#} info:%(User flags) = UserInfo flags;
    +user_absent {flags:#} = UserInfo flags;
    +getUser flags:# id:int = !UserInfo flags;

    +
    +

    In the future, bits 3 and 4 in the flags field may be used to transmit new fields after changing the names and types of the reserved3 and reserved4 fields. This will change the user constructor’s number, but this isn’t too important, since the User flags type is only used as a bare type. Transmitting bits 3 or 4 in the flags field in a getUser query before these fields have actually been defined will lead to an error in the (de)serialization of the request.

    +
      +
    • The type True with a single null constructor true plays a role similar to the void type in C/C++. It is especially useful as a bare type %True, alias true, because its serialization has zero length. For example, the first_name:flags.1?string constructor used above is in fact shorthand for (the as-yet unsupported) alternative-type general constructor first_name:(flags.1?string:true).
      • +
    +

    When directly used in a conditional field it may simply indicate the presence (absence) of a certain parameter with void type. +If the conditional field exists, the associated parameter will not be populated; the conditional field simply exists and the existance value can be used to perform certain operations, example:

    +
    user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string bot:flags.3?true reserved4:flags.4?False = User flags;
    +

    If bit 3 of the flags parameter isn't set, the user is a normal user. +If bit 3 of the flags parameter is set, this indicates that the specified user is a bot: however, during deserialization, the bot parameter must not be assigned any value, since true is actually a void type.

    +
      +
    • The typeUnit with a single null constructor Unit is similar to the previous type.
      • +
    +

    ANTLR definition

    +

    An ANLTR definition of TL grammar can be found here ».

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/core.telegram.org/mtproto/TL-optargs.html b/data/corefork.telegram.org/mtproto/TL-optargs.html similarity index 98% rename from data/core.telegram.org/mtproto/TL-optargs.html rename to data/corefork.telegram.org/mtproto/TL-optargs.html index 5c71a8e2bf..8aa55122a6 100644 --- a/data/core.telegram.org/mtproto/TL-optargs.html +++ b/data/corefork.telegram.org/mtproto/TL-optargs.html @@ -114,9 +114,9 @@
    -
    Platform
    +
    Platform
    @@ -133,7 +133,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/mtproto/TL-patterns.html b/data/corefork.telegram.org/mtproto/TL-patterns.html new file mode 100644 index 0000000000..a3ef5eb43e --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-patterns.html @@ -0,0 +1,129 @@ + + + + + TL-patterns + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    TL-patterns

    + +
    +

    partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
    +partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
    +partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

    +
    +

    According to the original design, templates must be used to replace concrete values in the first few or all of the optional arguments of a constructor or polymorphic type. For example, if Tuple int 10 is used frequently, you can declare a template for it, which will cause the appropriate constructors to be generated automatically. When using such a constructor there may be nowhere to pass an int type or the tuple size 10. Similarly, it was originally planned to declared templates for Vector int, Vector string, etc. in order to generate constructors for each vector type being used type. These constructors would make it possible during deserialization to determine what kind of array is being transmitted.

    +

    Templates are not used now. Instead, the same universal constructors (for example, vector {t:Type} [t] = Vector t) are used with the values of the optional parameters being inferred from the type of the result (if we already know from the schema that in this location there must be a Vector int during deserialization, we understand that we will see the universal vector constructor in which t is equal to int).

    +

    This approach is better in that it is not necessary to define Vector SomeType templates in advance for all possible types in order to generate their own constructors for each of these cases. Nevertheless, there is a drawback. If someone wants to transmit the serialization of a value of the clothed type Vector int as a serialization of a value of type Object, a problem arises during serialization: after seeing the universal vector constructor and then reading the vector length, we cannot determine what type of values should be expected next.

    +

    In theory, this problem can be solved by using the full form of the constructor (@vector) corresponding to vector (it is automatically defined and is different in that all of the optional parameters become required), or by defining

    +
    +

    object X:Type X = TypedObject

    +
    +

    and passing the object type explicitly. Type serialization is required in both cases.

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-polymorph.html b/data/corefork.telegram.org/mtproto/TL-polymorph.html new file mode 100644 index 0000000000..658321fb15 --- /dev/null +++ b/data/corefork.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. +
    2. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
      3. +
    3. serialize the head of the list (hd) as a value of type X;
      4. +
    4. serialize the tail of the list as a value of the polymorphic type List X.
      5. +
    +

    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
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/mtproto/TL-tl.html b/data/corefork.telegram.org/mtproto/TL-tl.html new file mode 100644 index 0000000000..6eb37b1df6 --- /dev/null +++ b/data/corefork.telegram.org/mtproto/TL-tl.html @@ -0,0 +1,308 @@ + + + + + TL schema for serialization of TL schemas + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    TL schema for serialization of TL schemas

    + +

    If necessary, a TL schema can be serialized in binary form. Here, this serialization format is defined by a TL schema (usually stored in the file tl.tl). This can be useful, for example, to make it possible to write a parser one time for converting a TL schema from text form (stored in the file something.tl) to binary form (stored in the file something.tlo). All other programs (for example, auto-generators of TL-(de)serializers for various programming languages) only need to know how to read .tlo files, which only requires generating an automatic deserializer according to the schema presented below.

    +

    First, a fragment of the file common.tl with certain required built-in types:

    +
    /////
+//
+// Common Types (source file common.tl, only necessary definitions included)
+//
+/////
+
+// Built-in types
+int ? = Int;
+long ? = Long;
+double ? = Double;
+string ? = String;
+
+// Boolean emulation
+boolFalse = Bool;
+boolTrue = Bool;
+
+// Vector
+vector {t:Type} # [t] = Vector t;
+tuple {t:Type} {n:#} [t] = Tuple t n;
+vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;
+
+Empty False;
+true = True;
    +

    Next, properly, comes tl.tl itself. Note that the declaration for a fairly complex data type required only twenty lines in TL. This demonstrates the expressiveness and compactness of the TL language.

    +
    /////
+//
+// Serialized binary TL-schema in TL format, source file tl.tl
+//
+/////
+tls.schema_v2 version:int date:int types_num:# types:types_num*[tls.Type] 
+
+    constructor_num:# constructors:constructor_num*[tls.Combinator] 
+    functions_num:# functions:functions_num*[tls.Combinator] = tls.Schema;
+tls.type name:int id:string constructors_num:int flags:int arity:int params_type:long = tls.Type;
+
+tls.combinator name:int id:string type_name:int left:tls.CombinatorLeft right:tls.CombinatorRight = tls.Combinator;
+tls.combinatorLeftBuiltin = tls.CombinatorLeft;
+tls.combinatorLeft args_num:# args:args_num*[tls.Arg] = tls.CombinatorLeft;
+tls.combinatorRight value:tls.TypeExpr = tls.CombinatorRight;
+
+tls.arg id:string flags:# var_num:flags.1?int exist_var_num:flags.2?int exist_var_bit:flags.2?int type:tls.TypeExpr = tls.Arg;
+
+tls.exprType _:tls.TypeExpr = tls.Expr;
+
+tls.exprNat _:tls.NatExpr = tls.Expr;
+tls.natConst value:int = tls.NatExpr;
+
+tls.natVar dif:int var_num:int = tls.NatExpr;
+tls.typeVar var_num:int flags:int = tls.TypeExpr;
+
+tls.array multiplicity:tls.NatExpr args_num:# args:args_num*[tls.Arg] = tls.TypeExpr;
+tls.typeExpr name:int flags:int children_num:# children:children_num*[tls.Expr] = tls.TypeExpr;
    +

    Remarks

    +

    Schema serialization (version 2) always begins with the index number of the tls.schema_v2 constructor for tls.Schema. +Because the CRC32 of the string

    +
    tls.schema_v2 version:int date:int types_num:# types:types_num*[ tls.Type ] constructor_num:# constructors:constructor_num*[ tls.Combinator ] functions_num:# functions:functions_num*[ tls.Combinator ] = tls.Schema
    +

    is 0x3a2f9be2, this constant is in fact the magic number for tlo files in the current version’s format. +If the format is extended in the future (for example, if TL’s additional features are supported), then a tls.schema_v3 constructor with a different number will appear.

    +

    Example

    +

    If one adds declarations for the used built-in types (like int ? = Int;) from the file common.tl before tl.tl and serialize the resulting schema, the following binary data is obtained (tl.tlo):

    +
    +

    0000: 3a2f9be2 00000000 51fec698 00000015 12eb4386 70659eff 00002301 00000000
    +0020: 00000000 00000000 00000000 00000000 12eb4386 250be282 6f6f4204 0000006c
    +0040: 00000002 02000010 00000000 00000000 00000000 12eb4386 2210c154 756f4406
    +0060: 00656c62 00000001 02000000 00000000 00000000 00000000 12eb4386 00000000
    +0080: 6c614605 00006573 00000000 00000401 00000000 00000000 00000000 12eb4386
    +00a0: a8509bda 746e4903 00000001 02000001 00000000 00000000 00000000 12eb4386
    +00c0: 22076cba 6e6f4c04 00000067 00000001 02000001 00000000 00000000 00000000
    +00e0: 12eb4386 b5286e24 72745306 00676e69 00000001 02000001 00000000 00000000
    +0100: 00000000 12eb4386 3fedd339 75725404 00000065 00000001 02000000 00000000
    +0120: 00000000 00000000 12eb4386 9770768a 70755405 0000656c 00000001 02000000
    +0140: 00000002 00000002 00000000 12eb4386 2cecf817 70795404 00000065 00000000
    +0160: 00000000 00000000 00000000 00000000 12eb4386 1cb5c415 63655606 00726f74
    +0180: 00000001 02000008 00000001 00000000 00000000 12eb4386 10133f47 6365560b
    +01a0: 54726f74 6c61746f 00000001 02000000 00000001 00000000 00000000 12eb4386
    +01c0: 29dfe61b 736c7407 6772412e 00000001 02000000 00000000 00000000 00000000
    +01e0: 12eb4386 5c0a1ed5 736c740e 6d6f432e 616e6962 00726f74 00000001 02000000
    +0200: 00000000 00000000 00000000 12eb4386 8133d9ba 736c7412 6d6f432e 616e6962
    +0220: 4c726f74 00746665 00000002 02000010 00000000 00000000 00000000 12eb4386
    +0240: 2c064372 736c7413 6d6f432e 616e6962 52726f74 74686769 00000001 02000000
    +0260: 00000000 00000000 00000000 12eb4386 307d41a0 736c7408 7078452e 00000072
    +0280: 00000002 02000010 00000000 00000000 00000000 12eb4386 c2635441 736c740b
    +02a0: 74614e2e 72707845 00000002 02000010 00000000 00000000 00000000 12eb4386
    +02c0: 3a2f9be2 736c740a 6863532e 00616d65 00000001 02000000 00000000 00000000
    +02e0: 00000000 12eb4386 12eb4386 736c7408 7079542e 00000065 00000001 02000000
    +0300: 00000000 00000000 00000000 12eb4386 193fd378 736c740c 7079542e 70784565
    +0320: 00000072 00000003 02000010 00000000 00000000 00000000 00000018 5c0a1ed5
    +0340: bc799737 6f6f6209 6c61466c 00006573 250be282 4c12c6d9 00000000 2c064372
    +0360: c1863d08 250be282 00000000 00000000 5c0a1ed5 997275b5 6f6f6208 7572546c
    +0380: 00000065 250be282 4c12c6d9 00000000 2c064372 c1863d08 250be282 00000000
    +03a0: 00000000 5c0a1ed5 2210c154 756f6406 00656c62 2210c154 cd211f63 2c064372
    +03c0: c1863d08 2210c154 00000000 00000000 5c0a1ed5 a8509bda 746e6903 a8509bda
    +03e0: cd211f63 2c064372 c1863d08 a8509bda 00000000 00000000 5c0a1ed5 22076cba
    +0400: 6e6f6c04 00000067 22076cba cd211f63 2c064372 c1863d08 22076cba 00000000
    +0420: 00000000 5c0a1ed5 b5286e24 72747306 00676e69 b5286e24 cd211f63 2c064372
    +0440: c1863d08 b5286e24 00000000 00000000 5c0a1ed5 3fedd339 75727404 00000065
    +0460: 3fedd339 4c12c6d9 00000000 2c064372 c1863d08 3fedd339 00000000 00000000
    +0480: 5c0a1ed5 9770768a 70757405 0000656c 9770768a 4c12c6d9 00000003 29dfe61b
    +04a0: 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000 29dfe61b
    +04c0: 00006e01 00020005 00000001 c1863d08 70659eff 00000000 00000000 29dfe61b
    +04e0: 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
    +0500: 00000000 00000000 0142ceae 00000000 00000000 2c064372 c1863d08 9770768a
    +0520: 00000000 00000002 ecc9da78 0142ceae 00000000 00000000 dcb49bd8 4e8a14f0
    +0540: 00000000 00000001 5c0a1ed5 1cb5c415 63657606 00726f74 1cb5c415 4c12c6d9
    +0560: 00000003 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000
    +0580: 00000000 29dfe61b 00000000 00000004 00000001 c1863d08 70659eff 00000000
    +05a0: 00000000 29dfe61b 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001
    +05c0: 00000001 29dfe61b 00000000 00000000 0142ceae 00000000 00000000 2c064372
    +05e0: c1863d08 1cb5c415 00000000 00000001 ecc9da78 0142ceae 00000000 00000000
    +0600: 5c0a1ed5 10133f47 6365760b 54726f74 6c61746f 10133f47 4c12c6d9 00000003
    +0620: 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000
    +0640: 29dfe61b 746f740b 635f6c61 746e756f 00000000 c1863d08 a8509bda 00000001
    +0660: 00000000 29dfe61b 63657606 00726f74 00000000 c1863d08 1cb5c415 00000001
    +0680: 00000001 ecc9da78 0142ceae 00000000 00000000 2c064372 c1863d08 10133f47
    +06a0: 00000000 00000001 ecc9da78 0142ceae 00000000 00000000 5c0a1ed5 29dfe61b
    +06c0: 736c7407 6772612e 29dfe61b 4c12c6d9 00000006 29dfe61b 00646902 00000000
    +06e0: c1863d08 b5286e24 00000001 00000000 29dfe61b 616c6605 00007367 00000004
    +0700: 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b 72617607 6d756e5f
    +0720: 00000002 00000000 00000001 c1863d08 a8509bda 00000001 00000000 29dfe61b
    +0740: 6978650d 765f7473 6e5f7261 00006d75 00000002 00000000 00000002 c1863d08
    +0760: a8509bda 00000001 00000000 29dfe61b 6978650d 765f7473 625f7261 00007469
    +0780: 00000002 00000000 00000002 c1863d08 a8509bda 00000001 00000000 29dfe61b
    +07a0: 70797404 00000065 00000000 c1863d08 193fd378 00000000 00000000 2c064372
    +07c0: c1863d08 29dfe61b 00000000 00000000 5c0a1ed5 5c0a1ed5 736c740e 6d6f632e
    +07e0: 616e6962 00726f74 5c0a1ed5 4c12c6d9 00000005 29dfe61b 6d616e04 00000065
    +0800: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 00646902 00000000
    +0820: c1863d08 b5286e24 00000001 00000000 29dfe61b 70797409 616e5f65 0000656d
    +0840: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 66656c04 00000074
    +0860: 00000000 c1863d08 8133d9ba 00000000 00000000 29dfe61b 67697205 00007468
    +0880: 00000000 c1863d08 2c064372 00000000 00000000 2c064372 c1863d08 5c0a1ed5
    +08a0: 00000000 00000000 5c0a1ed5 cd211f63 736c7419 6d6f632e 616e6962 4c726f74
    +08c0: 42746665 746c6975 00006e69 8133d9ba 4c12c6d9 00000000 2c064372 c1863d08
    +08e0: 8133d9ba 00000000 00000000 5c0a1ed5 4c12c6d9 736c7412 6d6f632e 616e6962
    +0900: 4c726f74 00746665 8133d9ba 4c12c6d9 00000002 29dfe61b 67726108 756e5f73
    +0920: 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b
    +0940: 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000 00000001
    +0960: 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000 2c064372
    +0980: c1863d08 8133d9ba 00000000 00000000 5c0a1ed5 2c064372 736c7413 6d6f632e
    +09a0: 616e6962 52726f74 74686769 2c064372 4c12c6d9 00000001 29dfe61b 6c617605
    +09c0: 00006575 00000000 c1863d08 193fd378 00000000 00000000 2c064372 c1863d08
    +09e0: 2c064372 00000000 00000000 5c0a1ed5 ecc9da78 736c740c 7078652e 70795472
    +0a00: 00000065 307d41a0 4c12c6d9 00000001 29dfe61b 00000000 00000000 c1863d08
    +0a20: 193fd378 00000000 00000000 2c064372 c1863d08 307d41a0 00000000 00000000
    +0a40: 5c0a1ed5 dcb49bd8 736c740b 7078652e 74614e72 307d41a0 4c12c6d9 00000001
    +0a60: 29dfe61b 00000000 00000000 c1863d08 c2635441 00000000 00000000 2c064372
    +0a80: c1863d08 307d41a0 00000000 00000000 5c0a1ed5 8ce940b1 736c740c 74616e2e
    +0aa0: 736e6f43 00000074 c2635441 4c12c6d9 00000001 29dfe61b 6c617605 00006575
    +0ac0: 00000000 c1863d08 a8509bda 00000001 00000000 2c064372 c1863d08 c2635441
    +0ae0: 00000000 00000000 5c0a1ed5 4e8a14f0 736c740a 74616e2e 00726156 c2635441
    +0b00: 4c12c6d9 00000002 29dfe61b 66696403 00000000 c1863d08 a8509bda 00000001
    +0b20: 00000000 29dfe61b 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001
    +0b40: 00000000 2c064372 c1863d08 c2635441 00000000 00000000 5c0a1ed5 3a2f9be2
    +0b60: 736c740d 6863732e 5f616d65 00003276 3a2f9be2 4c12c6d9 00000008 29dfe61b
    +0b80: 72657607 6e6f6973 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
    +0ba0: 74616404 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
    +0bc0: 70797409 6e5f7365 00006d75 00000004 00000000 c1863d08 70659eff 00000000
    +0be0: 00000000 29dfe61b 70797405 00007365 00000000 d9fb20de 4e8a14f0 00000000
    +0c00: 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 12eb4386 00000000
    +0c20: 00000000 29dfe61b 6e6f630f 75727473 726f7463 6d756e5f 00000004 00000001
    +0c40: c1863d08 70659eff 00000000 00000000 29dfe61b 6e6f630c 75727473 726f7463
    +0c60: 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
    +0c80: 00000000 00000000 c1863d08 5c0a1ed5 00000000 00000000 29dfe61b 6e75660d
    +0ca0: 6f697463 6e5f736e 00006d75 00000004 00000002 c1863d08 70659eff 00000000
    +0cc0: 00000000 29dfe61b 6e756609 6f697463 0000736e 00000000 d9fb20de 4e8a14f0
    +0ce0: 00000000 00000002 00000001 29dfe61b 00000000 00000000 c1863d08 5c0a1ed5
    +0d00: 00000000 00000000 2c064372 c1863d08 3a2f9be2 00000000 00000000 5c0a1ed5
    +0d20: 12eb4386 736c7408 7079742e 00000065 12eb4386 4c12c6d9 00000006 29dfe61b
    +0d40: 6d616e04 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
    +0d60: 00646902 00000000 c1863d08 b5286e24 00000001 00000000 29dfe61b 6e6f6310
    +0d80: 75727473 726f7463 756e5f73 0000006d 00000000 c1863d08 a8509bda 00000001
    +0da0: 00000000 29dfe61b 616c6605 00007367 00000000 c1863d08 a8509bda 00000001
    +0dc0: 00000000 29dfe61b 69726105 00007974 00000000 c1863d08 a8509bda 00000001
    +0de0: 00000000 29dfe61b 7261700b 5f736d61 65707974 00000000 c1863d08 22076cba
    +0e00: 00000001 00000000 2c064372 c1863d08 12eb4386 00000000 00000000 5c0a1ed5
    +0e20: 0142ceae 736c740b 7079742e 72615665 193fd378 4c12c6d9 00000002 29dfe61b
    +0e40: 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
    +0e60: 616c6605 00007367 00000000 c1863d08 a8509bda 00000001 00000000 2c064372
    +0e80: c1863d08 193fd378 00000000 00000000 5c0a1ed5 d9fb20de 736c7409 7272612e
    +0ea0: 00007961 193fd378 4c12c6d9 00000003 29dfe61b 6c756d0c 6c706974 74696369
    +0ec0: 00000079 00000000 c1863d08 c2635441 00000000 00000000 29dfe61b 67726108
    +0ee0: 756e5f73 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000
    +0f00: 29dfe61b 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000
    +0f20: 00000001 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000
    +0f40: 2c064372 c1863d08 193fd378 00000000 00000000 5c0a1ed5 c1863d08 736c740c
    +0f60: 7079742e 70784565 00000072 193fd378 4c12c6d9 00000004 29dfe61b 6d616e04
    +0f80: 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 616c6605
    +0fa0: 00007367 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 6968630c
    +0fc0: 6572646c 756e5f6e 0000006d 00000004 00000000 c1863d08 70659eff 00000000
    +0fe0: 00000000 29dfe61b 69686308 6572646c 0000006e 00000000 d9fb20de 4e8a14f0
    +1000: 00000000 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 307d41a0
    +1020: 00000000 00000000 2c064372 c1863d08 193fd378 00000000 00000000 00000000

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + 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.*
      • +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + 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

    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/passport/sdk-android.html b/data/corefork.telegram.org/passport/sdk-android.html deleted file mode 100644 index 9784921198..0000000000 --- a/data/corefork.telegram.org/passport/sdk-android.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - 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.

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - - - diff --git a/data/corefork.telegram.org/themes.html b/data/corefork.telegram.org/themes.html new file mode 100644 index 0000000000..c0f349d55b --- /dev/null +++ b/data/corefork.telegram.org/themes.html @@ -0,0 +1,143 @@ + + + + + Creating Custom Cloud Themes + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Creating Custom Cloud Themes

    + +

    Official Telegram apps support custom cloud themes as of version 5.11. Everyone is welcome to create and share their themes.

    +

    Creating a theme

    +

    You can use the Online Theme Editor (use a VPN if it is blocked in your country) to create new Telegram themes from scratch or edit existing ones. Simply log in with your Telegram account and pick a platform to start editing the relevant theme file – or import an existing theme.

    +
      +
    • Set a name for your theme using the name attribute
      • +
    • Set colors for elements using hex codes or the color picker
      • +
    • Press ‘Save and apply theme’ to push changes to all users of your theme
      • +
    +

    Checking your theme in-app

    +

    Once you have saved a theme for the first time, Telegram will send you a message with its sharing link. Open the link in the app to switch to your theme.

    +

    You can always switch to your theme in Settings > Chat Settings. On iOS and MacOS native app – Settings > Appearance.

    +

    Publishing your theme

    +

    Each theme has a t.me/addtheme link which people can use to switch to your theme. You can choose a beautiful short link (e.g., https://t.me/addtheme/desert) by changing the shortname attribute. If you add support for multiple platforms, the same link can be used for setting your theme on all of them.

    +

    Updating your theme

    +

    Your theme gets updated automatically for all its users whenever you save and apply changes.

    +

    Including a chat background

    +

    Your themes can include a custom wallpaper. To do this, simply go to Settings > Chat Settings > Chat Background. On iOS and MacOS native app – Settings > Appearance > Chat Background.

    +

    Open any background and tap the sharing button in the top right corner, then copy its t.me/bg/... link. In the theme file, set this link as the value of the wallpaper attribute.

    +

    For Telegram Desktop, if you want to make the background tiled, add ?mode=tiled at the end of the link. For example:

    +
    wallpaper: t.me/bg/-jI7lnO3DFABAAAA1vXcFaZP_Vo?mode=tiled
    +

    Creating themes in-app

    +

    If you prefer a more WYSIWYG approach, try creating themes using the in-app tools for customizing appearance. Telegram for Android and Telegram Desktop have advanced in-app theme editors. Telegram for iOS and MacOS allow choosing a custom accent color from the color wheel and a background, then saving the result as a custom theme.

    +

    Once you have saved a new theme in any of the apps, it also becomes accessible in the online editor.

    +

    Read more

    + +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/type/CdnConfig.html b/data/corefork.telegram.org/type/CdnConfig.html deleted file mode 100644 index 4bec9e352c..0000000000 --- a/data/corefork.telegram.org/type/CdnConfig.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - CdnConfig - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    CdnConfig

    - -

    Configuration for CDN file downloads.

    -

    - -
    -
    cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
----functions---
-
-help.getCdnConfig#52029342 = CdnConfig;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    cdnConfigConfiguration for CDN file downloads.
    -

    Methods

    - - - - - - - - - - - - - -
    MethodDescription
    help.getCdnConfigGet configuration for CDN file downloads.
    -

    Related pages

    -

    Encrypted CDNs for Speed and Security

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/InputPrivacyKey.html b/data/corefork.telegram.org/type/ChannelParticipantsFilter.html similarity index 70% rename from data/corefork.telegram.org/type/InputPrivacyKey.html rename to data/corefork.telegram.org/type/ChannelParticipantsFilter.html index add8e6263f..057166248d 100644 --- a/data/corefork.telegram.org/type/InputPrivacyKey.html +++ b/data/corefork.telegram.org/type/ChannelParticipantsFilter.html @@ -2,12 +2,12 @@ - InputPrivacyKey + ChannelParticipantsFilter - - + + - + @@ -36,10 +36,10 @@
    -
    -

    InputPrivacyKey

    +
    +

    ChannelParticipantsFilter

    -

    Privacy key

    +

    Filter for fetching channel participants

    • @@ -52,14 +52,14 @@
    -
    inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
-inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
-inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
-inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
-inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
-inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
-inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
-inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

    +
    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;

    Constructors

    @@ -70,36 +70,36 @@ - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + +
    inputPrivacyKeyStatusTimestampWhether we can see the exact last online timestamp of the userchannelParticipantsRecentFetch only recent participants
    inputPrivacyKeyChatInviteWhether the user can be invited to chatschannelParticipantsAdminsFetch only admin participants
    inputPrivacyKeyPhoneCallWhether the user will accept phone callschannelParticipantsKickedFetch only kicked participants
    inputPrivacyKeyPhoneP2PWhether the user allows P2P communication during VoIP callschannelParticipantsBotsFetch only bot participants
    inputPrivacyKeyForwardsWhether messages forwarded from this user will be anonymouschannelParticipantsBannedFetch only banned participants
    inputPrivacyKeyProfilePhotoWhether people will be able to see the user's profile picturechannelParticipantsSearchQuery participants by name
    inputPrivacyKeyPhoneNumberWhether people will be able to see the user's phone numberchannelParticipantsContactsFetch only participants that are also contacts
    inputPrivacyKeyAddedByPhoneWhether people can add you to their contact list by your phone numberchannelParticipantsMentionsThis filter is used when looking for members to mention.
    diff --git a/data/corefork.telegram.org/type/ImportedContact.html b/data/corefork.telegram.org/type/ImportedContact.html deleted file mode 100644 index a5bf089395..0000000000 --- a/data/corefork.telegram.org/type/ImportedContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ImportedContact - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    ImportedContact

    - -

    Object contains info on a successfully imported contact.

    -

    - -
    -
    importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    importedContactSuccessfully imported contact.
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/InputWebFileLocation.html b/data/corefork.telegram.org/type/InputChannel.html similarity index 84% rename from data/corefork.telegram.org/type/InputWebFileLocation.html rename to data/corefork.telegram.org/type/InputChannel.html index 4e09dceb44..68ed6460a5 100644 --- a/data/corefork.telegram.org/type/InputWebFileLocation.html +++ b/data/corefork.telegram.org/type/InputChannel.html @@ -2,12 +2,12 @@ - InputWebFileLocation + InputChannel - - + + - + @@ -36,10 +36,10 @@
    -
    -

    InputWebFileLocation

    +
    +

    InputChannel

    -

    Location of remote file

    +

    Represents a channel

    • @@ -52,8 +52,9 @@
    -
    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;

    +
    inputChannelEmpty#ee8c1e86 = InputChannel;
+inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
+inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

    Constructors

    @@ -64,12 +65,16 @@ - - + + - - + + + + + +
    inputWebFileLocationLocation of a remote HTTP(s) fileinputChannelEmptyRepresents the absence of a channel
    inputWebFileGeoPointLocationGeolocationinputChannelRepresents a channel
    inputChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
    diff --git a/data/corefork.telegram.org/type/RecentMeUrl.html b/data/corefork.telegram.org/type/InputPeer.html similarity index 73% rename from data/corefork.telegram.org/type/RecentMeUrl.html rename to data/corefork.telegram.org/type/InputPeer.html index d9bcb3d2a3..b4d03a4a8d 100644 --- a/data/corefork.telegram.org/type/RecentMeUrl.html +++ b/data/corefork.telegram.org/type/InputPeer.html @@ -2,12 +2,12 @@ - RecentMeUrl + InputPeer - - + + - + @@ -36,10 +36,10 @@
    -
    -

    RecentMeUrl

    +
    +

    InputPeer

    -

    Recent t.me urls

    +

    Peer

    • @@ -52,11 +52,13 @@
    -
    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;

    +
    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

    @@ -67,24 +69,32 @@ - - + + - - + + - - + + - - + + - - + + + + + + + + + +
    recentMeUrlUnknownUnknown t.me urlinputPeerEmptyAn empty constructor, no user or chat is defined.
    recentMeUrlUserRecent t.me link to a userinputPeerSelfDefines the current user.
    recentMeUrlChatRecent t.me link to a chatinputPeerChatDefines a chat for further interaction.
    recentMeUrlChatInviteRecent t.me invite link to a chatinputPeerUserDefines a user for further interaction.
    recentMeUrlStickerSetRecent t.me stickerset installation URLinputPeerChannelDefines 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/corefork.telegram.org/type/PageListItem.html b/data/corefork.telegram.org/type/InputUser.html similarity index 81% rename from data/corefork.telegram.org/type/PageListItem.html rename to data/corefork.telegram.org/type/InputUser.html index b006e41ab2..12e3526161 100644 --- a/data/corefork.telegram.org/type/PageListItem.html +++ b/data/corefork.telegram.org/type/InputUser.html @@ -2,12 +2,12 @@ - PageListItem + InputUser - - + + - + @@ -36,10 +36,10 @@
    -
    -

    PageListItem

    +
    +

    InputUser

    -

    Item in block list

    +

    Defines a user for subsequent interaction.

    • @@ -52,8 +52,10 @@
    -
    pageListItemText#b92fb6cd text:RichText = PageListItem;
-pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

    +
    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;

    Constructors

    @@ -64,12 +66,20 @@ - - + + - - + + + + + + + + + +
    pageListItemTextList iteminputUserEmptyEmpty constructor, does not define a user.
    pageListItemBlocksList iteminputUserSelfDefines the current user.
    inputUserDefines a user for further interaction.
    inputUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
    diff --git a/data/corefork.telegram.org/type/PageListOrderedItem.html b/data/corefork.telegram.org/type/PageListOrderedItem.html deleted file mode 100644 index 1d07e0bd56..0000000000 --- a/data/corefork.telegram.org/type/PageListOrderedItem.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PageListOrderedItem - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    PageListOrderedItem

    - -

    Represents an instant view ordered list

    -

    - -
    -
    pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
-pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

    -

    Constructors

    - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    pageListOrderedItemTextOrdered list of text items
    pageListOrderedItemBlocksOrdered list of IV blocks
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/PaymentSavedCredentials.html b/data/corefork.telegram.org/type/PaymentSavedCredentials.html deleted file mode 100644 index 0e7bb22a23..0000000000 --- a/data/corefork.telegram.org/type/PaymentSavedCredentials.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentSavedCredentials - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    PaymentSavedCredentials

    - -

    Saved payment credentials

    -

    - -
    -
    paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    paymentSavedCredentialsCardSaved credit card
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/ReceivedNotifyMessage.html b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html deleted file mode 100644 index 83eae56879..0000000000 --- a/data/corefork.telegram.org/type/ReceivedNotifyMessage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ReceivedNotifyMessage - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    ReceivedNotifyMessage

    - -

    Confirmation of message receipt

    -

    - -
    -
    receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

    -

    Constructors

    - - - - - - - - - - - - - -
    ConstructorDescription
    receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/RichText.html b/data/corefork.telegram.org/type/RichText.html deleted file mode 100644 index 209db9a1da..0000000000 --- a/data/corefork.telegram.org/type/RichText.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - RichText - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    RichText

    - -

    Rich text

    -

    - -
    -
    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;

    -

    Constructors

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ConstructorDescription
    textEmptyEmpty rich text element
    textPlainPlain text
    textBoldBold text
    textItalicItalic text
    textUnderlineUnderlined text
    textStrikeStrikethrough text
    textFixedfixed-width rich text
    textUrlLink
    textEmailRich text email link
    textConcatConcatenation of rich texts
    textSubscriptSubscript text
    textSuperscriptSuperscript text
    textMarkedHighlighted text
    textPhoneRich text linked to a phone number
    textImageInline image
    textAnchorText linking to another section of the page
    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/RestrictionReason.html b/data/corefork.telegram.org/type/True.html similarity index 88% rename from data/corefork.telegram.org/type/RestrictionReason.html rename to data/corefork.telegram.org/type/True.html index 3ffe864b2b..d67f5b3273 100644 --- a/data/corefork.telegram.org/type/RestrictionReason.html +++ b/data/corefork.telegram.org/type/True.html @@ -2,12 +2,12 @@ - RestrictionReason + True - - + + - + @@ -36,10 +36,10 @@
    -
    -

    RestrictionReason

    +
    +

    True

    -

    Restriction reason

    +

    See predefined identifiers.

    • @@ -52,7 +52,7 @@
    -
    restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

    +
    true#3fedd339 = True;

    Constructors

    @@ -63,11 +63,13 @@ - - + + -
    restrictionReasonRestriction reasontrueSee predefined identifiers.
    + +

    Related pages

    +

    TL-formal

    diff --git a/data/corefork.telegram.org/type/auth.CheckedPhone b/data/corefork.telegram.org/type/auth.CheckedPhone deleted file mode 100644 index d8e6f611cd..0000000000 --- a/data/corefork.telegram.org/type/auth.CheckedPhone +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Auth.CheckedPhone - - - - - - - - - - - - - -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -

    Auth.CheckedPhone

    - -

    Checked phone

    -

    - -
    -

    - -
    - -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    -
    - - - - - - diff --git a/data/corefork.telegram.org/type/help.DeepLinkInfo b/data/corefork.telegram.org/type/help.CountriesList similarity index 82% rename from data/corefork.telegram.org/type/help.DeepLinkInfo rename to data/corefork.telegram.org/type/help.CountriesList index 2102d2bf51..9ccbe3777e 100644 --- a/data/corefork.telegram.org/type/help.DeepLinkInfo +++ b/data/corefork.telegram.org/type/help.CountriesList @@ -2,12 +2,12 @@ - Help.DeepLinkInfo + help.CountriesList - - + + - + @@ -36,10 +36,10 @@
    -
    -

    Help.DeepLinkInfo

    +
    +

    help.CountriesList

    -

    Contains information about a tg:// deep link

    +

    Name, ISO code, localized name and phone codes/patterns of all available countries

    • @@ -52,12 +52,12 @@
    -
    help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
-help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
+
    help.countriesListNotModified#93cc1f32 = help.CountriesList;
+help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
 
 ---functions---
 
-help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;
    
+help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

    Constructors

    @@ -68,12 +68,12 @@ - - + + - - + +
    help.deepLinkInfoEmptyDeep link info emptyhelp.countriesListNotModifiedThe country list has not changed
    help.deepLinkInfoDeep linking infohelp.countriesListName, ISO code, localized name and phone codes/patterns of all available countries
    @@ -87,8 +87,8 @@ -help.getDeepLinkInfo -Get info about a t.me link +help.getCountriesList +Get name, ISO code, localized name and phone codes/patterns of all available countries
    diff --git a/data/core.telegram.org/type/string.html b/data/corefork.telegram.org/type/long.html similarity index 66% rename from data/core.telegram.org/type/string.html rename to data/corefork.telegram.org/type/long.html index ad86e71f6b..f36446d0dc 100644 --- a/data/core.telegram.org/type/string.html +++ b/data/corefork.telegram.org/type/long.html @@ -2,12 +2,12 @@ - string + long - - + + - + @@ -36,20 +36,12 @@
    -
    -

    string

    +
    +

    long

    -

    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»

    +

    A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

    +

    More 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

    @@ -89,9 +81,9 @@
    -
    Platform
    +
    Platform
    @@ -108,7 +100,7 @@
    Apps
    -
    Platform
    +
    Platform
    Twitter
    diff --git a/data/corefork.telegram.org/type/account.PasswordSettings b/data/corefork.telegram.org/type/messages.AffectedHistory similarity index 74% rename from data/corefork.telegram.org/type/account.PasswordSettings rename to data/corefork.telegram.org/type/messages.AffectedHistory index 16f470b4ab..ff2e529d91 100644 --- a/data/corefork.telegram.org/type/account.PasswordSettings +++ b/data/corefork.telegram.org/type/messages.AffectedHistory @@ -2,12 +2,12 @@ - account.PasswordSettings + messages.AffectedHistory - - + + - + @@ -36,10 +36,10 @@
    -
    -

    account.PasswordSettings

    +
    +

    messages.AffectedHistory

    -

    Private info associated to the password info (recovery email, telegram passport info & so on)

    +

    Object contains info on affected part of communication history with the user or in a chat.

    • @@ -52,11 +52,15 @@
    -
    account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
+
    messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
 
 ---functions---
 
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
    
+messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
+messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
+messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
+
+channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

    Constructors

    @@ -67,8 +71,8 @@ - - + +
    account.passwordSettingsPrivate info associated to the password info (recovery email, telegram passport info & so on)messages.affectedHistoryAffected part of communication history with the user or in a chat.
    @@ -82,13 +86,23 @@ -account.getPasswordSettings -Get private info associated to the password info (recovery email, telegram passport info & so on) +messages.deleteHistory +Deletes communication history. + + +channels.deleteUserHistory +Delete all messages sent by a certain user in a supergroup + + +messages.readMentions +Mark mentions as read + + +messages.unpinAllMessages +Unpin all pinned messages - -

    Related pages

    -

    Telegram Passport Manual

    +
    diff --git a/data/corefork.telegram.org/widgets.html b/data/corefork.telegram.org/widgets.html new file mode 100644 index 0000000000..d39effe6f6 --- /dev/null +++ b/data/corefork.telegram.org/widgets.html @@ -0,0 +1,141 @@ + + + + + Telegram Widgets + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Telegram Widgets

    + +

    Telegram widgets offer a quick way to add a sharing button to your pages, embed posts from public channels or groups. Widgets can also help your users log in with Telegram or view Telegram Discussions on your website.

    +
    +
    +
    + +
    + Sharing button +
    +
    +
    + +
    + Post Widget +
    +
    +
    + +
    + Login Widget +
    +
    +
    + +
    + Discussion Widget +
    +
    +
    +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + diff --git a/data/corefork.telegram.org/widgets/discussion.html b/data/corefork.telegram.org/widgets/discussion.html new file mode 100644 index 0000000000..4a057af876 --- /dev/null +++ b/data/corefork.telegram.org/widgets/discussion.html @@ -0,0 +1,226 @@ + + + + + Discussion Widget + + + + + + + + + + + + + + + +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +

    Discussion Widget

    + +

    You can embed discussions from any public channel on your website. You only need a link to a post with comments to embed it together with all discussion.

    +

    If you have a website with articles and a telegram channel where you post links to these articles, you can use this widget to show discussions from that channel on your website. In this case you only need a link to the channel. Discussions will be available on your website as soon as you post a link into the channel. For this to work, you should add the <link rel="canonical" href="%page_url%"> tag to the page header where %page_url% is the canonical URL of the current page.

    +

    Configure widget

    +

    You can choose options for your widget using the form below.

    +

    +
    + +
    +
    + +
    + +
    +
    +
    + +
    + +
    +
    + +
    +
    +
    + +
    +
    + +
    +
    +
    +
    + +
    + +
    +
    + + + + + + + +
    + + +
    +
    + +
    + +
    + +
    Make sure you have a <link rel="canonical" href="%page_url%"> tag in the page header with the canonical url of the current page.
    +
    +
    + +
    +
    +
    +
    +
    +

    +

    Basic comments

    +

    If you're looking to simply add Telegram comments to pages on your website, without linking them with a channel, you can use our basic comments solution.

    +
    + +
    + +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    +
    + + + + + + + + + + diff --git a/data/telegram.org/android.html b/data/desktop.telegram.org.html similarity index 50% rename from data/telegram.org/android.html rename to data/desktop.telegram.org.html index b3446fa6dc..0c2dd88f8e 100644 --- a/data/telegram.org/android.html +++ b/data/desktop.telegram.org.html @@ -2,20 +2,19 @@ - Telegram for Android + Telegram Desktop - - + + - + - - + @@ -31,9 +30,9 @@ @@ -42,27 +41,24 @@
    -
    +
    -
    +
    - -

    Telegram for Android

    +     +

    Telegram Desktop

     -
    You can download Telegram for your Android device here. This version has fewer restrictions and receives automatic updates directly from telegram.org
    +
    Fast and secure desktop app, perfectly synced with your mobile phone.
    -
    Download Telegram
    +
    Get Telegram for Windows x64Portable version Get Telegram for macOSMac App Store
    +
    +
    Get Telegram for Linux x64
    Flatpak • Snap
     Get Telegram for WindowsPortable version +
    +
    Show all platforms
    -
    -

    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
    -
    +
    +
    This software is available under GPL v3 license.

    Source code is available on GitHub.

    Follow us on Twitter – Beta version
    +
    diff --git a/data/instantview.telegram.org.html b/data/instantview.telegram.org/auth.html similarity index 99% rename from data/instantview.telegram.org.html rename to data/instantview.telegram.org/auth.html index 19f59bc6fa..a7721d2364 100644 --- a/data/instantview.telegram.org.html +++ b/data/instantview.telegram.org/auth.html @@ -205,7 +205,8 @@ - + + + + + + + + + + + + diff --git a/data/instantview.telegram.org/samples.html b/data/instantview.telegram.org/samples.html deleted file mode 100644 index ba272ec2a2..0000000000 --- a/data/instantview.telegram.org/samples.html +++ /dev/null @@ -1,395 +0,0 @@ - - - - - Sample Templates - Instant View - - - - - - - - - - -
    - -
    -
    -
    -
    -
    -
    - -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    -
    - -
    - Login - - Hello, anonymous! - -
    -
    -
    -
    -
    -
    -

    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

    -
    -
     -
    - -
    - -
    Not modified
    -

    - https://medium.com/@_cmdv_/i-want-to-learn-javascript-in-2015-e96cd85ad225 -

    -

    - Want to learn JavaScript ? -

    -
    -     -
    - -
    Not modified
    -

    - https://medium.com/@durov/how-to-hack-telegram-43dc9e6c5ac2 -

    -

    - How to “hack” Telegram -

    -
    -     -
    - -
    Not modified
    -

    - https://medium.com/@ev/welcome-to-medium-9e53ca408c48 -

    -

    - Welcome to Medium -

    -
    -     -
    - -
    Not modified
    -

    - https://medium.com/@ev/writing-in-medium-df8eac9f4a5e -

    -

    - Writing in Medium -

    -
    -     -
    - -
    Not modified
    -

    - https://medium.com/@frisch/math-the-elections-over-can-we-please-move-on-20b2ad1b6088 -

    -

    - Math: The Election’s Over. Can We Please Move On? -

    -
    -     -
    - -
    Not modified
    -

    - https://medium.com/charged-tech/apple-just-told-the-world-it-has-no-idea-who-the-mac-is-for-722a2438389b -

    -

    - Apple just told the world it has no idea who the Mac is for -

    -
    -     -
    - -
    Not modified
    -

    - https://medium.com/matter/the-terrifying-true-story-of-the-garbage-that-could-kill-the-whole-human-race-b17eebd6d54 -

    -

    - The terrifying true story of the garbage that could kill the whole human race -

    -
    -     - -
    -
    -

    - telegra.ph2 -

    -
    -
    -

    2 pages

    -

    Not modified

    -
    -
     -
    - -
    - -
    Not modified
    -

    - https://telegra.ph/Gifs-FAQ -

    -

    - What are GIFs? -

    -
    -     -
    - -
    Not modified
    -

    - https://telegra.ph/api -

    -

    - Telegraph API -

    -
    -     - -
    -
    -

    - telegram.org7 -

    -
    -
    -

    7 pages

    -

    Not modified

    -
    -
     -
    - -
    - -
    Not modified
    -

    - https://telegram.org/blog/android-themes -

    -

    - Custom Themes -

    -
    -     -
    - -
    Not modified
    -

    - https://telegram.org/blog/calls -

    -

    - Voice Calls: Secure, Crystal-Clear, AI-Powered -

    -
    -     -
    - -
    Not modified
    -

    - https://telegram.org/blog/desktop-1-0 -

    -

    - Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL -

    -
    -     -
    - -
    Not modified
    -

    - https://telegram.org/blog/edit -

    -

    - Edit Messages, New Mentions and More -

    -
    -     -
    - -
    Not modified
    -

    - https://telegram.org/blog/instant-view -

    -

    - Instant View, Telegraph, and Other Goodies -

    -
    -     -
    - -
    Not modified
    -

    - https://telegram.org/blog/telegraph -

    -

    - Meet the Telegraph API for Logins and Stats -

    -
    -     -
    - -
    Not modified
    -

    - https://telegram.org/blog/unsend-and-usage -

    -

    - Unsend Messages, Network Usage, and More -

    -
    -     - -
    -
    -
    -
    -
    -
    - - - - - - - - - diff --git a/data/promote.telegram.org/basics.html b/data/promote.telegram.org/basics.html deleted file mode 100644 index 77daa7e61b..0000000000 --- a/data/promote.telegram.org/basics.html +++ /dev/null @@ -1,205 +0,0 @@ - - - - - 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..471bdaf271 --- /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/tos.html b/data/promote.telegram.org/tos.html deleted file mode 100644 index 6bb122c2a2..0000000000 --- a/data/promote.telegram.org/tos.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - 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/api.html b/data/telegram.org.html similarity index 99% rename from data/telegram.org/api.html rename to data/telegram.org.html index 909849ddfc..c8aca89b2d 100644 --- a/data/telegram.org/api.html +++ b/data/telegram.org.html @@ -31,10 +31,10 @@
    diff --git a/data/telegram.org/blog/unsend-and-usage.html b/data/telegram.org/blog/admin-revolution.html similarity index 58% rename from data/telegram.org/blog/unsend-and-usage.html rename to data/telegram.org/blog/admin-revolution.html index b4b9878776..cfb3035f2f 100644 --- a/data/telegram.org/blog/unsend-and-usage.html +++ b/data/telegram.org/blog/admin-revolution.html @@ -2,18 +2,18 @@ - Unsend Messages, Network Usage, and More + Supergroups 10,000: Admin Tools & More - - + + - - + + - + @@ -74,90 +74,78 @@
    -

    Unsend Messages, Network Usage, and More

    +

    Supergroups 10,000: Admin Tools & 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:

    +
    +

    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:

    - -

    Ooops!

    + +

    Search for members

    -

    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.

    +

    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.

    - -

    Works in groups and PM

    + +

    Admin rights

    -

    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.

    +

    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.

    - -

    Data and Storage

    + +

    Recent admin actions

    - -

    Network Usage

    + +

    Precise filters

    -

    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.
      • -
    +

    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.

    - -

    That's the date up there

    + +

    New sharing extension

    -
      -
    • 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

    +

    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

    - Forward - Tweet + Forward + Tweet
    diff --git a/data/telegram.org/blog/backgrounds-2-0.html b/data/telegram.org/blog/animated-stickers.html similarity index 55% rename from data/telegram.org/blog/backgrounds-2-0.html rename to data/telegram.org/blog/animated-stickers.html index d84f3ba709..07eafcd86b 100644 --- a/data/telegram.org/blog/backgrounds-2-0.html +++ b/data/telegram.org/blog/animated-stickers.html @@ -2,18 +2,18 @@ - Chat Backgrounds 2.0: Make Your Own + Animated Stickers Done Right - - + + - - + + - + @@ -74,48 +74,78 @@
    -

    Chat Backgrounds 2.0: Make Your Own

    +

    Animated Stickers Done Right

    - +
    - Telegram 5.3: Introducing the Backgrounds Platform + Cover Image
    -

    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.

    -
    -
    diff --git a/data/telegram.org/blog/apple-watch.html b/data/telegram.org/blog/apple-watch.html deleted file mode 100644 index 1572cb68d5..0000000000 --- a/data/telegram.org/blog/apple-watch.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - Telegram on Apple Watch - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    -     -
    -
    -
    -
    -
    -

    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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - diff --git a/data/telegram.org/blog/cryptocontest.html b/data/telegram.org/blog/cryptocontest.html deleted file mode 100644 index 7ca25a4dad..0000000000 --- a/data/telegram.org/blog/cryptocontest.html +++ /dev/null @@ -1,224 +0,0 @@ - - - - - $300,000 for Cracking Telegram Encryption - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    -     -
    -
    -
    -
    -
    -

    $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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - diff --git a/data/telegram.org/blog/folders.html b/data/telegram.org/blog/folders.html deleted file mode 100644 index be41e8623c..0000000000 --- a/data/telegram.org/blog/folders.html +++ /dev/null @@ -1,298 +0,0 @@ - - - - - Chat Folders, Archive, Channel Stats and More - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - diff --git a/data/telegram.org/blog/unsend-privacy-emoji.html b/data/telegram.org/blog/group-video-calls.html similarity index 58% rename from data/telegram.org/blog/unsend-privacy-emoji.html rename to data/telegram.org/blog/group-video-calls.html index 510f91e58c..a9b82fc3e0 100644 --- a/data/telegram.org/blog/unsend-privacy-emoji.html +++ b/data/telegram.org/blog/group-video-calls.html @@ -2,18 +2,18 @@ - Taking Back Our Right to Privacy + Group Video Calls - - + + - - + + - + @@ -74,78 +74,79 @@
    -

    Taking Back Our Right to Privacy

    +

    Group Video Calls

    - +
    - Unsending messages, anonymized forwarding, improved search and VoiceOver/TalkBack support + Introducing Group Video Calls
    - -

    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.

    -
    -
    - - + + + + + + + diff --git a/data/telegram.org/blog/invite-links.html b/data/telegram.org/blog/invite-links.html deleted file mode 100644 index 3c98d9290e..0000000000 --- a/data/telegram.org/blog/invite-links.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - Migrating Existing Group Chats to Telegram - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    -     -
    -
    -
    -
    -
    -

    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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - diff --git a/data/telegram.org/blog/photo-editor-and-passcodes.html b/data/telegram.org/blog/photo-editor-and-passcodes.html deleted file mode 100644 index bc8ca9a721..0000000000 --- a/data/telegram.org/blog/photo-editor-and-passcodes.html +++ /dev/null @@ -1,252 +0,0 @@ - - - - - Photo Editor and Passcode Lock - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    -     -
    -
    -
    -
    -
    -

    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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + 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 deleted file mode 100644 index 1d2c5e897a..0000000000 --- a/data/telegram.org/blog/profile-videos-people-nearby-and-more.html +++ /dev/null @@ -1,315 +0,0 @@ - - - - - Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - - 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    + +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
    + +
    +

    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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + diff --git a/data/telegram.org/blog/reactions-spoilers-translations.html b/data/telegram.org/blog/reactions-spoilers-translations.html new file mode 100644 index 0000000000..7d17033f44 --- /dev/null +++ b/data/telegram.org/blog/reactions-spoilers-translations.html @@ -0,0 +1,300 @@ + + + + + Reactions, Spoilers, Translation and QR Codes + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    +     +
    +
    +
    +
    +
    +

    Reactions, Spoilers, Translation and QR Codes

    + +
    +
    +
    + +
    + 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.

    +

    Reactions

    +

    Telegram was the first messaging app to add animated and interactive emoji, giving users unparalleled ways to express themselves in chats. Today some of these emoji become available as reactions to share feelings and feedback – without sending any messages.

    +
    + +
    + +

    Double tap a message to send a quick 👍 reaction. For more reactions like 😁 🎉 😱 🔥 👎, tap once on the message (or press and hold, if on iOS). Each reaction appears with its own unique animation.

    +
    +

    You can change your default reaction to another emoji in Settings. Android: Chat Settings > Quick Reaction. iOS: Stickers and Emoji > Quick Reaction.

    +
    +

    Reactions are always on in private chats. In groups and channels, the admins decide whether to turn on reactions and choose which reaction emoji are available in the chat. This enables many different ways to collect feedback – from simple likes ❤️ to upvote 👍 and downvote 👎 systems, and beyond.

    + + +
    +

    Admins can control reactions via their group or channel's Info Page > Edit > Reactions. For more feedback options, try channel comments and our powerful polls.

    +
    +

    Spoilers

    +

    To discuss the fates of Ciri or Peter Parker without spoiling the fun for others, select any part of your text when typing and choose the new 'Spoiler' formatting. This will hide the selected part of the message in the chat, as well as in the chat list and notifications.

    +
    + +
    + +

    When you're ready to see what's hidden, tap the spoiler to reveal its text.

    +

    Message Translation

    +

    Over half a billion people around the world use Telegram not only to stay in touch with friends, but also to chat in public groups and view content from channels – in every language imaginable. Now you can translate any message into another language, right in the app.

    + + +
    + +
    + +

    Enabling Translation in Settings > Language adds a dedicated Translate button to the context menu when selecting a message. You can also exclude any languages you speak fluently – which will hide the translate button for those messages.

    +
    +

    Translation is available on all Android devices that support Telegram, but requires iOS 15+ on Apple devices. The list of available languages depends on your phone's operating system.

    +
    +

    Themed QR Codes

    +

    You can generate QR codes for any users that have a public username. This also works for groups, channels and bots, making it easy to show someone your favorite blog or fan club.

    +
    + +
    + +

    Tap the new QR code icon next to the username of a person (or from a chat’s info page), choose the colors and pattern that fit best, then print, post or share your QR code to other apps.

    +
    +

    A QR code for your own username can be obtained in Settings.

    +
    +

    New Menus for macOS

    +

    We've redesigned all the context menus in Telegram for macOS – adding some new shortcut hints and introducing beautifully animated icons for every single menu item in the app.

    +
    + +
    + +

    More Interactive Emoji

    +

    Our animators also added new interactive versions of 🔥 😁 🤩 😢 😭 😱 ❄️. Send any of them in 1-on-1 chats, then tap to unleash a full-screen effect for you and your partner.

    +
    + +
    + +

    Thank you all for an incredible year. Here's to making 2022 even greater. 🎉

    +

    + +

    December 30, 2021
    The Telegram Team

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
    + +
    +

    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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + diff --git a/data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html b/data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html new file mode 100644 index 0000000000..9799a921f6 --- /dev/null +++ b/data/telegram.org/blog/shared-media-scrolling-calendar-join-requests-and-more.html @@ -0,0 +1,343 @@ + + + + + Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    +     +
    +
    +
    +
    +
    +

    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

    + +
    +
    +
    + +
    + Introducing 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 high-speed scrolling and a calendar view, an admin approval setting for invite links, global chat themes for your entire app, and more.

    +

    Hyper-Speed Scrolling for Shared Media

    +

    Every Telegram user has unlimited cloud storage – and each chat has a Shared Media page that shows all the photos, videos, files and music that have been sent there. We've added a new date bar on the side of the page, which you can drag up and down to scroll through shared media faster.

    +
    + +
    + +

    To get a better look, pinch to zoom in and out, so you can see anywhere from 2 big thumbnails to a dozen small squares per row.

    +

    Calendar View for Shared Media

    +

    To quickly find media from a specific time, tap on the date bar to open a calendar interface with media previews for each day – then tap to see all the media from that date.

    +
    + Calendar view in shared media +
    + +

    In addition to the new tools for jumping between past and present, you can now filter shared media to show only photos, only videos, or both.

    +
    + New menu with filtering options +
    + +
    +

    To view shared media, simply tap the header at the top of your screen in any chat and scroll down. To open the new menu, tap Menu Android on Android or Menu iOS on iOS.

    +
    +

    Join Requests for Groups and Channels

    +

    Invite links let you give users the opportunity to join your group or channel on their own time – whether you share the link privately or turn it into a QR code on a billboard is up to you. When you create additional invite links for your chat, there is now a Request Admin Approval setting, which gives admins more control over who is able to join and see the chat.

    +
    + +
    + +

    When a user opens a link with Admin Approval turned on, they will see a button to send a join request that admins can manage from a new bar at the top of the chat. From there, admins can view an applicant's public profile pictures and bio, then approve or dismiss their request.

    +
    +

    For example, you could post an invite link to your poetry channel on social media – then approve only your close friends and people in purple to see your writing.

    +
    + + +

    Unique Names for Invite Links

    +

    Admin Approval can be applied to any link in the 'Additional Invite Links' section – we've also added the ability to give all of those links unique names, so you can label them for better organization.

    +
    + List of invite links with custom names visible only to admins +
    + +
    +

    Link names will be especially helpful if you're using all the different options that exist for invite links, such as limits on duration, number of uses, etc.

    +
    +

    Global Chat Themes on iOS

    +

    Our last update introduced 8 new themes that you could set for individual chats – and now they're available for your entire app on iOS (with Android soon to follow). Appearance Settings have been fully redesigned, giving these 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 ‘Chat Themes’ to edit and share your creations.

    + + +

    Transit Times for Shared Locations on iOS

    +

    You can show where you are or where you're headed by sending a location from the attachment menu Attach in the message bar. Tapping a shared location pulls up a map of the area – which now shows you the travel time to get there by Foot foot, Car car, or Public Transport public transport. To see detailed directions or get a taxi to the location, tap on the travel time to open it in your preferred app.

    +
    + New transit time buttons on iOS +
    + +
    +

    Transit times are shown for both static and live locations – so you can see how long it will take to meet your friends while they're on the move.

    +
    +

    Instant Media Captions for iOS

    +

    The text you type in the message bar now automatically converts to a caption when you attach media, so you'll never have to retype or cut and paste what you just wrote. This also works with Cloud Drafts – so you can type out the message on your computer, then simply attach the photo from your phone and send it all together.

    +
    + +
    + +
    +

    Naturally, both transit times and instant media captions will be added to our Android app in the coming updates.

    +
    +

    Settings updated for iOS 15

    +

    Settings on iOS have been redesigned to match the style of iOS 15, including streamlined Notifications Notification and Stickers Sticker settings. The Devices Devices section now gives you a clearer overview of your active sessions with new icons – tap any device to see more details or log out from it remotely.

    +
    + +
    + +
    +

    Remember that locations shown for your devices are based exclusively on their IP addresses. This data is not always accurate, so don't be surprised if your laptop suddenly travels to Iceland while you're sleeping.

    +
    +

    More Interactive Emoji

    +

    This update brings new interactive emoji. Send a single 👻 👎 🤮 😂 💸 or 🎃 in any private chat, then tap the emoji to unleash its full-screen effect.

    +
    + +
    + +

    If your chat partner also has the chat open, you will both see the effects and feel the vibrations simultaneously.

    +
    +

    As you know from our previous update, this magic also works with 🎆 🎉 🎈 👍 💩 and ❤️.

    +
    +

    Winter is coming, but our next update is racing to beat it. Stay tuned!

    +

    + +

    November 3, 2021
    The Telegram Team

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
    + +
    +

    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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + diff --git a/data/telegram.org/blog/android-2-0.html b/data/telegram.org/blog/translations-iv2.html similarity index 52% rename from data/telegram.org/blog/android-2-0.html rename to data/telegram.org/blog/translations-iv2.html index 80f5a9fe0c..d61a63107a 100644 --- a/data/telegram.org/blog/android-2-0.html +++ b/data/telegram.org/blog/translations-iv2.html @@ -2,18 +2,18 @@ - Telegram 2.0 for Android: Material Design + Custom Languages, Instant View 2.0 and More - - + + - - + + - + @@ -74,74 +74,93 @@
    -

    Telegram 2.0 for Android: Material Design

    +

    Custom Languages, Instant View 2.0 and More

    - +
    -

    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:

    -
    -
    -
    -
    -
    -
    - -
    +
    +Introducing custom languages, IV 2.0, a new design for Android and more
    + -

    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.

    -
    - - -
    +

    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
    -

    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.

    -
    - +

    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.

    +
    + +
    - -

    -
    + -

    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 »

    +

    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.


    -

    The Telegram Team,
    November 19, 2014

    +

    December 10, 2018
    The Telegram Team

    - Forward - Tweet + Forward + Tweet
    diff --git a/data/telegram.org/blog/verifiable-apps-and-more.html b/data/telegram.org/blog/verifiable-apps-and-more.html deleted file mode 100644 index 277dc0b29d..0000000000 --- a/data/telegram.org/blog/verifiable-apps-and-more.html +++ /dev/null @@ -1,392 +0,0 @@ - - - - - Verifiable Builds, New Theme Editor, Send When Online and So Much More - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed and 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

    -

    - -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed 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

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other News +

    +
    +
    + +
    +

    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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + Recent News +
    + +
    Jan 31
    +
    Video Stickers, Better Reactions and More
    +     +
    Dec 30
    +
    Reactions, Spoilers, Translation and QR Codes
    +     +
    Dec 7
    +
    Protected Content, Delete by Date, Device Management and More
    +     +
    Nov 3
    +
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    +     +
    Sep 19
    +
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    +     +
    Aug 31
    +
    Live Streams, Flexible Forwarding and More
    +     +
    Jul 30
    +
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    +     +
    +
    +
    +
    +
    +

    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

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other 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
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + diff --git a/data/telegram.org/blog/6-years.html b/data/telegram.org/evolution.html similarity index 57% rename from data/telegram.org/blog/6-years.html rename to data/telegram.org/evolution.html index 63918b1cdb..d79af7b532 100644 --- a/data/telegram.org/blog/6-years.html +++ b/data/telegram.org/evolution.html @@ -2,18 +2,18 @@ - Celebrating 6 Years of Telegram + The Evolution of Telegram - - + + - - + + - + @@ -43,72 +43,560 @@
    -
    -
    - Recent News -
    - -
    Jan 31
    -
    Video Stickers, Better Reactions and More
    -     -
    Dec 30
    -
    Reactions, Spoilers, Translation and QR Codes
    -     -
    Dec 7
    -
    Protected Content, Delete by Date, Device Management and More
    -     -
    Nov 3
    -
    Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests and More
    -     -
    Sep 19
    -
    Chat Themes, Interactive Emoji, Read Receipts in Groups
    -     -
    Aug 31
    -
    Live Streams, Flexible Forwarding and More
    -     -
    Jul 30
    -
    Video Calls with up to 1000 Viewers, Video Playback Speed and More
    -     -
    -
    -
    -

    Celebrating 6 Years of Telegram

    +

    The Evolution 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 + 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. (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

    +

    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

    +
    +

    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.

    +

    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.

    - TITLE + Silent Messages, Slow Mode, Admin Titles and More

    On Telegram since August 2019:

    @@ -123,13 +611,13 @@
  • Accent colors for night mode on iOS
  • Comments widget
    • -

    July 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 + Animated Stickers Done Right

    On Telegram since July 2019:

    @@ -138,12 +626,12 @@
  • Open platform for animated stickers
    • -

    June 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 + Location-Based Chats, Adding Contacts Without Phone Numbers and More

    On Telegram since June 2019:

    @@ -158,19 +646,19 @@
  • Change your app icon on iOS
    • -

    May 2019, Second Update

    +

    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 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 + Focused Privacy, Discussion Groups, Seamless Web Bots and More

    On Telegram since May 31, 2019:

    -

    May 2019, First Update

    +

    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 + TITLE

    On Telegram since May 9, 2019:

    @@ -195,12 +683,12 @@
  • Improved passcodes on iOS
  • Message links in groups
    • -

    March 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 + Taking Back Our Right to Privacy

    On Telegram since March 2019:

    @@ -211,13 +699,13 @@
  • Search emoji by keyword
  • VoiceOver and TalkBack support
    • -

    February 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 + Autoplaying Videos, Automatic Downloads and Multiple Accounts

    On Telegram since February 2019

    @@ -228,12 +716,12 @@
  • Multiple account support on iOS (on Android since December '17)
  • Logout alternatives screen
    • -

    January 2019, Second Update

    +

    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 + Chat Backgrounds 2.0: Make Your Own

    On Telegram since January 31, 2019

    @@ -245,44 +733,44 @@
  • Search for new backgrounds
  • Instant View 2.0 contest finished
    • -

    January 2019, First Update

    +

    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.

    +

    The update also added an 'Undo' option after deleting chats or clearing history. It's like a time machine, but with fewer paradoxes.

    - TITLE + Group Permissions, Undo Delete and More

    On Telegram since January 21, 2019

    -

    2018

    +

    2018

    -

    December 2018, Second Update

    +

    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 + Polls: Bringing Choice to Communities

    On Telegram since December 22, 2018

    -

    December 2018, First Update

    +

    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 + Custom Languages, Instant View 2.0 and More

    On Telegram since December 10, 2018

    @@ -294,13 +782,13 @@
  • Zoom videos during playback on Android
  • Instant View 2.0 supports tables, nested lists, RTL languages and more
    • -

    October 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 + Telegram 5.0 for iOS

    On Telegram since October 2018

    @@ -313,11 +801,11 @@
  • TouchBar support for Macbook Pro
  • Local storage for Telegram Desktop
    • -

    August 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 + Telegram dude rides a horse-drawn cart with boxes away from a great safe in the clouds.

    On Telegram since August 2018

    @@ -327,11 +815,11 @@
  • Support for new document types in Telegram Passport
  • Support for names in original language in Telegram Passport
    • -

    July 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 + 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

    @@ -339,12 +827,12 @@
  • Telegram Passport
  • E2E Encryption for ID storage
    • -

    June 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 + 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:

    @@ -355,7 +843,7 @@
  • Share detailed contact information
  • Chat previews, text URLs and cancel sending messages on Android
    • -

    March 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.

    @@ -366,7 +854,7 @@

    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 + 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:

    @@ -376,7 +864,7 @@
  • Auto-night mode on iOS (Android since February '18)
  • Over 200,000,000 users
    • -

    February 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.

    @@ -396,9 +884,9 @@
  • Auto-night mode on Android
  • Login widget for external websites
  • Website bots
    • -
  • Manage connected websites via ‘Active Sessions’
    • +
  • Manage connected websites via 'Active Sessions'
    • -

    January 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.

    @@ -421,11 +909,11 @@
  • TDLib code is available on GitHub
    • -

    2017

    +

    2017

    -

    December 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.

    +

    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 @@ -440,7 +928,7 @@
  • Web embeds for public messages
  • Night theme on iOS (on Android since February '17)
    • -

    November 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.

    @@ -456,7 +944,7 @@
  • Pinned Messages in Channels
  • Select the order of photos
    • -

    October 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.

    @@ -473,9 +961,9 @@
  • Admin Badges
    • -

    August 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.

    +

    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 @@ -491,7 +979,7 @@
  • Forward to multiple people
    • -

    July 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.

    @@ -507,7 +995,7 @@
  • CDN Support
    • -

    June 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.

    @@ -526,7 +1014,7 @@
  • Android Pay
    • -

    May 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.

    @@ -553,7 +1041,7 @@
  • Bot Payments
    • -

    March 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.

    @@ -567,7 +1055,7 @@
  • Compression Slider
    • -

    February 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.

    @@ -596,7 +1084,7 @@
  • GMail Bot
    • -

    January 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.

    @@ -612,9 +1100,9 @@
  • Saved scroll position when re-entering chats
    • -

    2016

    +

    2016

    -

    December 2016, Second Update

    +

    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.

    @@ -627,7 +1115,7 @@
  • @Telegraph bot
    • -

    December 2016, First Update

    +

    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.

    @@ -642,7 +1130,7 @@
  • Forwarding to secret chats
    • -

    November 2016

    +

    November 2016

    Instant View, Telegraph, and Other Goodies

    TITLE @@ -660,7 +1148,7 @@

    This is where wide full-color illustrations for our blog posts end – or begin, depending on which direction you just came from.

    -

    October 2016

    +

    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.

    @@ -674,9 +1162,9 @@
  • Game creator tools
    • -

    September 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.

    +

    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.

    @@ -688,9 +1176,9 @@
  • Trending Stickers tab
    • -

    August 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.

    +

    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.

    @@ -702,7 +1190,7 @@
  • Android camera redesign
    • -

    June 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.

    @@ -717,7 +1205,7 @@
  • Unread message counters
    • -

    May 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.

    @@ -731,7 +1219,7 @@
  • Bots in attachment menu
    • -

    April 2016, Second Update

    +

    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.

    @@ -744,7 +1232,7 @@
  • 3D Touch
    • -

    April 2016, First Update

    +

    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.

    @@ -766,7 +1254,7 @@
  • Inline bots 2.0 with new powers
    • -

    March 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.

    @@ -781,7 +1269,7 @@
  • Public chat groups
    • -

    February 2016, Second Update

    +

    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.

    @@ -794,7 +1282,7 @@
  • Admin signatures in channels
  • Silent messages in channels
    • -

    February 2016, First Update

    +

    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.

    @@ -809,7 +1297,7 @@
  • Secret chats support all cloud chat features
    • -

    January 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.

    @@ -830,9 +1318,9 @@
  • Separate GIF tab
    • -

    2015

    +

    2015

    -

    December 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).

    @@ -846,7 +1334,7 @@
  • Reorder sticker packs
    • -

    November 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.

    @@ -859,7 +1347,7 @@
  • Supergroups for 1,000 members
    • -

    September 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.

    @@ -873,7 +1361,7 @@
  • More tools for iOS photo editor
    • -

    August 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.

    @@ -886,7 +1374,7 @@
  • Recent search results
    • -

    July 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.

    @@ -899,7 +1387,7 @@
  • Chat-specific search
    • -

    June 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.

    @@ -919,7 +1407,7 @@
  • Apple Watch support
    • -

    May 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.

    @@ -933,7 +1421,7 @@
  • Adding and sharing sticker sets
    • -

    April 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.

    @@ -969,7 +1457,7 @@
  • Link previews
    • -

    March 2015, Second Update

    +

    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.

    @@ -982,7 +1470,7 @@
  • Trim videos before sending
    • -

    March 2015, First Update

    +

    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.

    @@ -997,7 +1485,7 @@
  • More stickers
    • -

    February 2015, Second Update

    +

    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.

    @@ -1010,7 +1498,7 @@
  • Local passcode lock for apps
    • -

    February 2015, First Update

    +

    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.

    @@ -1023,7 +1511,7 @@
  • Mute notifications
    • -

    January 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.

    @@ -1035,13 +1523,13 @@
    -

    2014

    +

    2014

    -

    December 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.

    @@ -1060,11 +1548,11 @@
  • GIF and Image Search on Android
    • -

    November 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.

    +

    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.

    @@ -1086,7 +1574,7 @@
  • Android 2.0 with Material Design
    • -

    October 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.

    @@ -1109,7 +1597,7 @@ -->
    -

    September 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.

    @@ -1125,7 +1613,7 @@
  • Cloud search
    • -

    August 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.

    @@ -1136,7 +1624,7 @@
  • Broadcast lists
    • -

    June 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.

    @@ -1150,7 +1638,7 @@
  • Improved notifications
    • -

    March 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.

    @@ -1165,7 +1653,7 @@
  • Message deletion for both sides in Secret Chats
    • -

    February 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.

    @@ -1181,7 +1669,7 @@
  • Windows Phone support
    • -

    January 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.

    @@ -1196,9 +1684,9 @@
  • Send documents on Telegram Desktop
    • -

    2013

    +

    2013

    -

    December 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.

    @@ -1211,7 +1699,7 @@
  • Detailed technical FAQ
    • -

    October 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.

    @@ -1226,58 +1714,16 @@
  • Documented protocol and API
    • -

    August 14, 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

    +
    +

    Armed with this much knowledge about Telegram, you should probably join our Volunteer Support Force.

    +
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other 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
    -
     -
    @@ -1343,10 +1789,10 @@
    - - + + + 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. +
    2. Protecting your personal data from third parties, such as marketers, advertisers, etc.
      3. +
    +

    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. +
    2. 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.
      3. +
    3. Contact your phone provider, so that they block your old SIM and issue a new one with your number.
      4. +
    4. 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.
      5. +
    +
    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. +
    2. 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.
      3. +
    +
    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. +
    2. Check whether contact or group is muted.
      3. +
    3. Make sure Google Play Services are installed on your phone.
      4. +
    4. Check notification priority for Telegram in Android settings, it can be called Importance or Behaviour depending on your device.
      5. +
    5. If your phone uses some battery saving software, make sure that Telegram is whitelisted in that application.
      6. +
    +
    +

    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. +
    2. Check that notifications are ON in phone Settings.
      3. +
    3. Check, whether contact or group is muted.
      4. +
    4. 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.
      5. +
    +

    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. +
    2. Relaunch the app (by terminating it from processes list and launching again).
      3. +
    3. Temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
      4. +
    4. If that didn't help, re-login. Remember that logging out kills your Secret Chats.
      5. +
    +

    iOS:

    +
      +
    1. Force quit the app (double tap home button, then swipe up on Telegram), then relaunch and check if it helped.
      2. +
    2. If that doesn't help, temporarily change the name of the contact in phone contacts (add a few symbols, then change back again).
      3. +
    3. If that doesn’t work, re-login: Settings > Edit > Log Out. Remember that logging out kills all your Secret Chats. Then log in again.
      4. +
    +

    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.

    +

    +
    + +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + diff --git a/data/telegram.org/faq_spam.html b/data/telegram.org/faq_spam.html deleted file mode 100644 index a7ff571d34..0000000000 --- a/data/telegram.org/faq_spam.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - 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.

    -
    - -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - 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.

    +
    + +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + diff --git a/data/telegram.org/js/games.js b/data/telegram.org/js/games.js deleted file mode 100644 index 86d81d5052..0000000000 --- a/data/telegram.org/js/games.js +++ /dev/null @@ -1,206 +0,0 @@ -(function () { - var eventHandlers = {}; - - // Parse init params from location hash: for Android < 5.0, TDesktop - var locationHash = ''; - try { - locationHash = location.hash.toString(); - } catch (e) {} - - var initParams = urlParseHashParams(locationHash); - - var isIframe = false; - try { - isIframe = (window.parent != null && window != window.parent); - } catch (e) {} - - - function urlSafeDecode(urlencoded) { - try { - return decodeURIComponent(urlencoded); - } catch (e) { - return urlencoded; - } - } - - function urlParseHashParams(locationHash) { - locationHash = locationHash.replace(/^#/, ''); - var params = {}; - if (!locationHash.length) { - return params; - } - if (locationHash.indexOf('=') < 0 && locationHash.indexOf('?') < 0) { - params._path = urlSafeDecode(locationHash); - return params; - } - var qIndex = locationHash.indexOf('?'); - if (qIndex >= 0) { - var pathParam = locationHash.substr(0, qIndex); - params._path = urlSafeDecode(pathParam); - locationHash = locationHash.substr(qIndex + 1); - } - var locationHashParams = locationHash.split('&'); - var i, param, paramName, paramValue; - for (i = 0; i < locationHashParams.length; i++) { - param = locationHashParams[i].split('='); - paramName = urlSafeDecode(param[0]); - paramValue = param[1] == null ? null : urlSafeDecode(param[1]); - params[paramName] = paramValue; - } - return params; - } - - // Telegram apps will implement this logic to add service params (e.g. tgShareScoreUrl) to game URL - function urlAppendHashParams(url, addHash) { - // url looks like 'https://game.com/path?query=1#hash' - // addHash looks like 'tgShareScoreUrl=' + encodeURIComponent('tgb://share_game_score?hash=telegram-crawler_long_hash123') - - var ind = url.indexOf('#'); - if (ind < 0) { - // https://game.com/path -> https://game.com/path#tgShareScoreUrl=etc - return url + '#' + addHash; - } - var curHash = url.substr(ind + 1); - if (curHash.indexOf('=') >= 0 || curHash.indexOf('?') >= 0) { - // https://game.com/#hash=1 -> https://game.com/#hash=1&tgShareScoreUrl=etc - // https://game.com/#path?query -> https://game.com/#path?query&tgShareScoreUrl=etc - return url + '&' + addHash; - } - // https://game.com/#hash -> https://game.com/#hash?tgShareScoreUrl=etc - if (curHash.length > 0) { - return url + '?' + addHash; - } - // https://game.com/# -> https://game.com/#tgShareScoreUrl=etc - return url + addHash; - } - - - function postEvent (eventType, callback, eventData) { - if (!callback) { - callback = function () {}; - } - if (eventData === undefined) { - eventData = ''; - } - - if (window.TelegramWebviewProxy !== undefined) { - TelegramWebviewProxy.postEvent(eventType, JSON.stringify(eventData)); - callback(); - } - else if (window.external && 'notify' in window.external) { - window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData})); - callback(); - } - else if (isIframe) { - try { - var trustedTarget = 'https://web.telegram.org'; - // For now we don't restrict target, for testing purposes - trustedTarget = '*'; - window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), trustedTarget); - } catch (e) { - callback(e); - } - } - else { - callback({notAvailable: true}); - } - }; - - function receiveEvent(eventType, eventData) { - var curEventHandlers = eventHandlers[eventType]; - if (curEventHandlers === undefined || - !curEventHandlers.length) { - return; - } - for (var i = 0; i < curEventHandlers.length; i++) { - try { - curEventHandlers[i](eventType, eventData); - } catch (e) {} - } - } - - function onEvent (eventType, callback) { - if (eventHandlers[eventType] === undefined) { - eventHandlers[eventType] = []; - } - var index = eventHandlers[eventType].indexOf(callback); - if (index === -1) { - eventHandlers[eventType].push(callback); - } - }; - - function offEvent (eventType, callback) { - if (eventHandlers[eventType] === undefined) { - return; - } - var index = eventHandlers[eventType].indexOf(callback); - if (index === -1) { - return; - } - eventHandlers[eventType].splice(index, 1); - }; - - function openProtoUrl(url) { - if (!url.match(/^(web\+)?tgb?:\/\/./)) { - return false; - } - var useIframe = navigator.userAgent.match(/iOS|iPhone OS|iPhone|iPod|iPad/i) ? true : false; - if (useIframe) { - var iframeContEl = document.getElementById('tgme_frame_cont') || document.body; - var iframeEl = document.createElement('iframe'); - iframeContEl.appendChild(iframeEl); - var pageHidden = false; - var enableHidden = function () { - pageHidden = true; - }; - window.addEventListener('pagehide', enableHidden, false); - window.addEventListener('blur', enableHidden, false); - if (iframeEl !== null) { - iframeEl.src = url; - } - setTimeout(function() { - if (!pageHidden) { - window.location = url; - } - window.removeEventListener('pagehide', enableHidden, false); - window.removeEventListener('blur', enableHidden, false); - }, 2000); - } - else { - window.location = url; - } - return true; - } - - // For Windows Phone app - window.TelegramGameProxy_receiveEvent = receiveEvent; - - window.TelegramGameProxy = { - initParams: initParams, - receiveEvent: receiveEvent, - onEvent: onEvent, - shareScore: function () { - postEvent('share_score', function (error) { - if (error) { - var shareScoreUrl = initParams.tgShareScoreUrl; - if (shareScoreUrl) { - openProtoUrl(shareScoreUrl); - } - } - }); - }, - paymentFormSubmit: function (formData) { - if (!formData || - !formData.credentials || - formData.credentials.type !== 'card' || - !formData.credentials.token || - !formData.credentials.token.match(/^[A-Za-z0-9\/=_\-]{4,512}$/) || - !formData.title) { - console.error('[TgProxy] Invalid form data submitted', formData); - throw Error('PaymentFormDataInvalid'); - } - postEvent('payment_form_submit', false, formData); - } - }; - -})(); 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.

    +
    + +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + + diff --git a/data/telegram.org/privacy/gmailbot.html b/data/telegram.org/privacy/gmailbot.html new file mode 100644 index 0000000000..1b8ff4270d --- /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.

    +
    + +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + + + 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.

    +
    +
    + +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +

    Telegram News

    +
    +
    + +
    +

    Quizzes

    +
    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…
    +
    +
    Dec 22, 2020
    +
    + +
    +

    Group Chats on Telegram

    +
    Telegram groups are a powerful tool for building communities and each can have up to 200,000 members.
    +
    +
    Jan 29, 2018
    +
    + +
    +

    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…
    +
    +
    Jan 29, 2018
    +
     +
    + +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + 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 + + + + + + + + + + + + + + + + + + + +
    +
    +
    +
    +
    + + +
    +
    +
    +
    +
    +
    +
    +
    + More Features +
    + + +
    Quizzes
    +     + +
    Groups
    +     + +
    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.

    +
    + +
    +
    + Forward + Tweet +
    + +
    +
    +

    + Other News +

    +
    +
    + +
    +

    Quizzes

    +
    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…
    +
    +
    Dec 22, 2020
    +
    + +
    +

    Group Chats on Telegram

    +
    Telegram groups are a powerful tool for building communities and each can have up to 200,000 members.
    +
    +
    Jan 29, 2018
    +
     +
    +
    + +
    +
    +
    +
    +
    +
    +
    Telegram
    +
    + Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. +
    + +
    +
    About
    + +
    +
    +
    Mobile Apps
    + +
    +
    +
    Desktop Apps
    + +
    +
    +
    Platform
    + +
    +
    +
    +
    +
    About
    +
    +
    +
    Blog
    +
    +
    +
    Apps
    +
    +
    +
    Platform
    +
    +
    +
    Twitter
    +
    +
    +
    + + + + + + diff --git a/data/telegram.org/tour/screenshots.html b/data/telegram.org/tour/screenshots.html deleted file mode 100644 index 4029c0ce4f..0000000000 --- a/data/telegram.org/tour/screenshots.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - Telegram Logos and App Screenshots - - - - - - - - - - - - - - - - - - - -
    -
    -
    -
    -
    - - -
    -
    -
    -
    -
    -
    -
    -
    - More Features -
    - - -
    Quizzes
    -     - -
    Groups
    -     - -
    Channels
    -     -
    -
    -
    -
    -
    -

    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

    -
    - -
    -
    - Forward - Tweet -
    - -
    -
    -

    - Other News -

    -
    -
    - -
    -

    Quizzes

    -
    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…
    -
    -
    Dec 22, 2020
    -
    - -
    -

    Group Chats on Telegram

    -
    Telegram groups are a powerful tool for building communities and each can have up to 200,000 members.
    -
    -
    Jan 29, 2018
    -
    - -
    -

    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…
    -
    -
    Jan 29, 2018
    -
     -
    -
    - -
    -
    -
    -
    -
    -
    -
    Telegram
    -
    - Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. -
    - -
    -
    About
    - -
    -
    -
    Mobile Apps
    - -
    -
    -
    Desktop Apps
    - -
    -
    -
    Platform
    - -
    -
    -
    -
    -
    About
    -
    -
    -
    Blog
    -
    -
    -
    Apps
    -
    -
    -
    Platform
    -
    -
    -
    Twitter
    -
    -
    -
    - - - - - - diff --git a/data/tsf.telegram.org/manuals/e2ee.html b/data/themes.telegram.org.html similarity index 64% rename from data/tsf.telegram.org/manuals/e2ee.html rename to data/themes.telegram.org.html index ad36876041..37f3420801 100644 --- a/data/tsf.telegram.org/manuals/e2ee.html +++ b/data/themes.telegram.org.html @@ -2,10 +2,12 @@ - Telegram Support Force - - - + Telegram Themes + + + + + @@ -14,72 +16,34 @@ - + - - -
    -
    -
    -
    -
    - -
    +
    + 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.

    +
    -
    -
    - -
    -
    -
    -

    A Detailed Guide to End-to-End Encryption

    - -

    Alas, this magnificent work is not finished yet. Come back later. Yes.

    -
    - -
    -
    -
    -