Channel
@LoopDNSPODT
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
3subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003842694850 |
|---|---|
| Type | Channel |
| Username | @LoopDNSPODT |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/LoopDNSPODT |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 15:03 | 3 | no change |
| 7 Aug 2026, 18:52 | 3 | first reading |
20 posts held, back to 11 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 1 pageof 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 13 August 2026 |
|---|---|
| Posts held | 20 (11 August 2026 – 13 August 2026) |
| Views total | 20 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 15:03 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 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
DeepSeek 开源 DeepSeek Harness，进入开发者预览 DeepSeek 正式公开自研 Agent Harness「DeepSeek Harness（dsh）」代码，目前处于 Developer Preview 阶段，并采用 MIT 许可证开源。官方同时提醒，该项目仍在快速迭代，后续可能出现破坏兼容性的更新。 DeepSeek Harness 定位为通用 Agent 运行框架。其底层基于 Cordis，采用高度插件化架构，包括模型适配器、工具注册、会话日志和 Agent Loop 在内的核心组件均可替换或扩展。官方提供 Web UI 与 Headless 等运行方式，并支持工作区文件读写、命令执行、任务规划、子 Agent 委派以及权限审批。 此前 DeepSeek 已在 V4-Flash 的官方更新中披露，其 Code Agent 公开基准测试使用 DeepSeek Harness minimal mo…
DeepSeek V4 Pro 正式版上线，重点强化 Agent 能力 2026 年 8 月 13 日，DeepSeek 正式发布 DeepSeek V4 Pro 正式版，模型版本更新为 DeepSeek-V4-Pro-0813。目前已同步上线 DeepSeek App、网页端和 API，网页及 App 用户可通过“专家模式”使用。API 原有 deepseek-v4-pro 模型名保持不变，将自动指向新版本。 本次更新重点提升 Agent 能力。DeepSeek 表示，新模型在实际生产环境中的表现有明显改善。API 同时原生支持 Responses API、Tool Calls 和 Anthropic API，并针对 Codex 等 Agent 工具进行了适配。V4 Pro 支持 low、high、max 三档思考强度，默认开启思考模式并使用 high。 模型继续提供 1M Token 上下文，单次最大输出为 384K T…
File, posted without a caption
deepseek v4pro上新？
xAI 发布 Grok 4.6，强化长程 Agent 与交互式开发能力 2026 年 8 月 12 日，xAI 正式发布 Grok 4.6。新模型在 Grok 4.5 基础上继续强化长时间运行的 Agent、复杂多步骤任务，以及交互式和视觉应用开发能力。xAI 称其可持续完成研究、信息分析、大型代码库操作以及从想法到完整应用的开发流程。 训练方面，Grok 4.6 进行了比 4.5 更长的补充训练，并加入模型生成的推理与技术数据、高质量工程数据，同时更新优化器和训练方法。后续 SFT 数据由 Grok 4.5 重新生成，并在知识工作、通用编程、Kernel 优化、Web 开发和 CAD 等环境中进行了 Agentic RL。 在 xAI 公布的评测中，Grok 4.6 High 的 Artificial Analysis Intelligence Index 得分为 61，与 GPT-5.6 Sol Max 持平；Curso…
‼️huge ssi news. ilya is about to take his first tentative steps out of the age of research and back into the age of scale. it’s time to smell what ssi is cooking. ssi have built a small reasoning engine that can compete with much larger training runs because his data is better curated to meta learning. but, more importantly. we’re about to step into the era of TTT (test time training. gradient descent happening i…
【慢讯】OpenAI 扩展 Daybreak，推出 GPT-5.6-Cyber OpenAI 于 8 月 10 日宣布扩展网络安全项目 Daybreak，将其划分为 Blue 与 Red 两个访问级别，并推出针对高级网络安全任务训练的 GPT-5.6-Cyber。Daybreak Red 主要面向经过审核的漏洞研究人员和红队团队，可用于漏洞发现、利用验证与高级安全测试。 GPT-5.6-Cyber 基于 GPT-5.6 Sol，在零日漏洞发现和漏洞利用链开发等任务上进行了专项训练。OpenAI 的内部测试显示，其高级网络安全请求完成率达到 95.0%。OpenAI 还使用该模型研究 Chrome 的 V8 引擎，发现两个此前未知的漏洞，其中一个已被 Google 修复并编号为 CVE-2026-15903。 OpenAI 将 GPT-5.6-Cyber 的网络安全能力评定为 “High”，尚未达到 Preparedness…
中共中央 全国人大常委会 国务院 全国政协讣告 朱镕基同志逝世 中国共产党中央委员会、中华人民共和国全国人民代表大会常务委员会、中华人民共和国国务院、中国人民政治协商会议全国委员会沉痛宣告：中国共产党的优秀党员，久经考验的忠诚的共产主义战士，杰出的无产阶级革命家、政治家，党和国家的卓越领导人，中国共产党第十四届、十五届中央政治局常委，国务院原总理朱镕基同志，因病医治无效，于2026年8月12日11时06分在北京逝世，享年98岁。
腾讯控股公告，第二季度资本支出527.8亿元人民币，市场预估321.4亿元人民币。
美伊同意延长60天停火期限，8月17日到期前达成共识 巴基斯坦政府消息人士周三告诉阿纳多卢通讯社，美国和伊朗已“同意”延长根据《伊斯兰堡谅解备忘录》达成的60天停火协议。该协议将于8月17日到期。 一名熟悉调解进程的消息人士表示：“双方已向调解方传达了同意延长最后期限的意愿。” 该消息人士补充说：“不过，双方仍在通过信息往来，就延长多长时间进行磋商。” 来源：Anadolu Ajansı
Lumentum Q4 FY26 Earnings
Docker 高危漏洞“CopyEscape”公开：docker cp 可越界写入宿主机 安全公司 Imperva 公开了 Docker 漏洞 CVE-2026-17106，代号“CopyEscape”。GitHub 将其评级为 High，CVSS v4 评分 7.1。漏洞存在于 Docker 文件复制与归档解压流程中，攻击者控制的容器可构造恶意归档，使 docker cp 在从容器向外复制文件时突破用户指定的目标目录，在宿主机上创建或覆盖文件。 该漏洞并不能让恶意容器在运行后自动逃逸，利用过程需要用户或自动化系统对攻击者控制的容器执行 docker cp。成功利用后的权限取决于 Docker CLI 本身：普通用户执行时可覆盖该账户有权写入的文件；如果 Linux 上的 CI、运维任务或管理员以高权限执行复制，则可能进一步实现 root 级代码执行。Imperva 已在 Linux Docker Engine 29.6.1…
Showing the 12 most recent of 20 posts we hold for @LoopDNSPODT. 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“LoopDNS资讯播报” (@LoopDNSPODT), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/LoopDNSPODT.
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.