We are live now (in Ukrainian)! You can join by the YouTube link below. YouTube link
❤8👍4🔥4

Channel
@catops
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
5,076subscribers
-19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001145020158 |
|---|---|
| Type | Channel |
| Username | @catops |
| Created | 22 May 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/catops |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 09:55 | 5,076 | -13 |
| 27 Sept 2026, 06:02 | 5,089 | +2 |
| 15 Sept 2026, 22:20 | 5,087 | +6 |
| 12 Sept 2026, 12:37 | 5,081 | -3 |
| 8 Sept 2026, 18:56 | 5,084 | -2 |
| 31 Aug 2026, 09:16 | 5,086 | -3 |
| 28 Aug 2026, 02:38 | 5,089 | -9 |
| 24 Aug 2026, 23:53 | 5,098 | +6 |
| 21 Aug 2026, 00:22 | 5,092 | +6 |
| 17 Aug 2026, 23:28 | 5,086 | +1 |
| 15 Aug 2026, 01:56 | 5,085 | +2 |
| 12 Aug 2026, 05:08 | 5,083 | -8 |
| 9 Aug 2026, 10:01 | 5,091 | -2 |
| 6 Aug 2026, 14:30 | 5,093 | -2 |
| 6 Aug 2026, 04:01 | 5,095 | no change |
| 6 Aug 2026, 03:54 | 5,095 | first reading |
23 posts held, back to 7 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 8 pages 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 23 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
111 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 53.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 59 | 53.2% | |
| 👍 | 31 | 27.9% | |
| 🔥 | 20 | 18.0% | |
| 😱 | 1 | 0.901% |
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 21 of the 23 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 126 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 7 July 2026 to 9 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.
We are live now (in Ukrainian)! You can join by the YouTube link below. YouTube link
❤8👍4🔥4
A new issue of the CatOps digest is live! https://newsletter.catops.dev/p/catops-digest-2026-08-07 #digest #newsletter
❤3
If you have nothing to do this Sunday and you understand Ukrainian, join us for a live discussion about AI in the DevOps-ish field at 11:00 UTC (14:00 Kyiv / 13:00 Berlin). YouTube link
🔥14❤1
An interesting article that explains how Karpenter works. It does have flaws, though. Apart from useless footnotes, it doesn’t elaborate on how did they address the behavior, only some abstract suggestions, some of which kinda contradict what Karpenter actually is. Spoiler: their fix is a separate node pool. You can learn it from this thread on Reddit. Otherwise, it’s a good article and a good thread. #kubernetes…
❤4
An article from Anthropic on the AI agents evaluation strategies, basically test strategies for AI agents. It's an interesting read, even if you do not create your own agents. There are also some interesting points in the difference of evaluating a coding agent vs a communication agent (customer support, etc.), as well as examples of the metrics you can use for that. Besides, you can use the ideas from this article…
👍3
For today's Donations Monday, I'd like to remind you about a big fundraiser by DOU for the 2nd separate corps of the National Guard of Ukraine «Хартія». The goal of this fundraiser is to buy heavy bomber drones "Vampire" for the Kupiansk direction. Monobank jar: https://send.monobank.ua/jar/26mrQPQ3PZ #donations #Ukraine
❤6
An interesting article by Coroot on reproducing split brain on CloudNativePG. Regardless of whether or not you use CloudNativePG, it's a good example of chaos testing. Chaos testing is about an experiment: here they define a clear gap in certainty (what would happen if?) and tested it. The article also has some recommendations on CloudNativePG configuration, if you're using it. #databases #postgres #kubernetes
👍1🔥1
A book bundle on Python, Rust, and Data by O’Reilly on Humble Bundle. https://www.humblebundle.com/books/python-rust-and-data-oreilly-books The bundle is active for 18 more days. Enjoy! #books
❤3
You likely already know about the recent security incident that involves OpenAI and Hugging Face, when a model escaped its containment to cheat an evaluation test and hacked Hugging Face in the process. Now, postmortems are available from both OpenAI and Hugging Face. - Initial incident disclosure by Hugging Face - Postmortem by Hugging Face - Postmortem by OpenAI This is quite interesting read. On one hand, in the…
👍7❤2
Being a good communicator is becoming more and more important in the world, where more and more code is generated. 15 principles for managing up is an article with some tips that can help you not only get on a better foot with your manager, but also to become a better colleague in general. I personally so not like the term “managing up”, but I guess you have to call it somehow. #culture #mgmt
👍4
We continue with a fundraiser a pickup truck for the 423rd battalion. Right now, one jar has 218/350k raised, and the other one 37/50k. Jar 1: https://send.monobank.ua/jar/2aMqtZT592 Jar 2: https://send.monobank.ua/jar/8oTyqJUjPV #donations #Ukraine
❤5
Another book bundle on HumbleBundle. This one is about software architecture. Hopefully, you’d find something interesting there. https://www.humblebundle.com/books/software-architecture-apress-books #books
Showing the 12 most recent of 23 posts we hold for @catops. 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.
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.
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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“CatOps” (@catops), 5,076 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/catops.
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.