diff --git a/data/web/corefork.telegram.org/api/folders.html b/data/web/corefork.telegram.org/api/folders.html index 88e6387c57..c2e2518f35 100644 --- a/data/web/corefork.telegram.org/api/folders.html +++ b/data/web/corefork.telegram.org/api/folders.html @@ -71,7 +71,7 @@
  • messages.getSuggestedDialogFilters to fetch a list of suggested folder combinations.
  • help.getAppConfig to fetch app-specific configuration parameters.
    • -

    The boolean under the dialog_filters_tooltip JSON key in the result of help.getAppConfig can be used to determine whether a folder tooltip should be presented to the user right away.
    +

    The boolean under the dialog_filters_tooltip JSON key in the result of help.getAppConfig can be used to determine whether a folder tooltip should be presented to the user right away.
    The UI should then show a list of suggested folder combinations.

    Once configuration is finished, apps call messages.updateDialogFilter to create or update existing folders.
    As per the dialogFilter constructor, folders have multiple flags that can be combined to determine which chats should be included in (or excluded from) the folder.
    @@ -84,16 +84,21 @@ Clients can also receive updateDialog

    Peer folders

    The API also has another method for identifying groups of peers, used by archived chats.

    Schema:

    -
    inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
-inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
+
    inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;
 
-dialogPeer#e56dbf05 peer:Peer = DialogPeer;
-dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
+folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;
 
 updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
 
 updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
 
+
+inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
+inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
+
+dialogPeer#e56dbf05 peer:Peer = DialogPeer;
+dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
+
 ---functions---
 
 folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
@@ -105,7 +110,8 @@ Clients can also receive updateDialog
 
  • folders.deleteFolder can be used to delete peer folders, moving all peers previously present in that folder to the default 0 folder.
    • 
 
 
    Both methods return an updates constructor, containing a single updateFolderPeers with the new folder_id of moved peers.
    
-Clients can also receive updateFolderPeers as a normal update, generated by other clients when modifying peer folders.
    
+Clients can also receive updateFolderPeers as a normal update, generated by other clients when modifying peer folders.
    
+
    Clients can then use InputDialogPeer to refer either to a specific chat, or to all chats in a peer folder: the server will return a DialogPeer in certain constructors for the same purpose.  
    
   
 
           
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index 13a4d232ba..c9ac3b0935 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -266,7 +266,8 @@ Also, discussion group admins can now Schema
 
    phoneConnection#9cc123c7 flags:# tcp:flags.0?true id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;
    
 
    Layer 140
    
-
    Introducing attachment menus, bot web apps, custom bot menu buttons, suggested bot admin rights and ringtones.
    
+
    Introducing attachment menus, bot web apps, custom bot menu buttons, suggested bot admin rights and ringtones.
    
+Also introducing replies to scheduled messages, deletion of all our supergroup messages for everyone, recommended sponsored messages, forced IPv6 connection attempts and more specific DC connection settings.  
    
 
    Schema changes
    
 
    New Methods