Channel
@puddin_share
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
955subscribers
+23 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001639969676 |
|---|---|
| Type | Channel |
| Username | @puddin_share |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/puddin_share |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 17 Sept 2026, 06:59 | 955 | +1 |
| 8 Sept 2026, 06:56 | 954 | +13 |
| 29 Aug 2026, 03:35 | 941 | +4 |
| 21 Aug 2026, 03:07 | 937 | +1 |
| 14 Aug 2026, 22:05 | 936 | +5 |
| 7 Aug 2026, 13:20 | 931 | -1 |
| 6 Aug 2026, 14:48 | 932 | no change |
| 6 Aug 2026, 14:37 | 932 | first reading |
20 posts held, back to 31 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 1 page 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
TIL: (每日火星) DeepSeek API 早就提供了免费的 web search 接口: Responses API: https://api-docs.deepseek.com/zh-cn/guides/responses_api/#tools — web_search / web_search_2025_08_26 : 支持，服务端执行。 A\ API: https://api-docs.deepseek.com/zh-cn/guides/anthropic_api#message-fields — web_search_tool_result: Supported 使用的供应商应该是 https://open.bochaai.com/, 最终的数据上游依旧是万能的 Bing 相当于免费白嫖 ￥36/千次 的搜索 API, 梁圣的恩情还不完 ✋😭🤚 btw: 冷门 (?) 小知识, Kimi For …
前段时间我看到nginx的洞想的又是什么商业炒作。不过最近仔细看了下他们的工作，绝对不是普通研究员+大模型就能轻易做到。查看了成员发现他们拥有非常深厚的系统安全背景，并且在exp和工程上都做的非常强 https://www.ycombinator.com/companies/nebula-security https://www.usenix.org/conference/usenixsecurity22/presentation/zou https://blackhat.com/us-26/briefings/schedule/#prompt2own-real-world-kernel-exploit-development-with-llms-52528
不得不说大家的思路都是非常相似的…… https://kritt.ai/open-kritt-launch/
冷钱包攻击导致比特币被盗近 8900 万美元 #安全 硬件钱包本应是保存比特币最安全的地方：不联网、密钥不离设备，攻击者需物理接触才能盗取加密货币。Coinkite 制造的比特币硬件钱包 Coldcard 使用硬件随机数生成器产生 128 位熵值，这个数字是如此之大现有的计算能力无法破解。然而 2021 年 3 月的一次更新引入了严重 bug，默认的硬件随机数生成器被切换为软件随机数生成器，在 Mk3 设备上，有效搜索空间缩小到 40 位。128 位和 40 位之间的差异并是无法被打开的锁和可以被打开的锁之间的区别。攻击者可以租用云计算资源进行暴力破解，在无需接触硬件的情况下获得钱包的密钥。过去几天，攻击者从 4585 个地址窃取了 1367 个比特币，价值近 8900 万美元。Coinkite 已释出新固件，受影响用户需在更新后的硬件上生成全新钱包，将资金迁移至新钱包。 https://www.coindesk.com/te…
Sticker, posted without a caption
貌似是为数不多的能代表日本AI的成果
日本信创 AI，但基于国模 Kimi K2.6 微调 Sakana Namazu 是 Sakana AI 提供的专为日语设计的 LLM API。 基于开源模型，利用公司内部专有数据推进了对日语和日本业务语境的适应性调整，此外，还进行了针对特定话题的响应回避和输出偏差抑制的调优。 博客请看这里：https://sakana.ai/namazu-api 🐟 src https://x.com/SakanaAILabs/status/2084079157491998971
🤖 Qwen 发布 3.8-Max：2.4 万亿参数，首次开源 Max 级模型 通义千问团队今日正式发布 Qwen 3.8-Max，参数规模达 2.4 万亿（活跃参数 95B），成为 Qwen 家族迄今最强的模型，模型权重将于下周开源。这是 Qwen 首次对 Max 级别模型开放权重。 Qwen 3.8-Max 基于 Qwen 3.5 架构，在编码、工作、研究和长周期任务方面全面提升。在编码测试中，模型可自主运行超 10 天完成项目构建与自我进化，并在 24 小时内参加 WWW2025 多模态对话意图识别竞赛，击败了 526 支队伍中的 458 支。模型现已通过 QwenCloud 提供 API 服务。 Qwen 🌸 在花频道 · 茶馆水群 · 投稿通道
https://mp.weixin.qq.com/s/AkEBNWuw-nGK1he3cQWrxA
Chrome近期3个版本修复1,442个漏洞 比之前23个版本修复的漏洞总和还多😬😬（作者：sasser） 谷歌透露 Chrome 近期 3 个版本合计修复 1,442 个漏洞，比之前 23 个版本修复的漏洞总和还多。具体来说在 6 月发布的 149/150 版中谷歌修复 1,072 个漏洞，而 126~148 合计修复的漏洞都没超过 1,000 个。如此快的漏洞发掘速度自然是靠 AI 实现的，无论是谷歌还是安全公司现在都在积极使用 AI 发掘漏洞。
Sticker, posted without a caption
太vibe了
Showing the 12 most recent of 20 posts we hold for @puddin_share. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Puddin在TG上看到了啥” (@puddin_share), 955 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/puddin_share.
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.