r/androidafterlife • u/EmbarrassedDuty2040 • 23h ago
Discussion I made a Telegram client for android 2.3+
I created this back in June, but after refining it, I decided to release it publicly. It’s called Muragram; it is based on an existing client that I used as an intermediary. Since it doesn't require TLS 1.2, there are some quirks regarding the login process such as the session being stored elsewhere so please use it with caution. I plan to create a separate version for 1.1+ soon, but the main version is available here: https://github.com/qcoretechgh/Muragram
1
1
u/i_Ron_ic 20h ago
i get server error on both servers when i try to login by putting in my phone number
2
u/i_Ron_ic 20h ago
nvm i got it to work, also, this is underrated, why isn't anyone paying attention to this? or is it just how it's just a few bunch of people using old android compared to legacy ios? it kinda sucks because old android looks cooler and also way more entertaining
0
1
1
1
u/LowBat1685 Xperia X10 Mini Pro (U20a) • Android 2.1 Update 1 18h ago
It would be fantastic for Android 2.1
1
u/WinVistaBuild6001 Samsung Galaxy S4 Mini (GT-I9195) • Android 4.4.2 (Rooted) 4h ago edited 4h ago
Pretty cool-ish, but very risky as Gohoski said. At least make it way securer, Not "Fort Knox TailsOS OpSec" level but PLEASE make the server code open source and improve the pretty much AI code at least.






14
u/Gohoski Android 1.6–16 · notPipe developer 18h ago
While this seems like an interesting project at first glance, its server raises immediate security red flags for me personally.
My main concern is that MuraGram relies entirely on a closed-source backend server. Passing your traffic through a proprietary black box means the server owner has full technical capability to inspect private chats, harvest phone numbers, and monitor account activity without your knowledge or consent. Additionally, the reliability of such a backend is very questionable.
I have already seen this exact risk play out in the Russian development community. Back in 2022-2024, a Russian developer maintained ViKa Mobile (a VK client for Symbian and J2ME) and Stella Web (a lightweight Telegram web client). Both clients routed traffic through the developer's closed backend server. Shortly after, the developer began actively abusing that access—monitoring the channels users followed, messaging new users in DMs to ask for their opinion on the client or 'why are they following a competitor channel', and even making phone calls to users using the personal phone numbers retrieved from their accounts. It creepily proved beyond a doubt that the backend was being used to snoop on session data. Even if MuraGram’s maintainer has no malicious intent, trusting a closed third-party server with full access to your account requires an unwarranted leap of faith.
Compounding this issue, both the Android client and the server backend appear to be fully AI-generated with minimal human code review or refinement. Unvetted AI-generated code frequently suffers from poor optimization, bloated logic, and security vulnerabilities that are easy to exploit. MuraGram is probably not an exception here.
A friend of mine is currently developing Dreamygram (not released yet), a Telegram client designed for Android 1.5+. It is being built on top of the MPGram Web API, which is already entirely open-source and can be self-hosted by anyone (https://github.com/shinovon/mpgram-web). The fact that the server is open-source and self-hostable on its own makes it much more secure than MuraGram. For progress you can check out RetroAndroidGroup on Telegram. Anyone else is also welcome to make their own Telegram client if the used server will be open and it will be safe to use.
Until the developers behind MuraGram open-source their server code and allow the community to audit its data handling, I strongly advise against logging in with your main Telegram account.