Telegram RegisterThe public register of Telegram
Telegram profile photo for Веб-страница

Channel

Веб-страница

@tproger_web

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

22,155subscribers

-552 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001325963535
TypeChannel
Username@tproger_web
Created14 June 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/tproger_web

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and 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 2 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/6391 · this entry10 Aug 2026, 16:42 UTC@tproger/1469011 Aug 2026, 19:32 UTC1.0027 hours
@tproger_web/6445 · this entry2 Sept 2026, 13:49 UTC@tproger/147692 Sept 2026, 16:56 UTC1.003.1 hours
@tproger_web/6391 · this entry10 Aug 2026, 16:42 UTC@ithumor/1567111 Aug 2026, 19:33 UTC1.0027 hours
@tproger_web/6393 · this entry11 Aug 2026, 14:01 UTC@ithumor/1566811 Aug 2026, 14:02 UTC1.00under a minute
@tproger_web/6397 · this entry12 Aug 2026, 13:02 UTC@ithumor/1567412 Aug 2026, 14:27 UTC1.0085 minutes
@tproger_web/6400 · this entry13 Aug 2026, 10:44 UTC@ithumor/1567713 Aug 2026, 13:48 UTC1.003.1 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
@tproger17 (8/8 hand-verifiable sample passed)1.004.3 hoursthis entry (9–8)
@ithumor7 (7/7 hand-verifiable sample passed)1.002.2 hoursthis entry (5–2)

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. 8 of the 8 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 189 comparable posts for this entry, running 24 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. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, 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

22,15522,70722,4316 August 202611 November 2026
67 measurements spanning 97 days, net -552. 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 22,072–22,790 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
11 Nov 2026, 11:1022,155-9
9 Nov 2026, 15:0822,164-8
8 Nov 2026, 03:4922,172-5
7 Nov 2026, 01:2522,177-9
6 Nov 2026, 03:2622,186-8
5 Nov 2026, 06:4022,194+1
4 Nov 2026, 06:2922,193-4
3 Nov 2026, 05:4522,197-8
2 Nov 2026, 06:4522,205-12
1 Nov 2026, 06:0922,217-8
31 Oct 2026, 07:5422,225-1
30 Oct 2026, 06:3522,226-9
29 Oct 2026, 07:2022,235-7
28 Oct 2026, 04:1722,242-7
27 Oct 2026, 05:1122,249-4
26 Oct 2026, 08:3622,253-8
25 Oct 2026, 10:2922,261-5
24 Oct 2026, 13:2122,266-5
23 Oct 2026, 13:4622,271-6
22 Oct 2026, 12:0622,277first reading

Engagement

204 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 97 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.65%
avg views ÷ 22,155 subscribers
Avg views / post
1,700
37 posts measured
Reaction rate
0.175%
reactions ÷ views · ER floor
Posts in window
37
of 204 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 10 November 2026
Posts held204 (23 July 2026 – 10 November 2026)
Views total62,716
Reactions total110
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 03:04 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.

Reaction mix

921 reactions across 200 posts, in 13 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤27229.5%
👍19020.6%
😁18520.1%
🔥12914.0%
🤣566.08%
🤔313.37%
🫡192.06%
👎141.52%
🤯141.52%
🗿40.434%
🤩30.326%
💩20.217%
🥰20.217%

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

Measured over the 204 most recent posts we hold, published 23 July 2026 to 10 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.

Advertising

Ad load
1.47%
3 of 204 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
1,640
over 3 measured posts
Median views · rest
1,720
over 201 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
2SDnjdSC4XD131 August 202631 August 2026
2VtzqwLN1Md131 August 202631 August 2026
2W5zFHGPF8M16 August 20266 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 204 most recent posts we hold, published 23 July 2026 to 10 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: 0 of 37 posts held from the last 30 days (0%) 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).

10 Nov 2026, 11:03 UTC849 views2 reactionsread 11 November 2026

Область position-area можно выбрать прямо в DevTools Всплывающий блок привязан к якорю, но оказывается не с той стороны кнопки. Перебирать значения position-area в уме необязательно: в Chrome DevTools появился визуальный редактор областей вокруг якоря. Google описывает его в обзоре изменений Chrome 155 и 156, вышедших в stable в октябре. В Elements → Styles нажмите значок рядом с объявлением position-area. В сетке …

👍1🔥1

10 Nov 2026, 05:13 UTC≈1,190 views2 reactionsread 11 November 2026
Photo

Почему Safari затемняет сайт, а JavaScript видит прежние цвета В Safari 27.3 beta пользователь может включить Adaptive Dark Mode для светлого сайта. WebKit меняет яркость фонов и текста, стараясь сохранить оттенки. Большинство картинок и содержимое <canvas> остаются исходными. На сравнении WebKit это видно по графику Interop. Преобразование происходит внутри движка. Запрос цвета через JavaScript возвращает авторско…

👍1🔥1

9 Nov 2026, 11:27 UTC≈1,330 views1 reactionsread 11 November 2026
Photo

hx-sync может отдать отправке формы приоритет над валидацией поля Поле отправило запрос проверки, а пользователь сразу нажал кнопку отправки формы. Два запроса от разных элементов могут выполняться одновременно. В htmx атрибут hx-sync="closest form:abort" на поле связывает его запрос с ближайшей формой. Если запрос формы уже идёт, проверка поля не запускается. Если отправка начинается позже, текущий запрос проверки…

❤1

9 Nov 2026, 05:17 UTC≈1,320 views1 reactionsread 11 November 2026
Photo

write вернул false: дождитесь drain перед следующими порциями Если Writable.write вернул false, приостановите запись новых данных. Уже переданный chunk повторно отправлять не нужно. После такого результата дождитесь drain и только затем продолжайте запись. В стандартной связке Readable.pipe управляет потоком данных автоматически. highWaterMark задаёт порог буферизации, а не жёсткий предел памяти всего приложения. …

🔥1

8 Nov 2026, 11:07 UTC≈1,340 views1 reactionsread 11 November 2026
Photo

scheduler.yield даёт продолжению задачи приоритет перед похожими новыми задачами Если разбить тяжёлую работу через setTimeout, её вторая часть может оказаться после уже поставленных задач. await scheduler.yield() тоже разбивает работу на задачи, но продолжение получает преимущество перед новыми задачами похожего приоритета. Браузер при этом может обработать более приоритетную работу. Параллельного выполнения JavaSc…

🔥1

8 Nov 2026, 05:27 UTC≈1,320 views2 reactionsread 11 November 2026
Photo

Обработчики MSW можно переиспользовать между Node и браузером Описанный в обработчике MSW ответ API можно использовать в разных тестовых средах. Но сами handlers ничего не перехватывают. В Node их передают в setupServer, в браузере — в setupWorker. Затем подмену ответов включают в точке входа выбранного инструмента. В примере для Vitest сервер запускают через listen, после каждого теста вызывают resetHandlers, а по…

🔥2

7 Nov 2026, 11:29 UTC≈1,360 views1 reactionsread 11 November 2026
Photo

server:defer в Astro выносит компонент в отдельный серверный запрос Блок с персональными данными можно загружать отдельно, не задерживая выдачу всей страницы. В Astro компонент с server:defer становится server island. Основная страница сначала приходит с содержимым slot="fallback". Небольшой скрипт запрашивает отдельный endpoint острова и заменяет заглушку полученным HTML. Для отложенного серверного рендеринга нуже…

🔥1

7 Nov 2026, 05:30 UTC≈1,370 views2 reactionsread 11 November 2026
Photo

fastForward и runFor в Playwright по-разному двигают таймеры Пропустить ожидание в тесте и проверить каждый тик таймера — разные задачи. У page.clock для них есть разные методы. setFixedTime фиксирует значения Date, сохраняя естественную работу таймеров. После install можно управлять ходом времени. fastForward похож на закрытие и открытие ноутбука: просроченные таймеры срабатывают по одному разу. runFor проходит ин…

🔥2

6 Nov 2026, 10:57 UTC≈1,460 views2 reactionsread 11 November 2026
Photo

Server-Timing передаёт в браузер метрики, которые измерил сервер Браузер видит начало запроса, ожидание ответа и загрузку. Но по этим данным он не узнает, сколько времени сервер потратил на запрос к базе данных или обработку шаблона. Через Server-Timing бэкенд может передать собственные именованные метрики. В serverTiming у записей навигации и ресурсов доступны name, duration и description. Браузер не вычисляет эти…

❤2

6 Nov 2026, 05:28 UTC≈1,470 views1 reactionsread 11 November 2026
Photo

Что возвращает import.meta.glob в Vite с eager и без него Собрать реестр модулей из папки можно через import.meta.glob. Значения в полученном объекте зависят от режима загрузки. По умолчанию Vite создаёт функции с динамическим импортом. Найденные модули загружаются лениво и при сборке разделяются на чанки. С eager: true импорты становятся статическими, а значения объекта — самими импортированными модулями. Меняется…

🔥1

5 Nov 2026, 11:03 UTC≈1,490 views3 reactionsread 11 November 2026
Photo

Selector Stats помогает разбирать затраты на Recalculate Style По длительности события Recalculate Style в Performance trace ещё нельзя понять, какой селектор стоит менять. Для этого в DevTools есть Selector Stats. До записи включите Enable CSS selector stats, повторите проблемный сценарий и откройте событие пересчёта стилей. Elapsed показывает время сопоставления, Match Attempts — число попыток, Match Count — числ…

👍2🔥1

5 Nov 2026, 05:14 UTC≈1,520 views3 reactionsread 11 November 2026
Photo

Почему RegExp.escape превращает foo-bar в строку с hex-escape Вы собираете регулярное выражение из строки поиска и хотите искать её буквально. RegExp.escape экранирует строку для вставки в шаблон. У foo-bar первая буква превращается в \x66, а дефис — в \x2d. Экранирование первой буквы не даёт ей слиться с предшествующей escape-последовательностью. Для дефиса нужен hex-escape, потому что простой обратный слеш перед …

🔥3

Showing the 12 most recent of 204 posts we hold for @tproger_web. 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 recorded as deleted after publishing

We recorded 2 posts on @tproger_web 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
28 September 2026
Most recent seen missing
10 October 2026
Median time before seen missing
4 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.

9 Oct 2026, 16:25 UTCAnonymous Poll1,370 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.

4 Oct 2026, 14:21 UTCAnonymous Poll107 voters

Отложили видео, а потом вернулись к нему. Вспомните последний такой просмотр: с какого места вы продолжили?

  1. С того места, где остановился.63%
  2. С более раннего момента, в том числе с начала.31%
  3. Перешёл дальше, к нужному фрагменту.3%
  4. Не помню такого просмотра.4%

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

3 Oct 2026, 15:09 UTCAnonymous Poll137 voters

Вспомните последнее видео, которое смотрели на телефоне, когда рядом были другие люди. Как вы его слушали?

  1. В наушниках.57%
  2. Через динамик телефона.15%
  3. Смотрел без звука (или с субтитрами).18%
  4. Не помню такого просмотра.10%

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

2 Oct 2026, 12:23 UTCAnonymous Poll127 voters

Во время видео переключились с Wi-Fi на мобильный интернет. Вспомните последний такой случай: что вы первым делом сделали с качеством изображения?

  1. Оставил настройку как была.59%
  2. Выбрал качество пониже.16%
  3. Выбрал качество повыше.8%
  4. Не помню такого случая.17%

Shares as published. 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 204 most recent posts we hold, published 23 July 2026 to 10 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 3 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.

Типичный программист
@tproger · 78,009
#1
IT Юмор
@ithumor · 60,047
#2
Frontender's notes [ru]
@frontendnoteschannel_ru · 30,770
#3
FrontEndDev
@front_end_dev · 25,428
#4
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
#5
Инструменты программиста
@prog_tools · 12,864
#6
Точка входа в программирование
@prog_point · 17,850
#7
Senior Frontend - javascript, html, css
@seniorFront · 23,475
#8
Библиотека программиста
@proglibrary · 77,612
#9
Rozetked
@rozetked · 646,921
#10
NOP::Nuances of Programming
@nuancesprog · 55,956
#11
WebDEV
@webb_dev · 8,209
#12
Будни разработчика
@htmlshit · 14,341
#13
Programmer & IT Memes
@itmemes · 121,903
#14
Владилен: IT в эпоху AI
@vladm · 39,328
#15
Хабр
@habr_com · 134,497
#16
Node.JS [ru] | Серверный JavaScript
@we_use_js · 10,605
#17
Frontend Головного Мозга
@frontend_mind · 6,228
#18
Yandex for Frontend
@yandex4frontend · 10,816
#19
GitHub Community
@github · 154,995
#20
Представляешь,
@your_tech · 8,575
#21
mefody.dev
@mefody_dev · 5,386
#22
Верстальщик от бога
@godinhtml · 9,189
#23
Сохранёнки программиста
@prog_stuff · 6,453
#24
Frontend | Вопросы собесов
@easy_javascript_ru · 17,284
#25
CodeCamp
@codecamp · 177,629
#26
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
#27
Frontender Libs - обзор библиотек JS / CSS
@sWebDev · 7,338
#28
Clean Code
@codeclean · 11,944
#29
Zen of Python
@zen_of_python · 18,645
#30
Говнокод
@g_code · 14,805
#31
Журнал «Код»
@thecodemedia · 48,864
#32
Веб-стандарты
@webstandards_ru · 13,780
#33
Логово верстальщика
@webdevlair · 7,813
#34
r/ретранслятор
@retra · 165,780
#35
Frontend Interview - собеседования по Javascript / Html / Css
@frontendInterview · 10,249
#36
Фронтендер от бога
@godofjs · 3,367
#37
Web Stack
@web_stack · 4,069
#38
Frontend по-флотски 👨‍💻 | AI & Modern Dev
@frontend_pasta · 4,425
#39
xCode Journal
@xCode_Journal · 13,767
#40
Уставший техдир
@tired_glebmikheev · 18,460
#41
artalog
@artalog · 4,235
#42
Сова пишет…
@sergeysova · 2,983
#43
Мобильная разработка
@mobi_dev · 13,011
#44
Programmer memes
@programmer_memes · 50,542
#45
Настоящий JavaScript
@true_js · 5,793
#46
Frontend Portal
@FrontendPortal · 36,268
#47
GameDev: разработка игр
@make_game · 7,595
#48
Гайды по JavaScript | Программирование
@guides_js · 7,071
#49
JavaScript test
@js_test · 9,582
#50
Javascript jobs — вакансии по фронтенду, джаваскрипт, React, Angular, Vue
@jsdevjob · 9,749
#51
React JS
@react_tg · 16,049
#52
CodePen Amazing
@codepen_amazing · 4,705
#53
Нейроканал
@neuro_channel · 12,073
#54
Заметки про React
@ru_react_notes · 3,381
#55
Javascript
@javascriptv · 16,664
#56
For Web — фронтенд, дизайн, программирование
@forwebdev · 12,960
#57
Не баг, а фича
@bugfeature · 552,118
#58
JavaScript заметки
@notesjs · 7,359
#59
Простой JavaScript
@simple_js · 4,701
#60
Библиотека пхпшника | PHP, Laravel, Symfony, CodeIgniter
@phpproglib · 10,432
#61
Макеты для верстки
@figma2html · 44,399
#62
Технотренды
@techno_media · 928,461
#63
Laravel World
@laravel_it · 7,982
#64
Код найма
@soft_skillz · 5,219
#65
Катерина | Про Frontend
@katerina_profrontend · 2,799
#66
XOR
@xor_journal · 195,549
#67
Frontend разработчик
@frontend_1 · 10,262
#68
melikhov.dev
@melikhov_dev · 4,760
#69
Denis Sexy IT 🤖
@denissexy · 140,753
#70
Метод утёнка
@devs_books · 6,607
#71
Yandex for Developers
@Yandex4Developers · 28,656
#72
vc.ru
@vcnews · 112,144
#73
The ExtremeCode Times
@extremecode · 35,840
#74
JavaScript задачи с собеседований
@javascriptquiz · 4,577
#75
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,423
#76
WebCraft - ремесло веб разработки
@web_craft · 4,967
#77
BZD • Книги для программистов
@bzd_channel · 36,213
#78
Vue-FAQ
@vuefaq · 856
#79
Фронтенд Гайд
@frontendGA · 7,650
#80
UX Live 🔥
@uxlive · 36,198
#81
JavaScript | LeetCode
@easy_frontend_task · 8,179
#82
Двач
@dvachannel · 969,331
#83
Эксплойт
@exploitex · 2,022,997
#84
Бэкдор
@whackdoor · 1,538,229
#85
Код.ру
@d_code · 405,444
#86
Ньюсач/Двач
@ru2ch · 710,451
#87
Пекарня
@pekagame · 1,117,922
#88
ВИЛСАКОМ РЕД / WYLSACOM RED
@wylsared · 1,088,291
#89
NOP::Humor
@nophumor · 7,522
#90
codepen.js
@codepen_js · 8,706
#91
THINGS PROGRAMMERS DO
@thingsprogrammersdo · 16,061
#92
VG/Двач
@ru2chvg · 183,087
#93
Frontend Info
@frontend_info · 5,247
#94
Рестарт
@remedia · 667,251
#95
Лентач
@oldlentach · 262,523
#96

Read from Telegram’s recommendation API, most recently 20 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js
@frontendproglib · 20,611
Telegram ranks this channel #4 of 93 here — alongside 92 others — read 25 September 2026
Типичный программист
@tproger · 78,009
Telegram ranks this channel #4 of 95 here — alongside 94 others — read 19 August 2026
FrontEndDev
@front_end_dev · 25,428
Telegram ranks this channel #5 of 95 here — alongside 94 others — read 13 September 2026
Frontender's notes [ru]
@frontendnoteschannel_ru · 30,770
Telegram ranks this channel #8 of 95 here — alongside 94 others — read 6 September 2026
NOP::Nuances of Programming
@nuancesprog · 55,956
Telegram ranks this channel #8 of 84 here — alongside 83 others — read 23 August 2026
Senior Frontend Developer | JavaScript, React, HTML & CSS
@senior_front · 18,893
Telegram ranks this channel #10 of 90 here — alongside 89 others — read 2 October 2026
Senior Frontend - javascript, html, css
@seniorFront · 23,475
Telegram ranks this channel #10 of 89 here — alongside 88 others — read 17 September 2026
Журнал «Код»
@thecodemedia · 48,864
Telegram ranks this channel #10 of 97 here — alongside 96 others — read 25 August 2026
IT Юмор
@ithumor · 60,047
Telegram ranks this channel #10 of 94 here — alongside 93 others — read 22 August 2026
Zen of Python
@zen_of_python · 18,645
Telegram ranks this channel #12 of 91 here — alongside 90 others — read 5 October 2026
Владилен: IT в эпоху AI
@vladm · 39,328
Telegram ranks this channel #16 of 96 here — alongside 95 others — read 30 August 2026
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг
@sitodel · 25,423
Telegram ranks this channel #21 of 89 here — alongside 88 others — read 13 September 2026
[404] — программирование
@procode404 · 40,080
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 30 August 2026
Библиотека программиста
@proglibrary · 77,612
Telegram ranks this channel #29 of 82 here — alongside 81 others — read 19 August 2026
FrontEnd Development
@fedevelopment · 28,445
Telegram ranks this channel #32 of 88 here — alongside 87 others — read 9 September 2026
Макеты для верстки
@figma2html · 44,399
Telegram ranks this channel #39 of 90 here — alongside 89 others — read 27 August 2026
Porscode | CMD
@porscode_tg · 28,099
Telegram ranks this channel #45 of 77 here — alongside 76 others — read 9 September 2026
Python Academy
@python_academy · 43,823
Telegram ranks this channel #47 of 87 here — alongside 86 others — read 28 August 2026
Code Ready | Frontend
@code_ready · 21,534
Telegram ranks this channel #64 of 89 here — alongside 88 others — read 23 September 2026
Frontend Portal
@FrontendPortal · 36,268
Telegram ranks this channel #64 of 90 here — alongside 89 others — read 1 September 2026
Front End World
@front_end_first · 25,604
Telegram ranks this channel #67 of 90 here — alongside 89 others — read 13 September 2026

This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 11 November 2026 — this entry's latest reading, not the date you are reading this.

“Веб-страница” (@tproger_web), 22,155 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/tproger_web.

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.