泡芙小圆手 (@tnanko_haha) 在 6 astra快是快,就是后端不动脑思考 中发帖 大佬们有没有遇到过这个情况,如何解决呢?

Channel
LINUX DO Channel
@linux_do_channel
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
36,699subscribers
+1,463 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 | 4 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/linux_do_channel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 15:00 | 36,699 | +95 |
| 2 Sept 2026, 23:23 | 36,604 | +61 |
| 1 Sept 2026, 19:54 | 36,543 | +45 |
| 31 Aug 2026, 21:25 | 36,498 | +63 |
| 30 Aug 2026, 21:07 | 36,435 | +23 |
| 29 Aug 2026, 18:38 | 36,412 | +37 |
| 28 Aug 2026, 19:37 | 36,375 | +50 |
| 27 Aug 2026, 17:46 | 36,325 | +61 |
| 26 Aug 2026, 19:02 | 36,264 | +49 |
| 25 Aug 2026, 16:53 | 36,215 | +73 |
| 24 Aug 2026, 14:25 | 36,142 | +82 |
| 22 Aug 2026, 18:44 | 36,060 | +46 |
| 21 Aug 2026, 11:28 | 36,014 | +73 |
| 20 Aug 2026, 12:03 | 35,941 | +65 |
| 19 Aug 2026, 11:45 | 35,876 | +45 |
| 18 Aug 2026, 13:15 | 35,831 | +51 |
| 17 Aug 2026, 14:16 | 35,780 | +95 |
| 16 Aug 2026, 05:48 | 35,685 | +78 |
| 14 Aug 2026, 14:08 | 35,607 | +80 |
| 13 Aug 2026, 06:55 | 35,527 | first reading |
Engagement
1,280 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 64 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.107%
- avg views ÷ 36,699 subscribers
- Avg views / post
- 39.2
- 1,240 posts measured
- Reaction rate
- 0.434%
- reactions ÷ views · ER floor
- Posts in window
- 1,240
- of 1,280 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 8 of 1,240 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 September 2026 |
|---|---|
| Posts held | 1,280 (7 August 2026 – 7 September 2026) |
| Views total | 48,575 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Sept 2026, 00:57 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
- ≈454,000
Lifetime counters from Telegram’s own channel header, read 7 September 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
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😱 | 1 | 100.0% |
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 6 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 1 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 12 August 2026 to 7 September 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
@jing0306 在 如何查看是哪一个帖子被举报的? 中发帖 这个是另外一个号的,如何查看是那一条被举报的内容呢? 如何联系管理呢? [chrome_l2Z41jj4fq]
@xiaoyu6666 在 有那种快过期的team工作空间吗 中发帖 有那种快过期的team工作空间吗,各位佬,我很有诚意!
zhangn 在 实在不理解为啥L站有帖子推bybit 中发帖 跟风申请了,发现就1%返现之外,没别的优惠,折腾半天,在灰色的小字链接点进去,看到一堆MCxx的编号,再仔细看,好像是特定商户消费才返现10%,这不忽悠人吗?大多数是旅游,酒店,飞机的。
@xiaoyu6666 在 【收team】7,8,9,10的临期都要,高价回收 中发帖 【收team】7,8,9,10的临期都要,高价回收,价格可谈,后面的日期也可以来谈
Zane (@Zanen) 在 360:A\赶紧有多远滚多远,老子现在用GPT6了 中发帖 今天上班例行更新一下vscode的插件,结果360直接把Claude Code 2.1.260的Claude.exe判为木马了,可惜当时弹窗拦截报毒的时候没截图,只有这个了,我笑死,360圈粉了 [image] [image] [image]
@Bethany 在 求分享,大家现在在用什么 AI?求 GPT、Claude 性价比方案 中发帖 来向各位大神请教,现在日常各位都在用哪些 AI 工具? 想使用 ChatGPT、Claude,官方订阅成本高,注册支付也有门槛。求靠谱、性价比高的使用渠道,有踩坑经历也欢迎提醒,谢谢大家。
小许 (@XiaoXuRa) 在 震惊,GPT现在可以退出已经封禁的空间了 中发帖 [image] 我记得半个月前还不行的,一直加载中,但是今天寻思点一下试试,发现可以退出了
行思渐远 (@6868888) 在 GPT6 sub2api额度估算 中发帖 以前5.6sol sub2api,基本在2000$-2500$/周上下浮动. 现在GPT 6,sub2api,已用百分之50,消耗$731刀,一周就是一周大概就是1460刀。 [image] 这个已消耗也不全是用GPT6,有时候还会用一下GPT 5.6 模型,所以只能粗略估计,仅供参考.
JXMs 在 ollama的deepseek v4 flash真的没降智吗? 中发帖 俺刚才让K3写了一份prompt交给dsv4f执行,试了两遍都是在工作树来回打转,完全没有任何进展。俺生气的不行,就直接掏了d老师官方api推,结果一次就ok了,也不打转,一击即中。 ollama的d老师真的没降智吗?这智力感觉还不如commandcode的GOAT :bili_020:
Frank Darking 在 zcode号被封了?还是服务器炸了。 中发帖 昨天领了免费额度,搞了一整天逆向,早上起来号被强退了·····登录不上去了
@MeiCai 在 Team订阅该怎么避免GPT封子号呢?已经被封三次了 中发帖 可能是母号花钱的原因一直没事,但是子号我拉一个封一个,不管是本地用还是CPA都坚持不到一周,被封后我就踢掉再拉新的,但是这种情况多了之后怕连累母号,该怎么办呢?
Showing the 12 most recent of 1,280 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 · 114 postsY
@fanjie · 13 postsCHG NEWS - Новости😮💨
@chgblog2 postsHonest
@honest · 2082 postsneptune1
@neptune12 postsT彩
@tcai · 1,6472 postsailii
@ailii · 31 post斑斓
@banlan · 31 post搜女推广|Instagram账号|IG增粉|IG资源
@bunnhack · 21 postUsernames – III abccc
@feddd · 171 post菲德
@feide · 21 post我是卡尔白!
@Karlbaey · 21 postVafli.ai
@lion_cai1 postanonпж
@maincai · 11 post🫶
@ngunfi · 11 postpizzatnt
@pizzatnt · 11 post六合彩源码彩票网源码搭建信用盘源码搭建
@qaqa393 · 2671 post@qinggan
@qinggan · 21 post首饰/时尚
@shoushi · 21 post万事如意 待售
@wanshiruyi · 21 postxiao777
@xiao777 · 31 postxiaoyouzi
@xiaoyouzi · 21 postSpider man
@Yomihime · 11 post@yuncan
@yuncan · 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
- 171
- 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
- 171
- vacant every time we have ever looked
@linux_do_channel named 171 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 6 posts, 9 August 2026 – 18 August 2026
named in 3 posts, 18 August 2026 – 6 September 2026
named in 3 posts, 8 August 2026 – 5 September 2026
named in 3 posts, 8 August 2026 – 14 August 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, 3 September 2026 – 3 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, 6 September 2026 – 6 September 2026
named in 1 post, 6 September 2026 – 6 September 2026
named in 1 post, 6 September 2026 – 6 September 2026
named in 1 post, 6 September 2026 – 6 September 2026
named in 1 post, 6 September 2026 – 6 September 2026
named in 1 post, 6 September 2026 – 6 September 2026
named in 1 post, 6 September 2026 – 6 September 2026
named in 1 post, 5 September 2026 – 5 September 2026
named in 1 post, 5 September 2026 – 5 September 2026
named in 1 post, 5 September 2026 – 5 September 2026
named in 1 post, 5 September 2026 – 5 September 2026
named in 1 post, 5 September 2026 – 5 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 4 September 2026 – 4 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 3 September 2026 – 3 September 2026
named in 1 post, 2 September 2026 – 2 September 2026
named in 1 post, 2 September 2026 – 2 September 2026
named in 1 post, 2 September 2026 – 2 September 2026
named in 1 post, 2 September 2026 – 2 September 2026
named in 1 post, 2 September 2026 – 2 September 2026
121 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 · 35,906#1
@zaihuapd · 280,522#2
@AI_News_CN · 21,580#3
@pokemon521 · 68,583#4
@serveruniverse · 1,407#5
@AI_Copilot_Channel · 10,554#6
@zhetengsha · 48,646#7
@coalcloud · 6,071#8
@akile_notice · 18,501#9
@DNSPODT · 71,413#10
@BestVmCloud · 2,794#11
@projectXtls · 29,900#12
@vps_xhq · 49,371#13
@acgdaily · 16,474#14
@kuaileceshi2 · 3,718#15
@Ptfxq · 17,119#16
@wtfbugtoday · 2,939#17
@me888888888888 · 49,394#18
@NewlearnerChannel · 67,021#19
@UOVZNEWS · 5,045#20
@hostloc2tg · 4,420#21
@hostmonit · 10,404#22
@vps_track_share · 3,425#23
@GodlyNews1 · 68,526#24
@xhqcankao · 160,314#25
@wawowiki · 2,691#26
@nezhanews · 3,549#27
@landiansub · 44,267#28
@tnews365 · 157,625#29
@hax_seats · 3,003#30
@wap_ac · 3,220#31
@yxvmcom · 2,468#32
@DMITstock · 10,698#33
@pasyun1 · 2,012#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 · 68,583
Telegram ranks this channel #1 of 35 here — alongside 34 others — read 21 August 2026
@MatsuriDayo · 45,305
Telegram ranks this channel #4 of 58 here — alongside 57 others — read 30 August 2026
@nodeseekc · 35,906
Telegram ranks this channel #23 of 52 here — alongside 51 others — read 2 September 2026
@chongshengvpn · 71,061
Telegram ranks this channel #32 of 35 here — alongside 34 others — read 20 August 2026
This channel appears in 4 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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“LINUX DO Channel” (@linux_do_channel), 36,699 subscribers as measured 4 September 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.