Telegram RegisterThe public register of Telegram
Telegram profile photo for Архитектура ИТ-решений

Channel

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

@it_arch

On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

16,225subscribers

+52 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
Created1 February 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/it_arch

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

16,17316,22616,199.56 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 subscribers13 August 2026 — 16,195 subscribers14 August 2026 — 16,192 subscribers19 August 2026 — 16,191 subscribers20 August 2026 — 16,192 subscribers21 August 2026 — 16,197 subscribers23 August 2026 — 16,198 subscribers24 August 2026 — 16,202 subscribers25 August 2026 — 16,204 subscribers26 August 2026 — 16,203 subscribers27 August 2026 — 16,188 subscribers28 August 2026 — 16,195 subscribers29 August 2026 — 16,198 subscribers30 August 2026 — 16,200 subscribers31 August 2026 — 16,201 subscribers1 September 2026 — 16,202 subscribers2 September 2026 — 16,205 subscribers4 September 2026 — 16,213 subscribers10 September 2026 — 16,220 subscribers12 September 2026 — 16,225 subscribers14 September 2026 — 16,226 subscribers15 September 2026 — 16,221 subscribers18 September 2026 — 16,225 subscribers16,2256 August 202618 September 2026
31 measurements spanning 43 days, net +52. 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,165–16,234 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
18 Sept 2026, 04:1916,225+4
15 Sept 2026, 21:5816,221-5
14 Sept 2026, 03:3616,226+1
12 Sept 2026, 14:2116,225+5
10 Sept 2026, 11:3516,220+7
4 Sept 2026, 09:5616,213+8
2 Sept 2026, 21:5816,205+3
1 Sept 2026, 22:0516,202+1
31 Aug 2026, 21:0416,201+1
30 Aug 2026, 19:4816,200+2
29 Aug 2026, 22:5516,198+3
28 Aug 2026, 20:0316,195+7
27 Aug 2026, 17:5816,188-15
26 Aug 2026, 15:5416,203-1
25 Aug 2026, 15:3516,204+2
24 Aug 2026, 19:0516,202+4
23 Aug 2026, 03:0816,198+1
21 Aug 2026, 18:0616,197+5
20 Aug 2026, 14:3616,192+1
19 Aug 2026, 16:4816,191first reading

Engagement

26 posts held, back to 16 April 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 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.6%
avg views ÷ 16,225 subscribers
Avg views / post
3,010
1 post measured
Reaction rate
0.532%
reactions ÷ views · ER floor
Posts in window
1
of 26 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 29 August 2026
Posts held26 (16 April 2026 – 29 August 2026)
Views total3,010
Reactions total16
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 10: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.

Reaction mix

534 reactions across 24 posts, in 11 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍22141.4%
❤10319.3%
🔥9618.0%
💯529.74%
🤩244.49%
😢101.87%
👎91.69%
🤔81.50%
🥱71.31%
🎉20.375%
👏20.375%

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

Measured over the 26 most recent posts we hold, published 16 April 2026 to 29 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

29 Aug 2026, 11:55 UTC≈3,010 views16 reactionsread 3 September 2026
Photo

Ну и страсти на выходных в твиттере x.com. Сначала Open AI сообщает, что в ноябре они отключат от своих моделей пользователей Cursor. Их там уже за это активно хейтят, почитайте. Но лучший ответ - сожаления от CEO Cursor, что так сложилось, c нечаянным упоминанием, что модели Open AI - это целых 5% трафика пользователей Cursor

👍15🤔1

28 Aug 2026, 07:47 UTC≈3,800 views25 reactionsread 3 September 2026
Photo

📆 3 сентября 10:30 MSK Проведу бесплатный вебинар Навыки AI-агентов для аналитиков и ИТ-архитекторов Сегодня AI-агенты активно развиваются для задач программирования. Но их потенциал гораздо шире. Закономерный следующий шаг — использование агентов в других видах профессиональной деятельности. Для аналитиков и ИТ-архитекторов - это прежде всего работа с требованиями, проектирование и документирование архитектурных ре…

👍17❤4🔥3👎1

28 Aug 2026, 05:52 UTC≈3,890 views45 reactionsread 3 September 2026

Пятничное: Я наконец сообразил почему соревнования роботов имеют своих ярых фанатов. Уж больно похожи такие забеги на корпоративные проекты, программы, инициативы. Просто представьте себе, что каждый соревнующийся робот — это вовсе не робот, а тот или иной проект в вашей организации. И движется он так же смешно и неуклюже как традиционный ИТ-проект: путает дорожки, размахивает конечностями, исполняет невероятные кул…

👍19❤10🔥8💯6🤔1🤩1

12 Aug 2026, 04:58 UTC≈5,950 views18 reactionsread 3 September 2026

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

👍14❤2😢2

8 Aug 2026, 05:00 UTC≈6,690 views55 reactionsread 3 September 2026
Photo

Photo, posted without a caption

💯30🔥15🤩6👍3❤1

7 Aug 2026, 09:57 UTC≈6,710 views5 reactionsread 3 September 2026
Photo

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

❤5

3 Aug 2026, 10:07 UTC≈7,320 views17 reactionsread 3 September 2026
Photo

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

🔥12❤4👍1

30 Jul 2026, 16:35 UTC≈8,640 views48 reactionsread 3 September 2026

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

👍31❤10🔥6🤔1

30 Jul 2026, 16:35 UTC≈5,720 viewsread 3 September 2026
Photo

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

20 Jul 2026, 05:35 UTC≈7,020 views8 reactionsread 3 September 2026
Poll

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

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

The shares total 135%, 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,980 views13 reactionsread 3 September 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,560 views20 reactionsread 3 September 2026
Forwarded from @book_cube

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

❤20

Showing the 12 most recent of 26 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 Poll927 voters

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

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

The shares total 135%, 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 26 most recent posts we hold, published 16 April 2026 to 29 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.

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 12 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.

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.

Teamlead Good Reads – ежедневные советы про менеджмент людей и команд
@leadgr · 28,120
Telegram ranks this channel #78 of 96 here — alongside 95 others — read 10 September 2026
GetAnalyst - Навыки • Системный анализ • Бизнес-анализ
@getanalysts · 22,509
Telegram ranks this channel #79 of 96 here — alongside 95 others — read 20 September 2026
Максим Дорофеев: Прокрастинация и джедайские техники
@mnogosdelal · 26,254
Telegram ranks this channel #93 of 97 here — alongside 96 others — read 14 September 2026

This channel appears in 3 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Архитектура ИТ-решений” (@it_arch), 16,225 subscribers as measured 18 September 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.