#服务器 腾讯云轻量应用服务器六周年秒杀活动,2 核 4GB 内存 5M 服务器仅 88 元 / 年。 热门款: 国内:2 核心 2GB 内存 5M 带宽 - 58 元 / 年 国内:2 核心 4GB 内存 5M 带宽 - 88 元 国内:4 核心 8GB 内存 12M 带宽 - 298 元 / 年 国内:2 核心 2GB 内存 5M 带宽 - 3 年版 199 元 / 年 抢购地址:https://ourl.co/ltfs 😁订阅 🤔解封 🥰推特 🎉CN2VPS
👎39👍6❤1

Channel
@landiansub
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
44,850subscribers
+1,875 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001125882855 |
|---|---|
| Type | Channel |
| Username | @landiansub |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/landiansub |
Hacking & security — 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 92% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 16:37 | 44,850 | +121 |
| 17 Sept 2026, 03:36 | 44,729 | +107 |
| 15 Sept 2026, 01:21 | 44,622 | +61 |
| 13 Sept 2026, 09:41 | 44,561 | +108 |
| 11 Sept 2026, 13:39 | 44,453 | +66 |
| 9 Sept 2026, 00:01 | 44,387 | +120 |
| 5 Sept 2026, 15:17 | 44,267 | +46 |
| 3 Sept 2026, 19:20 | 44,221 | +62 |
| 2 Sept 2026, 09:03 | 44,159 | +18 |
| 1 Sept 2026, 12:24 | 44,141 | +28 |
| 31 Aug 2026, 13:17 | 44,113 | +28 |
| 30 Aug 2026, 14:43 | 44,085 | +33 |
| 29 Aug 2026, 12:04 | 44,052 | +29 |
| 28 Aug 2026, 14:44 | 44,023 | +39 |
| 27 Aug 2026, 11:33 | 43,984 | +37 |
| 26 Aug 2026, 11:52 | 43,947 | +42 |
| 25 Aug 2026, 14:48 | 43,905 | +46 |
| 24 Aug 2026, 15:52 | 43,859 | +44 |
| 23 Aug 2026, 03:14 | 43,815 | +62 |
| 21 Aug 2026, 12:58 | 43,753 | first reading |
497 posts held, back to 4 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 95 pages of Telegram’s post history, 20 posts per page.
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 23 September 2026 |
|---|---|
| Posts held | 497 (4 August 2026 – 23 September 2026) |
| Views total | 1,279,140 |
| Reactions total | 20,807 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 21: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.
Lifetime counters from Telegram’s own channel header, read 23 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.
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.
33,636 reactions across 479 posts, in 50 distinct kinds. The most used accounts for 22.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 7,652 | 22.7% | |
| 😁 | 7,389 | 22.0% | |
| 👍 | 3,895 | 11.6% | |
| 👎 | 2,613 | 7.77% | |
| 🖕 | 1,223 | 3.64% | |
| ❤ | 1,130 | 3.36% | |
| 🤬 | 950 | 2.82% | |
| 🤔 | 786 | 2.34% | |
| 🫡 | 620 | 1.84% | |
| 🤯 | 537 | 1.60% | |
| 👌 | 531 | 1.58% | |
| 🥱 | 502 | 1.49% | |
| 🤗 | 481 | 1.43% | |
| 😭 | 452 | 1.34% | |
| 🤪 | 442 | 1.31% | |
| 😱 | 432 | 1.28% | |
| 🕊 | 378 | 1.12% | |
| 💊 | 357 | 1.06% | |
| 👏 | 322 | 0.957% | |
| 🌚 | 299 | 0.889% | |
| 30 further kinds | 2,645 | 7.86% |
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 492 of the 497 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 34,343 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 497 most recent posts we hold, published 4 August 2026 to 23 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @landiansub. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 497 most recent posts we hold for this entry, published 4 August 2026 to 23 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
#服务器 腾讯云轻量应用服务器六周年秒杀活动,2 核 4GB 内存 5M 服务器仅 88 元 / 年。 热门款: 国内:2 核心 2GB 内存 5M 带宽 - 58 元 / 年 国内:2 核心 4GB 内存 5M 带宽 - 88 元 国内:4 核心 8GB 内存 12M 带宽 - 298 元 / 年 国内:2 核心 2GB 内存 5M 带宽 - 3 年版 199 元 / 年 抢购地址:https://ourl.co/ltfs 😁订阅 🤔解封 🥰推特 🎉CN2VPS
👎39👍6❤1
#行业资讯 阿里云宣布向 Omarchy 捐赠 300 万美元,也将为 Omarchy 提供中国服务器和 CDN 赞助等。 阿里云每年向 Omacom 基金会捐赠 100 万美元,持续 3 年合计 300 万美元。 阿里巴巴 Qwen Book 将支持 Omarchy 系统,Omarchy 需要对千问模型进行开箱即用优化以及与用户依赖的中国服务实现全面集成。 查看全文:https://ourl.co/127076?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
👎58🤡20🥴13🤨2❤1👍1🖕1😁1
#硬件设备 苹果更新支持文档不再将 M5/M6 Mac Mini SSD 列为可更换零件,当然这只是苹果官方层面的,不影响华强北工程师继续扩容。 在旧款 Mac Mini 中,固态盘类似 2242 尺寸 (实际是苹果定制的),可以拔掉更换。 但新款 Mac Mini 将 NAND 芯片焊在逻辑板上,无论是更换还是扩容都需要吹掉原芯片重新植球焊接,扩容时还需要补线路等。 查看全文:https://ourl.co/127080?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
🤡49👎10😁2❤1
#安全资讯 朝鲜黑客伪装成招聘方投放恶意代码,相关活动涉及 100 多个国家和地区的从业者,窃取超过千万美元加密货币。 这些黑客在各类平台自称招聘软件工程师、前端工程师和加密货币从业者,通过虚假技术面试和编程测试传播恶意软件。 例如黑客要求应聘者打开的仓库里面包含后门程序,可以持续从 PC 上窃取敏感数据。 查看全文:https://ourl.co/127079?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
🔥20😁4🤯3🖕2👎1
#系统资讯 中国区独占功能:iOS 27.2 测试版新增运动传感器设置,主要意义就是打击摇一摇广告。 该功能不区分国行版还是外版,只有应用商店登录国区账号时才有效。 用户可以在设置、隐私与安全、运动与健身下,将与运动健身无关的应用全部禁用读取运动数据,这样摇一摇开屏广告就不会在轻微晃动时被触发。 查看全文:https://ourl.co/127078?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
🤡59👍37🥴3😁2🤬1
#人工智能 特朗普在联大演讲中表示,美国政府文件将把人工智能改为超级智能 (SI),希望其他国家也跟着改。 特朗普再次强调人工这个词听起来让人觉得是虚假的,所以要改成超级智能。 不过超级智能并不是特朗普发明的,在人工智能研究中超级智能通常指认知能力显著超过人类、能够在广泛领域胜过人类的理论系统。 查看全文:https://ourl.co/127077?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
🤡73👌6😁2🤪1🥰1
#系统资讯 苹果正在为 iPhone 开发防抢自动锁定功能,检测到手机可能被抢后将自动锁定避免数据泄露。 该功能对应的场景是在某些国家经常发生的手机抢劫事件,用户正在刷视频结果手机被抢,此时手机仍然处于解锁状态。 苹果将利用多种信号判断手机是否异常,如果异常则自动锁定设备,这样至少可以避免抢劫犯获取手机里的数据。 查看全文:https://ourl.co/127031?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
😁59🥰4
#系统资讯 Android 17 或增加使用谷歌账号解锁功能,忘记 PIN 码后无需恢复出厂设置清空所有数据。 该功能目前出现在 Android 17 QPR2 Beta 5 中,只有代码并未实际启用功能。 从代码描述来看该功能默认关闭,启用后如果用户忘记 PIN 码,就可以登录谷歌账号解锁设备。 默认关闭而非开启是因为 PIN 码是手机数据保护的最后一道防线,谷歌担心攻击者同时获得手机和账号凭据后绕过屏幕锁获得用户数据。 查看全文:https://ourl.co/127030?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
😱33👎7😁5
#手机数码 iPhone 18 Pro 系列在面容识别失败后可能会出现触控失灵 / 系统卡死 / 自动重启等问题。 该问题并非发生在解锁阶段,而是打开密码等密码保护的应用中,如果故意遮挡面部触发认证失败,再次点击尝试面容解锁时,系统就会发生问题。 目前苹果尚未就此事发布回应,估计后需要通过 iOS 更新修复问题。 查看全文:https://ourl.co/127029?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
💊41😁12🤡3🤬2❤1
#软件资讯 谷歌正在调查 Chrome for macOS 扩展程序弹窗加载缓慢问题,像是 1Password 等扩展点击后可能要等待数分钟才能弹出窗口。 在接到用户反馈后 Chrome 开发团队承诺将这个问题设置高优先级进行调查,不过当前尚不清楚问题发生原因,也没有临时解决方案。 查看全文:https://ourl.co/127028?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
🥱26😁1
#行业资讯 开源项目维护者拿不到收益怎么办?能不能强迫企业使用开源软件时付费? NPM 联合创始人劳里・沃斯日前发表长文讨论开源软件领域长期存在的商业困境,事实上企业在为各类供应链服务商付费,但原始项目维护者很少获得收益。 劳里・沃斯建议向大型公司收取开源软件使用费,这部分资金将分配给维护者,让维护者可以从自己创造的代码被广泛使用的事实中获得收益。 查看全文:https://ourl.co/127027?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
👍69👏7🤔5❤2😁2
#安全资讯 被数亿网站使用的 WordPress 被爆出新漏洞:Click2Shell,管理员点击恶意链接可以触发 PHP 代码执行。 该漏洞危害程度较高,目前 WordPress 已经在 7.1.1 版中修复漏洞,旧分支版本也获得补丁移植。 建议使用 WordPress 的网站立即升级到不受影响的新版本,或者通过配置文件启用策略阻止后台安装主题和插件。 查看全文:https://ourl.co/127026?t 😁订阅 🤔解封 🥰推特 🎉CN2VPS
😁24🌚7❤1
Showing the 12 most recent of 497 posts we hold for @landiansub. 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.
@landiansub edited 12 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 30 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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.
Read from Telegram’s recommendation API, most recently 28 August 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.
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.
This channel appears in 76 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“蓝点网订阅频道” (@landiansub), 44,850 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/landiansub.
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.