New version is out!
1.3.3 (TD 2.1.1)

Minor version, which updates official app sources to 2.1.1.

By the way, two patches were moved to official app:
• Bot message privacy status in group member list.
• "Subscribers" instead of "members" in channels.

Also TDesktop 2.1.1 now have custom shortcuts for folders, but with changed names. Old shortcuts-custom.json commands should work fine, but it's recommended to update to use TDesktop ones to increase compatibility.

Changed commands
• folder_1..folder_6 -> folder1..folder6
• folder_all -> all_chats
• folder_last -> last_folder
• folder_next -> next_folder
• folder_previous -> previous_folder

If you're using my gist for old hotkey behavior, it's now updated to reflect these changes.

But where is 1.3.2?
1.3.2 had severe bug that caused crash if you hide "All chats" folder. 1.3.3 fixed it, but I had to delay the release because of it.

A little poll before the release.

TDesktop 2.1.2 has decreased sticker size from 256 to 228 pixels. This causes problems with height changing option like increased gaps. There are two ways to solve it:

1. Cut the part of the option, making 228 as maximum value. In this case highest value will be equal to official app's value.
2. Add option "Apply to sticker width", which will scale sticker width along with sticker height.

Question is not about this, as you could think, because it's clear that I would add an option. Question is: should this option be default? Of course, you can disable it at any time.

New version is out!
1.3.4 (TD 2.1.2)

In previous poll most people voted for enabling "Apply for sticker width" by default, so with adding this option it's enabled by default.

Apart from that, there are other interesting changes:

• Option "Chat ID in profile" now offers Bot API chat ID format (minus in the beginning for groups, -100 for channels and supergroups).
• Message ID now shown by hover on message date.
• Service message (joining chat, creating chat, pinning a message, and so on) now shows time when this action happened.

Fixes are there too:
• Fixed protection from broken JSON settings file. When wrong values are set in kotato-settings-custom.json file, opening settings could cause crash.
• Fixed length of sticker set noscript, earlier three-dots button could overlap part of the noscript, if it's too long.
• Fixed missing "account inaccessible" in drop-down chat list, earlier it was good old "last seen a long time ago".
• Icon for removing member from chat in member list is back on old place. Hovering hides admin rank though, since it looks more clear than, for example, moving rank.

Also @IlyaFedin made some changes to AppImage:
• Now AppImage can take settings from qt5ct and lxqt (in addition to gtk3, gtk2 and kde).
• It now uses TDesktop's code for creating shortcut, and AppImageLauncher doesn't detect it as AppImage. Because of this you can freely move it in any folder, and it will work just as static Linux binary build.

Poll about future of Linux builds

@IlyaFedin, who made AppImage builds for fork, suggested to keep only AppImage from Linux builds.

Advantages:
• lower binary size (50 MB AppImage vs 100 MB static binary)
• easier and faster builds (less waiting for release)
• can automatically take icon theme and font settings from GTK without qt5ct (system icons support without unnecessary installs)
• supports Kvantum themes
• more supported systems (Ubuntu 14.04+, static binary built on 16.04)

From what I see, only drawback here is an update size (50 MB AppImage vs 30 MB static binary). If you have any problem with AppImage, that wasn't on static binary, share it in comments. Also vote in poll on how do you like this idea.

Convenient links:
• Static binary: suggested to remove
• AppImage: suggested to make only official build for Linux

Please note, that it won't change building for individual distros. The question is about builds that are posted on this channel and GitHub.

A little explanation regarding AppImage from @IlyaFedin:

AppImage doesn't have any significant differences from static binary. Both takes all dependencies with them, both by themselves are files, that you just need to run. However, AppImage build requires less effort and gives better system integration.

I'll also remind that it's not about builds package manager: i.e. it won't affect kotatogram-desktop-dynamic-bin from AUR.

New version is out!
1.3.5 (TD 2.1.4)

TDesktop sources has been updated to 2.1.4.

Regarding static builds for Linux

Even though many voters supported static binary, nobody told why it's better than AppImage. So I decided to support static binary builds until 1.4 version, and in 1.4 switch to AppImage.

Once again I'm reminding you that other builds like package manager builds won't change because of this.