Telegram RegisterThe public register of Telegram

Channel

虹线

@pls1q43

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

721subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001551116890
TypeChannel
Username@pls1q43
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/pls1q43

Growth

720721720.56 August 2026 — 721 subscribers6 August 2026 — 721 subscribers7 August 2026 — 720 subscribers14 August 2026 — 721 subscribers6 August 202614 August 2026
4 measurements spanning 8 days. 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 720–721 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:38721+1
7 Aug 2026, 03:25720-1
6 Aug 2026, 16:15721no change
6 Aug 2026, 15:48721first reading

Engagement

19 posts held, back to 1 August 2025the 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
32.0%
avg views ÷ 721 subscribers
Avg views / post
231
2 posts measured
Reaction rate
0.813%
reactions ÷ views · ER floor
Posts in window
2
of 19 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 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held19 (1 August 20256 August 2026)
Views total462
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 16:15 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.

Reaction mix

37 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 54.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2054.1%
👍1540.5%
12.70%
👏12.70%

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 11 of the 19 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 37reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 1 August 2025 to 6 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

6 Aug 2026, 03:17 UTC123 views1 reactionsread 6 August 2026

#博客 更新啦~ 📰标题:AI 不会带来超级组织 📅日期:2026/8/06 ✏️摘要: 发一篇职务写作,给 AI 赋能组织浇浇冰水。 2025 年之后,“AI 裁员”终于从一种饭桌上的猜测,变成了公司公告里的正式理由。 过去的裁员通稿通常很讲体面:宏观环境变化、组织结构调整、提升运营效率、聚焦核心业务。话说得越圆,真实原因越像被塞进了抽屉。 AI 改变了这套话术。亚马逊、Meta、Block、Klarna,一批科技公司开始把人力收缩和 AI 效率提升放在同一个叙事框架里。美国媒体和咨询机构也开始追踪那些直接归因于 AI 的岗位消失。到 2025 年底,美国直接归因于 AI 的裁员已经超过 5.5 万人。亚马逊两轮裁员约 3 万,其中相当大一部分集中在 L5 到 L7 的中层岗位。Block 更极端,在盈利状态下一次裁掉了 46% 的员工。[1] 🏷️标签:#AI #互联网 #企业管理 #组织 #超级个体 👉阅读全

1

17 Jul 2026, 01:59 UTC339 viewsread 6 August 2026

#博客 更新啦~ 📰标题:善用“古法 AI”,能帮你省下很多 Token 📅日期:2026/7/17 ✏️摘要: AI 之后,个性化信息系统突然泛滥了。 日报、舆情监控、行业雷达、选题助手、知识推送——名字不同,后台却经常长得一模一样:先抓一堆原始文章,再把每篇文章塞进大语言模型,问它「这篇和我的主题相关吗?」 这很自然。大语言模型看起来会读、会判断,而我又需要一个人替我筛信息,那就让模型把文章读一遍。过去是实习生坐在电脑前逐条判断,现在把实习生换成 API 就行了。 问题是,实习生是固定工资,但 LLM 不是。… 🏷️标签:#Agent #AI #Embedding #Harness #工作流 #邸报 👉阅读全文👈

1 Jul 2026, 05:09 UTC441 views3 reactionsread 6 August 2026

#博客 更新啦~ 📰标题:为什么说 Anthropic 是邪恶的? 📅日期:2026/7/01 ✏️摘要: 如果你重度依赖海外 AI 工具,又恰好生活在中国,你大概早就习惯了”赛博二等公民”的待遇。 你得找干净的节点,得注册海外的信用卡,得时刻担心那个好不容易养起来的账号,会不会在某次风控里被”连坐”封掉。 但 Anthropic 这次干的事,还是超出了我的想象。 2026 年… 🏷️标签:#AI #Claude #地缘政治 👉阅读全文👈

👍3

29 May 2026, 05:03 UTC591 views5 reactionsread 6 August 2026
Photo

各位中午好,自荐一下我的新项目——邸报。 这是一个免费、自部署的、带推荐算法的 RSS 阅读器。 效果是在你的 RSS 订阅中实现类似今日头条的个性化排序,把你最感兴趣的内容提到前面,如果你的 RSS 收件箱每天有 100 篇以上的文章,可能会非常需要这个。 和 AI 时代兴起的个性化阅读不同,邸报使用的是传统的“推荐算法”。它的效果实际比 LLM 要好很多,而且 API 成本非常低(几近于零)。 它只要本地或接入一个 0.6B 的 Embedding 模型就能使用——如果你用硅基流动那么费用就是 0。如果你在本地部署,那么几乎不耗性能。 它刚刚发布了非常早期 0.1 版本,有任何问题欢迎在 Github 上提 Issue: https://github.com/Pls-1q43/Dibao 官网在这里:https://dibao.app/

5

14 May 2026, 02:52 UTC790 viewsread 6 August 2026

#博客 更新啦~ 📰标题:错称|小说 📅日期:2026/5/14 ✏️摘要: 1. 称 槐荫坞的门在天亮前开了。 林知夏先听见井绳响。木轴多年没有上油,转起来像有人在院墙后低声咳嗽。接着是陶老的脚步,慢,准,每一步都压在湿土上。灶里的灰还没有被拨开,瓦罐里昨夜剩下的水已经冷透。五月的风从门缝里钻进来,带着麦秆和猪圈的味道。 她把布鞋穿好。鞋面上有一块补丁,针脚由她自己缝,密得像一行没有字的注释。她把袖口扎紧,又摸了摸腰间的红绳。红绳上串着一粒黑豆。今天轮到她过秤。 院子外已经站了十几个人。没人说话。说话会让事情显得像送行。槐荫坞的人早就学会了把重大事情做成杂活,像挑水,像磨刀,像清明前给祖坟除草。只要动作够熟,心里就不会空出太大的洞。 陶老站在最前面。她的头发全白,梳得很紧,脑后插着一根竹簪。她手里捧着一个小布袋,袋口用麻线绕了三道。里面装着今年新收的谷粒。 “今日试的事,”陶老说,“分谷。” 她说到这里停住。

12 May 2026, 01:09 UTC431 views1 reactionsread 6 August 2026

#博客 更新啦~ 📰标题:如何给 Notion AI 接入第三方 API? 📅日期:2026/5/12 ✏️摘要: 我之前讲过将「哈勃半径」作为一种私人信息宇宙,并将它接入 Notion AI。 但问题是,Notion AI 如果不使用 Custom… 🏷️标签:#AI #CLoudFlare #notion 👉阅读全文👈

1

6 May 2026, 01:02 UTC639 views4 reactionsread 6 August 2026

#博客 更新啦~ 📰标题:一个新的 AI 记忆层概念:哈勃半径 📅日期:2026/5/06 ✏️摘要: 最近几个月,我给自己的 AI Agent 配了三层上下文记忆。 第一层是「我知道的」。第二层是「我应该知道的」。第三层是「我可能知道的」。这个第三层,我叫它「哈勃半径」。 AI 不应该只知道我已经写下来的东西,也不应该一遇到问题就冲进公共搜索引擎。它应该先知道一件事:在我的世界里,哪些东西本来就有可能被我看见。 很多人在谈 AI… 🏷️标签:#AI #Dayflow #LLM_Wiki #notion #哈勃半径 👉阅读全文👈

👍31

27 Apr 2026, 10:20 UTC548 viewsread 6 August 2026

#博客 更新啦~ 📰标题:AI 也该有护照了 📅日期:2026/4/27 ✏️摘要: 以前公司出海,像搬家。 现在 AI 公司出海,更像改户口,哦不,像改国籍。 Manus 这件事有意思的地方,不在 Meta 到底想不想买,也不在这家公司值不值 20… 🏷️标签:#AI #Manus #Meta #监管 👉阅读全文👈

16 Mar 2026, 03:11 UTC≈1,190 viewsread 6 August 2026

#博客 更新啦~ 📰标题:艾司唑仑戒断与 BIND 自救记录 📅日期:2026/3/16 ✏️摘要: 线下认识我的朋友都知道,2025 年末到 2026 年初,我经历了一段相当痛苦的时期。 起因是腰椎间盘突出,但很快情况发展到了体位性心动过速——站立心跳持续在 100 以上,坐姿的心率也在 90 以上。… 🏷️标签:#安眠药 #艾司唑仑 #苯二氮卓 👉阅读全文👈

26 Nov 2025, 07:34 UTC915 views3 reactionsread 6 August 2026
Photo

#广告 老牌低价云服务商 CloudCone 的黑五价格上线了。 KVM 四个机型,三个机房目前全都有存货,2G1C 最低 10.59 美元一年。 但今年最值的应该是最高规格版 10v8G 的 KVM 只要 55 美元一年。 🔗入口在这里,囤机的从速,按以往经验库存不会很多:https://hello.cloudcone.com/bf-mega-sale-2025/?ref=11379 (此链接为Affiliate Link,通过此链接购买我会获得返利,如介意可通过 CloudCone 官网入口进入) CC 目前三个机房 Los Angeles, St. Louis, Reston,分别在美国西岸、中部和东岸。 放个人博客首选选洛杉矶,对境内访问友好,但同款比另外两个机房贵一点。 我博客之前 3 年托管在 Dreamhost 一个低价套餐,性能不是很理想。刚刚也抢了一个 CC 洛杉矶机房的 KVM,打算有时间就迁移上去了。

3

18 Nov 2025, 03:12 UTC≈1,120 views1 reactionsread 6 August 2026

#博客 更新啦~ 📰标题:AI 可能不会改变许多工作 📅日期:2025/11/18 ✏️摘要: 如果你在焦虑 AI 导致的大规模失业, 那不妨先思考这样一个问题: 在 2025 年,有多少人的工作完全用不到电脑和手机? 如果你给出的答案是非常少,那你可以一边看文章,一边再想想,我们会在文章的中部计算这个数字与百分比。… 🏷️标签:#AI #体力劳动 #就业 #数字化 👉阅读全文👈

1

8 Nov 2025, 01:09 UTC757 views0 reactionsread 6 August 2026

#博客 更新啦~ 📰标题:翁法罗斯与价值对齐 📅日期:2025/11/08 ✏️摘要: 其实,翁法罗斯 3.7 的剧情争议,早在 GPT-5 上线的时候就有记载。 先给不知道翁法罗斯是什么的朋友做下科普,这是米哈游回合制游戏《崩坏:星穹铁道》中 3.0 – 3.7… 🏷️标签: 👉阅读全文👈

Showing the 12 most recent of 19 posts we hold for @pls1q43. 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 — 153,578 of 1,478,351entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“虹线” (@pls1q43), 721 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/pls1q43.

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.