Telegram RegisterThe public register of Telegram
Telegram profile photo for 技术拾荒者

Channel

技术拾荒者

@tech_scavenger

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

457subscribers

+19 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003681261276
TypeChannel
Username@tech_scavenger
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live6 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 6 October 2026
On Telegramt.me/tech_scavenger

Topic

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

438463450.57 August 2026 — 438 subscribers8 August 2026 — 438 subscribers15 August 2026 — 447 subscribers21 August 2026 — 455 subscribers28 August 2026 — 460 subscribers4 September 2026 — 461 subscribers12 September 2026 — 463 subscribers6 October 2026 — 457 subscribers4577 August 20266 October 2026
8 measurements spanning 59 days, net +19. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 434–467 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Oct 2026, 09:36457-6
12 Sept 2026, 23:01463+2
4 Sept 2026, 15:20461+1
28 Aug 2026, 13:44460+5
21 Aug 2026, 10:37455+8
15 Aug 2026, 04:09447+9
8 Aug 2026, 05:16438no change
7 Aug 2026, 23:48438first reading

Engagement

20 posts held, back to 30 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 01:30 UTC9 viewsread 8 August 2026

开源 kkRepo v0.7.0 发布,平替 Nexus 的制品仓库,新增企业级的制品清理策略+安全扫描策略功能支持 旨在解决 Sonatype Nexus 社区版的各类限制与痛点,为社区提供开放、可靠且可持续演进的制品管理方案。 支持 AOT 编译运行,约 1 秒启动就绪,内存占用低于 200 MB 。 支持 16+ 种主流仓库格式,覆盖 hosted、proxy 和 group 仓库管理。 阅读全文 · V2EX-programmer

7 Aug 2026, 05:30 UTC32 viewsread 8 August 2026

前端转 AI 全栈,到底应该按什么顺序学? 传统前端边界被拉开,工程师还要补上大模型调用、逻辑编排和服务端对接。 Next.js 团队在 2026 年发布了 Building Next.js for an agentic future,明确提出要把 Coding Agent 当成框架的一等用户。 前端框架正在同时服务人类开发者和 Coding Agent。 阅读全文 · V2EX-programmer

7 Aug 2026, 01:30 UTC41 viewsread 8 August 2026

烧了 6B+ token,分享下我实践出来最好的 AGENTS.md Opus 4.7 经常在对话中突然切换成英文; Opus 4.8 经常任务做到一半就停下来; 一旦任务持续时间超过 4 小时,就容易出现类似早期 LLM 的“上下文焦虑”,很难稳定地把长任务做到底。 始终使用简体中文回答,代码、命令、专有名词和用户明确要求保留的原文除外。 阅读全文 · V2EX-create

6 Aug 2026, 05:30 UTC52 viewsread 8 August 2026

没有后端的产品怎么做付费墙? 因为不想为了收费加一台后台服务器,怎么验证用户的 license 就成了问题。 我的想法:用 Ed25519 签一段 payload (订单号、有效期、买家名字),公钥编译进前端 bundle ,浏览器里 WebCrypto 离线验签。不联网、不绑设备、不做撤销。 阅读全文 · V2EX-programmer

6 Aug 2026, 01:30 UTC50 viewsread 8 August 2026

当我们在和 AI 谈人天时,我们在谈什么 我下午四点才介入。 我就随口跟 codex 讲,评估一下,先给方案,超过 2 人天的话就延期发布。 接着它就带着我刚刚提及的另外一个小改动,一口气把小改动和这个 1.5 人天的内容都写完了。 阅读全文 · V2EX-programmer

5 Aug 2026, 05:30 UTC60 viewsread 8 August 2026

记录自己作为业余编程爱好者的 10 年 公司业务缩水,员工减半,我的收入减半,慌了,有点焦虑。 凭借自己的编程基础,开发了一些裂变页面、公众号邀请海报、为吸粉提供了非常关键的技术支持。 阅读全文 · V2EX-programmer

5 Aug 2026, 01:30 UTC59 viewsread 8 August 2026

「听记」一款免费的 AI 会议录音软件 修复了部分转写显示异常、播放定位不准确等问题。 上个月在 V 站分享我个人开发的 AI 录音工具后,收到一些反馈。 可以点击文字快速跳转到对应录音位置,播放时也会自动跟随当前段落。 阅读全文 · V2EX-programmer

4 Aug 2026, 05:30 UTC61 viewsread 8 August 2026

coding agent 的 5 个回合 vs 1 次 command_run:完整例子 真正的额外成本,不只是這些命令,而是模型醒來 5 次,並且每次都要重新读取越来越长的對話。 不要讓模型在可预测的每一步都重新醒來。 阅读全文 · V2EX-programmer

4 Aug 2026, 01:30 UTC56 viewsread 8 August 2026

极致精简,已经优化为仅 100 多 KB!单文件 PHP 论坛! 可选功能全部以插件的形式提供,由用户自由选择搭配。 一个极简 PHP 论坛。 阅读全文 · V2EX-programmer

3 Aug 2026, 09:30 UTC63 viewsread 8 August 2026

用了大半年 AI 工具,说说哪些真提效、哪些是智商税 大部分 AI PPT 工具都挺智商税的。我测了快 20 款,能用的就两三个,大部分生成的 PPT 排版丑、逻辑乱,改的时间比自己重做还长。 我买了 ChatGPT Plus 三个月,最后退了。不是因为不好,而是日常需求——改文案、翻译、查资料、写邮件——免费版完全够。 Kimi 是中文长文本王者。 丢一份 200 页的 PDF 进去让它总结,这是我最常用的场景,效果比其他国产的好。 阅读全文 · V2EX-programmer

3 Aug 2026, 05:30 UTC63 viewsread 8 August 2026

让 Windows 也能无缝连接 HomePod:全新 AirPlay 2 音频串流工具 WinAirCast 很多用户不得不去寻找第三方的音频串流软件(例如 TuneBlade 或 AirParrot)。但在实际体验中,这些老牌软件往往存在一些明显的短板: 高延迟:传统的缓冲机制导致看视频时容易出现声画不同步。 打开 WinAirCast,网络中的全部 AirPlay 接收器(无论是 HomePod、Apple TV,还是支持 AirPlay 1 的早期 AirPort Express)都会集中呈现在同一个设。 我们使用 Rust 语言从零重写了底层协议栈,推出了一款原生支持 AirPlay 2、向下兼容 AirPlay 1 的低延迟音频串流工具 —— WinAirCast。 阅读全文 · 少数派 -- Matrix

3 Aug 2026, 01:30 UTC63 viewsread 8 August 2026

分享最近做的一个免费截图工具 这是一款约 4 MB 的免费截图工具,支持截图标注、OCR、滚动截图和剪贴板历史。 作者做它的原因也很简单:不想每次截图都先找手机、再启动微信。 打开原文 · V2EX-programmer

Showing the 12 most recent of 20 posts we hold for @tech_scavenger. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.

“技术拾荒者” (@tech_scavenger), 457 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/tech_scavenger.

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.