clawk Give coding agents a disposable Linux VM, not your laptop https://github.com/clawkwork/clawk

Channel
DevOps&SRE Library
@devopslibrary
On this record: Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Telegram's recommendations · Cite this entry
19,757subscribers
+87 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 | -1001329220738 |
|---|---|
| Type | Channel |
| Username | @devopslibrary |
| Description | Библиотека статей по теме DevOps и SRE. Реклама: @ostinostin Контент: @mxssl РКН: https://www.gosuslugi.ru/snet/67704b536aa9672b963777b3 |
| Created | 21 April 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/devopslibrary |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 08:06 | 19,757 | +5 |
| 20 Aug 2026, 19:42 | 19,752 | +10 |
| 19 Aug 2026, 22:05 | 19,742 | -1 |
| 18 Aug 2026, 20:53 | 19,743 | +10 |
| 17 Aug 2026, 19:45 | 19,733 | +6 |
| 16 Aug 2026, 15:38 | 19,727 | +8 |
| 14 Aug 2026, 21:48 | 19,719 | +11 |
| 12 Aug 2026, 07:54 | 19,708 | +9 |
| 11 Aug 2026, 05:58 | 19,699 | +2 |
| 10 Aug 2026, 08:11 | 19,697 | +18 |
| 8 Aug 2026, 03:01 | 19,679 | +5 |
| 7 Aug 2026, 03:06 | 19,674 | +4 |
| 6 Aug 2026, 04:00 | 19,670 | no change |
| 6 Aug 2026, 03:53 | 19,670 | first reading |
Engagement
64 posts held, back to 29 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 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 12.2%
- avg views ÷ 19,757 subscribers
- Avg views / post
- 2,420
- 64 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 64
- of 64 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 22 August 2026 |
|---|---|
| Posts held | 64 (29 July 2026 – 22 August 2026) |
| Views total | 154,835 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 21:43 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
- ≈431
- Videos
- ≈2
- Links
- ≈5,450
Lifetime counters from Telegram’s own channel header, read 22 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
- 1m 59s
- Average length
- 1m 59s
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.
Advertising
- Ad load
- 17.2%
- 11 of 64 posts carry an ad marker
- Regulatory tokens
- 11
- posts carrying an erid · 11 distinct tokens
- Median views · ads
- 2,540
- over 11 measured posts
- Median views · rest
- 2,530
- over 53 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 |
|---|---|---|---|
| 2VtzquZctk3 | 1 | 10 August 2026 | 10 August 2026 |
| 2VtzqvHEFpX | 1 | 11 August 2026 | 11 August 2026 |
| 2VtzqvY8GGz | 1 | 29 July 2026 | 29 July 2026 |
| 2VtzqvYKd9d | 1 | 17 August 2026 | 17 August 2026 |
| 2VtzqvfVsqU | 1 | 3 August 2026 | 3 August 2026 |
| 2Vtzqvqgags | 1 | 12 August 2026 | 12 August 2026 |
| 2VtzqvwpkP4 | 1 | 6 August 2026 | 6 August 2026 |
| 2VtzqwcGyWj | 1 | 19 August 2026 | 19 August 2026 |
| 2VtzqxCannf | 1 | 20 August 2026 | 20 August 2026 |
| 2VtzqxWDJ2v | 1 | 3 August 2026 | 3 August 2026 |
| 2W5zFGTNqcD | 1 | 17 August 2026 | 17 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.
Measured over the 64 most recent posts we hold, published 29 July 2026 to 22 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
☁☁☁☁☁☁☁ 24 сентября Yandex Cloud проведёт Yandex Scale 2026 — флагманскую технологическую конференцию, посвящённую облачным технологиям, инфраструктуре и искусственному интеллекту. 🎨🎨🎨🎨🎨🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨🎨🎨🎨🎨 В программе четыре продуктовых трека — AI, Data, Security и Hybrid Infrastructure & DevOps, — и отдельный углублённый технологический трек DeepTech, который пройдёт только онлайн. В треке Hybrid Infrastru…
destructive_command_guard A high-performance hook for AI coding agents that blocks destructive commands before they execute, protecting your work from accidental deletion across Claude Code, Codex CLI, Gemini CLI, Copilot CLI, VS Code Copilot Chat, Cursor, Hermes Agent, Grok (xAI), and related tools. https://github.com/Dicklesworthstone/destructive_command_guard
The git history command deserves more attention Working with lots of changes in parallel on git can be painful. You end up juggling branches and commits, and running scary rebase -i commands that can leave your tree in a half-broken state if you so much as sneeze. https://lalitm.com/post/git-history
htop explained Explanation of everything you can see in htop/top on Linux https://peteris.rocks/blog/htop
You probably don't need another database Do you really need separate systems for caching, queues, search, documents, and vector embeddings when you already have Postgres? https://postgresisenough.dev
Бесплатный курс про ИИ для DevOps, SRE и инженеров Слёрм собрал бесплатный курс в записи «ИИ для инженеров: польза и риски». Он для тех, кто уже пробовал использовать ИИ в рабочих задачах или только присматривается, но хочет понимать, где модель действительно помогает, а где лучше сначала открыть логи и подумать самому. В курсе 6 записанных занятий, материалы и самостоятельная практика. Разбираются прикладные сцен…
Karpenter + Cluster API https://a-cup-of.coffee/blog/karpenter-capi-ovh
kloak Kloak transparently intercepts outbound TLS traffic in Kubernetes using eBPF uprobes, replacing hashed placeholders with real secrets at the kernel level before encryption. Applications never handle actual credentials, and no sidecars or code changes are required. https://github.com/spinningfactory/kloak
🔐 Средства защиты в ядре Linux — это фундамент безопасности всей системы. Если вы хотите понимать: ❔ как защищается ядро; ❔ почему работают SELinux, AppArmor, KASLR и PTI ❔ как проверить защищённость системы на практике, этот практикум для вас. 🗓 20 августа в 20:00 МСК приглашаем вас на открытый урок в преддверии старта курса «Разработка ядра Linux». Разберём: • модели DAC и MAC; • механизмы защиты ядра; • парамет…
Kubernetes Native FQDN Based Egress Network Policies Kubernetes Network Policies are powerful, but when it comes to allowing egress access to specific domains, things get tricky. Most real world applications don't connect to fixed IPs, they rely on third-party APIs, cloud services, and CDNs with dynamic DNS records. In this post, I'll take you through the motivation behind building FQDN-Controller, how it works unde…
Optimizing node and pod startup performance We at Outreach are working hard to improve performance of our platform for our clients. Reducing startup times of nodes and pods can have positive impact on performance and cost as well. I am part of our infrastructure team focusing on AWS and Kubernetes and I recently implemented several improvements in node and startup time. I decided to share some of them in this articl…
Showing the 12 most recent of 64 posts we hold for @devopslibrary. 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
Citation-graph rank — 736,977 of 1,583,249entries 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 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.
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.
@linuxgram · 72,798
Telegram ranks this channel #76 of 90 here — alongside 89 others — read 19 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“DevOps&SRE Library” (@devopslibrary), 19,757 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/devopslibrary.
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.