4 measurements spanning 7 days, net +5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,441–1,465 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 06:56
1,462
+18
10 Aug 2026, 00:54
1,444
-12
7 Aug 2026, 08:23
1,456
-1
6 Aug 2026, 13:51
1,457
first reading
Engagement
20 posts held, back to 4 August 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
15.9%
avg views ÷ 1,462 subscribers
Avg views / post
233
20 posts measured
Reaction rate
1.88%
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 15 of 20 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
20 (4 August 2026 – 6 August 2026)
Views total
4,657
Reactions total
72
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 13:51 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.
Reaction mix
72 reactions across 15 posts, in 16 distinct kinds. The most used accounts for 15.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👏
11
15.3%
😨
9
12.5%
🤣
8
11.1%
🤮
7
9.72%
😁
6
8.33%
👍
5
6.94%
🔥
5
6.94%
🖕
4
5.56%
😱
4
5.56%
👎
3
4.17%
🤯
3
4.17%
❤
2
2.78%
🙈
2
2.78%
🍾
1
1.39%
🐳
1
1.39%
🦄
1
1.39%
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 15 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 72reactions 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 4 August 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.
Google DeepMind CEO Demis Hassabis 卸任
#Google
Google 对其 AI 部门 DeepMind 进行了领导层重组,诺贝尔奖得主、DeepMind CEO Demis Hassabis 卸任,他将担任新设立的首席科学家职位并改任董事长。资深工程师以及 Google Brain 联合创始人 Jeff Dean、Sanjay Ghemawat、Oriol Vinyals 和 Quoc Le 都离开 Google,他们成立了一家公益性 AI 企业 Discovery Loop,专注于机器学习、科学和工程领域的突破性研究。这次人事变动恰逢 Google 最新 Gemini 模型的发布滞后,原计划 6 月发布,但至今仍未发布,引发了 Google 落后于竞争对手 Anthropic 和 OpenAI 的担忧。
https://www.reuters.com/business/google-s…
微软要求工程师不要最大化 AI Token 使用
#Idle
为了推广 AI 工具,许多企业将 AI 使用率作为绩效考核的一部分。结果就是员工为了绩效致力于最大化 AI 使用,导致企业很快发现 token 费用大幅超出预算。软件巨头微软成为最新一家建议工程师限制使用 AI 的公司。微软执行副总裁 Jay Parikh 在一封发给微软员工的邮件中要求工程师专注于业务成果,而非最大化 AI token 的使用量,为了“从 token 投资中获得更大的价值”,微软将比其它模型更便宜的 OpenAI GPT-5.6 设为内部使用的默认模型。自 2026 年 7 月起,微软各部门将设定“AI token 预算目标”,员工可以追踪各自的 AI 支出。
https://slashdot.org/story/26/08/04/1833219/microsoft-tells-engineers-tokenmaxxing-is-not-what-…
Waymo CEO 解释为什么光靠摄像头难以实现自动驾驶
#科技
Waymo 联席 CEO Dmitri Dolgov 在 Y Combinator 的 Startup School 发表演讲,解释为什么自动驾驶汽车需要的传感器不能仅限于摄像头。特斯拉汽车只配备了光学摄像头,它的辅助驾驶系统依赖于来自摄像头的数据。Dolgov 解释说,人类仅靠眼睛就能驾驶汽车,如果自动驾驶系统的目标是实现人类水平的驾驶,那么只靠摄像头可能够了,但上限也就是人类水平,而无人驾驶汽车被寄希望有更高的安全标准。相比下,Waymo 的自动驾驶汽车使用了摄像头、激光雷达和雷达三种传感技术。摄像头提供高分辨率和彩色图像,它们是被动传感,在黑暗和强光下性能会下降。激光雷达直接测量世界的三维结构。雷达能穿透雾、雨、雪,利用多普勒效应直接读取速度。激光雷达和雷达都是主动传感器,在漆黑的夜晚或刺眼夕阳下也能清晰探测物体。三种传感器并不是互为冗余,而是组合成一个完…
Showing the 12 most recent of 20 posts we hold for @SolidotR. 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 — 84,381 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.
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“Solidot 纯净版” (@SolidotR), 1,462 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/SolidotR.
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.