Telegram RegisterThe public register of Telegram

Channel

Flow — конференция про системный и бизнес-анализ

@flowconf_channel

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

599subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001535203769
TypeChannel
Username@flowconf_channel
DescriptionКонференция про системный анализ и бизнес-анализ. Подробности и билеты: https://jrg.su/FlowConf Чат конференции: @flowconf Саппорт: @JUGruSupport
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/flowconf_channel

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 77% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@techtrainfest_channel/2855 Nov 2025, 15:18 UTC@flowconf_channel/352 · this entry5 Nov 2025, 15:20 UTC1.002 minutes
@techtrainfest_channel/28928 Apr 2026, 15:47 UTC@flowconf_channel/357 · this entry28 Apr 2026, 15:54 UTC1.007 minutes
@techtrainfest_channel/29110 May 2026, 08:33 UTC@flowconf_channel/358 · this entry10 May 2026, 08:33 UTC1.00under a minute
@flowconf_channel/359 · this entry15 May 2026, 12:51 UTC@techtrainfest_channel/29215 May 2026, 12:52 UTC1.0072 seconds
@techtrainfest_channel/28818 Apr 2026, 10:32 UTC@flowconf_channel/356 · this entry18 Apr 2026, 10:34 UTC0.9672 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@techtrainfest_channel5 (5/5 hand-verifiable sample passed)0.9972 seconds@techtrainfest_channel (41)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 17 comparable posts for this entry, running 3 October 2025 to 15 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @techtrainfest_channel. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5996 Aug 2026, 02:20 — 599 subscribers6 Aug 2026, 17:48 — 599 subscribers6 Aug 2026, 02:206 Aug 2026, 17:48
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 598–600 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 17:48599no change
6 Aug 2026, 02:20599first reading

Engagement

20 posts held, back to 3 October 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 15 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
240
Videos
3
Links
248

Lifetime counters from Telegram’s own channel header, read 6 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.

Reaction mix

112 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4237.5%
❤‍🔥3026.8%
👍2017.9%
1311.6%
32.68%
🍾32.68%
🤩10.893%

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

Measured over the 20 most recent posts we hold, published 3 October 2025 to 15 May 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

15 May 2026, 12:51 UTC569 views0 reactionsread 6 August 2026

Менеджмент времен McKinsey уходит в прошлое. Добро пожаловать в эпоху роя AI-агентов! Как управлять командой, если код теперь пишут нейросети? Зачем нужны Jira и task-трекеры, когда постановка задачи занимает больше времени, чем её исполнение? И почему ваша следующая зарплата будет зависеть не от количества строк кода, а от умения «дружить» с LLM? В новом выпуске AI Dev Podcast мы разбираем горячую тему года: транс

10 May 2026, 08:33 UTC499 views1 reactionsread 6 August 2026

Замена людей на ИИ — путь к разорению компании? Агенты всё лучше пишут код, делают ревью и документацию. Но им нужна адаптация, поэтому ставить цели, изобретать и управлять контекстом — останется за человеком. Мы продолжаем готовиться к AI Dev Conf, где обсудим эти вопросы, и продолжаем серию подкастов 📢 [AI Dev подкаст #2] Архитектура в эпоху ИИ — от хаоса к новой инженерной реальности О чем выпуск: Как LLM и мул

1

28 Apr 2026, 15:54 UTC942 views5 reactionsread 6 August 2026
Photo

Полгода назад мы разбирались, как повысить личную продуктивность разработчика. А сейчас уже думаем над новыми метриками, чтобы измерять влияние агентов на весь процесс Если вы тоже обнаружили, что ваши новые коллеги — не люди, а агенты — подключайтесь ко второму сезону AI Dev Conf — 21 мая, онлайн Для кого конференция: Individual Contributors (Dev, QA, DevOps, SA/BA, etc.) — Какие практики и инструменты брать в ра

👍5

18 Apr 2026, 10:34 UTC≈10,600 views9 reactionsread 6 August 2026

Что послушать на выходных? 📢 [AI Dev подкаст #1] ИИ в проектировании архитектуры: метрики и «скиллы» Спойлер: LLM уже справляется с проверкой техрадара, оценкой пул-реквестов и анализом архитектурного долга. Но есть нюансы. Мы собрали трех практиков, чтобы ответить на вопросы: — как ИИ меняет работу архитектора; — почему SDD (Spec-Driven Development) пока сырой, но пробовать уже надо; — что такое agent skills и

🔥71👍1

30 Dec 2025, 14:16 UTC873 views10 reactionsread 6 August 2026
Photo

С наступающим Новым годом! ✨ Спасибо, что этот год были вместе с нами — слушали, делились опытом и вдохновляли нас своими вопросами и идеями. Весной мы проведем пять конференций — будем рады видеть вас среди участников и вместе открыть сезон. Желаем вам хорошо отдохнуть и душевно провести время. Берегите себя! С Новым кГодом!

👍4🍾321

5 Dec 2025, 15:24 UTC858 views12 reactionsread 6 August 2026
Photo

Привет! Очередной сезон конференций от JUG Ru Group закончился. Спасибо всем, кто был с нами этой осенью на Flow и оставил отзывы о докладах и конференции! Настало время подвести итоги розыгрыша билетов и записей докладов. 📺 Доступ к записям докладов любой из наших осенних конференций получают: — ev***.m**v2**2@yandex.ru — o***pl@outlook.com — a***e.log***a@yandex.ru — b***a.dd@skbkontur.ru — k***a.***va@gmail.com

5👍4🔥3

5 Nov 2025, 15:20 UTC≈1,640 views6 reactionsread 6 August 2026
Photo

AI-разработка без иллюзий: что работает, а что нет? Бесплатная онлайн-конференция AI-Development Conf — 8 ноября, 11:00–15:00. AI уже умеет генерировать код, тесты и архитектуру, но как это работает в реальных проектах? На конференции покажем все без прикрас: реальные кейсы, инструменты и подходы, которые помогают ускорить работу. В программе: 🔹 11:00 — Как копилот генерит код? — Claude Code, Cursor, Explyt․ai, C

🔥6

27 Oct 2025, 08:04 UTC674 views8 reactionsread 6 August 2026

Альбом с фото Flow 2025 Autumn готов! Смотрите, ищите себя и делитесь понравившимися с хештегом #flowjrg

❤‍🔥7🤩1

18 Oct 2025, 11:40 UTC≈1,960 views8 reactionsread 6 August 2026
Photo

Исследование SA/BA x Flow live: разбираем итоги на онлайн-митапе В этом году мы проводили исследование, чтобы понять, кто такой современный системный и бизнес-аналитик и что происходит в профессии. Первыми наблюдениями мы поделились на Flow 2025 Autumn, теперь пришло время поговорить о результатах. Приглашаем на онлайн-митап 22 октября в 19:00. Расскажем все, что не вошло в первый обзор, вместе разберем все детали и

🔥8

8 Oct 2025, 12:02 UTC947 views7 reactionsread 6 August 2026
Photo

#видеозаписи Видео всех докладов Community Day Flow 2025 Autumn теперь доступны на сайте конференции. Чтобы посмотреть их, достаточно залогиниться через Личный кабинет JUG Ru Group. ▶️ Михаил Максимов — ИТ-продукт/система вчера, сегодня, завтра. Управление на протяжении всего ЖЦ ▶️ Ирина Гертовская — Концептуальная целостность, синдром «второй системы» и культура производства ▶️ Александр Белин — Трансформация зн

🔥7

4 Oct 2025, 16:33 UTC599 views23 reactionsread 6 August 2026
Photo

Конференция Flow 2025 Autumn подошла к концу Целых два дня мы слушали доклады, дискутировали, играли и знакомились. Без вас ничего бы не случилось! Спасибо всем спикерам, участникам, экспертам и сообществам, поддержавшим конференцию. До встречи на следующих конференциях! Мы пришлем вам на почту опрос. В нем можно дать обратную связь о конференции, а среди заполнивших — мы разыграем билеты на следующую конференцию.

❤‍🔥23

4 Oct 2025, 15:46 UTC461 views19 reactionsread 6 August 2026
Photo

Кто делает Flow еще лучше? Конференция — это не только доклады, дискуссии и нетворкинг. За кулисами Flow 2025 Autumn — огромная команда профессионалов из разных IT-компаний, без которых все это было бы невозможным. Благодарим профессиональные сообщества, которые поддержали конференцию: → Летний Аналитический Фестиваль → IT HR → Soft Skills Lab → System Analyst

🔥116👍2

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

Citation-graph rank

Citation-graph rank — 145,357 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

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

“Flow — конференция про системный и бизнес-анализ” (@flowconf_channel), 599 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/flowconf_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.