Channel

Selena (powered by StarRocks)

@starrocks_selena

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

383subscribers

+1 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	-1003660739244
Type	Channel
Username	@starrocks_selena
Created	Between 1 December 2025 and 13 April 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	7 August 2026
Last confirmed live	15 August 2026
Measurements held	2
Confirmed unchanged	2 times, most recently 15 August 2026
On Telegram	t.me/starrocks_selena

Growth

2 measurements taken within a single day, 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 382–383 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
7 Aug 2026, 16:53	383	+1
7 Aug 2026, 03:01	382	first reading

Engagement

19 posts held, back to 13 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days: 45.4%; avg views ÷ 383 subscribers
Avg views / post: 174; 1 post measured
Reaction rate: 27.0%; reactions ÷ views · ER floor
Posts in window: 1; of 19 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
Window	Rolling 30 days · latest post in window 28 July 2026
Posts held	19 (13 April 2026 – 28 July 2026)
Views total	174
Reactions total	47
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	7 Aug 2026, 03:01 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

541 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 56.6% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
🔥	306	56.6%
👍	107	19.8%
⚡	37	6.84%
🆒	29	5.36%
❤	16	2.96%
💯	16	2.96%
👏	8	1.48%
🤝	8	1.48%
❤‍🔥	4	0.739%
👨‍💻	4	0.739%
💘	3	0.555%
🤯	3	0.555%

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

Measured over the 19 most recent posts we hold, published 13 April 2026 to 28 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

28 Jul 2026, 12:11 UTC174 views47 reactionsread 7 August 2026

Forwarded from @dis_group_newsPhoto

Александр Моисеев, главный архитектор интеллектуальной дата-платформы AIDP и автор технического канала о системе хранения и обработки данных Селена Lakehouse получил признание международного сообщества StarRocks Community Champion 2026 и звания Ambassador, Advocate за публикации в канале, статьи на Хабр, выступления и другие активности, связанные с продвижением этой передовой технологии в России 👏 В проекте Selena (…

🔥33⚡7💘3🆒3👏1

9 Jul 2026, 07:53 UTC357 views21 reactionsread 7 August 2026

Photo

🖥 Release digest: Selena 3.0. Обзор ключевых доработок Представляем Selena 3.0. Это релиз, в котором основной фокус сделан на enterprise-эксплуатацию платформы: повышении безопасности, упрощении развёртывания, автоматизации управления кластерами и единой модели доступа. В этой версии закрыт ряд уязвимостей CVE в компонентах Selena Auth и MCP, обновлены runtime-зависимости движка, а в CI/CD-процессы внедрено единое с…

🔥13👍3🆒3⚡1💯1

6 Jul 2026, 09:01 UTC395 views21 reactionsread 7 August 2026

SQL UDF в StarRocks 4.1: собственные функции прямо на SQL Встроенных функций SQL обычно хватает для большинства задач: upper() приведёт строку к верхнему регистру, date_trunc() обрежет дату до месяца, round() округлит сумму. Но почти в любом проекте появляются задачи, для которых встроенных функций уже недостаточно: 🔹 нормализация телефонных номеров; 🔹 очистка и нормализация текста; 🔹 транслитерация; 🔹 маскирование…

🔥9👍5🤝4⚡2🆒1

25 Jun 2026, 07:06 UTC424 views19 reactionsread 7 August 2026

🚀 Через час начинаем вебинар! Если еще не успели зарегистрироваться или добавить себе напоминание, то сейчас самое время! Поговорим о миграции с Greenplum и Clickhouse на StarRocks: разберем архитектурные подходы, варианты переноса данных, миграцию объектов базы данных и практические нюансы, которые возникают в реальных проектах. До встречи через час! 👋

👍9🔥8🤝2

18 Jun 2026, 06:41 UTC454 views17 reactionsread 7 August 2026

Forwarded from @dis_group_newsPhoto

Как перейти с DWH на Data Lakehouse? Расскажем на вебинаре DIS Group с участием разработчиков Селены и StarRocks ✨ 🗓 Дата: 25 июня ⏰ Время: 11:00 мск Регистрируйтесь, чтобы вместе разобраться в теме и получить ответы на вопросы Мы обсудим: 🔹 Где не справляются DWH, и как получить выгоду от Data Lakehouse 🔹 Миграцию данных с Greenplum на StarRocks 🔹 Технологии и шаги миграции с Clickhouse на StarRocks Спикеры: - …

🔥12👍3🆒2

17 Jun 2026, 09:46 UTC478 views18 reactionsread 7 August 2026

Как StarRocks загружает данные из S3 и HDFS: FILES() и PIPE StarRocks умеет работать с данными, которые лежат в удаленном хранилище, не загружая их к себе заранее. К ним он обращается двумя способами: через внешний каталог, когда это таблицы озера вроде Iceberg, и напрямую к файлам в бакете (Parquet, ORC, CSV и другие) через табличную функцию FILES(). В обоих случаях без промежуточной выгрузки. Такая задача возника…

🔥9💯4⚡3❤1👍1

11 Jun 2026, 07:53 UTC412 views17 reactionsread 7 August 2026

🔥 Как устроен StarRocks внутри? Недавно наткнулся на хороший (простой и легко читается с телефона) разбор архитектуры StarRocks — от загрузки данных до выполнения распределённых запросов. Особенно интересно сравнение двух режимов работы: 🔹 Shared-Nothing — данные и вычисления находятся на одних и тех же узлах. Максимум производительности за счёт локальности данных. 🔹 Shared-Data — вычисления отделены от хранения. Д…

🔥11❤‍🔥2👍2🤝2

4 Jun 2026, 03:53 UTC516 views36 reactionsread 7 August 2026

Photo

🇰🇿 Сегодня команда Selena на DATA AI Summit 2026 в Алматы Выступаем сразу в двух форматах: 🎙 Дмитрий Замула с докладом «Selena Lakehouse как аналитическая память для AI-агентов». 💻 Александр Моисеев проведёт воркшоп по продуктовой аналитике в real time. На живом демо покажем, как события из мобильного банка на лету превращаются в воронки, retention-метрики и инструменты для разбора инцидентов. 📍 The Ritz-Carlton …

🔥21👍6⚡4💯3👏2

29 May 2026, 15:01 UTC643 views28 reactionsread 7 August 2026

Photo

🔥 Новая статья на Хабре: Автоскейлинг StarRocks в Kubernetes: как я довел его до предела Автоскейлинг обычно показывают на красивых графиках: нагрузка выросла → добавились ноды → всё хорошо. Но что происходит в менее приятном сценарии? Когда кластер уже упёрся в лимиты, Kubernetes начинает пересоздавать Pod’ы, а ресурсы заканчиваются прямо во время выполнения запросов? Я решил проверить именно этот пограничный случа…

🔥16👍6👨‍💻4🆒2

27 May 2026, 14:01 UTC487 views25 reactionsread 7 August 2026

Photo

Как StarRocks защищает production от перегрузки. Pipeline DOP В прошлых постах я разбирал Multi-Warehouse, Resource Groups и Query Queues. Сегодня четвертая часть: про то, как StarRocks подстраивает параллелизм каждого отдельного запроса под текущую загрузку кластера. И тут, к сожалению, без мат. части не обойтись, чтобы не запутаться, поэтому пост будет больше обычного. Напомню, Resource Groups делят ресурсы между…

🔥15⚡4👍4👏1💯1

19 May 2026, 07:56 UTC644 views32 reactionsread 7 August 2026

Photo

Как StarRocks защищает production от перегрузки. Query Queues В прошлых постах я рассказывал про Multi-Warehouse и про Resource Groups. Сегодня третья часть, и она отвечает на вопрос, которым предыдущий пост закончился: что делает кластер, когда запросов прилетает больше, чем все группы вместе способны обработать? Представим ситуацию: в кластер одновременно приходит 500 тяжёлых запросов. Resource Groups поделят меж…

🔥21💯6👍5

6 May 2026, 10:04 UTC≈1,150 views43 reactionsread 7 August 2026

Photo

🔥 Новая статья на Хабре: Миграция с Greenplum. Эпизод I: Атака клонов и спасение на звёздных камнях В мае 2024 Broadcom заархивировал публичный репозиторий Greenplum. Сам код остался под Apache 2.0 — на нём выросли форки: Apache Cloudberry, Greengage DB от Arenadata, WarehousePG от EDB. Но публичная разработка Greenplum в прежнем виде остановилась. У тех, кто строил аналитику на Greenplum, появилась развилка: остат…

🔥26👍8🆒6⚡2💯1

Showing the 12 most recent of 19 posts we hold for @starrocks_selena. 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 — 112,358 of 1,481,217entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

DIS Group | Пульс данных
@dis_group_news · 9103 posts

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.

Named by

Channels on the register whose posts name this channel's handle.

DIS Group | Пульс данных
@dis_group_news · 9102 posts StarRocks and modern data stack
@modern_data_stack · 5391 post

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

“Selena (powered by StarRocks)” (@starrocks_selena), 383 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/starrocks_selena.

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.