4 measurements spanning 17 days, net +4. 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 10–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
24 Aug 2026, 14:59
15
+1
16 Aug 2026, 02:34
14
+3
12 Aug 2026, 08:15
11
no change
7 Aug 2026, 19:28
11
first reading
Engagement
9 posts held, back to 9 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.
ERR · 30 days
86.7%
avg views ÷ 15 subscribers
Avg views / post
13.0
3 posts measured
Reaction rate
14.3%
reactions ÷ views · ER floor
Posts in window
3
of 9 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 1 of 3 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 10 August 2026
Posts held
9 (9 December 2025 – 10 August 2026)
Views total
39
Reactions total
2
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 08:15 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
5 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 20.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1
20.0%
🆒
1
20.0%
👍
1
20.0%
🔥
1
20.0%
🤝
1
20.0%
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 4 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 5reactions 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 9 December 2025 to 10 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.
№2 - Anthropic удалила часть ограничений безопасности из своей AI Scaling Policy
- Количество связанных статей: 1756
- Дата: 2026-02-24
- Ссылка: https://oecd.ai/en/incidents/2026-02-24-0b1e
Anthropic обновила свою Responsible Scaling Policy, отражающую действия компании при получении моделей большей мощности. В первой версии, опубликованной в сентябре 2023 года основное правило было довольно прямолинейным и обознача…
Истинно-хайповые инциденты AI Safety
Введение
За последний год я просмотрел множество вебинаров и демонстраций новых инструментов из сферы безопасности ИИ. Почти на каждой такой встрече докладчики использовали примерно одни и те же аргументы для доказательства актуальности проблемы. Например, среди них часто упоминался кейс о сотрудниках Samsung, которые в 2023 году использовали ChatGPT сливая в него конфиденциальны…
Представьте: вы CTO небольшой компании.
Полгода назад вы с командой запустили AI-фичу – умный ассистент поверх LLM, который дергает пару внутренних API и векторную базу по документации продукта (RAG), отвечает клиентам и в целом делает жизнь пользователей лучше. Внедрили, продали, метрики радуют, инвесторы довольны.
А потом вы листаете ленту и натыкаетесь на очередную новость про утечку данных через почтового ИИ-аг…
Тренды на стыке ИБ и ИИ
12 мая группа Threat Intelligence компании Google выложила очередной отчёт из серии AI Threat Tracker (предыдущий был опубликован в феврале).
TL;DR - какие выводы можно сделать из отчета:
1. Для атакующих системы ИИ имеют двойное значение - это и цель, и инструмент одновременно
2. ИИ облегчает прохождение всех (или почти всех) этапов атаки и уже сейчас в этих целях используется на высоком ур…
Статические сканеры ML-моделей: тотальная защита или ещё один рубеж?
При появлении новых технологий вслед за ними возникают неизвестные до этого угрозы, одной из них является отравление моделей машинного обучения - злоумышленник заранее внедряет в артефакт модели вредоносный код, исполняемый в процессе загрузки модели на устройстве жертвы. Создать опасную модель может даже школьник - при помощи fickling это делается…
Оркестрация ИИ-агентов для кодинга – прорубаем окно к новым возможностям [часть 1]
Введение Моя мотивация
По моему опыту разумное использование даже всего лишь одного агента сильно ускоряет и упрощает разработку ПО. Но мой опыт включает использование агентов исключительно для решения довольно точечных задач, с последующей самостоятельной проверкой внесенных изменений и работоспособности системы в целом.
Однако, нед…
Showing the 9 most recent of 9 posts we hold for @BorZaseka. 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.
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 24 August 2026 — this
entry's latest reading, not the date you are reading this.
“BorZaseka – ИБ | AI | AI Security” (@BorZaseka), 15 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/BorZaseka.
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.