Telegram RegisterThe public register of Telegram

Channel

Трифонов_IT

@trifonovit

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

592subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001984828518
TypeChannel
Username@trifonovit
DescriptionПривет, я Миша Head of Development Cloud.ru. Пишу здесь о личном опыте, инсайтах и закулисье IT. Внутрянка профессии без прикрас. #menu - навигация
Created6 June 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/trifonovit

Growth

5927 Aug 2026, 12:59 — 592 subscribers8 Aug 2026, 03:18 — 592 subscribers7 Aug 2026, 12:598 Aug 2026, 03:18
2 measurements taken within a single day. 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 591–593 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 03:18592no change
7 Aug 2026, 12:59592first reading

Engagement

14 posts held, back to 25 May 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
44.3%
avg views ÷ 592 subscribers
Avg views / post
262
2 posts measured
Reaction rate
4.20%
reactions ÷ views · ER floor
Posts in window
2
of 14 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 July 2026
Posts held14 (25 May 202518 July 2026)
Views total524
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:18 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
51
Videos
21
Links
44

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
2m 24s
Average length
1m 12s

Measured directly from 2 videos 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

215 reactions across 14 posts, in 11 distinct kinds. The most used accounts for 58.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12558.1%
❤‍🔥2612.1%
😁2511.6%
177.91%
🎉73.26%
🥰62.79%
🤔31.40%
20.93%
😎20.93%
👌10.465%
👍10.465%

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 14 of the 14 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 215reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 25 May 2025 to 18 July 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

18 Jul 2026, 13:29 UTC287 views15 reactionsread 8 August 2026

С Сашей Поломодовым(@book_cube) вчера случайно заговорили про агентов — проговорили два часа. Поняли, что надо записывать 😄 В понедельник 20 июля в 17:00 мск делаем прямой эфир. Всё как вчера, но с микрофонами. Анонс Саши — выше, приходите.

🔥12😁2👌1

18 Jul 2026, 13:29 UTC237 views7 reactionsread 8 August 2026
Forwarded from @book_cube

Research Insights Made Simple #22: как собрать управляемый агентный стек (Рубрика #AI4SDLC) Что компания делает «своим» в агентной платформе: код клиента, модель, контур исполнения, данные или право агента менять внутренние системы? Эти вещи часто смешивают и сводят выбор к спору между «своим OpenCode» и «чужим Claude Code или Codex». В понедельник 20 июля в 17:00 по мск мы с Мишей Трифоновым из Cloud.ru разберём в

🔥42❤‍🔥1

6 Nov 2025, 08:38 UTC862 views18 reactionsread 8 August 2026
Forwarded from @LogachevaEQVideo

Пока все отдыхали на длинных выходных, мы с Михаилом Трифоновым, Head of DevOps из Cloud. ru обсуждали важную тему (чтобы вам было, что посмотреть с пользой прямо сегодня). КАК ПЕРЕСТАТЬ БЫТЬ СПАСАТЕЛЕМ ДЛЯ СВОЕЙ КОМАНДЫ? Эфир получился позитивным, под стать самому Михаилу. Мне кажется, даже по этому короткому фрагменту видно характер героя. Обсудили: 📌 термин «лидер-слуга» - и вы удивитесь, но это совсем не то, о

🔥113❤‍🔥3😁1

3 Nov 2025, 14:33 UTC678 views10 reactionsread 8 August 2026
Forwarded from @LogachevaEQPhoto

😂👍👍❤️👌😅😊😊😍😘 Понедельник, 4 ноября, в 18-00 мск - ZOOM Вы – «скорая помощь» для своей команды? Тот самый лидер, который решает все проблемы, тушит пожары и тащит на себе проекты, пока остальные... просто работают? Остановитесь! Это не героизм, а прямой путь к выгоранию. Желание быть опорой – благородно. Но оно же превращает вас в «решателя проблем», а не в стратега. И пока вы спасаете всех подряд, вы теряете главное

4❤‍🔥3🔥3

24 Jul 2025, 11:04 UTC≈1,230 views22 reactionsread 8 August 2026
Photo

Сейчас выступаю на TechCommunity Fest. Тема доклада: IDP (Internal Development Platform): Как превратить микросервисный хаос в инженерный рай Доп материалы по презентации: - Building Microservices Сэма Ньюмана https://clck.ru/3NGvke - State of DevOps Russia 2024 https://clck.ru/3MUNzz - Team Topologies https://clck.ru/3MUNw - Рекомендуемая архитектура IDP McKinsey https://clck.ru/3MUQFY - AI-commit https://clck.ru/

🔥15🎉4❤‍🔥3

4 Jul 2025, 07:04 UTC≈1,000 views8 reactionsread 8 August 2026
Forwarded from @prouxuiVideo

Ощутите какой путь люди проделали во взаимодействии человек-компьютер. Даже такая мелочь как даблклик должна обладать определенными свойствами, чтобы быть максимально нативной. Добавил ру-субтитры, чтобы было комфортнее смотреть) 😋

🔥42😎2

3 Jul 2025, 08:21 UTC959 views24 reactionsread 8 August 2026

🎙️ Идеализм vs реальность Подкаст с Антоном Тодосийчуком и Даной Миндзаевой Мы сделали всё по учебнику: ✅ Записали 3-часовой подкаст с крутыми гостями ✅ 3 ночи монтировали, вырезали моменты, сводили звук ✅ Готовились к релизу как в кино... А потом — *бац* — битые исходники. Осталась только режиссёрская версия (та самая, которую обычно никто не видит). И знаете что? Решил ее все равно выложить. Без идеального монта

🔥16❤‍🔥4🤔31

21 Jun 2025, 10:02 UTC747 views18 reactionsread 8 August 2026

Годнота подъехала!🚀 Полгода назад записали с Артёмом (@badTechProject, CPO платформенных решений Яндекса) разбор DevEx и Платформ – как ускорить разработку в 2 раза и не сойти с ума. Вышло огонь! 🔥 Кому актуально – ловите ссылку 👇 https://youtu.be/1aYnzXFefc8?si=u8nI80Uw5TEwnrUk

🔥9❤‍🔥5🎉3😁1

14 Jun 2025, 18:56 UTC740 views10 reactionsread 8 August 2026
Photo

Platform Engineering Guide: написал первые статьи! ✅ Когда IDP реально нужна? ✅ Шаг 1. Как ставить цели для IDP? 🔗 Читать (devplatform.pro) Первый раз делаю такой проект — как вам: - Удобно ли читать? - Вставки со скринами – зашквар? - Есть что дополнить? P.S. «Какие ошибки вы совершили при внедрении IDP?» Дополню статьи вашими кейсами!

🔥72❤‍🔥1

10 Jun 2025, 07:14 UTC834 views25 reactionsread 8 August 2026
Photo

Создаю OpenSource базу знаний по Platform Engineering На CTO Conf 2025 я рассказал о своём проекте — OpenSource базе знаний для инженеров, которые хотят: - Разбираться в Platform Engineering без «велосипедов». - Иметь под рукой проверенные гайды по платформенным архитектурам и AI интеграции. - Делиться опытом в комьюнити (приветствуются PR!). Что уже сделано: 1. Выбрал Docusaurus – для удобной навигации и поддержки

🔥16❤‍🔥63

6 Jun 2025, 10:35 UTC961 views18 reactionsread 8 August 2026
Photo

Сейчас выступаю на CTO Conf 2025. Полезные материалы к докладу: Слайд 1: State of Platform Engineering 2024 https://clck.ru/3MUN2r Слайд 5: State of DevOps 2024 clck.ru/3MUNiW Слайд 6: State of DevOps Russia 2024 https://clck.ru/3MUNzz Слайд 34: Team Topologies https://clck.ru/3MUNw Слайд 36: State of DevOps 2020: https://clck.ru/3MUPBo Слайд 39: Рекомендуемая архитектура IDP https://clck.ru/3MUQFY Слайд 49: Обзор г

🔥18

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

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

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

“Трифонов_IT” (@trifonovit), 592 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/trifonovit.

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.