Telegram RegisterThe public register of Telegram
Telegram profile photo for Типичный программист

Channel

Типичный программист

@tproger

Verified by Telegram2 usernames

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

78,009subscribers

-1,058 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001044298783
TypeChannel
Usernames@tproger @tproger_official
DescriptionВсё самое интересное по программированию Разместить рекламу: @tproger_sales_bot Правила общения: https://tprg.ru/rules Другие каналы: @tproger_channels Сайт: https://tprg.ru/site VK: vk.com/tproger Регистрация в перечне РКН: https://tprg.ru/mJwo
Created11 March 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held129
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/tproger

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 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)
Posted firstThenOverlapGap
@tproger_web/639110 Aug 2026, 16:42 UTC@tproger/14690 · this entry11 Aug 2026, 19:32 UTC1.0027 hours
@tproger_web/64452 Sept 2026, 13:49 UTC@tproger/14769 · this entry2 Sept 2026, 16:56 UTC1.003.1 hours
@ithumor/1566510 Aug 2026, 18:02 UTC@tproger/14697 · this entry14 Aug 2026, 07:03 UTC1.004 days
@tproger/14679 · this entry10 Aug 2026, 16:35 UTC@ithumor/1566811 Aug 2026, 14:02 UTC1.0021 hours
@tproger/14690 · this entry11 Aug 2026, 19:32 UTC@ithumor/1567111 Aug 2026, 19:33 UTC1.00under a minute
@ithumor/1567412 Aug 2026, 14:27 UTC@tproger/14695 · this entry13 Aug 2026, 15:39 UTC1.0025 hours
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
ChannelMatching postsText overlapTypical gapPublished first
@tproger_web17 (8/8 hand-verifiable sample passed)1.004.3 hours@tproger_web (9–8)
@ithumor7 (7/7 hand-verifiable sample passed)1.0024 hoursthis entry (4–3)
@your_tech5 (5/5 hand-verifiable sample passed)1.0069 minutes@your_tech (4–1)

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.

Growth

77,96779,13978,55378,0095 August 202610 November 2026
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)SubscribersChange
10 Nov 2026, 17:5678,009-2
10 Nov 2026, 16:3778,011+21
9 Nov 2026, 01:4177,990no change
9 Nov 2026, 00:4177,990-25
7 Nov 2026, 16:1878,015no change
7 Nov 2026, 15:4778,015-2
6 Nov 2026, 17:0878,017+15
6 Nov 2026, 11:3678,002-4
5 Nov 2026, 14:1678,006-5
5 Nov 2026, 10:3878,011-2
4 Nov 2026, 16:1678,013+4
4 Nov 2026, 10:2678,009+8
3 Nov 2026, 12:3978,001-3
3 Nov 2026, 09:4778,004+8
2 Nov 2026, 15:1077,996+4
2 Nov 2026, 10:5977,992no change
1 Nov 2026, 15:2877,992-8
1 Nov 2026, 10:5678,000-8
31 Oct 2026, 18:3978,008+6
31 Oct 2026, 12:0678,002first 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
WindowRolling 30 days · latest post in window 11 November 2026
Posts held331 (27 July 2026 – 11 November 2026)
Views total607,920
Reactions total2,530
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 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
ReactionCountShareShare, drawn
👍1,81915.9%
❤1,67714.7%
🔥1,0679.33%
😁7406.47%
👏5945.19%
🤣4253.72%
🤔4103.58%
🎉4023.51%
💯3382.96%
💊3372.95%
👎2061.80%
👌1671.46%
🤝1531.34%
✍1351.18%
🌚1251.09%
⚡1201.05%
🤯1151.01%
🤩960.839%
👀920.804%
🙈920.804%
45 further kinds2,32720.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
eridPostsFirst seenLast seen
2W5zFJrVGHw124 September 202624 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).

11 Nov 2026, 11:04 UTC≈2,600 views15 reactionsread 11 November 2026

Процессор не загружен, а сервер всё равно тормозит Низкая загрузка CPU ещё не означает, что у сервера есть свободные ресурсы. Запросы могут ждать диск, память или сеть. Даже load average в Linux учитывает задачи в непрерываемом ожидании I/O, так что читать его как «занятость процессора» опасно. У Брендана Грегга есть чек-лист USE для Linux. Он предлагает пройтись по каждому ресурсу с тремя вопросами: насколько он з…

👍7🎉2❤1🌭1👌1🔥1🤗1🙈1

11 Nov 2026, 04:42 UTC≈4,310 views27 reactionsread 11 November 2026

Почему Python срочно обновил сразу пять веток В Python 3.15.2, 3.14.10, 3.13.18, 3.12.16 и 3.11.18 добавили блокировку скомпрометированных ключей промежуточных CA eMudhra в ssl. Это дополнительная защита на уровне интерпретатора. Она распространяется и на обычные операции pip, включая обновление самого pip, даже если установленная версия менеджера пакетов старая. В том же срочном выпуске исправили обход tarfile.tar…

⚡7🙊5😍4🎉3💅2🐳1👀1🤷1

10 Nov 2026, 14:02 UTC≈4,940 views26 reactionsread 11 November 2026
Photo

Новый уровень ИТ-практик: Импульс Т1 снова в Москве 🚀 19 ноября столица примет ИТ-конференцию Импульс Т1. Мы создаём среду, где специалисты получают не просто полезную информацию, а рабочие инструменты, применимые в проектах уже на следующий день. Импульс Т1 2026 — это: 🔹5 направлений деловой программы; 🔹130+ экспертных спикеров; 🔹70+ прикладных активностей; 🔹2 000+ участников сообщества. Уникальный формат — учимс…

💊7🔥4🆒3💋2💔2😎2😨2☃1

10 Nov 2026, 10:47 UTC≈4,980 views27 reactionsread 11 November 2026
Photo

Управление GPU-кластерами можно попробовать без GPU У NVIDIA есть NVKE — управляющий слой для Kubernetes-кластеров на серверах с GPU NVIDIA. Жизненным циклом кластеров можно управлять через API и nvkectl. Познакомиться с устройством системы можно без видеокарты, на симулированных машинах. Для такого стенда нужны Linux или виртуалка, 6 CPU, 12 ГиБ свободной RAM, 100 ГиБ диска, Docker и виртуальный TPM. NVKE пока в …

👍7🔥5✍2🍾2🎄2🐳2🤷2😱2

10 Nov 2026, 05:19 UTC≈5,440 views25 reactionsread 11 November 2026

GitHub заменит имя enterprise на slug в событиях аудита 12 ноября поле business в событиях secret scanning начнёт содержать slug enterprise вместо отображаемого имени. Тип останется строкой, названия событий тоже прежние. То есть обработчик может успешно разобрать JSON и при этом перестать узнавать нужную организацию. Изменение касается событий secret_scanning_alert.* и secret_scanning_push_protection.bypass. Если …

🤔6❤4🔥4🎅3🌚2⚡1❤‍🔥1🤷‍♀1

9 Nov 2026, 14:10 UTC≈5,870 views29 reactions3 Starsread 11 November 2026
Photo

Где учиться на инженера, если хочется с первых курсов работать с реальным железом и связью? Рассказываем, какие вузы запустили программы вместе с индустрией. В МФТИ готовят разработчиков микропроцессоров и специалистов по беспроводным сетям, в МИЭТ — инженеров по RTL-проектированию и верификации на RISC-V, в ИТМО — экспертов по компиляторам, фаззингу и беспроводным технологиям. В СибГУТИ учат писать ПО для 4G и 5G, а…

❤13😘4🍓2😁2🆒2⚡1🤩1🤪1

9 Nov 2026, 12:02 UTC≈6,190 views27 reactionsread 11 November 2026
Photo

Спокойное море героя не воспитает Одиссей хотел услышать пение сирен и услышал. Но сначала велел команде привязать его к мачте, чтобы не свернуть с курса. Любое большое внедрение устроено похоже: голосов вокруг много, и каждый хочет чего-то своего. На ИТ-Одиссее Евгений Зубков, начальник управления развития ИИ-решений и внешних партнёрств Альфа-Банка, расскажет, как провести масштабный ИТ-проект через бурю и не пот…

👍8🤔6❤3🔥3👀1💅1💋1🕊1

9 Nov 2026, 10:52 UTC≈5,470 views19 reactionsread 11 November 2026
Photo

Маленькая модель пишет черновик для большой Маленькая модель может накидать несколько токенов, а большая — проверить весь блок одним проходом. В разборе Hugging Face 2023 года разобран случай с greedy-декодированием. Пока варианты совпадают с выбором большой модели, префикс принимается. На первом расхождении берут токен большой модели, а оставшийся черновой хвост отбрасывают: он продолжал последовательность с други…

👏5🔥4🎉3❤2👍2⚡1🤯1😭1

9 Nov 2026, 05:02 UTC≈5,580 views28 reactionsread 11 November 2026
Photo

Трассу можно расспрашивать через SQL Записать побольше событий — ещё не значит понять, почему программа тормозит. Формат трассы рассчитан на быструю запись с небольшими накладными расходами. Для анализа эти данные ещё нужно разобрать и связать. В Perfetto этим занимается Trace Processor. Он читает трассы в форматах Perfetto, ftrace и Chrome JSON, структурирует события и даёт запрашивать их через PerfettoSQL. Найден…

🎉7❤6👍5👎3🔥3🍌1🤔1🤷‍♂1

8 Nov 2026, 11:14 UTC≈5,800 views34 reactionsread 11 November 2026
Photo

Изменения в бэкапе есть, нужной точки восстановления уже нет Litestream может сохранить изменение, но со временем потерять возможность восстановить базу ровно до него. В описании v0.5 страницы SQLite WAL собираются в файлы LTX. Один такой пакет может содержать несколько транзакций SQLite. Его TXID — идентификатор пакета, а не каждой прикладной транзакции. При восстановлении берут подходящий snapshot и применяют це…

❤9👍8👏4🔥4👾2🤩2🌭1💋1

8 Nov 2026, 04:59 UTC≈5,780 views37 reactionsread 11 November 2026
Photo

Для восстановления файла не обязательно держать его копию Backblaze в разборе Reed–Solomon 2015 года описала схему 17+3. Файл делят на 17 равных фрагментов данных и вычисляют ещё три фрагмента избыточности. Всего 20, а для восстановления достаточно любых 17. Здесь нет двадцати полных копий. Дополнительные фрагменты получаются из исходных через кодирование. Когда часть потерялась, оставшиеся дают достаточно информац…

👍11❤6🤔5😇3👏2👾2💋2🤝2

7 Nov 2026, 10:50 UTC≈6,040 views39 reactionsread 11 November 2026
Photo

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.

14 Oct 2026, 07:05 UTCAnonymous Poll1,980 voters approx.

Приходится ли вам копипастить данные и какие именно, когда переходите из одной нейросети в другую?

  1. Код17%
  2. Описание задачи27%
  3. Документацию14%
  4. Результаты работы17%
  5. Настройки и контекст: историю чатов, промпты, скиллы19%
  6. Ничего, использую один инструмент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.

13 Oct 2026, 16:32 UTCAnonymous Poll559 voters

Вебинар в прямом эфире уже идёт десять минут. Вы только открыли трансляцию. Что для вас важнее всего?

  1. Минимальная задержка от живого момента.13%
  2. Стабильное разрешение картинки.10%
  3. Ровный звук.14%
  4. Возможность отмотать назад и вернуться в эфир.62%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

11 Oct 2026, 16:50 UTCAnonymous Poll1,380 voters approx.

Если приходилось уходить с одного ИИ-инструмента на другой, что стало главной причиной?

  1. Качество ответов и кода стало не устраивать29%
  2. Упёрся в лимиты или не хватает функций14%
  3. Цены кусаются10%
  4. Проблемы с доступом: блокировки, нужен VPN17%
  5. Сложности с оплатой3%
  6. Стало неудобно работать3%
  7. Не менял инструмент — сижу на привычном23%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

9 Oct 2026, 13:11 UTCAnonymous Poll1,390 voters approx.

Где вы чаще всего работаете с ИИ-инструментом?

  1. В отдельном окне чата или веб-версии34%
  2. Прямо в редакторе кода20%
  3. В терминале26%
  4. Через корпоративные сервисы или платформы2%
  5. По-разному, зависит от того, что нужно сделать18%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

7 Oct 2026, 12:23 UTCAnonymous Poll264 voters

Приходится ли вам копипастить данные и какие именно, когда переходите из одной нейросети в другую?

  1. Код17%
  2. Описание задачи28%
  3. Документацию13%
  4. Результаты работы19%
  5. Настройки и контекст: историю чатов, промпты, скиллы18%
  6. Ничего, использую один инструмент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.

3 Oct 2026, 15:33 UTCAnonymous Poll496 voters

Открываете видео. В одном варианте оно начинается сразу, а изображение постепенно становится чётче. В другом — нужно подождать три секунды, зато картинка будет чёткой с первого кадра. Как вам удобнее?

  1. Начать сразу, чёткость подстроится.25%
  2. Подождать три секунды ради чёткой картинки.45%
  3. Зависит от того, что смотрю.23%
  4. Для меня особой разницы нет.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

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.

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.

IT Юмор
@ithumor · 60,047
#1
Хабр
@habr_com · 134,497
#2
Библиотека программиста
@proglibrary · 77,612
#3
Веб-страница
@tproger_web · 22,155
#4
Rozetked
@rozetked · 646,921
#5
Код.ру
@d_code · 405,458
#6
Представляешь,
@your_tech · 8,575
#7
Programmer & IT Memes
@itmemes · 121,903
#8
Zen of Python
@zen_of_python · 18,630
#9
CodeCamp
@codecamp · 177,529
#10
Инструменты программиста
@prog_tools · 12,863
#11
Мобильная разработка
@mobi_dev · 13,002
#12
Журнал «Код»
@thecodemedia · 48,864
#13
addmeto
@addmeto · 72,001
#14
Точка входа в программирование
@prog_point · 17,850
#15
r/ретранслятор
@retra · 165,761
#16
vc.ru
@vcnews · 112,144
#17
Denis Sexy IT 🤖
@denissexy · 140,753
#18
Programmer memes
@programmer_memes · 50,517
#19
FrontEndDev
@front_end_dev · 25,428
#20
Clean Code
@codeclean · 11,942
#21
The After Times
@theaftertimes · 16,833
#22
Библиотека Go-разработчика | Golang
@goproglib · 23,894
#23
Не баг, а фича
@bugfeature · 551,367
#24
Код найма
@soft_skillz · 5,219
#25
Нейроканал
@neuro_channel · 12,073
#26
Сохранёнки программиста
@prog_stuff · 6,453
#27
Библиотека питониста | Python, Django, Flask
@pyproglib · 36,965
#28
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
#29
Технотренды
@techno_media · 928,461
#30
BZD • Книги для программистов
@bzd_channel · 36,213
#31
Библиотека шарписта | C#, F#, .NET, ASP.NET
@csharpproglib · 21,474
#32
Frontender's notes [ru]
@frontendnoteschannel_ru · 30,750
#33
эйай ньюз
@ai_newz · 98,339
#34
Рестарт
@remedia · 667,251
#35
WebDEV
@webb_dev · 8,209
#36
Яндекс
@yandex · 599,122
#37
Метод утёнка
@devs_books · 6,597
#38
hahacker_news
@hahacker_news · 25,231
#39
Machinelearning
@ai_machinelearning_big_data · 275,659
#40
Хабр Новости
@habr_com_news · 12,588
#41
Neural Shit
@NeuralShit · 54,643
#42
ЗаТелеком 🌐
@zatelecom · 64,510
#43
ТЕХНО: Яндекс про технологии
@techno_yandex · 218,253
#44
XOR
@xor_journal · 195,083
#45
Yandex for Developers
@Yandex4Developers · 28,656
#46
Рабы галерные
@rabynagalerah · 8,650
#47
Двач
@dvachannel · 969,125
#48
Эксплойт
@exploitex · 2,021,350
#49
Говнокод
@g_code · 14,797
#50
Mash
@mash · 3,140,033
#51
Раньше всех. Ну почти.
@bbbreaking · 1,975,436
#52
Ньюсач/Двач
@ru2ch · 710,451
#53
Бэкдор
@whackdoor · 1,538,229
#54
NOP::Nuances of Programming
@nuancesprog · 55,923
#55
Медуза — LIVE
@meduzalive · 1,116,844
#56
Varlamov News
@varlamov_news · 1,058,487
#57
Лентач
@lentachold · 391,507
#58
Пекарня
@pekagame · 1,117,922
#59
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,088,291
#60
THINGS PROGRAMMERS DO
@thingsprogrammersdo · 16,061
#61
Пикабу
@pikabu · 254,915
#62
Лентач
@oldlentach · 262,523
#63
GitHub Community
@github · 154,995
#64
Артемий Лебедев
@temalebedev · 968,108
#65
Reddit
@Reddit · 160,928
#66
Программист
@progeri · 15,013
#67
NN
@naebnet · 2,177,859
#68
Банкста
@banksta · 439,838
#69
Минцифры России
@mintsifry · 232,434
#70
Дудь
@yurydud · 849,220
#71
твиттота
@twitt_ota · 415,877
#72
Лепра
@Lepragram · 340,793
#73
Big Geek
@biggeekru · 601,397
#74
Physics.Math.Code
@physics_lib · 146,676
#75
GameDev: разработка игр
@make_game · 7,595
#76
Yaplakal.com
@yaplakal · 419,820
#77
Go in Action
@go_in_action · 4,057
#78
VG/Двач
@ru2chvg · 183,087
#79
MDK
@mudak · 524,131
#80
Golang
@Golang_google · 40,453
#81
Т-Инвестиции
@tb_invest_official · 521,159
#82
[BadComedian]
@TheBadComedian · 605,041
#83
СТАС БОМБИТ
@ikakprosto · 322,499
#84
Типичный Сисадмин
@sysodmins · 40,818
#85
Библиотека IT-мемов
@itmemlib · 9,429
#86
.NET / C#
@dot_net_c_sharp · 3,806
#87
4chan
@ru4chan · 181,861
#88
Чашечка Java
@a_cup_of_java · 8,285
#89
Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 21,780
#90
Не баг, а фича
@bugnotfeature · 1,162,637
#91
Metanit
@metanit · 7,941
#92
DTF
@dtfbest · 57,966
#93
Утечки информации
@dataleak · 117,675
#94
Кинопоиск | Фильмы и сериалы
@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.