19 Jan 2026, 11:41 UTC113 viewsread 10 August 2026
60,000+ 代理技能供你使用的 AI 构建 我们分享了超过 60,000 个代理技能的超强合集——这是提升你的 AI 构建的完美方式。 兼容 Claude Code、Visual Studio Code 和 Antigravity。升级所需的一切尽在此处！
Channel
VibecodingCN
@vibecodingCN
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
38subscribers
-5 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002547262755 |
|---|---|
| Type | Channel |
| Username | @vibecodingCN |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/vibecodingCN |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 15:25 | 38 | -1 |
| 17 Aug 2026, 09:39 | 39 | -4 |
| 10 Aug 2026, 16:45 | 43 | no change |
| 9 Aug 2026, 04:45 | 43 | first reading |
Engagement
20 posts held, back to 18 January 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.
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 19 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 57s
- Average length
- 11s
Measured directly from 5 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.
Recent posts
19 Jan 2026, 11:41 UTC110 viewsread 10 August 2026
Photo
Photo, posted without a caption
19 Jan 2026, 08:34 UTC99 viewsread 10 August 2026
Photo
Photo, posted without a caption
19 Jan 2026, 08:34 UTC105 viewsread 10 August 2026
关于优化 React 和 Next.js 的指南现在可以直接在 Claude Code 中使用 Vercel 发布了一个详细的技能，用于优化 React 和 Next.js 的性能 — 只需几次点击即可连接！ 该怎么做： 1. 在终端中输入 npx claude-code-templates@latest --skill=web-development/react-best-practices --yes 2. 输入 /react-best-practices，技能将直接在您的项目中启动。 接下来 — 您可以继续自己编码，或者观察 Claude 为您完成编码 😄
19 Jan 2026, 05:28 UTC79 viewsread 10 August 2026
Photo
Photo, posted without a caption
19 Jan 2026, 05:28 UTC88 viewsread 10 August 2026
AI 一周内写出浏览器——这现在成真了 我偶然发现了一个非常有趣的案例：开发者们通过 GPT-5.2 在 Cursor 中直接创建了一个新的浏览器，仅用了一周的时间，让 AI 不停地工作。这可不是“晚间实验”——这里有超过 300 万行代码和成千上万的文件！ 特别酷的是：整个渲染引擎都是用 Rust 从头开始编写的。内部完整地运作着一条管线——HTML 解析、CSS 样式表、布局、文本渲染、绘制，甚至还有自己的 JS 引擎。 当然，结果远不及 WebKit 或 Chromium：bug 很多，复杂的网站可能会崩溃。但是简单的页面渲染速度很快，外观也相当不错。Google 的截图——还挺好看的！ 接下来，团队承诺将测试这种方法的极限，并分享见解。 代码在这里：https://github.com/wilsonzlin/fastrender
19 Jan 2026, 02:20 UTC75 viewsread 10 August 2026
Claude Code 现在直接在应用程序中显示差异 不再需要在 GitHub 和 IDE 之间跳来跳去了查看变更：在 Claude Code 的网页和桌面版本中新增了差异查看功能。现在您可以直接在应用程序中看到具体有什么变化。可以打开完整的差异，留下行内评论，并与 Claude 一起逐步进行修改——一切都在一个地方完成。
19 Jan 2026, 02:20 UTC72 viewsread 10 August 2026
Photo
Photo, posted without a caption
18 Jan 2026, 23:14 UTC66 viewsread 10 August 2026
如何绕过反机器人系统而不影响代理 如果你曾尝试自动化从 YouTube、Instagram 或 Amazon 收集数据，你会知道——这些网站会立即切断任何自动请求。结果总是相同：要么代理崩溃，要么开始“幻想”，没有获得所需的数据。 这对所有人来说都是个问题： ▪️ 新闻研究代理，拉取新闻 ▪️ 销售代理，抓取 LinkedIn ▪️ 电子商务代理，监测价格 ▪️ 社交媒体代理，捕捉趋势 在视频中，我展示了一个简单的测试： - 左侧：Claude 从 YouTube 抓取数据。没有特定工具——尝试使用 yt-dlp，但很快崩溃 - 右侧：通过 Bright Data 的 MCP 服务器——同一个请求一键解决，一切正常 所有的魔力都在内部：Bright Data 处理代理、旋转、验证码和反机器人系统，而对代理来说，这一切看起来就像普通的调用。 MCP 服务器是开源的，提供每月 5000 个请求的免费套餐。链接，看看如何…
18 Jan 2026, 23:14 UTC54 viewsread 10 August 2026
Video
Video, posted without a caption
18 Jan 2026, 20:06 UTC52 viewsread 10 August 2026
Video
Video, posted without a caption
18 Jan 2026, 20:06 UTC53 viewsread 10 August 2026
GitHub Copilot 现在与 OpenCode 一起工作！ 现在，GitHub Copilot 的订阅者可以正式使用 OpenCode。通过订阅 Pro+，您可以访问顶级编程模型。令人欣慰的是，该平台继续支持开源，并保留用户选择工具的自由！
Showing the 12 most recent of 20 posts we hold for @vibecodingCN. 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.
Citation-graph rank
Citation-graph rank — 1,207,186 of 1,626,884entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“VibecodingCN” (@vibecodingCN), 38 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/vibecodingCN.
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.