Всегда интересно, кто что видит на своей работе. Например, админы вот такое :) А что у вас перед глазами на работе? 🖱Кстати, сегодня День системного администратора! С праздником, друзья! 🖥
❤🔥5❤4👍4

Channel
@bitblaze_ru
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
676subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001847305925 |
|---|---|
| Type | Channel |
| Username | @bitblaze_ru |
| Description | Мы — команда BITBLAZE | bitblaze.ru Мы разрабатываем системы хранения данных для тех, кто дорожит информацией За демо-доступом и расчетом тех задания на info@bitblaze.ru Актуальные вакансии: https://omsk.hh.ru/employer/2698061 |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bitblaze_ru |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 04:16 | 676 | no change |
| 7 Aug 2026, 04:03 | 676 | first reading |
20 posts held, back to 30 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 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.
| Window | Rolling 30 days · latest post in window 31 July 2026 |
|---|---|
| Posts held | 20 (30 April 2026 – 31 July 2026) |
| Views total | 807 |
| Reactions total | 34 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 04:16 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.
Lifetime counters from Telegram’s own channel header, read 7 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.
373 reactions across 19 posts, in 9 distinct kinds. The most used accounts for 27.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 104 | 27.9% | |
| ❤ | 80 | 21.4% | |
| 🔥 | 64 | 17.2% | |
| custom 5384235070292768522 | 42 | 11.3% | |
| custom 5220034484837042918 | 33 | 8.85% | |
| ❤🔥 | 19 | 5.09% | |
| 🕊 | 16 | 4.29% | |
| 🤔 | 13 | 3.49% | |
| 👎 | 2 | 0.536% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 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 373reactions 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 30 April 2026 to 31 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.
Всегда интересно, кто что видит на своей работе. Например, админы вот такое :) А что у вас перед глазами на работе? 🖱Кстати, сегодня День системного администратора! С праздником, друзья! 🖥
❤🔥5❤4👍4
Почему высокопроизводительным СХД уже мало просто «поддерживать сеть» Сегодня вопрос высокопроизводительного доступа к данным уже не сводится к тому, есть ли в системе iSCSI или FC. Если раньше достаточно было просто «подключить хранилище», то теперь от СХД ждут зрелой функциональности и готовности работать в современной инфраструктуре – с NVMe-дисками, 25/100GbE и RDMA-сетями. На таком фоне работа по протоколу iSCS…
👍7❤4
Композитный пул: новая логика роста Как мы уже с вами разбирали самый сложный момент в жизни любой СХД, когда данных становится больше, чем был прогноз. Здесь есть два пути. 1️⃣: пытаться дальше наращивать старую структуру, добавляя диски по одному и рассчитывая, что все продолжит работать так же. Но тут важно понимать, где именно лежат данные, как распределяются блоки и что произойдет, если один из дисков выйдет и…
👍8🤔2
А ваша ИТ-инфраструктура уже готовится к смене парка машин?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🕐 Как вам кажется, российские компании сейчас чаще откладывают обновление ИТ-инфраструктуры? Оборудование может формально продолжать работать, но при этом уже не соответствовать текущим требованиям по поддержке, производительности и отказоустойчивости. Когда цикл обновления инфраструктуры растягивается из-за бюджета, ограниченного выбора или недоступности привычных решений, потребность в замене только накапливается…
🤔5👍3🔥2
RAID: аппаратный и программный подход Прежде чем мы продолжим тему «тонких томов» и как реализованы у нас «композитные пулы», важно вспомнить базовую вещь: данные редко хранятся на одном диске. Для повышения надежности и производительности накопители объединяют в RAID-массивы – логическую структуру из двух и более дисков, которая помогает распределять данные и снижать риски при отказе одного из носителей. При этом R…
custom 53842350702927685228❤6👍6
Об аппаратной архитектуре СХД BITBLAZE из первых уст Все, кто бывает у нас на производстве, обычно удивляются, что мы сами разрабатываем и производим корпуса. В этом видео директор по развитию Константин Соколов рассказывает, как устроена СХД BITBLAZE. Мы подготовили для вас короткую нарезку с вебинара для партнеров, чтобы вы тоже могли заглянуть внутрь нашей архитектуры. #bitblaze #отличнаяпятницачтобывыбратьсхд
custom 53842350702927685229🔥7custom 52200344848370429187❤1👍1
⚡️Наша киллер-фича: тонкий LUN + расширение физики⚡️ Самый неприятный момент в жизни любой СХД – когда данные растут быстрее прогноза, а свободное место заканчивается. В этот момент многие системы требуют тяжелых сценариев: переносы, миграции, простои, с риском для работающих сервисов. С СХД BITBLAZE можно пойти другим путем. Достаточно докупить диски, подключить их в систему, создать дочерний пул и на этот пул рас…
custom 538423507029276852211🔥8👍6custom 52200344848370429183
Продукция BITBLAZE на карте «Российская электроника 2026» CNews Analytics представил карту и обзор на тему «Российская электроника 2026», где собрал крупных производителей российской вычислительной техники, компьютерного оборудования и электронной компонентной базы. BITBLAZE отмечен в нескольких ключевых сегментах: СХД, серверы, рабочие станции, ноутбуки. Также мы разрабатываем печатные платы, которые интегрируются…
❤7custom 52200344848370429186custom 53842350702927685225
Друзья, продолжается опрос по теме систем хранения данных в России: эксплуатация, требования, ожидания. Опрос займет несколько минут ➡️ https://forms.gle/uRrn3Thshoua8hxZ8 Благодарим всех, кто уже заполнил анкету 💚
❤7👍2
Мы давно сотрудничаем с РЕД СОФТ, и при этом регулярно проверяем совместимость решений, потому что линейки продуктов постоянно развиваются, появляются новые версии и новые функциональные возможности. На этот раз была подтверждена совместимость РЕД ОС 8 и РЕД Виртуализация 8 с системой хранения данных BITBLAZE Sirius 3100 на базе ПО BlazeX. ✅ РЕД ОС 8 обеспечивает надежную отечественную платформу для рабочих и сервер…
👍10❤4custom 52200344848370429182🤔1custom 53842350702927685221
Прокомментировали ввод с 1 сентября 2026 года технологического сбора на электронику ➡️ как повлияет на цены ➡️ будет ли стимулировать производителей #bitblaze
👍9🤔5custom 52200344848370429182custom 53842350702927685222
Showing the 12 most recent of 20 posts we hold for @bitblaze_ru. 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.
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.
А ваша ИТ-инфраструктура уже готовится к смене парка машин?
Shares as published. No per-option vote count is published by Telegram, so none is 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 20 most recent posts we hold, published 30 April 2026 to 31 July 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 — 1,052,628 of 1,336,469entries 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.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“BITBLAZE” (@bitblaze_ru), 676 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/bitblaze_ru.
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.