From f96d8ca577cf2ea2c50546c5ab19406bfae4c3bd Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Thu, 23 Nov 2023 19:16:45 +0000 Subject: [PATCH] Update content of files --- data/web/corefork.telegram.org.html | 10 +- data/web/corefork.telegram.org/api.html | 10 +- data/web/corefork.telegram.org/api/boost.html | 2 +- .../api/bots/attach.html | 4 +- .../api/bots/inline.html | 2 +- .../corefork.telegram.org/api/bots/menu.html | 8 +- .../api/bots/webapps.html | 4 +- .../web/corefork.telegram.org/api/config.html | 4 +- .../api/end-to-end/seq_no.html | 22 +- .../web/corefork.telegram.org/api/layers.html | 67 ++- data/web/corefork.telegram.org/api/links.html | 22 +- .../web/corefork.telegram.org/api/nearby.html | 8 +- .../corefork.telegram.org/api/payments.html | 2 +- data/web/corefork.telegram.org/api/poll.html | 6 +- .../corefork.telegram.org/api/stories.html | 14 +- .../corefork.telegram.org/api/web-events.html | 54 +-- .../constructor/appWebViewResultUrl.html | 6 +- .../constructor/attachMenuBot.html | 6 +- .../constructor/attachMenuBotIcon.html | 8 +- .../constructor/attachMenuBotIconColor.html | 6 +- .../constructor/attachMenuBots.html | 8 +- .../constructor/attachMenuBotsBot.html | 8 +- .../attachMenuBotsNotModified.html | 6 +- .../constructor/botApp.html | 22 +- .../constructor/chatAdminRights.html | 6 +- .../constructor/inlineBotWebView.html | 6 +- .../constructor/inputBotAppID.html | 10 +- .../constructor/inputBotAppShortName.html | 10 +- .../keyboardButtonSimpleWebView.html | 10 +- .../constructor/keyboardButtonWebView.html | 10 +- .../constructor/messageActionBotAllowed.html | 6 +- .../messageActionWebViewDataSent.html | 8 +- .../messageActionWebViewDataSentMe.html | 8 +- .../constructor/messages.botApp.html | 8 +- .../constructor/messages.botResults.html | 2 +- .../constructor/stories.stories.html | 2 +- .../constructor/updateAttachMenuBots.html | 2 +- .../constructor/updateNewAuthorization.html | 4 +- .../method/account.initTakeoutSession.html | 2 +- .../method/channels.createChannel.html | 7 +- .../method/channels.editForumTopic.html | 5 + .../method/channels.editLocation.html | 7 +- .../method/contacts.setBlocked.html | 4 +- .../method/messages.getAttachMenuBot.html | 6 +- .../method/messages.getAttachMenuBots.html | 6 +- .../method/messages.getBotApp.html | 8 +- .../method/messages.migrateChat.html | 5 + .../method/messages.prolongWebView.html | 6 +- .../method/messages.requestAppWebView.html | 14 +- .../method/messages.requestSimpleWebView.html | 8 +- .../method/messages.requestWebView.html | 6 +- .../method/messages.sendInlineBotResult.html | 5 + .../method/messages.sendMessage.html | 10 + .../messages.sendScreenshotNotification.html | 5 + .../method/messages.sendWebViewData.html | 8 +- .../messages.sendWebViewResultMessage.html | 2 +- .../method/messages.setInlineBotResults.html | 2 +- .../messages.toggleBotInAttachMenu.html | 2 +- .../method/stories.applyBoost.html | 2 +- .../method/stories.canApplyBoost.html | 6 +- .../method/stories.canSendStory.html | 6 +- .../method/stories.getPeerStories.html | 5 + .../method/stories.getPinnedStories.html | 2 +- .../method/stories.getStoriesArchive.html | 7 +- .../method/stories.getStoriesViews.html | 10 + .../method/stories.incrementStoryViews.html | 5 + .../method/upload.reuploadCdnFile.html | 10 + data/web/corefork.telegram.org/methods.html | 24 +- .../mtproto/samples-auth_key.html | 412 +++++++++--------- .../type/AppWebViewResult.html | 10 +- .../type/AttachMenuBot.html | 8 +- .../type/AttachMenuBotIcon.html | 8 +- .../type/AttachMenuBotIconColor.html | 8 +- .../type/AttachMenuBots.html | 12 +- .../type/AttachMenuBotsBot.html | 10 +- .../type/AttachMenuPeerType.html | 6 +- data/web/corefork.telegram.org/type/Bool.html | 2 +- .../corefork.telegram.org/type/BotApp.html | 8 +- .../type/InlineBotWebView.html | 8 +- .../type/InputBotApp.html | 10 +- .../type/KeyboardButton.html | 4 +- .../type/MessageAction.html | 4 +- .../type/SimpleWebViewResult.html | 2 +- .../corefork.telegram.org/type/Update.html | 2 +- .../corefork.telegram.org/type/Updates.html | 2 +- .../type/WebViewResult.html | 2 +- .../type/messages.BotApp.html | 10 +- .../type/stories.Stories.html | 8 +- 88 files changed, 600 insertions(+), 532 deletions(-) diff --git a/data/web/corefork.telegram.org.html b/data/web/corefork.telegram.org.html index 74185f53a7..c2c078361a 100644 --- a/data/web/corefork.telegram.org.html +++ b/data/web/corefork.telegram.org.html @@ -136,15 +136,15 @@

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.

-

Web apps

-

Bots can offer users interactive HTML5 web apps to completely replace any website.

+

Mini apps

+

Bots can offer users interactive HTML5 mini apps to completely replace any website.

Attachment menu

-

Bots can install attachment menu entries, offering conveniently accessible, versatile web apps.

+

Bots can install attachment menu entries, offering conveniently accessible, versatile mini apps.

Stories

Telegram users and channels can easily post and view stories through the API.

Privacy settings

Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.

-

Search & filters

+

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

@@ -221,7 +221,7 @@ This allows the server to filter messages based on a text query, and even on the

Working with contacts in the API.

Blocklist

Working with the blocklist.

-

Nearby users&chats

+

Nearby users&chats

How to work with geolocation-based features like geochats and the nearby users feature.

Web events

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

diff --git a/data/web/corefork.telegram.org/api.html b/data/web/corefork.telegram.org/api.html index 74185f53a7..c2c078361a 100644 --- a/data/web/corefork.telegram.org/api.html +++ b/data/web/corefork.telegram.org/api.html @@ -136,15 +136,15 @@

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.

-

Web apps

-

Bots can offer users interactive HTML5 web apps to completely replace any website.

+

Mini apps

+

Bots can offer users interactive HTML5 mini apps to completely replace any website.

Attachment menu

-

Bots can install attachment menu entries, offering conveniently accessible, versatile web apps.

+

Bots can install attachment menu entries, offering conveniently accessible, versatile mini apps.

Stories

Telegram users and channels can easily post and view stories through the API.

Privacy settings

Telegram allows users to specify granular privacy settings, choosing which users can or can't interact with them in certain ways.

-

Search & filters

+

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

@@ -221,7 +221,7 @@ This allows the server to filter messages based on a text query, and even on the

Working with contacts in the API.

Blocklist

Working with the blocklist.

-

Nearby users&chats

+

Nearby users&chats

How to work with geolocation-based features like geochats and the nearby users feature.

Web events

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

diff --git a/data/web/corefork.telegram.org/api/boost.html b/data/web/corefork.telegram.org/api/boost.html index ced1e41dd2..de56939552 100644 --- a/data/web/corefork.telegram.org/api/boost.html +++ b/data/web/corefork.telegram.org/api/boost.html @@ -86,7 +86,7 @@ A BOOST_NOT_MODIFIED RPC error will be returned when calling any of ---functions--- stories.getChatsToSend#a56a8b60 = messages.Chats; -

Everything works exactly the same as when posting stories as a user, with the only difference that clients should pass the appropriate inputPeerChannel instead of inputPeerSelf to stories.canSendStory, stories.sendStory and all the other story methods, see the main documentation » for more info.

+

Everything works exactly the same as when posting stories as a user, with the only difference that clients should pass the appropriate inputPeerChannel instead of inputPeerSelf to stories.canSendStory, stories.sendStory and all the other story methods, see the main documentation » for more info.

Use stories.getChatsToSend to obtain a list of channels where the user can post stories; stories.canSendStory must still be used before uploading a story to make sure no other limit was reached, as described in the main documentation ».

diff --git a/data/web/corefork.telegram.org/api/bots/attach.html b/data/web/corefork.telegram.org/api/bots/attach.html index 28bd602d77..e659acc482 100644 --- a/data/web/corefork.telegram.org/api/bots/attach.html +++ b/data/web/corefork.telegram.org/api/bots/attach.html @@ -44,7 +44,7 @@
-

Bots can install attachment menu entries, offering conveniently accessible, versatile web apps.

+

Bots can install attachment menu entries, offering conveniently accessible, versatile web apps.

Schema:

user#abb5f120 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 bot_attach_menu:flags.27?true premium:flags.28?true attach_menu_enabled:flags.29?true flags2:# bot_can_edit:flags2.1?true close_friend:flags2.2?true stories_hidden:flags2.3?true stories_unavailable:flags2.4?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 emoji_status:flags.30?EmojiStatus usernames:flags2.0?Vector<Username> stories_max_id:flags2.5?int = User;
 
@@ -83,7 +83,7 @@
 Changes made using this method will trigger an updateAttachMenuBots update in other clients, which should trigger a messages.getAttachMenuBots call to fetch the full updated list of installed attachment menu entries.

 The attachment menu list should also be refreshed if the user changes the app's language in the settings.  

 
Once an attachment menu is enabled for a certain user, the user.attach_menu_enabled flag will be set for the bot, and the attachMenuBot.inactive flag will be unset.  

-
Clicking on the attachment menu entry should open the related bot web app, see here » for more info on the required steps.

+
Clicking on the attachment menu entry should open the related bot mini app, see here » for more info on the required steps.

 
Attachment menus can be installed and opened through attachment menu deep links.
diff --git a/data/web/corefork.telegram.org/api/bots/inline.html b/data/web/corefork.telegram.org/api/bots/inline.html index 634e8990fe..6539929130 100644 --- a/data/web/corefork.telegram.org/api/bots/inline.html +++ b/data/web/corefork.telegram.org/api/bots/inline.html @@ -104,7 +104,7 @@ Just like its bot API counterpart, the messages.sendInlineBotResult#f7bc68ba flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to:flags.0?InputReplyTo random_id:long query_id:long id:string schedule_date:flags.10?int send_as:flags.13?InputPeer = Updates;

The user client should display the messages.botResults.results obtained during querying in a list, making sure to handle eventual bot timeouts in the form of a BOT_RESPONSE_TIMEOUT RPC error, by simply not displaying anything.

-

If either the messages.botResults.switch_pm or messages.botResults.switch_webview flags are populated, a button should be displayed on top of the result list, that when clicked, instead of sending an inline result to the chat, switches the user to a private chat with the bot (switch_pm) or to a bot web app (switch_webview).

+

If either the messages.botResults.switch_pm or messages.botResults.switch_webview flags are populated, a button should be displayed on top of the result list, that when clicked, instead of sending an inline result to the chat, switches the user to a private chat with the bot (switch_pm) or to a bot mini app (switch_webview).

If the user instead chooses a specific BotInlineResult from the normal results list, the messages.sendInlineBotResult method should be invoked, passing: