Channel
@zuoluotvofficial
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,893subscribers
-22 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001478104037 |
|---|---|
| Type | Channel |
| Username | @zuoluotvofficial |
| Created | Between 1 April 2019 and 30 September 2021 — 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 | 13 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/zuoluotvofficial |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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, 03:18 | 2,893 | +2 |
| 13 Sept 2026, 09:37 | 2,891 | -2 |
| 9 Sept 2026, 14:55 | 2,893 | -7 |
| 3 Sept 2026, 23:22 | 2,900 | -2 |
| 31 Aug 2026, 11:23 | 2,902 | -1 |
| 28 Aug 2026, 01:04 | 2,903 | -3 |
| 25 Aug 2026, 11:23 | 2,906 | -5 |
| 22 Aug 2026, 19:44 | 2,911 | -2 |
| 16 Aug 2026, 07:47 | 2,913 | -1 |
| 12 Aug 2026, 08:18 | 2,914 | -2 |
| 6 Aug 2026, 13:40 | 2,916 | +1 |
| 6 Aug 2026, 06:46 | 2,915 | no change |
| 6 Aug 2026, 06:39 | 2,915 | first reading |
13 posts held, back to 8 February 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 2 pages 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 13 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
重大改版: MXGA v0.5 已正式上架 Chrome 商店 🎉 已安装用户无需操作，Chrome 会陆续静默升级。同时感谢@tualatrix 贡献的 iOS Safari 版本，现在 iPhone 也能启用 MXGA 的保护。 👉 https://x.zuoluo.tv MXGA 是一个公益、开源的 X 反 SPAM 插件，目前已服务 5,000+ 用户。上线两个月来，我们累计识别并收录了近 20 万个 SPAM 账号。 数据规模变大后，准确度、误伤和处理尺度也成了新的挑战。v0.5 基于社区和用户反馈，主题是更准确、更克制，重点做了 4 个升级： 🧩 分级处理 色情引流、币圈投放、博彩推广、网盘资源、营销引流等不同类型的 SPAM，可以分别选择：仅标记 / 本地隐藏 / X 静音 / X 拉黑。 🎯 范围可选 自动处理可以只作用于评论区，也可以覆盖信息流、主页和评论区。 🛡️ 保护我的账号 新增白名单自助申…
在考虑要不要给 MXGA 新增一个「AI 人类清除计划」模式。🤖 过去一周，已经收集到 40k+ 公开账号，发现 X 简中圈的 AI BOT 比想象中严重得多。 自动发帖、自动回复。表面是干货，实际是洗稿。看着像是真人，实际是流量工厂那套玩法。 再这样下去，未来 X 上最稀缺的可能不是流量，而是真人。🤫 x.zuoluo.tv
最近 X 上「dd 蹲一个线下的哥哥」这类 spam 号刷屏太凶了，我自己也深受其害 🫠 做了一个开源、免费的 Chrome 插件：MXGA（Make X Great Again）。先从干掉评论区的色情 bot 开始。 🧠 分布式上报 + 中心处理，AI 识别可疑账号 🚫 你确认后，一键拉黑（走 X 原生屏蔽） 🔓 不收集你的 X 身份，黑白名单全部公开 正式版已提交 Chrome 商店，欢迎试用、提 issue 👇 🌐 官网：https://x.zuoluo.tv/ 🔗 GitHub：https://github.com/foru17/make-x-great-again
🗓 活动预告： #疯狂星期四 深圳场第12期，下周四，不见不散哟～ 🎡 让我们海边小聚，远眺摩天轮，吹着五月海风，和 App & AI Builder 们一起聊聊产品、创作与生活 ☕️ 无需准备，无需PPT，喝喝咖啡、随意交流、海边散步，主打一个 Chill～ - 时间：2026年05月14日(星期四) 12:00~18:00 - 地点：南山区·前海石公园·福叁咖啡 - 报名入口：https://developer.apple.com/community/events/ - 活动名称：Crazy Thursday Meetup - AI & App Builder 🍎 - 更多说明：免费/无门槛/一键报名/限制人数 更多细节： - 设施：空调/WiFi/插座 - 地铁：1号线 · 前湾站 - 停车：恒裕前海金融中心T1停车场
AI 听懂人话了，还要像以前那样学编程吗？ https://www.youtube.com/watch?v=f3fGQfdHoIo
建议对 Vibe Coding 或 AI 做产品感兴趣，看看 @turingou 最近的直播。很多人讲 AI 是为了流量（比如我），但郭宇不是：他早已财务自由，是 Github 中文区最顶级程序员之一，字节早期员工，见过世面，有很强架构思维。看他怎么 Vibe，其实是在看 AI 时代，能力、经验、资源都拉满的人，会怎么做产品。 📺 https://vibelab.live/guoyu
Channel photo updated
我把 5 个 OpenClaw agent 放进了一个叫「相亲相爱一家人」的小群里，各有分工： Lulu 🐱：项目管家，负责规划、任务拆解、推进和跨 agent 协调 Uber 灰猫 🐱：技术工匠，负责开发、部署、脚本和落地实现 Momo 🐰：小兔，负责博客、推文、视频脚本和内容策划 Neko 蓝猫 🐱：洞察猫咪，负责数据分析、趋势洞察和统计反馈 Bit / 比特 🐕：负责查资料、信息检索和日常轻事务
过去 10 年，我给自己设了个「人生马拉松」计划：每年至少一场全马 🏃♂️，今年刚好 10 场。 现在准备开启另一个长期项目「人生 AI」：持续迭代我的 AI 分身 🤖，也顺手记录这波 AI 浪潮的技术演进。 拍了个视频，记录这次有趣的尝试👇 https://youtu.be/_uj7sQ7CvQw?si=_HOiNEbVbhAVBXxy
2 月以来 Vibe Coding 工作量剧增，Tokens 消耗也跟着暴涨 🚀 我原本的 ChatGPT、Claude、Antigravity、Cursor、Warp 原厂额度基本都用光了。 最近又补了几个 Tokens 渠道备用： 1️⃣ Kimi Code Allegretto ¥199/月（国内版） 比国际版便宜，跟老婆一起用，Tokens 基本用不完，速度也挺快，适合普通 agent 场景。 2️⃣ 阿里云 Code Plan Pro ¥199/月（首月 ¥39.9） https://www.aliyun.com/benefit/scene/codingplan 支持 qwen3.5 / glm-5 / kimi k2.5，整体速度不错，先用这个月再看看。 3️⃣ HONGMACC 中转站 ¥368/月（月卡） https://hongmacc.com/signup?ref=HONGMACC-B53D84C7 每天…
这两天做了一件挺有意思的事。 把自己过去十多年的公开内容全部结构化，做成一个可以聊天的「AI 版的我」。 多模型画像、加权 RAG、强反幻觉规则、三级限流与安全校验。 写了篇博客，把完整架构和设计流程梳理了一遍。 🔗 https://luolei.org/luolei-ai
我把过去 10 多年 300+ 篇博客、推文、GitHub 内容全部做了 Embedding 向量化，构建了一个基于 RAG 的个人知识系统 🧠 刚刚又花了 1 个小时，让这个「AI 罗磊」接入新的 Vinext 博客。 现在可以直接在博客和我的数字分身聊天 🤖 和自己聊天的感觉，还挺奇妙的。 在生成式时代： 内容一定会被 AI 读取。 但是否被完整理解，取决于你是否主动构建自己的知识结构。 被动被抓取，和主动建立语义索引，是两回事。 让 AI 理解你，本质是在拿回解释权 ⚙️ 🔗 luolei.org
Showing the 12 most recent of 13 posts we hold for @zuoluotvofficial. 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.
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.
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.
“ZUOLUOTV” (@zuoluotvofficial), 2,893 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/zuoluotvofficial.
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.