Channel
@doctorponos
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
560subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002241481407 |
|---|---|
| Type | Channel |
| Username | @doctorponos |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/doctorponos |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 08:07 | 560 | -8 |
| 7 Aug 2026, 07:31 | 568 | no change |
| 7 Aug 2026, 07:18 | 568 | first reading |
12 posts held, back to 20 September 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 31 May 2026. An engagement rate over an empty window would be a number about nothing.
260 reactions across 12 posts, in 18 distinct kinds. The most used accounts for 31.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 82 | 31.5% | |
| ❤ | 50 | 19.2% | |
| 🔥 | 42 | 16.2% | |
| 👍 | 39 | 15.0% | |
| ❤🔥 | 9 | 3.46% | |
| 🌚 | 8 | 3.08% | |
| 🤯 | 6 | 2.31% | |
| 🗿 | 5 | 1.92% | |
| 💘 | 3 | 1.15% | |
| 🤔 | 3 | 1.15% | |
| 👏 | 2 | 0.769% | |
| 💩 | 2 | 0.769% | |
| 🕊 | 2 | 0.769% | |
| 🙈 | 2 | 0.769% | |
| 🤮 | 2 | 0.769% | |
| 👾 | 1 | 0.385% | |
| 😢 | 1 | 0.385% | |
| 🤓 | 1 | 0.385% |
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 12 of the 12 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 260reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 20 September 2025 to 31 May 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.
⚡️⚡️⚡️ Осмотра простаты НЕ БУДЕТ Просто Доктор П снова приехал на CodeFest. Сюда публикую ссылки и полезные материалы. Презу и источники кину после доклада. А пока можете заглянуть на моковое приложение по ссылке https://ai-chat-shop.onrender.com (я его сломал на время доклада, потом включу обратно)
❤3😁3💘1
❗️❗️❗️ИЩУ 2 ЕМЕЛЬЩИКОВ 1️⃣ Первый ML-специалист нужен на создание рекомендательной системы офферов для крупного enterprise-продукта. Нужно будет строить всё практически с нуля: пайплайны, ранжирование, обучение моделей, production и оценку качества. Ожидаем two‑tower модель, поэтому важны знания или опыт с поисковыми движками (OpenSearch и т.п.). ⚠️Необходимо, чтобы у тебя уже был опыт в построении RecSys!⚠️ DevOp…
❤3👍2💘1
Ссылки для доклада по ИИ-пентестеру https://github.com/grentank/prompts-for-scanner-pentester
❤6💘1
#видеозаписи #ТестоваяСреда Открываем новую видеозапись выступления: Александр Князев — Взлом AI-агентов: прикладная инструкция к уязвимостям LLM и тулов Доклад о популярных векторах атак на веб-приложения с AI-агентами. Спикер показал реальные примеры атак на API, которые могут привести к компрометации системы, раскрытию данных и выполнению нежелательных действий. 😉 YouTube | 📺 VK Видео Скачать презентацию с сай…
❤12🔥8💩2🌚1🕊1
❗️❗️❗️HTTP/1.1 ВСЁ Вчера выступил на конференции Dump в Питере 🗣 Рассказал, какая же залупа этот ваш HTTP/1.1 🤮 Пытался ломануть апстрим соединение всратыми заголовками Content-Length и Transfer-Encoding 😈 Всё бы ничего, но я забыл добавить мемы в презу, поэтому как долбоёб показывал картинки котиков со второго ноута 🤦🤦🤦 Само выступление было заебись, зрители живые. Особенно тот, кто свалил посреди доклада 🥳🥳🥳 (я …
😁22❤10🗿1
Если бы сатана пёк блины, то первый блин комом был бы именно таким 👆
🔥14😁1
Вот что бывает, когда на новогодних каникулах тебе приходится исследовать ИИ-аватары вместо отдыха 🤖 Доктор П, я создал тебе цифрового конкурента. Знакомьтесь: Нейро-Князь 👑
😁11🔥8👍6🙈2
HeadHunter ВСЁЁЁ😠😠 Сегодня я расскажу насколько сломан этот ебучий портал поиска работы в 3 пунктах 👿 Краткая предыстория: 👉Расширяю свою команду 👉Открыли вакансию на AI-инженера 👉В первые часы на hh.ru уже сотни откликов 👉Я начинаю разгребать эту свалку 1️⃣ 99% мэтчей — это автоотклики 🖱 Это платная фича для соискателей, благодаря которой hh.ru сам спамит работодателей вашим резюме. Вот только кандидаты могут быт…
😁23❤🔥9🤯6❤5👏2🔥1
Следующий пост будет о поносном нейрослопе
😁17🤔3
🤦♂️ Обоссаные LLM-шлюзы: Как я чуть не проебал прод в субботу вечером Привет, подписечник! Новая true story с пылу-жару, прямо с прода 😐 Картина маслом: шестидневная рабочая неделя, рабочая суббота, на часах 17:00. В воздухе уже пахнет трёхдневными выходными. Планы просты — доделать пару задач, закоммитить и пойти в бар отдыхать. Ничто не предвещало беды... как вдруг — алерт! 🚨 Один мой ИИ-агент начал сходить с у…
👍15🌚4🗿4😁3🤮2👾1
Photo, posted without a caption
❤10🌚3😁2👍1🤓1😢1
SOC-Forum — крупнейший форум по информационной безопасности в России 🔥 Организуется ФСБ, длится три дня и собирает топовых людей из РФ и дружественных стран. Туда приезжают официальные делегации даже из Китая 🇨🇳 и Индии 🇮🇳 — вплоть до министров по инфобезу. Это реально масштабное и мощное событие мирового уровня 🚀👍 В прошлом году я туда ворвался с хорошим проработанным докладом, который потом разлетелся по многим др…
👍15🔥11❤1🕊1
Showing the 12 most recent of 12 posts we hold for @doctorponos. 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 — 1,055,275 of 1,481,217entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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.
“Мысли Доктора П” (@doctorponos), 560 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/doctorponos.
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.