Photo, posted without a caption
👍15🤬5

Channel
@WhenFlowersAreInBloom
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
27,101subscribers
-1,791 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001896812961 |
|---|---|
| Type | Channel |
| Username | @WhenFlowersAreInBloom |
| Created | 25 April 2023 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 50 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/WhenFlowersAreInBloom |
Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 84% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 09:16 | 27,101 | +1 |
| 26 Oct 2026, 09:09 | 27,100 | -4 |
| 25 Oct 2026, 07:35 | 27,104 | +3 |
| 24 Oct 2026, 05:18 | 27,101 | -18 |
| 23 Oct 2026, 02:18 | 27,119 | -4 |
| 21 Oct 2026, 23:06 | 27,123 | -10 |
| 20 Oct 2026, 21:06 | 27,133 | -12 |
| 19 Oct 2026, 19:08 | 27,145 | -16 |
| 18 Oct 2026, 16:28 | 27,161 | -38 |
| 17 Oct 2026, 13:05 | 27,199 | -20 |
| 16 Oct 2026, 15:26 | 27,219 | -24 |
| 15 Oct 2026, 12:56 | 27,243 | -27 |
| 14 Oct 2026, 13:40 | 27,270 | -43 |
| 13 Oct 2026, 00:50 | 27,313 | -97 |
| 8 Oct 2026, 13:57 | 27,410 | -134 |
| 4 Oct 2026, 01:21 | 27,544 | -200 |
| 25 Sept 2026, 07:02 | 27,744 | -185 |
| 17 Sept 2026, 06:01 | 27,929 | -37 |
| 15 Sept 2026, 04:18 | 27,966 | -27 |
| 13 Sept 2026, 11:39 | 27,993 | first reading |
26 posts held, back to 25 April 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 126 pages of 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 25 October 2026 |
|---|---|
| Posts held | 26 (25 April 2023 – 25 October 2026) |
| Views total | 15,310 |
| Reactions total | 122 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Oct 2026, 09:11 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.
4,105 reactions across 25 posts, in 12 distinct kinds. The most used accounts for 20.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 843 | 20.5% | |
| ❤ | 748 | 18.2% | |
| 🔥 | 688 | 16.8% | |
| 🥰 | 650 | 15.8% | |
| 😱 | 382 | 9.31% | |
| 🤬 | 340 | 8.28% | |
| 😭 | 339 | 8.26% | |
| 👏 | 54 | 1.32% | |
| 🤔 | 36 | 0.877% | |
| 😇 | 18 | 0.438% | |
| 😨 | 6 | 0.146% | |
| 😘 | 1 | 0.024% |
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 25 of the 26 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 4,105 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 25 April 2023 to 25 October 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.
Photo, posted without a caption
👍15🤬5
File, posted without a caption
👍14🤬5
修复在线脚本我的消息红点已读不会消失的问题 优化模块深色模式下设置页卡片颜色不一致 优化脚本页面底栏加大 优化部分弹窗没有跟随设置的主题 优化部分安全问题,性能问题
👍15😭5❤3
QWishJava脚本文档2026-11-1.md
👍12🤬3
新增一些拓展功能 新增自由切换的模块主题和自定义壁纸 修复抢红包失效的问题 修复已知功能失效的问题 优化toast风格 优化在线脚本体验
👍27😱12❤3😇2🤬1
本项目因不可抗原因停止维护 你的权益会保留并延续到未来的其他关联项目 很高兴您的使用与反馈 也很抱歉给您带来的不便与失落 我们很感谢这一路上的用户提交的宝贵意见 我们才得以解决和改善此项目的各种问题与提升模块非常大的体验 提示: 别升级到9.3.x以上 还能用 在线服务在服务器到期前还能用 明年过年到期 就让夏天的故事也在夏天结束2023-4-25 - 2026-7-5 愿你在这段旅程中找到属于自己的幸福。 May the path make you stronger than the destination could.
😱340😭329👏53🤬39❤36👍18🤔9🥰5
qs脚本下载器,可以下载到在线脚本之外的已下架,未上架,待审核脚本
👍43🤬24❤2
新增 净化/聊天删除QQ表情底栏中的AI选项 优化 消息显示时间支持自定义显示 优化 群打卡获取不到uin闪退(表现为玄学闪退) 优化 防撤回数据库 现在在模块点击防撤回可以查看缓存以及清理缓存 修复 隐藏菜单图标在930异常 修复 一键20赞失效 修复 抢红包在931失效 修复 在线脚本我的消息页无法下滑 修复 9.3.5上因为获取不到当前会话导致的脚本,表情面板异常
👍41🤬25❤9🤔3😨1
优化 上传自定义半透明头像的效果 优化 在线脚本我的消息弹窗弹出效果 移除 你不喜欢的代码
🔥671👍590🥰517❤506🤬111😱15😇8🤔6
https://t.me/QStoryBlacklist 有你想要的答案 不用听风就是雨
🤬118🤔18😱8❤6😇5😨5👍1🥰1
保持了脚本文档的新鲜度
🥰8❤4😱3
新增 辅助功能/资料卡/上传半透明头像 优化 在线脚本ui Java脚本显示效果
❤25😱3
Showing the 12 most recent of 26 posts we hold for @WhenFlowersAreInBloom. 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.
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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“QStory-Release” (@WhenFlowersAreInBloom), 27,101 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/WhenFlowersAreInBloom.
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.