Channel
@tsuFeed
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,979subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001432765801 |
|---|---|
| Type | Channel |
| Username | @tsuFeed |
| Created | 10 November 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| 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/tsuFeed |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:56 | 1,979 | +1 |
| 9 Aug 2026, 23:36 | 1,978 | -1 |
| 6 Aug 2026, 17:16 | 1,979 | no change |
| 6 Aug 2026, 16:43 | 1,979 | first reading |
20 posts held, back to 20 January 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.
| Window | Rolling 30 days · latest post in window 20 July 2026 |
|---|---|
| Posts held | 20 (20 January 2026 – 20 July 2026) |
| Views total | 472 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:10 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.
74 reactions across 11 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 74 | 100.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 13 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 74reactions 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 20 January 2026 to 20 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.
招行万事达借记卡明日上线ApplePay 据招商银行客服消息，7月21日起，招商银行万事达借记卡将支持绑定至 Apple Pay。 该Apple Pay虚拟卡的相关信息可参考 https://t.me/encmasuta/877 *明日正式发布时可能有所调整 感谢 Roy He, JOKe 投稿 #招商 #ApplePay #万事达 #万事网联
现在模型厂搞这些 PR，说实话有一种手机厂搞参数对标的感觉……如果要用这种风格写广告语的话： 🌞 GPT-5.6 Sol｜时 代 旗 舰 前沿性能，再攀 Mythos 级算力巅峰。 全球首发 OpenAI IntelliToken 智能计算技术，在保持同等前沿性能的同时，任务耗时至高降低 50%。搭载全新 OpenAI「瓯诧」分布式 Agent 架构，至高可协同调度 1000 个智能代理，复杂任务，一呼百应。 旗舰性能、旗舰智能、旗舰体验。 集 OpenAI 前沿科技之大成，重新定义时代旗舰。 🌍 GPT-5.6 Terra｜全能越级旗舰 与 GPT-5.6 Sol 同代、同源、同架构，带来全面无短板的旗舰体验。 搭载 OpenAI 欧文斯湖能效优化技术，重构推理链路，释放革命性能效表现，相比上一代综合能效比至高提升 40%。全新 Agentic RL 深度加持，开启 Max 强度后，复杂推理能力越级媲美 GPT-…
❤6
Photo, posted without a caption
❤7
好吧发晚了，Sam已经说了是 ChatGPT Work 了
ChatGPT和Codex客户端终于合并了 其实早有端倪： 1. 三个月前就有说 Superapp 计划 2. 这几天 Codex App 启动已经是 ChatGPT 的 logo 了 3. 昨天 tease 说会发布 ChatGPT Wxxx，我猜是 ChatGPT Work，对标 Claude Cowork 冲刺！全人类都要用上 AI！
❤6
【做了一个萨莉亚扭蛋】 导入了 上海 广东 北京 香港 台湾 萨莉亚的菜单，选定预算，扭蛋就可以看到今天吃什么。非常适合选择困难症。 明天会把武汉萨莉亚最新菜单导入进去。 在这里玩👇 https://tsuba.ng/saizeriya 灵感来自于日本原版的 サイゼリヤ1000円ガチャ，感谢。微信小程序版近期我也会尝试做上，如有问题和建议可以私聊反馈我。
❤9
看了下还是有区别的 ✅ Fugu 是“前置编排”，Fusion 是“后置打分” ✅ Fugu（前置编排）： 入口设“指挥官”拆解任务，挑选 GPT、Claude、Gemini、Deepseek 等中最擅长者组合交替执行，甚至也可以再递归选自己再进行下一轮拆解 ✅ Fusion（后置编排）： 全员（GPT、Claude、Gemini）并行处理，最后由“裁判官”整合输出 所以 Fugu Ultra 还是相对更省钱的，一种 Orchestration，应该是前置做了一些评测集训练了这个编排模型
OpenRouter 一开源，Sakana AI 就突破？ 标题党了，不算开源，但是原理都是路由到合适的模型来达到 Fable 级别效果的 API，Sakana.ai 好能营销 OpenRouter Fusion API： https://x.com/i/status/2065856853989270011 Sakana Fugu： https://x.com/i/status/2068936087838585267
Fyi
❤1
7月1日开始签证涨价 单次涨到15000日元 多次涨到30000日元 冷知识日本七成以上签证收入来自于中国人，因为剩下的大多数地方免签 高市政府死了，还没有签证的按照部分旅行社要求，24日之前递签证还不涨价
Google AI Pro 每月 20 美元，现已包含 YouTube Premium Lite （不含 YouTube Music 权益的 YouTube Premium） Google AI Ultra 每月 100 美元方案，现已包含完整的 YouTube Premium 订阅。🎵🎶✨ 狠狠找老板报销中😘
❤6
更新：银联疑似提前更新汇率了，大家不要盲冲了（可能还是可以，大家可以小充一点先验证一下汇率，在0.0430以下就是正常的）
Showing the 12 most recent of 20 posts we hold for @tsuFeed. 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 — 142,982 of 1,176,613entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 2 registered channels — 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“tsuFeed” (@tsuFeed), 1,979 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/tsuFeed.
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.