TgDB Search will be down for maintenance for about ~8h

🎉 TgDB is back online!

  📱 TgDB Search Lite: @tgdb_search_bot

  🖥  TgDB Search Plus: tgdb.org/bot

ℹ️ TgDB Update

🇬🇧 The issue causing slow response times for Chinese language queries on the TelegramDB Search Bot has been resolved.
System indexing has been optimized, and Chinese search results now load instantly.

🇨🇳 TelegramDB Search Bot 中文搜索响应缓慢的问题现已修复。系统已完成优化，中文搜索结果现可实现即时加载。


  📱 TgDB Search Lite: @tgdb_search_bot

  🖥  TgDB Search Plus: tgdb.org/bot

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

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

We've eased the restrictions on the /search command, so regular searches are back to normal!

Unfortunately, we’ve had to limit the 'search by ID' feature for certain users for now. Thanks for your patience!

  📱 TgDB Search Lite: @tgdb_search_bot

  🖥  TgDB Search Plus: tgdb.org/bot

The webchat is currently experiencing some technical issues; we are working to resolve them. The issues will be resolved shortly.

All known bugs related to the TgDB Search Plus webchat have finally been fixed.
The webchat now supports notifications and read receipts for messages sent to the bot.
Infinite scrolling and search functionality within the chat history will also be implemented shortly.

  📱 TgDB Search Lite: @tgdb_search_bot

  🖥  TgDB Search Plus: tgdb.org/bot

TgDB Search webchat is down for maintenance

🎉 TgDB is back online!

  📱 TgDB Search Lite: @tgdb_search_bot

  🖥  TgDB Search Plus: tgdb.org/bot

🎉 TgDB is back online!

  📱 TgDB Search Lite: @tgdb_search_bot

  🖥  TgDB Search Plus: tgdb.org/bot