搬瓦工涨价后的漏网之鱼,迪拜机房,可切换美西CN2,荷兰CN2等多机房 简单讲就是上次下架的169刀年付套餐同款,可能随时下架,有需求的可先加入购物车 方案: 硬盘:20 GB SSD 内存:1 GB CPU:2 核心 流量:500 GB/月 带宽:1Gbps 月付:19刀,年付:169刀 购买:https://bwh89.net/aff.php?aff=62581&pid=114

Channel
1024社区 | 1024.day
@Hello_1024
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry
12,493subscribers
+54 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 | -1001482339148 |
|---|---|
| Type | Channel |
| Username | @Hello_1024 |
| Description | 这是一个分享VPS资讯以及Linux学习频道。 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 57 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/Hello_1024 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 |
|---|---|---|
| 11 Nov 2026, 11:57 | 12,493 | +5 |
| 9 Nov 2026, 15:56 | 12,488 | +1 |
| 8 Nov 2026, 08:56 | 12,487 | +2 |
| 7 Nov 2026, 06:39 | 12,485 | +5 |
| 6 Nov 2026, 08:56 | 12,480 | +1 |
| 5 Nov 2026, 09:56 | 12,479 | +2 |
| 4 Nov 2026, 09:18 | 12,477 | +6 |
| 3 Nov 2026, 05:46 | 12,471 | +2 |
| 2 Nov 2026, 06:07 | 12,469 | +1 |
| 1 Nov 2026, 06:49 | 12,468 | +4 |
| 31 Oct 2026, 10:19 | 12,464 | +5 |
| 30 Oct 2026, 09:30 | 12,459 | +3 |
| 29 Oct 2026, 11:16 | 12,456 | +1 |
| 28 Oct 2026, 11:36 | 12,455 | +3 |
| 27 Oct 2026, 12:01 | 12,452 | -2 |
| 26 Oct 2026, 09:25 | 12,454 | +2 |
| 25 Oct 2026, 05:57 | 12,452 | +7 |
| 24 Oct 2026, 06:29 | 12,445 | -2 |
| 23 Oct 2026, 06:27 | 12,447 | -5 |
| 22 Oct 2026, 07:10 | 12,452 | first reading |
Engagement
40 posts held, back to 11 June 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 67 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 39.7%
- avg views ÷ 12,493 subscribers
- Avg views / post
- 4,960
- 8 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 8
- of 40 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.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 40 (11 June 2026 – 7 November 2026) |
| Views total | 39,650 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 20:41 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
- ≈425
- Videos
- ≈7
- Links
- ≈1,110
Lifetime counters from Telegram’s own channel header, read 11 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
- 30s
- Average length
- 30s
Measured directly from 1 video 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.
Recent posts
Telegram’s own ‘edited’ marker: 1 of 8 posts held from the last 30 days (12.5%) 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).
https://1024.day/d/4124 距上次开放注册已过3个月,本社区11月份放出注册邀请码200个
被墙的IP逐步放出来了,开始大赦天下了。 https://t.me/Hello_1024/4053
搬瓦工 E-Commerce VPS 入门款增加了1 vCPU,1T流量,价格由年付169刀涨到299刀,直白点讲就是涨价了! 详见:https://bwh89.net/aff.php?aff=62581
这个线路又有变动,联通回程由CMI改成了AS10099,也就是4837,联通也能打了。 线路: 电信:香港163PP 联通:香港4837 移动:香港CMI 香港EB线路,总体来说是一个被低估的香港线路机,详细评测如下(联通回程改成4837): https://hostalk.net/posts/dmit_hkeb.html
二十届五中全会于 2026年10月26日至29日 在北京召开 懂吧?
最新Linux 网络栈漏洞:客户机可构造普通网络包,利用延迟校验和计算篡改数据包元数据,进而读取甚至写入宿主机内核内存,最终可能实现从虚拟机逃逸到宿主机。 https://pwn.ai/blog/pwnescape 研究者于 2026 年 8 月发现并报告问题,上游补丁于 2026 年 10 月 8 日进入 net.git,并于 2026 年 10 月 14 日合入 Linux 主线。 建议:尽快升级到包含官方修复的 Linux 内核版本。
ZgoCloud补货洛杉矶9929+CMIN2优化线路机型,上游kurun,带宽300Mbps,原生IP 电信,联通走9929,移动走CMIN2 1 Core AMD EPYC 7003 Series or Intel(R) Xeon(R) Gold 2 GB DDR4 RAM 30G NVMe SSD 1 IPV4 1T/Month/300Mbps 购买:https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=66 2 Cores AMD EPYC 7003 Series or Intel(R) Xeon(R) Gold 3 GB DDR4 RAM 50G NVMe SSD 1 IPV4 2T/Month/300Mbps 购买:https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=67 …
因为DMIT香港EB线路有变动,所以重新测试了下香港EB线路,总体来说电信无脑入,联通移动可用: https://hostalk.net/posts/dmit_hkeb.html
DMIT 香港特价款EB套餐上线了 香港AS3 EB WEE套餐: 1C / 1G / 20G SSD / 500G 流量每月 / 24.9刀每月 购买:https://www.dmit.io/aff.php?aff=1538&pid=209 详细评测:https://1024.day/d/4093 联通路由有改观,官方测速:https://lg.dmit.sh/?server=hkg-eb 联通去程优化了,没走ntt了,和HKG Pro去程一致,走的4837 - CTG,延时降下来了,回程CMI不变
DMIT 洛杉矶Pro套餐补货了 洛杉矶Pro套餐,三网CN2GIA: 1C / 2G / 20G SSD / 1T 流量每月 / 10.9刀每月 https://www.dmit.io/aff.php?aff=1538&pid=253
香港EB上架了 购买: https://www.dmit.io/cart.php?region=hong-kong&network=eyeball&generation=as3&aff=1538
Showing the 12 most recent of 40 posts we hold for @Hello_1024. 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.
Posts recorded as deleted after publishing
We recorded 2 posts on @Hello_1024 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 20 August 2026
- Most recent seen missing
- 26 August 2026
- Median time before seen missing
- 4 days
- Seen missing in the last 30 days
- 0
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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.
@abskoop · 303,754
Telegram ranks this channel #44 of 50 here — alongside 49 others — read 17 August 2026
@github_2dust · 92,921
Telegram ranks this channel #59 of 71 here — alongside 70 others — read 17 August 2026
This channel appears in 2 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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“1024社区 | 1024.day” (@Hello_1024), 12,493 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/Hello_1024.
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.