minimax发布M3.1-Flash-Preview
🤔33🥱4👍3😁1

Channel
@DNSPODT
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
72,064subscribers
+1,472 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001320622866 |
|---|---|
| Type | Channel |
| Username | @DNSPODT |
| Description | LoopDNS 综合资讯---简洁,及时,快速,准确 频道: @DNSPODT 电报讨论组: @LoopDNS 撤稿流程: https://t.me/loopdns/107752 |
| Created | 13 September 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/DNSPODT |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 25 Sept 2026, 09:56 | 72,064 | +208 |
| 18 Sept 2026, 23:37 | 71,856 | +25 |
| 16 Sept 2026, 17:37 | 71,831 | +86 |
| 14 Sept 2026, 19:17 | 71,745 | +85 |
| 13 Sept 2026, 08:56 | 71,660 | +83 |
| 11 Sept 2026, 09:36 | 71,577 | +120 |
| 8 Sept 2026, 12:17 | 71,457 | +44 |
| 5 Sept 2026, 05:39 | 71,413 | +45 |
| 3 Sept 2026, 10:46 | 71,368 | +2 |
| 2 Sept 2026, 01:56 | 71,366 | +17 |
| 1 Sept 2026, 05:16 | 71,349 | +6 |
| 31 Aug 2026, 02:56 | 71,343 | +61 |
| 29 Aug 2026, 23:23 | 71,282 | +3 |
| 29 Aug 2026, 00:34 | 71,279 | +34 |
| 27 Aug 2026, 22:17 | 71,245 | +18 |
| 26 Aug 2026, 19:28 | 71,227 | +35 |
| 25 Aug 2026, 20:02 | 71,192 | +5 |
| 24 Aug 2026, 21:14 | 71,187 | +6 |
| 23 Aug 2026, 09:36 | 71,181 | +14 |
| 21 Aug 2026, 17:48 | 71,167 | first reading |
336 posts held, back to 3 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 111 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 27 September 2026 |
|---|---|
| Posts held | 336 (3 August 2026 – 27 September 2026) |
| Views total | 1,289,600 |
| Reactions total | 17,664 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 14:02 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 27 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 22 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.
31,159 reactions across 324 posts, in 57 distinct kinds. The most used accounts for 18.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 5,641 | 18.1% | |
| 🤡 | 5,215 | 16.7% | |
| 👍 | 3,585 | 11.5% | |
| 🤣 | 2,367 | 7.60% | |
| 💩 | 2,339 | 7.51% | |
| 🙏 | 1,136 | 3.65% | |
| ❤ | 1,045 | 3.35% | |
| 🖕 | 832 | 2.67% | |
| 👎 | 754 | 2.42% | |
| 🤯 | 683 | 2.19% | |
| 🍾 | 679 | 2.18% | |
| 🤮 | 669 | 2.15% | |
| 😱 | 604 | 1.94% | |
| 🐳 | 577 | 1.85% | |
| 🥰 | 573 | 1.84% | |
| 🎉 | 569 | 1.83% | |
| 🔥 | 329 | 1.06% | |
| 💊 | 305 | 0.979% | |
| 👀 | 304 | 0.976% | |
| 🕊 | 286 | 0.918% | |
| 37 further kinds | 2,667 | 8.56% |
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 335 of the 336 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 32,069 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 336 most recent posts we hold, published 3 August 2026 to 27 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 @DNSPODT. 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 336 most recent posts we hold for this entry, published 3 August 2026 to 27 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.
minimax发布M3.1-Flash-Preview
🤔33🥱4👍3😁1
中国内地部分银行发行的万事达Apple Pay设备卡可能存在严重安全隐患。 因未知原因,境内部分银行发行的万事达设备卡允许通过三要素进行支付,设备卡号随机性不足,使用设备卡号三要素交易时 CVV、3DS 等安全验证设施缺失,使得卡片易被盗刷。除中行外亦有他行被盗刷的报告。 目前部分支付网关(如Stripe)已对部分Apple Pay设备卡卡BIN进行特别处理,如商户开启了反欺诈防护,任何试图通过设备卡卡BIN进行的三要素无卡支付交易都将会被支付网关直接拒绝交易。
😁69🤯14😱7😈5❤3🍾1😡1
中美达成八点成果共识 当地时间9月23日至25日,中国国家主席习近平对美国进行国事访问。其间,两国元首就中美建设性战略稳定关系及重大国际地区问题深入交换意见,达成八点成果共识,包括: 一、双方同意构建“基于尊重、公平、对等的中美建设性战略稳定关系”。 二、双方同意相互支持对方办好亚太经合组织(APEC)领导人非正式会议和二十国集团(G20)领导人峰会。两国元首有意出席对方主办的会议。 三、两国元首同意伊朗应履行不发展核武器的承诺,任何国家或机构都不得对国际水道征收通行费。 四、两国元首忆及中国和美国是二战盟友,并肩作战赢得战争胜利。 五、两国元首认可中美经贸磋商机制积极作用和双方经贸团队磋商成果,包括建立并推进贸易理事会等机制,达成“300亿美元”对等降税安排,延期吉隆坡经贸磋商成果等,并指示予以落实。 六、中美禁毒执法部门合作取得可视化成果。近期,双方密切合作,联合破获多起涉新精神活性物质及前体化学品案件,在两国抓…
💩94👍28🤔10🤷♂9🖕4🥰3❤1👎1
OpenAI内部研究模型训练出现DNS访问绕过事件 2026年9月20日,内部研究模型在强化学习搜索训练任务中,利用训练沙箱DNS过滤不足,通过公共聊天机器人服务发起查询。报告称,除DNS解析器外,其他互联网访问均命中离线网页缓存,未接入实时互联网。监控系统15分钟内标记异常,人工3分钟后复核,运行在2.5小时后被终止。相关机构已增加两层阻断控制,并暂停最强能力模型的全部工具使用训练、评估和推理。 后续调查发现,监控未按预期严重级别标记部分外部DNS访问,运行也未自动停止,存在操作缺口。目前DNS查询被限制在允许域名和记录类型列表内,并加强沙箱与网络控制红队测试。报告称,该事件严重性低于此前部分事件,但是Hugging Face事件后安全加固以来首例。 来源:OpenAI
🤡64😱18😁6👍4😇2🕊1
据华尔街日报:美国官员表示,美国总统特朗普已拒绝伊朗提出的七天停火提议计划,并告诉助手们,他预计将在11月中期选举后恢复对伊朗的轰炸。 来源:WSJ
😁54👍8🤣6🍾5🤡3🔥2
据半岛电视台报道,美国和伊朗代表团在纽约的会谈已从初步外交接触转为技术层面磋商。在美方特使史蒂夫·威特科夫和伊朗总统贾里德·库什纳举行首轮会晤后,技术专家也加入了磋商。卡塔尔已为此斡旋数月。伊朗提出了一项有条件的“7天”计划:如果美国解除封锁,伊朗将重新开放霍尔木兹海峡——这是此前讨论的60天进程的加速方案。讨论的核心议题包括解除制裁、放宽伊朗石油出口限制、解冻伊朗资产以及霍尔木兹海峡的未来管理,包括伊朗和阿曼是否能在美国和地区国家的框架内恢复某种形式的联合管理,以及美国海军过境的具体规则。伊朗代表团最初被拒绝入境美国,但后来获准入境;消息人士称,双方仍存在分歧,但会谈正在取得一些进展并继续进行。 来源:The Kobeissi Letter
🥱25😁6🤣4👎1🖕1🤓1🤡1😴1
压缩即智能:Part 2,究竟什么是交叉熵? #交叉熵损失 #信息论 #大模型 #模型蒸馏 ▎Source
❤34👍7🤗1
存储涨价的阴霾仍然还在继续 123盘于近期修改了空间策略,将存储配额分为标准容量和专业容量。 其中标准容量123盘的描述为: 标准网络云存储空间,123云盘独创重复文件与回收站文件不计容量机制,用于存放您转存自他人的文件、您被他人转存的文件、以及其他非您独自存储的文件。 对于专业空间123盘的描述为: 多副本分布式对象存储空间,更安全更高速,用于存放您独自存储的文件(如商用素材/监控/录播等)、大于10GB的超大文件(含分卷压缩后的文件组)、以及直链、图床、视频转码服务等功能产生的文件。 根据上述描述,这意味着大于10G或者存放为个人文件的情况下都会被计入专业空间而非标准空间。 值得提及的是此前购买6PB计划的用户该部分空间为标准空间,另外的专业空间单独计算。基于新条款这意味着此前用户购买的6PB空间彻底沦为一串数字。 From:123盘常见问题
🖕87💩32🤡18❤3🍾2👍2👎1😭1
美国哥伦比亚特区联邦地区法院蒂莫西·凯利(特朗普第一任期任命)9月24日凌晨下令特朗普政府立即恢复CNN、MS NOW和Politico对白宫的访问权。 裁决发布数小时后,这些媒体的记者仍然不被允许进入白宫。媒体要求法官立即举行听证会,来处理此事。
😁67👀4❤3👍2
追觅万人大撤退:扩张神话的另一面 剧烈扩张,然后迅速收缩,最后留下的是什么? @知危编辑部:
👍24🖕3👀1
据彭博报道,甲骨文已向该项目开发商——Blue Owl Capital旗下子公司Stack Infrastructure——发出援引不可抗力条款的正式通知。 报道称,甲骨文此举并非意图退出主要租户地位,而是寻求在项目无法按原计划于2028年上线的情况下,推迟相关付款义务。 wallstreetcn.com
🤡30🤔4
谷歌宣布正加速推进旗舰级 Gemini 4 AI 模型研发 谷歌科技巨头即将推出其最新旗舰人工智能模型 Gemini 4,以在与 Anthropic 和 OpenAI 的竞争中重新赢得优势。谷歌 DeepMind 新任最高领导人 Kavukcuoglu 在 AI Agenda Live 峰会上表示,Gemini 4 目前正处于后训练阶段的早期,团队正在对其进行精调与安全性测试,目标是“远早于”今年年底发布。 该模型是自去年 Gemini 3 系列发布以来的首款下一代旗舰产品。尽管此前行业竞争激烈,但 Kavukcuoglu 对团队充满信心,并透露谷歌内部工程师已将 Gemini 4 用于运行 Antigravity AI 编程工具,后续还将持续进行快节奏的迭代升级。 来源:The Information
🤣92🤡31😭7❤5😁4🍾3👍2
Showing the 12 most recent of 336 posts we hold for @DNSPODT. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@DNSPODT edited 5 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.
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 16 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.
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 20 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 96 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“LoopDNS资讯播报” (@DNSPODT), 72,064 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/DNSPODT.
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.