From df39c2ac458b980a8625af1cb7e52d317bd36387 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 17 Jul 2024 17:26:01 +0000 Subject: [PATCH] Update content of files --- .../corefork.telegram.org/api/factcheck.html | 142 ++++++ .../corefork.telegram.org/api/privacy.html | 12 +- .../constructor/updateSmsJob.html | 15 +- .../constructor/updateStarsBalance.html | 21 +- .../users.getIsPremiumRequiredToContact.html | 10 +- .../mtproto/samples-auth_key.html | 412 +++++++++--------- 6 files changed, 382 insertions(+), 230 deletions(-) create mode 100644 data/web/corefork.telegram.org/api/factcheck.html diff --git a/data/web/corefork.telegram.org/api/factcheck.html b/data/web/corefork.telegram.org/api/factcheck.html new file mode 100644 index 0000000000..1d92753fe3 --- /dev/null +++ b/data/web/corefork.telegram.org/api/factcheck.html @@ -0,0 +1,142 @@ + + + + + Fact-checks + + + + + + + + + + + + + + + + +
+ +
+
+
+ +

Fact-checks

+ +
+ +

Telegram clients support displaying fact-checks added to messages by independent fact-checkers.

+

Displaying fact-checks

+
factCheck#b89bfccf flags:# need_check:flags.0?true country:flags.1?string text:flags.1?TextWithEntities hash:long = FactCheck;
+
+message#94345242 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 invert_media:flags.27?true flags2:# offline:flags2.1?true id:int from_id:flags.8?Peer from_boosts_applied:flags.29?int peer_id:Peer saved_peer_id:flags.28?Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long via_business_bot_id:flags2.0?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long reactions:flags.20?MessageReactions restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int quick_reply_shortcut_id:flags.30?int effect:flags2.2?long factcheck:flags2.3?FactCheck = Message;
+
+---functions---
+
+messages.getFactCheck#b9cdc5ee peer:InputPeer msg_id:Vector<int> = Vector<FactCheck>;
+

Fact-checks are represented by factCheck constructors, optionally contained in the factcheck field of the message constructor.

+

Editing fact-checks

+
factCheck#b89bfccf flags:# need_check:flags.0?true country:flags.1?string text:flags.1?TextWithEntities hash:long = FactCheck;
+
+---functions---
+
+messages.editFactCheck#0589ee75 peer:InputPeer msg_id:int text:TextWithEntities = Updates;
+messages.deleteFactCheck#d1da940c peer:InputPeer msg_id:int = Updates;
+

Fact-checks may be created, deleted and edited by independent fact-checkers using messages.editFactCheck and messages.deleteFactCheck.

+

Those methods can be used by independent fact-checkers, which will have the appConfig.can_edit_factcheck configuration flag set to true.

+

If the flag mentioned above is set to true, the maximum UTF-8 length for a fact check will be specified in the appConfig.factcheck_length_limit field.

+ +
+ +
+
+ +
+ + + + + + + + diff --git a/data/web/corefork.telegram.org/api/privacy.html b/data/web/corefork.telegram.org/api/privacy.html index 55e78f7580..df4f9ea6c3 100644 --- a/data/web/corefork.telegram.org/api/privacy.html +++ b/data/web/corefork.telegram.org/api/privacy.html @@ -123,7 +123,17 @@ account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings; account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

Some global privacy settings can also be fetched and modified using account.getGlobalPrivacySettings and account.setGlobalPrivacySettings.

-

Global privacy settings are represented by the globalPrivacySettings constructor, please see the constructor page for a full description of all settings.

+

Global privacy settings are represented by the globalPrivacySettings constructor, please see the constructor page for a full description of all settings.

+

Require Premium for new non-contact users

+
userFull#cc997720 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 voice_messages_forbidden:flags.20?true translations_disabled:flags.23?true stories_pinned_available:flags.26?true blocked_my_stories_from:flags.27?true wallpaper_overridden:flags.28?true contact_require_premium:flags.29?true read_dates_private:flags.30?true flags2:# sponsored_enabled:flags2.7?true id:long about:flags.1?string settings:PeerSettings personal_photo:flags.21?Photo profile_photo:flags.2?Photo fallback_photo:flags.22?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 private_forward_name:flags.16?string bot_group_admin_rights:flags.17?ChatAdminRights bot_broadcast_admin_rights:flags.18?ChatAdminRights premium_gifts:flags.19?Vector<PremiumGiftOption> wallpaper:flags.24?WallPaper stories:flags.25?PeerStories business_work_hours:flags2.0?BusinessWorkHours business_location:flags2.1?BusinessLocation business_greeting_message:flags2.2?BusinessGreetingMessage business_away_message:flags2.3?BusinessAwayMessage business_intro:flags2.4?BusinessIntro birthday:flags2.5?Birthday personal_channel_id:flags2.6?long personal_channel_message:flags2.6?int = UserFull;
+
+---functions---
+
+users.getIsPremiumRequiredToContact#a622aa10 id:Vector<InputUser> = Vector<Bool>;
+

If a user enables their new_noncontact_peers_require_premium global privacy setting, represented in userFull.contact_require_premium, only users that have a premium account, are in our contact list, or already have a private chat with them can write to them in private.

+

To easily check whether we can write to a user with this flag enabled, if we haven't yet cached all the required information (for example we don't have the userFull or history of all users while displaying the chat list in the sharing UI) this method may be invoked, passing the list of users currently visible in the UI, returning a list of booleans that directly specify whether we can or cannot write to each user.

+

This list may then be used, for example, to display a lock near the avatar of each user that we cannot write to, with an appropriate tooltip to purchase a Premium subscription.

+

Note that this method should only be invoked if we don't have a Premium subscription, only for users whose full info (userFull + message history information) is not cached yet, as the same info can be computed locally if all the mentioned information is available, and updated automatically using the usual updates.

diff --git a/data/web/corefork.telegram.org/constructor/updateSmsJob.html b/data/web/corefork.telegram.org/constructor/updateSmsJob.html index e4641e4766..b754f471b0 100644 --- a/data/web/corefork.telegram.org/constructor/updateSmsJob.html +++ b/data/web/corefork.telegram.org/constructor/updateSmsJob.html @@ -4,24 +4,26 @@ updateSmsJob - - @@ -58,7 +60,8 @@ Update">

updateSmsJob

-

+

A new SMS job was received

+