Всё самое интересное по программированию
Разместить рекламу: @tproger_sales_bot
Правила общения: https://tprg.ru/rules
Другие каналы: @tproger_channels
Сайт: https://tprg.ru/site
VK: vk.com/tproger
Регистрация в перечне РКН: https://tprg.ru/mJwo
Created
11 March 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
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 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 sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 313 comparable posts for this entry, running 27 July 2026 to 10 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 3 channels, the one whose matching posts we hold earliest is @tproger — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 11 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 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.
129 measurements spanning 97 days, net -1,058. 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,791–79,315 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 129
Measured (UTC)
Subscribers
Change
10 Nov 2026, 17:56
78,009
-2
10 Nov 2026, 16:37
78,011
+21
9 Nov 2026, 01:41
77,990
no change
9 Nov 2026, 00:41
77,990
-25
7 Nov 2026, 16:18
78,015
no change
7 Nov 2026, 15:47
78,015
-2
6 Nov 2026, 17:08
78,017
+15
6 Nov 2026, 11:36
78,002
-4
5 Nov 2026, 14:16
78,006
-5
5 Nov 2026, 10:38
78,011
-2
4 Nov 2026, 16:16
78,013
+4
4 Nov 2026, 10:26
78,009
+8
3 Nov 2026, 12:39
78,001
-3
3 Nov 2026, 09:47
78,004
+8
2 Nov 2026, 15:10
77,996
+4
2 Nov 2026, 10:59
77,992
no change
1 Nov 2026, 15:28
77,992
-8
1 Nov 2026, 10:56
78,000
-8
31 Oct 2026, 18:39
78,008
+6
31 Oct 2026, 12:06
78,002
first reading
Engagement
331 posts held, back to 27 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 207 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
9.62%
avg views ÷ 78,009 subscribers
Avg views / post
7,510
81 posts measured
Reaction rate
0.416%
reactions ÷ views · ER floor
Posts in window
81
of 331 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 11 November 2026
Posts held
331 (27 July 2026 – 11 November 2026)
Views total
607,920
Reactions total
2,530
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
11 Nov 2026, 14:45 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
≈3,850
Videos
≈1,160
Links
≈8,520
Lifetime counters from Telegram’s own channel header, read 11 November 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 33s
Average length
1m 11s
Measured directly from 3 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
11,437 reactions across 327 posts, in 65 distinct kinds. The most used accounts for 15.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
1,819
15.9%
❤
1,677
14.7%
🔥
1,067
9.33%
😁
740
6.47%
👏
594
5.19%
🤣
425
3.72%
🤔
410
3.58%
🎉
402
3.51%
💯
338
2.96%
💊
337
2.95%
👎
206
1.80%
👌
167
1.46%
🤝
153
1.34%
✍
135
1.18%
🌚
125
1.09%
⚡
120
1.05%
🤯
115
1.01%
🤩
96
0.839%
👀
92
0.804%
🙈
92
0.804%
45 further kinds
2,327
20.3%
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 331 of the 331 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 11,684 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 331 most recent posts we hold, published 27 July 2026 to 11 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
19
across the posts below
Posts paid on
14
of 331 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 @tproger. 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 331 most recent posts we hold for this entry, published 27 July 2026 to 11 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.302%
1 of 331 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
7,180
over 1 measured post
Median views · rest
6,990
over 330 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
2W5zFJrVGHw
1
24 September 2026
24 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 331 most recent posts we hold, published 27 July 2026 to 11 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: 2 of 81 posts held from the last 30 days (2.47%) 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).
Процессор не загружен, а сервер всё равно тормозит
Низкая загрузка CPU ещё не означает, что у сервера есть свободные ресурсы. Запросы могут ждать диск, память или сеть. Даже load average в Linux учитывает задачи в непрерываемом ожидании I/O, так что читать его как «занятость процессора» опасно.
У Брендана Грегга есть чек-лист USE для Linux. Он предлагает пройтись по каждому ресурсу с тремя вопросами: насколько он з…
Почему Python срочно обновил сразу пять веток
В Python 3.15.2, 3.14.10, 3.13.18, 3.12.16 и 3.11.18 добавили блокировку скомпрометированных ключей промежуточных CA eMudhra в ssl. Это дополнительная защита на уровне интерпретатора. Она распространяется и на обычные операции pip, включая обновление самого pip, даже если установленная версия менеджера пакетов старая.
В том же срочном выпуске исправили обход tarfile.tar…
Новый уровень ИТ-практик: Импульс Т1 снова в Москве 🚀
19 ноября столица примет ИТ-конференцию Импульс Т1. Мы создаём среду, где специалисты получают не просто полезную информацию, а рабочие инструменты, применимые в проектах уже на следующий день.
Импульс Т1 2026 — это:
🔹5 направлений деловой программы;
🔹130+ экспертных спикеров;
🔹70+ прикладных активностей;
🔹2 000+ участников сообщества.
Уникальный формат — учимс…
Управление GPU-кластерами можно попробовать без GPU
У NVIDIA есть NVKE — управляющий слой для Kubernetes-кластеров на серверах с GPU NVIDIA. Жизненным циклом кластеров можно управлять через API и nvkectl. Познакомиться с устройством системы можно без видеокарты, на симулированных машинах.
Для такого стенда нужны Linux или виртуалка, 6 CPU, 12 ГиБ свободной RAM, 100 ГиБ диска, Docker и виртуальный TPM.
NVKE пока в …
GitHub заменит имя enterprise на slug в событиях аудита
12 ноября поле business в событиях secret scanning начнёт содержать slug enterprise вместо отображаемого имени. Тип останется строкой, названия событий тоже прежние. То есть обработчик может успешно разобрать JSON и при этом перестать узнавать нужную организацию.
Изменение касается событий secret_scanning_alert.* и secret_scanning_push_protection.bypass. Если …
Где учиться на инженера, если хочется с первых курсов работать с реальным железом и связью? Рассказываем, какие вузы запустили программы вместе с индустрией. В МФТИ готовят разработчиков микропроцессоров и специалистов по беспроводным сетям, в МИЭТ — инженеров по RTL-проектированию и верификации на RISC-V, в ИТМО — экспертов по компиляторам, фаззингу и беспроводным технологиям. В СибГУТИ учат писать ПО для 4G и 5G, а…
Спокойное море героя не воспитает
Одиссей хотел услышать пение сирен и услышал. Но сначала велел команде привязать его к мачте, чтобы не свернуть с курса. Любое большое внедрение устроено похоже: голосов вокруг много, и каждый хочет чего-то своего.
На ИТ-Одиссее Евгений Зубков, начальник управления развития ИИ-решений и внешних партнёрств Альфа-Банка, расскажет, как провести масштабный ИТ-проект через бурю и не пот…
Маленькая модель пишет черновик для большой
Маленькая модель может накидать несколько токенов, а большая — проверить весь блок одним проходом.
В разборе Hugging Face 2023 года разобран случай с greedy-декодированием. Пока варианты совпадают с выбором большой модели, префикс принимается. На первом расхождении берут токен большой модели, а оставшийся черновой хвост отбрасывают: он продолжал последовательность с други…
Трассу можно расспрашивать через SQL
Записать побольше событий — ещё не значит понять, почему программа тормозит. Формат трассы рассчитан на быструю запись с небольшими накладными расходами. Для анализа эти данные ещё нужно разобрать и связать.
В Perfetto этим занимается Trace Processor. Он читает трассы в форматах Perfetto, ftrace и Chrome JSON, структурирует события и даёт запрашивать их через PerfettoSQL. Найден…
Изменения в бэкапе есть, нужной точки восстановления уже нет
Litestream может сохранить изменение, но со временем потерять возможность восстановить базу ровно до него.
В описании v0.5 страницы SQLite WAL собираются в файлы LTX. Один такой пакет может содержать несколько транзакций SQLite. Его TXID — идентификатор пакета, а не каждой прикладной транзакции.
При восстановлении берут подходящий snapshot и применяют це…
Для восстановления файла не обязательно держать его копию
Backblaze в разборе Reed–Solomon 2015 года описала схему 17+3. Файл делят на 17 равных фрагментов данных и вычисляют ещё три фрагмента избыточности. Всего 20, а для восстановления достаточно любых 17.
Здесь нет двадцати полных копий. Дополнительные фрагменты получаются из исходных через кодирование. Когда часть потерялась, оставшиеся дают достаточно информац…
QOI экономит ещё и на сложности кодека
Разработчик Доминик Шаблевски разбирался с упрощением видеокодека, а в итоге придумал lossless-формат для картинок — Quite OK Image Format. Занятно свернул.
QOI проходит RGB/RGBA-пиксели по порядку за один проход. Повторился предыдущий — запишем повтор. Цвет уже есть в индексе на 64 позиции — сошлёмся на него. Изменился ненамного — сохраним разницу. Не подошло ничего — положим…
🏆7🤔7👏5🎉4👍4👌3👎2🔥2
Showing the 12 most recent of 331 posts we hold for @tproger. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Posts recorded as deleted after publishing
We recorded 11 posts on @tproger 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
9 August 2026
Most recent seen missing
2 November 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
3
Polls
The 6 most recent of 7 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%
Описание задачи27%
Документацию14%
Результаты работы17%
Настройки и контекст: историю чатов, промпты, скиллы19%
Ничего, использую один инструмент51%
The shares total 145%, 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.
Приходится ли вам копипастить данные и какие именно, когда переходите из одной нейросети в другую?
Код17%
Описание задачи28%
Документацию13%
Результаты работы19%
Настройки и контекст: историю чатов, промпты, скиллы18%
Ничего, использую один инструмент53%
The shares total 148%, 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.
Открываете видео. В одном варианте оно начинается сразу, а изображение постепенно становится чётче. В другом — нужно подождать три секунды, зато картинка будет чёткой с первого кадра.
Как вам удобнее?
Начать сразу, чёткость подстроится.25%
Подождать три секунды ради чёткой картинки.45%
Зависит от того, что смотрю.23%
Для меня особой разницы нет.6%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is 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 331 most recent posts we hold, published 27 July 2026 to 11 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 10 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.
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
1
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
1
vacant every time we have ever looked
@tproger named 1 handle 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.
@ternlight 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.
Кинопоиск | Фильмы и сериалы @kinopoisk · 794,552#95
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.
Zen of Python @zen_of_python · 18,630 Telegram ranks this channel #1 of 91 here — alongside 90 others — read 5 October 2026
Веб-страница @tproger_web · 22,155 Telegram ranks this channel #1 of 96 here — alongside 95 others — read 20 September 2026
IT Юмор @ithumor · 60,047 Telegram ranks this channel #1 of 94 here — alongside 93 others — read 22 August 2026
Библиотека программиста @proglibrary · 77,612 Telegram ranks this channel #1 of 82 here — alongside 81 others — read 19 August 2026
Уголок программиста @conhum · 20,441 Telegram ranks this channel #3 of 89 here — alongside 88 others — read 26 September 2026
Журнал «Код» @thecodemedia · 48,864 Telegram ranks this channel #3 of 97 here — alongside 96 others — read 25 August 2026
Хабр @habr_com · 134,497 Telegram ranks this channel #7 of 92 here — alongside 91 others — read 13 August 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js @frontendproglib · 20,611 Telegram ranks this channel #10 of 93 here — alongside 92 others — read 25 September 2026
TechNews @techlucker · 42,607 Telegram ranks this channel #10 of 79 here — alongside 78 others — read 28 August 2026
[404] — программирование @procode404 · 40,060 Telegram ranks this channel #11 of 83 here — alongside 82 others — read 30 August 2026
BZD • Книги для программистов @bzd_channel · 36,213 Telegram ranks this channel #12 of 57 here — alongside 56 others — read 1 September 2026
Библиотека питониста | Python, Django, Flask @pyproglib · 36,965 Telegram ranks this channel #12 of 84 here — alongside 83 others — read 1 September 2026
Английский для программиста | EnglishScript @EnglishScript · 44,353 Telegram ranks this channel #13 of 82 here — alongside 81 others — read 27 August 2026
FrontEndDev @front_end_dev · 25,428 Telegram ranks this channel #16 of 95 here — alongside 94 others — read 13 September 2026
hahacker_news @hahacker_news · 25,231 Telegram ranks this channel #20 of 59 here — alongside 58 others — read 14 September 2026
АйТиБорода @itbeard · 19,001 Telegram ranks this channel #22 of 93 here — alongside 92 others — read 3 October 2026
медиатрендс @mediatrends · 594,657 Telegram ranks this channel #23 of 90 here — alongside 89 others — read 13 September 2026
Physics.Math.Code @physics_lib · 146,676 Telegram ranks this channel #23 of 72 here — alongside 71 others — read 13 August 2026
Programmer memes @programmer_memes · 50,517 Telegram ranks this channel #25 of 96 here — alongside 95 others — read 24 August 2026
Хабр Карьера @habr_career · 33,749 Telegram ranks this channel #26 of 97 here — alongside 96 others — read 4 September 2026
Хауди Хо - IT юмор, жизнь программиста @howdyho_official · 77,428 Telegram ranks this channel #26 of 90 here — alongside 89 others — read 18 August 2026
The ExtremeCode Times @extremecode · 35,846 Telegram ranks this channel #27 of 93 here — alongside 92 others — read 2 September 2026
Python Academy @python_academy · 43,823 Telegram ranks this channel #27 of 87 here — alongside 86 others — read 28 August 2026
Programmer & IT Memes @itmemes · 121,903 Telegram ranks this channel #27 of 95 here — alongside 94 others — read 13 August 2026
This channel appears in 73 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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Типичный программист” (@tproger), 78,009 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/tproger.
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.