Channel
@huhuhublahblah
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
207subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001119643234 |
|---|---|
| Type | Channel |
| Username | @huhuhublahblah |
| Created | Between 1 March 2017 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/huhuhublahblah |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 14:55 | 207 | -1 |
| 29 Aug 2026, 20:37 | 208 | -1 |
| 22 Aug 2026, 16:24 | 209 | +1 |
| 8 Aug 2026, 11:05 | 208 | no change |
| 7 Aug 2026, 21:22 | 208 | first reading |
19 posts held, back to 2 February 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 1 page of 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 19 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
48 reactions across 11 posts, in 8 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 33.3% | |
| 🥰 | 12 | 25.0% | |
| 🤔 | 5 | 10.4% | |
| 👏 | 4 | 8.33% | |
| 🔥 | 4 | 8.33% | |
| ❤🔥 | 3 | 6.25% | |
| 🤯 | 3 | 6.25% | |
| 🙏 | 1 | 2.08% |
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 11 of the 19 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 48 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 2 February 2026 to 31 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.
九十分钟的纪录片就像时光机，让我们回到了1985年。当时的英国顶流乐队，为了站在美国的舞台中央，剑走偏锋般选择去中国开了两场演唱会，又在机缘巧合之下找了个奥斯卡最佳纪录片导演记录此行。陌生的文化环境、对立的社会制度，过度的媒体曝光与相互冲突的目的和决定让这十天的行程充满冲突。纪录片也因此没能按原计划推出。唯一贯穿始终的，应该是那个年代的中国人对西方文化的渴望与向往，还有被音乐的力量触动过的人们留下的珍贵的成长轨迹。 关于wham，有件小时候的事我还记得。96年我上小学一年级，有天晚上在家发烧，我爸在外面吃完饭后把他的朋友带到家里聊天。这个大大在珠海工作，看我在发烧，就把他的索尼随身听送给了我，里面放的磁带是一盘英文歌拼盘，最后一首就是wham的careless whisper。三十年前这首歌带给我的那种特别的感觉，直到现在当萨克斯间奏响起，我仿佛还能感受得到。 原本纪录片导演拍摄的段落在捂了三十年后终于被重新剪辑，在大荧幕上…
❤5👏1
真·时代故事 https://x.com/tbpn/status/2061582078060445838?s=20
头回听说
🤔4🥰1
上班可真烦。
❤1🙏1
Photo, posted without a caption
多伦多也是好起来了！可能之前也不差只是我out of the loop太久🧐 https://x.com/_torontosociety/status/2049519165505953813?s=10
分享一下我过去四个月的补铁经历： 去年12月初，抽血体检发现铁蛋白只有5，血红蛋白100，红细胞体积也小于标准水平……怪不得我每天都觉得发冷、疲惫、昏昏沉沉，几乎每个月前后嘴上都会出现一到两个cold sore（我以前从没长过这个）🥴我以为是因为运动太少、血液循环不好，所以每周还去跑个2次。我的家庭医生看到我的化验结果，满脸惊讶地问我“你不晕吗？你跑步不大喘气吗？”，我以为只是心肺功能太差，并没联想到贫血或者缺铁。现在回想一下，估计当时只剩点意志力了，体力已经岌岌可危。 收到检查结果后，在家人的敦促下，立即停喝任何咖啡、茶、酒或者相关的饮料。用ai系统地了解了咖啡和茶类饮料对铁蛋白吸收的阻碍作用，掂量了下自己一把逐渐变老的骨头，决定彻底与其告别，后会无期……在亚马逊上买了ferosom forte，喝了几天后，才发现对于我这种铁蛋白低到可以晕菜的病号，这个补剂里的铁蛋白少得可怜，完全不够用😭 12月中旬放假回国，在国内又做…
❤🔥3🥰2
a16z投了24小时连播、话题覆盖更广的MTS，全名monitor the situation。 老美拿出东大搞直播卖货的那一套做内容，卷得火花四溅。这一波充分验证一件事：内容不再只是做市场的方式，它正在成为科技行业的基础设施。
🤯3
tbpn真的值得，两位主播称职、专业、懂协调，藏得住ego（这点对好节目的主持人是多么关键啊）
昨晚手搓出来了俺的第一个CLI app Selah，根据每日心情和状态推荐圣诗片段、旧约故事和祈祷词。过程比IDE更顺。之前以为不习惯开发环境一直没勇气学习，试过了才知道又是没来由的心理障碍，跨过了就好。
❤6🔥1
Channel photo updated
花开富贵了！
❤4
Showing the 12 most recent of 19 posts we hold for @huhuhublahblah. 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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“hu² ｜糊糊🍀” (@huhuhublahblah), 207 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/huhuhublahblah.
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.