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;
dialogFilterDefault#363293ae = DialogFilter;
@@ -65,6 +64,8 @@
messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
help.getAppConfig#61e3f854 hash:int = help.AppConfig;In the API, folders are called "dialog filters".
+In the UI, folders are typically represented as tabs.
On startup, clients call:
API peer folders are typically used only by archived chats, and are really handy for distinguishing groups of peers, since most peer-related constructors (updates, chat info) will contain the folder_id assigned the specified chat.
In Telegram apps, API peer folders are used only to implement the chat archive, identified by folder_id 1; all other peers are in folder_id 0 by default; no other folder_id is allowed at the moment.
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.
rotation indicates clockwise rotation angle of the gradient
account.wallPapersNotModified#1c199183 = account.WallPapers;
account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
+messageActionSetChatWallPaper#bc44a927 wallpaper:WallPaper = MessageAction;
+messageActionSetSameChatWallPaper#c0787d6d wallpaper:WallPaper = MessageAction;
+
---functions---
account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
@@ -131,9 +134,11 @@ If set, rotation indicates clockwise rotation angle of the gradient
account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
account.getWallPapers#7967d36 hash:long = account.WallPapers;
-account.resetWallPapers#bb3b9804 = Bool;
+account.resetWallPapers#bb3b9804 = Bool;
+
+messages.setChatWallPaper#8ffacae1 flags:# peer:InputPeer wallpaper:flags.0?InputWallPaper settings:flags.2?WallPaperSettings id:flags.1?int = Updates;
Once you've uploaded your wallpaper or received a wallpaper deep link, it can be installed as follows.
-Note that fill wallpapers cannot be installed using the API, clients should install and keep track of them only locally, without synchronizing the wallpaper list or signaling installations.
+Note that fill wallpapers cannot be globally installed using installWallpaper or saveWallpaper, clients should install and keep track of them only locally, without synchronizing the wallpaper list or signaling installations.
The API keeps a list of wallpapers that the user can set as chat background, including some preinstalled ones.
To fetch the list use account.getWallPapers.
To save a wallpaper to the list use account.saveWallPaper with unsave=false.
@@ -145,8 +150,11 @@ Note that calling this method will also automatically save the wallpaper, if it'
Wallpapers can also be installed in a specific chat, by using messages.setChatWallPaper: this will emit a messageActionSetChatWallPaper service message, displaying the wallpaper in the UI along with an invitation for the other user to apply the same wallpaper.
+If the other user decides to apply the same wallpaper to the chat, messages.setChatWallPaper should be invoked passing the wallpaper and wallpaper settings received in the messageActionSetChatWallPaper service message, along with the id of the messageActionSetChatWallPaper service message: this way, the action will emit a different messageActionSetSameChatWallPaper, which should be displayed in the UI as a simple acknowledgment service message, without the full wallpaper and without an invitation for the other user to apply it (since both participants just did that already).
Note that unlike installWallpaper or saveWallpaper, messages.setChatWallPaper accepts fill wallpapers just fine.
diff --git a/data/web/corefork.telegram.org/method/account.uploadWallPaper b/data/web/corefork.telegram.org/method/account.uploadWallPaper index a0291db4c9..c25fc8bd79 100644 --- a/data/web/corefork.telegram.org/method/account.uploadWallPaper +++ b/data/web/corefork.telegram.org/method/account.uploadWallPaper @@ -77,7 +77,7 @@Telegram apps support generating, sharing and synchronizing chat backgrounds.
diff --git a/data/web/corefork.telegram.org/method/messages.setChatWallPaper b/data/web/corefork.telegram.org/method/messages.setChatWallPaper index ab5d7151c5..965eaa318a 100644 --- a/data/web/corefork.telegram.org/method/messages.setChatWallPaper +++ b/data/web/corefork.telegram.org/method/messages.setChatWallPaper @@ -4,32 +4,24 @@Set a custom wallpaper » in a specific private chat with another user.
+wallpaper.settings.