Channel
@archlinux
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
933subscribers
+4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001301055143 |
|---|---|
| Type | Channel |
| Username | @archlinux |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/archlinux |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:55 | 933 | +4 |
| 6 Aug 2026, 14:03 | 929 | no change |
| 6 Aug 2026, 09:21 | 929 | first reading |
20 posts held, back to 16 January 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 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 21 July 2026 |
|---|---|
| Posts held | 20 (16 January 2025 – 21 July 2026) |
| Views total | 522 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 14:03 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.
254 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 45.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 115 | 45.3% | |
| 😱 | 72 | 28.3% | |
| 🤔 | 28 | 11.0% | |
| 🔥 | 23 | 9.06% | |
| 👏 | 13 | 5.12% | |
| 😁 | 3 | 1.18% |
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 254reactions 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 16 January 2025 to 21 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.
📨 virtualbox-ext-vnc >= 7.2.12-2 requires manual intervention Previously, we installed its contents in a way that made pacman not aware of the files (using VBoxManage extpack install ... from an install script). To mitigate issues during upgrade, you can use one of the following methods: Uninstall... 🗞 Read more
👍6🤔2
📨 Active AUR malicious packages incident We are currently experiencing a high volume of malicious package adoptions and updates in the Arch User Repository. We are actively working to track down existing malicious commits and attempting to prevent additional malicious commits from... 🗞 Read more
😱15🔥8👏4🤔4👍2
📨 Arch Linux 2026 Leader Election Results Recently we held our leader elections and after a lively discussion period on the (internal) mailing lists and voting phase with two candidates Levente "anthraxx" Polyák was re-elected as Arch Linux Project Lead. As per our election rules... 🗞 Read more
👍10👏4😱1
📨 Breaking changes for all users of `varnish`, which is renamed to `vinyl-cache` The Varnish project has renamed itself to Vinyl Cache. We followed this rename with a new vinyl-cache package. This upgrade results in breaking changes and users are advised to study these changes and how it affects them before following... 🗞 Read more
🤔11
📨 kea >= 1:3.0.3-6 update requires manual intervention The kea package has moved all services to run as a dedicated kea user (instead of root) for improved security. This change requires permission updates to the runtime files created by the kea services. Users upgrading from an existing kea... 🗞 Read more
🤔7👍2😱1
📨 iptables now defaults to the nft backend The old iptables-nft package name is replaced by iptables, and the legacy backend is available as iptables-legacy. When switching packages (among iptables-nft, iptables, iptables-legacy), check for .pacsave files in /etc/iptables/ and... 🗞 Read more
👍7🤔3😁1
📨 NVIDIA 590 driver drops Pascal and lower support; main packages switch to Open Kernel Modules With the update to driver version 590, the NVIDIA driver no longer supports Pascal (GTX 10xx) GPUs or older. We will replace the nvidia package with nvidia-open, nvidia-dkms with nvidia-open-dkms, and nvidia-lts with nvidia-lts-open.... 🗞 Read more
😱11👏2
📨 .NET packages may require manual intervention The following packages may require manual intervention due to the upgrade from 9.0 to 10.0: aspnet-runtime aspnet-targeting-pack dotnet-runtime dotnet-sdk dotnet-source-built-artifacts dotnet-targeting-pack pacman may display the following... 🗞 Read more
👍11😱4
📨 waydroid >= 1.5.4-3 update may require manual intervention The waydroid package prior to version 1.5.4-2 (including aur/waydroid) creates Python byte-code files (.pyc) at runtime which were untracked by pacman. This issue has been fixed in 1.5.4-3, where byte-compiling these files is now done... 🗞 Read more
👍12
📨 dovecot >= 2.4 requires manual intervention The dovecot 2.4 release branch has made breaking changes which result in it being incompatible with any <= 2.3 configuration file. Thus, the dovecot service will no longer be able to start until the configuration file was migrated,... 🗞 Read more
👍4😱3
📨 Recent service outages We want to provide an update on the recent service outages affecting our infrastructure. The Arch Linux Project is currently experiencing an ongoing denial of service attack that primarily impacts our main webpage, the Arch User Repository... 🗞 Read more
😱17👍3🔥3👏2
📨 zabbix >= 7.4.1-2 may require manual intervention Starting with 7.4.1-2, the following Zabbix system user accounts (previously shipped by their related packages) will no longer be used. Instead, all Zabbix components will now rely on a shared zabbix user account (as originally intended by... 🗞 Read more
👍4🔥2
Showing the 12 most recent of 20 posts we hold for @archlinux. 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 — 996,929 of 1,481,217entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“ArchLinux - News” (@archlinux), 933 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/archlinux.
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.