Skip to content
This repository has been archived by the owner on May 10, 2019. It is now read-only.

Telegram X #202

Open
mostafa-v opened this issue Dec 23, 2017 · 42 comments
Open

Telegram X #202

mostafa-v opened this issue Dec 23, 2017 · 42 comments

Comments

@mostafa-v
Copy link

Hi
What is Telegram X?
Is it an official Telegram? Is it really in swift? Where is its source code?

@lampanon
Copy link

lampanon commented Dec 26, 2017

Yes, it's official and developed by the same developer - Peter.
Pay attention to the account that published Telegram X in the app store. Telegram Desktop and Telegram for macOS (native) are both published under this account. Previously, there was a Telegram HD instead of Telegram X.

And yes, it's really in swift.

Where is its source code?

You can find part of it here

@mostafa-v
Copy link
Author

mostafa-v commented Dec 26, 2017

Thanks
That repository is updating more frequently than this.
what do yo mean by part of it?
Do you have more info?
Why telegram is not promoting Telegram X?
Is the objective c code became obsolete in near future?
We want to write a telegram client, we don't know which to choose. (Telegram or Telegram X)

@SiNaPsEr0x
Copy link

he's right @mostafa-v , do you have any other information? it is a wonderful project indeed the new language is the future .. it would be possible to have info about the updates?

@laizaraujo
Copy link

Was it possible for someone to get the Telegram X source code? I'm about to start developing a Telegram client app, and would like to use the swift source code.

@SiNaPsEr0x
Copy link

@laizaraujo another app? .... no please

@mostafa-v
Copy link
Author

As peter himself said:
The source code for Telegram X will be released eventually, no later than the first official public release of the app.
https://github.com/peter-iakovlev/TelegramCore/issues/11

@Younes-L
Copy link

@mostafa-v hello, first official release is today, do you have any info about the code ? Thanks :)

@zeroxxx2
Copy link

I'm wondering what's the advantage of continuing to develop the Old Telegram than X? It's slicker and faster.

Will X support theme files also?

@rafaelekol
Copy link

Is there source code of Telegram X for Android version?

@vyamkovyi
Copy link

vyamkovyi commented Jan 23, 2018

Maybe the sound will be fixed finally?
(yes, related to android and ios version but not sure enough to report here, needs more testing)
What about battery drain?

@vyamkovyi
Copy link

@isopen I believe sound quality and buttery drain, as well as client behavior, is unrelated to TDLib. Should be reported here or in TDesktop repo.
Currently I'm looking toward developers of Kepka because they ALREADY fixed memory leaks. Mobile version leaks as well!

@vyamkovyi
Copy link

@Younes-L
Copy link

@isopen "• As a consequence, one confident programmer for many platforms is enough."

Not sure what you mean, but it got me concerned...

@Younes-L
Copy link

@isopen I have no clue what you're trying to point out. More people = more work and ideas = more better, right ?

@laizaraujo
Copy link

@peter-iakovlev I just read about Telegram official release on January 31 (yesterday)
https://telegram.org/blog/telegram-x
Any information about the source code?

@tulssinep
Copy link

Neeeeeeed this

@puddly
Copy link

puddly commented Feb 2, 2018

  • The code for Telegram for Android was last updated on December 8, 2017. The latest Google Play Store build was updated on January 28, 2018.
  • The code for Telegram for Mac was last updated on December 29, 2017. Mine just auto-updated a few hours ago.
  • The code for Telegram for iOS was last updated on December 8th yet the latest version in the App Store is from January 4, 2018.
  • Telegram X has been in the Play Store since January 22, 2018 yet there's no source code

A lot of the backend code is developed publicly but for whatever reason the actual apps are not. Why is the source code trailing the binary builds by a over a month? Why do people have to open issues asking for more recent code?

@DanielZanchi
Copy link

waiting for the source code.

@Enelar
Copy link

Enelar commented Feb 6, 2018

I don't like where it heading. Once they told us that this platform is secure. You might read protocol specs and client sources, but no the servers, its our commercial secret. OK, said the audience, we skeptical about it, but it does make sense, so lets give it a try. And then, OFFICIAL telegram sources promoting CLOSED source client, that way ahead of alternatives, and tell they doing it for competition. Great, so you do have thousands of the bitcoins, and you want somebody compete with you.

I've reported major bug months ago - any government surveillance service is authorized to receive your messages without sending them to your device. You just have to be on their territory physically. Then they just log in, and remove message "new log in detected". Copy ALL the data, and then terminate their session. So, by the time you read this, all your data may be synced to FBI servers. Just in case.
Security, privacy. What a scam. Official client with source code that "will be released eventually" (read: never). Very suspicious move, and i have no justification or reason for that.

This is common known (Pavel mention this by him self), that all data from his previous project is accessible to Russian government without an order. I don't know what game they are playing, but lets summarize:

You have no clue which data sends yours app, no idea how this data is processed by their service, and there is no way to decrypt your traffic and analyse whats actually been sent. Why am i so paranoid? Go to your settings, open them, and see HOW MUCH EXACTLY permissions (open sourced) telegram needs to work. If you have doubt in somebody's honesty you either don't trust them, or check them. In a case of open source, it just means - go to the repository and read the code. Telegram X have no such choice. Don't trust it until full source disclosure.

P.S I thought in 2018 its clear to everybody that no company with closed source that actually executes on your device(read: not a website) is going to have a chance to survive. Looks like another group of folk want to make sure by them self. Good luck fooling everybody around.

And if you think i am delusional, just say hi to the Skype. And their perfectly encrypted binaries.

P.P.S I have nothing to hide. Each time i need privacy i'm either taking a shit or masturbate, or something like that. And i am DONT like when somebody watching. If you think you don't care, then broadcast such sensitive moments with webcam to the strangers. Why not?

RELEASE THE CODE NOW

P.P.P.S Read this comment, this is important: #202 (comment)
JUST DON'T TRUST TELEGRAM ANYMORE.
You've promised, and we claimed whats ours, whats we payed with our trust.

@isopen
Copy link

isopen commented Feb 6, 2018

telegram x and tdlib are very cool work!

@zeroxxx2
Copy link

zeroxxx2 commented Feb 6, 2018

It's a bit getting out of hand, isn't it? Just because they're slow to release the source codes or maintain the updated copies it doesn't mean they're suddenly malicious and want to sell users' data to govt.

I trust Telegram as much as I trust WhatsApp. There's so much at stake here, once they betray users' trust there's no going back. If you want to disown them, go ahead. I won't at the moment and not anytime soon.

People just love to hate.

@sasha314
Copy link

sasha314 commented Feb 6, 2018

Any information about the source code?

@hcl24
Copy link

hcl24 commented Feb 6, 2018

waiting for...

@DanielZanchi
Copy link

Will the UI be converted to Swift?
or only the core will remain swift?

@lampanon
Copy link

lampanon commented Feb 7, 2018

@danny182 The UI is already on swift, like the whole application.

For those who wanted source code:
Opening source code is great, yeah, but how do you check if the application you have installed was compiled from this source code? Will you compile them manually and sign with your personal developer certificate? I doubt.
This is a beta version in active development and no one forces you to use it. If you don't trust - use the objective-C version and wait for the official release of the Telegram X stable.

I guess Peter will post the source code as soon as FBI downloads all user data.

@vyamkovyi
Copy link

If they were really honest with people, they would have already published all code, no matter how does it "looks". I'm also suggesting moving from Telegram. If they really wanted to, they would have already released all code without fooling users. Both server-side and client-side.

Security through obscurity is a bullshit that doesn't works any more at all.

@hackertron
Copy link

Hey is telegram X for android source code released ?

@laizaraujo
Copy link

@peter-iakovlev
Any news about iOS Telegram X source code release?

@mosqueiro
Copy link

mosqueiro commented Mar 14, 2018

The Android version that was releasing faster is months without updates.
And we did not receive any information from the Telegram on the this, I believe it will not be open source, so we created Telergam X, to have a closed source.

@AlexMercier
Copy link

Telegram X Bug in stickers preview for Inline mode. Instead of the preview image, a white square is shown
screenshot
example: @sticker 👍

@ttyusupov
Copy link

@peter-iakovlev , I can't find Telegram X in Apple store neither for Russia nor for US, what happened with it ?

@Shell32-Natsu
Copy link

@ttyusupov Same. Telegram X has disappeared from the App Store.

@pavelgordon
Copy link

Still waiting for the Telegram X android source code ...

@shekoofev
Copy link

No such module 'Postbox' Telegram x swift source code
I'm having the problem with compiling the new swift source code of telegram X. The source code folder doesn't have the .xcworkspace file and I'm getting errors with modules like Postbox, SwiftSignalKit, MtProtoKitDynamic and etc. Please guide me how to compile this release.
Can anyone help me with that?

@ShadowJonathan
Copy link

Bump, i wanted to develop a small feature in X that I feel many people would need (X messages per X minutes, already exists in official client but not in X), only to find to my suprise that there is no such repository for X, and all other three (IOS X, IOS official, Android official) are tailing behind official releases, and commits are dumps of unknown origin, with hundreds of issues and PRs open that never get answered or acknowledged.

What is it, then? An open source community project, or a place to dump sanitized code and call it "development"?

There's not even a dev branch, ffs.

@tabarani
Copy link

tabarani commented Nov 1, 2018

No such module 'Postbox' Telegram x swift source code
Regarding Postbox, I've seen this repository, give it a try

https://github.com/peter-iakovlev/Postbox

@kingwill101
Copy link

where do i go to request telegramX features in android? curently there is no support for deleting cache for a specific group/channel like in the main telegram version and id love to see that get added

@Younes-L
Copy link

@glenfordwilliams go to the official telegram x android supergroup :

t.me/tgandroidtests

The feature you're looking for can be found under Settings > Data and Storage
It's even better than telegram's (where I accidentally cleared history of a regular chat thinking it would just delete the cache 😫) and you can select what type of cache you want to delete from individual chats

@VictorQueiroz
Copy link

Do we have any date to release Telegram X source code?

@9Morello
Copy link

Any updates on this? Where is the source code for Telegram X?

@lampanon
Copy link

lampanon commented May 5, 2019

@9Morello
Cote part: https://github.com/peter-iakovlev/TelegramCore
UI part: https://github.com/peter-iakovlev/TelegramUI

Have you tried looking at the Peter's github before asking? ( ͡° ͜ʖ ͡°)

@9Morello
Copy link

9Morello commented May 6, 2019

@lampanon I forgot to clarify, I meant the source code for the Android version of Telegram X.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests