“人类能够持续学习,但 AI 还没有,下一代模型必须要具有持续学习能力。” —— 摘自网传梁文锋在最近一轮投资人会议上的讲话

Channel
昨日书
@Ynewtime_Channel
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
51subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001233633705 |
|---|---|
| Type | Channel |
| Username | @Ynewtime_Channel |
| Created | 12 December 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Ynewtime_Channel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 10:31 | 51 | no change |
| 8 Aug 2026, 12:05 | 51 | first reading |
Engagement
20 posts held, back to 29 August 2021 — 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
- 36.8%
- avg views ÷ 51 subscribers
- Avg views / post
- 18.8
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- 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.
| Window | Rolling 30 days · latest post in window 23 July 2026 |
|---|---|
| Posts held | 20 (29 August 2021 – 23 July 2026) |
| Views total | 75 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 10:31 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
- 239
- Videos
- 12
- Links
- 169
Lifetime counters from Telegram’s own channel header, read 10 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.
- Video runtime
- 3m 13s
- Average length
- 3m 13s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 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 3 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 2reactions 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 29 August 2021 to 23 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.
Recent posts
我的一些 AI 偏好: 1. 技能:不再安装 skills,如有需要,可以把 skills 所属 repo 缓存到本地,显式指定 agent 调用; 2. 模型:弃用 claude 订阅,改用 gpt-5.6-sol,如需 fable 5 走 api key; 3. Harness:本地 agent 用 pi 即可,复杂的工作流再按需切换 claude code; 4. "APIs & CLIs" over "SDKs & MCPs": 简单来说,SDK 和 MCP 是 API 和 CLI 的二次封装,带来了更多的不确定性,如果条件允许,优先用 API 和 CLI;
世界杯半决赛,西班牙2-0完败法国队提前晋级决赛,赛前所有人看好大热的法国队本场表现十分一般,传控上丢分严重,射门效率奇低,奥利塞屡屡丢失球权以至于被提前换下,完全没踢出之前的水平~ 但这就是足球!最强的矛终究负于最强的盾,可惜了。 法国队继续加油,奥利塞加油!
Bun 團隊僅花了11天、約165k USD便完成了一個長達1.78M LOC的代碼庫重構,從Zig到Rust。4個Dynamic Workflows批跑,64個Claude並行開工,最終通過6個操作系統的全量60k+測試和編譯。在社區大量的批評聲中,硬著頭皮完成了主幹分支合入,雖然還未發布生產版本,但已經默默支撐Claude Code運行了一個月。堪稱迄今為止最受矚目的AI重構大型代碼庫活動了(用的是Fable5模型的早期版本)。 https://bun.com/blog/bun-in-rust
Claude Fable 5 已经到了看山还是山的境界了,理解力惊人、主动性极强,不乱用黑话、语言表达能力也是一流。
今日份与 AI 的对话: 在这场 AI 的浪潮下,毫无疑问我们要搭上船。你怎么看 AI 时代下人类的困惑? Claude Fable 5 Max: 「搭上船」这个说法本身就挺值得玩味的——它预设了一场洪水。大家都在喊要上船,却很少有人问这船开往哪里。我觉得 AI 时代人的困惑,有相当一部分不是「会不会被淘汰」,而是把全部精力都花在「不被淘汰」上,以至于没有时间想「我到底想去哪」。 如果拆开看,困惑大概有几层。 最表面的一层是能力的困惑:模型、工具、范式更新太快,永远学不完,永远怕落后。这层其实最不值得焦虑,因为工具本质上在趋同,你不需要追每一个新东西,抓住「用它解决真实问题」这条主线就够了。追新闻的疲惫感,很多时候是把「了解」误当成了「掌握」。 更深一层是身份的困惑。过去的技术革命替代的是肌肉和重复劳动,这一波碰到的是语言、推理、创造——而很多人恰恰把自我价值建立在这些东西上。一个写了十年代码的人,看着 AI 几分…
本届世界杯默契球、冷门和操盘的痕迹也太多了。 1. 昨天的伊朗进球被吹,实际并没有越位,被死死按在小组第三等待区; 2. 土耳其vs美国,超过补时时间裁判不吹最后半分钟3-2决胜; 3. 今天的葡萄牙vs哥伦比亚闷平(表演痕迹太明显... 禁区不攻乱传); 4. 阿尔及利亚vs奥地利过超时时间2分钟同样裁判不吹最后进两个球绝平3-3杀盘; 5. PM预测市场上多个临时注册的号码,临开场前重注数百万美金获利(人称内幕哥); 6. 从小组赛开始到结束惊人的平局率(一直压平一直获益); etc...
SpaceX 股价上市后暴涨,马斯克一天增加的财富,超过了巴菲特数十年在伯克希尔积累的全部身家。彭博亿万富翁指数把他的总净资产记为 1.27 万亿美元。 —— 也算是见证历史了。 https://www.benzinga.com/markets/tech/26/06/53215719/buffett-called-musk-remarkable-but-never-invested
注册了一个新的 Outlook 邮箱,用于后续做一些亲朋好友的订阅共享,比如订阅 Claude/ChatGPT 服务,让不方便订阅的人也体验看看,或者大家一起用,都可以。 当然现在 DeepSeek 已经很强了,在国内完全可以通过 pi agent + deepseek api key 的方式实现很好用的 agent 体验(下午花几分钟的时间快速帮人设置了一下,她自己体验过后的感觉是 DeepSeek 非常流畅,对话也很快很自然)。 小小吐槽下这过程中遇到的巨硬的机器人验证问题,在电脑上体验极差,不知道谁设计出来的交互方式,简直反人类,按了十几次按钮都校验失败,翻了下小红书发现全是吐槽的... 最后还是通过手机端的 Outlook 才成功注册... 找了个演示视频,瞅瞅: https://www.tiktok.com/@djmolehill/video/7621745607748701470
之前经常跟同事讨论定制分层的问题,这是个解决大型软件协作开发的方案,尤其是在一套 2B 软件系统面向多个客户时的研发场景,做法是定义一个 base 分支,做局点无关的基线特性,然后面向不同客户的商发版本拉取独立的定制分支开发,目标是通过基线和定制分层实现成本优化,定制交由外包或者客户,以分摊我司高昂的研发费用(但实际在运作上每年仍然面临高额的定制费用问题,而且是每个新签局点都会做标前解决方案评审的热点问题)。 当然这里不是想讨论商业问题,主要是今天看到一行命令,`git rebase upstream/main`。这行命令的思想跟我们一直追求的基线定制分层是百分百贴切的,而且足够简洁优雅,甚至如果现在去给新员工介绍基线定制分层的问题,我的理解是都不需要画那么多 PPT,面向研发新员工,直接给这行命令就可以了,思想是如此的简洁优雅:rebase 让上游历史在下面打底,你的定制浮在最顶上 —— 定制始终基于上游最新代码。
“昨日”系列:前尘往事、滚滚红尘,目光当然要放远,但妙手常从旧梦中偶得。可曾记得那些年轻岁月中伏案摘下的文字、快意少年郎时潇洒的墨影?而今辗转迁徙,早已尔尔。是故不敢忘、不能忘,走过一段路,就拾掇一些东西,如此甚好。(昨日书一词,最早听自伏仪的民谣《记昨日书》,此处贴切,故引用之。)
Channel name was changed to «昨日书»
Showing the 12 most recent of 20 posts we hold for @Ynewtime_Channel. 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 — 551,574 of 1,160,990entries 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
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.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“昨日书” (@Ynewtime_Channel), 51 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Ynewtime_Channel.
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.