Telegram RegisterThe public register of Telegram

Channel

Архитектура ИТ-решений

@it_arch

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

16,197subscribers

+24 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-1001110752018
TypeChannel
Username@it_arch
DescriptionРазговоры об архитектуре корпоративных информационных систем (архитектура предприятия, архитектура ИТ-решений). Регистрация в перечне РКН: https://knd.gov.ru/license?id=6735f4cd97de7d1d1953c457&registryType=bloggersPermission
Created1 February 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/it_arch

Growth

16,17316,19716,1856 August 2026 — 16,173 subscribers6 August 2026 — 16,173 subscribers6 August 2026 — 16,174 subscribers7 August 2026 — 16,179 subscribers8 August 2026 — 16,183 subscribers9 August 2026 — 16,189 subscribers10 August 2026 — 16,190 subscribers11 August 2026 — 16,193 subscribers12 August 2026 — 16,197 subscribers6 August 202612 August 2026
9 measurements spanning 6 days, net +24. 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 16,169–16,201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:2316,197+4
11 Aug 2026, 09:4416,193+3
10 Aug 2026, 10:2816,190+1
9 Aug 2026, 07:5316,189+6
8 Aug 2026, 07:2616,183+4
7 Aug 2026, 10:0616,179+5
6 Aug 2026, 07:3016,174+1
6 Aug 2026, 02:1916,173no change
6 Aug 2026, 01:5616,173first reading

Engagement

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

ERR · 30 days
32.1%
avg views ÷ 16,197 subscribers
Avg views / post
5,190
8 posts measured
Reaction rate
0.423%
reactions ÷ views · ER floor
Posts in window
8
of 23 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 7 of 8 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 12 August 2026
Posts held23 (16 April 202612 August 2026)
Views total41,540
Reactions total155
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 01:03 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
355
Videos
3
Links
1,250

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.

Reaction mix

439 reactions across 21 posts, in 11 distinct kinds. The most used accounts for 37.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍16637.8%
8820.0%
🔥8419.1%
💯439.79%
🤩235.24%
😢102.28%
👎81.82%
🥱71.59%
🤔61.37%
🎉20.456%
👏20.456%

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 22 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 453reactions 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 16 April 2026 to 12 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

12 Aug 2026, 04:58 UTC≈2,280 views14 reactionsread 13 August 2026

10 open-source сканеров безопасности агентских навыков Хочу поделиться ссылкой на статью с таким заголовком и еще парой ссылок по теме: - В январском исследование SkillScan говорится, что среди 31 132 общедоступных навыков agent skills удалось выявило 26,1% потенциально опасных, и 5,2% заведомо опасных навыка. - В конце июля организовался Open Secure AI Alliance (см. пресс-релиз в блоге Nvidia) В общем, сканируйт

👍11😢21

8 Aug 2026, 05:00 UTC≈4,180 views50 reactionsread 13 August 2026
Photo

Photo, posted without a caption

💯27🔥14🤩6👍21

7 Aug 2026, 09:57 UTC≈4,510 views5 reactionsread 13 August 2026
Photo

Поддержка новой (stateless)версии MCP появилась далеко не везде. Например, KiloCode, с котором я много вожусь последнее время, новые MCP сервера подцеплять не умеет. Причем, release candidate новой версии протокола появился еще в мае. Т.е. времени подготовиться было достаточно, но... И тут вчера появляется стандарт Agent Plugins версии 1.0.0 от группы разработчиков: ChatGPT, VS Code, Cursor,... в общем всех кроме ко

5

3 Aug 2026, 10:07 UTC≈5,530 views17 reactionsread 13 August 2026
Photo

📆 7 августа c 10:30 MSK я проведу сессию ответов на вопросы (AMA, ask me anything session) для выпускников учебных курсов: - Мастерская проектирования ИТ-решений, - Модели корпоративной архитектуры. TOGAF 10 и Archimate 4.0, - Микросервисная архитектура и др. Конечно, я приглашаю и всех остальных подписчиков. А чтоб было совсем интересно в начале сессии мы 10-15 минут поговорим про новую версию Model Context Protoco

🔥124👍1

30 Jul 2026, 16:35 UTC≈7,160 views48 reactionsread 13 August 2026

MCP 2026-07-28: что действительно изменилось Вышла новая версия спецификации MCP. Если убрать маркетинговые заявления, то действительно важных изменений не так уж и много: 1. Stateless-протокол - самое важное Из протокола убрали обязательные сессии (initialize, initialized, Mcp-Session-Id). Теперь каждый запрос самодостаточен. В общем, сервер становится обычным HTTP API 2. Стандартизованы долгие операции (Tasks) Ра

👍3110🔥6🤔1

30 Jul 2026, 16:35 UTC≈4,930 viewsread 13 August 2026
Photo

Слова в следующем сообщении

20 Jul 2026, 05:35 UTC≈6,400 views8 reactionsread 13 August 2026
Poll

Как вы используете агентские навыки (agentskills.io)?

  1. Вообще не использую31%
  2. Использую очень редко9%
  3. Беру готовые с маркетплейсов14%
  4. Дорабатываю чужие навыки11%
  5. Генерю свои LLM-кой (/create-skill и т.п.)31%
  6. Пишу сам15%
  7. Свой вариант ответа напишу в комментариях1%
  8. Не голосую, хочу посмотреть результаты24%

The shares total 136%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

5👍2👎1

17 Jul 2026, 05:32 UTC≈6,550 views13 reactionsread 13 August 2026
Forwarded from @book_cubePhoto

Материалы про Loop Engineering (Рубрика #RnD) Готовы материалы с подкаста Research Insights Made Simple, который был во вторник с Максимом Смирновым: - Презнтация: Слайд дека с разбором - Видео: Youtube, VK - Аудио: Podster, Ya Music - Текст: Краткая расшифровка #AI4SDLC #Agents #Architecture #Engineering #Research

6🥱4👍3

13 Jul 2026, 15:27 UTC≈7,200 views20 reactionsread 13 August 2026
Forwarded from @book_cube

Кто управляет кодинг-агентом: человек или спроектированный им цикл? Мы привыкли обсуждать промпты, контекст и обвязку одного запуска агента. Но когда агент сам возвращается к работе - по расписанию, событию или результату прошлого прохода, - задача становится архитектурной: кто находит работу, проверяет результат, хранит состояние и может остановить цикл. 14 июля в 16:00 по Москве проведу прямой эфир с Максимом Сми

20

4 Jul 2026, 07:12 UTC≈7,840 views23 reactionsread 13 August 2026
Photo

Улыбнуло, как говорили когда-то: https://x.com/github/status/2072801888525840476 gh.io/cd

🤩173🔥2🤔1

30 Jun 2026, 09:53 UTC≈9,280 views13 reactionsread 13 August 2026

Пока я только готовлю вебинар про 2-ую версию Open Agile Architecture поделюсь официальным вебинаром от TheOpenGroup https://youtu.be/hIDn1xhfA24 У них есть такой формат Toolkit Tuesday. Вот в предыдущий раз немного поговорили про новую версию O-AA. Коротко, но интересно

🔥8👍5

16 Jun 2026, 15:22 UTC≈9,610 views10 reactionsread 13 August 2026

SpaceX воспользовалась опционом на приобретение Cursor за $60 млрд https://x.com/SpaceX/status/2066873915717136548

👍53🤔2

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

20 Jul 2026, 05:35 UTCAnonymous Poll900 voters

Как вы используете агентские навыки (agentskills.io)?

  1. Вообще не использую31%
  2. Использую очень редко9%
  3. Беру готовые с маркетплейсов14%
  4. Дорабатываю чужие навыки11%
  5. Генерю свои LLM-кой (/create-skill и т.п.)31%
  6. Пишу сам15%
  7. Свой вариант ответа напишу в комментариях1%
  8. Не голосую, хочу посмотреть результаты24%

The shares total 136%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 23 most recent posts we hold, published 16 April 2026 to 12 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 — 58,827 of 1,151,006entries 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

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

“Архитектура ИТ-решений” (@it_arch), 16,197 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/it_arch.

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.