Telegram RegisterThe public register of Telegram

Channel

Russian Association of Software Architects

@ru_arc

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

4,336subscribers

+1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001769802203
TypeChannel
Username@ru_arc
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/ru_arc

Growth

4,3354,3364,335.57 August 2026 — 4,335 subscribers8 August 2026 — 4,335 subscribers11 August 2026 — 4,336 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net +1. 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 4,335–4,336 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 15:544,336+1
8 Aug 2026, 05:124,335no change
7 Aug 2026, 11:464,335first reading

Engagement

16 posts held, back to 9 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 6 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.6%
avg views ÷ 4,336 subscribers
Avg views / post
592
2 posts measured
Reaction rate
1.96%
reactions ÷ views · ER floor
Posts in window
3
of 16 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 8 August 2026
Posts held16 (9 April 20268 August 2026)
Views total1,183
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:20 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

Video runtime
6m 59s
Average length
6m 59s

Measured directly from 1 video 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

120 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 38.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4638.3%
🤣2420.0%
👎1310.8%
🔥119.17%
108.33%
🤯43.33%
😁32.50%
😐32.50%
😢32.50%
🤔21.67%
💯10.833%

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

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

8 Aug 2026, 17:54 UTC163 viewsread 8 August 2026

В Архитектурных Этюдах новый кейс: https://t.me/archicases/9786/9787

Signed Сергей Баранов

22 Jul 2026, 19:39 UTC≈1,020 views17 reactionsread 8 August 2026
Forwarded from @event_stormingVideo

Вот так Notebooklm сжал теорию первого дня корп курса по Event Storming, очень хорошо сжал, я бы сказал. Никакой лишней информации нет, так что можно выложить :)

👍9🔥3😐32

Signed Ivan

27 Jun 2026, 12:37 UTC≈2,260 views22 reactionsread 8 August 2026
Forwarded from @blog_sb

SPDD (Structured Promt Driven Development) https://martinfowler.com/articles/structured-prompt-driven/ Пришла пора подвести итоги использования SPDD, как самостоятельного, так и в рамках консалтинга. Я не увидел в SPDD чего-то, что бы фундаментально меняло подход к разработке, в сущности – это инструмент для того, чтобы обуздать и дисциплинировать работу ненадежным, стохастическим генератором кода (хотя Мартин Фаул

👍18🤯31

Signed Сергей Баранов

20 Jun 2026, 19:10 UTC≈2,020 views8 reactionsread 8 August 2026
Forwarded from @blog_sb

Я обещал написать, начал писать и уже получилось пять страниц, так что это будет уже статья, но кое что я все же напишу здесь. В прошлом году я выступил с темой «Экономические последствия архитектурных решений». В ней было о том, как архитектура влияет на экономику. После этого было несколько проектов, в которых мы реализовали оценку архитектурных решений в деньгах. Это оказалось проще, чем кажется на первый взгляд,

👍3🤣32

Signed Сергей Баранов

19 Jun 2026, 18:00 UTC≈1,450 views8 reactionsread 8 August 2026
Forwarded from @blog_sbPoll

Фиксируете ли вы трудозатраты в часах? Не для планирования, а фактически затраченное время?

  1. Да, честные трудозатраты21%
  2. Да, формальность, не сколько на самом деле25%
  3. Нет54%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

👎5👍21

Signed Сергей Баранов

17 Jun 2026, 05:35 UTC≈1,940 views32 reactionsread 8 August 2026
Forwarded from @neuraldeep

Ищу человека, который возьмёт на себя почтовую платформу на 100 млн ящиков Рынок почты в РФ переформатируется на глазах Старая модель «жить на чужой бесплатной почте» закончилась На этом фоне нужна экспертиза на почтовый сервис национального масштаба, до 100 000 000 ящиков, полностью в российском контуре Ищу не «инженера Postfix», а технического лидера направления того, кто возьмёт архитектуру/стратегию и результа

🤣21👍5👎3🔥3

Signed Сергей Баранов

16 Jun 2026, 12:36 UTC≈2,260 views3 reactionsread 8 August 2026

Мы продолжаем прием тем для выступления на archdays.ru Этот год богат на темы, подавайте, встретимся, обсудим :)

😢3

Signed Сергей Баранов

1 May 2026, 12:52 UTC≈2,880 views18 reactionsread 8 August 2026
Forwarded from @it_architecture_rssPhoto

Structured-Prompt-Driven Development (SPDD) LLM programming assistants have demonstrated considerable value, but mostly with individual developers. The internal IT organization in Thoughtworks has been using them for their teams and have developed a method and workflow called Structured Prompt-Driven Development (SPDD). Wei Zhang and Jessie Jie Xia describe a simple example of this workflow with details in github. T

👍6👎5🔥4😁3

Signed Ivan

16 Apr 2026, 18:48 UTC≈2,960 views4 reactionsread 8 August 2026
Forwarded from @unauthzPhoto

401 meetup – call for papers Друзья, пишу поделиться отличной новостью! Анонсирую оффлайн-митап про Identity & Access Management (IAM) в Москве 27 мая. Концепция: свободный вендор-независимый митап для сообщества. Подробности и начало регистрации для участников будут объявлены позднее, а пока приглашаю спикеров заявиться с докладами. Очень жду и приветствую доклады про аутентификацию, управление доступом и смежн

4

Signed Ivan

15 Apr 2026, 10:25 UTC≈2,090 views2 reactionsread 8 August 2026

Новый кейс в Архитектурных Этюдах! «Расхождение между учетной системой и реальностью на складе» Как построить архитектуру информационной системы управления складом, при которой физическое состояние склада и его цифровое отображение остаются синхронизированными в реальном времени несмотря на то, что операции с материалами выполняют десятки людей, не заинтересованных в корректном вводе данных? https://t.me/archicase

👍2

Signed Сергей Баранов

13 Apr 2026, 16:07 UTC≈2,150 views1 reactionsread 8 August 2026

Хм. Раньше настройки опроса в Телеграм по-умолчанию были такими: • Можно выбрать только один вариант ответа Теперь по-умолчанию через десктопное приложение осталось как и было раньше (можно выбрать только один вариант ответа), а в мобильной версии по-умолчанию теперь: • Можно выбрать несколько вариантов • Перемешивать варианты ответа при каждом отображении (новая настройка) Вот я и создал опрос, через мобильное при

💯1

Signed Сергей Баранов

Showing the 12 most recent of 16 posts we hold for @ru_arc. 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 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

19 Jun 2026, 18:00 UTCAnonymous Poll560 voters

Фиксируете ли вы трудозатраты в часах? Не для планирования, а фактически затраченное время?

  1. Да, честные трудозатраты21%
  2. Да, формальность, не сколько на самом деле25%
  3. Нет54%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Apr 2026, 15:34 UTCAnonymous Poll297 voters

Вы бы пошли учиться IoT архитектуре? (Мотив не важен) Говорят, огромный запрос на IoT-архитекторов, а специалистов нет, проверим интерес.

  1. Да43%
  2. Нет (нет потребности/интереса)36%
  3. Нет (уже разбираюсь в IoT-архитектуре)10%
  4. Не знаю, что это такое20%

The shares total 109%, 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 16 most recent posts we hold, published 9 April 2026 to 8 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 — 311,895 of 1,169,250entries 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

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.

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

“Russian Association of Software Architects” (@ru_arc), 4,336 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ru_arc.

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.