Channel
@ai_sec_notes
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
49subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003547915012 |
|---|---|
| Type | Channel |
| Username | @ai_sec_notes |
| Created | 11 February 2026 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/ai_sec_notes |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 19:38 | 49 | +2 |
| 22 Aug 2026, 19:23 | 47 | +7 |
| 15 Aug 2026, 10:18 | 40 | +1 |
| 10 Aug 2026, 20:16 | 39 | no change |
| 7 Aug 2026, 19:34 | 39 | first reading |
5 posts held, back to 11 February 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
22 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 40.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 9 | 40.9% | |
| 🌭 | 4 | 18.2% | |
| 🔥 | 4 | 18.2% | |
| 🍓 | 3 | 13.6% | |
| 👀 | 1 | 4.55% | |
| 🤯 | 1 | 4.55% |
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 5 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 22reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 11 February 2026 to 29 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.
Loop Engineering: Часть 1. Automatic Prompt Optimization Наверное многие видели твит Бориса Черного, разработчика Claude Code, который заявил что больше не пишет код, а его задача теперь только создавать циклы (loop) для автономных агентов. “И такой переход мы будем наблюдать в течение всего оставшегося года” Соглашусь с этим мнением, сейчас когда агенты стали более автономными, а LLM более адаптированными под раб…
👍4
Месяц назад был представлен отчет Latio по анализу AppSec-решений рынка на 2026 год. В котором есть напрашивающиеся выводы, но я бы хотел остановиться на одном. Безопасность цепочки поставок (supply chain security) расширяется и выходит за рамки CVE: теперь она включает обнаружение вредоносного кода, оценку «здоровья» пакетов (package health) и практики безопасного использования зависимостей по умолчанию (secure-by…
🌭4👍2
Вы даете задачи LLM неправильно! Что если я скажу, что вы, скорее всего, неправильно работаете или даже кодите с LLM. Если у вас есть опыт уже боевого кодинга, скорее всего, вы планируете реализацию фичей за фичей, и это логично, ведь помещением всех целей в LLM, которые вы хотите реализовать, в контекст сразу, скорее всего, снизит качество этих фич, ведь LLM будет "разбрасываться" по задачам. Ну и логично строить с…
🔥4👍2🤯1
Sift or Get Off the PoC: Applying Information Retrieval to Vulnerability Research with SiftRank Ресерч, Реализация Одна из проблемных задач в исследовании уязвимостей связана с ограниченными ресурсами и расстановкой приоритетов. Когда вы пытаетесь найти 0 day уязвимость в каком-либо продукте, вы сосредоточиваетесь в основном на каких-то интересных моментах кодовой базы и попросту мало времени и энергии, чтобы пытат…
🍓3👀1👍1
Channel created
Showing the 5 most recent of 5 posts we hold for @ai_sec_notes. 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 — 671,707 of 1,628,524entries 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.
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.
Named by 1 registered channel — 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.
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.
“AI Sec Notes” (@ai_sec_notes), 49 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/ai_sec_notes.
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.