Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
33 measurements spanning 42 days, net +153. 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 40,224–40,482 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
17 Sept 2026, 07:20
40,434
-18
15 Sept 2026, 08:55
40,452
+18
13 Sept 2026, 14:42
40,434
+10
11 Sept 2026, 16:42
40,424
-9
9 Sept 2026, 01:56
40,433
-9
5 Sept 2026, 19:56
40,442
-5
3 Sept 2026, 20:39
40,447
+8
2 Sept 2026, 12:26
40,439
+37
1 Sept 2026, 13:25
40,402
+39
31 Aug 2026, 15:48
40,363
+18
30 Aug 2026, 19:05
40,345
+3
29 Aug 2026, 22:28
40,342
+3
28 Aug 2026, 21:14
40,339
+13
27 Aug 2026, 17:42
40,326
-3
26 Aug 2026, 20:47
40,329
-4
25 Aug 2026, 21:16
40,333
+7
24 Aug 2026, 23:54
40,326
-3
23 Aug 2026, 09:43
40,329
+39
21 Aug 2026, 20:14
40,290
+14
20 Aug 2026, 19:47
40,276
first reading
Engagement
53 posts held, back to 14 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 89 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
17.9%
avg views ÷ 40,434 subscribers
Avg views / post
7,250
23 posts measured
Reaction rate
0.405%
reactions ÷ views · ER floor
Posts in window
23
of 53 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
Window
Rolling 30 days · latest post in window 22 September 2026
Posts held
53 (14 July 2026 – 22 September 2026)
Views total
166,780
Reactions total
676
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Sept 2026, 10:35 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
Photos
≈1,940
Videos
≈66
Links
≈2,020
Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
3m 36s
Average length
43s
Measured directly from 5 videos 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,789 reactions across 48 posts, in 13 distinct kinds. The most used accounts for 33.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
594
33.2%
❤
449
25.1%
🔥
428
23.9%
😁
110
6.15%
🤬
75
4.19%
🤔
37
2.07%
🥰
33
1.84%
😱
14
0.783%
😢
12
0.671%
🤯
12
0.671%
🤩
10
0.559%
👏
8
0.447%
🎉
7
0.391%
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 53 of the 53 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 2,012 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 53 most recent posts we hold, published 14 July 2026 to 22 September 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
3
across the posts below
Posts paid on
3
of 53 we hold a reading for · 6%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Golang_google. 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 53 most recent posts we hold for this entry, published 14 July 2026 to 22 September 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.
Advertising
Ad load
17.0%
9 of 53 posts carry an ad marker
Regulatory tokens
9
posts carrying an erid · 9 distinct tokens
Median views · ads
6,450
over 9 measured posts
Median views · rest
8,090
over 44 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2SDnjeu4DaB
1
22 September 2026
22 September 2026
2VSb5ymsSNn
1
14 July 2026
14 July 2026
2VSb5z2NqwG
1
31 July 2026
31 July 2026
2Vtzqv6wVTp
1
4 August 2026
4 August 2026
2VtzqvSBEDR
1
13 August 2026
13 August 2026
2VtzqwJiXik
1
12 September 2026
12 September 2026
2VtzqwfdQ9Q
1
14 July 2026
14 July 2026
2W5zFGiGmVs
1
11 September 2026
11 September 2026
2W5zFHofQNu
1
1 September 2026
1 September 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 53 most recent posts we hold, published 14 July 2026 to 22 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
👣 webctl: экономный веб-поиск для ИИ-агентов
Умная CLI-утилита на Go для поиска в интернете с помощью Jev.
Jev - модель от TypeSafe AI для быстрых структурированных решений. Она не пишет тексты, а выбирает вариант, выставляет оценку или вероятность.
webctl возвращает компактные и релевантные результаты, сокращая расход токенов при работе агентов с вебом.
https://github.com/dorkitude/webctl
#golang
Не отставайте от рынка — учитесь со скидкой 16%
Если чувствуете, что стоите на месте, и хотите освоить востребованную профессию, — сейчас хороший момент начать.
Потому что до 30 сентября на все курсы Практикума действует скидка 16%.
Выбрать курс
Вы сможете:
— получить актуальные навыки;
— освоить ИИ-инструменты для работы;
— перенять опыт экспертов, которые двигают индустрию;
— попасть в сообщество выпускников, …
🛠 Ax - фреймворк в стиле DSPy для Go, TypeScript, Python, Java, C++, и Rust
Вы описываете, что подать модели на вход и какой результат получить, через типизированную сигнатуру. Например: текст отзыва → тональность из трёх вариантов.
const classify = ax(
'review:string -> sentiment:class "positive, negative, neutral"'
);
const { sentiment } = await classify.forward(llm, {
review: "Отличный продукт!",
});
Что…
🔥 Rune - быстрый IDE и terminal multiplexer с GPU-рендерингом, который теперь открыт на GitHub.
Он объединяет редактор кода, терминалы, CLI-инструменты, language intelligence, отладку, рабочие пространства и coding agents в одной среде. Сам Rune Agent вынесен в отдельное расширение, поэтому редактор можно использовать и как обычную IDE без обязательного AI-слоя.
Проект написан на Go, поддерживает macOS и Linux, а о…
🔥 Большой гайд по миграции с Go на Rust
Для разработчиков переход обычно упирается не в скорость, а в гарантии корректности, runtime trade-offs и ergonomics.
Внутри подробно сравниваются:
go build → cargo build
go test → cargo test
go vet → cargo clippy
nil → Option<T>
error → Result<T, E>
interfaces → traits
goroutines → async/await
-race → compile-time ограничения через Send / Sync
Отдельно хорошо показано, где…
🔥 Yoke - управление пакетами Kubernetes без гор YAML
Вместо сложных Helm-шаблонов Yoke позволяет описывать инфраструктуру обычным кодом.
Схема простая:
`код → WebAssembly → ресурсы Kubernetes`
Пакеты в Yoke называются flights: это WASM-программы, которые генерируют Kubernetes-ресурсы, а Yoke применяет их в кластер.
Что это даёт:
- обычный код вместо шаблонов
- строгую типизацию
- условия и циклы
- нормальное те…
🔥 Yzma - прямое подключение `llama.cpp` к Go-приложениям для локального inference
Проект позволяет запускать локальные LLM из Go без отдельного inference-сервера.
Что интересно:
- прямой доступ к llama.cpp
- hardware acceleration
- Linux, macOS и Windows
- поддержка WebAssembly
- локальный inference внутри Go-приложения
- удобно для desktop, edge и offline-сценариев
То есть вместо схемы:
Go app → HTTP → отдельны…
🐳 Как правильно использовать Docker для Go-приложения - пошаговый гайд
Хороший разбор от freeCodeCamp для тех, кто хочет понять Docker на реальном Go-проекте, а не только по отдельным командам.
Внутри:
- что такое image и container
- как написать Dockerfile для Go
- go mod download и сборка бинарника внутри контейнера
- как собрать image через docker build
- как связать Go-приложение с MySQL
- как добавить phpMyAd…
AvitoTech всегда славился своими проектами на День разработчика, но в этот раз ребята превзошли самих себя!
В честь наступающего Дня разработчика вместе со студией FU2RE и 3D-художником Dmitriev Video они создали большой портал в прошлое — эмулятор 2006 года будущего разработчика. Внутри — олдскульные игры и викторины, за которые можно лутать баллы и подниматься в рейтинге.
Трём лучшим игрокам 15 сентября подарят с…
✔️ Голосовая модель GPT-Live-1 стала доступна по API
OpenAI открыла API полнодуплексной голосовой модели GPT-Live-1 стоимостью 5 центов за минуту. Модель слушает и синтезирует речь одновременно, заменяя традиционный каскад STT–LLM–TTS.
Единая архитектура снизила задержку реакции с 1,4 до 0,8 секунды и позволила обрабатывать перебивания. Обновленная фильтрация пауз и фонового шума сократила число ложных прерываний н…
Уже используете ИИ в проектах? Уверены, что делаете это эффективно и безопасно?
Разберемся 8 октября на бесплатной конференции Selectel ТехноДень про ИТ-тренды, инфраструктуру, ИИ, данные и информационную безопасность.
Присоединяйтесь, чтобы:
🔺Узнать о реальном опыте внедрения ИИ в технологических компаниях.
🔺Обсудить изменение подходов к информационной безопасности в бизнесе в 2027.
🔺Наметить план по созданию отка…
Как вам идея поучаствовать в создании платформы для агентской разработки?
В Ozon Tech сейчас создают такую платформу. Базовый слой и LLM-шлюз уже готовы, дальше — SDK, Tool Hub, оркестрация, инструменты observability и evaluation для AI-агентов.
Ищут Senior-разработчиков. Стек не принципиален — важнее сильная инженерная база и интерес к AI.
Если хочется поработать не просто с LLM, а с инфраструктурой вокруг AI-аген…
😁12❤7👍4🔥4🤬3
Showing the 12 most recent of 53 posts we hold for @Golang_google. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 57 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
3
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
3
vacant every time we have ever looked
@Golang_google named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@fizmat named in 3 posts, 8 August 2026 – 10 August 2026
@front named in 3 posts, 8 August 2026 – 10 August 2026
@kubernetc named in 3 posts, 8 August 2026 – 10 August 2026
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.
Библиотека Go-разработчика | Golang @goproglib · 24,071#1
Read from Telegram’s recommendation API, most recently 30 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.
DevOps @DevOPSitsec · 23,663 Telegram ranks this channel #1 of 90 here — alongside 89 others — read 18 September 2026
Библиотека Go-разработчика | Golang @goproglib · 24,071 Telegram ranks this channel #1 of 91 here — alongside 90 others — read 17 September 2026
Linux Academy @linuxacademiya · 28,422 Telegram ranks this channel #3 of 84 here — alongside 83 others — read 9 September 2026
BZD • Книги для программистов @bzd_channel · 36,430 Telegram ranks this channel #6 of 57 here — alongside 56 others — read 1 September 2026
AvitoTech @avitotech · 25,625 Telegram ranks this channel #13 of 96 here — alongside 95 others — read 14 September 2026
Python вопросы с собеседований @python_job_interview · 24,887 Telegram ranks this channel #17 of 90 here — alongside 89 others — read 15 September 2026
hahacker_news @hahacker_news · 25,571 Telegram ranks this channel #17 of 59 here — alongside 58 others — read 14 September 2026
NOP::Nuances of Programming @nuancesprog · 56,542 Telegram ranks this channel #18 of 84 here — alongside 83 others — read 23 August 2026
Библиотека программиста @proglibrary · 78,334 Telegram ranks this channel #19 of 82 here — alongside 81 others — read 19 August 2026
Selectel @Selectel · 63,289 Telegram ranks this channel #24 of 96 here — alongside 95 others — read 21 August 2026
DevOps by REBRAIN @rebrain_devops · 28,890 Telegram ranks this channel #28 of 94 here — alongside 93 others — read 9 September 2026
Полка Разработчика @developer_shelf · 26,827 Telegram ranks this channel #31 of 63 here — alongside 62 others — read 11 September 2026
Yandex for Developers @Yandex4Developers · 28,505 Telegram ranks this channel #33 of 94 here — alongside 93 others — read 9 September 2026
Machinelearning @ai_machinelearning_big_data · 280,660 Telegram ranks this channel #33 of 95 here — alongside 94 others — read 10 August 2026
The ExtremeCode Times @extremecode · 35,635 Telegram ranks this channel #34 of 93 here — alongside 92 others — read 2 September 2026
Timeweb Cloud Alerts @timewebcloud_alerts · 27,753 Telegram ranks this channel #40 of 87 here — alongside 86 others — read 9 September 2026
Анализ данных (Data analysis) @data_analysis_ml · 50,631 Telegram ranks this channel #40 of 93 here — alongside 92 others — read 25 August 2026
GitHub Community @github · 156,145 Telegram ranks this channel #47 of 87 here — alongside 86 others — read 12 August 2026
Английский для программиста | EnglishScript @EnglishScript · 45,194 Telegram ranks this channel #49 of 82 here — alongside 81 others — read 27 August 2026
Alek OS @Alek_OS · 32,932 Telegram ranks this channel #53 of 95 here — alongside 94 others — read 4 September 2026
Kali Linux @linuxkalii · 55,349 Telegram ranks this channel #53 of 89 here — alongside 88 others — read 23 August 2026
Java библиотека @javalib · 30,666 Telegram ranks this channel #54 of 84 here — alongside 83 others — read 7 September 2026
IT Portal @IT_Portal · 100,284 Telegram ranks this channel #57 of 78 here — alongside 77 others — read 15 August 2026
Data Science. SQL hub @sqlhub · 35,969 Telegram ranks this channel #58 of 87 here — alongside 86 others — read 2 September 2026
This channel appears in 43 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Golang” (@Golang_google), 40,434 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Golang_google.
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.