30 Jul 2026, 07:07 UTC≈442 views9 reactionsread 6 August 2026
Photo
Со вчерашнего вечера у многих разрабов "выходной" :D Отдыхаешь? Или перешел на другого провайдера? #Claude #incidents
Signed Mikhail Savin
Channel
Мишка на сервере
@jtprogru_channel
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,277subscribers
+16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001006744436 |
|---|---|
| Type | Channel |
| Username | @jtprogru_channel |
| Created | Between 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/jtprogru_channel |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 16 Sept 2026, 07:39 | 1,277 | +1 |
| 12 Sept 2026, 13:57 | 1,276 | +2 |
| 3 Sept 2026, 11:59 | 1,274 | +2 |
| 31 Aug 2026, 06:26 | 1,272 | -1 |
| 28 Aug 2026, 06:09 | 1,273 | +2 |
| 24 Aug 2026, 22:14 | 1,271 | +2 |
| 21 Aug 2026, 19:06 | 1,269 | +1 |
| 15 Aug 2026, 20:07 | 1,268 | +5 |
| 9 Aug 2026, 09:11 | 1,263 | +1 |
| 6 Aug 2026, 09:00 | 1,262 | +1 |
| 6 Aug 2026, 08:15 | 1,261 | no change |
| 6 Aug 2026, 03:53 | 1,261 | first reading |
Engagement
19 posts held, back to 11 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 19 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
27 Jul 2026, 16:44 UTC≈1,710 views13 reactionsread 6 August 2026
Photo
SRE Mind map Просто оставлю это тут: https://jtprogru.github.io/The-Way-of-SRE/mindmap/ Заходи, знакомься и накидывай PR/issues с полезностями! #TheWayofSRE #TWoSRE #Github #SRE #DevOps
Signed Mikhail Savin
20 Jul 2026, 15:28 UTC≈740 views8 reactionsread 6 August 2026
Photo
Что происходит, когда ты открываешь сайт Спойлер: этот вопрос не зря любят на собеседованиях — по тому, где кандидат останавливается, видно всю его карту знаний. И полезен он не ради галочки: когда знаешь, из каких этажей состоит путь, «сайт тормозит» перестаёт быть магией и превращается в конкретный этаж, на котором надо копать. https://jtprog.ru/posts/what-happens-when-you-open-website/ Как дочитаешь – приходи р…
Signed Mikhail Savin
18 Jul 2026, 18:36 UTC≈666 views9 reactionsread 6 August 2026
Я слышу, как модель думает И это буквально, а не метафорически. https://habr.com/ru/articles/1060510/ #habr #SRE #DevOps #LLM #LMStudio
Signed Mikhail Savin
14 Jul 2026, 12:25 UTC≈884 views7 reactionsread 6 August 2026
Photo
Как облачная синхронизация тихо ломает git и как это чинить Главный тезис статьи: порча объектов git — это не потеря данных, если жив origin. А раздутый .git лечится только переписью истории, и никак иначе. Разберём оба случая до винтика — с теорией, диагностикой и командами, которые можно копировать. https://jtprog.ru/posts/cloud-sync-breaks-git/ #Git #Blog #Post #iCloud #CloudSync
Signed Mikhail Savin
8 Jul 2026, 05:54 UTC≈898 views8 reactionsread 6 August 2026
Как ставить задачи ~~начальнику~~ AI-агенту? Привет, %vibecodername%! Тут мой дорогой друг и товарищ по палате через неделю собирается провести в онлайне мастер-класс по теме постановки задач для AI-агентов. Для тех, кто как и я относится к категории «лучше один раз покажите, чем сто раз поясните» – мой персональный рекомендосьён! #SipkiTech #AgenticAI #AgenticDevelopment
Signed Mikhail Savin
7 Jul 2026, 09:42 UTC≈773 views9 reactionsread 6 August 2026
NeoVim Pack UI Привет, %username%! Я довольно давно живу на nvim (локальный алиас v для упрощения жизни) и все, кто следит/использует его, заметили, что появился встроенный менеджер плагинов vim.pack. С этим менеджером плагинов все отлично, кроме одного – у него из коробки нету никакого UI (да, я слишком сильно привык к Lazy / Mason) и мне очень сильно хотелось более наглядного взаимодействия с vim.pack. Короче, д…
Signed Mikhail Savin
23 Jun 2026, 07:35 UTC≈888 views10 reactionsread 6 August 2026
Просто оставлю это тут! Пока я в Питере на SHL, тут наконец-то дооформился АОТ! Саша Титов говорил «первые упоминания этого делались еще 8 лет назад» - свершилось! Ребята, вы крутые! Теперь жду задачу на эссе ;) https://habr.com/ru/companies/open-aot/news/1050314/
Signed Mikhail Savin
19 Jun 2026, 09:54 UTC≈784 views7 reactionsread 6 August 2026
Video
Впервые в истории кибербитвы Standoff все виртуальное Государство F погрузилось во тьму 🌃 Команда Dataeli&only_f4st реализовала одно из самых масштабных межотраслевых критических событий — вывела из строя все электроподстанции. Это случилось впервые за все 10 лет битвы. Реализовать атаку получилось за 20 шагов Полтора миллиона человек остались без света. Парализована работа метро и другого общественного транспорта…
Signed Mikhail Savin
15 Jun 2026, 05:47 UTC≈825 views4 reactionsread 6 August 2026
Photo
Как объяснить маме, папе, бабушке и дедушке, что такое сложный пароль Гайд для немолодых родственников: как придумать сложный пароль по NIST SP 800-63B, поставить менеджер паролей и включить 2FA — без боли и паники. https://jtprog.ru/posts/passwords-for-parents/
Signed Mikhail Savin
13 Jun 2026, 09:26 UTC≈866 views11 reactionsread 6 August 2026
The Way of SRE – куда смотреть если хочешь понять SRE Я долго откладывал эту тему, но видимо пришло время. Смотри, знакомься, изучай и предлагай улучшения: https://jtprogru.github.io/The-Way-of-SRE/ Проект открытый, PR приветствуются: новым листьям, правкам, ссылкам на материалы. Исходники на GitHub, сайт сделан на Astro Starlight и деплоится на GitHub Pages автоматически. #SRE #TheWayofSRE
Signed Mikhail Savin
8 Jun 2026, 06:04 UTC≈913 views11 reactionsread 6 August 2026
Photo
Надёжность строится в диалоге с бизнесом SLO становится контрактом только через error budget policy. Диалог о надёжности с бизнесом, System Design-кейсы про SLO и метрики SRE при мультипродукте. https://jtprog.ru/posts/reliability-is-a-conversation/ Это продолжение темы в сторону диалога с бизнесом – то, чего не хватало в прошлой статье. #SRE #SLO #ErrorBudget #SystemDesign #Reliability
Signed Mikhail Savin
Showing the 12 most recent of 19 posts we hold for @jtprogru_channel. 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.
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.
IT STAND
@ITSTAND_ORG · 151,441
Telegram ranks this channel #20 of 98 here — alongside 97 others — read 9 September 2026
@ITSTAND_ORG · 151,441
Telegram ranks this channel #20 of 98 here — alongside 97 others — read 9 September 2026
DevOps community for love
@devopsforlove · 44,673
Telegram ranks this channel #73 of 95 here — alongside 94 others — read 9 September 2026
@devopsforlove · 44,673
Telegram ranks this channel #73 of 95 here — alongside 94 others — read 9 September 2026
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Мишка на сервере” (@jtprogru_channel), 1,277 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/jtprogru_channel.
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.