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 why it has no browse page of its own yet.
Growth
49 measurements spanning 79 days, net -436. 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,206–22,772 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)
Subscribers
Change
23 Oct 2026, 13:46
22,271
-6
22 Oct 2026, 12:06
22,277
-8
21 Oct 2026, 06:27
22,285
-6
20 Oct 2026, 04:20
22,291
-4
19 Oct 2026, 06:54
22,295
+1
18 Oct 2026, 08:15
22,294
-3
17 Oct 2026, 10:50
22,297
-8
16 Oct 2026, 12:28
22,305
-7
15 Oct 2026, 14:04
22,312
-8
14 Oct 2026, 13:37
22,320
-7
13 Oct 2026, 04:21
22,327
-26
8 Oct 2026, 22:40
22,353
-20
4 Oct 2026, 14:18
22,373
-56
26 Sept 2026, 05:20
22,429
-30
19 Sept 2026, 08:36
22,459
-15
16 Sept 2026, 21:18
22,474
-8
14 Sept 2026, 23:21
22,482
-10
13 Sept 2026, 07:15
22,492
-23
11 Sept 2026, 09:41
22,515
-5
8 Sept 2026, 18:16
22,520
first reading
Engagement
168 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 80 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
7.31%
avg views ÷ 22,271 subscribers
Avg views / post
1,630
69 posts measured
Reaction rate
0.155%
reactions ÷ views · ER floor
Posts in window
69
of 168 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 12 October 2026
Posts held
168 (23 July 2026 – 12 October 2026)
Views total
112,317
Reactions total
174
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Oct 2026, 20:21 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
815 reactions across 164 posts, in 13 distinct kinds. The most used accounts for 29.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
240
29.4%
😁
181
22.2%
👍
159
19.5%
🔥
92
11.3%
🤣
56
6.87%
🤔
29
3.56%
🫡
19
2.33%
👎
14
1.72%
🤯
14
1.72%
🗿
4
0.491%
🤩
3
0.368%
💩
2
0.245%
🥰
2
0.245%
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 168 of the 168 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 851 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 168 most recent posts we hold, published 23 July 2026 to 12 October 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.79%
3 of 168 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,680
over 165 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
2SDnjdSC4XD
1
31 August 2026
31 August 2026
2VtzqwLN1Md
1
31 August 2026
31 August 2026
2W5zFHGPF8M
1
6 August 2026
6 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 168 most recent posts we hold, published 23 July 2026 to 12 October 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.
Gran Turismo 4 переехала в Chrome — с гонками, звуком и сохранениями
В PS2 Web Recomp старые игры запускают прямо во вкладке. Gran Turismo 4 проходит меню и гонки, играет музыку и сохраняет прогресс в браузере. По замерам автора, PAL-версия держит 50 FPS в Chrome на встроенной графике ноутбука при удвоенном разрешении PS2.
Машинный код игры заранее переводят в C++, затем собирают в WebAssembly. Графику рисует WebGP…
Как плавно переставлять карточки Grid при изменении ширины
Когда число колонок меняется, карточки обычно прыгают на новые места. Брамус показал вариант на CSS Anchor Positioning и обычных transitions: видимое содержимое привязывается к обёртке, которая занимает ячейку Grid.
Обёртка получает anchor-name и anchor-scope, содержимое позиционируется абсолютно через inset: anchor(inside). Переход для inset сглаживает сме…
Перелистывание веб-журнала можно собрать из живого HTML
Эффект загиба страницы обычно рисуют через Canvas или WebGL. Если содержимое превращается в картинку, выделение текста и работа ссылок требуют отдельного решения. В эксперименте с `<hic-pageflip>` автор использует HTML-in-Canvas, чтобы передать живые DOM-элементы в графику.
Внутри компонента страницы задаются тегами <hic-pageflip-page>. Для объёмного загиба ис…
🧑💻 Какие навыки помогают вам в разработке в 2026 году?
Что вы чаще используете в работе? В каких задачах помогает ИИ, а где проще справиться самостоятельно?
Мы решили собрать портрет современного разработчика — и приглашаем вас поделиться своим опытом. Расскажите, какие навыки вам пригодились и как вы используете ИИ. Если обходите его стороной, нам тоже интересно узнать почему.
Опрос анонимный и займёт около 5 ми…
Часть запросов можно обработать без запуска Service Worker
Service Worker умеет отдавать ресурсы из кеша, но его запуск тоже занимает время. Если маршрут заранее известен, не обязательно поднимать обработчик только для решения «сеть или кеш».
Static Routing API позволяет зарегистрировать правила через InstallEvent.addRoutes() во время установки воркера. Для подходящих запросов браузер использует заданный маршрут и …
Vitest 5 помогает выяснить, куда уходит время тестового прогона
Медленный запуск не всегда означает медленные проверки. Основное время может занимать создание окружения, импорт модулей или преобразование файлов. В Vitest 5 разбивка длительности показывает доли этих этапов, а vitest doctor запускает набор с альтернативными конфигурациями и предлагает варианты ускорения.
Для Browser Mode появился Trace View: он запис…
Shopify начал отправлять HTML до завершения рендеринга страницы
Раньше браузер ждал, пока сервер соберёт и head, и остальные секции шаблона. Теперь подходящие Liquid-страницы отправляют начало документа сразу: браузер уже ищет стили и шрифты, пока сервер продолжает готовить содержимое.
У медианного магазина TTFB на 75-м перцентиле снизился примерно на 29%. Видимые метрики FCP и LCP улучшились скромнее: на 2–6%. Ран…
Почему мобильная клавиатура прячет панель с position: fixed
Когда открывается клавиатура, браузер может уменьшить только видимую область страницы. Область, относительно которой рассчитывается вёрстка, остаётся прежней, и закреплённая снизу панель оказывается под клавиатурой.
Директива interactive-widget=resizes-content в viewport meta позволяет уменьшать обе области. Пример: <meta name="viewport" content="width=dev…
Почему сотни маленьких JS-чанков тоже могут замедлять сайт
Один большой бандл заставляет каждую страницу скачивать код всего приложения. Отдельный бандл на маршрут дублирует общие компоненты. Если же разнести каждый модуль в свой файл, браузер получит сотни запросов, а сжатие будет хуже находить повторяющиеся фрагменты.
Команда Next.js разобрала, как Turbopack выбирает между этими расходами. Он учитывает группы чан…
Диаграмму Mermaid можно положить прямо в HTML
Для схемы запросов или графа зависимостей часто хватает нескольких строк Mermaid. Компонент `<mermaid-element>` позволяет поместить этот текст в HTML: подключаете модуль, добавляете тег и записываете внутри описание диаграммы.
По умолчанию компонент загружает Mermaid через jsDelivr по требованию и рисует схему в Shadow DOM. Несколько диаграмм на странице используют одну…
Как добавить в поиск фильтры вида author: и year:
В поиске GitHub обычный текст соседствует с фильтрами ключ:значение. Веб-компонент `<rich-input>` переносит этот шаблон на свой сайт: подсказывает названия фильтров и допустимые значения, подсвечивает структуру запроса и отмечает неверный ввод.
Настройки задаются через вложенные <datalist>. Компонент участвует в обычной отправке формы и работает с FormData, поэтому …
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🤔1
Showing the 12 most recent of 168 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.
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.
Во время видео переключились с Wi-Fi на мобильный интернет. Вспомните последний такой случай: что вы первым делом сделали с качеством изображения?
Оставил настройку как была.59%
Выбрал качество пониже.16%
Выбрал качество повыше.8%
Не помню такого случая.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 168 most recent posts we hold, published 23 July 2026 to 12 October 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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
5
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
4
vacant every time we have ever looked
@tproger_web named 5 handles 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@reactuses named in 4 posts, 23 August 2026 – 29 August 2026 · confirmed gone 4 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@supports named in 4 posts, 29 August 2026 – 29 September 2026
@property named in 3 posts, 4 October 2026 – 6 October 2026
@ternlight named in 3 posts, 8 August 2026 – 12 August 2026
@ambientcss named in 2 posts, 3 September 2026 – 4 September 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.
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,734 Telegram ranks this channel #4 of 93 here — alongside 92 others — read 25 September 2026
Типичный программист @tproger · 78,018 Telegram ranks this channel #4 of 95 here — alongside 94 others — read 19 August 2026
FrontEndDev @front_end_dev · 25,631 Telegram ranks this channel #5 of 95 here — alongside 94 others — read 13 September 2026
Frontender's notes [ru] @frontendnoteschannel_ru · 30,987 Telegram ranks this channel #8 of 95 here — alongside 94 others — read 6 September 2026
NOP::Nuances of Programming @nuancesprog · 56,141 Telegram ranks this channel #8 of 84 here — alongside 83 others — read 23 August 2026
Senior Frontend Developer | JavaScript, React, HTML & CSS @senior_front · 19,069 Telegram ranks this channel #10 of 90 here — alongside 89 others — read 2 October 2026
Senior Frontend - javascript, html, css @seniorFront · 23,668 Telegram ranks this channel #10 of 89 here — alongside 88 others — read 17 September 2026
Журнал «Код» @thecodemedia · 49,003 Telegram ranks this channel #10 of 97 here — alongside 96 others — read 25 August 2026
IT Юмор @ithumor · 60,231 Telegram ranks this channel #10 of 94 here — alongside 93 others — read 22 August 2026
Zen of Python @zen_of_python · 18,760 Telegram ranks this channel #12 of 91 here — alongside 90 others — read 5 October 2026
Владилен: IT в эпоху AI @vladm · 39,191 Telegram ranks this channel #16 of 96 here — alongside 95 others — read 30 August 2026
Сайтодел | GitHub, Верстка, Сайты, Вайбкодинг @sitodel · 25,549 Telegram ranks this channel #21 of 89 here — alongside 88 others — read 13 September 2026
[404] — программирование @procode404 · 40,255 Telegram ranks this channel #22 of 83 here — alongside 82 others — read 30 August 2026
Библиотека программиста @proglibrary · 77,945 Telegram ranks this channel #29 of 82 here — alongside 81 others — read 19 August 2026
FrontEnd Development @fedevelopment · 28,567 Telegram ranks this channel #32 of 88 here — alongside 87 others — read 9 September 2026
Макеты для верстки @figma2html · 44,805 Telegram ranks this channel #39 of 90 here — alongside 89 others — read 27 August 2026
Porscode | CMD @porscode_tg · 28,248 Telegram ranks this channel #45 of 77 here — alongside 76 others — read 9 September 2026
Python Academy @python_academy · 44,005 Telegram ranks this channel #47 of 87 here — alongside 86 others — read 28 August 2026
Code Ready | Frontend @code_ready · 21,600 Telegram ranks this channel #64 of 89 here — alongside 88 others — read 23 September 2026
Frontend Portal @FrontendPortal · 36,426 Telegram ranks this channel #64 of 90 here — alongside 89 others — read 1 September 2026
Front End World @front_end_first · 25,768 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 23 October 2026 — this
entry's latest reading, not the date you are reading this.
“Веб-страница” (@tproger_web), 22,271 subscribers as measured 23 October 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.