From 439019a81c3a18c5a7de6c3e84578b17ce91a177 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sat, 15 Apr 2023 14:32:50 +0000 Subject: [PATCH] Update content of files --- .../web/corefork.telegram.org/api/layers.html | 16 +-- .../messageActionAttachMenuBotAllowed.html | 118 ------------------ 2 files changed, 8 insertions(+), 126 deletions(-) delete mode 100644 data/web/corefork.telegram.org/constructor/messageActionAttachMenuBotAllowed.html diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html index 5d803101af..a57124062c 100644 --- a/data/web/corefork.telegram.org/api/layers.html +++ b/data/web/corefork.telegram.org/api/layers.html @@ -59,7 +59,7 @@ Web apps can now be opened by clicking on a switch_webview inline result, similar to switch_pm inline results.
Bots can now edit their own about text and description.
Also, the future auth token is now directly returned in the config constructor, which was also cleaned up to remove redundant information already contained in the appConfig configuration.
-messages.getMessageReadParticipants now returns a timestamp for each user, indicating when that user has read the specified message.

+messages.getMessageReadParticipants now returns a timestamp for each user, indicating when that user has read the specified message.

Additionally, when using messages.addChatUser, channels.inviteToChannel or messages.createChat, 0-N updates of type updateGroupInvitePrivacyForbidden may be returned, indicating that the server couldn't add a user to a chat because of their privacy settings; if required, an invite link can be shared with the user, instead.

Finally, sponsored messages can now contain detailed info about the sponsor of the message or the message itself.

Schema changes

@@ -95,10 +95,6 @@ Also, the future auth token is now di
  • Added flags, attach_menu, app parameters, changed type of domain from string to flags.0?string in messageActionBotAllowed
  • Added sponsor_info, additional_info parameters in sponsoredMessage
    • -
    Deleted Constructors
    -

    Schema

    config#cc1a241e flags:# default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true force_try_ipv6:flags.14?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 edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int channels_read_media_period:int tmp_sessions:flags.0?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 reactions_default:flags.15?Reaction autologin_token:flags.16?string = Config;
    
 messages.botResults#e021f2f6 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM switch_webview:flags.3?InlineBotWebView results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
@@ -156,6 +152,12 @@ Also, the future auth token is now di
 stickers.renameStickerSet#124b1c00 stickerset:InputStickerSet title:string = messages.StickerSet;
 stickers.deleteStickerSet#87704394 stickerset:InputStickerSet = Bool;

    Layer 152

    +

    Users can now set stickers or custom emojis as profile or group/channel pictures », and Telegram Premium users can enable real-time chat translation », which allows seamless translation of chat messages, keeping style entities intact.
    +Bots can now prompt the user to select and share a peer with the bot with messages.sendBotRequestedPeer, by using a keyboardButtonRequestPeer bot button.
    +Added support for categorized custom emojis », and a messages.searchCustomEmoji method to look up custom emojis by their corresponding UTF8 emoji.
    +Also implemented synchronization of media autosave settings.

    +

    Most importantly, added support for Safetynet/Firebase SMS authentication, which is now mandatory when requesting SMS codes to log in or sign up to Telegram.
    +Currently, only official apps can make use of Safetynet/Firebase SMS authentication: this means that only the official applications can be used to sign up to Telegram, or receive the login code via SMS/call. Third-party apps may log in using any of the other code delivery methods (Telegram codes, Fragment codes, email codes, future auth tokens).

    Schema changes

    New Methods