我有一种情结,在爱上一个人后就会想去她的家乡旅游,去看一看她自小长大的地方,走一走她曾经上学的路,去她爱去的饭馆尝尝她爱吃的菜,如果能和她一起就更好了,边走在街上边听她向我讲述曾经在这里或哪里发生的趣事,就好像我没缺席过她的人生
❤9
Signed cc

Channel
@weflow_cc
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
8,958subscribers
+1,059 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003455495563 |
|---|---|
| Type | Channel |
| Username | @weflow_cc |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/weflow_cc |
Technology — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 09:37 | 8,958 | +90 |
| 9 Sept 2026, 04:39 | 8,868 | +186 |
| 3 Sept 2026, 18:56 | 8,682 | +115 |
| 31 Aug 2026, 11:06 | 8,567 | +78 |
| 28 Aug 2026, 09:22 | 8,489 | +142 |
| 25 Aug 2026, 03:35 | 8,347 | +80 |
| 21 Aug 2026, 10:47 | 8,267 | +95 |
| 18 Aug 2026, 08:42 | 8,172 | +117 |
| 15 Aug 2026, 06:13 | 8,055 | +55 |
| 12 Aug 2026, 04:57 | 8,000 | +81 |
| 8 Aug 2026, 19:23 | 7,919 | +20 |
| 7 Aug 2026, 21:16 | 7,899 | first reading |
67 posts held, back to 26 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 20 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. It is computed over the 18 of 25 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 67 (26 July 2026 – 28 August 2026) |
| Views total | 40,341 |
| Reactions total | 291 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 17:17 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
885 reactions across 51 posts, in 9 distinct kinds. The most used accounts for 43.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 387 | 43.7% | |
| ❤ | 282 | 31.9% | |
| 👍 | 97 | 11.0% | |
| 💩 | 50 | 5.65% | |
| 👀 | 48 | 5.42% | |
| 💊 | 13 | 1.47% | |
| 👾 | 5 | 0.565% | |
| 🔥 | 2 | 0.226% | |
| 👎 | 1 | 0.113% |
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 53 of the 67 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 885 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 67 most recent posts we hold, published 26 July 2026 to 28 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @weflow_cc. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 67 most recent posts we hold for this entry, published 26 July 2026 to 28 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
我有一种情结,在爱上一个人后就会想去她的家乡旅游,去看一看她自小长大的地方,走一走她曾经上学的路,去她爱去的饭馆尝尝她爱吃的菜,如果能和她一起就更好了,边走在街上边听她向我讲述曾经在这里或哪里发生的趣事,就好像我没缺席过她的人生
❤9
Signed cc
目前深挖针对盗用WeFlow代码内容的Viwoo导出助手,获得了以下信息: 公司名:惠州大鹅软件有限公司 公司地址:惠州市仲恺高新区惠风七路7号公园壹号广场商务办公大楼11层01号(广东惠州大学生创业孵化基地) 公司法人:胡丽娟 最终受益人:谢春玉 法人留存电话:18933507661 公司域名:daetool.com 盗版软件展示地址:https://www.daetool.com/derive?channel=044 公司邮箱:[email protected] 法人留存邮箱:[email protected] 此公司还将盗用换皮后的软件,进行了软件著作权申请:https://aiqicha.baidu.com/copyright?pid=67403485637804&softId=copyright_e4cdd31b62088b4efa2797f308fe329d 不但收费,并且收费价格极…
👍21
Signed 鸡 小龙
我愿称weflow就是 4.0 微信最高的山 最长的河🤷♂️ 一想到weflow是第一个公开解密朋友圈的 导出用rust重构后基本最快的 后续即将上线公众号导出和协议发消息的 我的胸膛就不自觉的挺起😁
👍11
Signed 寻茶 | 🥲
每天上网就能看到一群傻逼,中元节结束了你和你老冯怎么没被收回去😂 https://www.daetool.com/derive?channel=044
Signed cc
Pro20x下放低价组 0.12倍率 高缓存; 快去用,要不然就没了。使劲蹬! https://aiapi.aiqji.cn/
Signed 鸡 小龙
https://testflight.apple.com/join/1Nb5MwPX 公测版本
Signed 鸡 小龙
漫长的人生总是要无数次调整心态去接纳一些事与愿违
🤡3
Signed cc
新项目(代号alpha)在秘密启动了 预计会加入公众号导出 后续发消息以及更多功能还在筹备中 但是还差一个更好的名字 所以各位有没有名字来推荐呢
❤5
Signed Shenandoh
这边建议宝子去用最新闭源weflow的组件呢,为什么对不齐这些功能呢,是因为没有源代码做不到了么?😂
👀9
Signed cc
自从AI变得让普通人也可以轻易使用之后,开源的环境变得更加恶臭了,我不明白这位“开发者”是怎么厚着脸皮直接将最后一版开源的WeFlow改了个名字再让AI稍加改动就变成自己的项目然后发出去的,我没有在任何致谢或来源部分看到WeFlow的名字。 你甚至对此深感骄傲么,commit里清楚的记录了你是怎么一步一步从weflow的原始代码改的,你甚至连最基础的洗分支都不知道,仅靠AI做你的外置大脑就这样上传了一个项目 我也不知道你是出于虚荣心还是什么作祟在出此下策做了这样一个项目,我从来都没说不能借用weflow的东西,许多大脑发育正常的人都知道写在致谢或一个显眼的地方,而你不光不只是借用了weflow,甚至是完全克隆weflow改个名字改点ui就声称这是你自己的了。 你真给你们学校丢脸,一个学生连最基础的所有意识都没有。 图1为个人主页,图2为其项目中的resource文件夹,而这与各位群友本地安装的weflow中的resour…
👀20❤2👾2
Signed cc
Photo, posted without a caption
❤6
Signed cc
新团队的版本将需要付费使用,或给原团队众筹20x来继续面向群内更新
Signed cc
Showing the 12 most recent of 67 posts we hold for @weflow_cc. 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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“WeFlow通知频道” (@weflow_cc), 8,958 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/weflow_cc.
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.