From 0f435816a1f57c577e69ebbd3e5b90ea30b873a8 Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 13 Oct 2021 19:01:35 +0000 Subject: [PATCH] Update content of files --- data/corefork.telegram.org/api/config.html | 2 +- data/corefork.telegram.org/api/folders.html | 4 ++-- data/corefork.telegram.org/api/layers.html | 2 +- .../method/channels.convertToGigagroup | 10 ++++++---- data/corefork.telegram.org/methods.html | 2 +- 5 files changed, 11 insertions(+), 9 deletions(-) diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html index 5a44971e8c..2f1c3cffc6 100644 --- a/data/corefork.telegram.org/api/config.html +++ b/data/corefork.telegram.org/api/config.html @@ -51,7 +51,7 @@ help.getConfig#c4f9186b = Config; help.getNearestDc#1fb33026 = NearestDc;

The huge config constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the constructor page for more information.

-

Client configuration

+

Client configuration

jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
 
 jsonNull#3f6d7b68 = JSONValue;
diff --git a/data/corefork.telegram.org/api/folders.html b/data/corefork.telegram.org/api/folders.html
index ef41365ad0..d046347576 100644
--- a/data/corefork.telegram.org/api/folders.html
+++ b/data/corefork.telegram.org/api/folders.html
@@ -60,7 +60,7 @@ In the API, folders are called "dialog filters"; in the UI, they are typically r
 messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
 
 help.getAppConfig#98914110 = JSONValue;
-

Folders

+

Folders

On startup, clients call:

Changed Methods
diff --git a/data/corefork.telegram.org/method/channels.convertToGigagroup b/data/corefork.telegram.org/method/channels.convertToGigagroup index c63a545d76..174fc28465 100644 --- a/data/corefork.telegram.org/method/channels.convertToGigagroup +++ b/data/corefork.telegram.org/method/channels.convertToGigagroup @@ -4,10 +4,10 @@ channels.convertToGigagroup - + - + @@ -39,7 +39,7 @@

channels.convertToGigagroup

-

Convert a supergroup to a gigagroup

+

Convert a supergroup to a gigagroup, when requested by channel suggestions.

{scheme}

Parameters

@@ -62,7 +62,9 @@

Updates

Related pages

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

+

How to handle channels, supergroups, groups, and what's the difference between them.

+

Client configuration

+

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

diff --git a/data/corefork.telegram.org/methods.html b/data/corefork.telegram.org/methods.html index 351f3d88b5..c309db3af8 100644 --- a/data/corefork.telegram.org/methods.html +++ b/data/corefork.telegram.org/methods.html @@ -748,7 +748,7 @@ - +
channels.convertToGigagroupConvert a supergroup to a gigagroupConvert a supergroup to a gigagroup, when requested by channel suggestions.