Telegram RegisterThe public register of Telegram
Telegram profile photo for linux.do

Channel

linux.do

@linuxdoit

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

23,749subscribers

+962 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-1002329614234
TypeChannel
Username@linuxdoit
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 October 2026
Measurements held46
Confirmed unchanged1 time, most recently 25 October 2026
On Telegramt.me/linuxdoit

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 10 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 why it has no browse page of its own yet.

Growth

22,78723,75223,269.56 August 2026 — 22,787 subscribers6 August 2026 — 22,809 subscribers7 August 2026 — 22,824 subscribers8 August 2026 — 22,830 subscribers10 August 2026 — 22,847 subscribers12 August 2026 — 22,868 subscribers12 August 2026 — 22,875 subscribers14 August 2026 — 22,893 subscribers15 August 2026 — 22,902 subscribers17 August 2026 — 22,921 subscribers18 August 2026 — 22,932 subscribers19 August 2026 — 22,952 subscribers20 August 2026 — 22,962 subscribers21 August 2026 — 22,977 subscribers23 August 2026 — 22,988 subscribers24 August 2026 — 22,995 subscribers25 August 2026 — 23,008 subscribers26 August 2026 — 23,014 subscribers27 August 2026 — 23,018 subscribers28 August 2026 — 23,025 subscribers29 August 2026 — 23,041 subscribers1 September 2026 — 23,044 subscribers2 September 2026 — 23,054 subscribers3 September 2026 — 23,075 subscribers5 September 2026 — 23,101 subscribers8 September 2026 — 23,157 subscribers11 September 2026 — 23,196 subscribers12 September 2026 — 23,224 subscribers14 September 2026 — 23,237 subscribers16 September 2026 — 23,263 subscribers18 September 2026 — 23,314 subscribers1 October 2026 — 23,511 subscribers6 October 2026 — 23,554 subscribers11 October 2026 — 23,593 subscribers14 October 2026 — 23,622 subscribers15 October 2026 — 23,634 subscribers16 October 2026 — 23,642 subscribers17 October 2026 — 23,654 subscribers18 October 2026 — 23,676 subscribers19 October 2026 — 23,684 subscribers20 October 2026 — 23,714 subscribers21 October 2026 — 23,727 subscribers22 October 2026 — 23,735 subscribers23 October 2026 — 23,743 subscribers24 October 2026 — 23,752 subscribers25 October 2026 — 23,749 subscribers23,7496 August 202625 October 2026
46 measurements spanning 80 days, net +962. 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 22,642–23,897 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
25 Oct 2026, 15:5623,749-3
24 Oct 2026, 14:3723,752+9
23 Oct 2026, 11:1523,743+8
22 Oct 2026, 12:3623,735+8
21 Oct 2026, 08:4523,727+13
20 Oct 2026, 04:3623,714+30
19 Oct 2026, 03:2123,684+8
18 Oct 2026, 02:4623,676+22
17 Oct 2026, 04:2523,654+12
16 Oct 2026, 04:1623,642+8
15 Oct 2026, 05:3923,634+12
14 Oct 2026, 01:2823,622+29
11 Oct 2026, 04:5923,593+39
6 Oct 2026, 22:3923,554+43
1 Oct 2026, 22:5623,511+197
18 Sept 2026, 15:1823,314+51
16 Sept 2026, 09:1823,263+26
14 Sept 2026, 16:1523,237+13
12 Sept 2026, 23:4023,224+28
11 Sept 2026, 02:1623,196first reading

Engagement

1,315 posts held, back to 6 August 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 101 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.399%
avg views ÷ 23,749 subscribers
Avg views / post
94.9
530 posts measured
Reaction rate
0.865%
reactions ÷ views · ER floor
Posts in window
530
of 1,315 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. It is computed over the 116 of 530 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 October 2026
Posts held1,315 (6 August 2026 – 24 October 2026)
Views total50,280
Reactions total128
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Oct 2026, 10:21 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

Video runtime
1m 43s
Average length
52s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

141 reactions across 116 posts, in 10 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9466.7%
❤2920.6%
👎53.55%
😨42.84%
😢32.13%
💩21.42%
😁10.709%
😱10.709%
🤣10.709%
🤬10.709%

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

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 15 August 2026 to 24 October 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

24 Oct 2026, 10:19 UTC5 viewsread 24 October 2026

Gemini3.8flashhigh删库跑路 如题,题主在ubuntu 22.04中挂载了windows的三个盘。 跑东西的时候gemini 3.8 flash执行rm -rf ./* ,后面的路径误用反引号,直接把windows的CD盘2T,一个sata小盘1T和一个14T机械删完了。还把ubuntu本身的文件删了一部分,主目录基本删光了。 损失了近10万篇顶刊顶会论文,600篇自己精心手写的论文笔记和llmwiki,几十个项目代码和资料,无数PPT素材和我硕士开题工作资料,虽然都在github上有,但依旧丢失了不少大文件。 现在很自闭,正在恢复中。还是个人生产力电脑,沉淀的工作流和skills毁于一旦,系统还得重装。 在此特意提醒佬友们,注意每半个月导出磁盘镜像冷备份,备份盘挂载为只读。若不幸发生了上述事情,先断电,再写镜像抢救。不要在被误删的位置新写入任何文件。 😭 17 个帖子 - 15 位参与者 阅读完整…

24 Oct 2026, 10:19 UTC5 viewsread 24 October 2026

【Hyxapi公益站】关于绑定邮箱发送验证码失败 如果各位使用我们公益站的佬友在绑定邮箱的时候出现发送验证码失败的问题,可以去提交一下工单,说明无法绑定邮箱,并且将你的邮箱贴出来,没有问题的话会自动绑定,另外我们的邮箱白名单列表为gmail,163,qq,icloud 41 个帖子 - 31 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: 1in)

24 Oct 2026, 10:19 UTC5 viewsread 24 October 2026
Photo

【富可敌国】嘿嘿我又回来了,来点0.95倍率的ccmax吧 哟西,打赢复活赛了,开始进入盈利状态了,自己也卖了点钩子接了点小业务回血。 这次就不整那个乱七八糟的小作文了直接开始整活吧。 喜迎一下1024程序员节+1025站点满月,鼓捣点赔钱货活动 :tieba_025: 活动有效期至本月31号,如果各位佬们用的开心大概率会考虑继续延期。1.余额充值赠送10%返利,用邀请码注册可获得双方5%返利,可叠加至其他活动一起使用。2.Claude Max分组下调至1.1倍率,98%缓存率,1小时缓存有效期,结合充值返利等优惠实际可达到0.95倍率。3.每天都开抽奖,虽然抽奖系统有点弱智,但是发了总比没有强,算是个凑数活动吧4.我最爱的送鸡蛋环节新注册用户发UID可领10元站内余额,可体验任意模型和功能。 叠楼,每50楼抽1位送100元站内余额。 传送门 有其他关于开票/退款/售后类型的疑问可以私信我处理,本帖就不做一一解答了…

24 Oct 2026, 10:19 UTC2 viewsread 24 October 2026

K3.1 初测: 拉完了[完结撒花:更新astra opus5.5 argon ds对比] via LINUX DO - 热门话题 (author: EVELance)

24 Oct 2026, 10:19 UTC2 viewsread 24 October 2026

这次 PHP 漏洞 (109618/109619) 事件的一些复盘和反思 via LINUX DO - 热门话题 (author: 青)

24 Oct 2026, 10:19 UTC2 viewsread 24 October 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7387292324

24 Oct 2026, 10:19 UTC2 viewsread 24 October 2026
Photo

谁说 Astra 不行的!我用 Astra 把 GitHub 变成了可探索的星球游戏! 之前比较长一段时间都在钻研如何使用 AI 开发游戏,每天都在提交代码,然后我想到是否可以把 GitHub 做成一款可以观看,可以探索星球游戏? 我通过 Three.js 生成星球,然后根据用户的 GitHub 数据,生成星球上的生态,比如不同的项目形成不同的岛屿🏝️,不同的开发语言生成不同的树木🌲,你的私有项目会变成深不见底的海洋🌊,然后再点缀一些建筑和生物,让整颗星球🌍️变得生机盎然。 这是我的星球,你也可以直接通过 Amery2010 的编程星球进行访问。 快来认领您的专属星球吧!1024.u14.app Programming Planet · Grow a world from code Explore low-poly planets made from GitHub projects and contributions…

24 Oct 2026, 10:08 UTC12 views1 reactionsread 24 October 2026

最新话题 - 2026年10月24日18:00摘要 (近3小时) 综合摘要生成失败,以下是各批次内容: 第 1 批处理失败: HTTP 404: Not Found --- 第 2 批处理失败: HTTP 404: Not Found --- 第 3 批处理失败: HTTP 404: Not Found --- 第 4 批处理失败: HTTP 404: Not Found --- 第 5 批处理失败: HTTP 404: Not Found via LINUX DO 每日摘要 - 最新话题 (author: AI bot)

👍1

24 Oct 2026, 07:24 UTC103 viewsread 24 October 2026

【一鸣公益站】模型上新:DeepSeek 1017 正式接入! 本帖使用社区公益推广,符合推广要求。我申明并遵循社区要求的以下内容: ● 我的项目是免费使用的,无收费(变相收费、赞助)部分: 是 ● 我的帖子已经打上 公益推广 标签: 是 ● 我的项目属于个人项目,与公司或商业机构无关: 是 ● 我的项目不存在QQ、TG等群组引流: 是 ● 我的项目不存在非运营必要的网站引流: 是 ● 我的项目不存在为他人推广、AFF: 是 ● 我的项目无关联的商业项目: 是 ● 我的站点存在登录,并已接入 LINUX DO Connect: 是 ● 我帖子内的项目介绍,AI生成、润色内容部分已截图发出: 是 ● 以上选择我承诺是永久有效的,接受社区和佬友监督: 是 以下是正文: 感谢大家一路以来的支持与陪伴!为了带来更流畅、更强劲的模型调用体验,平台现已完成底层接口升级,正式上线 deepseek-v4.1-flash-1017 版本。…

24 Oct 2026, 07:24 UTC119 views0 reactionsread 24 October 2026
Photo

随机出没!TRAE Friends桂林 随机出没! 位置:TRAE Friends @ 桂林 如果能在现场抓到nhh或淇淇,奖励一个淇淇的钥匙扣哦 :lark_186: 13 个帖子 - 8 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: 欧阳淇淇)

24 Oct 2026, 07:24 UTC84 viewsread 24 October 2026
Photo

Kimi 3.1 真的起来了 Kimi 3.1 pro ,AA 榜第四,超越 Gpt-6-Astra(Max),不知道佬友们实际使用下来怎么样? 55 个帖子 - 40 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: AkaChou)

24 Oct 2026, 07:24 UTC91 viewsread 24 October 2026

和我一样周六还在上班的佬们多吗? 打工人太难了,找个双休的工作都这么困难,北京应该已经算劳动法落实的不错的地区了,怎么双休也这么难找? 65 个帖子 - 48 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: 三季人)

Showing the 12 most recent of 1,315 posts we hold for @linuxdoit. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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.

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

“linux.do” (@linuxdoit), 23,749 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/linuxdoit.

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.