BBZQ 1.5.2-427 Author: NkBe Branch: master feat(core): 新增 BbzqLevelGate 並同步調整設定橋與帳號解析 Commit | Workflow run

Channel
BBZQ Canary Builds
@BBZQ_CI
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
478subscribers
+0 since we began measuring on 18 November 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004470794679 |
|---|---|
| Type | Channel |
| Username | @BBZQ_CI |
| Description | BBZQ 官方频道 @bbx_show 自动上传 BBZQ 的 Action 构建 |
| Created | Between 1 June 2026 and 31 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 November 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BBZQ_CI |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Nov 2026, 22:22 | 478 | no change |
| 18 Nov 2026, 21:47 | 478 | first reading |
Engagement
7 posts held, back to 18 November 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 17.9%
- avg views ÷ 478 subscribers
- Avg views / post
- 85.7
- 7 posts measured
- Reaction rate
- 1.12%
- reactions ÷ views · ER floor
- Posts in window
- 7
- of 7 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. It is computed over the 2 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 7 (18 November 2026 – 18 November 2026) |
| Views total | 600 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 22:22 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
- Links
- 32
Lifetime counters from Telegram’s own channel header, read 18 November 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
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👍 | 1 | 50.0% |
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 2 of the 7 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 18 November 2026 to 18 November 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
Telegram’s own ‘edited’ marker: 0 of 7 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
BBZQ 1.5.2-425 Author: NkBe Branch: master feat(settings): 移動自動領取經驗至隱藏功能並新增手動填寫 AccessKey 將「自動領取大會員經驗」開關移入隱藏功能區,並於 AccessKey 對話框補上手動填寫與清除功能。 Commit | Workflow run
BBZQ 1.5.2-424 Author: NkBe Branch: master feat(playback): 新增強制解鎖小窗播放功能 攔截 PlayConfig\ 的全部構造函數與 fromJsonObject,對 MINIPLAYER 類型強制允許小窗並清空不支援場景列表。 Commit | Workflow run
👍1
BBZQ 1.5.2-423 Author: NkBe Branch: master feat(appearance): 新增彈窗毛玻璃背景功能(預設開啟) 在 Android 12+ 攔截 Dialog.onStart() 套用 FLAG_BLUR_BEHIND 與背景模糊半徑,並於外觀設定頁新增開關(預設開啟)。 Commit | Workflow run
BBZQ 1.5.2-422 Author: NkBe Branch: master feat(mine): 新增啟動時自動領取大會員每日經驗功能 於我的頁設定分類新增開關(預設關閉),在主進程啟動後透過宿主登入 Cookie 每天自動呼叫 /x/vip/experience/add 一次並以本地日期快取防重複。 Commit | Workflow run
❤1
BBZQ 1.5.2-421 Author: NkBe Branch: master fix(appearance): 修復 9.19.0 自訂字體大小不生效的問題 攔截 Resources.updateConfiguration、LimitTextSizeUtil.limitTextSize 以及 BaseAppCompatActivity / ComposeActivity / DialogContainerActivity / VertexActivity 的 getResources(),防止宿主將 fontScale 與 scaledDensity 強制重設回 1.0f。 Commit | Workflow run
BBZQ 1.5.2-420 Author: NkBe Branch: master docs(intro): 移除首頁設定入口並改為引導於嗶哩嗶哩內開啟 保留 WO Mic 與 ReadEra 入口卡片,移除「打開 BBZQ 設置」跳轉卡片並註明所有功能預設皆未開啟,引導用戶前往嗶哩嗶哩「我的 → 設定 → 進階設定」啟用。 Commit | Workflow run
Showing the 7 most recent of 7 posts we hold for @BBZQ_CI. 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.
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 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.
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 18 November 2026 — this entry's latest reading, not the date you are reading this.
“BBZQ Canary Builds” (@BBZQ_CI), 478 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/BBZQ_CI.
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.