Telegram RegisterThe public register of Telegram
Telegram profile photo for Arch Linux Chinese Messages

Channel

Arch Linux Chinese Messages

@archlinuxcn

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

11,265subscribers

+152 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 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held58
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/archlinuxcn

Topic

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Growth

11,11211,26511,188.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 subscribers13 August 2026 — 11,154 subscribers14 August 2026 — 11,158 subscribers16 August 2026 — 11,166 subscribers17 August 2026 — 11,162 subscribers18 August 2026 — 11,167 subscribers20 August 2026 — 11,169 subscribers23 August 2026 — 11,164 subscribers25 August 2026 — 11,163 subscribers26 August 2026 — 11,165 subscribers27 August 2026 — 11,172 subscribers28 August 2026 — 11,178 subscribers29 August 2026 — 11,176 subscribers31 August 2026 — 11,179 subscribers1 September 2026 — 11,176 subscribers2 September 2026 — 11,178 subscribers3 September 2026 — 11,179 subscribers5 September 2026 — 11,176 subscribers8 September 2026 — 11,168 subscribers11 September 2026 — 11,167 subscribers13 September 2026 — 11,165 subscribers15 September 2026 — 11,172 subscribers17 September 2026 — 11,175 subscribers4 October 2026 — 11,189 subscribers9 October 2026 — 11,185 subscribers13 October 2026 — 11,195 subscribers14 October 2026 — 11,202 subscribers15 October 2026 — 11,205 subscribers16 October 2026 — 11,206 subscribers17 October 2026 — 11,211 subscribers18 October 2026 — 11,214 subscribers19 October 2026 — 11,220 subscribers21 October 2026 — 11,223 subscribers22 October 2026 — 11,236 subscribers23 October 2026 — 11,241 subscribers24 October 2026 — 11,233 subscribers25 October 2026 — 11,230 subscribers26 October 2026 — 11,233 subscribers27 October 2026 — 11,235 subscribers28 October 2026 — 11,239 subscribers29 October 2026 — 11,244 subscribers30 October 2026 — 11,246 subscribers31 October 2026 — 11,245 subscribers1 November 2026 — 11,248 subscribers2 November 2026 — 11,256 subscribers3 November 2026 — 11,254 subscribers4 November 2026 — 11,257 subscribers5 November 2026 — 11,254 subscribers6 November 2026 — 11,258 subscribers7 November 2026 — 11,261 subscribers10 November 2026 — 11,265 subscribers6 August 202610 November 2026
58 measurements spanning 96 days, net +152. 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,089–11,288 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
10 Nov 2026, 00:5711,265+4
7 Nov 2026, 09:1411,261+3
6 Nov 2026, 12:0611,258+4
5 Nov 2026, 11:3611,254-3
4 Nov 2026, 14:5611,257+3
3 Nov 2026, 11:2111,254-2
2 Nov 2026, 10:1011,256+8
1 Nov 2026, 09:2711,248+3
31 Oct 2026, 07:4611,245-1
30 Oct 2026, 10:5511,246+2
29 Oct 2026, 11:4111,244+5
28 Oct 2026, 13:2511,239+4
27 Oct 2026, 12:0511,235+2
26 Oct 2026, 12:2911,233+3
25 Oct 2026, 09:5811,230-3
24 Oct 2026, 13:1711,233-8
23 Oct 2026, 10:0911,241+5
22 Oct 2026, 10:4411,236+13
21 Oct 2026, 04:3711,223+3
19 Oct 2026, 23:4811,220first reading

Engagement

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

ERR · 30 days
41.1%
avg views ÷ 11,265 subscribers
Avg views / post
4,630
5 posts measured
Reaction rate
1.60%
reactions ÷ views · ER floor
Posts in window
5
of 33 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 10 November 2026
Posts held33 (11 December 2025 – 10 November 2026)
Views total23,140
Reactions total371
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 20:59 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
219

Lifetime counters from Telegram’s own channel header, read 10 November 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,920 reactions across 32 posts, in 35 distinct kinds. The most used accounts for 13.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😨51813.2%
😱50412.9%
👍49712.7%
🤬40910.4%
😇2757.02%
🎉2476.30%
❤2466.28%
💩2145.46%
🤯1975.03%
👌1904.85%
🤣1022.60%
👾972.47%
👏731.86%
🙏441.12%
🥰370.944%
😁350.893%
🫡350.893%
🔥320.816%
😢250.638%
😴240.612%
15 further kinds1193.04%

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

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

Telegram’s own ‘edited’ marker: 3 of 5 posts held from the last 30 days (60.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 09:45 UTC≈1,770 views60 reactionsread 10 November 2026

openssl 4 已经进入软件仓库 本次大版本变更涉及 soname 变化(libssl.so.3 → libssl.so.4, libcrypto.so.3 → libcrypto.so.4),所有依赖它的软件包需要重新编译,包括 AUR helper。请勿部分更新系统。如果系统更新后遇到不能找到 libssl.so.3 或 libcrypto.so.3 之类的报错可以尝试先安装 openssl-3 包过渡,然后手动更新所有来自 AUR 的包。 [archlinuxcn] 中的包也正在重新编译,如果遇到需要重新打包的包请告知我们。 也可以考虑在下次更新系统时顺便装上 openssl-3 包(pacman -Syu openssl-3)以防御性地应对尚未重新构建的软件。

🫡35👍9👀6👌6💊2🤯2

Signed 依云

21 Oct 2026, 15:50 UTC≈5,670 views93 reactionsread 10 November 2026

更新到 ca-certificates-mozilla ≥ 3.131.1-1 以避免中间人攻击 在2026年10月20日,已表明eMudhra中间CA提供的多个证书已遭破解。 受影响的证书已经在 ca-certificates-mozilla ≥ 3.131.1-1 中删除或吊销。 若不更新证书包,系统将面临被中间人(MitM)攻击的风险。因此,我们强烈建议所有人立即升级系统。 https://www.archlinuxcn.org/update-to-ca-certificates-mozilla-31311-1-to-prevent-man-in-the-middle-attacks/

👍50😇22🤯15❤3👌3

Signed farseerfc 😂

21 Oct 2026, 15:41 UTC≈5,000 views46 reactionsread 10 November 2026

升级到 php ≥ 8.5.12 和/或 php-legacy ≥ 8.3.36 以避免远程代码执行漏洞 PHP在版本号 8.5.12 和 8.3.36 之前的版本存在 CVE-2026-109618 和 CVE-2026-109619 漏洞,可导致远程代码执行。 我们强烈建议任何用之前版本的PHP公开暴露PHP程序的系统都尽快升级到最新版本(php ≥ 8.5.12 和 php-legacy ≥ 8.3.36)。 https://www.archlinuxcn.org/update-to-php-8512-andor-php-legacy-8336-to-prevent-remote-code-execution/

😇38👍6❤2

Signed farseerfc 😂

21 Oct 2026, 13:57 UTC≈5,090 views65 reactionsread 10 November 2026

Arch Linux 已更新 php 8.5.12-1。

👍62❤3

Signed 依云

21 Oct 2026, 04:34 UTC≈5,610 views107 reactionsread 10 November 2026

eMudhra 中间证书泄露,请尽快更新/处置。 PHP 被发现严重远程代码执行漏洞,请准备好今晚更新。

😱78💩14🙏7👻4😡3😭1

Signed 依云

22 Sept 2026, 12:14 UTC≈9,410 views47 reactionsread 10 November 2026

mkinitcpio >= 42 更新在基于TPM2解锁LUKS的设备上可能需要手动干预 从包版本 42-1 起,mkinitcpio 的 systemd 挂钩现在也包括了 systemd-pcrosseparator.service 服务(按照 systemd v261 的计划)。 这会影响 PCR 值 0-7、9 和 12-14 的测量。如果您配置了 systemd 钩子,并且使用的 LUKS 分区解锁依赖于这些值,您需要重新 enroll 所使用的 TPM2。 如需指导,当使用固定值时,请参考 systemd-cryptenroll(1),或 ArchWiki 上的 systemd-cryptenroll 文章。当依赖自定义策略并禁用了 systemd-pcrlock-make-policy.service 时,请参考 systemd-pcrlock(8)。 https://www.archlinuxcn.org/mk…

💩39👍6❤2

Signed farseerfc 😂

15 Sept 2026, 15:30 UTC≈9,900 views54 reactionsread 10 November 2026

linux-firmware-amdgpu 20260910-2 已修复前一个问题。

👍37👏8❤5🥰3👎1

Signed 依云

13 Sept 2026, 07:32 UTC≈9,760 views49 reactionsread 10 November 2026

ddcutil 3.0.1-1 已修复后一个问题。

❤31👍10👏8

Signed 依云

13 Sept 2026, 01:24 UTC≈10,500 views119 reactionsread 10 November 2026

AMD 显卡用户谨慎升级 linux-firmware-amdgpu 20260910-1。有多位用户报告该版本固件导致了启动问题。 AMD 显卡的 KDE 用户谨慎升级 ddcutil 3.0.0-1。有多位用户报告该版本在 KDE 上会导致显卡出现问题。 https://gitlab.archlinux.org/archlinux/packaging/packages/linux-firmware/-/work_items/52 https://github.com/rockowitz/ddcutil/issues/629

😱72🤯18🤬12💩7❤4👀3👌1👍1

Signed 依云

5 Sept 2026, 03:34 UTC≈9,590 views39 reactionsread 10 November 2026

www.archlinuxcn.org 也已于夜里恢复服务。此次维护所有中断服务均已恢复。

❤29👏10

Signed 依云

4 Sept 2026, 13:38 UTC≈8,850 views39 reactionsread 10 November 2026

wiki.archlinuxcn.org 、 forum.archlinuxcn.org 和邮件服务已经恢复。

👏22❤12👍5

Signed 依云

4 Sept 2026, 09:00 UTC≈8,270 views51 reactionsread 10 November 2026

www.archlinuxcn.org 、 wiki.archlinuxcn.org 、 forum.archlinuxcn.org 及邮件服务正在维护。

❤28👌12🤔6👀4👍1

Signed 依云

Showing the 12 most recent of 33 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.

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

Named by 2 registered channels — 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.

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.

QAuxiliary
@QAuxiliary · 44,497
Telegram ranks this channel #18 of 58 here — alongside 57 others — read 12 September 2026
QAuxiliary CI Builds
@QAuxiliary_CI · 19,690
Telegram ranks this channel #24 of 56 here — alongside 55 others — read 1 October 2026
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 22,486
Telegram ranks this channel #27 of 54 here — alongside 53 others — read 23 September 2026
每日无数猫
@miaowu · 19,930
Telegram ranks this channel #30 of 55 here — alongside 54 others — read 29 September 2026
赛博忏悔室
@cyber_confessional · 40,952
Telegram ranks this channel #34 of 35 here — alongside 34 others — read 30 August 2026
Project X Channel
@projectXtls · 30,507
Telegram ranks this channel #37 of 58 here — alongside 57 others — read 8 September 2026
风向旗参考快讯
@xhqcankao · 168,108
Telegram ranks this channel #37 of 45 here — alongside 44 others — read 12 August 2026
煎蛋无聊图
@jandan_pic · 25,561
Telegram ranks this channel #43 of 51 here — alongside 50 others — read 14 September 2026
每日沙雕墙
@woshadiao · 114,495
Telegram ranks this channel #47 of 52 here — alongside 51 others — read 14 August 2026
蓝点网订阅频道
@landiansub · 47,142
Telegram ranks this channel #48 of 58 here — alongside 57 others — read 28 August 2026
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,407
Telegram ranks this channel #51 of 55 here — alongside 54 others — read 10 September 2026
Solidot
@solidot · 48,812
Telegram ranks this channel #51 of 59 here — alongside 58 others — read 28 August 2026
Iyouport
@iyouport · 27,612
Telegram ranks this channel #53 of 55 here — alongside 54 others — read 10 September 2026
每日消费电子观察
@CE_Observe · 77,552
Telegram ranks this channel #54 of 62 here — alongside 61 others — read 19 August 2026
少数派sspai
@sspai · 39,123
Telegram ranks this channel #55 of 58 here — alongside 57 others — read 31 August 2026
2019-nCoV疫情实时播报🅥
@nCoV2019 · 32,452
Telegram ranks this channel #57 of 59 here — alongside 58 others — read 4 September 2026
LoopDNS资讯播报
@DNSPODT · 73,241
Telegram ranks this channel #57 of 59 here — alongside 58 others — read 20 August 2026
竹新社
@tnews365 · 167,192
Telegram ranks this channel #59 of 59 here — alongside 58 others — read 12 August 2026

This channel appears in 18 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Arch Linux Chinese Messages” (@archlinuxcn), 11,265 subscribers as measured 10 November 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.