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 10 August 2026 and assigned it the closest of 31 fixed categories, at 75% 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 the other topics.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 3 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 6 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 244 comparable posts for this entry, running 23 July 2026 to 15 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @proglibrary — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_mutual · clone_source, last confirmed 16 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
68 measurements spanning 103 days, net -487. 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 77,343–78,591 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 68
Measured (UTC)
Subscribers
Change
16 Nov 2026, 12:10
77,487
-81
12 Nov 2026, 21:46
77,568
-44
10 Nov 2026, 18:19
77,612
-27
9 Nov 2026, 02:59
77,639
-26
7 Nov 2026, 16:51
77,665
-21
6 Nov 2026, 18:40
77,686
-18
5 Nov 2026, 15:09
77,704
-7
4 Nov 2026, 15:18
77,711
-16
3 Nov 2026, 14:54
77,727
-3
2 Nov 2026, 17:39
77,730
-13
1 Nov 2026, 14:07
77,743
-19
31 Oct 2026, 16:31
77,762
-8
30 Oct 2026, 17:35
77,770
-26
29 Oct 2026, 15:57
77,796
-35
28 Oct 2026, 17:07
77,831
-19
27 Oct 2026, 19:20
77,850
-24
26 Oct 2026, 16:26
77,874
-22
25 Oct 2026, 19:26
77,896
-14
24 Oct 2026, 19:27
77,910
-12
23 Oct 2026, 21:26
77,922
first reading
Engagement
265 posts held, back to 23 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 206 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
4.82%
avg views ÷ 77,487 subscribers
Avg views / post
3,730
117 posts measured
Reaction rate
0.381%
reactions ÷ views · ER floor
Posts in window
117
of 265 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 16 November 2026
Posts held
265 (23 July 2026 – 16 November 2026)
Views total
436,620
Reactions total
1,662
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
16 Nov 2026, 07:50 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
11m 23s
Average length
49s
Measured directly from 14 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
8,325 reactions across 261 posts, in 18 distinct kinds. The most used accounts for 21.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,804
21.7%
😁
1,301
15.6%
👍
1,127
13.5%
🔥
927
11.1%
👾
516
6.20%
🌚
321
3.86%
🤔
307
3.69%
😢
301
3.62%
👏
289
3.47%
💯
225
2.70%
🎉
177
2.13%
🥱
173
2.08%
⚡
161
1.93%
🥰
151
1.81%
😍
144
1.73%
🤩
139
1.67%
❤🔥
135
1.62%
🙏
127
1.53%
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 265 of the 265 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 8,536 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 265 most recent posts we hold, published 23 July 2026 to 16 November 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
18
across the posts below
Posts paid on
11
of 265 we hold a reading for · 4%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @proglibrary. 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 265 most recent posts we hold for this entry, published 23 July 2026 to 16 November 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
0.377%
1 of 265 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
3,740
over 1 measured post
Median views · rest
4,170
over 264 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
erid
Posts
First seen
Last seen
2VtzqxF9x3v
1
7 October 2026
7 October 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 265 most recent posts we hold, published 23 July 2026 to 16 November 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
Telegram’s own ‘edited’ marker: 1 of 117 posts held from the last 30 days (0.855%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🖥 Где потренироваться в Git, если rebase всё ещё хочется делать с подсказкой
На рабочей ветке учиться страшновато. Вот три места, где можно спокойно посмотреть, что команда сделает с историей.
• Learn Git Branching рисует коммиты и ветки прямо в браузере. Возьмите один сценарий и попробуйте сначала merge, а затем rebase. Разницу будет видно на схеме. Тренажёр
• Oh My Git! превращает команды в карточки. Рядом есть т…
🚀 Хватит откладывать обучение, время не ждет. Купи один курс Proglib Academy - второй получи бесплатно!
До 15 ноября включительно можно забрать два курса, оплатив только один 😳
Выбирай свою комбинацию:
🤖 Хочешь в AI-разработку?
«ИИ для разработчиков» + «Разработка ИИ-агентов»
Освой AI в разработке и научись создавать собственных ИИ-агентов.
🧠 Хочешь усилить техническую базу?
«Алгоритмы и структуры данных» + «Мат…
🖥 Что показывает сторонняя проверка IP для Claude
Сервис выдаёт оценку от 0 до 100 по признакам, которые видит снаружи. Среди них тип IP-адреса и отметки о прокси или VPN. Оценку рассчитывают авторы сервиса по собственной формуле. Anthropic свою формулу антифрода не раскрывает.
В «Нейроканале» разобрали, из каких сигналов складывается эта оценка. Там есть и другие разборы сервисов и инструментов для работы с ИИ.
🐸…
🖥 Как подтверждать право доступа к сайту с помощью анонимного токена
Сайт может проверять право доступа с помощью токена, не связывая предъявленный токен с моментом выдачи. Так работает Privacy Pass. Один из его механизмов — слепая подпись.
Клиент скрывает содержимое сообщения перед отправкой на подпись. После получения ответа он снимает маскировку и получает подпись, которую сайт может проверить. Это позволяет, на…
🖥 ИИ предложил индекс для SQL. Запрос ускорился с 18,2 до 0,067 мс
PostgreSQL уже использовал индекс, но отбрасывал 99 990 строк из 100 тысяч. Codex предложил частичный индекс, в который вошли только оплаченные заказы. На учебной базе оба варианта вернули те же десять строк в том же порядке. Время сравнили по медиане пяти прогонов.
Посмотреть планы PostgreSQL и повторить замер
🐸 Библиотека программиста
🖥 Chrome или Firefox: кто займёт меньше памяти с 30 вкладками?
Браузер может освободить память, выгрузив вкладку, а при возвращении загрузить её заново. Поэтому для сравнения нужны два замера: сколько памяти занято через 15 минут и сколько приходится ждать, чтобы снова работать со страницей.
Как провести тест Chrome и Firefox на одном компьютере
🐸 Библиотека программиста
🖥 Как измерить, какие таблицы и индексы занимают место в SQLite
Файл SQLite вырос, и по одному его размеру сложно понять, сколько места занимают данные и сколько приходится на индексы. В CLI SQLite 3.54 для этого появилась команда .diskused.
sqlite3 -readonly app.db ".diskused"
Отчёт показывает распределение места в основном файле базы. Начните с крупнейших таблиц и индексов, затем посмотрите, какие запросы пользу…
🖥 Первую версию npm-пакета теперь можно отправить на проверку перед публикацией
Первый релиз нового npm-пакета можно отправить на проверку командой npm stage publish. Версия попадёт в очередь. Установить её из реестра можно будет после одобрения мейнтейнером.
npm pack --dry-run
npm stage publish
Первая команда показывает, какие файлы попадут в пакет. Вторая отправляет версию на проверку. Для отправки подходят лока…
📊 Бэкендерам в Москве платят 278 тысяч ₽ по медиане. Как сравнить с этой цифрой свой офер?
По данным Хабр Карьеры за первое полугодие 2026 года, медиана по бэкенду составила 278 тысяч ₽ в Москве, 251 тысячу в Петербурге и 220 тысяч в регионах. В этих цифрах учтены разные грейды и премии, а в вакансии может стоять только верхняя граница оклада.
Как сравнить зарплатную вилку, оклад и премию
🐸 Библиотека программиста
🖥 После обновления date-fns вызов parseISO(undefined) начал падать
В date-fns 2.8.1 такой вызов возвращал Invalid Date, а в 4.1.0 выбрасывал исключение при обращении к .split(). Мы воспроизвели разницу и проверили локальную правку: до неё проходили шесть из девяти проверок, после — все девять в CommonJS и ESM.
Посмотреть, где падал парсер, и повторить проверку
🐸 Библиотека программиста
❤2💯2🤩1
Showing the 12 most recent of 265 posts we hold for @proglibrary. 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.
Posts edited after publishing
@proglibrary edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
9 September 2026
Most recent edit
16 September 2026
Posts recorded as deleted after publishing
We recorded 1 post on @proglibrary as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
20 August 2026
Most recent seen missing
20 August 2026
Median time before seen missing
10 days
Seen missing in the last 30 days
0
Polls
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Приходится ли вам копипастить данные и какие именно, когда переходите из одной нейросети в другую?
Код17%
Описание задачи28%
Документацию14%
Результаты работы17%
Настройки и контекст: историю чатов, промпты, скиллы19%
Ничего, использую один инструмент51%
The shares total 146%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Какими ИИ-ассистентами и агентами вы пользуетесь? Можно выбрать несколько
GitHub Copilot8%
Codeium1%
Claude Code47%
Gemini24%
ChatGPT48%
GigaCode (Сбер)4%
Yandex Code Assistant2%
DeepSeek29%
Hermes Agent4%
Другое (напишу в комментариях)12%
The shares total 179%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 265 most recent posts we hold, published 23 July 2026 to 16 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 27 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.
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.
Python jobs — вакансии по питону, Django, Flask @pydevjob · 9,727#82
Read from Telegram’s recommendation API, most recently 19 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.
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js @frontendproglib · 20,572 Telegram ranks this channel #1 of 93 here — alongside 92 others — read 25 September 2026
hahacker_news @hahacker_news · 25,193 Telegram ranks this channel #1 of 59 here — alongside 58 others — read 14 September 2026
Библиотека питониста | Python, Django, Flask @pyproglib · 36,923 Telegram ranks this channel #1 of 84 here — alongside 83 others — read 1 September 2026
NOP::Nuances of Programming @nuancesprog · 55,879 Telegram ranks this channel #1 of 84 here — alongside 83 others — read 23 August 2026
BZD • Книги для программистов @bzd_channel · 36,189 Telegram ranks this channel #2 of 57 here — alongside 56 others — read 1 September 2026
Типичный программист @tproger · 77,999 Telegram ranks this channel #3 of 95 here — alongside 94 others — read 19 August 2026
Журнал «Код» @thecodemedia · 48,860 Telegram ranks this channel #4 of 97 here — alongside 96 others — read 25 August 2026
Библиотека джависта | Java, Spring, Maven, Hibernate @javaproglib · 21,756 Telegram ranks this channel #5 of 88 here — alongside 87 others — read 21 September 2026
[404] — программирование @procode404 · 40,018 Telegram ranks this channel #6 of 83 here — alongside 82 others — read 30 August 2026
Веб-страница @tproger_web · 22,132 Telegram ranks this channel #9 of 96 here — alongside 95 others — read 20 September 2026
Библиотека программиста (книги для разработчиков) @programmist_of · 20,562 Telegram ranks this channel #10 of 63 here — alongside 62 others — read 5 October 2026
Учебные фильмы 🎞 @maths_lib · 25,592 Telegram ranks this channel #10 of 67 here — alongside 66 others — read 14 September 2026
GitHub Community @github · 155,088 Telegram ranks this channel #10 of 87 here — alongside 86 others — read 12 August 2026
Полка Разработчика @developer_shelf · 26,696 Telegram ranks this channel #12 of 63 here — alongside 62 others — read 11 September 2026
Книги и Аудиокниги | Флибуста @skachat_chitat_besplatno · 88,772 Telegram ranks this channel #12 of 73 here — alongside 72 others — read 17 August 2026
Physics.Math.Code @physics_lib · 146,700 Telegram ranks this channel #13 of 72 here — alongside 71 others — read 13 August 2026
Pythonist.ru - образование по питону @pythonist_ru · 23,857 Telegram ranks this channel #15 of 82 here — alongside 81 others — read 17 September 2026
Библиотека Go-разработчика | Golang @goproglib · 23,889 Telegram ranks this channel #15 of 91 here — alongside 90 others — read 17 September 2026
Windows Community @wind_community · 40,828 Telegram ranks this channel #15 of 74 here — alongside 73 others — read 29 August 2026
Английский для программиста | EnglishScript @EnglishScript · 44,304 Telegram ranks this channel #16 of 82 here — alongside 81 others — read 27 August 2026
Python Academy @python_academy · 43,803 Telegram ranks this channel #19 of 87 here — alongside 86 others — read 28 August 2026
IT Юмор @ithumor · 60,108 Telegram ranks this channel #19 of 94 here — alongside 93 others — read 22 August 2026
Zen of Python @zen_of_python · 18,614 Telegram ranks this channel #20 of 91 here — alongside 90 others — read 5 October 2026
Selectel @Selectel · 62,356 Telegram ranks this channel #20 of 96 here — alongside 95 others — read 21 August 2026
This channel appears in 70 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 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“Библиотека программиста” (@proglibrary), 77,487 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/proglibrary.
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.