News for hackers. Stuff that matters.

A comment on Why Telegram is insecure (2015). Parent comment

Re:Why Telegram is insecure (2015) by stunt on Sunday January 06, 2019 @12:03PM (#18839239)
You can literally build your own client. Full spec is open source and documented and it works. There are many implementations already.

You can also compile the official client yourself.

[ Parent | on HN ]
Re:Why Telegram is insecure (2015) by saagarjha on Sunday January 06, 2019 @12:43PM (#18839453)
> You can literally build your own client.

I mean, I could, but the Telegram developers being so opaque about this doesn’t make me feel like this is a good use of my time.

> There are many implementations already.

As far as I can tell, the only implementations for the platforms I care about are the “official” ones (in the sense that they are placed under some random person’s GitHub account and linked to by the Telegram website).

> You can also compile the official client yourself.

I have never been able to get this to work. Either way, what I compile from the “sources” they have put online and what they are shipping are two different things.

[ Parent | on HN ]
Re:Why Telegram is insecure (2015) by dzsekijo on Sunday January 06, 2019 @02:46PM (#18840155)
> As far as I can tell, the only implementations for the platforms I care about are the “official” ones

Telethon (https://github.com/LonamiWebs/Telethon) is a decent up to date (with MTProto) independent clean-room client implementation in the form of a Python lib.

You might consider trying to take care about it.

[ Parent | on HN ]
Re:Why Telegram is insecure (2015) by saagarjha on Sunday January 06, 2019 @02:58PM (#18840228)
Hmm, I’ll take a look. I’m still not convinced that I would work on a better client, though.
[ Parent | on HN ]