4 ms·
For people that are not aware: There's a Telegram FOSS [1] fork which contains all kinds of fixes; and additionally is Google Services and tracking free, which
by cookiengineer 6y ago
For people that are not aware: There's a Telegram FOSS [1] fork which contains all kinds of fixes; and additionally is Google Services and tracking free, which means it will run on AOSP and LineageOS without any burden of push services.
You can verify this yourself with AppWarden [2].
[1] https://github.com/Telegram-FOSS-Team/Telegram-FOSS https://github.com/Telegram-FOSS-Team/Telegram-FOSS
[2] https://gitlab.com/AuroraOSS/AppWarden https://gitlab.com/AuroraOSS/AppWarden
- pelasaco 6y agobeing FOSS just in the client side, IMO changes little in comparsion with WhatsApp.
- fsflover 6y agoAt least you know what your device is doing. But walled garden is definitely bad.
- cookiengineer 6y ago> being FOSS just in the client side, IMO changes little in comparsion with WhatsApp. There are efforts implementing mtproto servers that are compatible with the Telegram codebase like telegramd [1] or madelineproto [2] in case you want to host your own server. But, if decentralization is your main focus (interpreting your statement); you probably want to switch to a Matrix-based client anyways. [1] https://github.com/nebula-chat/telegramd https://github.com/nebula-chat/telegramd [2] https://github.com/danog/MadelineProto https://github.com/danog/MadelineProto
- pelasaco 6y agoI would love to have my own telegram infrastructure. I will check those projects, thank you!
- troyvit 6y agoI like Telegram FOSS because it doesn't rely on google's infrastructure to run. That's good enough for me given I already made the questionable decision to run a chat client with a home-baked security protocol ;)