diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html index 709727188f..5a44971e8c 100644 --- a/data/corefork.telegram.org/api/config.html +++ b/data/corefork.telegram.org/api/config.html @@ -42,7 +42,7 @@

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

-

MTProto configuration

+

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;
 
@@ -81,13 +81,7 @@ While help.getConfig returns MTProto-specif
 
  • 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 show below:
-
    • 
+
  • 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 ».  
    • 
 
 
    Example value:  
    
 
    {
@@ -202,7 +196,7 @@ While help.getConfig returns MTProto-specif
         "VALIDATE_PHONE_NUMBER",
         "NEWCOMER_TICKS"
     ],
-    "autologin_token": "yPsoJyg7wwd1xOC7GJchrRjcH8S-vnyc-NgdjPbnNy5hYb6CFgAAAABGkwcvAKSBUUgM3V0NdMeDpfmRzGyqTigcHSU0zwly2_EAJ9YN",
+    "autologin_token": "string",
     "autologin_domains": [
         "instantview.telegram.org",
         "translations.telegram.org",
@@ -219,7 +213,56 @@ While help.getConfig returns MTProto-specif
         "max_size": 12582912
     }
 }
    
-
    App-specific configuration
    
+
    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 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;
 
@@ -239,7 +282,7 @@ While help.getConfig returns MTProto-specif
 
  • 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
    
+
    Terms of service
    
 
    help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
 help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
 
@@ -261,7 +304,7 @@ While help.getConfig returns MTProto-specif
 
    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
    
+
    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;
@@ -276,7 +319,7 @@ If an update to the Terms Of Service is available, clients are supposed to show
 
  • help.getSupport - Will return the user object that can be used for contacting support.
    • 
 
  • help.getSupportName - Will return a localized name for the support chat.
    • 
 
-
    Country information and login phone patterns
    
+
    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;
diff --git a/data/corefork.telegram.org/api/layers.html b/data/corefork.telegram.org/api/layers.html
index 5d9f1c0428..b7778cefb0 100644
--- a/data/corefork.telegram.org/api/layers.html
+++ b/data/corefork.telegram.org/api/layers.html
@@ -1244,7 +1244,7 @@ Layer…">
 
  • Added stats.getMegagroupStats - Get supergroup statistics
    • 
 
  • Added account.getGlobalPrivacySettings - Get global privacy settings
    • 
 
  • Added account.setGlobalPrivacySettings - Set global privacy settings
    • 
-
  • Added help.dismissSuggestion - Dismiss a suggestion
    • 
+
  • Added help.dismissSuggestion - Dismiss a suggestion, see here for more info ».
    • 
 
 
    Changed Methods
    
 
      
diff --git a/data/corefork.telegram.org/constructor/channelFull.html b/data/corefork.telegram.org/constructor/channelFull.html
index 4204819eef..8af3e695df 100644
--- a/data/corefork.telegram.org/constructor/channelFull.html
+++ b/data/corefork.telegram.org/constructor/channelFull.html
@@ -251,7 +251,7 @@
 
 pending_suggestions
 flags.25?Vector<string>
-A list of suggested actions for the supergroup admin, allowed values:
      CONVERT_GIGAGROUP - The supergroup has many participants: the admin should call channels.convertToGigaGroup to convert it to a gigagroup.
+A list of suggested actions for the supergroup admin, see here for more info ».
 
 
 groupcall_default_join_as
@@ -284,8 +284,8 @@
 
      Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
      
 
      Working with Updates
      
 
      How to subscribe to updates and handle them properly.
      
-
      channels.convertToGigagroup
      
-
      Convert a supergroup to a gigagroup
      
+
      Client configuration
      
+
      The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
      
 
      phone.getGroupCallJoinAs
      
 
      Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
    diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel index a20af15846..c82b1177c7 100644 --- a/data/corefork.telegram.org/method/channels.createChannel +++ b/data/corefork.telegram.org/method/channels.createChannel @@ -158,7 +158,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 ».

    +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/method/help.dismissSuggestion b/data/corefork.telegram.org/method/help.dismissSuggestion index d69e47a19d..7248168e91 100644 --- a/data/corefork.telegram.org/method/help.dismissSuggestion +++ b/data/corefork.telegram.org/method/help.dismissSuggestion @@ -4,10 +4,10 @@ help.dismissSuggestion - + - + @@ -39,7 +39,7 @@

    help.dismissSuggestion

    -

    Dismiss a suggestion

    +

    Dismiss a suggestion, see here for more info ».

    +

    Full info about a channel/supergroup

    +

    Client configuration

    +

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

    diff --git a/data/corefork.telegram.org/method/messages.startHistoryImport b/data/corefork.telegram.org/method/messages.startHistoryImport index e6782a6158..4bab1bd688 100644 --- a/data/corefork.telegram.org/method/messages.startHistoryImport +++ b/data/corefork.telegram.org/method/messages.startHistoryImport @@ -86,7 +86,7 @@ To be called only after initializing the import with 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 ».

    +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 192c7a15cd..01a32f1d24 100644 --- a/data/corefork.telegram.org/method/messages.uploadImportedMedia +++ b/data/corefork.telegram.org/method/messages.uploadImportedMedia @@ -106,7 +106,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 ».

    +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 50ddd3fcbf..351f3d88b5 100644 --- a/data/corefork.telegram.org/methods.html +++ b/data/corefork.telegram.org/methods.html @@ -140,7 +140,7 @@ help.dismissSuggestion -Dismiss a suggestion +Dismiss a suggestion, see here for more info ». @@ -1513,7 +1513,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. +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.