5 measurements spanning 21 days, net +100. 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 572–703 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Aug 2026, 22:34
688
+100
21 Aug 2026, 13:44
588
+1
15 Aug 2026, 03:07
587
-1
8 Aug 2026, 03:18
588
no change
7 Aug 2026, 17:31
588
first reading
Engagement
20 posts held, back to 25 June 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
30.5%
avg views ÷ 688 subscribers
Avg views / post
210
1 post measured
Reaction rate
0.476%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 5 August 2026
Posts held
20 (25 June 2026 – 5 August 2026)
Views total
210
Reactions total
1
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 03:18 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
19 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 36.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🤯
7
36.8%
🥱
6
31.6%
🤔
2
10.5%
🏆
1
5.26%
🔥
1
5.26%
😱
1
5.26%
🤷♂
1
5.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 13 of the 20 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 June 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.
#ЗВТ. Это блоки данных, которые создаются веб-сервером во время посещения пользователем веб-сайта. Они часто используются для управления сессиями пользователей. Благодаря им пользователь будет оставаться аутентифицированным при переходе между страницами.
HTTP Cookies80%
Пароль2%
HTTP кэш16%
URL (Uniform Resource Locator)0%
Токен Рутокен за 3500 рублей2%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
#ЗВТ.1 Есть требование на запрет кэширования данных в методике ФСТЭК от 12.04.2026. С помощью каких средств можно реализовать запрет кэширования пользовательских данных в веб‑браузере, используя HTTP‑заголовки Cache‑Control и Pragma?
Настройка параметров в коде приложения3%
Конфигурация веб‑сервера (Apache с модулем mod_headers, NGINX и т.д.)64%
Использование WAF5%
Все указанное выше23%
Все указанное ниже0%
Все не указанное3%
Я ИБэшник, а не программист3%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
#ИАФ#УПД. JWT (JSON Web Token) используется для безопасной передачи данных аутентификации и авторизации между клиентом и сервером в клиент-серверных приложениях.
Что указывает атрибут alg в заголовке JWT? Пример: {"alg":"HS256","typ":"JWT"}
#ЗВТ. Чтобы противодействовать CSRF-атаке , разработчику приложения нужно внедрить специальный секретный токен (CSRF-token) в сессию пользователя. Какой элемент процесса защиты от CSRF-атаки лишний?
Генерация. Сервер генерирует токен, для передачи пользователю и для сохранения на сервере13%
Передача. Токен вставляется в DOM HTML-страницы или передается через API пользователю.23%
Проверка. Сервер сравнивает полученный токен с тем, который выдали пользователю в момент генерации.3%
Подписание. Токен используется для подписания и шифрования запроса пользователя.48%
Я просто ткну сюда13%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
#ИАФ#УПД. В 2026 году исследовать на веб-ресурсе FIFA нашел архитектурную ошибку. Клиент (Angular) проверял JWT на наличие маркера NO_ROLES. При наличии маркера— Angular сразу показывает страницу с запретом доступа, но этого было не достаточно. Почему?
JWT должен проверять ещё специалист ИБ5%
JWT должен проверяться на стороне веб-сервера, а не только клиента95%
JWT не должен проверяться вовсе0%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
#ИАФ.
Что должно происходить на сервере при нажатии «Выйти» (logout) в приложении с JWT и refresh‑токенами?
Только удалить куку на стороне клиента2%
Удалить/аннулировать refresh‑токен на сервере (например, в чёрном списке) и очистить куки на клиенте78%
Заблокировать пользователя в базе данных4%
Игнорировать: JWT сами истекут через короткое время4%
Очистить рабочий стол и идти в бар11%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
🤯1
Showing the 12 most recent of 20 posts we hold for @AstraLinuxSE. 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 6 most recent of 12 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.
#ЗВТ. Это блоки данных, которые создаются веб-сервером во время посещения пользователем веб-сайта. Они часто используются для управления сессиями пользователей. Благодаря им пользователь будет оставаться аутентифицированным при переходе между страницами.
HTTP Cookies80%
Пароль2%
HTTP кэш16%
URL (Uniform Resource Locator)0%
Токен Рутокен за 3500 рублей2%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
#ЗВТ.1 Есть требование на запрет кэширования данных в методике ФСТЭК от 12.04.2026. С помощью каких средств можно реализовать запрет кэширования пользовательских данных в веб‑браузере, используя HTTP‑заголовки Cache‑Control и Pragma?
Настройка параметров в коде приложения3%
Конфигурация веб‑сервера (Apache с модулем mod_headers, NGINX и т.д.)64%
Использование WAF5%
Все указанное выше23%
Все указанное ниже0%
Все не указанное3%
Я ИБэшник, а не программист3%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
#ИАФ#УПД. JWT (JSON Web Token) используется для безопасной передачи данных аутентификации и авторизации между клиентом и сервером в клиент-серверных приложениях.
Что указывает атрибут alg в заголовке JWT? Пример: {"alg":"HS256","typ":"JWT"}
#ЗВТ. Чтобы противодействовать CSRF-атаке , разработчику приложения нужно внедрить специальный секретный токен (CSRF-token) в сессию пользователя. Какой элемент процесса защиты от CSRF-атаки лишний?
Генерация. Сервер генерирует токен, для передачи пользователю и для сохранения на сервере13%
Передача. Токен вставляется в DOM HTML-страницы или передается через API пользователю.23%
Проверка. Сервер сравнивает полученный токен с тем, который выдали пользователю в момент генерации.3%
Подписание. Токен используется для подписания и шифрования запроса пользователя.48%
Я просто ткну сюда13%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
#ИАФ#УПД. В 2026 году исследовать на веб-ресурсе FIFA нашел архитектурную ошибку. Клиент (Angular) проверял JWT на наличие маркера NO_ROLES. При наличии маркера— Angular сразу показывает страницу с запретом доступа, но этого было не достаточно. Почему?
JWT должен проверять ещё специалист ИБ5%
JWT должен проверяться на стороне веб-сервера, а не только клиента95%
JWT не должен проверяться вовсе0%
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 20 most recent posts we hold, published 25 June 2026 to 5 August 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.
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 28 August 2026 — this
entry's latest reading, not the date you are reading this.
“Linux Security” (@AstraLinuxSE), 688 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/AstraLinuxSE.
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.