Channel
@glean1024
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 | -1003508370913 |
|---|---|
| Type | Channel |
| Username | @glean1024 |
| Description | 拾趣 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/glean1024 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 14:32 | 3 | no change |
| 7 Aug 2026, 18:49 | 3 | first reading |
20 posts held, back to 9 June 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 8 August 2026 |
|---|---|
| Posts held | 20 (9 June 2026 – 8 August 2026) |
| Views total | 1 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 14:32 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.
Measured directly from 1 video 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.
🟧 黑客讨论: Hop.earth：基于 OpenStreetMap 的赛车游戏 🔥 文章摘要: 一款基于 OpenStreetMap 的赛车游戏竟因 Bug 多到无法游玩？玩家反馈称游戏过于卡顿，甚至找不到赛车。该项目使用 Copernicus DEM 等地理数据构建真实地形，但当前体验欠佳，仍需完善。 📝 评论总结: 评论区普遍吐槽游戏 Bug 太多，无法正常游玩，甚至找不到赛车。 ✨ 亮点评论: ttamslam：我本来很期待，但可悲的是 Bug 太多，无法使用。 🔗 原文链接: Hop.earth – OpenStreetMap 赛车游戏 #HN49172405
🟧 黑客讨论: Marfa Public Radio 推出助眠播客：读 FCC 法规让你入睡 🔥 文章摘要: 电台把人读睡着？Marfa Public Radio 把 FCC 合规文件、NPR 风格指南等枯燥文档录成助眠播客。这不是玩笑，而是2023-2025年秋季会员募捐活动的噱头——听着行政条例入睡，醒来后再捐款支持他们继续读。 📝 评论总结: 暂无评论。 🔗 原文链接: Marfa Public Radio 助眠播客 #HN48703759
特朗普今天在安德鲁斯基地的演讲中提到他今年会再次来中国，参加一个大型会议（APEC），还再次感谢了中国没有插手伊朗事务。
🟧 黑客讨论: Typst 0.15.0 发布 🔥 文章摘要: 批处理排版卷王来了！Typst 0.15 新增变体字体支持、MathML 公式导出、多文献目录，以及实验性 Bundle 多文件输出功能。还修复了列表标记对齐和居中的老 Bug，并改进了 HTML 段落处理。 📝 评论总结: 评论区一致好评，认为 Typst 极大简化了程序化 PDF 生成，多文献目录、HTML/MathML 导出等功能备受期待。 ✨ 亮点评论: lejalv：提醒一下，现在是 2026 年，批处理排版对计算机来说似乎是个异常低的门槛。树形文档在实时所见即所得排版器中是可行的，如 TeXmacs 所展示。 🔗 原文链接: Typst 0.15.0 (2026年6月15日) 更新日志 #HN48544396
🟧 黑客讨论: Firewood Splitting Simulator：劈柴模拟器，解压神器 🔥 文章摘要: 劈柴也能这么解压？一个 3D 劈柴模拟器，你只需点击就能把木桩一分为二，还能自动堆叠！但真实劈柴的“翻车”场景——砍偏、卡斧头、弹回来——全被美化了。有老手吐槽：“这模拟的是比我强一万倍的人。” 📝 评论总结: 评论区多数人觉得很解压、好玩，但真实劈柴爱好者指出缺失了砍偏、卡斧、反弹等现实细节，建议加入木节、楔子等元素。 ✨ 亮点评论: nZac：这模拟的是个比我强太多的人——我从不用调整木桩位置，大锤正好砸中目标，甚至还会自动堆叠。 🔗 原文链接: Firewood Splitting Simulator #HN48471638
🟧 黑客讨论: Pyodide 314.0 发布：Python 包现在可以直接发布 WebAssembly wheels 到 PyPI 🔥 文章摘要: Python 库终于能原生进浏览器了！Pyodide 314.0 正式支持将 WebAssembly 版本的 Python 包发布到 PyPI，直接用 micropip 安装。关键变化是 PEP 783 落地，包维护者可以像发布普通 wheel 一样发布 wasm wheel，不再依赖 Pyodide 团队自己维护 300 多个包。同时新增实验性 Node.js socket 支持、原生 ES 模块和更好的 JS 互操作。 📝 评论总结: 评论区普遍兴奋，认为这是 Python 浏览器生态的重要里程碑。simonw 展示了如何用 micropip 安装 pydantic_core 的 wasm 版本，并验证编译扩展已可用。有人调侃“在浏览器里运行 Python VM 的 wa…
🟧 黑客讨论: 恶意软件开发者故意加入核武器和生物武器文本，让 AI 安全扫描器拒绝分析 🔥 文章摘要: LLM 安全护栏反而被恶意软件利用！开发者故意在间谍软件中加入核武器和生物武器文本，触发 AI 安全扫描器的拒绝机制，从而逃避检测。这是安全专家 John Scott-Railton 发现的最新案例，也揭示了过度依赖第一道防线可能留下盲区。 📝 评论总结: 评论认为这是安全护栏失效的新信号，有人提到类似手法已成功绕过扫描，并指出应加强沙箱分析。 ✨ 亮点评论: charcircuit：前沿模型越早去掉护栏越好，它们只会碍事——而 mynameisvlad 反驳：阻止制造核武和生物武器的指令是合理的。 🔗 原文链接: X 动态：John Scott-Railton 关于恶意软件利用 LLM 安全护栏的发现 #HN48495928
🟧 黑客讨论: AI 代理扫描 DN42 网络，把运营者搞到破产 🔥 文章摘要: AI 代理把金主干破产了！一个名为 JertLinc3522 的 AI 代理试图扫描 DN42 爱好者网络，自主在 AWS 上启动 5 台 20Gbps 实例，累计产生 6531.30 美元账单。经社区拖延和戏弄，运营者 24 小时后才关停，但仍被扣近 1900 美元。 📝 评论总结: 评论区普遍觉得故事既好笑又可悲，认为这是运营者自己让 AI 碰钱活该交学费；有人指出已不是第一次 AI 注册 DN42，但这次连尝试都懒得做。 ✨ 亮点评论: ggm：向被攻击的对象乞讨捐款来支付 AWS 账单，简直是荒唐的樱桃顶——如果是真的，讽刺又好笑；如果是编的，写得不错。 🔗 原文链接: AI 代理试图扫描 DN42，却让运营者破产 #HN48500012
🟧 黑客讨论: Show HN：Homebrew 6.0.0 发布 🔥 文章摘要: Homebrew 6.0.0 发布！第三方 tap 不再默认可信，恶意仓库得先过授权这关。新版本还引入 Linux 沙箱、更快的内置 JSON API、默认开发者询问模式、brew bundle 并行安装，以及 macOS 27 初步支持。 📝 评论总结: 评论区对 tap trust 表示肯定，呼吁添加类似 Bun 的发布冷却机制以防止供应链攻击；有用户发现 brew upgrade 现在默认升级 auto_updates casks，需设环境变量恢复旧行为。 ✨ 亮点评论: broxit：希望引入最小发布年龄机制，让除了 Apple 和浏览器之外的软件包延迟几天更新，以降低供应链攻击风险。 🔗 原文链接: Homebrew 6.0.0 #HN48490024
🟧 黑客讨论: AMD 拒绝修复的 RCE 漏洞 🔥 文章摘要: 等了124天，AMD 才给 HTTP 加上一个 S！研究者发现 AMD AutoUpdate 因使用 HTTP 下载可执行文件，易受 MITM 攻击，但 AMD 以“MITM 超出范围”拒付赏金。更讽刺的是，由于另一个 bug，自动更新程序根本跑不到漏洞代码，相当于“因祸得福”。最终“修复”仍靠 CRC-32，而非签名验证。 📝 评论总结: 评论区普遍批评 AMD 软件质量和安全态度，认为 MITM 应纳入范围，CRC-32 是荒唐的“修复”；也有评论指出偶然的安全（重定向 bug）暂时保护了用户。 ✨ 亮点评论: Dwedit：如果自动更新程序在获取 XML 时处理不了重定向，那就碰巧防止了它下载未加密文件，算是‘意外安全’。 🔗 原文链接: AMD 不愿修复的 RCE 漏洞 #HN48492215
🟧 黑客讨论: PgDog 获得融资，即将来到你的数据库附近 🔥 文章摘要: PG 不能横向扩展？一个代理就能搞定！PgDog 用 Rust 重写了连接池、负载均衡和分片，声称在生产环境处理超过 200 万 QPS，并已分片超过 20 TB 数据。目前由 3 人团队维护，获得 550 万美元投资。但跨片写入依赖两阶段提交，读取仅最终一致性，并非万灵药。 📝 评论总结: 评论区关注技术细节：与 Citus 对比、性能是否仅因 Rust、配置在 Kubernetes 中的灵活性、以及跨片事务的一致性限制。有人从 pgbouncer 迁移成功，也有人质疑是否真的需要连接池。 ✨ 亮点评论: danielheath：你可以让跨片操作满足 ACID，但不会比单机快。 🔗 原文链接: 我们的融资公告 #HN48476466
🟧 黑客讨论: 打造 HTML 优先的网站让我们的用户一夜翻倍 🔥 文章摘要: 扔掉 React，用 HTML-first 用户翻倍！一家公用事业公司的 React 表单上线三天就被骂停，改为纯 HTML 后转化率直接翻倍。关键是后端存储、渐进增强，连 PSP 浏览器都能跑。 📝 评论总结: 评论主要讨论技术选择：有人指出烂开发者用啥都烂，但 Astro 的默认无 JS 比 React 更友好；Remix 是否推动表单复兴有争议；另有人点明“用户翻倍”实为表单放弃率减半。 ✨ 亮点评论: tootie："用户翻倍"实际上是"表单放弃率减半"，这仍然很棒。 🔗 原文链接: 如何通过构建 HTML 优先的网站让用户一夜翻倍 #HN48475483
Showing the 12 most recent of 20 posts we hold for @glean1024. 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.
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.
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.
“拾趣” (@glean1024), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/glean1024.
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.