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 189–191 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Aug 2026, 07:15
190
no change
6 Aug 2026, 22:00
190
first reading
Engagement
20 posts held, back to 25 July 2024 — 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
170.5%
avg views ÷ 190 subscribers
Avg views / post
324
1 post measured
Reaction rate
0.309%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 18 July 2026
Posts held
20 (25 July 2024 – 18 July 2026)
Views total
324
Reactions total
1
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 07:15 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
Photos
3
Videos
2
Links
67
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.
Reaction mix
66 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 63.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
42
63.6%
🔥
9
13.6%
😱
6
9.09%
😁
4
6.06%
🤔
2
3.03%
🤯
2
3.03%
❤
1
1.52%
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 18 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 66reactions 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 25 July 2024 to 18 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.
Вышел Ceph v19.2.5 Squid
Пятый бэкпорт-релиз в серии Squid. Рекомендуется обновиться всем пользователям.
Из отмеченных изменений:
* MDS: пофиксили segfault, связанный с завершением MDSContext и постановкой запросов в очередь.
* OSD: поправили логику отката для object info (OI) при частичной записи и оптимизировали Erasure Coding — Twiddle теперь создаёт вектор полного * размера.
* RGW: добавили опцию ssl_ciphersui…
Вышел ceph 20.2.2 (Tentacle)
Второй минорный релиз в ветке Tentacle, как обычно всем пользователям этой ветки рекомендуют обновиться.
Из отмеченных изменений:
* Платформы: добавлена поддержка пакетных установок на Rocky Linux 10 , полный сипсок тут
* MDS: пофиксили segfault возникавший из-за некорректной постановки ретрай запросов в очередь
* OSD
* PGLog: исправлен баг чтоб точно атачить правильную версию к mi…
Вышел ceph 20.2.1 (tentacle)
Это первый минорный релиз в серии тенаклей. Рекомендуется обновится всем пользователям данной ветки.
Разработчики отметили:
• EC Recovery: пофиксили баг в расчёте длины в erase_after_ro_offset() — пустые шарды сохраняли данные, что приводило к assert shard_size >= tobj_size при восстановлении мелких объектов в EC-пулах
• BlueFS: исправлен выбор тома с учётом изменения размера файла при…
Вышел ceph 19.2.4 (Squid)
Четвёртый багфикс-релиз из ветки 19 с кодовым названием Squid. Разработчики рекомендуют всем обновиться.
Разработчики отметили:
- BlueFS: увеличен дефолтный размер WAL-тома до 1GB — чтобы реже получать ENOSPC
- Health: свежедобавленные мониторы больше не будут ложно триггерить MON_DOWN
- RADOS pybind: пофиксили баг в WriteOp.zero() — offset и length были перепутаны местами при вызове C AP…
Спасибо за помощь, нашел багу https://tracker.ceph.com/issues/75253
фикса скорее всего не будет
.. note:: Each RBD image may hold a maximum of 16383 snapshots due to
internal limitations.
Вышел ceph 18.2.8 (reef)
Вышел восьмой, и скорее всего последний, бекпорт (хотфикс) релиз в ветке reef.
Разработчики отметили:
Известные проблемы
- Во время тестировния обнаружился баз при котором во время апргейда с pacific на reef сообщение OSD_UPGRADE_FINISHED может выводиться до того как все OSD реально обновились. Зафиксированных проблем найдено не было, но в целях безопасности больше не рекомендуется выполн…
Что-то с новой работой совсем забил на канальчик, даже про 20 релиз не написал (когда нибудь обязательно исправлюсь)
Сейчас же предупреждение для тех кто любит тестить новинки в проде.
В 20.2 привезли новый крутой EC (FastEC), а вместе с ним такой баг https://tracker.ceph.com/issues/71642 который может доставить много весёлых приключений.
Поэтому если вы поставили 20.2 подождите врубать FastEC.
Вышел ceph 19.2.3 (squid)
Вышел третий бекпорт релиз в 19 ветке (squid). Всем юзера 19 ветки рекомендуют обновиться.
Разработчики отметили:
* RGW: PutObjectLockConfiguration теперь можно использовать для включения S3 Object Lock в существующем бакете с включённым версионированием, даже если этот бакет изначально был создан без Object Lock.
* RADOS: Добавлена новая команда ceph osd rm-pg-upmap-primary-all, которая …
Вышел ceph 18.2.7 (reef)
Вышел седьмой бекпорт (хотфикс) релиз в ветке reef.
Разработчики отметили:
Этот релиз исправляет критическую проблему с BlueStore, которая приводит к сбоям OSD. Она проявляется в релизах 18.2.5 и 18.2.6 (https://github.com/ceph/ceph/pull/61653). Пользователям, работающим с этими релизами, настоятельно рекомендуется обновиться.
Также этот релиз включает ещё несколько важных исправлений для…
Вышел ceph 18.2.6 (reef)
Вышел шестой бекпорт-релиз в ветке reef.
Разработчики отметили:
- ceph-volume: Пофиксили баг связанный с версией cryptosetup
- RADOS: Пофиксили баг связанный с поддержкой IPv6.
подробнее тут:
https://ceph.io/en/news/blog/2025/v18-2-6-reef-released/
#ceph #reef #release #blog #cephexpert
Showing the 12 most recent of 20 posts we hold for @cephexpert. 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 — 1,042,176 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.
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.
“ceph.expert” (@cephexpert), 190 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/cephexpert.
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.