If you love something, set it free 😇 https://github.com/SmartlyDressedGames/U3-SDK
custom 52131477324111662272custom 54542738922626165612custom 59609403565591813652

Channel
@zoyagurevich
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
166subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003527005441 |
|---|---|
| Type | Channel |
| Username | @zoyagurevich |
| Description | На связи @Ottosh, здесь травлю байки из жизни и рассказываю про карьеру и образование в сфере продакт-менеджмента и информационной безопасности. Все в этом канале исключительно личное мнение и фантазии его автора. 🖤 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/zoyagurevich |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 16:01 | 166 | no change |
| 7 Aug 2026, 19:34 | 166 | first reading |
20 posts held, back to 9 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 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.
| Window | Rolling 30 days · latest post in window 20 July 2026 |
|---|---|
| Posts held | 20 (9 June 2026 – 20 July 2026) |
| Views total | 261 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 16:01 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
170 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 27.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 47 | 27.6% | |
| custom 5960940356559181365 | 46 | 27.1% | |
| ❤🔥 | 27 | 15.9% | |
| custom 5454273892262616561 | 13 | 7.65% | |
| custom 5213309687037964344 | 11 | 6.47% | |
| 😁 | 9 | 5.29% | |
| custom 5215239948420003628 | 4 | 2.35% | |
| custom 5307495098613773492 | 4 | 2.35% | |
| custom 5463032631954250729 | 4 | 2.35% | |
| custom 5213147732411166227 | 2 | 1.18% | |
| 🙏 | 2 | 1.18% | |
| custom 5336867894619810730 | 1 | 0.588% |
Custom emoji. 8 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 20 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 170reactions 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 9 June 2026 to 20 July 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.
If you love something, set it free 😇 https://github.com/SmartlyDressedGames/U3-SDK
custom 52131477324111662272custom 54542738922626165612custom 59609403565591813652
🛠 Всем привет. Я тут допилил CLI-движок для LOLCreds на Go. Называется это безобразие CredsHound. Если коротко, это такая утилита для поиска учетных данных, ключей на хосте, которая работает по концепции Nuclei. Из коробки она ищет: - Пароли и API-ключи, забытые в истории терминалов (.bash_history, .zsh_history, ConsoleHost_history.txt). - Приватные ключи SSH, конфигурации Kubernetes и токены Docker Registry. - …
❤🔥2🔥1custom 59609403565591813651
когда меня в очередной раз спросят где-то про пентест агентов - мой ответ будет содержать только эту ссылку https://github.com/Yeti-791/Awesome-Offensive-AI-Agentic-Landscape
🔥2custom 54630326319542507292custom 59609403565591813652
Ахой, пирожочки! 😘 Я максимально рекомендую вам к прочтению ресерч от @s4dbrd. Adrian провел титаническую и безумно интересную работу. Так же у него есть статический анализ BattlEye. Фидбек и вопросы можно оставить в комментариях, если не забежит сам-я все передам. :) https://s4dbrd.github.io/posts/how-kernel-anti-cheats-work/
❤🔥2🔥2custom 59609403565591813652
Охаё, комрады. 🏴☠️ Продолжая топик понедельника, хочется немного затронуть тему того, где проходит граница ответственности вендора. Недавно на HackerOne отправили 7 уязвимостей в Vanguard от CVSS 3.8 до 7.8, приняли 0, потому что «DLL hijacking требует локального доступа, значит это out of scope». Формально - да. Практически - ну такое. Что удалось сделать на этой «out of scope» поверхности: 🔸 Получить произвольно…
🔥3custom 54542738922626165613custom 59609403565591813653
Кто если не я поделится с вами ссылочками на подкаст с @justmarfix из ЛК по теме его нашумевшего ресерча 😎 🎵 Яндекс.Музыка 🎵 Подкасты Apple
custom 59609403565591813655😁2custom 54542738922626165612
Ахой, комрады! 🏴☠️ Riot выкатили апдейт Vanguard и о боже мой - он переходит в On-Demand режим. Условие одно: хост должен пройти Vanguard Pre-Check. По сути, Riot строят endpoint zero-trust благодаря которому античит может себе позволить уходит в модель «по требованию», перекладывая работу на TPM, IOMMU и гипервизор. Что именно они пытаются сломать из типичных векторов атаки? [ BYOVD и Runtime Driver Attestation …
❤🔥2custom 54630326319542507292custom 59609403565591813652
Ахой комрады! 🏴☠️ Сегодня мне 31 и если честно в этом году мне кажется я получаю абсолютно рекордное количество поздравлений. Я безумно за это всем вам благодарна! Еще несколько лет назад я могла только мечтать о том, что найду себя и таких людей вокруг. Я знаю, что некоторые из вас ждут здесь посты, но работа пока не позволяет уделить времени ресерчам. Как вы помните я три недели назад вышла на новое место и все м…
❤🔥13🔥6custom 59609403565591813653
Agentic SAMM: безопасная разработка, когда разработчик больше не только человек. Расширенная версия моего кейноута на ISC.AI 2026 в Пекине. Фреймворк и инструмент открыты — берите, ломайте и присылайте мне, что найдёте. Русский Английский
custom 59609403565591813652🔥1
🪭 Разбираем Tencent ACE Part 2 🔷 [ Что под капотом? ] ❌ Война с гипервизорами Официальный гайд ACE требует отключать VBS / HVCI / Hyper-V. Главная причина - конфликт за гипервизор: ACE претендует на эксклюзивный контроль над VT-x. Зачем? Моя гипотеза, что ради EPT. Это позволяет античиту скрывать свои страницы памяти и делать невидимые хуки, не зля PatchGuard. Другие варианты которые в том числе обсуждали в коммент…
❤🔥3🔥2custom 59609403565591813652
你好 комрады! 🏴☠️ 🪭 Разбираем Tencent ACE Part 1(будет 2 части так как в одну все не влезло) Когда говорят про kernel-level античиты, на Западе принято вспоминать Riot Vanguard. Тут есть забавный нюанс: Riot на 100% принадлежит Tencent. Прямой связи «ACE → Vanguard» нет, но при общем владельце логично ожидать обмен экспертизой. В тени остаётся куда более масштабный монстр - Tencent Anti-Cheat Expert (ACE). По заявл…
custom 59609403565591813654❤🔥2🔥2
Реверс довольно популярного server crash эксплойта для CS2 😎 У автора кстати есть много интересных видео на тему читов и реверса в играх, рекомендую посмотреть. https://www.youtube.com/watch?v=9IUWPT0UVPg
🔥3❤🔥2custom 52133096870379643442custom 59609403565591813652
Showing the 12 most recent of 20 posts we hold for @zoyagurevich. 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“а я что хуже что ли?” (@zoyagurevich), 166 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/zoyagurevich.
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.