izi DevOps pinned a photo

Channel
izi DevOps
@izi_devops
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Polls · Cite this entry
3,120subscribers
+985 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003792250337 |
|---|---|
| Type | Channel |
| Username | @izi_devops |
| Created | Between 1 February 2026 and 13 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/izi_devops |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 23:14 | 3,120 | +41 |
| 28 Sept 2026, 07:36 | 3,079 | +116 |
| 15 Sept 2026, 13:19 | 2,963 | +32 |
| 11 Sept 2026, 22:18 | 2,931 | +13 |
| 7 Sept 2026, 11:41 | 2,918 | +120 |
| 2 Sept 2026, 09:22 | 2,798 | +58 |
| 30 Aug 2026, 16:05 | 2,740 | +15 |
| 27 Aug 2026, 17:36 | 2,725 | +20 |
| 25 Aug 2026, 03:57 | 2,705 | +5 |
| 21 Aug 2026, 16:25 | 2,700 | +61 |
| 18 Aug 2026, 06:26 | 2,639 | +309 |
| 15 Aug 2026, 01:04 | 2,330 | +160 |
| 11 Aug 2026, 08:17 | 2,170 | +15 |
| 8 Aug 2026, 17:41 | 2,155 | +20 |
| 7 Aug 2026, 20:31 | 2,135 | no change |
| 7 Aug 2026, 19:39 | 2,135 | first reading |
Engagement
20 posts held, back to 13 May 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 page of 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 4m 02s
- Average length
- 1m 21s
Measured directly from 3 videos 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.
Reaction mix
301 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 129 | 42.9% | |
| 👍 | 66 | 21.9% | |
| ❤ | 58 | 19.3% | |
| 😁 | 30 | 9.97% | |
| ❤🔥 | 9 | 2.99% | |
| 🎉 | 3 | 0.997% | |
| 😍 | 2 | 0.664% | |
| 🏆 | 1 | 0.332% | |
| 👾 | 1 | 0.332% | |
| 🤔 | 1 | 0.332% | |
| 🤝 | 1 | 0.332% |
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 19 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 301 reactions 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 13 May 2026 to 7 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.
Telegram Stars
- Stars received
- 19
- across the posts below
- Posts paid on
- 5
- of 19 we hold a reading for · 26%
- Most on one post
- 11
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @izi_devops. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 13 May 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
BGP ➖➖➖ ▎1. Маршрут выбирают не по географии Логично думать, что трафик идёт коротким путём. На деле роутер прогоняет анонсы через список правил и берёт первый, который отсеет остальные. Порядок такой: сначала local preference, число, которое провайдер ставит руками, чем больше тем лучше. Дальше длина AS-path, то есть через сколько чужих сетей ехать. Потом происхождение маршрута, потом MED, и только в самом конце …
❤2🔥2👍1
Что осталось за кадром: ▪️ Lumen и Cogent из ролика это Tier-1: сети, которые никому не платят за транзит, ядро интернета ▪️ веса из traceroute называются local preference, после них сравнивают длину AS-path: чем меньше сетей до цели, тем лучше маршрут ▪️ RPKI подписывает только владельца префикса, сам путь не проверяется: подписана пока примерно половина маршрутов ▪️ посмотреть свои хопы: tracero…
👍5❤1
Оказалось, что тут есть люди которые не подписаны в инсте, но подписаны тут. Поэтом буду дублировать сюда.
👍16🔥4
Ура!! Нас 2000 человеков🎉, за это вы получаете промокоды на скидку на сайте izidevops.ru я девопс — 40% я нищий девопс — 41% P.S. Все кто уже в этом месяце приобрел лабы получит бесплатный месяц дополнительно ❤️
😁17❤🔥9👍6🎉3
Ошибка в видео и три технических детали, которые не влезли в 2 минуты. Плюс ответ на комментарий про Rust-прослойку. ➖➖➖ ▎1. Моя ошибка: MySQL у GitHub не для кода В ролике сказал «GitHub держит код на MySQL». Точнее MySQL держит метаданные: issues, pull request'ы, users, permissions, ссылки на репо. Сам код лежит в git-репозиториях на файловой системе (packed object store в .git/objects/pack/, DEFLATE + delta co…
❤6🔥5
OpenAI, как масштабируют postgres под 800M юзеров. Разбираю их цифры и где я в ролике упростил. Один мастер + около 50 реплик. Чтения летят на реплики, пишет только мастер, поэтому потолок write-нагрузки это один сервер. Ниже конкретно что у них работает, что чуть не убило и почему они НЕ шардировали postgres. ➖➖➖ ▎1. 50 реплик и лаг возле нуля В ролике я сказал «реплика отстаёт на десятки мс». У OpenAI лаг практ…
🔥11❤6👍2
Kubernetes сам поднимает копии под нагрузку. Разберёмся, как это устроено. В ролике копии приложения множились в чёрную пятницу, гасли ночью, а упавшее восстанавливалось само. За этим стоят конкретные механизмы, давай посмотрим на них. ▎1. Копии живут не сами по себе Поды руками не запускают. Вместо этого описывают Deployment: «хочу три копии этого образа», а контроллер постоянно сравнивает желаемое число копий с …
🔥9👍2❤1
VPN включён. А тебя всё равно видно. Под прошлым видео разгорелся спор: мол, все эти деаноны работают только на древних L2TP и SSTP, а на Xray с Reality такое не прокатит. Reality прячет одну вещь: факт, что ты под VPN, от провайдера. Сайт, который тебя палит, живёт на другом уровне. ➖➖➖ ▎1. Транспорт и браузер это разные слои Reality, uTLS, VLESS, выбор протокола, всё это про транспорт. Как трафик доезжает до с…
❤11👍3🤔1
Всем привет! Запустил тренажёр по Kubernetes. Живые лабы с настоящим kubectl прямо в браузере: Первая лаба бесплатная. А если платить не хочешь, на сайте доработал десятки бесплатных уроков роадмап, теория, разборы, вся обязательная база. izidevops.ru
🔥22😍2❤1🏆1🤝1
Серты, что не влезло в ролик Самое частое и обидное это дата. Внутри серта две метки, начало и конец срока, браузер просто сверяет их с часами системы. Опоздал на минуту, и держи NET::ERR_CERT_DATE_INVALID. Мелочь, скажешь ты, но на этом падали Microsoft Teams в 2020 и Spotify позже. Огромные сервисы легли, потому что забыли продлить серт. Сейчас серты и так живут недолго: публичные CA выдают максимум на 398 дней, а…
👍7❤1
Совершенно абсолютно точно никак не связанная с прошлым постом ссылка реферальная https://my.adminvps.ru/aff.php?aff=31388 которая даст 30% скидку на первый сервер ваш с промокодом izidevops
😁13🔥4
Showing the 12 most recent of 20 posts we hold for @izi_devops. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Пока я делаю ластовый ролик по файловой системе докера, скажите какую тему дальше взять?
- Copy fail уязвимость18%
- Начинать ролики про k8s52%
- Сети, маршруты и тд64%
- Я предложу тебе тему в комментариях2%
The shares total 136%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 13 May 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“izi DevOps” (@izi_devops), 3,120 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/izi_devops.
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.