HAPPY NEW YEAR 🎉

Channel
胡图图粉絲全球後援會
@hututu00
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
727subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001655125509 |
|---|---|
| Type | Channel |
| Username | @hututu00 |
| Description | 项目仓库 https://tuu.cat/repo |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hututu00 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:05 | 727 | no change |
| 7 Aug 2026, 17:43 | 727 | first reading |
Engagement
20 posts held, back to 9 February 2024 — 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 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 December 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 60
- Videos
- 8
- Links
- 174
Lifetime counters from Telegram’s own channel header, read 8 August 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
23 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 43.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10 | 43.5% | |
| 🎉 | 6 | 26.1% | |
| 👍 | 6 | 26.1% | |
| 🥰 | 1 | 4.35% |
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 7 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 23reactions 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 9 February 2024 to 31 December 2025, 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
🎨 Attegi:一款优雅、现代且深度适配的 Ghost 主题 给大家介绍我开发的一款开源 Ghost 主题 —— Attegi。 最初是因为找不到满意的移动端阅读体验,所以我自己动手做了一个。它的设计理念是“内容优先”,注重排版细节和留白。 ✨ 核心特性: - 📱 移动端优先:专为手机阅读优化,极简且流畅。 - 📑 原生目录支持 (TOC): v6.9.0 新增!自动生成文章目录,长文阅读体验极佳。 - 🛠 深度适配 Ghost:Ghost 是非常好用的博客管理平台,支持自部署和提供后台编辑页面。Attegi 完美支持 Membership、付费分级、原生卡片(Callouts, Toggles, Quotes 等)。 - 🎨 内置组件库: 拥有精心设计的 404 页面、链接页 (Link Page) 和风格统一的 UI 组件。 - ⚡️ 轻量极速:代码干净,加载速度快。拥有超高 PageSpeed 跑分。 完全免费…
👍2❤1
#Mirrored 打搅了,晚上好。 我们正在经历一个变化。 许多曾经公开托管在 GitHub 上的模块与脚本,正在逐步迁移到私有部署环境中。它们不再提供自由访问接口,而是在请求时记录详细日志,还会拦截部分正常用户的使用。这意味着使用这些资源的脚本,不仅可能随时被拒绝,还可能在无形中暴露隐私或使用痕迹。 面对这一趋势,我们不得不承认:开源生态正在收紧,本是为了规避审查而生的社区,正逐渐建立起一座又一座的高墙。 为了让这些宝贵的工具与规则继续存在,我们发起了 Mirrored 项目。这个计划的核心目标是通过自建与分布式镜像的方式,最大程度地保留和同步现有资源,让脚本不再受制于单一源站或政策变化。Mirrored 的职责类似于互联网档案馆,让社区能继续在透明与自由的环境中使用这些工具。 我们深知,这并非易事。网络审查、源站封锁、反爬虫策略、以及私有化的快速蔓延,都让维持一个开放的资源镜像变得困难。但正因如此,我们更需要行…
❤7
#Surge #Updates SurgePro.sgmodule 近期我们发现,部分脚本在特定场景下可能产生冲突。为提升兼容性与灵活性,最新版 SurgePro.sgmodule 新增 “功能自定义开关”:您可在「Modules → Edit Arguments」中按需启用或停用对应脚本及规则,可避免潜在冲突并简化配置管理。 我们将经过观察和评估后,将此项功能拓展至更多模块。 此功能需要 Surge iOS >=5.9.0, Surge Mac >=5.5.0。 频道: @hututu00
❤1
#Outage #Surge 在 All-in-One-2.x.sgmodule 中我们已经观察到了部分JS资源失效的问题(return zero data),这是由于上游网络不稳定导致我们的自动化程序无法获取所致。请在我们解决这个问题期间耐心等待,并考虑延长自动更新脚本的时间。感谢使用! p.s. 我们的自动更新程序每小时从上游拉取最新脚本,以确保All-in-One-2.x.sgmodule 一直保持最新。
HAPPY NEW YEAR 🎉
🎉6
#Outage 服务器炸了不要紧,因为频道主是 Chill Guy。 由于我们用于生产环境的服务器也莫名其妙爆炸了,现影响以下服务: (未提及的服务仍旧运行中) [⚠️] Backend@SubsConverter [⚠️] API@URLShortener [⚠️] ChatAPI - Next [✅] tutuInsightsBot 正在快马加鞭迁移恢复服务,已服用两杯冰美式续命。 修复状态实时更新中。
https://utgd.net/article/20970/
#Outage 由于我们用于开发环境的服务器莫名其妙爆炸了,现影响以下服务: (未提及的服务仍旧运行中) [✅] TutuBetterRules/Surge - CI/CD [⚠️] GitProxy (Alpha) - AllWebServices [⚠️] 一些根本没人用的 Telegram Bots [✅] 可能还有一些读者的基于 Ghost 运行的博客 已解决。
🥰1
https://blog.skk.moe/post/home-network-setup/ #Blog
#Surge #Updates All-in-One-2.x.sgmodule Feat: 新增 Bilibili Pinduoduo去广告,优化了京东,微博去广告。 Chores: 优化了模块的描述,经 Surge 渲染后的分割线,去除了注释部分,审阅模块更新时可以更快划到最下面了。 Chores: 现可用 https://tuu.cat/ADBlock 更短地分享此模块。 如果您觉得好用,请不要吝啬把模块分享给任何人👀📢 频道: @hututu00
#Surge #Update 📢 All-in-One-2.x.sgmodule: 新增了 Arguments 参数,可指定 Weibo 的策略,默认设置为直连。 此功能需要 Surge iOS >=5.9.0
Showing the 12 most recent of 20 posts we hold for @hututu00. 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
Citation-graph rank — 663,237 of 1,340,412entries 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.
Forward network
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.
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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“胡图图粉絲全球後援會” (@hututu00), 727 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/hututu00.
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.