7 ms·
The commit that introduced this: https://github.com/DrKLO/Telegram/commit/a93d2994842ef694442a7ddf4e9be29e31ff0080 https://github.com/DrKLO/Telegram/commit/a93
by kpcyrd 11y ago
The commit that introduced this:
https://github.com/DrKLO/Telegram/commit/a93d2994842ef694442a7ddf4e9be29e31ff0080 https://github.com/DrKLO/Telegram/commit/a93d2994842ef694442...
> Showing 208 changed files with 5,479 additions and 1,841 deletions.
It looks like they squash all their commits and just push one big diff for each update. This isn't really what I've expect from a product that advertises itself as open source security software.
- electic 11y agoAs far as I know, Telegram does not have an official repo. These seem to be updates taken from Telegram's open source page and uploaded to GitHub. You can find the official source code files here: https://telegram.org/apps https://telegram.org/apps
- kpcyrd 11y agoThe page you've linked links to https://github.com/DrKLO/Telegram https://github.com/DrKLO/Telegram for the android client.
- drdaeman 11y agoThat "official" repo is just a code dump. They handle this pretty weirdly, with each commit on master being a release. There's dev branch that was meant to have actual changes (without commit comments - developer said most of his commits have useless descriptions like "bugfixes", but that's a personal preference), but seems to be dead. This was all discussed here: https://github.com/DrKLO/Telegram/pull/76 https://github.com/DrKLO/Telegram/pull/76
- zobzu 11y agoBet this is done on purpose. Also bet without checking anything that the telegram commit was prior to whatsapp block, and that it was just whatsapp retaliating. Dirty games. I don't want to use either.