#RELEASE v11.12.0-3d76896
What's Changed:
Fixes:
Chores:
Major Update:
Details see GitHub
Apks | Check Update | GitHub | Donate (ζθ΅ )
What's Changed:
Fixes:
- fix: a crash caused by NullPointerException from ffmpeg
- fix: privacy and channel follow checks missing- fix: unused camera icon in photo select sheetChores:
- chore: update ci channel id
- chore: update dependenciesMajor Update:
- feat: bump ndk version to r28b- upstream: update ffmpeg to n7.1
- upstream: bump version to v11.12.0Details see GitHub
Apks | Check Update | GitHub | Donate (ζθ΅ )
π₯30π₯°8π5β€βπ₯3β€3π1
Forwarded from Real WiΕ‘'adel
π₯12π9β€7
Real WiΕ‘'adel
Nullgram-v11.14.1-preview-7029c44-arm64.apk
This is a test version and i will not release stable one recently.
Cuz i am still fixing GnuPG problem and totally no idea why.
Cuz i am still fixing GnuPG problem and totally no idea why.
π23β€7π₯°3
Forwarded from Real WiΕ‘'adel
==== ====
upstream: bump version to v12.0.1
Known issue: The position of the ID display is a bit ugly, I am not very satisfied with it.
Signed-off-by: qwq233 <qwq233@qwq2333.top>
upstream: bump version to v12.0.1
Known issue: The position of the ID display is a bit ugly, I am not very satisfied with it.
Signed-off-by: qwq233 <qwq233@qwq2333.top>
π18β€14
Forwarded from Real WiΕ‘'adel
π55β€20π5π₯°3π2
upstream: bump version to v12.2.10
Long time no see!
We will stick with the old UI and this major version for a long time, until I find a stable way to merge upstream without switching to the new UI. The new UI is just too ugly; I don't like it.
The chat input bar is using the new UI. This was an oversight, but I don't have time to deal with it right now. I will revert it to the old UI later.
This version is an early release, as I haven't been tracking bugs for a while. I currently don't know the exact issues, though I may have a clue about one or two bugs. If you encounter any problems, please give your feedback.
For now, the short-term plan is to manually backport some of the interesting feature updates from newer upstream versions. Currently, I am quite interested in "member tag" and "recently visited chats".
Stay tuned.
Signed-off-by: qwq233 <qwq233@qwq2333.top>
Long time no see!
We will stick with the old UI and this major version for a long time, until I find a stable way to merge upstream without switching to the new UI. The new UI is just too ugly; I don't like it.
The chat input bar is using the new UI. This was an oversight, but I don't have time to deal with it right now. I will revert it to the old UI later.
This version is an early release, as I haven't been tracking bugs for a while. I currently don't know the exact issues, though I may have a clue about one or two bugs. If you encounter any problems, please give your feedback.
For now, the short-term plan is to manually backport some of the interesting feature updates from newer upstream versions. Currently, I am quite interested in "member tag" and "recently visited chats".
Stay tuned.
Signed-off-by: qwq233 <qwq233@qwq2333.top>
π39β€9π₯°6π1π€£1π1
β€31π13π€1
fix network lagging
this issue is caused by obfuscation.
i was obviously using the unobfuscated version, so i didn't encounter this problem. sry for that.
this issue is caused by obfuscation.
i was obviously using the unobfuscated version, so i didn't encounter this problem. sry for that.
π±8π1
Forwarded from Real WiΕ‘'adel
π₯12β€4
Forwarded from teleLakel
Warning about unofficial apps was found in Telegram iOS translation_keys.
So, if a user is using an unofficial Telegram app, you will see a warning Β«%@ uses an unofficial Telegram client β messages to this user may be less secureΒ».
@telelakel
So, if a user is using an unofficial Telegram app, you will see a warning Β«%@ uses an unofficial Telegram client β messages to this user may be less secureΒ».
@telelakel
π€¬25β€6π€3πΎ3
Maybe some of you have heard the news.
First of all, Nullgram is not a fork of that rumored client.
Secondly, even if you are using any of its forks, you don't need to worry. The data collection code is located in the private codebase, so unless the client you are using added something similar (really?), there is nothing to worry about.
Finally, if you are using that rumored client right now, there's no need to worry either. Because your info has already been uploaded, and it's a bit too late to switch to another client now anyway.
Btw, if you are worried about whether Nullgram has similar security risks, you can audit the APK build process yourself. The hash of the APK file should be identical to the sha256 hash recorded in GitHub Actions.
First of all, Nullgram is not a fork of that rumored client.
Secondly, even if you are using any of its forks, you don't need to worry. The data collection code is located in the private codebase, so unless the client you are using added something similar (really?), there is nothing to worry about.
Finally, if you are using that rumored client right now, there's no need to worry either. Because your info has already been uploaded, and it's a bit too late to switch to another client now anyway.
Btw, if you are worried about whether Nullgram has similar security risks, you can audit the APK build process yourself. The hash of the APK file should be identical to the sha256 hash recorded in GitHub Actions.
β€21π5π4π1π€1π1
Nullgram
Maybe some of you have heard the news. First of all, Nullgram is not a fork of that rumored client. Secondly, even if you are using any of its forks, you don't need to worry. The data collection code is located in the private codebase, so unless the clientβ¦
When you use a third-party client, you have to take responsibility for your own data security. If you don't have the ability to audit code, then you are still basically using a closed-source client. So even if you use an open-source client, you still need to pay attention to this kind of issue.
π11β€3π©1π1