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.

New beta is out!
1.3.6 (TD 2.1.6)

One of important releases in terms of builds. Static Linux binary changed to AppImage.

Ideally there should not be any difference. But in practice it could happen, so I won't risk making this build stable.

Also I've planned to release Windows build without LTO, but since it has auto-download bug, it's too early for this. But I hope that I'll move building to GitHub Actions eventually, because in this case release will be more frequent. If only GitHub won't decide to kick their servers down, like it happened a day ago.

Changes
• Option to disable emoji panel on mouse over. I had no problems with it, but people complained about accidental clicks, asking for this feature. Well, here it is.
• Expanded downloaded mediafiles clear limit. Aside from default options (from 1 week to 1 year), you can set now from 1 to 6 days.

Fixes
• If you had bug with sound switching in tray, or more specifically, option text wasn't changing, now it's fixed.
• Links to settings sections weren't working. Now they should. Test by yourself: tg://settings/kotato

@IlyaFedin also brought some features and changes.
• System window frame. It's already used on Linux, but Windows has its own, drawn by application. If you like system one more for any reason – that option is for you.
• Disable tray icon counter. Earlier it was Linux-only feature, since it took value from environment variable. If you don't like tray counter for any reason, you can disable it with this.
• System Telegram icon. This option still Linux-only, but it moved to Kotatogram Settings from environment variable. It allows to use Telegram icon from system icon theme instead of Kotatogram, that could be crucial, if there is no icon for Kotatogram in your icon theme.
• Also you can change tray icon without restart.

And as last one, taskbar flashing option now available in Telegram Desktop, so duplicate was removed. Now you can find it in Settings > Notifications, right after Play sound checkbox.

P.S. If you're waiting for fcitx fix, it will be soon, supposedly in the next version.

Telegram has been unblocked in Russia!

If you're from Russia, you probably know it anyway, or if not, you're probably not affected by it, but, well, now you know it anyway. It's good news for Russians, since using Telegram should be easier because you don't need to search and setup VPN/proxies.

Regarding Kotatogram: many, including myself, had a problem with using Kotatogram without proxy. Telegram Desktop worked fine, but Kotatogram, based on same sources, for some reason didn't work. Now you can use Kotatogram without redundant actions.

P.S. I perfectly understand that you're waiting for an update and new features. At the moment I can't work on fork at full scale, but when I'll can, I'll do it. I'm not planning to abandon it, since I use it most of the time. Just wait a little longer, and I'll make it soon.

With raising subscribers count (hello to @AlterTG) I'll answer the question which, as I understand, would be asked frequently: will ghost mode be implemented (don't send "read" message status, online status and typing status).

Answer is simple: no, it won't be implemented. I'm not planning to add features that violate Telegram API Terms of Service (section 1.4).