@Goutte it doesn't sound like it's true, do you have...

@Goutte it doesn't sound like it's true, do you have a source for that?

From a cursory look at https://github.com/telegramdesktop/tdesktop/tree/dev/Telegram/ThirdParty, it only seems to have about 20-somethig direct ones, and most of those don't seem to have further dependencies.

@evacide

Like 25 August at 23:51 | Wall-to-wall | Open on lor.sh

4 comments

Goutte

@iliazeus @evacide

I "built" (it's NodeJs-based) it myself about a year ago (did not bother checking the current source tree) ; can't blame you for not believing it, I did not either.

I had to check with a friend. I do build pretty much everything I use, for kicks but also because I find that's a good metric for the general quality of an open-source project.

Please do send me a blip if you find nothing suspicious of the sort, I'm always happy to reevaluate my beliefs. :)

26 August at 10:55 | Open on mastodon.social

iliazeus

@Goutte erm, are you sure we're talking about the same app? Telegram Desktop is _not_ NodeJS-based, it is a Qt app written in C++. My previous reply has a link to its source code.

@evacide

26 August at 11:00 | Open on lor.sh

Goutte

@iliazeus @evacide

You are totally right ! It was Signal Desktop that had that many dependencies ; just checked my local clone. I had been compiling Telegram and Element at around the same time, and got mixed up.

Thankfully, you were here.

I'll edit my original post, and profusely apologize to the fedi for such a blunder.

26 August at 11:37 | Open on mastodon.social

iliazeus

@Goutte from what I've heard, Telegram devs are more of a "reinvent the wheel" folks than "pull hundreds of dependencies" ones :)

Their end-to-end encryption implementation is usually criticized for that, for example.

@evacide

26 August at 16:55 | Open on lor.sh