纪念一下一个时代的结束~ 回顾这几年,不但公开的广告费不赚,连隐秘的角落白得的收益都不拿。不敢说自己分享的内容一定有价值,但敢说没有一条是为了博取流量,更是不惜冒着得罪人的风险提醒了很多信息是投资的噪音。不敢说自己分享的投资策略一定有效,但敢说所有投资策略皆是个人策略或至少认为适合大家的投资策略(风险更低)。

Channel
TingHu888
@TingHu8
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
328subscribers
+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 | -1002222569569 |
|---|---|
| Type | Channel |
| Username | @TingHu8 |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TingHu8 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 07:18 | 328 | no change |
| 7 Aug 2026, 13:40 | 328 | first reading |
Engagement
20 posts held, back to 30 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 1 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.98%
- avg views ÷ 328 subscribers
- Avg views / post
- 19.6
- 20 posts measured
- Reaction rate
- 11.1%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 held
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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (30 July 2026 – 8 August 2026) |
| Views total | 392 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:18 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.
What this channel posts
- Photos
- 210
- Links
- 245
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
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 1 | 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 1 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 1reactions 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 30 July 2026 to 8 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.
Recent posts
刘sir 2026-08-07 22:17: @TingHu888 英文区的“基本面”很多也是包装出来的流量,不过是换了个更体面的说法收割,中文区好歹明牌告诉你我在搞钱。 TingHu♪ 回复: 大多数所谓基本面选手,也是千篇一律的重复各种市场都知道的冗余信息。所以,基本面分析也非常好做,不断的重复加更新公开的媒体报道就行。哪有那么多基本面可写?企业又不是日结打零工的个人,一天一个基本面。最重要的是影响阶段性股价的基本面信息。而具备独立思考甄别能力还愿意公开分享的是极少数
😁1
看了不少聊CPO为何最近涨幅很多的分析,很多人说了很多各种基本面,但这些基本面又不是现在才有,这几个月市场一直在讲,也没影响CPO深度回调啊。我认为核心因素是以下原因:CPO板块在阶段性下行趋势中遇到预期延后的利空后进行了深度回调,在Leopold二级清仓后触底反弹,后续促使CPO摆脱了震荡区间直接往上大幅度拉升的关键因素是8月2号凌晨这则爆炸性消息的扩散➤英伟达副总裁宣布CPO开始量产,下半年大规模导入全球各地AI工厂,外加强调Scale-up带宽需求是Scale-out的10倍。这直接把之前的量产延期预期(可回看6月份CPO相关推文)基本打消了,现在预期又拉回来了。这属于典型的大回调底部出现后又出现大的利好带来的大幅度上涨。
看到很多人死在黎明前夕,其中不少人不割肉也可能直接爆仓,割肉或爆仓后市场还下行了一段路。这其实就是容错率的问题,杠杆越高,容错率越低。可以赚更多钱的代价就是也可能亏更多的钱。常在河边走哪有不湿鞋呢?智者千虑也必有一失啊。只能说,已经通过杠杆赚到大钱的最好收点手吧,别再大仓位赌了。
其实以前基本都是金字塔分批挂单的,过去捞油水做波段都是如此,大家还有印象不?还教了一些不同时候正倒金字塔的挂法。也就最近一段时间,部分抄底追求极致的精确,想要一箭射靶心🎯。之前就感受到了,所以我说我不想带短线了,当然了,还有怕某一次抄底带大家掉坑,所以更加谨慎,想要足够精确安全。
作为一个交易工具只有手机,还不喜欢装各种提醒软件,还没有把大把时间放在盯盘上的人来讲,似乎只有提前预判挂单这一种做法,或者运气好,正好盯盘的时刻发现了机会,直接买入,过往也遇到这样的机会实时分享过。一个人单打独斗就是这样,好像确实没有更好的办法了。
Gianna 2026-07-31 16:19: @TingHu888 关于T大1100撤单的我也想了下,如果没有这样的判断和谨慎,那之前1500的单子也不会撤,只能说没办法做到每一次挂单都完美吧,投资市场就是这样,大趋势判断对胜率高已经非常棒了 TingHu♪ 回复: 我现在发现我已经上了贼车,就是公开场合不能错,短线分享还越来越频繁,而且还越来越追求精确,但越这样越不行。好处是很难掉坑,抓到就是赚到,不会先大亏;坏处是容易错失机会。相信老朋友还记得我以前经常讲模糊的正确,主要讲的是趋势买卖,但短线频繁分享会破坏这个投资逻辑。这不是一件好事。
哈哈哈,其实,我也可以马后炮一下,说我其实接到了,只是一开始浮亏没好意思说,现在赚了再显摆一下。 但我这人在这方面说不了谎,而且,这种显摆给我带不来成就感,反而会带来人格撕裂。这两个单子我在28号撤了,因为我感觉还要跌,我就重新设置了几个900多的,结果是确实又跌了不少,但只跌到970。
Seventh Trait 2026-07-31 15:10: @TingHu888 不是说无法做到每一个反弹都吃得到吗?既然这是无法做得到的事情又为什么还要反思呢?反思的目的是为了以后把所有反弹都吃到? TingHu♪ 回复: 反思的目的是精益求精,看起来是为了获得更多金钱,但对我来讲,是获得更多“事做成”的成就感,如果能帮大家赚到钱,那成就感会更多。 市场中有很多波段,不可能都赚到,很多波段并不符合自己的交易逻辑,吃不到是无所谓的。但如果符合,却只是差一点,就是会有遗憾。遗憾是常态,但反思不能缺。
已经连续两次公开的抄底计划都发生了底部价格比我预期的高一点,上次差一点点,这次比一点点多一些,前面都还行,甚至很精确。上次已经反思过一次了,没想到又来一次反思。虽然前面还赚了,最近也没亏钱,但总感觉不对劲,快到嘴的肉没了。下次我能不能马后炮一下?我先抄,赚了就发出来,亏了就不吭声
猛,一日反弹到下降趋势线压力位。再次可惜,昨天再插一插,今天Leopold清仓新闻再爆出来就好了,这样就正好吃到了。 一点反思,市场痛麻+离目标位很近的时候可以先买,不必追求太精确的底部价格; 一点提醒,上升/下降的技术趋势线不会永对,早发现早受益,晚发现晚受益,太晚则生变➤逆趋势或破位。
一个有趣现象,一些人赚了钱有了很多知名度之后,市场的一些韭菜还会默认认为他们能够低买高卖,不可能亏钱,凡是说亏钱的都说是做戏。拜托,一个人一直在赚钱,那天下之财不都被尽收囊中了吗?进攻强的人在做对方向的时候会展现出来超强的赚钱能力,很容易吸引眼球,一旦方向变了,死的也快,过刚易折
Showing the 12 most recent of 20 posts we hold for @TingHu8. 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 — 1,083,683 of 1,350,102entries 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.
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.
“TingHu888” (@TingHu8), 328 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/TingHu8.
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.