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 12 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.
Growth
23 measurements spanning 97 days, net -24. 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 5,878–5,924 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)
Subscribers
Change
10 Nov 2026, 15:15
5,891
-4
6 Nov 2026, 17:28
5,895
+5
3 Nov 2026, 06:56
5,890
+7
27 Oct 2026, 22:11
5,883
-2
25 Oct 2026, 07:06
5,885
-10
22 Oct 2026, 08:18
5,895
+2
19 Oct 2026, 10:27
5,893
-2
16 Oct 2026, 17:28
5,895
+1
13 Oct 2026, 17:48
5,894
+4
7 Oct 2026, 14:41
5,890
+1
30 Sept 2026, 12:54
5,889
-4
19 Sept 2026, 17:56
5,893
+5
15 Sept 2026, 06:20
5,888
-11
11 Sept 2026, 22:00
5,899
-3
7 Sept 2026, 17:56
5,902
+1
3 Sept 2026, 00:17
5,901
-5
31 Aug 2026, 02:24
5,906
-6
28 Aug 2026, 05:12
5,912
-2
25 Aug 2026, 01:58
5,914
-5
18 Aug 2026, 17:06
5,919
first reading
Engagement
38 posts held, back to 12 May 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 11 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
50.4%
avg views ÷ 5,891 subscribers
Avg views / post
2,970
20 posts measured
Reaction rate
0.597%
reactions ÷ views · ER floor
Posts in window
20
of 38 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. It is computed over the 19 of 20 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 November 2026
Posts held
38 (12 May 2026 – 4 November 2026)
Views total
59,340
Reactions total
341
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
5 Nov 2026, 02:37 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.
What this channel posts
Video runtime
38m 33s
Average length
6m 26s
Measured directly from 6 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,248 reactions across 37 posts, in 4 distinct kinds. The most used accounts for 68.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
849
68.0%
👎
237
19.0%
🔥
115
9.21%
❤
47
3.77%
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 37 of the 38 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,248 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 38 most recent posts we hold, published 12 May 2026 to 4 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.
Recent posts
Telegram’s own ‘edited’ marker: 10 of 20 posts held from the last 30 days (50.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).
📱 Как Google Play шесть лет переводил на Compose приложение с 20-летней историей
В Play Store несколько миллионов строк кода, 200 экранов и 500 UI-компонентов. Команда начала переход в 2020-м. Сейчас 97% показов приходится на экраны только на Compose, а джанк на главных экранах за 14 месяцев снизился на 30%. На Android Dev Summit команда рассказала, как шёл переезд:
👉 Сначала малопосещаемые экраны вроде настроек, п…
⚙️ Haze 2.1: Glass стал стабильным, а hazeGlassContainer объединяет соседние эффекты в одну форму
Haze — библиотека для blur и эффекта стекла в Compose и Compose Multiplatform. Glass появился экспериментальным в версии 2.0, а про backdrop blur в Android 17 QPR2 мы писали на прошлой неделе.
👉 haze-glass и haze-glass-material3 больше не требуют opt-in ExperimentalHazeApi. Часть API из 2.0.x переименовали.
👉 hazeGlas…
🔍 Трейс покажет, какой стейт вызвал рекомпозицию: в Compose 1.13 появился recomposition tracing
Composition tracing в Perfetto давно показывает, какие composable-функции выполнялись. Почему функция перезапустилась, он не говорил, и для этого брали сторонние инструменты вроде ComposeStateMonitor. Теперь в гайде по трейсингу Compose описан recomposition tracing: в трейс попадают чтения и записи стейта, из-за которых c…
🧊 Glassmorphism на новых API Android: карточка поверх размытого фона и blur для видео
Демо с Android Dev Summit. Слева карточка «Jetpack Glass»: текст и иконки рисуются поверх размытого фона и остаются чёткими. Справа две панели над цветной сеткой: у одной blur 60px, у другой 40px и насыщенность 2.5x.
Для видео есть отдельный API. SurfaceView не входит в дерево RenderNode приложения, поэтому раньше размыть кадр под…
🔍 Лупа из кнопки: как Google склеила шейдер и blur в один backdrop-эффект
На слайде с Android Dev Summit код, который придает кнопку «Jump to bottom» эффект Liquid Glass.
val agslShader = RuntimeShader(CHROMATIC_ABERRATION)
val noiseEffect =
RenderEffect.createRuntimeShaderEffect(agslShader,
"backdropInput")
val finalEffect =
RenderEffect.createChainEffect(noiseEffect, vibrantBlur)
renderNode?.setBackdropRenderEffe…
🪟 Backdrop blur в Android 17 QPR2: размытие под элементом, а не самого элемента
Modifier.blur размывает composable целиком, вместе с заголовком и иконками. Backdrop blur работает иначе: размывается только контент под элементом, а текст сверху остаётся чётким.
👉 RenderNode.setBackdropRenderEffect() появился в API 37.2 (Android 17 QPR2). Узел сам берёт то, что лежит под ним, и применяет к этому эффект
👉 В Compose это…
⚙️ Prevue от Kakao: агент сам смотрит превью Compose в браузере
Prevue — плагин для Claude Code и Codex. Он показывает все @Preview из файла в браузере без Android Studio и перерисовывает их примерно через секунду после сохранения. Агент видит картинку, сверяет её с макетом или скриншотом и правит код сам.
claude plugin marketplace add https://github.com/kakao/prevue.git
claude plugin install prevue@prevue
👉 Клик …
🚀 AppState: общее состояние Compose вне Activity
На Android Dev Summit Google показала AppState (alpha). Это набор библиотек androidx.appstate. Главная из них, statestore, хранит Compose-состояние вне UI, то есть вне Activity, и раздаёт его разным частям приложения.
StateStore — обычный класс. Согласно документации, где создавать экземпляр, решает разработчик. Состояние читают по типизированному ключу, а меняют чер…
⚙️ Что Google показала для Compose на Android Dev Summit: стабильные Grid и Flexbox, Navigation 3 1.2 и UI из ответов агента
На Android Dev Summit Google рассказала, что приходит в Compose в ближайших релизах.
👉 Compose 1.13 скоро выйдет в стабильной версии: Grid и Flexbox для адаптивных раскладок станут стабильными, появятся Progressive Blur и Formatted Text
👉 Navigation 3 1.2 уже стабильна: в ней диплинки и расш…
⚙️ Как оптимизировали TGS‑стикеры в Compose Multiplatform: от Compottie к Frame Baking
Анимированные стикеры Telegram приходят в формате TGS — это Lottie-анимация в JSON, сжатая gzip. Чтобы показать стикер, файл распаковывают и отдают Lottie-плееру. Автор GhostGram, экспериментального клиента Telegram на KMP, рассказал на Хабре, как этот путь сломался на Android: с Compottie часть стикеров играла в 2–3 раза быстрее,…
⚙️ Styles API в Compose переделывают: документацию временно убрали
На Google I/O команда Compose показала Styles, новый способ настраивать внешний вид компонентов. Теперь она сообщила, что по итогам отзывов API станет менее навязчивым: определения визуальных свойств переедут из слоя foundation в слой дизайн-системы, то есть в Material или вашу собственную. Дизайн-система сама решит, какие свойства её компонентов мож…
👍13🔥4
Showing the 12 most recent of 38 posts we hold for @compose_broadcast. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Вам нужен Liquid Glass эффект в Compose Multiplatform?
Да37%
Нет35%
Что это?4%
Не пишу на Compose под iOS17%
Не участвую в опросе8%
Shares as published, totalling 101%. 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 38 most recent posts we hold, published 12 May 2026 to 4 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
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 4 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
@compose_broadcast 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.
@tracerecomposition named in 3 posts, 8 August 2026 – 11 August 2026
@navdestination named in 2 posts, 8 August 2026 – 11 August 2026
@navedge named in 2 posts, 8 August 2026 – 11 August 2026
@navgraphroot named in 2 posts, 8 August 2026 – 11 August 2026
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Compose Broadcast” (@compose_broadcast), 5,891 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/compose_broadcast.
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.