1 сентября разбираем реальные вакансии Junior DevOps🔥 Новый учебный год — хороший повод начать что-то новое. На этот раз — понятный план, как войти в DevOps и на какую зарплату рассчитывать Что будет: 1️⃣Живой разбор вакансий Разбираем требования и объясняем простым языком, что на самом деле стоит за каждым пунктом. 2️⃣Технический перевод Что на самом деле значит «знание K8s» для Junior. Сложное — простыми словами.…

Channel
Записки IT специалиста
@interface31
On this record: Topic · Growth · Engagement · Reactions · Stars · Advertising · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
8,987subscribers
+48 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001350557178 |
|---|---|
| Type | Channel |
| Username | @interface31 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 24 September 2026 |
| On Telegram | t.me/interface31 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 24 Sept 2026, 21:19 | 8,987 | +13 |
| 17 Sept 2026, 03:21 | 8,974 | +2 |
| 13 Sept 2026, 03:39 | 8,972 | +5 |
| 8 Sept 2026, 19:17 | 8,967 | -1 |
| 3 Sept 2026, 19:19 | 8,968 | +12 |
| 31 Aug 2026, 07:55 | 8,956 | -2 |
| 27 Aug 2026, 21:15 | 8,958 | +5 |
| 25 Aug 2026, 01:53 | 8,953 | +7 |
| 21 Aug 2026, 11:28 | 8,946 | +1 |
| 18 Aug 2026, 19:48 | 8,945 | +6 |
| 12 Aug 2026, 06:28 | 8,939 | +6 |
| 9 Aug 2026, 15:14 | 8,933 | -10 |
| 6 Aug 2026, 14:03 | 8,943 | +4 |
| 6 Aug 2026, 06:45 | 8,939 | no change |
| 6 Aug 2026, 06:38 | 8,939 | first reading |
Engagement
97 posts held, back to 30 July 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 35 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.68%
- avg views ÷ 8,987 subscribers
- Avg views / post
- 241
- 1 post measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 1
- of 97 held
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 28 August 2026 |
|---|---|
| Posts held | 97 (30 July 2026 – 28 August 2026) |
| Views total | 241 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 15:49 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.
Reaction mix
1,426 reactions across 82 posts, in 21 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 855 | 60.0% | |
| ❤ | 111 | 7.78% | |
| 🔥 | 85 | 5.96% | |
| 💯 | 63 | 4.42% | |
| 🤡 | 54 | 3.79% | |
| 🤔 | 48 | 3.37% | |
| 👌 | 38 | 2.66% | |
| 🥱 | 38 | 2.66% | |
| 🤮 | 34 | 2.38% | |
| 👎 | 30 | 2.10% | |
| 😱 | 13 | 0.912% | |
| 🤣 | 12 | 0.842% | |
| 😁 | 11 | 0.771% | |
| 👀 | 10 | 0.701% | |
| 🤝 | 7 | 0.491% | |
| 🫡 | 7 | 0.491% | |
| ⚡ | 3 | 0.21% | |
| 👨💻 | 3 | 0.21% | |
| 🤯 | 2 | 0.14% | |
| 🍌 | 1 | 0.07% | |
| 1 further kind | 1 | 0.07% |
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 89 of the 97 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 1,547 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 97 most recent posts we hold, published 30 July 2026 to 28 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
- 12
- across the posts below
- Posts paid on
- 6
- of 97 we hold a reading for · 6%
- Most on one post
- 5
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @interface31. 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 97 most recent posts we hold for this entry, published 30 July 2026 to 28 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.
Advertising
- Ad load
- 14.4%
- 14 of 97 posts carry an ad marker
- Regulatory tokens
- 14
- posts carrying an erid · 14 distinct tokens
- Median views · ads
- 956
- over 14 measured posts
- Median views · rest
- 1,620
- over 83 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2W5zFGHyh6Z | 1 | 12 August 2026 | 12 August 2026 |
| 2W5zFGapU7K | 1 | 28 August 2026 | 28 August 2026 |
| 2W5zFGdSdBf | 1 | 26 August 2026 | 26 August 2026 |
| 2W5zFGgXJcq | 1 | 11 August 2026 | 11 August 2026 |
| 2W5zFGuUhM3 | 1 | 18 August 2026 | 18 August 2026 |
| 2W5zFHDKaDP | 1 | 25 August 2026 | 25 August 2026 |
| 2W5zFHrv9xM | 1 | 7 August 2026 | 7 August 2026 |
| 2W5zFJD2hg5 | 1 | 12 August 2026 | 12 August 2026 |
| 2W5zFJWwGzV | 1 | 19 August 2026 | 19 August 2026 |
| 2W5zFJYNEs3 | 1 | 18 August 2026 | 18 August 2026 |
| 2W5zFJdJ5gM | 1 | 19 August 2026 | 19 August 2026 |
| 2W5zFJnKQ7j | 1 | 24 August 2026 | 24 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it. 2 further tokens are held for this entry and not listed here.
Measured over the 97 most recent posts we hold, published 30 July 2026 to 28 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Как сделать QR-код для доступа к Wi-Fi при помощи PowerShell Пароль для беспроводной сети – головная боль системного администратора. Сделать его простым – очень скоро его будет знать каждый первый. Сделать сложным – сам утомишься вводить. Отличный выход из этой ситуации – генерация специального QR-кода для автоматической настройки Wi-Fi. Сделать это совсем не сложно, нам только понадобится дополнительный модуль Pow…
🔥9🤮2🥱1
Клиент просит бэкап и DRaaS, а своей инфраструктуры у вас нет Вы ведёте ИТ у нескольких компаний. Приходит запрос — вынести 1С в облако, поднять терминальный сервер, настроить бэкап под 152-ФЗ. Строить под это своё железо смысла нет, и запрос уходит на сторону вместе с деньгами. Партнёрская программа LanCloud закрывает этот разрыв. Клиента ведёте вы. Мы берём инфраструктуру: помогаем подобрать конфигурацию, рассчит…
И как вы думаете, что это такое? Это скриншот из одного отеля в Дагестане, где я провел летний отпуск. Причем это не какой-то мелкий отель или гостевой дом, это дорогой сетевой отель 5 звезд уровня полный пансион. А весь выход во внешнюю сеть там организован через Cloudflare WARP, просто и «без палева». Хотя владельцев отеля понять можно – отель дорогой, зачем причинять неудобства тем, кто везет тебе деньги. В оста…
👍5❤1
Posted without readable text
🔥11👍8👌6❤1
...каждый раз думаете вы, когда видите у себя в подписках очередной ИТ-канал с проходным контентом. «Кучевые АйТи» вас точно не разочарует. Здесь нет нейрослопа — только редакционные материалы на тему облачных технологий. Ребята пишут о новых сервисах, влиянии ИИ на инфраструктуру и сети, тенденциях ИТ-рынка и берут интервью у экспертов ведущих ИТ-компаний. Читайте в канале: — Виртуальную машину с белым IP начинают…
Веселые картинки Недавно один из коллег снова притащил ссылку на «хороший материал по сегментации» на известный репозиторий на гитхабе: https://github.com/sergiomarotco/Network-segmentation-cheat-sheet К сожалению, я не могу считать данный материал хорошим и тем более рекомендовать его, хотя автор и ссылается на некие «лучшие практики». Почему? Начнем издалека, с принципов построения обучающих материалов. Хороший…
👍10❤4🥱1
Posted without readable text
👍1
Версии PowerShell PowerShell активно используется Windows-администраторами для автоматизации и написания скриптов, но далеко не все правильно ориентируются в версиях и выпусках PowerShell, поэтому сегодня разберем этот вопрос подробнее. На сегодняшний день существуют две версии PowerShell: 🔹 Windows PowerShell – основан на .NET Framework, существует только для Windows, предустановлен начиная с Windows Server 2008 …
👍20😱3👌1
Пойду смотреть, как и зачем команда Deckhouse сводит свои продукты в одну платформу. Сейчас у них целая экосистема инфраструктурных решений. 17.09.26 в 12:00 коллеги объяснят, что меняется. Особенно для тех, у кого рядом живут контейнеры, виртуалки и ИИ-нагрузки. Отдельно обещают сценарии для частных облаков и платформ данных. Если у вас инфраструктура размазана по нескольким средам, послушайте вместе со мной
История Windows NT Windows NT без преувеличения можно назвать ключевой системой для Microsoft, именно она и заложенные в нее технологии заложила ту основу, которую системы Windows используют сейчас. Начиная с Windows XP закончилось деление ОС Windows на пользовательскую и профессиональную линейку и дальше пошла развиваться именно линия NT и сегодня, запуская Windows 10 или 11 мы имеем под капотом потомка той самой …
👍8❤1
С днем рождения Linux! 25 августа 1991 года в рассылке новостей группы пользователей OC MINIX появилось сообщение: всем пользователям minix! Я пишу (бесплатную) операционную систему (это просто хобби, ничего большого и профессионального вроде gnu) для AT 386(486). Я вожусь с этим с апреля, и она, похоже, скоро будет готова. Напишите мне, кому что нравится/не нравится в minix, поскольку моя ОС на неё похожа (кроме…
👍34❤11
Showing the 12 most recent of 97 posts we hold for @interface31. 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.
Укажите наиболее часто используемый, можно выбрать несколько вариантов
- VMware32%
- Hyper‑V30%
- Proxmox VE63%
- Linux KVM9%
- XenServer0%
- XCP-ng1%
- Российские гипервизоры5%
- Bhyve0%
- Другое (напишу в комментариях)1%
- Просто посмотреть ответы4%
The shares total 145%, 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 97 most recent posts we hold, published 30 July 2026 to 28 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.
Forward network
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.
Mentions
Named by 2 registered channels — 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@srv_admin · 32,572
Telegram ranks this channel #1 of 96 here — alongside 95 others — read 5 September 2026
@i_odmin · 26,669
Telegram ranks this channel #9 of 89 here — alongside 88 others — read 12 September 2026
@sysodmins · 38,088
Telegram ranks this channel #10 of 93 here — alongside 92 others — read 31 August 2026
@sysadmin_library · 25,649
Telegram ranks this channel #15 of 85 here — alongside 84 others — read 13 September 2026
@remontka_pro · 26,197
Telegram ranks this channel #18 of 77 here — alongside 76 others — read 13 September 2026
@bashdays · 23,634
Telegram ranks this channel #19 of 94 here — alongside 93 others — read 18 September 2026
@Selectel · 63,289
Telegram ranks this channel #30 of 96 here — alongside 95 others — read 21 August 2026
@rebrain_devops · 28,873
Telegram ranks this channel #41 of 94 here — alongside 93 others — read 9 September 2026
@AlexKvazis · 23,517
Telegram ranks this channel #44 of 82 here — alongside 81 others — read 18 September 2026
@tech_debunker · 23,964
Telegram ranks this channel #56 of 89 here — alongside 88 others — read 17 September 2026
@school_network · 26,588
Telegram ranks this channel #56 of 85 here — alongside 84 others — read 12 September 2026
@devopsforlove · 44,673
Telegram ranks this channel #79 of 95 here — alongside 94 others — read 9 September 2026
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 24 September 2026 — this entry's latest reading, not the date you are reading this.
“Записки IT специалиста” (@interface31), 8,987 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/interface31.
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.