Re:Telegram: Video Calls and Seven Years
by dexwell on Saturday August 15, 2020 @07:36AM
(#24168127)
Telegram truly has the best UX of all messengers out there; it’s a shame I can’t switch to it because they don’t do E2EE by default. If I’m going to be switching to a new app it will have to be a Matrix (https://matrix.org/) client. Anyone want to work on a Telegram fork that runs on Matrix?
[ Parent
| on HN ]
Re:Telegram: Video Calls and Seven Years
by chacha2 on Saturday August 15, 2020 @11:41AM
(#24169642)
What I don't understand is why the free software movement so often reinvents the wheel, Telegram releases all the code to their UI but any new security focused chat app always starts from the ground up.
Re:Telegram: Video Calls and Seven Years
by dexwell on Saturday August 15, 2020 @12:42PM
(#24170195)
I think developers prefer writing code they understand over trying to understand someone else's code. I've taken a look at Telegram's codebase, and replacing the Telegram API with the Matrix API is way harder than it sounds. Telegram wasn't developed with this flexibility in mind, and the Matrix SDK has its own way of doing things.
This. I often end up writing my own libraries because of this reason.
Kinda hard to get into other people's minds...
Re:Telegram: Video Calls and Seven Years
by noisebeuter on Monday August 17, 2020 @06:23AM
(#24185814)
If you want to get involved, you might want to take a look at FluffyChat (https://gitlab.com/ChristianPauly/fluffychat) and Ditto (https://dittochat.org/) before starting your own fork. Both projects provide a more simple, Telegram-like user interface on top of Matrix.