Nube ☁️

#️⃣ Community limits update. You can add a channel to a Community only if it has up to 10,000 subscribers, and a group only if it has up to 500 members. As for the overall limits, as mentioned earlier, a Community can contain up to 100 groups and channels combined, as well as up to 100 bots. @telelakel

DSports: ¡EL LÍDER DE LA REMONTADA! El EMOTIVO PARTIDO de MESSI en el ARGENTINA VS EGIPTO https://youtu.be/_SCW09AUZ5s 5:10

INCLUDE: - Github source code: MDGram Messenger - MDGram official channel with 21,000 followers - Official MDGram Group - MDGram Telegram channel themes

Important: The future of MDGram 📢 Hi everyone, I want to be completely transparent with our community. As you know, MDGram was born out of my passion for improving the Telegram experience. However, due to my current work responsibilities, it has become impossible for me to dedicate the time that this project—and all of you—deserve for updates. For this reason, I have decided to put the development of MDGram up for sale. My priority is to ensure the project does not remain abandoned and that someone with the time and dedication can continue providing support and new features, as I know many of you are still waiting for updates. This is not a goodbye, but a "see you soon." I hope to return at some point with new ideas or new projects that will allow me to continue adding value to the community. If you are a developer or have an interest in taking over MDGram, please contact me privately at @Richar_CoCo. I sincerely appreciate all the support and patience you have shown me during this time. Best regards, MDGram Messenger

Nube libre para cualquier persona que necesite citar multimedia en un grupo o artículo, o simplemente para tenerlo guardado. Envíe su multimedia a @droidniuzzz_bot con la etiqueta #Nube, y se enviará automáticamente a este canal. (No importa el tipo de archivo)…

Por ejemplo aquí no supe que responder porque pues era incómodo

Otra de las niñas acosadas

Technical context It is important to understand that @tgdb_search_bot is a public service. For a long time, various third-party Telegram client developers have exploited our bot's functionality to resolve Telegram internal ids into usernames or to provide lookup features within their apps—all without our knowledge, consent, or approval. The presence of our username in a codebase does not imply any partnership or malicious intent on our part; it is simply proof that our public service has been abused by third-party developers who integrate it into their own software behind our backs. You can see for yourself how widespread this unauthorized integration is by checking the sheer number of results for our bot on GitHub: https://github.com/search?q=tgdb_search_bot&type=code

Public Statement regarding the Nekogram incident We are aware of the recent controversy surrounding the Nekogram application and the claims regarding the unauthorized transmission of user phone numbers. Following the public disclosure (GitHub Issue #336), many users have noticed the username @tgdb_search_bot mentioned within Nekogram's source code. We want to address this directly to clear up any misinformation and protect our community’s reputation. To be crystal clear: - TgDB is completely independent. We have no relationship, partnership, or communication with the Nekogram team. We were never consulted, and we did not authorize them to use or include our bot in their codebase. - The allegations that Nekogram phone numbers were transmitted to our bot are factually incorrect. Our bot has never received, processed, or stored any user phone numbers related to this incident. - The inclusion of our bot's username in their source code was a unilateral decision by the Nekogram developers, likely for their own internal app features, done entirely without our knowledge. We have been unfairly dragged into this scandal solely because our project was mentioned in their code, causing our users and the public to draw false conclusions about our involvement. We are currently in contact with the Telegram Team to provide all necessary clarifications and to prove that TgDB has played no part in these activities. Thank you for your continued support and understanding. TgDB Team @tgdb_search_bot www.tgdb.org

If your question is, “Is it true?”, the answer is yes, numbers were sent to the bot. Some people are asking for an “explanation,” but what kind of explanation do you need? It is exactly what it looks like; it is what it is. 🤷‍♂️ For those interested, here is the source code of Extra.java. Fact: not a single number has been stored anywhere or shared with anyone, though people may find that hard to believe.

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.

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.