微信灰度功能 仅 iOS26.2+可用? 不如写个原相机了...
Signed 热心网友

Channel
@bzapps
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
2,325subscribers
+43 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002463605380 |
|---|---|
| Type | Channel |
| Username | @bzapps |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/bzapps |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 21:13 | 2,325 | +10 |
| 10 Aug 2026, 05:36 | 2,315 | +19 |
| 7 Aug 2026, 10:28 | 2,296 | +14 |
| 6 Aug 2026, 21:03 | 2,282 | first reading |
17 posts held, back to 23 July 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 2 pagesof 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. It is computed over the 8 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 17 (23 July 2026 – 7 August 2026) |
| Views total | 19,316 |
| Reactions total | 19 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:42 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.
19 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 94.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 18 | 94.7% | |
| 👍 | 1 | 5.26% |
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 8 of the 17 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 23 July 2026 to 7 August 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.
微信灰度功能 仅 iOS26.2+可用? 不如写个原相机了...
Signed 热心网友
试一下吧,开启版本控制的冷启动优化 本来想默认开启的,又担心冲突问题。 所以手动开启吧,感受下区别。 上面的聊天工具附件动画写成对角线了 晚点下载 @WCRefine 的包就行
❤1
Signed 热心网友
从内放出的分组功能: 常规首页分组 插件收纳分组 官方表情分组 其他放出的自用功能: 语音包、消息同步、定时任务、分组转发、 自动跟圈、超级悬浮:默认、扇形、阵列,等等。 后续应该还会有更多,慢慢来吧。 喜欢可投喂支持,超过 50 元可私信加群。 投喂非强制,也非定制,微信群非许愿群。 花了大量时间精力兼容其他插件, 如非 WCR 主因请勿再要求强兼。 兼容是互相的事,别逮着一个开发者薅。 插件反馈:https://t.me/wcrchats 日常吹水:https://t.me/bzapps
❤2
Signed 热心网友
家人们我有点想shi 微信冷启动过程中会加载热更新问题 我让他启动后再加载,重启速度上去了 热更新的小微都不见了 能接受没有小微的再装吧 感觉一地鸡毛啊, gpt快给我重置吧,我需要你!
❤3
Signed 热心网友
预发布最终以公众号为准 反馈 bug 去对应分区反馈 https://t.me/@wcrchats
❤1
Signed 热心网友
WCRefine 悬浮宠物——— 提取Codex 的 没有上下动作可自行补齐或忽略
Signed 热心网友
应要求beta14 的插件收纳是默认开启的 Mik收纳后闪退问题我修不了只有原作者 原本的注册接口,不存在强制收纳 用 Mik去WCR-插件管理-插件收纳-关闭 使用 WCR的插件收纳可不注入独立的收纳 @interface WCPluginsMgr : NSObject + (instancetype)sharedInstance; - (void)registerControllerWithTitle:(NSString *)title version:(NSString *)version controller:(NSString *)controller; - (void)registerSwitchWithTitle:(NSString *)title key:(NSString *)key; @end 例 if (NSClassFromString(@"WCPluginsMgr")) { // 带设置页面…
❤5
Signed 热心网友
隐根不能用就注入无根吧 没有设备测试隐根 至于 Mikoto 打不开的, 就关闭 WCR 的插件收纳 Mikoto从 v9 开始不支持 wcr 的搜索 所以新版也不支持 wcr 的收纳强兼不了
Signed 热心网友
File, posted without a caption
❤4
Signed 热心网友
假是因为临时的 晚些时候会有个真 修完 bug 就是正式版
Signed 热心网友
File, posted without a caption
❤2
Signed 热心网友
视频号点击评论闪退,被微信云控了 😐 修复好了,内部功能没优化完 之前丢失的代码有点多 但是没办法临时更新个版本吧 新测试版有问题未修完,我建议先不要私聊反馈。
👍1
Signed 热心网友
Showing the 12 most recent of 17 posts we hold for @bzapps. 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 — 25,465 of 1,176,251entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@bzapps named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“热心の小窝” (@bzapps), 2,325 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bzapps.
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.