# itgoyo/TelegramGroup: A Curated Telegram Directory With Almost No Code > The repository is a README-only collection of Telegram group, channel and bot links, plus setup notes for iOS restrictions, +86 verification codes and API credentials. It is a directory, not a tool, and that changes who should bother with it. **itgoyo/TelegramGroup** — 2026最新悄咪咪收集的10000+个Telegram群和频道合集，附全网最有趣好用的机器人BOT🤖，聚合电报导航、电报推荐各种高质量站点。 - Repository: https://github.com/itgoyo/TelegramGroup - Website: https://www.tg10000.com - Stars: 5,845 · Forks: 386 - Language: Unknown - License: not declared - Published: 2026-09-28 · Updated: 2026-09-28 · Language: en - Canonical page: https://hysenlabs.com/projects/itgoyo-telegramgroup ## What itgoyo/TelegramGroup actually is This is a directory, not a program. The repository contains two top-level entries, .gitignore and README.md, and the README is the product. It lists Telegram search bots such as @soso, @haisou, @jiso, @jisou, @smss, @CJSY and @kuai, several search groups, and a long tail of recommended channels covering blockchain, shopping, news and regional content. The description claims more than 10,000 groups and channels, and the homepage points to tg10000.com. The audience is Telegram users who want to find groups and channels, not developers who want to build on top of a library. The README states plainly that mainland China users are prohibited from using it and that legal problems are not the project's responsibility. That sentence is the clearest signal about who the maintainer expects to read the page: someone outside mainland China, or someone willing to accept the risk the maintainer explicitly disclaims. ## How the directory is organised and where the content comes from The README is a set of Markdown tables and anchored sections. Search bots get one table with name, link and function. Search groups get another. Everything else, from blockchain groups to traffic-card shops, sits under a section called other recommendations. A navigation block at the top links to anchors such as iOS restrictions, security and privacy, Chinese language, +86 verification codes, Telegram API, common bots, finance, communities, Jingdong beans, circumvention, software, podcasts, channels, media, official verified bots, social media and Telegram groups. The data flow is manual. There is no crawler, no database and no script in the repository. Links are added or removed by editing README.md, so the freshness of any individual entry depends on the maintainer's attention rather than on automation. The .gitignore is the only other file, and it does not hint at a build step. If a bot changes its username or a group goes private, nothing in the repository detects it. That is the central trade-off of a hand-curated list: it can include judgement, but it cannot self-heal. ## Installing nothing: using the list and its search bots There is no package to install. The README gives no install command, no dependency file and no build step. Getting value from the project means opening the README or the homepage and following the links it already contains. The first real use is the search bots. The README describes @haisou as accepting a keyword and returning channels, groups, videos, music, images and files, and @CJSY as accepting a word and returning related groups and channels. In practice you open Telegram and message the bot with a keyword. Because these are Telegram links, there is no shell command to run; the equivalent is opening the t.me URL. ```bash # The README lists links in t.me form; open one to start a chat with the bot # https://t.me/haisou?start=a_7202424896 # https://t.me/CJSY?start=7202424896 ``` What you should see is a Telegram chat with the bot, not a web page with results. The bots answer inside Telegram, and the README notes that @soso requires you to change to a Chinese username before searching groups, channels or videos. That constraint is easy to miss and will look like a broken bot if you skip it. The README also documents how to enter restricted groups on iOS. The stated method is to enable Show Sensitive Content on a desktop or web client, after which the phone client works. The README gives three routes: Telegram Desktop on Windows via Settings, Privacy and Security; Telegram Desktop on macOS via the same path; and the web client at web.telegram.org via Settings. It states a requirement of Telegram iOS client version 5.13 or later, and notes that on macOS the Mac App Store build is now called Telegram Lite. The README says the setting does not need to be changed in the phone app itself. ## The API credentials section is the part to treat with care The README includes a block of api-id and api-hash pairs labelled as free and usable, attributed to clients such as nagram, telegram-android, telegram-desktop, telegram-swift, telegram-x, telegram-web and Nicegram. It also shows a sample application record with an App api_id, api_hash, title and short name, and links to my.telegram.org for official application. These are client identifiers, not personal accounts, and the README presents them without explanation of what happens if many people use the same pair. Telegram's own API application page is the legitimate route, and the README links to it. Anyone building a client or a bot should apply for their own credentials there rather than copy a shared pair from a README, because a shared identifier gives you no control over rate limits or revocation. The README does not discuss that risk, which is a real gap in an otherwise practical page. ## Where this directory fails you The repository has no releases, no licence and no source code beyond README.md. If your evaluation process requires a licence identifier before adoption, there is nothing to check. That is not a small omission for a corporate or open source compliance review. Link rot is the other failure mode. A curated list of Telegram links has no mechanism to detect a dead bot, a renamed channel or a group that has turned private. The README's own note that some search groups require passing a human verification check before joining shows how fragile the entry points are: the link works, but access does not follow automatically. The content also sits outside what many teams can use. The README bans mainland China users and disclaims legal responsibility, and several listed entries are commercial services such as membership resale, SIM cards and bulk-messaging tools. If you need a neutral, auditable source of Telegram community links for a product, this page is the wrong tool. It is a personal recommendation list, and it reads like one. ## Alternatives and how they differ in approach The nearest alternative named in the README itself is itgoyo/TelegramBot, a separate repository described as a collection of commonly used Telegram bots. The difference is scope: TelegramBot collects bots, while TelegramGroup collects groups, channels and bots together and adds setup notes for iOS restrictions, +86 verification and API credentials. If you only need bot links, the narrower repository is the more direct source. If you need the surrounding how-to material, this one carries it. A second difference is between this directory and Telegram's own search. Telegram's in-app search finds public groups and channels by name and keyword without any curated list, but it gives you no editorial selection and no explanation of how to reach restricted content. This repository trades automation for curation: fewer results, more context, and a maintainer's judgement attached to each entry. ## Maintenance, licensing and upgrade cost The last push was on 2026-09-22, and the repository is not archived. There are no releases, so there is no version to upgrade to and no changelog to read. Upgrading means pulling the latest README and diffing it against your copy, which is cheap in effort but offers no compatibility guarantee, because there is no interface to break. The licence is not stated anywhere in the repository. Without a licence file, the default position is that no permission has been granted for reuse, and the README's disclaimer about legal responsibility does not function as a licence. This is a factual gap, not legal advice: anyone planning to redistribute the list, or to build a product on top of it, should ask the maintainer to add an explicit licence before doing so. ## Conclusion Adopt itgoyo/TelegramGroup as a starting point if you want a single page that gathers Telegram search bots, group links and setup notes for restricted content, +86 verification and API credentials. Do not adopt it if you need a maintained package, a versioned release or an API you can call from your own code: the repository has no releases, no license and no source beyond README.md, and the last push was on 2026-09-22. Before relying on it, open the homepage, check that the search bots listed still respond, and confirm the licence situation with the maintainer, because nothing in the repository states one. ## FAQ ### What is itgoyo/TelegramGroup? It is a curated directory of Telegram groups, channels and bots, published as a README with a companion homepage at tg10000.com. The description claims more than 10,000 entries, and the README also carries setup notes for iOS restricted groups, +86 verification codes and Telegram API credentials. ### How do I find Telegram groups with itgoyo/TelegramGroup? The README lists search bots such as @haisou, @CJSY, @soso, @jiso, @jisou, @smss and @kuai, which you message inside Telegram with a keyword. The README notes that @soso requires changing to a Chinese username first, and that some search groups require passing a human verification check before joining. ### Does itgoyo/TelegramGroup need to be installed? No. The repository contains only .gitignore and README.md, and the README gives no install command, dependency file or build step. You use it by opening the README or the homepage and following the t.me links it contains. ### What licence does itgoyo/TelegramGroup use? No licence is stated in the repository. There is no licence file or licence identifier to check before reuse. ### Can mainland China users use itgoyo/TelegramGroup? The README explicitly prohibits mainland China users and states that legal problems arising from use are unrelated to the project. It also documents workarounds for +86 verification codes, including international roaming SMS instructions and TelegramX downloads. ## Sources - [Issues](https://github.com/itgoyo/TelegramGroup/issues) - [itgoyo/TelegramGroup on GitHub](https://github.com/itgoyo/TelegramGroup) - [Project website](https://www.tg10000.com) - [README](https://github.com/itgoyo/TelegramGroup/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/itgoyo-telegramgroup