diff --git a/data/web/corefork.telegram.org/api/folders.html b/data/web/corefork.telegram.org/api/folders.html index 1c9808693e..c076f136b4 100644 --- a/data/web/corefork.telegram.org/api/folders.html +++ b/data/web/corefork.telegram.org/api/folders.html @@ -44,8 +44,9 @@
Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
-In the API, folders are called "dialog filters"; in the UI, they are typically represented as tabs.
Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
+In the API, folders are called "dialog filters"; in the UI, they are typically represented as tabs.
Schema:
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
@@ -63,8 +64,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;
-On startup, clients call:
+On startup, clients call:
===144===
+messageEntitySpoiler#32ca960f offset:int length:int = MessageEntity;
+messageEntityCustomEmoji#c8cf05f8 offset:int length:int document_id:long = MessageEntity;
===143===
+decryptedMessageMediaDocument#8e4c064c thumb:bytes thumb_w:int thumb_h:int mime_type:string size:long key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
Allow TCP WebRTC connections.