最新话题 - 2026年11月14日06:00摘要 (近3小时) 第 1 批处理失败: HTTP 404: Not Found via LINUX DO 每日摘要 - 最新话题 (author: AI bot)

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,893subscribers
+1,106 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 |
|---|---|
| Type | Channel |
| Username | @linuxdoit |
| Description | linux.do最新话题和热议话题 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Nov 2026, 14:51 | 23,893 | +34 |
| 10 Nov 2026, 08:07 | 23,859 | +11 |
| 8 Nov 2026, 20:56 | 23,848 | +26 |
| 7 Nov 2026, 14:21 | 23,822 | -1 |
| 6 Nov 2026, 15:57 | 23,823 | +11 |
| 5 Nov 2026, 18:07 | 23,812 | +10 |
| 4 Nov 2026, 21:16 | 23,802 | +7 |
| 3 Nov 2026, 20:11 | 23,795 | +5 |
| 2 Nov 2026, 18:47 | 23,790 | +7 |
| 1 Nov 2026, 21:29 | 23,783 | +8 |
| 31 Oct 2026, 19:18 | 23,775 | -1 |
| 30 Oct 2026, 18:31 | 23,776 | -6 |
| 29 Oct 2026, 16:49 | 23,782 | +11 |
| 28 Oct 2026, 15:19 | 23,771 | +4 |
| 27 Oct 2026, 11:58 | 23,767 | +1 |
| 26 Oct 2026, 13:26 | 23,766 | +17 |
| 25 Oct 2026, 15:56 | 23,749 | -3 |
| 24 Oct 2026, 14:37 | 23,752 | +9 |
| 23 Oct 2026, 11:15 | 23,743 | +8 |
| 22 Oct 2026, 12:36 | 23,735 | first reading |
Engagement
1,685 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 126 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.336%
- avg views ÷ 23,893 subscribers
- Avg views / post
- 80.2
- 481 posts measured
- Reaction rate
- 1.43%
- reactions ÷ views · ER floor
- Posts in window
- 481
- of 1,685 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 203 of 481 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 1,685 (6 August 2026 – 13 November 2026) |
| Views total | 38,570 |
| Reactions total | 230 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 23:55 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
- ≈133,000
- Videos
- ≈103
- Links
- ≈196,000
Lifetime counters from Telegram’s own channel header, read 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 2m 16s
- Average length
- 45s
Measured directly from 3 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
332 reactions across 276 posts, in 12 distinct kinds. The most used accounts for 84.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 281 | 84.6% | |
| ❤ | 32 | 9.64% | |
| 😨 | 4 | 1.20% | |
| 👎 | 3 | 0.904% | |
| 😢 | 3 | 0.904% | |
| 💩 | 2 | 0.602% | |
| 😡 | 2 | 0.602% | |
| 🔥 | 1 | 0.301% | |
| 😁 | 1 | 0.301% | |
| 😱 | 1 | 0.301% | |
| 🤣 | 1 | 0.301% | |
| 🤬 | 1 | 0.301% |
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 292 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 332 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 30 August 2026 to 13 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: 0 of 481 posts held from the last 30 days (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).
豆包工作反代 本帖使用社区开源推广,符合推广要求。我申明并遵循社区要求的以下内容: ● 我的帖子已经打上 开源推广 标签: 是 ● 我的开源项目完整开源,无未开源部分: 是 ● 我的开源项目已链接认可 LINUX DO 社区: 是 ● 我帖子内的项目介绍,AI生成、润色内容部分已截图发出: 是 ● 以上选择我承诺是永久有效的,接受社区和佬友监督: 是 *以下为项目介绍正文内容,AI生成、润色内容已使用截图方式发出。 仓库 245678000000/doubao-work-gateway GitHub - 245678000000/doubao-work-gateway: 豆包工作专用本机账号管家:多账号登录、自动签到、额度查询与 API Key 管理,macOS... 豆包工作专用本机账号管家:多账号登录、自动签到、额度查询与 API Key 管理,macOS 清爽面板。 最近看到豆包工作支持很多外部模型,想着自己…
黄仁勋因桃色新闻被迫辞职,我有个大胆的想法 你们说黄仁勋有没有机会回到中国,加入龙芯 66 个帖子 - 65 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: dshengyan)
新MacBook Pro终于到了 总算从Air换成Pro了! 发光Logo真好看😍 总算没有丑丑的刘海了,屏幕看着舒服太多了 新鲜感满满❤️果然电子产品才是最好的情绪价值啊 57 个帖子 - 33 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: Inkouzel)
最近准备炒一盘大菜,问下这里的佬厨子们,咋个才能提高火力和成功率 今年一直和媳妇儿再备菜,都备了快大半年了 媳妇一直想要一盘狮子座的大菜,所以把烧锅时间放到了这段时间 但是这段时间我这个厨子我呀有点累,加班儿太多 感觉油每次都不太够的样子 而且天天倒油 存货都感觉快见底了 有没有什么门道 可以去多打点油呢? 不然感觉菜上不了桌了 52 个帖子 - 43 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: syskey)
“让老板回来”:英伟达员工请愿要求黄仁勋回归 | 一篇呼吁董事会考虑员工对英伟达前首席执行官看法的内部帖文,引发了超过1600条评论 via LINUX DO - 热门话题 (author: 🐟)
最新话题 - 2026年11月14日03:00摘要 (近3小时) 综合摘要生成失败,以下是各批次内容: 第 1 批处理失败: HTTP 404: Not Found --- 第 2 批处理失败: HTTP 404: Not Found --- 第 3 批处理失败: HTTP 404: Not Found via LINUX DO 每日摘要 - 最新话题 (author: AI bot)
LLM科研写作模型怎么选? via LINUX DO - 热门话题 (author: goku123)
muse免费白嫖资源一条龙 直接在下方复制提示词,粘贴给muse: 请帮我系统开通并配置一套免费白嫖资源组合,目标是搭建低成本 AI 算力 + 云电脑 + 节点环境。全程只用免费计划,不绑卡、不升级、不付费。 ### 核心要求(必须严格遵守) 1. 只用免费计划,绝不绑卡、不升级、不购买任何付费选项。 2. 遇到需要登录、Google 授权、手机验证码、人脸识别、协议确认、密码输入时,**立即停下来**,把页面留给我接管,等我完成后再继续。 3. 不要读取、存储或泄露我的任何密码、验证码、支付信息。 4. 每完成一项资源,先实际验证是否可用(例如运行 nvidia-smi、跑一个小 Python 程序、生成一张测试图、输出节点链接),再进入下一项。 5. 全部完成后,给我一份清晰的总结报告:每项资源的状态、如何再次进入、当前免费限制、注意事项,以及我需要手动保存的关键信息。 ### 按优先级依次执行以下任务 **第一优先…
🔥老黄的段子,图片和视频接龙 以下为L站,油管等收集关于老黄的评论和段子,祝佬友开怀 欢迎佬友踊跃接龙 在叛国面前他选择了叛妻, 在通敌面前他选择了通奸, 在出卖面前他选择了出轨, 在成罪面前他选择了成龙, 在格局面前他选择了格调 老黄啊,你说你,几百块的事被你搞成了几百亿的事。 一切都是命中注定 老黄=越老越黄 黄乐=让老黄快乐 我是皮衣客,不是皮条客 黄总为了卖显卡亲自和客户睡觉,太励志了😂 谁能想到AI泡沫最后是被黄仁勋一jb戳破的 大意了,大意了。老黄大意了。 常在河边走, 哪有不湿鞋, 况且还湿了个破鞋。 美國成功企業家背後都有一位中國美女,如媒體大亨的前妻,甲骨文老闆的妻子。 老話一句,大男人褲帶要綁緊。 應該不是外国間諜, 可能是AMD間諜 成龙:(设计对白)他犯了天下间男人都会犯的错。🙏🙏理解万岁 理解万岁 在美国人眼里,黄仁勋永远是中国人 黃仁勳太早離開台灣了,對中國歷史不夠熟 老…
【富可敌国】星驰公益每天放福利啦 送1000刀 送1000刀 无任何充值 #星驰公益 各位佬友 每天14:00 领取千刀兑换码 领兑换码 cdk.linux.do LINUX DO CDK Linux Do 社区 CDK 快速分享平台 - 让分享变得更简单 去哪用 领到之后到这里兑换:xingchiapi.com 星驰API公益站 - AI API Gateway 评论点赞随机私聊发送发兑换码 支持模型 gpt-6-astra、gpt-6.1-sol 其他模型陆续开放 TG频道:Telegram: Telegram: View @xingchigongyi TG交流群:Telegram: Telegram: Join Group Chat 92 个帖子 - 87 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: 星驰公益) Invalid media: image
无聊做了个蛆的模型 蛆 · 三维形态 6.1Sol做的 很精细 只迭代一轮(修复头尾有个小洞的问题) 其实一开始就只是想做这个图来着 ---------------------- 一编: 透明底版本 ---------------------- 二编: 精细化版本 40 个帖子 - 34 位参与者 阅读完整话题 via LINUX DO - 热门话题 (author: OctoberSama)
Showing the 12 most recent of 1,685 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.
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.
Handles this channel named that no longer answer
- Dead references
- 3
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 3
- vacant every time we have ever looked
@linuxdoit named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 3 October 2026 – 4 October 2026
named in 1 post, 3 October 2026 – 3 October 2026
named in 1 post, 10 August 2026 – 10 August 2026
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 November 2026 — this entry's latest reading, not the date you are reading this.
“linux.do” (@linuxdoit), 23,893 subscribers as measured 12 November 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.