goq/telegram-list: a curated Markdown index of Telegram channels and chats for developers

What goq/telegram-list actually is, and who it is for

This repository is a directory. It contains two top-level files, README.md and bots.md, and the README opens by describing itself as a list of interesting Telegram groups, channels and bots. The stated audience is explicit: programmers, developers, geeks, IT staff, sysadmins and DevOps people, plus anyone else who cares about computers and programming. The list is written in Russian, and the communities it indexes are overwhelmingly Russian-language.

The problem it addresses is discovery. Telegram search is poor at surfacing topic-specific communities, and there is no canonical registry of programming chats. goq/telegram-list substitutes editorial selection for search: a maintainer decides what counts as relevant, and the README states plainly that only relevant resources are added. That filter is the product. If you are a developer looking for a JVM news channel, a Linux users group, a data science job feed or a regional IT community, the README's menu is organised to get you there by category rather than by keyword.

The README also carries a maintenance signal of its own. An icon next to a name means, per the README, that the channel or chat has not been updated for a long time and that the information may be useful but outdated. That is a candid admission: entries are annotated rather than pruned.

How the list is structured: a menu, sections and a separate bots file

The README is a single long Markdown document with an anchor-linked menu at the top. The menu splits into two top-level branches, Channels and Chats, and each branch fans out into topic sections. Under Channels the README lists News, Software development, Frontend, Information security, Machine learning and data science, DevOps, Business and startups, Libraries and knowledge bases, Jobs, Miscellaneous, and Personal blogs. Under Chats it lists programming languages, frameworks and libraries, developer communities, game development and graphics, system and network administration, DevOps and configuration management, QA, databases, big data and machine learning, information security and cryptography, operating systems, mathematics and sciences, mobile development, jobs, project management and Agile, messenger development, geographic information systems, general IT communities, regional Russian IT communities, electronics and embedded systems, and books and philosophy.

Bots are not in the README. The menu links out to a separate file, bots.md, which is the third branch of the index. That split is sensible: bots are tools you invoke, while channels and chats are places you read or talk, and mixing them in one list would blur the distinction.

The data flow is entirely manual. There is no scraper, no build step and no generated output. A contributor opens a pull request against master, and a maintainer merges it if the entry fits. The README invites exactly this, asking readers to send suggestions and pull requests for channels, chats or bots relevant to programming and IT topics. The repository's topics list includes labels like bot, coding, community, data-science, devops, frontend, linux, machine-learning and telegram, which mirrors the section structure rather than adding information.

Using it: from repository to a joined Telegram chat

There is nothing to install. The project is a document, so the first real use is reading it and following a link. You can open README.md directly in a browser on the repository page, or keep a local copy. The README does not document a command-line workflow of its own, so any searching you do is with ordinary tools against the Markdown file.

The README gives this example of how an entry is written, in this case the Linux News channel:

* [Linux News](https://t.me/linux_news_ru) — Новости из мира GNU и Linux.

Every channel, chat and bot in the list follows that shape: a Markdown link to a t.me address, a dash, and a short Russian description. That regularity is what makes the file searchable with plain text tools. If you keep a local copy, you can look for a topic word across the README and read the matching entries with their links.

One structural detail matters when you search. Bots are not in README.md at all; the menu points to bots.md for that section, so a text search limited to the README will never return a bot. The README also states that the warning icon next to a name means the channel or chat has not been updated for a long time, so flag those lines before you spend time on a channel.

The staleness problem is structural, not incidental

A hand-maintained link list has one failure mode that no amount of care removes: links rot and communities go quiet, while the list keeps its shape. goq/telegram-list handles this by annotating rather than deleting. The README defines its warning icon as meaning the channel or chat has not been updated for a long time, and warns that the information may be useful but outdated. That is honest, but it puts the verification burden on you. A channel marked stale may still be readable, or it may be effectively dead; the marker does not distinguish.

The second limitation is language and geography. The README is Russian, and the communities it indexes are largely Russian-language and, in the regional section, tied to specific Russian cities. For an English-speaking developer looking for English-language programming chats, most of the list is not applicable. The repository does not present itself as a global directory, and reading it as one will disappoint.

The third limitation is scope discipline. The README states that only relevant resources are added, which is a filter, not a guarantee of quality. Nothing in the repository describes a review process, a freshness check, or a periodic audit. Relevance is a judgement made at merge time, and the list carries the accumulated result of those judgements. If you need a machine-readable index with health checks, this is the wrong tool; it is a curated reading list, and it behaves like one.

Alternatives: awesome lists, catalogs and Telegram's own search

The closest alternative in shape is an awesome-style list on a code host: a single Markdown file, community pull requests, topic sections. The difference is governance. An awesome list usually enforces a contribution format and a stated inclusion policy, and many are English-first. goq/telegram-list is narrower and deeper on one axis, Russian-language IT communities, with sections such as regional Russian IT communities and messenger development that a general awesome list would not carry. If your interest is Russian-language DevOps, JVM, Linux or data science channels, this list is more specific than a general one; if your interest is English-language communities, it is less useful.

Telegram's own search is the other alternative. It is live and needs no maintenance, but it surfaces channels by name and keyword, not by editorial relevance, and it gives you no way to distinguish an active community from an abandoned one. The list's value is precisely the judgement that search omits, at the cost of being a snapshot.

A third option is a bot-driven catalog: an index served through a Telegram bot or a website, updated programmatically. That approach can track activity and drop dead entries automatically, which this repository cannot. The trade-off is the opposite one: automated catalogs tend to be broader and noisier, and they rarely apply a relevance filter as strict as the one the README describes. Neither approach dominates; they fail in different directions.

Maintenance, licence and what the repository does not tell you

The repository is not archived, and the last push was on 2026-08-30, which is recent enough that the list is still being touched. There are no retrieved releases, which is expected for a document-only project: there is no software to version, and no upgrade path to plan. The cost of adoption is therefore not installation or migration but attention. You read a file, you follow links, and you re-check entries when you return to the list later.

Contributing has a cost too, and it is the cost of a pull request. The README asks readers to send suggestions and pull requests for relevant channels, chats and bots. No template, linter or CI is described, so a contribution is a manual edit to a Markdown file reviewed by a maintainer.

On licensing, the top-level entries are README.md and bots.md, and no licence file is listed among them. The repository's licence is therefore not shown by what is available. That matters if you intend to reuse the list in another project, mirror it, or republish it: without a stated licence you cannot assume permission to redistribute the compilation. Check the repository for a licence file or an explicit statement before reusing the content. This is a factual gap, not legal advice; if the reuse matters commercially, treat the absence of a stated licence as a reason to ask the maintainers directly.

Editorial conclusion

Adopt goq/telegram-list if you want a Russian-language, editorially filtered starting point for finding programming, DevOps, data science and sysadmin communities on Telegram, and you are willing to check each entry before joining. Do not adopt it if you need an English-language directory, an API, an exported data format, or any guarantee that a listed channel is still alive: the README marks stale entries with a warning icon rather than removing them. Before relying on it, open bots.md for the bot section, confirm whether the repository states a licence, and treat the warning marker as the project's own signal that an entry may be outdated.

Frequently asked questions

Official sources

1. goq/telegram-list on GitHub
2. Issues
3. README