Telegram RegisterThe public register of Telegram

Channel

GitHub Community

@github

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

149,921subscribers

+414 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001639833661
TypeChannel
Username@github
Created29 October 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/github

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 78% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

149,507149,985149,7466 August 2026 — 149,507 subscribers6 August 2026 — 149,507 subscribers6 August 2026 — 149,618 subscribers7 August 2026 — 149,809 subscribers8 August 2026 — 149,904 subscribers9 August 2026 — 149,924 subscribers10 August 2026 — 149,937 subscribers11 August 2026 — 149,985 subscribers13 August 2026 — 149,921 subscribers149,9216 August 202613 August 2026
9 measurements spanning 7 days, net +414. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 149,435–150,057 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:14149,921-64
11 Aug 2026, 20:35149,985+48
10 Aug 2026, 20:45149,937+13
9 Aug 2026, 19:57149,924+20
8 Aug 2026, 19:45149,904+95
7 Aug 2026, 22:10149,809+191
6 Aug 2026, 20:40149,618+111
6 Aug 2026, 01:45149,507no change
6 Aug 2026, 01:39149,507first reading

Engagement

68 posts held, back to 3 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 18 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
5.07%
avg views ÷ 149,921 subscribers
Avg views / post
7,610
68 posts measured
Reaction rate
0.305%
reactions ÷ views · ER floor
Posts in window
68
of 68 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held68 (3 August 202612 August 2026)
Views total517,180
Reactions total1,575
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 19:19 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 54s
Average length
1m 54s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1,297 reactions across 58 posts, in 6 distinct kinds. The most used accounts for 51.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
66851.5%
🤣30523.5%
🔥16913.0%
🤔1058.10%
😢312.39%
🤓191.46%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 68 of the 68 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1,575reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 68 most recent posts we hold, published 3 August 2026 to 12 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
25
across the posts below
Posts paid on
6
of 68 we hold a reading for · 9%
Most on one post
16
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @github. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 68 most recent posts we hold for this entry, published 3 August 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

12 Aug 2026, 17:32 UTC≈2,230 views6 reactionsread 12 August 2026
Photo

Sandbox — универсальная песочница для AI-агентов, объединяющая Browser, Shell, File, MCP и VSCode Server в одном контейнере Docker. 🐱 GitHub

5🔥1

12 Aug 2026, 16:17 UTC≈3,210 views3 reactionsread 12 August 2026
Photo

Athas — лёгкий кроссплатформенный редактор кода, созданный на Tauri (Rust и React) с поддержкой Git, AI-агентами, назначениями клавиш vim. 🐱 GitHub

3

12 Aug 2026, 15:17 UTC≈3,970 views32 reactionsread 12 August 2026
Photo

Уже очевидно, что ВАЙБКОДИНГ — главный навык ближайших лет Посмотрите сами. ИИ уже забирает на себя работу целых команд: пишет код, закрывает задачи джунов и позволяет стартапам запускать продукты в 2–3 раза меньшим составом. То, на что раньше нужны были несколько разработчиков, сегодня всё чаще делает один человек с ИИ-агентами. И это только начало. Те, кто освоит вайбкодинг сейчас, смогут быстрее запускать проект

🤣217🔥4

12 Aug 2026, 14:34 UTC≈4,090 views5 reactionsread 12 August 2026
Photo

Database-lab-engine — позволяет ветвить базу данных и тонкое клонирование для любой базы данных Postgres, а также поддерживает тестирование баз данных в CI/CD. Это оптимизирует затраты, связанные с базами данных, одновременно повышая время выхода на рынок и качество программного обеспечения. Следите за новостями, чтобы быть в курсе. 🐱 GitHub

5

12 Aug 2026, 11:33 UTC≈5,190 views14 reactionsread 12 August 2026
Photo

Aifreeforever — Онлайн‑платформа, где собраны сотни бесплатных ИИ‑сервисов для самых разных задач — от работы с текстом и изображениями до аудио и инструментов для разработчиков. Каталог удобно разбит на категории, есть фильтры для быстрого поиска подходящих решений. Все инструменты доступны без оплаты, что экономит время и упрощает подбор нужного сервиса. Подойдёт тем, кто работает с контентом, кодом или просто ищ

8🤣4🔥2

12 Aug 2026, 09:50 UTC≈5,350 views12 reactionsread 12 August 2026
Photo

Mcp-scanner — инструмент на Python для сканирования серверов MCP (Model Context Protocol) и инструментов для потенциальных находок в безопасности. MCP Scanner объединяет Cisco AI Defense inspect API, правила YARA и LLM-as-a-judge для обнаружения вредоносных инструментов MCP. 🐱 GitHub

9🤣2🔥1

12 Aug 2026, 09:21 UTC≈5,330 views10 reactionsread 12 August 2026
Photo

Маркетплейс GPU-серверов для AI-задач — по лучшим ценам в России Qudata.ai — аренда GPU-мощностей для обучения моделей, инференса и облачных вычислений. 🧠 Готовая инфраструктура под AI — обучение, дообучение, инференс моделей ИИ. 🔒 Закрытый контур — размещайте проекты с чувствительными данными в изолированной среде. 📈 Масштабирование по запросу — от одной GPU до кластера. 💳 Оплата по факту — платите только за и

🤣73

12 Aug 2026, 08:33 UTC≈5,480 views10 reactionsread 12 August 2026
Photo

WorldGrow — это иерархическая структура для бесконечной (открытой) генерации 3D-миров. Начиная с одного семенного блока, система выращивает большие среды за счёт блокового синтеза и доработки от грубого к тонкому, создавая согласованные глобальные планировки и детализированную локальную геометрию/внешний вид. Сгенерированные сцены пригодны для прогулок и подходят для навигации и оценки планирования. 🐱 GitHub

7🔥3

12 Aug 2026, 05:31 UTC≈6,020 views18 reactionsread 12 August 2026
Photo

Documentation AI — сервис, который автоматизирует процесс создания и обновления документации для вашего API. Ссылка на сервис 🐱 GitHub

🤣115🔥2

11 Aug 2026, 21:45 UTC≈6,880 views21 reactionsread 12 August 2026
Photo

GitX — это портативный навык AI-агента для создания чистых Git-коммитов, тегированных веток и безопасных push-файлов между Codex, Claude Code, Cursor и другими совместимыми с навыками агентами. 🐱 GitHub

10🤣9🤓2

11 Aug 2026, 19:32 UTC≈7,200 views23 reactionsread 12 August 2026
Photo

Logocreator – генератор логотипов с открытым исходным кодом. Собрать логотип можно как конструктор: выбрать нужные детали и настроить стили. 🐱 GitHub

16🤣7

11 Aug 2026, 17:35 UTC≈7,280 views14 reactionsread 12 August 2026
Photo

Text-extract-API — конвертируйте любое изображение, PDF или документ Office в текст Markdown или JSON-структурированный документ с очень высокой точностью, включая табличные данные, числа или математические формулы. API построен на FastAPI и использует Celery для асинхронной обработки задач. Redis используется для кэширования результатов OCR. 🐱 GitHub

13🤣1

Showing the 12 most recent of 68 posts we hold for @github. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 75,955 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 22 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s.When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Programmer & IT Memes
@itmemes · 124,779
#1
Open Source
@open_source_friend · 51,913
#2
Хабр
@habr_com · 131,717
#3
CodeCamp
@codecamp · 183,094
#4
Не баг, а фича
@bugfeature · 593,848
#5
Чёрный Треугольник
@black_triangle_tg · 63,811
#6
[PYTHON:TODAY]
@python2day · 63,944
#7
IT Юмор
@ithumor · 60,930
#8
Хауди Хо - IT юмор, жизнь программиста
@howdyho_official · 80,370
#9
Библиотека программиста
@proglibrary · 78,397
#10
SecurityLab.ru
@SecLabNews · 83,344
#11
IT Portal
@IT_Portal · 101,656
#12
Metanit
@metanit · 8,097
#13
Machinelearning
@ai_machinelearning_big_data · 286,250
#14
GitHub Сообщество
@Githublib · 8,386
#15
DevHumor
@devhumor_tg · 13,646
#16
Бэкдор
@whackdoor · 1,654,052
#17
Двач
@dvachannel · 938,558
#18
Эксплойт
@exploitex · 2,057,246
#19
Технотренды
@techno_media · 818,650
#20
Пекарня
@pekagame · 1,101,545
#21
Rozetked
@rozetked · 667,596
#22
Код.ру
@d_code · 381,029
#23
1337
@media1337 · 1,186,864
#24
Programmer memes
@programmer_memes · 52,088
#25
4PDA Community
@pda_4 · 89,067
#26
VG/Двач
@ru2chvg · 181,134
#27
NN
@naebnet · 2,194,148
#28
r/ретранслятор
@retra · 165,443
#29
Ateo Breaking
@ateobreaking · 646,333
#30
XOR
@xor_journal · 158,763
#31
Не баг, а фича
@bugnotfeature · 852,053
#32
Рестарт
@remedia · 732,645
#33
Reddit
@Reddit · 163,388
#34
Denis Sexy IT 🤖
@denissexy · 134,740
#35
Social Engineering
@Social_engineering · 125,155
#36
Типичный программист
@tproger · 78,786
#37
Лепра
@Lepragram · 342,561
#38
Yaplakal.com
@yaplakal · 423,658
#39
эйай ньюз
@ai_newz · 95,797
#40
КБ. экономика
@cb_economics · 344,290
#41
addmeto
@addmeto · 72,223
#42
4chan
@ru4chan · 163,936
#43
Этичный Хакер
@hack_less · 227,041
#44
Physics.Math.Code
@physics_lib · 145,853
#45
MDK
@mudak · 539,588
#46
Golang
@Golang_google · 40,283
#47
Сегодня в тренде
@trends · 1,114,868
#48
Data Secrets
@data_secrets · 92,020
#49
solo lemon.
@sololemonx · 3,949
#50
Gram RUS
@toncoin_rus · 541,574
#51
Пикабу
@pikabu · 256,983
#52
Говнокод
@g_code · 14,969
#53
infosec
@it_secur · 61,066
#54
Senior Python Developer
@seniorpy · 40,294
#55
Code Learning
@codelearning_tg · 9,463
#56
ЗаТелеком 🌐
@zatelecom · 64,553
#57
Клиент всегда прав
@klientvsprav · 1,083,531
#58
Windows Community
@wind_community · 41,631
#59
CMD | IT
@cmd_it · 24,628
#60
КБ. Игры
@cb_games · 380,373
#61
Telegram Info
@tginfo · 82,196
#62
Утечки информации
@dataleak · 120,632
#63
CyberYozh
@cyberyozh_official · 62,456
#64
Джейпег Малевича
@malepeg · 566,438
#65
Нейродвиж
@neuraldvig · 301,235
#66
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,595
#67
Сиолошная
@seeallochnaya · 77,459
#68
Frontender's notes [ru]
@frontendnoteschannel_ru · 31,807
#69
Библиотека Go-разработчика | Golang
@goproglib · 24,018
#70
Bash Days | Linux | DevOps
@bashdays · 23,760
#71
Типичный Сисадмин
@sysodmins · 37,623
#72
Книжное хранилище
@knijnoe_xranilishe · 19,765
#73
Ньюсач/Двач
@ru2ch · 638,514
#74
Mash
@mash · 3,112,068
#75
Раньше всех. Ну почти.
@bbbreaking · 1,972,542
#76
Baza
@bazabazon · 1,543,278
#77
Алексей Шевцов
@jolybells · 359,983
#78
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,096,087
#79
КБ
@cbpub · 637,809
#80
4ch
@why4ch · 1,063,362
#81
Абу
@abuwtf · 196,596
#82
Вестник Шевцова
@jolynews · 209,359
#83
Банки, деньги, два офшора
@bankrollo · 450,997
#84
Apple Media
@media_apple · 127,856
#85
Big Geek
@biggeekru · 575,858
#86
TrendWatching
@trendwatching24 · 1,473,361
#87

Read from Telegram’s recommendation API, most recently 12 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Physics.Math.Code
@physics_lib · 145,853
Telegram ranks this channel #18 of 72 here — alongside 71 others — read 13 August 2026
Не баг, а фича
@bugfeature · 593,848
Telegram ranks this channel #28 of 94 here — alongside 93 others — read 8 August 2026
CodeCamp
@codecamp · 183,094
Telegram ranks this channel #33 of 94 here — alongside 93 others — read 12 August 2026
Технотренды
@techno_media · 818,650
Telegram ranks this channel #45 of 94 here — alongside 93 others — read 8 August 2026
XOR
@xor_journal · 158,763
Telegram ranks this channel #57 of 93 here — alongside 92 others — read 12 August 2026
ГуголЪ | IT и Тренды
@google_trends2 · 402,675
Telegram ranks this channel #69 of 88 here — alongside 87 others — read 10 August 2026
Этичный Хакер
@hack_less · 227,041
Telegram ranks this channel #74 of 81 here — alongside 80 others — read 12 August 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.

“GitHub Community” (@github), 149,921 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/github.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.