Если уж писать бизнес-логику, то только для собственного бизнеса 🥸
👍2😁2

Channel
@ohmysecurity
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
47subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001451708370 |
|---|---|
| Type | Channel |
| Username | @ohmysecurity |
| Description | Сyber performance |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ohmysecurity |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 14:00 | 47 | no change |
| 10 Aug 2026, 01:46 | 47 | first reading |
20 posts held, back to 3 April 2022 — 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 20 posts for this entry, the most recent from 14 December 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
63 reactions across 9 posts, in 12 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18 | 28.6% | |
| 🔥 | 18 | 28.6% | |
| 😁 | 7 | 11.1% | |
| 🤣 | 5 | 7.94% | |
| 😢 | 4 | 6.35% | |
| ❤ | 2 | 3.17% | |
| 🍾 | 2 | 3.17% | |
| 👏 | 2 | 3.17% | |
| 🫡 | 2 | 3.17% | |
| 👨💻 | 1 | 1.59% | |
| 🗿 | 1 | 1.59% | |
| 🤔 | 1 | 1.59% |
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 9 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 63reactions 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 3 April 2022 to 14 December 2024, 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😁2
Есть удивительный феномен, когда внимание коллег к деталям на код-ревью PR превышает любые нормы приличия, но в мастере всеравно в итоге получается какое-то говно 🤔
🤣5👨💻1
Хотите поговорить об Agile? Agile и сопутствующие Scrum'ы со стороны кажутся довольно простой фигней, слишком простой. Поэтому многие инженеры, а то и инженерные менеджеры пролистав пару статеек, считают, что все поняли и не пытаются копать глубже. В этом и таится коварная проблема Agile, это вам не PMP, где целую PITA надо осилить. Если ваш менеджер называет дейлики "скрамом", то можем ставить ему диагноз прямо се…
🔥13🗿1
Access management для бедных и ленивых У меня тут близится SOC2 и HIPAA аудит, а значит пора навести марафет везде, куда может сунуть любопытный нос аудитор. Первое и самое излюбленное место это access management. Стартапы и маленькие компании любят двигаться быстро, а значит оставляют на своем пути кучу 💩. Обычно фаундер регает на свой личный имейл все важные сервисы, а гребцы, когда им нужен тот или иной доступ, …
🔥5👍4
Закат валютной удаленки Ничто не вечно, все меняется. Валютная удаленка вообще перестала существовать как явление. Конечно, есть еще исключения, чувачки которым повезло не быть уволенными в первые недели всем известных событий. Они сидят тише воды, попутно ищут возможности обходить новые препятствия в области финансового регулирования и санкционных механизмов. Но посмотрим правде в лицо, таких остается все меньше. …
😁5😢4🍾2🤔1
Root cause analysis Часто при возникновении проблемы появляется соблазн сразу задать вопрос: "Как мы можем это исправить?" Желание улучшать всегда похвально, но существует риск пропатчить не проблему, а симптом. Особенно часто это происходит, когда вы динамично развивающийся стартап, в котором нет времени думать, а нужно только делать. В таких проектах все часто скатывается к костылям и заплаткам, которые тушат пож…
👍4👏2
Цифровая карма Давненько думаю над концепцией цифровой кармы. Эдакий децентрализованный социальный рейтинг, где оценки выдаются не государством, а любым участником системы. Т.е. если большинство считает вас мудаком, то скорее всего вы мудак. Естественно подобную систему будет сложно внедрить в реальный мир, поэтому надо начинать с малого. Сегодня посетила идея локального применения этой концепции. Представьте станд…
❤2
Знакомство с командой Немного порефлексировал на тему онбординга внутри инженерных команд. За свою карьеру я не видел по-настоящему классного процесса 🤷♂️ И точно нигде не было внутри-командных ритуалов для новобранцев. Обычно HR присылает чеклист на первую неделю-месяц, тимлид добавляет в чаты, и считается, что гребец готов к плаванию. Дальше у новичка возникает ощущение, будто он попал на вечеринку в незнакомую …
👍6🫡2
Hello folks 👋 I've decided to revamp this blog in a bit new format 🚀 Taking into the account that most of subscribers here are Russian speaking, I'd like to post here in Russian. Not just about security, but whatever I work on or see in the industry. Hopefully this way I'll be able to make blogging my persistent habit 🤞 This idea came to me after watching this video https://www.youtube.com/watch?v=B96QNMoxtHQ by @pm…
👍2
Today working on one of the HTB boxes I discovered a readable .Xauthority file in other user's home directory. A quick googling revealed that this file works as a cookie to an X11 session. And it means that you can run any X11 apps on behalf of that user. Thanks to an article from 2004 for that piece of knowledge https://www.hackinglinuxexposed.com/articles/20040513.html Happy hacking 🤟
For the last month or so I've been focused on building a Linux From Scratch system on my old Raspberry Pi 1 Model B. Happy to share my summary and thoughts on the process 👉 https://cspub.net/2023/03/22/building-lfs-on-raspberry-pi.html
My personal checklist of security actions needed for any online project ✅ https://cspub.net/2023/03/14/smb-saas-security-checklist.html
Showing the 12 most recent of 20 posts we hold for @ohmysecurity. 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,002,670 of 1,151,006entries 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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“ohmysecurity” (@ohmysecurity), 47 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/ohmysecurity.
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.