Telegram RegisterThe public register of Telegram

Channel

Arch Linux Chinese Messages

@archlinuxcn

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

11,155subscribers

+42 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001171123781
TypeChannel
Username@archlinuxcn
DescriptionArch Linux 中文相关信息 跟进 Arch Linux 日常踩坑预警,翻译官方新闻, testing 测试预警等。另有 @archlinuxcn_updates 提供滚动打包记录。 频道内容来自 Arch Linux 中文社区群组 @archlinuxcn_group https://fars.ee/~readme.html 杜洛夫在所有订阅数较多的频道下方都添加了广告,其收益并不分配给频道主,频道主也无法控制其内容。如果在本频道下方看到广告,均与 Arch CN 社区无关,请勿点击或相信其内容
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/archlinuxcn

Growth

11,11211,15511,133.56 August 2026 — 11,113 subscribers6 August 2026 — 11,112 subscribers7 August 2026 — 11,119 subscribers8 August 2026 — 11,128 subscribers9 August 2026 — 11,131 subscribers10 August 2026 — 11,144 subscribers11 August 2026 — 11,147 subscribers12 August 2026 — 11,155 subscribers6 August 202612 August 2026
8 measurements spanning 6 days, net +42. 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 11,106–11,161 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 10:1511,155+8
11 Aug 2026, 07:2411,147+3
10 Aug 2026, 06:1011,144+13
9 Aug 2026, 08:0711,131+3
8 Aug 2026, 11:3511,128+9
7 Aug 2026, 09:3011,119+7
6 Aug 2026, 11:2111,112-1
6 Aug 2026, 06:4811,113first reading

Engagement

21 posts held, back to 11 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
76.4%
avg views ÷ 11,155 subscribers
Avg views / post
8,520
5 posts measured
Reaction rate
1.43%
reactions ÷ views · ER floor
Posts in window
5
of 21 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held21 (11 December 20257 August 2026)
Views total42,600
Reactions total611
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 04:19 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
3
Links
211

Lifetime counters from Telegram’s own channel header, read 13 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.

Reaction mix

3,074 reactions across 20 posts, in 33 distinct kinds. The most used accounts for 16.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😨51516.8%
🤬37712.3%
😱34911.4%
👍30810.0%
🎉2468.00%
😇2096.80%
🤯1615.24%
👌1494.85%
💩1494.85%
1234.00%
🤣1013.29%
👾963.12%
🙏371.20%
😁341.11%
🥰331.07%
🔥311.01%
👏250.813%
😢250.813%
😴240.781%
😭220.716%
13 further kinds601.95%

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 21 of the 21 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 3,147reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 11 December 2025 to 7 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.

Recent posts

7 Aug 2026, 02:32 UTC≈6,660 views84 reactionsread 13 August 2026

更新 openssh 后 sshd 需要手动重启 由于打包变化叠加上游变化,openssh 更新到 10.4p1-3 后有可能不会自动重启、并且无法接受新的连接。请最近更新服务器时记得手动重启 sshd 服务。

👌75😴7🤔2

Signed 依云

30 Jul 2026, 18:36 UTC≈12,200 views326 reactionsread 13 August 2026
Photo

AUR 正遭遇新一轮投毒攻击。已知的投毒方式是在包中添加一个可执行文件(如配图所示),并在 PKGBUILD 中以 root 权限执行。 目前还没有官方通报,但可能有上百软件包被投毒。看起来官方正在清理被投毒的包,并暂时禁止了接管孤儿包(package adoption)。

😇142🤬95😱47🤯14😁9😨9💩8😢2

Signed (ɔɥʌɔ) oɐɥınɔ

21 Jul 2026, 15:58 UTC≈7,990 views55 reactionsread 13 August 2026

virtualbox-ext-vnc >= 7.2.12-2 升级需要手动干预 之前我们安装该软件包内容的方式会导致 pacman 没有跟踪部分文件(即在安装脚本中使用 VBoxManage extpack install ... 进行安装)。为了解决系统升级过程中遇到的问题,你可以选择以下任意一种方法进行处理: ■ 在升级系统前先卸载 virtualbox-ext-vnc,升级完成后重新安装它。 ■ 在升级系统前,以 root 权限运行 VBoxManage extpack uninstall 'VNC' 命令。 ■ 指示 pacman 本次升级覆盖已有文件: pacman -Syu --overwrite '/usr/lib/virtualbox/ExtensionPacks/VNC/*' https://www.archlinuxcn.org/virtualbox-ext-vnc-7212-2-requires-man

💩23👌12😱10🤨53👍2

Signed farseerfc 😂

19 Jul 2026, 05:04 UTC≈7,640 views74 reactionsread 13 August 2026

linux 7.1.4.arch1-1 已经包含此补丁。

👍57🥰10💩7

Signed 依云

18 Jul 2026, 15:48 UTC≈8,110 views72 reactionsread 13 August 2026

使用 amdgpu 与 linux 包的用户可能在近期遇到 mpv 卡死的情况,具体来说是当 mpv 配置了 vo=gpu-next 时,在使用 mpv 播放视频后一定概率会很快出现“窗口无响应”,并且 mpv 进程陷入 D 状态,运行 dmesg | grep --after-context=4 "#PF" 能看到类似以下内容的输出: #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP NOPTI CPU: 4 UID: 0 PID: 100 Comm: kcompactd0 Not tainted 7.1.1-2-cachyos #1 PREEMPT(full) RIP: 0010:amdgpu_hmm_invalidate_gfx+0x22/0xb0 [amdgpu] 除此以外,浏览器也可能突然出现上面的情况。该问题已有报告。受影响的用户

😨48💩1311

Signed 依云

13 Jun 2026, 02:01 UTC≈11,700 views244 reactionsread 13 August 2026

正在进行中的 AUR 软件包投毒事件 目前,Arch 用户软件仓库(AUR)中出现了大量恶意的软件包被接管和更新的情况。 我们正在积极追踪现有的恶意提交,并努力阻止新的恶意提交被推送。在此期间,在更永久的解决方案出台之前,用户可能会在以下方面遇到问题: ■在 AUR 上创建新账户 ■推送软件包更新 ■接管或创建新软件包 我们继续建议所有 AUR 软件包的用户在更新时仔细审查所有的 PKGBUILD 和安装脚本变更,特别是在这段时期。如果您发现正在使用的软件包有可疑的提交,请通过 aur-general 邮件列表联系 Arch 团队并提供更多信息。 https://www.archlinuxcn.org/active-aur-malicious-packages-incident/

🤬159🤯42🙏31😁63😢2😱1

Signed farseerfc 😂

12 Jun 2026, 12:40 UTC≈10,200 views198 reactionsread 13 August 2026

涉事的 npm 包已经被清除,但相似的投毒仍在进行,现在使用的依赖包是 bun。

🤣101🤬60😇19😁123🐳2😭1

Signed 依云

12 Jun 2026, 04:57 UTC≈25,600 views420 reactionsread 13 August 2026

AUR 大量孤儿包被投毒 近日,有大量 AUR 孤儿包被多名新注册用户接管,并增加 npm 依赖、在安装时通过安装脚本(.install)或者 pacman hook 执行 # npm install atomic-lockfile 操作以运行恶意代码。该 atomic-lockfile 包亦是于近日上传至 npm registry。 一旦安装有问题的软件包,恶意代码将以 root 权限安装并运行,收集至少包括浏览器、Shell 命令历史记录、各种应用程序中的凭据等信息,并将其上传。恶意代码也会利用 ebpf 程序隐藏自身。建议受影响的用户重装系统并重置所有网络账户密码和各类密钥、凭据。 如果 pacman.log 表明未曾安装过 npm、或者在多天以前已经卸载 npm,则应当未受影响。 用户从 AUR 安装软件时请注意审阅构建脚本。另外及时卸载从官方仓库移出的、不再需要的依赖包,比如 libgdata。 另:[arc

😨338😱37💩2311🤯4😁4👍2🥰1

Signed 依云

5 Jun 2026, 00:28 UTC≈9,190 views243 reactionsread 13 August 2026

Arch Linux 2026 项目负责人选举结果 最近我们举办了项目负责人选举,经过在(内部)邮件列表上的热烈讨论环节和有两名候选人参选的投票环节之后, Levente “anthraxx” Polyák 再次获选为新一届项目负责人。 根据我们的选举规则,他再选的本届任期将持续两年。 Arch Linux 项目负责人的职责包括作出最终决策(当没法达成共识时),带领社区,保障执行行为守则,处理和SPI相关的财政事务,以及整体的项目任务管理。 恭喜 Levente ,感谢你站出来服务这个社区,并希望这一届任期也会是顺利的一届!🥳 https://www.archlinuxcn.org/arch-linux-2026-leader-election-results/

🎉197🥰22👏11👀82👍2😱1

Signed farseerfc 😂

25 May 2026, 06:00 UTC≈11,100 views87 reactionsread 13 August 2026

影响所有 `varnish` 用户的破坏性变更,它已更名为 `vinyl-cache` Varnish 项目已正式更名为 Vinyl Cache。紧随这一更名,我们发布了全新的 vinyl-cache 软件包。由于此次升级包含破坏性变更(Breaking Changes),建议用户在进行替换前,务必仔细研究这些变化及其带来的影响。目前,所有二进制文件和目录中的 “varnish” 字样均已全面变更为 “vinyl”。 用户至少需要执行以下操作: ■将 /etc/varnish 重命名为 /etc/vinyl-cache ■将 /var/lib/varnish 重命名为 /var/lib/vinyl-cache ■修正 /var/lib/varnish 目录内文件的所有权 ■用户名 varnish 变更为 vinyl ■用户组 varnish 变更为 vinyl ■用户名 varnishlog 变更为 vinyllog ■用户

💩58🤯23👌32😡1

Signed farseerfc 😂

21 May 2026, 13:04 UTC≈11,400 views215 reactionsread 13 August 2026

20260521 近期 Linux 内核本地提权漏洞汇总 近期 Linux 内核发现了多个本地提权漏洞(LPE, Local privilege escalation),以下是它们在 Arch Linux 官方源中提供的内核的修复版本和受影响的内核模块。请尽快更新到已修复版本的内核,或屏蔽受影响的内核模块以避免漏洞被恶意利用。更新到已修复版本内核后不再需要屏蔽内核模块的缓解措施。 1. copy fail (CVE-2026-31431) https://copy.fail/ Arch Linux 已修复版本: linux 6.19.12 以上(含7.0 以上)或 linux-lts 6.18.22 以上版本 缓解措施:屏蔽 algif_aead 内核模块 echo 'install algif_aead /bin/false' | sudo tee -a /etc/modprobe.d/cve-copyfail.conf

👾96🤯38👍32😭2011😱11🤓5🍾1

Signed farseerfc 😂

30 Apr 2026, 04:10 UTC≈13,400 views288 reactionsread 13 August 2026

内核提权漏洞公告 请尽快将内核更新到 linux 6.19.12+ 或 linux-lts 6.18.22+ 版本(并重启),以修复 CVE-2026-31431 漏洞。

😱225🔥31😨10👍9💩6🤔32😁2

Signed oldherl

Showing the 12 most recent of 21 posts we hold for @archlinuxcn. 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 — 32,853 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

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

风向旗参考快讯
@xhqcankao · 157,320
Telegram ranks this channel #37 of 45 here — alongside 44 others — read 12 August 2026
竹新社
@tnews365 · 156,398
Telegram ranks this channel #59 of 59 here — alongside 58 others — read 12 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“Arch Linux Chinese Messages” (@archlinuxcn), 11,155 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/archlinuxcn.

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.