diff --git a/data/corefork.telegram.org/api/import.html b/data/corefork.telegram.org/api/import.html new file mode 100644 index 0000000000..bdd6c945b5 --- /dev/null +++ b/data/corefork.telegram.org/api/import.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/api/layers.html b/data/corefork.telegram.org/api/layers.html index abe78e3006..0bb1de0b54 100644 --- a/data/corefork.telegram.org/api/layers.html +++ b/data/corefork.telegram.org/api/layers.html @@ -855,10 +855,10 @@ Layer…">
Changed Methods
@@ -1662,7 +1662,7 @@ Notice that all PINNED_* baseThemeNight - Night theme
  • Added baseThemeTinted - Tinted theme
  • Added baseThemeArctic - Arctic theme
    • -
  • Added inputWallPaperNoFile - Wallpaper with no file
    • +
  • Added inputWallPaperNoFile - Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
  • Added wallPaperNoFile - No file wallpaper
  • Added inputThemeSettings - Theme settings
  • Added themeSettings - Theme settings
    • diff --git a/data/corefork.telegram.org/constructor/inputThemeSettings.html b/data/corefork.telegram.org/constructor/inputThemeSettings.html index 392e96fc30..afcfcd8130 100644 --- a/data/corefork.telegram.org/constructor/inputThemeSettings.html +++ b/data/corefork.telegram.org/constructor/inputThemeSettings.html @@ -71,7 +71,7 @@ message_colors_animated flags.2?true -  +If set, the freeform gradient fill needs to be animated on every sent message base_theme @@ -81,17 +81,17 @@ accent_color int -Accent color, RGB24 format +Accent color, ARGB format outbox_accent_color flags.3?int -  +Accent color of outgoing messages in ARGB format message_colors flags.0?Vector<int> -  +The fill to be used as a background for outgoing messages, in RGB24 format. \
    If just one or two equal colors are provided, describes a solid fill of a background. \
    If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.\
    If three or four colors are provided, describes a freeform gradient fill of a background. wallpaper diff --git a/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html b/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html index 95a64c2407..d4adbf686d 100644 --- a/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html +++ b/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html @@ -4,10 +4,10 @@ inputWallPaperNoFile - + - + @@ -39,7 +39,7 @@

    inputWallPaperNoFile

    -

    Wallpaper with no file

    +

    Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.

    +

    InputWallPaper

    +

    Related pages

    +

    account.saveWallPaper

    +

    Install/uninstall wallpaper

    diff --git a/data/corefork.telegram.org/constructor/messages.historyImportParsed b/data/corefork.telegram.org/constructor/messages.historyImportParsed index e6652b0f86..d512bfddb0 100644 --- a/data/corefork.telegram.org/constructor/messages.historyImportParsed +++ b/data/corefork.telegram.org/constructor/messages.historyImportParsed @@ -4,36 +4,10 @@ messages.historyImportParsed - + - + @@ -65,7 +39,9 @@ title…">

    messages.historyImportParsed

    -

    +

    Contains information about a chat export file, generated by a foreign chat app.
    +If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

    +

    • Layer 133 @@ -96,17 +72,17 @@ title…"> pm flags.0?true -  +The chat export file was generated from a private chat. group flags.1?true -  +The chat export file was generated from a group chat. title flags.2?string -  +Title of the chat. diff --git a/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html b/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html index e24405f875..5c54da164c 100644 --- a/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html +++ b/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html @@ -81,7 +81,7 @@ placeholder flags.3?string -  +The placeholder to be shown in the input field when the keyboard is active; 1-64 characters. diff --git a/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html b/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html index b79e1b4bce..3ac5d68ddd 100644 --- a/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html +++ b/data/corefork.telegram.org/constructor/replyKeyboardMarkup.html @@ -91,7 +91,7 @@ placeholder flags.3?string -  +The placeholder to be shown in the input field when the keyboard is active; 1-64 characters. diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html index bb2d0fc0fb..acd366b5bc 100644 --- a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html +++ b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html @@ -4,38 +4,10 @@ sendMessageEmojiInteraction - + - + @@ -67,7 +39,8 @@ SendMessageAction">

      sendMessageEmojiInteraction

      -

      +

      User has clicked on an animated emoji, triggering a reaction

      +

      • Layer 133 @@ -93,12 +66,12 @@ SendMessageAction"> emoticon string -  +Emoji msg_id int -  +Message ID of the animated emoji that was clicked interaction diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html index 9c7c4ad852..34e30a227e 100644 --- a/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html +++ b/data/corefork.telegram.org/constructor/sendMessageEmojiInteractionSeen.html @@ -4,26 +4,10 @@ sendMessageEmojiInteractionSeen - + - + @@ -55,7 +39,8 @@ SendMessageAction">

        sendMessageEmojiInteractionSeen

        -

        +

        User is watching an animated emoji reaction triggered by another user

        +

        • Layer 133 @@ -81,7 +66,7 @@ SendMessageAction"> emoticon string -  +Emoji diff --git a/data/corefork.telegram.org/constructor/themeSettings.html b/data/corefork.telegram.org/constructor/themeSettings.html index 4288465446..9646dd36dd 100644 --- a/data/corefork.telegram.org/constructor/themeSettings.html +++ b/data/corefork.telegram.org/constructor/themeSettings.html @@ -71,7 +71,7 @@ message_colors_animated flags.2?true -  +If set, the freeform gradient fill needs to be animated on every sent message. base_theme @@ -81,17 +81,17 @@ accent_color int -Accent color, RGB24 format +Accent color, ARGB format outbox_accent_color flags.3?int -  +Accent color of outgoing messages in ARGB format message_colors flags.0?Vector<int> -  +The fill to be used as a background for outgoing messages, in RGB24 format. \
          If just one or two equal colors are provided, describes a solid fill of a background. \
          If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.\
          If three or four colors are provided, describes a freeform gradient fill of a background. wallpaper diff --git a/data/corefork.telegram.org/method/messages.checkHistoryImport b/data/corefork.telegram.org/method/messages.checkHistoryImport index e714fb383d..c4c8120e24 100644 --- a/data/corefork.telegram.org/method/messages.checkHistoryImport +++ b/data/corefork.telegram.org/method/messages.checkHistoryImport @@ -4,26 +4,10 @@ messages.checkHistoryImport - + - + @@ -55,7 +39,8 @@ messages.HistoryImportParsed">

          messages.checkHistoryImport

          -

          +

          Obtains information about a chat export file, generated by a foreign chat app.

          +

          • Layer 133 @@ -83,7 +68,7 @@ messages.HistoryImportParsed"> import_head string -  +Beginning of the message file; up to 100 lines. diff --git a/data/corefork.telegram.org/method/messages.initHistoryImport b/data/corefork.telegram.org/method/messages.initHistoryImport index 82fdc00ce4..47aeb22600 100644 --- a/data/corefork.telegram.org/method/messages.initHistoryImport +++ b/data/corefork.telegram.org/method/messages.initHistoryImport @@ -4,40 +4,10 @@ messages.initHistoryImport - + - + @@ -69,7 +39,11 @@ Bots…">

            messages.initHistoryImport

            -

            +

            Import chat history from a foreign chat app into a specific Telegram chat.
            +Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
            +Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

            +

            After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.

            +

            +

            Bots can use this method

            +

            Related pages

            +

            messages.uploadImportedMedia

            +

            Upload a media file associated with an imported chat.

            +

            messages.checkHistoryImportPeer

            +

            Check whether chat history exported from another chat app can be imported into a specific Telegram chat.

            +

            If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.

            +

            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.

            +

            messages.startHistoryImport

            +

            Complete the history import process, importing all messages into the chat.
            +To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.

            diff --git a/data/corefork.telegram.org/method/messages.startHistoryImport b/data/corefork.telegram.org/method/messages.startHistoryImport index c119a841af..e6782a6158 100644 --- a/data/corefork.telegram.org/method/messages.startHistoryImport +++ b/data/corefork.telegram.org/method/messages.startHistoryImport @@ -4,34 +4,10 @@ messages.startHistoryImport - + - + @@ -63,7 +39,9 @@ Bots can use this method">

            messages.startHistoryImport

            -

            +

            Complete the history import process, importing all messages into the chat.
            +To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.

            +

            • Layer 133 @@ -92,18 +70,26 @@ Bots can use this method"> peer InputPeer -  +The Telegram chat where the messages should be imported import_id long -  +Identifier of a history import session, returned by messages.initHistoryImport.

              Result

              Bool

              -

              Bots can use this method

            +

            Bots can use this method

            +

            Related pages

            +

            messages.initHistoryImport

            +

            Import chat history from a foreign chat app into a specific Telegram chat.
            +Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
            +Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

            +

            After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.

            +

            messages.uploadImportedMedia

            +

            Upload a media file associated with an imported chat.

            diff --git a/data/corefork.telegram.org/method/messages.uploadImportedMedia b/data/corefork.telegram.org/method/messages.uploadImportedMedia index 8f233152f1..192c7a15cd 100644 --- a/data/corefork.telegram.org/method/messages.uploadImportedMedia +++ b/data/corefork.telegram.org/method/messages.uploadImportedMedia @@ -4,44 +4,10 @@ messages.uploadImportedMedia - + - + @@ -73,7 +39,8 @@ MessageMedia…">

            messages.uploadImportedMedia

            -

            +

            Upload a media file associated with an imported chat.

            +

            +

            Bots can use this method

            +

            Related pages

            +

            messages.initHistoryImport

            +

            Import chat history from a foreign chat app into a specific Telegram chat.
            +Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
            +Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

            +

            After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.

            diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html index 3d15004347..f9adbc61f0 100644 --- a/data/corefork.telegram.org/methods.html +++ b/data/corefork.telegram.org/methods.html @@ -1497,11 +1497,11 @@ messages.uploadImportedMedia -  +Upload a media file associated with an imported chat. messages.startHistoryImport -  +Complete the history import process, importing all messages into the chat.
            To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia. messages.checkHistoryImportPeer @@ -1509,11 +1509,11 @@ messages.checkHistoryImport -  +Obtains information about a chat export file, generated by a foreign chat app. messages.initHistoryImport -  +Import chat history from a foreign chat app into a specific Telegram chat.
            Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
            Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

            After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat. diff --git a/data/corefork.telegram.org/type/Bool.html b/data/corefork.telegram.org/type/Bool.html index 6fb7d4ce13..dbb61287d7 100644 --- a/data/corefork.telegram.org/type/Bool.html +++ b/data/corefork.telegram.org/type/Bool.html @@ -603,7 +603,7 @@ messages.startHistoryImport -  +Complete the history import process, importing all messages into the chat.
            To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia. messages.deleteRevokedExportedChatInvites diff --git a/data/corefork.telegram.org/type/MessageMedia.html b/data/corefork.telegram.org/type/MessageMedia.html index 0520aa685e..0f8eed3aa9 100644 --- a/data/corefork.telegram.org/type/MessageMedia.html +++ b/data/corefork.telegram.org/type/MessageMedia.html @@ -153,7 +153,7 @@ messages.uploadImportedMedia -  +Upload a media file associated with an imported chat.
            diff --git a/data/corefork.telegram.org/type/SendMessageAction.html b/data/corefork.telegram.org/type/SendMessageAction.html index 39f446c82c..e016813bcf 100644 --- a/data/corefork.telegram.org/type/SendMessageAction.html +++ b/data/corefork.telegram.org/type/SendMessageAction.html @@ -145,11 +145,11 @@ sendMessageEmojiInteraction -  +User has clicked on an animated emoji, triggering a reaction sendMessageEmojiInteractionSeen -  +User has seen the reaction generated by another user
            diff --git a/data/corefork.telegram.org/type/messages.HistoryImport b/data/corefork.telegram.org/type/messages.HistoryImport index a18652350b..62d25f46d6 100644 --- a/data/corefork.telegram.org/type/messages.HistoryImport +++ b/data/corefork.telegram.org/type/messages.HistoryImport @@ -83,7 +83,7 @@ messages.initHistoryImport -  +Import chat history from a foreign chat app into a specific Telegram chat.
            Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
            Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

            After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
            diff --git a/data/corefork.telegram.org/type/messages.HistoryImportParsed b/data/corefork.telegram.org/type/messages.HistoryImportParsed index 46f36ca2fd..dc807d0713 100644 --- a/data/corefork.telegram.org/type/messages.HistoryImportParsed +++ b/data/corefork.telegram.org/type/messages.HistoryImportParsed @@ -4,10 +4,10 @@ messages.HistoryImportParsed - + - + @@ -39,7 +39,7 @@

            messages.HistoryImportParsed

            -

            Info about an imported chat

            +

            Contains information about a chat export file, generated by a foreign chat app.

            • @@ -68,7 +68,7 @@ messages.historyImportParsed -  +Contains information about a chat export file, generated by a foreign chat app. If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type. @@ -83,7 +83,7 @@ messages.checkHistoryImport -  +Obtains information about a chat export file, generated by a foreign chat app.