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
36 measurements spanning 52 days, net -110. 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 13,866–14,013 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 36
Measured (UTC)
Subscribers
Change
26 Sept 2026, 23:37
13,883
-24
19 Sept 2026, 17:56
13,907
-7
17 Sept 2026, 08:20
13,914
-4
13 Sept 2026, 21:01
13,918
-4
12 Sept 2026, 05:17
13,922
-10
9 Sept 2026, 23:38
13,932
-4
6 Sept 2026, 17:18
13,936
-5
4 Sept 2026, 04:41
13,941
-3
2 Sept 2026, 18:04
13,944
-4
1 Sept 2026, 19:33
13,948
+1
31 Aug 2026, 18:13
13,947
-3
30 Aug 2026, 20:38
13,950
-1
29 Aug 2026, 23:15
13,951
-9
28 Aug 2026, 23:04
13,960
+1
28 Aug 2026, 02:22
13,959
+1
27 Aug 2026, 04:59
13,958
-1
26 Aug 2026, 01:32
13,959
-3
24 Aug 2026, 23:35
13,962
-6
23 Aug 2026, 07:05
13,968
-7
21 Aug 2026, 20:08
13,975
first reading
Engagement
48 posts held, back to 17 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 50 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
18.1%
avg views ÷ 13,883 subscribers
Avg views / post
2,520
6 posts measured
Reaction rate
0.854%
reactions ÷ views · ER floor
Posts in window
6
of 48 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 2 September 2026
Posts held
48 (17 July 2026 – 2 September 2026)
Views total
15,110
Reactions total
129
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
2 Sept 2026, 19:25 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
1,029 reactions across 46 posts, in 4 distinct kinds. The most used accounts for 38.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
391
38.0%
👍
355
34.5%
❤
270
26.2%
🎉
13
1.26%
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 48 of the 48 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 1,057 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 48 most recent posts we hold, published 17 July 2026 to 2 September 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.
Новинки Firefox 155 для разработчиков. Релиз расширяет функцию attr() на любые CSS-свойства с единицами измерения и фолбеками, добавляет функции progress() и alpha(), переименовывает font-stretch в font-width и добавляет Promise.allKeyed() и Promise.allSettledKeyed(). В инструментах разработки появились панель эмуляции медиафич и поддержка JSON Lines. За флагами: анимации по скроллу и изолированные реестры кастомных …
Как заставить агентов писать хороший CSS. Брехт Де Рюйте пробует Modern Web Guidance от Google — набор навыков, который передаёт агентам для кодинга экспертные рекомендации по платформе вместе с данными Baseline. Поиск через CLI подгружает только нужные руководства из 103 фич, а фолбеки каждую ночь проверяют тесты на Playwright. Набор не привязан к проекту, поэтому автор добавил три своих навыка: уровни токенов, темы…
Как выделить фрагмент текста внутри поля. Олли Уильямс показывает, как новый OpaqueRange распространяет CSS Custom Highlight API на поля ввода. Вызовите createValueRange() у <textarea> или у <input> с типом text, password, search, tel или url, передайте результат в Highlight() и зарегистрируйте через CSS.highlights.set(). В ::highlight() доступны color, background-color, text-decoration и text-shadow. Работает в Chro…
Выпуск №542. Лёша Красиков и Никита Дубко про новинки Chrome 152, вычисление кастомных свойств, виртуальные списки и отказ от RSC.
— Лайв на Ютубе
— Слушайте на Ютубе
— Ссылки на сайте
Как ускорить длинный список: content-visibility или виртуализация. Агустин Барриентос сравнивает список из 50 тысяч карточек, отрисованный тремя способами. Свойство content-visibility: auto вместе с contain-intrinsic-size оставляет все строки в DOM и пропускает рендеринг за пределами экрана, а виртуализация выкидывает строки из DOM и заодно забирает у браузера поиск по странице, ссылки-якоря, сохранение фокуса и сост…
Новинки Chrome 152. Интерфейс CSSPseudoElement теперь работает с ::backdrop, ::scroll-marker и ::view-transition — клики по подложке диалога или маркеру прокрутки наконец получили цель. Новый CPU Performance API сообщает класс производительности устройства, а заголовок Connection-Allowlist ограничивает, куда страница может отправлять запросы. Ещё в CSS появилась функция alpha() для относительной прозрачности, а атриб…
Балансируем флекс-элементы свойством flex-wrap: balance. Ахмад Шадид начинает с вёрстки на сайте Buffer, где в последней строке остаётся один элемент, и показывает пять способов это исправить: выражения от контейнера, условный clamp() для max-width, display: contents, разделитель на псевдоэлементе и, наконец, flex-wrap: balance из Chrome 150 — всего одно объявление. Свойство flex-line-count задаёт минимальное число с…
Firefox готовится поддержать JPEG XL. Джейк Арчибальд рассказывает, что поддержка строится на jxl-rs — декодере на Rust от Google Research, который избавляет от рисков старой реализации на C++ в 100 тысяч строк. На фотографиях AVIF по-прежнему выигрывает при сжатии с потерями, а JPEG XL — без потерь. Ещё он пережимает JPEG и умеет прогрессивную отрисовку: большие картинки появляются уже во время загрузки. #image #fir…
Знакомимся с HTML-элементом <geolocation>. Даниэль Шварц разбирает новый элемент из Chrome 144, который заменяет Geolocation API разметкой: autolocate переиспользует ранее выданное разрешение, watch следит за перемещением, а onlocation обрабатывает результат. Таймауты браузер берёт на себя. Псевдокласс :granted стилизует кнопку, isValid и invalidReason сообщают о проблемах, а строгие правила стилизации защищают от пе…
Выпуск №541. Вадим Макеев, Лёша Красиков, Никита Дубко и Полина Гуртовая про Firefox 154, HTTP-метод QUERY, селектор с префиксом, метрику UNO и снова переключатели темы.
— Лайв на Ютубе
— Слушайте на Ютубе
— Ссылки на сайте
❤17👍3
Signed Vadim Makeev
Showing the 12 most recent of 48 posts we hold for @webstandards_ru. 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.
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 6 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
4
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
4
vacant every time we have ever looked
@webstandards_ru named 4 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@navigation named in 8 posts, 8 August 2026 – 26 August 2026
@property named in 6 posts, 8 August 2026 – 21 August 2026
@theme named in 3 posts, 16 August 2026 – 21 August 2026
@starting named in 3 posts, 8 August 2026 – 12 August 2026
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.
FrontEndDev @front_end_dev · 25,875 Telegram ranks this channel #25 of 95 here — alongside 94 others — read 13 September 2026
Веб-страница @tproger_web · 22,429 Telegram ranks this channel #33 of 96 here — alongside 95 others — read 20 September 2026
Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js @frontendproglib · 20,930 Telegram ranks this channel #35 of 93 here — alongside 92 others — read 25 September 2026
FrontEnd Development @fedevelopment · 28,752 Telegram ranks this channel #69 of 88 here — alongside 87 others — read 9 September 2026
Frontender's notes [ru] @frontendnoteschannel_ru · 31,430 Telegram ranks this channel #88 of 95 here — alongside 94 others — read 6 September 2026
This channel appears in 5 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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“Веб-стандарты” (@webstandards_ru), 13,883 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/webstandards_ru.
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.