Telegram RegisterThe public register of Telegram
Telegram profile photo for Библиотека Go-разработчика | Golang

Channel

Библиотека Go-разработчика | Golang

@goproglib

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

24,076subscribers

+111 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001465826763
TypeChannel
Username@goproglib
DescriptionВсе самое полезное для Go-разработчика в одном канале. Учиться у нас: clc.to/qaSdww По рекламе: @tproger_sales_bot Для обратной связи: @proglibrary_feeedback_bot РКН: https://gosuslugi.ru/snet/67a4a8c24689c2151c752af0 Заявка: 8137752389
Created6 November 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/goproglib

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 20 August 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

23,96524,08824,026.56 August 2026 — 23,965 subscribers6 August 2026 — 23,970 subscribers7 August 2026 — 23,983 subscribers8 August 2026 — 23,987 subscribers9 August 2026 — 23,994 subscribers10 August 2026 — 23,999 subscribers11 August 2026 — 24,005 subscribers12 August 2026 — 24,018 subscribers14 August 2026 — 24,024 subscribers15 August 2026 — 24,027 subscribers17 August 2026 — 24,036 subscribers18 August 2026 — 24,040 subscribers19 August 2026 — 24,045 subscribers20 August 2026 — 24,044 subscribers21 August 2026 — 24,043 subscribers22 August 2026 — 24,047 subscribers24 August 2026 — 24,048 subscribers25 August 2026 — 24,043 subscribers26 August 2026 — 24,049 subscribers27 August 2026 — 24,055 subscribers28 August 2026 — 24,058 subscribers29 August 2026 — 24,055 subscribers30 August 2026 — 24,053 subscribers31 August 2026 — 24,054 subscribers1 September 2026 — 24,057 subscribers2 September 2026 — 24,060 subscribers3 September 2026 — 24,067 subscribers8 September 2026 — 24,058 subscribers11 September 2026 — 24,085 subscribers13 September 2026 — 24,088 subscribers14 September 2026 — 24,073 subscribers16 September 2026 — 24,065 subscribers19 September 2026 — 24,071 subscribers25 September 2026 — 24,076 subscribers24,0766 August 202625 September 2026
34 measurements spanning 50 days, net +111. 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 23,947–24,106 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
25 Sept 2026, 10:1824,076+5
19 Sept 2026, 00:0124,071+6
16 Sept 2026, 14:3724,065-8
14 Sept 2026, 16:1524,073-15
13 Sept 2026, 05:5524,088+3
11 Sept 2026, 09:3624,085+27
8 Sept 2026, 18:3524,058-9
3 Sept 2026, 13:3824,067+7
2 Sept 2026, 04:4424,060+3
1 Sept 2026, 03:5924,057+3
31 Aug 2026, 05:0624,054+1
30 Aug 2026, 06:2724,053-2
29 Aug 2026, 07:1324,055-3
28 Aug 2026, 09:5824,058+3
27 Aug 2026, 07:1524,055+6
26 Aug 2026, 09:1324,049+6
25 Aug 2026, 11:4324,043-5
24 Aug 2026, 09:3724,048+1
22 Aug 2026, 18:4624,047+4
21 Aug 2026, 09:0524,043first reading

Engagement

66 posts held, back to 22 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 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.6%
avg views ÷ 24,076 subscribers
Avg views / post
3,270
22 posts measured
Reaction rate
0.626%
reactions ÷ views · ER floor
Posts in window
22
of 66 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 26 September 2026
Posts held66 (22 July 2026 – 26 September 2026)
Views total71,890
Reactions total450
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 12:48 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
≈2,780
Videos
≈54
Links
≈5,440

Lifetime counters from Telegram’s own channel header, read 27 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
1m 34s
Average length
24s

Measured directly from 4 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,253 reactions across 65 posts, in 18 distinct kinds. The most used accounts for 22.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥27622.0%
😁23418.7%
👍21216.9%
❤19115.2%
🥱1038.22%
😢403.19%
🌚383.03%
👏322.55%
🤔322.55%
👾252.00%
🎉151.20%
🤩120.958%
💯110.878%
⚡90.718%
😍70.559%
❤‍🔥60.479%
🥰60.479%
🙏40.319%

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 66 of the 66 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,273 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 66 most recent posts we hold, published 22 July 2026 to 26 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
6
across the posts below
Posts paid on
5
of 66 we hold a reading for · 8%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @goproglib. 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 66 most recent posts we hold for this entry, published 22 July 2026 to 26 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
4.55%
3 of 66 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
4,020
over 3 measured posts
Median views · rest
3,610
over 63 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VSb5xkYbZL110 August 202610 August 2026
2VtzqvWmvRr114 September 202614 September 2026
2W5zFJhn4Qy120 August 202620 August 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 66 most recent posts we hold, published 22 July 2026 to 26 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.

Recent posts

26 Sept 2026, 09:04 UTC≈2,020 views12 reactionsread 27 September 2026

🔥 В Go 1.27 появился portable SIMD До этого SIMD-оптимизации в Go требовали архитектурного кода — например, отдельно для amd64 и arm64. ➡️ Теперь экспериментальный пакет simd предлагает единый интерфейс для разных CPU: AVX/AVX2/AVX512, NEON и Wasm SIMD. Размер вектора при этом не зашит в типы, а при отсутствии аппаратной поддержки операции могут выполняться через эмуляцию. Пока API экспериментальный, но идея прос…

🔥10❤2

25 Sept 2026, 18:05 UTC≈2,440 views32 reactionsread 27 September 2026
Photo

🤡🤡 📍 Навигация: Вакансии • Задачи • Собесы 🐸 Библиотека Go-разработчика #GoGiggle

😁25😢4👏2⚡1

25 Sept 2026, 14:10 UTC≈2,530 views5 reactionsread 27 September 2026
Photo

💡 Код работает. А data race уже есть В Go можно записать значение в одной горутине, прочитать в другой — и получить именно тот результат, который ожидал. Проблема в том, что Go этого не гарантирует без синхронизации. Например, даже такой паттерн: msg = "hello" done = true for !done {} fmt.Println(msg) может выглядеть абсолютно логично, но содержит две data race. 🔜 В разборе наглядно показывают, почему так про…

🤔5

23 Sept 2026, 10:03 UTC≈3,030 views27 reactionsread 27 September 2026
Photo

💥 TCP/IP: что происходит с данными в сети Когда Go-приложение отправляет данные по сети, они проходят несколько уровней TCP/IP. Каждый отвечает за свою часть доставки. 1️⃣ Канальный Отвечает за передачу данных внутри конкретной сети: Ethernet, Wi-Fi и т. д. Здесь работают MAC-адреса и механизмы доступа к среде. 2️⃣ Межсетевой Здесь появляется IP — адресация и маршрутизация пакетов между сетями. Маршрутизаторы опре…

😁15👍6❤3🥱2🙏1

22 Sept 2026, 10:47 UTC≈3,310 views7 reactionsread 27 September 2026

🔴 Встроенные функции len, make, panic — встроенные функции Go, которые можно использовать без импорта пакетов. ❓ Но почему тогда len указана в документации builtin как: func len(v Type) int builtin — специальный пакет только для документации. Он не компилируется, а Type — условная заглушка для типа аргумента. При этом built-in — не обычные функции. У них нет стандартных Go-типов: компилятор обрабатывает их вызо…

❤4👍3

21 Sept 2026, 12:18 UTC≈3,850 views16 reactionsread 27 September 2026
File

🤩 Go с нуля: серия базовых шпаргалок Собрали путь от Hello, World! до goroutines, channels и context. День 1 — синтаксис, модули и инструменты День 2 — типы, функции, слайсы, map и ошибки День 3 — интерфейсы, структуры, методы, указатели и композиция День 4 — goroutines, channels, select, WaitGroup, Mutex и context Некоторые формулировки в карточках упрощены для новичков: порядок map не гарантирован, поведение sli…

❤10👍2🤔2🎉1🥱1

20 Sept 2026, 10:20 UTC≈3,670 views89 reactionsread 27 September 2026
Photo

🤔 Вопрос с собеседования по Go Что выведет программа? ❤️ — [1 2 3 4 5] / [1 2 10] 🔥 — [1 2 10 4 5] / [1 2 10] 👍 — [1 2 3 4 5] / [1 2 3] 👇 Правильный ответ (нажми, чтобы прочитать): 🔥 — [1 2 10 4 5] / [1 2 10] b := a[:2] создаёт слайс, который использует тот же backing array, что и a. У b остаётся capacity до конца исходного массива, поэтому append не выделяет новый массив, а записывает 10 в третий элемент. В и…

🔥77❤5🤔4🌚2👾1

19 Sept 2026, 10:27 UTC≈3,460 views20 reactionsread 27 September 2026
Video

🛠 Rune — open-source IDE и terminal multiplexer на Go Rune объединяет IDE, терминал и AI-agent в одном приложении. Что интересного: • GPU-ускоренный интерфейс; • native graphics: OpenGL на Linux и Metal на macOS; • language intelligence из коробки; • встроенный agent; • терминалы, вкладки и окна в едином workspace; • E2E-зашифрованная сеть между экземплярами Rune. Без Electron — приложение использует нативный гра…

🥱9❤6👍3🎉2

18 Sept 2026, 08:19 UTC≈3,860 views26 reactionsread 27 September 2026

🤩 SQLite вместо отдельного брокера в Go Watermill поддерживает SQLite Pub/Sub — сообщения передаются между publisher и subscriber через таблицы SQLite. Что это даёт: — не нужен Kafka, RabbitMQ или Redis; — сообщения хранятся в SQLite-файле; — данные переживают перезапуск приложения; — удобно для небольших сервисов и локальной разработки. 🔴 Публикация: publisher, err := wmsqlitemodernc.NewPublisher( db, …

😁11❤8🌚5👍2

17 Sept 2026, 15:15 UTC≈4,010 views18 reactionsread 27 September 2026

⚡️ Go 1.27 ускоряет небольшие аллокации В Go 1.27 появился size-specialized memory allocation — специальные пути выделения памяти для небольших объектов. Что изменилось: — аллокации объектов размером менее 80 байт могут стать быстрее на 20–30%; — в программах с большим количеством аллокаций общий прирост может достигать 1%; — максимальный эффект ожидается для объектов на 16 и 24 байта. 🔴 Почему это работает? Ран…

🎉7❤5👍5⚡1

16 Sept 2026, 10:29 UTC≈3,850 views15 reactionsread 27 September 2026

🛠 Напишите конфиг сами viper — самая частая рекомендация для конфигурации в Go. Он умеет читать файлы, переменные окружения, удалённые источники и устанавливать дефолты. Звучит удобно, но на практике создаёт проблемы. 🔴 В чём проблема Viper тянет большое дерево зависимостей. Методы GetString, GetInt и подобные не типизированы — значения возвращаются в рантайме без проверки на этапе компиляции. Ключи конфига разбро…

🥱6👍5🔥2💯1😁1

15 Sept 2026, 06:28 UTC≈4,020 views13 reactionsread 27 September 2026
Photo

🔥 Шейдеры на Go: как оживить игру с помощью кода В Ebitengine шейдеры пишутся на Kage — языке с Go-подобным синтаксисом. С их помощью можно создавать эффекты прямо на уровне пикселей: — маска повреждений зданий; — «дрожащий» рукописный текст; — ретро-CRT и глитчи; — зацикленная анимация текстур; — эффект строительства зданий. ➡️ В статье — практические примеры из игр Roboden и Decipherism, а также разбор Fragment…

👍6❤3👏2🤩1🥰1

Showing the 12 most recent of 66 posts we hold for @goproglib. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 8 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.

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.

Golang
@Golang_google · 40,461
#1
Библиотека Go для собеса | вопросы с собеседований
@go_interview_lib · 7,460
#2
Николай Тузов
@ntuzov · 16,870
#3
Go jobs — вакансии по Go
@godevjob · 11,360
#4
Библиотека задач по Go | тесты, код, задания
@go_problems_lib · 6,746
#5
Golang вопросы собеседований
@golang_interview · 15,058
#6
Golang Дайджест
@golang_digest · 13,404
#7
Golang Books
@golang_books · 16,949
#8
Golang Jobs
@GolangJobsit · 14,088
#9
Go tests
@golangtests · 7,833
#10
4gophers
@gophernews · 3,443
#11
Golang задачи с собеседований
@golangquiz · 4,438
#12
Go in Action
@go_in_action · 4,110
#13
Go Library
@golanglibrary · 4,392
#14
Библиотека программиста
@proglibrary · 78,288
#15
Библиотека девопса | DevOps, SRE, Sysadmin
@devopsslib · 10,374
#16
Код и Капуста
@kodikapusta · 1,666
#17
Go Update
@go_update · 3,228
#18
Golang Юниор
@golangprofi · 4,974
#19
Golang | Вопросы собесов
@easy_golang · 4,696
#20
AvitoTech
@avitotech · 25,625
#21
📍Олег Козырев - IT и жизнь ️
@olezhek28go · 11,091
#22
Владимир Балун
@vladimir_balun_programming · 8,618
#23
hahacker_news
@hahacker_news · 25,571
#24
Golang (GO) Работа Вакансии
@rabota_golang · 4,878
#25
Ozon Tech
@ozon_tech · 29,768
#26
Организованное программирование | Кирилл Мокевнин
@orgprog · 14,242
#27
Хабр
@habr_com · 132,465
#28
Библиотека пхпшника | PHP, Laravel, Symfony, CodeIgniter
@phpproglib · 10,492
#29
How to Go wrong
@HowToGoWrong · 1,670
#30
Пятничный деплой
@count0_digest · 4,748
#31
Rust
@rust_code · 8,870
#32
Библиотека питониста | Python, Django, Flask
@pyproglib · 37,384
#33
Go Golang Дайджест
@GolangStack · 2,300
#34
Golang Portal
@GolangPortal · 7,478
#35
Библиотека IT-мемов
@itmemlib · 9,546
#36
Rozetked
@rozetked · 656,361
#37
Типичный программист
@tproger · 78,305
#38
Route 256
@route_256 · 13,032
#39
PRO Go
@pro_gofer · 3,311
#40
DevOps
@DevOPSitsec · 23,684
#41
IT Юмор
@ithumor · 60,568
#42
Библиотека C/C++ разработчика | cpp, boost, qt
@cppproglib · 16,870
#43
Backend Podcast
@bkndpro · 452 (as read 17 September 2026)
#44
Пых
@phpyh · 7,860
#45
BZD • Книги для программистов
@bzd_channel · 36,402
#46
Golang | Тесты
@easy_golang_tests · 3,039
#47
The After Times
@theaftertimes · 16,799
#48
Programmer & IT Memes
@itmemes · 123,290
#49
myStack
@myStack · 883
#50
Библиотека дата-сайентиста | Data Science, Machine learning, анализ данных, машинное обучение
@dsproglib · 18,339
#51
defer panic
@deferpanic · 3,020
#52
Cross Join - канал о разработке
@crossjoin · 3,806
#53
🇺🇦 Go for two :)
@golang_for_two · 1,098
#54
Golang | LeetCode
@easy_golang_task · 3,605
#55
Библиотека ИИ для айтишников
@neuro_text · 6,508
#56
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,930
#57
Библиотека Go (Golang) разработчика
@golang_lib · 2,702
#58
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,705
#59
Библиотека собеса по DevOps | вопросы с собеседований
@devops_interview_lib · 3,446
#60
Linux Academy
@linuxacademiya · 28,434
#61
Evrone IT meetups
@meetups_evrone · 3,713
#62
Yandex for Developers
@Yandex4Developers · 28,545
#63
Ozon Tech | Вакансии
@ozon_tech_vacancies · 3,594
#64
✨Уютный микросервис✨
@go_microservice · 1,139
#65
Golang_Jobs
@Gollang_Jobs · 1,517
#66
NOP::Nuances of Programming
@nuancesprog · 56,542
#67
Yandex for Backend
@yandexforbackend · 10,122
#68
addmeto
@addmeto · 71,835
#69
Технологический Болт Генона
@tech_b0lt_Genona · 9,761
#70
Job for Go, Rust Developers
@forgoandrust · 4,409
#71
Эксплойт
@exploitex · 2,048,279
#72
Код.ру
@d_code · 406,147
#73
Senior Software Vlogger
@seniorsoftwarevlogger · 22,808
#74
Fedkin is thinking
@fedkin_thinking · 9,010
#75
DevOps&SRE Library
@devopslibrary · 19,856
#76
GitHub Community
@github · 155,991
#77
CodeCamp
@codecamp · 181,043
#78
Бэкдор
@whackdoor · 1,603,481
#79
Мониторим ИТ
@monitorim_it · 8,542
#80
Laravel World
@laravel_it · 7,947
#81
🇺🇦 Go performance channel
@go_perf · 1,423
#82
opennet.ru
@opennet_ru · 15,677
#83
Physics.Math.Code
@physics_lib · 146,712
#84
Диджитализируй!
@t0digital · 28,475
#85
k8s (in)security
@k8security · 13,151
#86
Минцифры России
@mintsifry · 234,926
#87
Machinelearning
@ai_machinelearning_big_data · 279,417
#88
🌚Пятисотые на проде😱
@code500 · 10,779
#89
Двач
@dvachannel · 938,773
#90
Николай Тузов - Live
@ntuzov_live · 834
#91

Read from Telegram’s recommendation API, most recently 17 September 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.

Golang
@Golang_google · 40,461
Telegram ranks this channel #1 of 90 here — alongside 89 others — read 30 August 2026
hahacker_news
@hahacker_news · 25,571
Telegram ranks this channel #4 of 59 here — alongside 58 others — read 14 September 2026
Библиотека программиста
@proglibrary · 78,288
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 19 August 2026
Библиотека питониста | Python, Django, Flask
@pyproglib · 37,384
Telegram ranks this channel #8 of 84 here — alongside 83 others — read 1 September 2026
BZD • Книги для программистов
@bzd_channel · 36,402
Telegram ranks this channel #9 of 57 here — alongside 56 others — read 1 September 2026
NOP::Nuances of Programming
@nuancesprog · 56,542
Telegram ranks this channel #14 of 84 here — alongside 83 others — read 23 August 2026
DevOps
@DevOPSitsec · 23,684
Telegram ranks this channel #16 of 90 here — alongside 89 others — read 18 September 2026
AvitoTech
@avitotech · 25,625
Telegram ranks this channel #17 of 96 here — alongside 95 others — read 14 September 2026
Linux Academy
@linuxacademiya · 28,434
Telegram ranks this channel #19 of 84 here — alongside 83 others — read 9 September 2026
Ozon Tech
@ozon_tech · 29,768
Telegram ranks this channel #21 of 98 here — alongside 97 others — read 8 September 2026
Типичный программист
@tproger · 78,305
Telegram ranks this channel #23 of 95 here — alongside 94 others — read 19 August 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,930
Telegram ranks this channel #25 of 93 here — alongside 92 others — read 25 September 2026
Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 22,022
Telegram ranks this channel #32 of 88 here — alongside 87 others — read 21 September 2026
DevOps by REBRAIN
@rebrain_devops · 28,873
Telegram ranks this channel #37 of 94 here — alongside 93 others — read 9 September 2026
Physics.Math.Code
@physics_lib · 146,712
Telegram ranks this channel #39 of 72 here — alongside 71 others — read 13 August 2026
Yandex for Developers
@Yandex4Developers · 28,545
Telegram ranks this channel #49 of 94 here — alongside 93 others — read 9 September 2026
Яндекс нанимает | Вакансии для разработчиков
@ya_jobs · 32,803
Telegram ranks this channel #54 of 96 here — alongside 95 others — read 5 September 2026
Диджитализируй!
@t0digital · 28,475
Telegram ranks this channel #67 of 88 here — alongside 87 others — read 9 September 2026
Alek OS
@Alek_OS · 32,888
Telegram ranks this channel #69 of 95 here — alongside 94 others — read 4 September 2026
GitHub Community
@github · 155,991
Telegram ranks this channel #70 of 87 here — alongside 86 others — read 12 August 2026
Dev KZ | Vacancy
@devkz_jobs · 25,182
Telegram ranks this channel #73 of 86 here — alongside 85 others — read 15 September 2026
RelocationDEV by GeeckoMove
@relocationdev · 23,875
Telegram ranks this channel #84 of 89 here — alongside 88 others — read 17 September 2026
Data Science. SQL hub
@sqlhub · 35,960
Telegram ranks this channel #87 of 87 here — alongside 86 others — read 2 September 2026
Selectel
@Selectel · 63,289
Telegram ranks this channel #90 of 96 here — alongside 95 others — read 21 August 2026

This channel appears in 24 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“Библиотека Go-разработчика | Golang” (@goproglib), 24,076 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/goproglib.

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.