面向Agent开发实例 #教程 #专题 希望对你有所启发. 面向Agent开发 和 面向chatbot开发 相比, 最大的优势就是, 可以让Agent自己测试最终产物, 大大节约以前人类测试的时间. 特别是, 当你用的不是SOTA模型, 大概率无法(one shot)一次开发成功, 那么让Agent自己测试循环迭代就尤为重要. 值得注意的是, 这里面都没有使用SOTA模型. 用的都是 mimo啊, longcat啊, hy3啊, deepseek-v4-flash啊, 要么就是路边捡别人不要的, 要么就是特别便宜的. 我希望作为一个示例, 让读者们看到, 像这个难度级别的需求开发, 不需要用到最贵的模型, 也就不会有那么大的代价, 也就欢迎更多的人尝试成为创造者, 通过开发, 满足自己的需求. 还有一点我希望读者们看到, 面向Agent开发, 要用一种什么表达方式和Agent交流. 进一步地, 在你自己的大脑里面, 要用一种…

Channel
FuckGFW-Newbie 翻墙新手村仓库
@FuckGFW_Newbie1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
959subscribers
+12 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 | -1002780688238 |
|---|---|
| Type | Channel |
| Username | @FuckGFW_Newbie1 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/FuckGFW_Newbie1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 03:36 | 959 | +1 |
| 22 Aug 2026, 13:05 | 958 | +6 |
| 14 Aug 2026, 15:45 | 952 | +6 |
| 8 Aug 2026, 07:18 | 946 | -1 |
| 8 Aug 2026, 00:49 | 947 | no change |
| 7 Aug 2026, 19:22 | 947 | first reading |
Engagement
20 posts held, back to 31 May 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 · 30 days
- 56.8%
- avg views ÷ 959 subscribers
- Avg views / post
- 545
- 3 posts measured
- Reaction rate
- 0.073%
- reactions ÷ views · ER floor
- Posts in window
- 3
- of 20 held
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. It is computed over the 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (31 May 2026 – 5 August 2026) |
| Views total | 1,634 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:49 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.
What this channel posts
- Video runtime
- 11s
- Average length
- 11s
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.
Reaction mix
6 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 33.3% | |
| 👎 | 2 | 33.3% | |
| 💯 | 2 | 33.3% |
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 6 of the 20 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 May 2026 to 5 August 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.
Recent posts
如果你不喜欢 Hermes 自动reset 清空上下文session 那么你可以关闭 hermes config set session_reset.mode none * 这个选项与自动压缩上下文无关. #Hermes #Tips
👍1
安装OmniRoute #白嫖 #免费 模型 by Hermes 对接 tencent/hy3:free 1. 学习 https://github.com/diegosouzapw/OmniRoute, 安装到你所在的环境上 2. 你自己启动浏览器使用 omniroute, 在没有邮箱, 没有钱的条件下, 找到可以使用的模型. 详细教程: https://zelikk.blogspot.com/2026/08/omniroute-hermes-agent-oracle-arm-ubuntu-root-sudo-.html
用非SOTA模型的开发心得 - Hermes 对接 longcat-2.0 longcat-2.0 许愿(one-shot)的效果并不好. 推荐你先让TA出设计方案, 然后你审视这个方案, 优化或者推翻这个方案, 或者找更高智能的模型出方案. 再让TA实施. 当你与 agent 讨论过多个方案后, 让agent把你决定要用的方案总结 为 .md 文件, 你再扫一眼. 然后让agent 按.md文件实施. 避免agent没听明白你最终选择的是哪个方案, 也避免长时间实施过程中, 注意力飘移, 转去尝试其它讨论过的方案. longcat-2.0有机率在做任务A时, 把任务B的正确的结果破坏了. 所以, 在验证功能满足要求后, 要提交github (我知道可以本地git, 但面对小白, 就不搞这么复杂了. 而且担心万一agent把本地整个目录删了呢?) 如果你突然发现, 哎呀, 现在在做任务A, 怎么任务B的效果没了/坏了? 你…
让 AI / agent 配置翻墙内核是未来的趋势 source: https://xtls.github.io/config/ 示例: https://zelikk.blogspot.com/2026/06/sing-box-anytls.html
#Telegram 如果你有其他设备是登录状态 可以申请 #passkey 再登录 Win10教程(申请到 Chrome) Win11教程(申请到 iOS)
forkgram/tdesktop 开发 #专题 <Oracle ARM VPS 编译 forkgram/tdesktop 用aqtinstall安装Qt> <2G内存 x86_64 VPS 编译 forkgram/tdesktop 内存不够 改大 swap 空间> <从forkgram/tdesktop github action编译 win10 amd64 二进制文件> <屏蔽某个用户消息的功能> <不查看某人的头像> <有@我消息的群置顶> <按对话分组批量静音> 已合入主线 https://github.com/forkgram/tdesktop V7.0.3
<去掉xray v2rayN对allowInsecure的报错> https://zelikk.blogspot.com/2026/06/xray-allow-insecure.html <去掉v2rayNG对allowInsecure的报错> https://zelikk.blogspot.com/2026/06/v2rayng-allow-insecure.html #教程
👎2
<ShareX 上传到 R2 的 S3 存储> https://zelikk.blogspot.com/2026/06/sharex-r2-s3.html <file-r2-worker 管理 R2 的 S3 存储> https://zelikk.blogspot.com/2026/06/file-r2-worker-cloudflare-r2.html #教程
ios swiftgram 直接点第11个folder提示充钱 从第10个folder直接滑过去 就没事
https://aistudio.xiaomimimo.com/#/settings
自动高亮 GitHub Release 推荐下载 演示视频 https://www.youtube.com/watch?v=Xz2v6k5Owg8 油猴脚本 https://github.com/crazypeace/github-release-highlighter 开发故事 https://zelikk.blogspot.com/2026/06/github-release-tampermonkey.html #Tips
Showing the 12 most recent of 20 posts we hold for @FuckGFW_Newbie1. 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,555,626 of 1,628,927entries 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“FuckGFW-Newbie 翻墙新手村仓库” (@FuckGFW_Newbie1), 959 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/FuckGFW_Newbie1.
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.