Telegram RegisterThe public register of Telegram

Channel

Библиотека девопса | DevOps, SRE, Sysadmin

@devopsslib

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

10,404subscribers

-7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001261760700
TypeChannel
Username@devopsslib
DescriptionВсе самое полезное для девопсера в одном канале. Наши курсы: https://clc.to/ZJ7Z1w По рекламе: @proglib_adv Для обратной связи: @proglibrary_feeedback_bot РКН: https://gosuslugi.ru/snet/6798b4e4509aba56522d1787
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/devopsslib

Growth

10,40410,41210,4086 August 2026 — 10,411 subscribers6 August 2026 — 10,411 subscribers7 August 2026 — 10,412 subscribers8 August 2026 — 10,410 subscribers10 August 2026 — 10,405 subscribers11 August 2026 — 10,404 subscribers6 August 202611 August 2026
6 measurements spanning 4 days, net -7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 10,403–10,413 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 04:4210,404-1
10 Aug 2026, 07:5510,405-5
8 Aug 2026, 06:0410,410-2
7 Aug 2026, 05:0310,412+1
6 Aug 2026, 18:4510,411no change
6 Aug 2026, 18:3510,411first reading

Engagement

20 posts held, back to 21 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
8.77%
avg views ÷ 10,404 subscribers
Avg views / post
913
20 posts measured
Reaction rate
0.739%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 15 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (21 July 20268 August 2026)
Views total18,251
Reactions total110
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 05:09 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.

What this channel posts

Photos
2,040
Videos
83
Links
3,510

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
8s
Average length
8s

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.

Reaction mix

110 reactions across 15 posts, in 12 distinct kinds. The most used accounts for 34.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
3834.5%
👍2522.7%
2018.2%
😁87.27%
🔥54.55%
🎉43.64%
🤩43.64%
💯21.82%
🌚10.909%
👾10.909%
😢10.909%
🤔10.909%

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 15 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 110reactions 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 21 July 2026 to 8 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.

Recent posts

8 Aug 2026, 18:20 UTC752 views1 reactionsread 13 August 2026
Photo

0️⃣ Калькулятор для сравнения облака и собственной инфраструктуры Когда нужно решить, где разворачивать инфраструктуру — в облаке или на своих серверах — начинается головная боль. Цифры нужны точные, но переменных слишком много: железо, электричество, зарплаты, лицензии, безопасность. Excel быстро превращается в хаос. InfraWise — открытый инструмент, который считает полную стоимость владения (TCO) для облачной и on

👍1

8 Aug 2026, 17:41 UTC431 viewsread 13 August 2026
Forwarded from @proglib_academyPhoto

🤔 У большинства разработчиков уже есть подписки на IDE, GitHub Copilot, Claude, ChatGPT или облачные сервисы. Логично, что обучение тоже постепенно приходит к той же модели: не покупать отдельный курс под каждую новую тему, а иметь доступ ко всей библиотеке и выбирать, что актуально именно сейчас. Такой формат недавно появился и в Proglib Academy. Вместо одного курса — доступ сразу ко всей библиотеке и новым матери

8 Aug 2026, 17:41 UTC700 viewsread 13 August 2026

Кажется, у онлайн-обучения появился формат, которого давно не хватало 👇

31 Jul 2026, 11:05 UTC≈1,200 views6 reactionsread 13 August 2026
Photo

🤔 Вопрос от подписчика: как обновляете stateful-приложения без downtime? Со stateless всё относительно просто — rolling update обычно хватает. А вот со stateful начинаются нюансы: — миграции БД; — WebSocket и gRPC-соединения; — rollback; — совместимость старой и новой версии. Кто-то использует Blue-Green, кто-то expand/contract для миграций, кто-то вообще предпочитает небольшое окно обслуживания вместо усложнения

5🌚1

30 Jul 2026, 13:26 UTC≈1,050 views42 reactionsread 13 August 2026
Forwarded from @devops_problems_lib

Что делает ConfigMap в Kubernetes? 👾 — Управляет сетевым трафиком 👍 — Хранит большие наборы данных 🥰 — Управляет секретами приложений ⚡️ — Отделяет конфигурацию от кода приложения Библиотека задач по DevOps

38👍2👾1😢1

29 Jul 2026, 15:31 UTC≈1,130 views5 reactionsread 13 August 2026

🔐 Как не пропустить истечение сертификата Истёкший сертификат может остановить сервис. Чтобы этого не произошло, достаточно настроить пару простых проверок. ➡️ В Kubernetes (cert-manager) Проверить сертификаты: kubectl get certificates -A Если используете kube-prometheus-stack, можно добавить алерт: - alert: CertExpiringSoon expr: certmanager_certificate_expiration_timestamp_seconds - time() < 7 * 24 * 3600

👍5

29 Jul 2026, 12:50 UTC592 views2 reactionsread 13 August 2026
Forwarded from @proglib_academyPhoto

😱 Знакомо? Лимит уже закончился, а задача всё ещё не готова. Часть токенов могла уйти на повторное чтение файлов, лишний контекст и неудачные попытки. ⚡️ Этому посвящён отдельный блок курса «ИИ для разработчиков». Вы разберёте расходы на собственных проектах, сравните подходы и найдёте места, где агент выполняет лишнюю работу. В итоге станет понятнее, сколько ресурсов выделять на запуск, когда его останавливать и в

👍2

29 Jul 2026, 12:50 UTC840 viewsread 13 August 2026

Куда на самом деле уходят токены во время агентного кодинга? 😧

28 Jul 2026, 14:03 UTC982 views6 reactionsread 13 August 2026
Photo

🌍 us-east-1 снова лёг. Значит ли это, что пора переходить на multi-region? Несмотря на статус самого крупного региона AWS, именно us-east-1 регулярно оказывается в центре крупных инцидентов. В июле проблемы затронули Lambda, CloudFormation и Management Console. В отчёте IncidentHub за H1 2026 этот регион снова оказался лидером по суммарному времени недоступности. Построение multi-region повышает отказоустойчивость,

👍4🔥1🤔1

27 Jul 2026, 12:51 UTC≈1,060 views5 reactionsread 13 August 2026

💡 Почему облака ломаются: главные выводы отчётов за 2026 год IncidentHub изучил более 30 тысяч сбоев у 1082 облачных и SaaS-провайдеров за первую половину 2026 года. Больше всего инцидентов пришлось на облачные платформы и инструменты разработчиков. 🔴 Один из главных выводов: плохие изменения распространяются по инфраструктуре так же быстро, как хорошие. В распределённых системах новая конфигурация может за минуты

3👍2

26 Jul 2026, 14:03 UTC988 views3 reactionsread 13 August 2026
Forwarded from @php_problems_libPoll

Преимущество __serialize()/__unserialize() (PHP 7.4) над __sleep()/__wakeup()?

  1. Быстрее в 10 раз23%
  2. Возвращает/принимает произвольный массив32%
  3. Работает без объявления в классе23%
  4. Автоматически даёт JSON22%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

3

25 Jul 2026, 15:03 UTC936 views9 reactionsread 13 August 2026

📍 Шпаргалка по циклам в Bash Чтобы не держать в голове всю синтаксическую магию, собрали удобные примеры: for, while, until, диапазоны, чтение файлов и даже управление потоком с break и continue. 🈂️ Цикл for в Bash: for i in /etc/*; do echo $i done # То же самое (альтернативный синтаксис), также работает с другими видами циклов for i in /etc/* do echo $i done 🈂️ Цикл for, как в C: for ((i = 0; i < 100; i+

🎉43🔥2

Showing the 12 most recent of 20 posts we hold for @devopsslib. 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.

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.

26 Jul 2026, 14:03 UTCAnonymous Quiz168 voters

Преимущество __serialize()/__unserialize() (PHP 7.4) над __sleep()/__wakeup()?

  1. Быстрее в 10 раз23%
  2. Возвращает/принимает произвольный массив32%
  3. Работает без объявления в классе23%
  4. Автоматически даёт JSON22%

Shares as published. No per-option vote count is published by Telegram, so none is 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 21 July 2026 to 8 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.

Citation-graph rank

Citation-graph rank — 663,876 of 1,160,990entries 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.

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 8 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.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Библиотека девопса | DevOps, SRE, Sysadmin” (@devopsslib), 10,404 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/devopsslib.

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.