Channel
@hollyink
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,062subscribers
+30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002258439522 |
|---|---|
| Type | Channel |
| Username | @hollyink |
| Created | Between 1 October 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/hollyink |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 09:37 | 1,062 | +18 |
| 10 Aug 2026, 13:46 | 1,044 | +13 |
| 8 Aug 2026, 00:21 | 1,031 | no change |
| 7 Aug 2026, 16:27 | 1,031 | -1 |
| 7 Aug 2026, 13:01 | 1,032 | first reading |
18 posts held, back to 9 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 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 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 18 (9 July 2026 – 6 August 2026) |
| Views total | 5,152 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:21 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.
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 2 of the 18 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 18 most recent posts we hold, published 9 July 2026 to 6 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.
《达利欧最新访谈：已身处AI泡沫之中，投资组合的1%是比特币》 @hollyink 80年的大周期，我们身处历史的哪个位置？ 桥水基金创始人瑞·达利欧（Ray Dalio）近期接受了知名商业播客节目 The Diary Of A CEO 的深度专访，谈及了自己对 AI 泡沫、80 年大周期迭代和比特币的看法。在访谈中，达利欧揭示了我们为何正处于 AI 泡沫之中，还阐述了泡沫即将被刺破的 3 大征兆，同时认为虽然资本家会是 AI 变革的最大受益者，但拥有卓越的人类智能并能与他人合作的人，仍然会在未来表现出色。 https://holly.ink/archives/1265
加密草台班子： 3个月 Web3 超过300个项目被盗 ！ 加密新手最全避坑指南 ！保护你的钱袋子 ！ 揭秘币圈潜规则： 你以为的安全全是纸糊的。 https://youtu.be/mWCJia2hhIE
近日，一位 Anthropic 工程师发布了一份关于「智能体系统的循环工程」的 11 页资料，把 Loop Engineering 放在 Prompt Engineering、Context Engineering 和 Harness Engineering 之后，视为 AI 编程进入下一阶段的关键方法。 软件开发的重心正在从「人类告诉模型写什么」，转向「人类设计一个会自己排队、取任务、写代码、检查结果、保存状态并继续运行的系统」。 过去一年，AI 编程工具的叙事大多围绕模型能力：代码补全更准、上下文窗口更长、代理能一次性完成更复杂任务。但 Loop Engineering 讨论的是另一件事：当生成代码本身越来越便宜，工程师真正要设计的，变成一个可持续运转的循环。机器可以不断产出候选方案，人类要决定哪些结果可信、哪些必须挡下、哪些长期成本正在被隐藏。 AI 编程从「一次提示」走向「持续循环」 Loop Engineeri…
为什么MEME 钻石手成了接盘侠？ 我觉得，现在 Meme 正在走向一个终点 市场越来越像 ICO 后期。 2017 年：每天几十个 ICO。 后来：没人研究白皮书。 只研究：什么时候上市。什么时候卖。 最后：整个模式崩掉。 现在 Meme： 也开始出现同样特征： 社区价值越来越弱； 持有价值越来越弱； 交易价值越来越强； 流动性迁移越来越快； 生命周期越来越短。 当所有参与者都默认 "第一时间买、稍后就卖" 时，市场就进入了一个近似负和博弈： 除了少数极早入场者、做市者、机器人和平台，大部分人的收益来自彼此，而每一轮交易还要支付手续费、滑点和失败成本。 长期来看，这种结构很难持续。 真正发生的变化，是 Meme 市场已经从 "叙事驱动" 演变成了 "注意力套利 + 流动性套利"。 🐦 https://x.com/AntCaveClub/status/2083944297834111255?s=20 📱 http…
《Dan Koe：逃离打工人宿命，如何在AI替代潮中生存下来？》 如果你轻信社交媒体上的恐慌言论，可能会觉得「所有工作马上就要被 AI 取代了」。许多人因此给自己贴上「反 AI」的标签，试图用网络上的愤怒掩饰自身不愿改变、拒绝成长的事实。 然而，AI 并不是最大的威胁，真正的危机在于将自己的生存和幸福完全寄托在他人身上。技术变革来临时，如果你还天真地相信别人理应对你的未来负责，那注定会大失所望。 靠哭诉是无法控制 AI 这个庞然大物的。在社交媒体上发帖抱怨你有多讨厌 AI，并不能阻止工作被取代，也绝对无法阻止在这个技术不断发展的时代，获取成功所需的核心技能发生改变。 本文将探讨如何逃离「薪水奴隶」的打工人宿命，并找到有意义的工作方式。 https://holly.ink/archives/1246 好资源分享： @hollyink
神器： Mac 垃圾文件清理 🧹 很多安装的无用软件， 废弃文件直接清除。 释放了 110 GB 的存储。 https://t.me/yongzhuan_bot?start=sr_WTc0NDE2MTlBSUwKTW9sZQ
《Robinhood MEME 23 万美元实战复盘！ CLARITY Act 即将引爆加密市场？真正的机会才刚开始？》 首先： CLARITY Act 一定会通过， 只是讨论何时通过的问题。 现在的市场处于一个前 CLARITY、后 GENIUS 的政策过渡期。 三波势力争夺定义权： 传统金融 → 通过 ETF + 合规通道进入（慢、稳、大） 【代表： 华尔街】 原生加密 → 通过 CEX + DeFi 继续运转（快、乱、内卷）【币安、OKX、Coinbase】 链上基建 → 通过新 L1/L2 争夺应用层（新叙事、新用户）【Hyperliquid、Polymarket、Robinhood Chain 】 Robinhood Chain 不是典型的 L1。它兼顾了上面三个生态位。 是华尔街的”反向入侵”加密生态 Robinhood Chain 不是要替代 Solana 或以太坊。它要替代的是 Bina…
梁文锋因对闭门会内容外泄不满，叫停DeepSeek第二轮融资 - 链接 《梁文峰四小时投资者交流会》 完整版下载： https://holly.ink/archives/1239
《加密货币清晰法案“Clarity Act”解析 – 未来6个月市场玩法预判》 最近， a16z 合伙人 Chris Dixon 发文呼吁通过 CLARITY Act，称这将让美国”再次像商业互联网时代一样引领未来”。 GENIUS Act（稳定币监管）已通过，CLARITY 是其自然延伸， 为区块链网络和数字资产市场建立联邦监管框架。 首先： CLARITY Act 一定会通过， 只是讨论何时通过的问题。 因为， 除了美国推动法案，海外其他国家也在进行。 如果通过，美国将主导下一代金融基础设施；如果不通过，创新将流向海外。 — #判断 美国想赢， CLARITY Act 必须通过。✅ 📖 https://holly.ink/archives/1229
Ondo Perps 刷奖励套利工具：ONDO 低成本自动化空投, 每周 17 万美金 ！ 一个脚本，每天自动跑，Points 每周自动到账。 2026 年，一个叫 Ondo Perps 的产品正在改变一件很多人没注意到的事： ONDO 官网： https://app.ondoperps.xyz/?ref=8RU3VB 你能在链上做空 AAPL、做多 NVDA、20 倍杠杆玩 HOOD。 而且，24 小时不关门。 🪙 Points：空投时代的最后一班车 Ondo Foundation 在 Perps 上启动了 Points 奖励计划： – 每周从 固定池子 分配 Points – 你的份额 = 你的交易量 ÷ 全网总交易量 – Points = 未来 $ONDO 代币的兑换券 – 每周自动发放，无需领取 这不是积分商城换杯子的那种积分。 这是 Ondo Finance： 一个管理着 数十亿美元 RWA…
本周加密货币漏洞中被盗金额超过 7580 万美元： • @Ostium 的 OLP 保险库损失约 2400 万美元 • @AFX_XYZ 被利用损失约 2400 万美元 • @wanchain_org 在 Cardano 桥漏洞中损失约 1000 万美元 • @VerusCoin 的桥储备损失约 750 万美元 • @BSquaredNetwork 在流动性池漏洞中损失近 400 万美元 • @LayerZero_Core 的执行者钱包被入侵，损失约 240 万美元 • @Allbridge_io 被利用损失约 165 万美元 • @cascade_xyz 的 CLS 保险库损失约 134 万美元 • @42dao_official 因预言机漏洞损失约 91.2 万美元 ⚠️ 关停 • @movement_xyz Labs 申请第 11 章破产保护 • @BitMEX 宣布将于 9 月关闭运营 • @rhinofi 正在关闭…
X 封号潮不是一个事件，是一个信号。 X 一年内封了 8 亿个账户 。 每一个平台都在告诉你一个道理：你在它们上面的"资产"不是你的。 我称之为： 数字霸权主义 🐦 https://x.com/AntCaveClub/status/2079185142325887309?s=20 关注更多： @hollyink
Showing the 12 most recent of 18 posts we hold for @hollyink. 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 — 740,774 of 1,478,351entries 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 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.
@hollyink named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“好了资源站 💰Holly.ink 💎” (@hollyink), 1,062 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hollyink.
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.