fist2005 在 Anthropic 正式推出 Claude Duet 中发帖 Anthropic 今天正式发布Claude Duet。它会主动盯着你的邮箱、日历、记账软件这些账号,发现要处理的事就来提醒你,交给它的任务你关机后也照样做。目前是研究预览版,只对美国用户开放候补名单。 [image] 官网产品介绍 加入候补名单:

Channel
LINUX DO Channel
@linux_do_channel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
38,707subscribers
+3,471 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002035446470 |
|---|---|
| Type | Channel |
| Username | @linux_do_channel |
| Description | https://linux.do 论坛的话题更新通知频道。 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 October 2026 |
| Measurements held | 44 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/linux_do_channel |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Oct 2026, 08:10 | 38,707 | +81 |
| 20 Oct 2026, 03:37 | 38,626 | +51 |
| 19 Oct 2026, 00:55 | 38,575 | +63 |
| 18 Oct 2026, 00:28 | 38,512 | +42 |
| 17 Oct 2026, 00:06 | 38,470 | +30 |
| 16 Oct 2026, 02:19 | 38,440 | +48 |
| 15 Oct 2026, 03:30 | 38,392 | +60 |
| 13 Oct 2026, 21:17 | 38,332 | +202 |
| 10 Oct 2026, 13:54 | 38,130 | +175 |
| 6 Oct 2026, 11:14 | 37,955 | +178 |
| 1 Oct 2026, 06:42 | 37,777 | +466 |
| 18 Sept 2026, 05:39 | 37,311 | +96 |
| 16 Sept 2026, 01:00 | 37,215 | +74 |
| 14 Sept 2026, 06:17 | 37,141 | +60 |
| 12 Sept 2026, 17:18 | 37,081 | +68 |
| 10 Sept 2026, 16:00 | 37,013 | +154 |
| 7 Sept 2026, 16:15 | 36,859 | +160 |
| 4 Sept 2026, 15:00 | 36,699 | +95 |
| 2 Sept 2026, 23:23 | 36,604 | +61 |
| 1 Sept 2026, 19:54 | 36,543 | first reading |
Engagement
2,780 posts held, back to 7 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 139 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.083%
- avg views ÷ 38,707 subscribers
- Avg views / post
- 32.2
- 1,180 posts measured
- Reaction rate
- 2.66%
- reactions ÷ views · ER floor
- Posts in window
- 1,180
- of 2,780 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 34 of 1,180 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 October 2026 |
|---|---|
| Posts held | 2,780 (7 August 2026 – 21 October 2026) |
| Views total | 37,968 |
| Reactions total | 32 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Oct 2026, 19:30 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
- Links
- ≈498,000
Lifetime counters from Telegram’s own channel header, read 21 October 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.
Reaction mix
32 reactions across 31 posts, in 2 distinct kinds. The most used accounts for 96.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 31 | 96.9% | |
| ❤ | 1 | 3.13% |
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 34 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 32 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 27 September 2026 to 21 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
Zcb 在 抛开信息安全,中转站和订阅到底哪个更划算? 中发帖 我实在搞不明白,似乎中转好像更便宜,但是订阅又有时不时重置,求各位佬解惑
@LeoQAQ 在 codex Pro100,最近天天重置,额度用不完,佬们给点建议 中发帖 快到期了,连续2周额度没下过50%,还有几张重置卡。到期后就准备换号了,佬们给点建议,搞点啥好呀
鸽吾安 (@guanhuhao) 在 【Jev 决策模型】| 除了变得更聪明,AI还可以?—— Opus 5.5 科普视频试水制作 中发帖 Opus 5.5 太强了,圆了我想做科普视频的梦! 国庆期间看 Vibe Coding 使用Opus 5.5 + Hyperframes 做科普视频,一整个大震惊! 最近终于有空尝试了一下,摸索一下视频制作工作流,把之前的 发的 Jev 的文章作为基础修改了一下,效果太棒了! 现在唯一的问题是,Opus 5.5 比较慢通常一个很小的修改也需要 10 mins,不过效率都属于工程问题 未来可期! 以后慢慢吧自己学到的看到的有趣的东西转化成科普视频,这感觉太棒了,起号! 等熟悉完善一下自己的工作流,看看能不能把这种视频制作工作流也开源了 嘿嘿~
keroro军曹 (@wildman) 在 软著有什么想法吗 中发帖 最近想拿个软著,提升一下级别,不知道各位有什么想法吗?毕竟ai时代,感觉idea比能力更重要,要是到时候想法采纳,到时候可以包个小红包
@miliyam_bell 在 claude的重置卡都是哪来的 中发帖 刚刚突然福至心灵打开claude app看了一眼,发现我有一张重置卡23号就过期了,正愁这周周限头两天就用完了,于是赶紧用了,感觉跟从旧衣服兜里发现二百块一样。 不过这重置卡是哪来的?我这个号是10月2号开的pro,最近有送过重置卡吗?还是说每个新开的号都有,我之前都没注意过 🥲,差点就亏大了
@Drlinuxdo 在 让dsv4.1f简化一个插件,结果所有行为100%出错,最后dsh被塞满了屎山 中发帖 让ds4.1f给一个插件做个精简,结果它的每一个判断/行为/决策,全他妈都是错的,每一个!甚至是在放任模型进行防御性编程,做了大量检查和测试的情况下,因为测试的结果也他妈是错的!只要问它上一轮回答/行为的正确性,它一定会说自己做错了,而且也都的确是错的。 现在新旧两个插件互相打架已经快在dsh里拉满了屎了,而且问题越来越多了。 什么提示词、插件都屁用没有,前脚说明白了后脚就继续犯。 最麻烦的就是狗日的闷头干的毛病,根本不汇报进度,眨个眼睛的功夫就开始瞎搞了,而且因为是flash模型,等你发现不对劲的时候它已经在上下文里拉了小几万token的屎了。 一晚上的时间,本来只是给插件删点东西的,一晚上过去后整个dsh都快要被迫重装了…… 论坛里那些说模型够用就行的人是怎么做到的?智力不够的模型哪怕你把要求和规范写好了,喂到…
Neo (@tausak) 在 大半夜的,抱怨几句 中发帖 当生活过的太顺的时候就要小心生活背后给你捅刀子了。 事情要从今年 5 月份开始说起。5 月末的时候,我在 BOSS 直聘上找大三的实习公司,遇见了一位老板。我们 5 月份加了微信,约定 6 月末左右去上班。6 月末刚好我放假,就直接去上班了。 老板人很好,工作安排也很合理,我在那里上班挺快乐的。我很幸运能在大三实习时碰到这样一位老板。在他身上我学到了很多,他还给我报销 AI 订阅,每个月准时发工资,大概 5000 左右,不算少。上班这几个月我也陆陆续续攒了点钱。 日子看起来越来越好了:白天上班,下班之后去学吉他、练练唱歌,晚上再复习专升本考试,感觉日子很有奔头。 但就在日子蒸蒸日上的时候,变故来了。 就在前天(20 号)中午偏下午的时候,老板给我发了一条消息,说项目那边出了问题。AI 发展太快,他现在接项目没办法把价格谈上来,被压得很低。没错,又是 AI, 现在很多客…
keroro军曹 (@wildman) 在 求gemini3.8 gemini4渠道 中发帖 有的话联系我,可不可以对公都可以说下,有量
@Blackwood416 在 感觉有大事件要爆了(纯意淫) 中发帖 最近这些漏洞全是高危还不好处理的,而且影响范围太广了,加上最近国模能力还挺强的,感觉有大规模(能直接影响到普通人)的攻击事件要发生了,就是不知道是何时何地了,不过我有预感大概在年前就会发生。希望我预言失败吧 🫠
酢乙女爱 (@caixukun6) 在 奖池还未结束,奖励继续叠加,Chrome 156.0.8078.48 版本紧急更新,修复了极高危漏洞 中发帖 奖池还未结束,奖励继续叠加,Chrome 156.0.8078.48 版本紧急更新,修复了极高危漏洞 继node.js也进入大逃杀时代 巨严重的bug,速度修复,T0级php漏洞,晚上抓紧更新 [image] Chrome Releases: Stable Channel Update for Desktop [image]
河豚 (@hnxxwf) 在 分享两个Claude小技巧注意事项,想玩Claude的可以参考参考 中发帖 一.本人网络代理配置:DMIT东京中转机+日本软银动态家宽落地机,中转机与落地机使用socks5连接。 二.封号情况:我自己有两个号,一个开会员做开发,另外一个拿来聊天,主要是想用两个号来测试排除偶然因素。除此之外,我还有俩朋友也用的我的网络代理,他们也用claude。目前三个人,共四个号,稳定了半年了,没有一个人封。这四个号的时区都是东八区,而且和Claude交互都说中文,软件内语言也全是简体中文,网页端,手机端(包括ios和安卓),Windows与MacOS桌面客户端,cil,全都用,全都登录了。也就是说,除了使用家宽以外,没有采用其他任何的防封措施。 三.KYC情况: 1.由于我用AI开发软件不怎么多,大部分还是自己古法编程,搞不定再喊AI,所以我一直用Pro,没用过Max,而我那俩朋友和我一样也是Pro,都不用Ma…
Showing the 12 most recent of 2,780 posts we hold for @linux_do_channel. 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.
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.
@lezishen · 229 postsneptune1
@neptune19 postsCHG NEWS - Новости😮💨
@chgblog4 postsY
@fanjie · 14 postsHonest
@honest · 2484 postsUsernames – III abccc
@feddd · 163 postsالسعاده|فرانكلن ♛ٌ💜
@Frankln3 posts我是卡尔白!
@Karlbaey · 33 postsyahataumiri
@yahataumiri · 23 postsAIBOX
@aibox · 21,9782 postsПрактическая астрология
@astrostar · 82 posts不归客
@buguike · 12 postsبعض مني هنا 🌿🧡
@Qq1244 · 92 posts【初夜】包养 选妃频道 @XuanFei
@xuanfei · 9,3492 postsCelax
@Celax · 11 postdahuanghe
@dahuanghe · 11 postd
@dext7r · 11 postfang7
@fang7 · 21 post菲德
@feide · 21 postWork
@figure · 1431 postlazyrain
@lazyrain · 11 postچنل اعتماد [ Vpanl]
@nextpi · 161 post@teruhashikokomi
@teruhashikokomi · 31 post文件传输助手
@wjcszs · 81 post
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
- 262
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 261
- vacant every time we have ever looked
@linux_do_channel named 262 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 6 posts, 8 August 2026 – 20 September 2026
named in 6 posts, 9 August 2026 – 18 August 2026
named in 5 posts, 8 August 2026 – 2 October 2026
named in 4 posts, 18 August 2026 – 4 October 2026
named in 3 posts, 3 September 2026 – 3 October 2026
named in 3 posts, 18 August 2026 – 6 September 2026
named in 2 posts, 11 August 2026 – 19 October 2026
named in 2 posts, 11 October 2026 – 19 October 2026
named in 2 posts, 4 October 2026 – 11 October 2026
named in 2 posts, 3 October 2026 – 6 October 2026
named in 2 posts, 27 September 2026 – 4 October 2026
named in 2 posts, 3 September 2026 – 4 October 2026
named in 2 posts, 31 August 2026 – 3 October 2026
named in 2 posts, 2 September 2026 – 11 September 2026
named in 2 posts, 5 September 2026 – 5 September 2026
named in 2 posts, 11 August 2026 – 4 September 2026
named in 2 posts, 10 August 2026 – 27 August 2026
named in 2 posts, 13 August 2026 – 20 August 2026
named in 2 posts, 8 August 2026 – 14 August 2026
named in 2 posts, 10 August 2026 – 11 August 2026
named in 1 post, 19 October 2026 – 19 October 2026
named in 1 post, 19 October 2026 – 19 October 2026
named in 1 post, 19 October 2026 – 19 October 2026
named in 1 post, 19 October 2026 – 19 October 2026
named in 1 post, 13 October 2026 – 13 October 2026
named in 1 post, 13 October 2026 – 13 October 2026
named in 1 post, 13 October 2026 – 13 October 2026
named in 1 post, 13 October 2026 – 13 October 2026
named in 1 post, 13 October 2026 – 13 October 2026
named in 1 post, 11 October 2026 – 11 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 9 October 2026 – 9 October 2026
named in 1 post, 8 October 2026 – 8 October 2026
named in 1 post, 8 October 2026 – 8 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 7 October 2026 – 7 October 2026
named in 1 post, 6 October 2026 – 6 October 2026
212 more handles are in this same list but not shown individually here — capped at 50.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@nodeseekc · 38,631#1
@zaihuapd · 286,562#2
@AI_News_CN · 22,763#3
@pokemon521 · 74,406#4
@serveruniverse · 1,410#5
@AI_Copilot_Channel · 11,052#6
@zhetengsha · 52,152#7
@coalcloud · 5,975#8
@akile_notice · 18,826#9
@DNSPODT · 72,815#10
@BestVmCloud · 2,940#11
@projectXtls · 30,018#12
@vps_xhq · 50,251#13
@acgdaily · 16,887#14
@kuaileceshi2 · 3,778#15
@Ptfxq · 17,358#16
@wtfbugtoday · 3,116#17
@me888888888888 · 52,186#18
@NewlearnerChannel · 67,873#19
@UOVZNEWS · 5,075#20
@hostloc2tg · 4,472#21
@hostmonit · 10,831#22
@vps_track_share · 3,941#23
@GodlyNews1 · 70,183#24
@xhqcankao · 165,765#25
@wawowiki · 3,010#26
@nezhanews · 3,541#27
@landiansub · 46,071#28
@tnews365 · 165,259#29
@hax_seats · 2,925#30
@wap_ac · 3,283#31
@yxvmcom · 2,482#32
@DMITstock · 12,165#33
@pasyun1 · 2,080#34
Read from Telegram’s recommendation API, most recently 1 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@pokemon521 · 74,406
Telegram ranks this channel #1 of 35 here — alongside 34 others — read 21 August 2026
@AI_News_CN · 22,763
Telegram ranks this channel #3 of 45 here — alongside 44 others — read 22 September 2026
@MatsuriDayo · 45,626
Telegram ranks this channel #4 of 58 here — alongside 57 others — read 30 August 2026
@nodeseekc · 38,631
Telegram ranks this channel #23 of 52 here — alongside 51 others — read 2 September 2026
@chongshengvpn · 70,281
Telegram ranks this channel #32 of 35 here — alongside 34 others — read 20 August 2026
This channel appears in 5 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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“LINUX DO Channel” (@linux_do_channel), 38,707 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/linux_do_channel.
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.