微信小程序搜索:影厅指南 CINEMA GUIDE 可以更加直观查询全国IMAX,杜比音效等特效影厅,以及查看银幕尺寸、放映技术、影院地址 标签:#科普 #影视 #安利
❤6

Channel
@lihaiba
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry
38,770subscribers
+175 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001351552963 |
|---|---|
| Type | Channel |
| Username | @lihaiba |
| Description | 一个分享频道,进频道先看置顶,不定时不定量更新,希望推送内容对你能有帮助 有问题或投稿找资源私聊 bot @lihaibaBot 助力: https://t.me/boost/lihaiba LIHAI的收藏夹 @lihai GitHub的存档 @iGitHub 优质网盘资源分享存档 @lihaiCloud 转载原档请注明出处 @lihaiba 频道资源均收集于网上各大博客论坛资源网站等,对资源源以及真实性一概不知,如不慎对您的权利造成了伤害,请立即与我们 BOT 联系进行处理 |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/lihaiba |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 02:17 | 38,770 | +19 |
| 12 Aug 2026, 21:53 | 38,751 | +22 |
| 11 Aug 2026, 19:48 | 38,729 | +27 |
| 10 Aug 2026, 23:22 | 38,702 | +43 |
| 9 Aug 2026, 20:21 | 38,659 | +23 |
| 8 Aug 2026, 18:36 | 38,636 | +34 |
| 7 Aug 2026, 15:37 | 38,602 | +6 |
| 6 Aug 2026, 13:27 | 38,596 | +1 |
| 6 Aug 2026, 06:45 | 38,595 | first reading |
24 posts held, back to 26 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 20 pagesof 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 13 August 2026 |
|---|---|
| Posts held | 24 (26 May 2026 – 13 August 2026) |
| Views total | 64,680 |
| Reactions total | 76 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 13:06 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 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
234 reactions across 22 posts, in 7 distinct kinds. The most used accounts for 51.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 121 | 51.7% | |
| 👍 | 56 | 23.9% | |
| 💩 | 42 | 17.9% | |
| 😱 | 6 | 2.56% | |
| 🫡 | 6 | 2.56% | |
| 🤔 | 2 | 0.855% | |
| 😁 | 1 | 0.427% |
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 24 of the 24 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 251reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 26 May 2026 to 13 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @lihaiba. 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 24 most recent posts we hold for this entry, published 26 May 2026 to 13 August 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.
微信小程序搜索:影厅指南 CINEMA GUIDE 可以更加直观查询全国IMAX,杜比音效等特效影厅,以及查看银幕尺寸、放映技术、影院地址 标签:#科普 #影视 #安利
❤6
Macked的破解工具无敌
❤1
#互推 【转存&引流】媒体托管机器人 【网络分享】纸鸢分享社-破解软件|游戏分享 【资源分享】小声逼逼 【网络分享】互联网研习社(破解软件/游戏 | 实测) 【网络分享】LIHAI 分享 【科技分享】Fᴜғᴜ の Cʜᴀɴɴᴇʟ 【视频分享】B站充电视频分享 【小说分享】Lemaned的宝藏书屋(轻小说书库) 【软件分享】TK集库 Powered by @Summer_Clear_Sky_Bot
💩1
迁移网易云/汽水/QQ音乐歌单 至 Apple/Youtube/Spotify Music 1. 粘贴原歌单链接 2. 获取并复制歌曲列表 3. 粘贴列表文本导入目标平台:Spotify官方/TuneMyMusic 官网:https://music.unmeta.cn/ 标签:#开源 #音乐 #网站 #GitHub
❤6
【腾讯文档】全球IMAX及其他系统影厅分布20230822实时更新-推荐收藏 https://docs.qq.com/sheet/DQ3FEUUZJdklNSWJP
❤3
Uninstally:基于 SwiftUI 构建的原生卸载工具 另一款开源卸载工具 — Pearcleaner GitHub 标签: #工具 #MacOS #软件 #开源 #GitHub ✈️合作/投稿 频道群组 频道标签
▎💻 Microsoft PowerToys Microsoft PowerToys 是一套免费的开源实用工具集,可显著提升 Windows 系统的生产力和自定义程度 GitHub 官方介绍 标签:#插件 #Windows #开源 #GitHub ✈️合作/投稿 频道群组 频道标签
❤6
⭐ BilibiliDown 哔哩哔哩视频下载器,还能用 GitHub下载 标签:#B站 #下载 #Win
😱4❤2
【寻找卢本伟】 https://www.bilibili.com/video/BV1oHNv6kEzB 标签:#B站 #短视频
💩41🫡4❤2
🅰️ 印度区App Store的 SuperGrok 3个月¥50 先确认账号有7天试用 再往Apple Store账号充值700卢比余额 开通7天免费试用 开通后Grok左滑设置打开「SuperGrok」选项 点管理您的账单—点选择「降级 SuperGrok」 点「继续降级」后页面会弹出一个「专属限时优惠」 相当用低价区的1个月的价格(¥50)订阅3个月SuperGrok 标签:#AI #羊毛 ✈️合作/投稿 频道群组 频道标签
❤10🤔2
Mac 上两个⌘Tab 键快速切换窗口的应用 AltTab:基本功能免费,部分高阶功能收费 👨💻 GitHub 🌐 官网 BetterCmdTab:开源,宣传永久免费 👨💻 GitHub 🌐 官网 也可以自己用 AI 写一个😼 标签:#软件 #工具 #Mac ✈️合作/投稿 频道群组 频道标签
❤6
今天7月11号,外卖平台 711 便利店有羊毛 领各种券叠一起,觉得优惠可以看看 标签:#羊毛
😱2
Showing the 12 most recent of 24 posts we hold for @lihaiba. 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.
@lihaiba edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Citation-graph rank — 207,762 of 1,345,403entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 7 registered channels — 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“LIHAI 分享” (@lihaiba), 38,770 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/lihaiba.
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.