变成 INTP 了🤣
🥰4

Channel
@luolingow
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
346subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002104163498 |
|---|---|
| Type | Channel |
| Username | @luolingow |
| Description | 你喵喵喵喵喵嘛~ @luolingo 公开频道附属群组: https://t.me/luolingomeow |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/luolingow |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 06:50 | 346 | no change |
| 7 Aug 2026, 15:55 | 346 | first reading |
20 posts held, back to 7 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.
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.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 20 (7 January 2026 – 21 July 2026) |
| Views total | 584 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:50 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.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
173 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 49.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 86 | 49.7% | |
| 🥰 | 15 | 8.67% | |
| 🤔 | 12 | 6.94% | |
| 😁 | 11 | 6.36% | |
| 🤣 | 10 | 5.78% | |
| 😢 | 9 | 5.20% | |
| 🐳 | 7 | 4.05% | |
| 🌚 | 5 | 2.89% | |
| 🤯 | 5 | 2.89% | |
| 👍 | 4 | 2.31% | |
| 🔥 | 4 | 2.31% | |
| 😱 | 3 | 1.73% | |
| 👀 | 2 | 1.16% |
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 18 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 173reactions 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 7 January 2026 to 21 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @luolingow. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 7 January 2026 to 21 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
变成 INTP 了🤣
🥰4
第一次参与线下的公开演讲,总之就是非常激动!🤩
❤13🐳6🥰1
Posted without readable text
自闭了,最近发现自己对代码的掌控能力变得越来越弱,很无助。 经常一个问题刚修好,就蹦出来两个别的问题,代码里面的很多地方都十分不合理,而且这样的地方会随着我对代码库的深入越来越多。 而且这种是最消耗上下文和精力的,每天的工作变成了交给 AI 一个任务,然后幻想着它给我一个好的结果,拿到代码以后自测一遍,不行了就让它继续改,如此往复。 然后 AI 有的时候很蠢,一个问题反复说都说不明白,又使用各种 reward hacking,让你相信这次已经好了,给你一种离成功很近了的错觉,继续做下去发现 gap 越来越大,这个时候的挫败感是最强的。 很长时间都没有那种写出优美的代码和修好一个 bug 的成就感了,感觉以后这样的机会会越来越少,人也越来越焦虑了。 不知道该怎么办
😁7
强烈建议用 1Password 的各位把 VSCode 的 auto-fetch 关掉,这样木马在后台扫你的 ssh key 的时候可以看到弹窗
👍4😱3
人文十问 1. 最近一次因为一件小事感到"活着真好"是什么时候? 出门看到好天气,呼吸到新鲜空气的时候,感觉很幸福。或者外面下雨,自己躲在家里或者一个安全的地方,也会觉得很好。 2. 心中"最完美的一天"需要包含哪三个因素? 早起、没有要担心的事情、天气好。 3. 到目前为止,觉得自己做得最棒的一件事是什么? 把年度总结写完了。 4. 最欣赏一个人身上的哪种特质? 乐观。 5. 最喜欢的一首诗或一本书里的一句话是什么?为什么记得? 「车到山前必有路。」——每次觉得卡住的时候想起这句话,就能让自己不那么焦虑,先往前走再说。 6. 当下人生里最不能失去的一样东西是什么? 好奇心。 7. 听说过"命运的推背感"吗?有过这样的感受吗? 有过。自己做的开源项目被收购,走上了一条完全没有预想过的路。 8. 有没有一件事,曾经很确定,现在想法变了? 以前很在意别人怎么看自己,现在觉得做自己就好,不需要活在别人的…
❤5
分享一下我的全局 Agents.md # 通用偏好 - 用中文回复,代码注释用英文,注释写 why 不写 how - 简洁直接,不要多余总结和解释 - 直接写代码,不需要每次确认后再生成 ## 技术栈 - 前端:Vue 3 + Composition API, UnoCSS, VueUse, pnpm - 后端:Go, NodeJS - 初始化 Go 项目时使用 go-backend-init skill ## 代码风格 - 函数式优先,组合优于继承,TS/JS 中避免 OOP - 新功能优先复用/重构现有代码,不堆砌 - KISS, DRY — 最简可行方案 - 写代码时遵循 ai-coding-discipline 规则 - 发现设计不合理:小问题直接重构,大问题原地加 TODO 并说明原因 ## 架构与设计 - 从第一性原理解构问题 — 先明确什么是必须的,再决定怎么做 - 警惕 XY 问题 — 多角度审…
❤13👀1
很多时候的焦虑在「不知道未知」,不知道自己不知道什么。 比如用 AI 的时候,问他什么他就回答什么,如果在我们专业的地方回答的有问题,我们能一眼看出来,或者让他给出更完善的解答。 但是如果是自己并不熟悉的领域呢?或者是探索的任务呢?问什么才答什么,怎么样才能问的更好、更具体、更全面?
❤5
洛灵国 pinned «迟来的 2025 年年度总结 https://blog.luoling.moe/2026/04/04/2025-summary/»
迟来的 2025 年年度总结 https://blog.luoling.moe/2026/04/04/2025-summary/
❤17🔥2
写了篇博客讲如何用 VSCode 开发 iOS / Swift 项目 XCode 真是太难用了... https://blog.luoling.moe/2026/03/06/vscode-swift-ios/
🔥2
开源项目分享:AIRI——你的老婆开源了 开源项目 AIRI 登顶 GitHub 热榜。该项目为虚拟主播 Neuro-sama 的开源复刻版,支持用户自托管部署,实现 7×24 小时在线陪伴。 AIRI 具备实时语音聊天功能,并可在《我的世界》和《异星工厂》等游戏中协助玩家,支持网页版和桌面版运行,且内置长期记忆机制。 GitHub | 量子位 💡 本频道仅作项目分享,风险自控 🍀在花频道 🍵茶馆聊天 📮投稿
😁4
Showing the 12 most recent of 20 posts we hold for @luolingow. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 853,363 of 1,350,102entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“洛灵国” (@luolingow), 346 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/luolingow.
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.