2 measurements spanning 1 day. 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 117–119 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Aug 2026, 04:32
118
no change
8 Aug 2026, 00:13
118
first reading
Engagement
9 posts held, back to 12 December 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
39
Videos
2
Links
15
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
46 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 43.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
20
43.5%
🔥
13
28.3%
👍
12
26.1%
🤯
1
2.17%
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 9 of the 9 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 46reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 12 December 2025 to 4 June 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
16
across the posts below
Posts paid on
6
of 9 we hold a reading for · 67%
Most on one post
11
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @webeach_ru. 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 9 most recent posts we hold for this entry, published 12 December 2025 to 4 June 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.
🔥 Представляю ECSS v0.2
Я полностью переосмыслил ECSS.
Первая версия была экспериментом: можно ли перенести управление состояниями компонентов из JS/TS прямо в стили?
Теперь ECSS — это typed, component-oriented надмножество CSS, которое позволяет описывать компоненты в .ecss файлах и получать на выходе обычный CSS + готовые типизированные компоненты для вашего фреймворка.
──
🧩 В чём идея?
Обычно UI-компонент жи…
😌 Что такое CSS FlexBox?
По сути, FlexBox — это система раскладки элементов в CSS, которая позволяет удобно управлять расположением блоков внутри контейнера.
Раньше для этого приходилось использовать float, таблицы, хаки и страдания 😭
Но потом появился FlexBox — и верстать интерфейсы стало намного проще ✨
Давайте разберёмся на практике 👇
──
🔹 Включаем FlexBox
Допустим, у нас есть контейнер с карточками:
<div …
😅 Что такое «миры» (realms) в JavaScript?
По сути, «мир» (realm) в JS — это отдельная область выполнения кода. Она может существовать внутри вкладки/окна браузера или, например, внутри iframe.
Но иногда эти «миры» сталкиваются 💥
Давайте разберёмся на реальных примерах 👇
──
🔸 Айфреймовое проникновение
// создаём iframe
const iframe = document.createElement('iframe');
document.body.append(iframe);
// объект win…
🛡 Представляю dist-guard — сканер секретов для бандлов
Инструмент, который проверяет ваши собранные файлы (dist, build) на утечки токенов, API-ключей, паролей и приватных данных — прямо перед деплоем.
──
🤔 Зачем это нужно?
Бандлеры (Vite, Webpack, Rollup) иногда тянут в production-сборку то, что не должно туда попасть. Переменные окружения, жёстко прописанные ключи, строки подключения к базам данных, локальные пу…
🔥 Представляю всем ECSS — Extended CSS
Новый язык, который расширяет CSS тремя конструкциями для декларативного управления состояниями компонентов прямо в файлах стилей.
А точнее — полноценную экосистему:
— Сайт документации: https://ecss.webea.ch
— Исходники (Rust-парсер, Vite-плагин, TS-плагин и расширение): https://github.com/webeach/ecss
──
Зачем нужен ECSS?
Вы наверняка уставали писать className={clsx(style…
🧐 using элегантная замена try...finally?
Если вы когда-нибудь работали с сокетами, слушателями событий или таймерами, вы знаете эту боль: открыл ресурс — будь добр закрой его в блоке finally. Иначе получите утечку памяти.
Но начиная со стандарта ES2025 появилось ключевое слово using, которое решает эту проблему элегантно и без лишнего кода.
──
👎 Как мы писали раньше:
const file = openFile('data.txt');
try {
f…
🤔 Почему Math.random() опасен?
Все знают фразу: «не используй Math.random() для безопасности».
Но обычно никто не объясняет почему именно.
Давайте разберем конкретный механизм и реальный сценарий проблемы.
──
💠 Как Math.random() работает под капотом
В большинстве окружений Node.js это движок V8.
И начиная примерно с 2015 года V8 использует PRNG-алгоритм xorshift128+.
Он хранит внутреннее состояние из двух 64-би…
🔥 Представляю всем мою новую библиотеку небольшого расширения React
react-x — небольшая либа, которая прокачивает JSX для работы с CSS-классами, стилями и CSS-переменными без лишнего шума, хаков и кастомных хелперов.
Вдохновился svelte 🙃
──
🤔 Зачем это нужно?
Если ты устал от:
▫️ clsx(className, condition && styles.container)
▫️ сложных style объектов
▫️ трудной работы с css-переменными при разработке UI-компо…
🤔 Как правильно клонировать массив в JavaScript?
В этом посте мы поговорим о том, как оптимальнее всего поверхностно склонировать массив.
У нас есть 3 самых популярных способа сделать это:
▫️ через spread → [...arr]
▫️ через concat → [].concat(arr)
▫️ через slice → arr.slice()
Мы провели замеры клонирования массива на 100к элементов в 1000 итераций на каждом браузерном движке, используя обычный console.time().
Н…
👍6❤2
Showing the 9 most recent of 9 posts we hold for @webeach_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.
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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
1
we ourselves saw one of these resolve, at some point
Never seen alive
0
vacant every time we have ever looked
@webeach_ru named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
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.
@element named in 1 post, 10 August 2026 – 10 August 2026 · confirmed gone 12 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 9 August 2026 — this
entry's latest reading, not the date you are reading this.
“Вебыч” (@webeach_ru), 118 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/webeach_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.