I guess CSS is hard.

Channel
黑科技资源分享
@deeptech123
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,471subscribers
+121 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001577030058 |
|---|---|
| Type | Channel |
| Username | @deeptech123 |
| Created | Between 1 August 2021 and 28 February 2023 — 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 | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/deeptech123 |
Topic
Science — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 |
|---|---|---|
| 19 Sept 2026, 16:21 | 3,471 | +19 |
| 15 Sept 2026, 14:20 | 3,452 | +2 |
| 12 Sept 2026, 03:58 | 3,450 | +13 |
| 7 Sept 2026, 15:01 | 3,437 | +7 |
| 3 Sept 2026, 01:53 | 3,430 | +10 |
| 30 Aug 2026, 18:28 | 3,420 | +8 |
| 27 Aug 2026, 08:58 | 3,412 | +7 |
| 24 Aug 2026, 16:58 | 3,405 | +9 |
| 21 Aug 2026, 10:33 | 3,396 | +9 |
| 18 Aug 2026, 12:36 | 3,387 | +7 |
| 15 Aug 2026, 10:48 | 3,380 | +14 |
| 12 Aug 2026, 04:48 | 3,366 | +16 |
| 6 Aug 2026, 04:46 | 3,350 | no change |
| 6 Aug 2026, 04:01 | 3,350 | first reading |
Engagement
20 posts held, back to 29 July 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 3 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 0s
- Average length
- 0s
Measured directly from 9 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
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 1 of the 20 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 20 most recent posts we hold, published 29 July 2026 to 31 July 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
《自然·通讯》研究借NODDI技术看清大脑微观布线:智商越高,皮层神经突密度越低、排列越规整,推翻“脑子越满越聪明”的直觉。这印证神经效率假说——智力拼的是信号传递效率而非堆料,高智商大脑经突触修剪“瘦身”,剔除冗余通路、保留核心高速链路,能耗更低、响应更快。宏观上高智商者皮层体积可能更大,但微观是“少而精”的稀疏化架构,这种精简布线才是高效信息处理的底层密码。
王虹得菲尔兹奖证伪二向箔? 刚看到一篇科普是王虹得菲尔兹奖的那个挂谷猜想证明了二向箔在物理世界不可能存在,理由是二向箔要剥离一个空间维度。王虹证明了测度为 0 的三维挂谷集的分形维度数不能小于 3。也相当于证明宇宙不会坍缩。
这次没别人,就陈震一个人在LA体验美版“软硬满血”Model Y=HW4.0后期+前杠摄像头硬件 × FSD V14.3.4,是北美无阉割端到端纯视觉顶配,感知与决策底座拉满,区别于国内保守监督版,说比他自己开得好,牛B 开Mad Max激进模式后变道超车果敢、无保护路口不拖泥带水,低速不抖、避让逆行货车/手推车像老司机主动倒让,拟人化与自信度远超普通人类道路驾驶,体验者直呼“惊艳”。 从加油站自动挂挡出发到终点自主找位泊入,近乎“车位到车位”全脱手;但仍是L2监督辅助、北美路况特化,不能等同Robotaxi无安全员,要担心的是“驾驶能力退化”隐忧
现在碰到好东西 我就扔给 fable 5,请参考这个把好的功能借鉴融合到我的系统里面
Agent 拿着密钥到处调工具,没人管它该不该做某件事。CyVisGuard 就在 Agent 和它要碰的东西之间插一层,每次调用都问一句:谁调的、替谁调的、还能不能继续。 https://github.com/flankerhqd/cyvisguard
数学家王虹 #菲尔兹奖 #王虹 #血染的风采 #beyond
药会自己变异?揭秘震惊世界的利托那韦之谜! #科普
MCP的商业化春天来了,MCP第五版2026-07-28发布了:MCP输出结果不再只是一段文字,而是能直接在对话里渲染出可交互的界。 除此之外还有一个更大的改动,从"有状态的双向连接"改成了"请求/响应"——这一下就能跑在 serverless 和边缘上了,这个版本的几个重要变化: ① 无状态内核(架构层最大的迭代) 协议从"双向有状态"改成"请求/响应"的无状态模型,这样 MCP 服务就能部署到 serverless 和边缘基础设施上,部署和扩容都简单了——这是从"长连接的巧妙管道"迈向"能规模化的生产基建"的关键。 ② 两个重要的扩展成官方标准 MCP Apps:服务器可以在对话里直接渲染可交互 UI——工具结果不再是纯文本块。 Tasks:不改核心协议就能跑长时间任务。 ③ 认证对齐企业生产级 授权向生产级 OAuth 2.0 / OIDC 看齐,MCP 服务器能接 Entra、Okta 这类企业身份系统。 Anthrop…
基于 rathole 和 Nginx 的多地点反向隧道编排系统,用一个域名、一个端口、一张证书即可将多个境外节点流量路由回境内。 https://github.com/loopy-iri/RatholeEngine
等离子静电造水机原理:无冷却结构也能凭空取水! #科普
美巨头谷歌、特斯拉宁可举债也要单季砸下数百亿美元All in AI与自动驾驶算力基建,其经营现金流规模是腾讯阿里的5倍,资源集中度远超国内企业将资金分散于外卖内卷的现状。 算力已成中美AI竞争核心短板,国内所有车企算力总和不及特斯拉一半,尽管大模型应用层差距不大,但底层硬件代差正不断拉大技术鸿沟。 特斯拉短期现金流承压致股价大跌属预期内阵痛,达拉斯无安全员Robotaxi落地印证技术领先,投资者宜忽略波动静待FSD全面商业化兑现。NFA
❤1
Showing the 12 most recent of 20 posts we hold for @deeptech123. 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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“黑科技资源分享” (@deeptech123), 3,471 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/deeptech123.
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.