Telegram RegisterThe public register of Telegram

Channel

✨ confreviewer - мы любим конференции

@confreviewer

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

130subscribers

+2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003666455569
TypeChannel
Username@confreviewer
Created18 January 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/confreviewer

Growth

1281301296 August 2026 — 128 subscribers9 August 2026 — 128 subscribers14 August 2026 — 130 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net +2. 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 128–130 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:43130+2
9 Aug 2026, 01:46128no change
6 Aug 2026, 05:08128first reading

Engagement

18 posts held, back to 18 January 2026the 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.

ERR · 30 days
965.4%
avg views ÷ 130 subscribers
Avg views / post
1,260
2 posts measured
Reaction rate
0.319%
reactions ÷ views · ER floor
Posts in window
2
of 18 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 5 August 2026
Posts held18 (18 January 20265 August 2026)
Views total2,510
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 01:46 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

84 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 39.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3339.3%
🔥2934.5%
💯67.14%
55.95%
🎉44.76%
🏆22.38%
11.19%
🌚11.19%
🍌11.19%
🐳11.19%
🦄11.19%

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

Measured over the 18 most recent posts we hold, published 18 January 2026 to 5 August 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
1
across the posts below
Posts paid on
1
of 17 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @confreviewer. 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 18 most recent posts we hold for this entry, published 18 January 2026 to 5 August 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.

Recent posts

5 Aug 2026, 09:04 UTC≈1,160 views4 reactionsread 9 August 2026
Photo

Типизируем не только код: договорённости между слоями 🤝 — Андрей Едунов Доклад проходит всю карту слоёв фронтенда и показывает, что TypeScript пасует ровно на стыках. Идея честная: тип — это про контракт между слоями, автор даже касается её цены, хотя не хватило слова про TS на Go в 7-й версии, который эту цену сильно меняет. Но по пунктам концепция классная, а реализация местами оверинжиниринг. Три места я бы подс

🔥21🍌1

29 Jul 2026, 09:05 UTC≈1,350 views4 reactionsread 9 August 2026
Photo

Кеширование данных на максималках 😀 — Даниил Рублёв Крутой доклад, в котором мы идём от самых простых концепций кеширования к полноценной и довольно сложной архитектурной схеме. Автор постепенно разбирает, что именно стоит кешировать, где хранить данные и кто должен отвечать за работу с ними, а затем шаг за шагом добавляет драйверы хранилища, политики вытеснения, шифрование, прогрев и инвалидацию. В итоге из обычной

2🔥1🦄1

15 Jul 2026, 09:03 UTC≈1,580 views4 reactionsread 9 August 2026
Photo

PWA вместо App Store 👍 — Константин Шкурко Хороший вводный доклад про PWA, который особенно полезен за счёт фокуса на iOS. Автор последовательно разбирает базовые части PWA: manifest, HTTPS, Service Worker, установку приложения, offline-режим и стратегии кэширования. При этом почти каждый механизм сравнивается с Android. Отдельная часть посвящена возможностям, которые особенно важны при попытке заменить нативное при

🔥21🌚1

8 Jul 2026, 08:01 UTC≈1,720 views3 reactionsread 9 August 2026
Photo

FSD — это беда, спасёт только FDA 👍 — Дмитрий Дин Круто, что во фронтенде постепенно приходит понимание: архитектуры с бэкенда нельзя просто натянуть на клиентский код. Даже концептуальное деление на сущности, фичи и слои часто начинает мешать реальным связям внутри продукта — логика размазывается по папкам, появляются спорные абстракции, а навигация по проекту усложняется с его ростом. Автор подробно разбирает проб

1💯1🔥1

8 Jun 2026, 09:00 UTC≈1,790 views3 reactionsread 9 August 2026
Photo

Нефронтендерские оптимизации 🧙‍♂️ — Роман Фурсов Производительность веба не заканчивается на бандле, React и lazy loading. Автор разбирает варианты ускорения ниже уровня фронтенда: TCP Fast Open, TLS False Start, TLS Early Data, QUIC 0-RTT, OCSP Stapling, выбор алгоритмов шифрования, sendFile/zero-copy-подходы, асинхронную отдачу файлов, direct I/O, а также gzip, brotli, zstd и dictionary-based compression. Автор со

1🏆1🔥1

29 May 2026, 04:25 UTC≈1,790 views3 reactionsread 9 August 2026
Photo

AI-Driven UI: каким станет UI в эпоху агентов 🧠 - Юрий Карпов В рамках доклада автор проходит путь от «давайте просто генерировать HTML/JSX» до более контролируемой идеи: модель не пишет произвольный код, а возвращает структуру, которую уже рендерит приложение. По ощущениям это где-то рядом с динамическими виджетами, хоть автор и подчеркивает, что это не виджетная система. Важное отличие от классического BDUi — здес

1🎉1🔥1

18 Feb 2026, 03:16 UTC≈2,010 viewsread 9 August 2026
Photo

HTTP-кеш, Service Workers и TanStack Query: как выбрать правильный инструмент и не наломать дров 🍜 - Илья Соколов Доклад быстро пробегается по кешированию в вебе: HTTP cache, Service Workers и TanStack Query. Скорее обзорный проход по основным концепциям и типовым кейсам, чем разбор реальных прод-практик. Часть про SW и границы HTTP-кеша полезна для выстраивания базовой ментальной модели, но глубины и конкретных инж

14 Feb 2026, 16:26 UTC281 views4 reactionsread 9 August 2026
Photo

50 оттенков веб-компонентов 😎 - Алексей Назаренко Если вы до сих пор не понимали, что такое веб-компоненты и как их применять — этот доклад стоит посмотреть. Хочется глянуть именно на интеграцию с разными фреймворками, а не только теорию. Круто, что веб-компоненты можно использовать и точечно как хак, и как способ интеграции внешних сервисов в приложение — тема выглядит свежо, но вопросов по прод-использованию всё е

21🔥1

14 Feb 2026, 05:35 UTC219 views6 reactionsread 9 August 2026
Photo

Я 💛 Фронтенд 2026 Главная фронтенд-конференция Яндекса и ежегодный флагман для тех, кто создаёт современные интерфейсы. 14 февраля соберутся разработчики и дизайнеры, которые искренне влюблены во фронтенд: в код, архитектуру, визуал и пользовательский опыт. В программе — прикладные доклады от экспертов индустрии, живые дискуссии, интерактивные активности с подарками, нетворкинг и общение с единомышленниками. Всё, ч

22🔥2

10 Feb 2026, 11:00 UTC≈1,880 views5 reactionsread 9 August 2026
Photo

Утечки* Next.js. Расследование на миллион 😠 - Вадим Королев Доклад наглядно показывает, почему мониторинг критически важен: без метрик невозможно понять, что происходит с Node.js в проде и где именно утекает память. По слайдам видно, как спикер шаг за шагом дебажит проблему — через гипотезы, снапшоты памяти, анализ RSS и разбор типовых источников утечек. В итоге доклад хорошо передаёт инженерный подход: сначала набл

🔥311

28 Jan 2026, 07:58 UTC≈2,990 views6 reactionsread 9 August 2026
Photo

CSS Anchor Positioning: упрощаем разработку связанных друг с другом элементов 📰 - Рома Ахмадуллин Доклад отличное и при этом приземлённое введение в CSS Anchor Positioning как в API. Он не просто объясняет, как работает механизм якорей, но и последовательно показывает реальные use case’ы. За счёт живых демо и наглядных примеров хорошо видно, как решаются типовые боли — флип, переполнение, привязка к разным якорям. В

3🔥2💯1

25 Jan 2026, 12:48 UTC313 views7 reactionsread 9 August 2026
Photo

MoscowJS 69 🏠 Архитектура, платформа, дизайн, монолит, расчёт нагрузок — иногда не сразу понимаешь, где находишься: на стройке или в родной айтишечке. Но на MoscowJS 69 выбирать не придётся: мы идём в гости в Лемана Тех.

3🔥2🐳1💯1

Showing the 12 most recent of 18 posts we hold for @confreviewer. 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.

Citation-graph rank

Citation-graph rank — 171,866 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“✨ confreviewer - мы любим конференции” (@confreviewer), 130 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/confreviewer.

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.