Telegram RegisterThe public register of Telegram
Telegram profile photo for 山有木兮木有枝の百宝箱

Channel

山有木兮木有枝の百宝箱

@louisgreenchannel

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

414subscribers

+2 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-1002188050181
TypeChannel
Username@louisgreenchannel
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/louisgreenchannel

Growth

4124144137 August 2026 — 412 subscribers8 August 2026 — 412 subscribers15 August 2026 — 414 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net +2. 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 412–414 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:45414+2
8 Aug 2026, 05:35412no change
7 Aug 2026, 14:32412first reading

Engagement

20 posts held, back to 3 February 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 13 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

166 reactions across 19 posts, in 16 distinct kinds. The most used accounts for 15.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2615.7%
💩1710.2%
👎169.64%
😁169.64%
🤮169.64%
🤔159.04%
😢127.23%
😱116.63%
🤯116.63%
👍106.02%
🤬95.42%
🤡21.20%
🥰21.20%
👀10.602%
😇10.602%
🤩10.602%

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 19 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 166reactions 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 3 February 2025 to 13 May 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.

Advertising

Ad load
5.00%
1 of 20 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
1,970
over 1 measured post
Median views · rest
2,170
over 19 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 20 most recent posts we hold, published 3 February 2025 to 13 May 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

13 May 2026, 04:50 UTC≈1,110 views2 reactionsread 8 August 2026

关于机场“专用客户端” 2026年以来,大家或许都有一个直观的感受:整个网络代理行业的风向正在发生剧烈的变化。随着上游IDC监管与合规审查的骤然收紧,各路机房“拔线”通报、路由阻断事件层出不穷,整个生态正面临着前所未有的生存压力。 为了在这波冲击中维持服务的可用性,机场主们被迫展开了一场防守反击的军备竞赛。我们看到,越来越多的机场开始放弃传统的公共解析,转而采用自建节点域名DNS来规避外部追踪;传统的长期订阅链接也逐渐演变为“阅后即焚”的动态下发机制,以防止节点信息被恶意爬取或滥用。而在这些技术防御手段中,最为彻底、也引发最多争议的,便是强制推行深度定制的“专用客户端”。 平心而论,站在机场主的立场,这种不断收紧防线、走向封闭的做法是充满无奈的。在当下的网络环境中,维持一条低延迟、高稳定的跨境线路不仅成本高昂,且风险极高。机场主不仅要应对随时可能降临的审查与封锁,还要时刻防范同行的恶意嗅探、DDoS攻击以及部分用户的无节制

1👍1

16 Apr 2026, 15:16 UTC≈1,400 views3 reactionsread 8 August 2026

项目已开源在 https://github.com/louisgreen0726/financial-calc 欢迎各位的Issue

2👀1

29 Dec 2025, 19:06 UTC≈2,450 views5 reactionsread 8 August 2026

致南方周末2026新年献词: 岁末的温热里,怀念那记刺破长夜的击打 在这篇2026年的献词里,我确实读到了温热。 字里行间,是AI与人的辩证,是宏大叙事下对个体命运的抚摸,是试图用“柔软”去弥合裂缝的善意。这文风依旧华丽、排比依旧工整,像极了一场精心编排的晚会,灯光打在每一个人的脸上,柔光镜下,泪水与汗水都显得晶莹剔透,不再苦涩。 可是,读罢掩卷,在这岁末的寒意里,我却没能等来那股曾经让我热血沸腾的暖流。 记忆总是执拗地将我拉回那间中学教室。那时,课桌下偷偷摊开的新闻纸,粗糙的质感却承载着最细腻的理想。那时候的你,不谈“柔软”,你谈的是 “让无力者有力,让悲观者前行”;那时候的你,不只是告诉我们要彼此微笑,你告诉我们 “没有人是一座孤岛” ,并用犀利的笔触去连接那些被海水隔绝的岛屿。 那时的你,是早已预备好的那束光,在总是还有些黑暗的时刻,即便微弱,也要像利刃一样刺破它,而不是像现在这样,用漫溢的柔情去包裹它。 这

4🤮1

19 Dec 2025, 16:34 UTC≈2,300 views3 reactionsread 8 August 2026

https://financial-calc.pages.dev/ 0编程基础(All Powered by Google Antigravity)的一个金融计算器 有需自取🥰

🥰2🤮1

25 Nov 2025, 12:27 UTC≈2,380 views1 reactionsread 8 August 2026
Forwarded from @speedcentre

关于头部几家机场的劫持检测已经做了详细的报告可以参考下: https://telegra.ph/Speedcentre小众机场测评机场劫持观察报告-11-25-2

🤮1

27 Aug 2025, 11:42 UTC≈2,660 views7 reactionsread 8 August 2026

频道近期更新非常少,望各位海涵。 究其原因,除了日常事务的些许牵绊,更重要的是,近期的“机场”圈子正经历着一场前所未有的动荡,堪称黑白两道的联合绞杀,令人不得不审慎观察。 ​从明面上看,随着9.3节点的临近,审查力度正层层加码。坊间消息传言,如今的策略已非简单的技术封堵,而是可能存在专人购买订阅、循迹查封IP的定点清除模式。前段时间深夜全国出口443端口的集体异常的这种事件的发生,不难看出审查变得愈发严格。 ​从暗地里看,DDoS攻击等黑产手段也愈发猖獗。许多机场成为其攻击与勒索的目标,直接导致大量服务体验骤降,甚至部分运营方在重压之下选择关停跑路。 ​在这双重挤压下,即便是声誉卓著的老牌服务商也难免受到冲击,至于那些原在观察计划中的小型机场,处境则更为艰难。往期内容中提及的部分服务商,确实出现了运营中断的状况,有些甚至已停摆数月,未来能否恢复,已是未知之数。 ​基于此等现状,以下是一些恳切的建议: ​近期在选择服务时

👍32🤡1🤮1

8 Aug 2025, 03:58 UTC≈2,170 views1 reactionsread 8 August 2026

SNTP Media Lite 公益计划将于 8月8日(周五)晚上8点 开放新用户注册。 新增名额: 超过 500 个。 注册期间: 服务器的观看功能将会暂停,以确保注册顺利进行。 新用户要求: 注册成功后,必须在 8月10日(周日)前 至少观看一次内容。 @sntp_emby_lite_v2 守候的这个公益服真的挺不错的,肖总也确实很大方了。没有号的可以今天晚上试一试能不能注册上。

🤮1

10 Jun 2025, 14:46 UTC≈2,720 views4 reactionsread 8 August 2026
Photo

#Aladdin #阿拉丁 #非正式测评 #灵车 类别 #专线 入口 #深圳电信 落地 #MoeChuang #Spike #CatalystVM #Akari #Apple #Oracle #Cloudflare 速率 单线程1.5Gbps+ 解锁 流媒体解锁较好 测试时间 2025.6.10 22:00 主观评价 一家已运营一年有余的机场,近期正在进行网络线路调整,并于近日上线了一线机场同款的深圳电信183段入口。可以说在同等价位下提供了极为卓越的表现,在晚高峰时段,电信用户也能体验到稳定在近个位数毫秒的极低延迟,且抖动也极小。然而,由于基本只有单个电信入口,移动和联通用户的延迟则会显著升高,并伴有剧烈的网络波动(具体情况详见测速图),因此目前仅推荐给电信用户购买。同时,用户也必须意识到此新入口的潜在风险,由于其上线时间不长,未来的服务生命周期存在不确定性,这也是我将其打上“灵车”Tag的原因。基于这一

2👍1🤮1

11 May 2025, 17:23 UTC≈2,180 views1 reactionsread 8 August 2026

もし私と一緒に音楽を聴きたいなら @What_Louis_Listening

🤩1

5 May 2025, 06:55 UTC≈2,130 views9 reactionsread 8 August 2026
Forwarded from @Milkdragon888

#viking #送测 #专线 #电信 #移动 #联通 #唯云 #火山云 #广港专线 #莞港专线 #沪日专线 官网 群组 (购买高级套餐后可私聊管理进入高级群) 测速图 拓扑 价格 入口: IPLC三网 121广州电信,183深圳移动,58广州联通 IEPL 163深圳联通 N 42东莞唯云电信 Vol 14上海火山 新近上线的专线机场,配置相当豪华。 南区入口在三网线路的基础上,同时提供唯云电信与深圳联通两条独立线路(后续计划升级IEPL至三网全覆盖),东区则采用上海火山BGP,几乎不存在因 QoS 策略导致的访问受限。 落地节点质量同样出色,覆盖了 Dmit、Eons、Jinx、MISAKA、CTC、SGGS、DDPS、BAGE 等多个优质落地,并接入了多家本地家宽运营商,如 HKT HGC 等。 在用户体验方面,运营团队响应及时:最初节点未标注落地信息,在用户反馈后及时补充了相关信息

💩4👎2🤮21

27 Apr 2025, 13:25 UTC≈1,880 viewsread 8 August 2026
Photo

#BestTelecom 编号 06 类别 #专线 #中转 入口 #深圳电信 #海口移动 #揭阳移动 #淮南移动 #武汉联通 #北京亚马逊BGP #江苏宿迁BGP 落地 #Asymptote #快车道 #Misaka #Akari #Haruka 速率 无速率限制,单线程可达1Gbps,部分入口多线程可达5Gps+ 解锁 流媒体解锁较好 测试时间 2025.4.27 20:00 主观评价 开业时间一个月左右的小机场,入口复杂多样,采取智能解析策略,也可自己修改配置文件指定入口,落地较为优秀。入口多元化、多样化,同时不乏精品入口(如103段深圳电信),也有普通中转大宽带,总体上具有三网入口,能满足不同运营商用户的需求。不过智能解析策略存在一定问题,有时会分配到受跨省qos影响较大的入口(比如江苏宿迁BGP)(具体详见测速图)。流媒体解锁也还是比较优秀,尚有一定的提升空间,承诺全部节点无审计也是一个优点。定价方面

21 Apr 2025, 12:41 UTC≈1,410 views10 reactionsread 8 August 2026
Photo

#Aideer 编号 05 类别 #专线 入口 #深圳移动 #广州联通 #广州电信 #广州 Ucloud 落地 #Hytron #Cogent #快车道 #Akari #Wap #Nearoute 速率 按套餐等级限速,100G 套餐限速 300Mbps,200G 套餐限速 600Mbps,500G 套餐限速 1000Mbps 解锁 流媒体解锁较好 测试时间 2025.4.21 19:00 主观评价 开业时间一个月左右的小机场,广东三网运营商 +Ucloud BGP 入口,落地较为普通,不过完全足够日常使用。速率受套餐等级影响,最高等级月付限速在 1000Mbps 左右,单线程能跑满限速。由于提供了不同运营商的入口,因此推荐用户选择与自己运营商相同的线路,以免部分地区受到晚高峰跨网 qos 影响使用体验(具体情况测速图有显示),难能可贵的是提供 1 倍率的 Ucloud BGP 入口。流媒体解锁也还是比较优秀

👎2💩2🤔1🤬1🤮1🤯1😢1😱1

Showing the 12 most recent of 20 posts we hold for @louisgreenchannel. 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.

Forward network

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

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

“山有木兮木有枝の百宝箱” (@louisgreenchannel), 414 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/louisgreenchannel.

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.