android-oss VS Telegram

what do you mean dead? https://github.com/kickstarter/android-oss

The kickstarter is all rx all the time and it's b-e-a-utiful: https://github.com/kickstarter/android-oss

Those benefits feel like the benefits I used to get when I'd right apps in the genuinely fully reactive flow, like how kickstarter writes their app. It's the benefits of streams, right?

Also, if you want to go hardcore: https://github.com/DrKLO/Telegram

Compare https://github.com/signalapp/Signal-Desktop/commits/main with https://github.com/DrKLO/Telegram/commits/master

Here's a good example https://github.com/DrKLO/Telegram/blob/master/TMessagesProj/src/main/java/org/telegram/ui/ChatActivity.java

Forkgram have more features, but not a fork of Telegram-FOSS, is based on official source witch can contain some proprietary blobs

For a couple of updates already I've been noticing this behavior on my Android phone. Telegram support has been silent unsurprisingly, so I've considered opening an issue directly on github, but repo for android client doesn't allow this. I'm out of ideas how to bring attention to this, because I know other android users with the same issue so it's not user-specific

I see this huge C++ file and I raise you a Java file that's so enormous github refuses to render it: https://github.com/DrKLO/Telegram/blob/master/TMessagesProj/...

— Do not use checkboxes and radio buttons in cells. Due to the complex xml structure and internal layers coloring, simple initialization of the checkbox on old phones took a very long time. As a solution, either use the checkbox images (but then they will be without animation), or use a custom checkbox, as for example telegram uses https://github.com/DrKLO/Telegram/blob/master/TMessagesProj/src/main/java/org/telegram/ui/Components/CheckBoxSquare.java Made by analogy on kotlin: https://github.com/ivan200/buyer/blob/master/app/src/main/java/app/simple/buyer/util/views/CheckBoxSquare.kt