原帖链接:https://x.com/BrianRoemmele/status/2085814816669921707?s=20 这件衣服到底有几个洞? Grok 给的答案是 18 个洞。我的第一反应是 16 个洞。可实际上,这两个答案都是错的。 错在哪里?错在你没办法确定后面到底是几个洞。为什么呢?你能看到的是正面六个洞都能看到纸板,可这并不意味着衣服后面也是对应六个洞。毕竟,为什么不能是后面一个大洞呢?还有,就不可以是两个纵向大洞吗?你没有办法确定这件衣服的背面到底有多少个洞。所以,你就没有办法确定整件衣服到底有多少个洞。 99% 的人答错是正常的。

Channel
余烬
@ciceros_self_talk
On this record: Growth · Engagement · Posts · Citations · Cite this entry
201subscribers
+4 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002182932228 |
|---|---|
| Type | Channel |
| Username | @ciceros_self_talk |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ciceros_self_talk |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:00 | 201 | +1 |
| 11 Sept 2026, 04:56 | 200 | -3 |
| 24 Aug 2026, 11:44 | 203 | -2 |
| 16 Aug 2026, 21:58 | 205 | +6 |
| 10 Aug 2026, 01:31 | 199 | +2 |
| 9 Aug 2026, 04:16 | 197 | 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 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
以前想着用 Excel 或者其他工具来实现每日打卡。昨天偶然之间看到 yihong0618 频道的 bot,就想着能不能通过 Telegram bot 来实现每日打卡以及一些提醒功能。于是,今天跟鲸鱼兄弟讨论、确定设计方案后,一下子就搞出能跑的东西来了。AI 还是强大。
刚刚在推特刷到一个自杀事件。看了一下事情的经过,然后我就想说,就是别人说什么、做什么,其实并不重要,重要的是你自己能说什么、做什么。甚至说你自己能说什么都不重要, 你自己能做什么才是最重要的事情 。当我说“别人”的时候,这个“别人”是除你之外的任何人,不管你将这个别人看得有多重。不要轻易地被别人说的话、做的事给奴役。
我真心觉得,Buffett Munger,以及段永平阿段,这些人不写书,可却是真正的老师。 可能是在约翰逊博士传记看到的吧,就有人问约翰逊博士,「您是怎么学习逻辑的?」,约翰逊博士说:「脑子。先生。是用脑子学习逻辑的。」 我对这几个人的感激之情无以复加,因为这几个人教我怎么用脑子来学习逻辑。
和朋友聊哭了 身心健康最重要 多和同频的人打交道
现在笔记本电脑上面装了:claude code,OpenCode,Kimi code。接下来打算装 CodeX,走 DeepSeek API。用的都是鲸鱼兄弟的 API。哦,还有智谱当备用。就像我手机上装了好几个梯子,一个主用、其余备用,就怕哪天哪个梯子挂了…
虽然孙的身体表面上看不出致命伤痕,但是在切开腰背部以后,法医发现,孙志刚的皮下组织出现了厚达3·5厘米的出血,其范围更是大到60×50厘米。孙志刚生前是一个身高一米七四、肩宽背阔的小伙子,这么大的出血范围,意味着他整个背部差不多全都是出血区了。 “翻开肌肉,到处都是一砣一砣的血块”4月3日,中山大学中山医学院法医鉴定中心解剖孙志刚尸体,孙志刚的两个叔叔孙兵武和孙海松在现场目睹了解剖过程。“惨不忍睹!”孙兵武说,“尸体上没穿衣服,所以伤很明显。” 孙兵武说,他看到孙志刚双肩各有两个直径约1·5厘米的圆形黑印,每个膝盖上,也有五六个这样的黑印,这些黑印就像是“滴到白墙上的黑油漆那样明显”。孙兵武说,他当时听到一名参加尸体解剖的人说“这肯定是火烫的”。 孙兵武说,他看到在孙志刚的左肋部,有一团拳头大小的红肿,背部的伤甚至把负责尸检的医生“吓了一跳”,“从肩到臀部,全是暗红色,还有很多条长条状伤痕。”医生从背部切下第一刀,随着手术刀划动…
[USA For Africa - We Are The World (HQ official Video) - YouTube](https://www.youtube.com/watch?v=s3wNuru4U0I)
经过测试,设计一套质量还过得去的 JLPT 模拟题,花费大概是一块钱。
中午花几块钱的瑞幸还是划算:不仅能喝上一杯冰“水”,还能在有空调、无烟味的地方坐上两个小时。
--- layout: post title: [2026-w31](https://hong525-gh.github.io/hong525_blog/2026/08/04/2026-w31.html) date: 2026-08-04 08:13 +0800 --- Date range: 2026-07-27~2026-08-02 > 「Our main business is not to see what lies dimly at a distance, but to do what lies clearly at hand.」 > > Thomas Carlyle 引用某些人的话,不是因为这些话是这些人说的,而是话本身有道理才引用。加人名和出处是尊重对方的脑力成果。 What I didn't do: - 不再详细说周报的每一件事 - 调整后,不再背包上下班 - 尽量不使用敲打输入法、而是使用语言输入法 …
调整后的桌面布局。这样一来,屏幕和笔记本电脑都能正常使用。
Showing the 12 most recent of 20 posts we hold for @ciceros_self_talk. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“余烬” (@ciceros_self_talk), 201 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ciceros_self_talk.
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.