Telegram 已上线 Community(社区)功能,支持将多个独立群组绑定至统一社区下。 如有相关群组需要加入本社区,请直接提交申请,收到申请后会审核。
Signed Guanran Wang

Channel
@nixos_zhcn_news
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
313subscribers
+27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002897051612 |
|---|---|
| Type | Channel |
| Username | @nixos_zhcn_news |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/nixos_zhcn_news |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 19:58 | 313 | +8 |
| 27 Sept 2026, 04:16 | 305 | +5 |
| 14 Sept 2026, 17:19 | 300 | -1 |
| 6 Sept 2026, 23:22 | 301 | +6 |
| 29 Aug 2026, 16:44 | 295 | +3 |
| 16 Aug 2026, 05:55 | 292 | +6 |
| 8 Aug 2026, 08:19 | 286 | no change |
| 7 Aug 2026, 17:12 | 286 | first reading |
20 posts held, back to 8 April 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 19 July 2026. An engagement rate over an empty window would be a number about nothing.
250 reactions across 18 posts, in 14 distinct kinds. The most used accounts for 28.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😱 | 70 | 28.0% | |
| 😁 | 57 | 22.8% | |
| 🎉 | 37 | 14.8% | |
| 🤯 | 22 | 8.80% | |
| 😢 | 16 | 6.40% | |
| 👍 | 10 | 4.00% | |
| 🔥 | 9 | 3.60% | |
| 🤣 | 8 | 3.20% | |
| 🤨 | 6 | 2.40% | |
| ❤ | 5 | 2.00% | |
| 😇 | 4 | 1.60% | |
| 🍾 | 2 | 0.8% | |
| 🕊 | 2 | 0.8% | |
| 🥰 | 2 | 0.8% |
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 19 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 250 reactions 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 8 April 2026 to 19 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.
Telegram 已上线 Community(社区)功能,支持将多个独立群组绑定至统一社区下。 如有相关群组需要加入本社区,请直接提交申请,收到申请后会审核。
Signed Guanran Wang
Posted without readable text
来源 https://t.me/nixos_zhcn/856397
🤯18🎉9😁5🍾1
Signed dram🎀
[unstable] x86_64-darwin 平台即将停止支持 由于 Nixpkgs 开发者精力和构建资源有限,x86_64-darwin 平台即运行 macOS 的 Intel Mac 即将停止受到 Nixpkgs 支持。随着 release: stop building for x86_64-darwin (#493096) 合入,Nixpkgs unstable 将不再会有 x86_64-darwin 构建。请相关设置了 allowDeprecatedx86_64Darwin 选项的用户暂时切换使用 26.05,并尽快迁移。不建议长期自行构建 x86_64-darwin 的软件包。 请注意,Homebrew 也将在 2026 年 9 月将 x86_64-darwin 支持降级至 Tier 3,并于 2027 年 9 月完全停止支持 [2]。Apple 也将在 2028 年停止为 macOS 26 提供安全更新。 …
🎉12😁7🕊2🍾1
Signed dram🎀
cache.nixos.org 基础设施问题异常事件 由于最近开始测试新的 Hydra queue runner 遇到的一些未预期情况,导致上传到 cache.nixos.org 部分路径出现内容异常下载失败。该问题也影响到部分之前已有的路径。 特别提示,此次基础设施异常并非外来攻击导致。另外,由于 Nix 下载 binary cache 路径有签名检查,大家无需担心成功下载的路径内容损坏。 目前 Hydra 已经修复,而 cache.nixos.org 完善检查和修复正在进行中。如果确实受到影响,可以考虑端午节休息一下非必要别玩 NixOS 了。 Update:目前该基础设施问题已经解决,如果还遇到缓存的错误信息,请尝试清除本地缓存 rm -rf ~/.cache/nix sudo rm -rf ~root/.cache/nix nixos-unstable 还未更新原因与该基础设施问题无关。
😁22🤯4
Signed dram🎀
[25.11, 26.05, unstable] Linux 内核 CVE-2026-46331 "PACKET_EDIT_MEME" 本地提权漏洞 Linux 内核网络流量控制 tc 子系统 pedit 动作协议实现存在漏洞 [1][2],任意用户(非特权用户如果可用 unprivileged user namespace 可以获得 CAP_NET_ADMIN 也能利用)可以覆盖任意可读文件的 page cache,效果相当于写入任意文件,可以导致任意用户获得 root 权限。 目前最新 Linux 7.1 中已有修复 [3],稳定版 7.0.13+, 6.18.36+, 6.12.94+ 已有修复。nixos-unstable 暂时还没有更新。 在等待修复期间,请使用如下配置禁止受影响模块自动加载,然后重启机器。绝大部分用户不会用到 tc-pedit,在此情况下正常系统功能不应受到影响。 boot.blacklist…
😁9❤1
Signed dram🎀
NixOS 26.05 “Yarara” 释出 https://nixos.org/blog/announcements/2026/nixos-2605/
🎉16😁2
Signed Guanran Wang
Garnix 将于 7 月 15 日关停:团队加入 Shopify,核心代码现已开源 Garnix 宣布加入 Shopify,其托管服务将于 2026 年 7 月 15 日关闭,届时将清空所有用户数据及构建产物。 目前核心代码已开源(GitHub 仓库),支持用户自建实例。团队亦在寻找有意愿运营公共社区实例的合作者,并对 Nix 社区多年来的支持表示感谢。 https://discourse.nixos.org/t/garnix-is-shutting-down-not-oc/77895
😢16😁1
Signed Guanran Wang
[25.11, unstable] Linux 内核 "PinTheft" 本地提权漏洞 Linux 内核 RDS (Reliable Datagram Sockets) 协议实现存在漏洞 [1][2],错误处理路径对用户提供的内存页面的资源管理不当,使得任意用户可以覆盖任意可读文件的 page cache,效果相当于写入任意文件,可以导致任意用户获得 root 权限。 目前 Linus Torvalds 的分支已包含修复 [3],并已回合至 7.0.10+, 6.18.33+, 6.12.91+, 6.6.141+。对于 NixOS 用户: - 请 NixOS unstable 用户更新到最新 nixos-unstable channel (包含 kernel updates for 2026-05-23 (#523326) 的版本) - 请 NixOS 25.11 用户更新到最新 nixos-25.11 channel…
🤣8😇4😱2
Signed dram🎀
Nix CN 文化衫概念征集公告 为迎接下一次Nix CN社区聚会,及长线周边贩售工作,NixCN Conf会务组(以下简称我们)决定开启文化衫概念征集和贩售工作。任何感兴趣的伙伴可以通过Telegram联系 @Cryolitia 或邮件联系 [email protected] 提交自己的文化衫设计。我们将在初步筛选后发起社区投票,并下单制作高人气的文化衫在社区销售或在各类活动中作为纪念品发放。 参考其他社区经验后,我们决定选取 T社定制 (https://www.tshe.com/) 作为文化衫供货商,请参赛选手自行在其官网了解可使用的底衫及印花工艺,在提交参赛作品时应包含底衫颜色,印花图案文件,概念预览图,可包含一段对设计的文字描述。 最终胜出的作品及其设计师的名字将会在我们的社区页面永久展示,并在下一次聚会时颁发奖项,高人气作品有机会在未来不断返场重贩售。 征集截止时间为2026年5月24日。
🔥7
Signed Eero Tang
[25.11, unstable] Linux 内核 __ptrace_may_access 权限漏洞可能导致越权访问高权限隐私数据 Linux 内核 __ptrace_may_access 在进程退出时的权限检查漏洞 [2] [3],使得普通用户可以在高权限进程退出时有机会读取该进程的敏感信息和高权限的任意打开文件,影响包括但不限于进程隐秘数据、SSH 私钥、/etc/shadow 等泄漏。 目前 Linus Torvalds 的分支已包含修复 [1],并已回合入 Linux 7.0.8+, 6.18.31+, 6.12.89+, 6.6.139+ 等版本。Unstable 和 25.11 均已更新,建议用户尽快升级。 - unstable kernel updates for 2026-05-15 (#520443) - 25.11 [Backport release-25.11] kernel updates for …
😱10
Signed dram🎀
[25.11, unstable] Nginx ngx_http_rewrite_module 远程代码执行漏洞 ngx_http_rewrite_modul 存在一个已存在约 18 年的内存损坏漏洞,攻击者可通过构造特定请求触发堆溢出,在部分场景下可能实现远程代码执行(RCE)。漏洞影响范围较广,几乎所有通用发行版默认构建的 Nginx 均会包含该模块。 受影响版本: * Nginx 0.6.27 ~ 1.30.0 建议用户尽快升级至以下已修复版本: * 1.30.1 * 1.31.0 目前 NixOS unstable 和 25.11 均已已合入相关更新,建议尽快更新: - unstable:https://github.com/NixOS/nixpkgs/pull/519893 - 25.11: https://github.com/NixOS/nixpkgs/pull/520076 对于暂时无法切换到已修复…
😱10❤1
Signed Eero Tang
Showing the 12 most recent of 20 posts we hold for @nixos_zhcn_news. 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.
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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“NixOS CN 新闻” (@nixos_zhcn_news), 313 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/nixos_zhcn_news.
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.