Telegram RegisterThe public register of Telegram
Telegram profile photo for 自留 channel

Channel

自留 channel

@who_channel

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

291subscribers

-1 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-1001352530400
TypeChannel
Username@who_channel
CreatedBetween 1 March 2018 and 16 March 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/who_channel

Growth

291292291.56 August 2026 — 292 subscribers6 August 2026 — 292 subscribers15 August 2026 — 291 subscribers6 August 202615 August 2026
3 measurements spanning 9 days, net -1. 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 291–292 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 10:57291-1
6 Aug 2026, 22:48292no change
6 Aug 2026, 15:55292first reading

Engagement

17 posts held, back to 16 March 2021the 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 17 posts for this entry, the most recent from 12 March 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

17 Apr 2022, 15:29 UTC≈2,040 viewsread 6 August 2026
Photo

https://github.com/blankmagic/surge/blob/main/profile.conf 新参数 include-other-group 使用新参数后,策略组只需要添加一次订阅地址,添加位置参见注释。 你可以从该 URL 下载这个配置文件: https://blankmagic.github.io/surge/profile.conf

Signed MAICOO

14 Sept 2021, 10:40 UTC≈2,020 viewsread 6 August 2026
Forwarded from @AppleNutsVideo

☎️「加州来电」 北京时间 9 月 15 日,凌晨 1 点  Apple Special Event

Signed MAICOO

10 May 2021, 02:12 UTC≈2,410 viewsread 6 August 2026
Forwarded from @odysseyplusPhoto

#BigNews #公益服 1️⃣ 公益服正式上线 - 如之前所讲,首批账号会被删除,请大家用全新的开号bot进行注册:@OdysseyPlusBot - 开号bot首次大规模部署,如出现问题,请大家保持耐心 - 关于账号注册以及账号保持的细节,请参考 食用指南 - 等会服务器关机,本次维护同时会升级一下服务器配置 2️⃣ Odyssey+食用指南上线 - 有任何使用问题请优先参考 食用指南 - 指南持续更新中 3️⃣ 加入我们 - 具体详情请参考 加入我们 Channel: @Odyssey+

Signed MAICOO

29 Apr 2021, 05:38 UTC≈1,720 viewsread 6 August 2026

https://twitter.com/blankwonder/status/1387624531699769345?s=12

Signed MAICOO

24 Apr 2021, 13:20 UTC≈1,910 viewsread 6 August 2026
Photo

怀念 Surge 3的policy group UI 现在的策略组UI看久了有点腻了,怎么看都不舒服!

Signed MAICOO

22 Apr 2021, 03:40 UTC≈1,710 viewsread 6 August 2026
Photo

#Surge 流量信息显示脚本中文版,自己替换脚本链接即可。 https://raw.githubusercontent.com/mieqq/mieqq/master/sub_info.js 感谢作者 @mieqq 频道 @who_channel

Signed MAICOO

15 Apr 2021, 07:07 UTC≈1,560 viewsread 6 August 2026
Photo

#AppStore 一键换区 频道 @who_channel

Signed MAICOO

9 Apr 2021, 08:26 UTC≈1,320 viewsread 6 August 2026
Video

#Surge 本地文本编辑教程 发现很多新人在Surge新建本地文件的时候都不知道从何下手,今天推荐个App(前提是使用Dropbox同步配置)Documents 频道 @who_channel

Signed MAICOO

8 Apr 2021, 13:16 UTC≈1,150 viewsread 6 August 2026

#Surge 配置文件指引 Surge 核心的功能由配置文件(Profile)所控制,当遇到一些特殊需求时,需要通过手动编辑配置文件方可实现,本文总结了 Surge 配置文件系统的一些梳理。 https://community.nssurge.com/d/508-surge 频道 @who_channe

Signed MAICOO

8 Apr 2021, 09:15 UTC≈1,080 viewsread 6 August 2026

为了满足各种使用场景的复杂性,Surge Mac 4.1.0 Beta / Surge iOS Beta 1903 开始支持将配置的一个段分离至另一个文件中。 如: [General] loglevel = notify [Proxy] #!include Proxy.dconf [Proxy Group] #!include Group.dconf [Rule] #!include Rule.dconf 其中所引用的另一个文件,必须包含对应段的 [] 声明。因此,该文件既可以是一个只包含部分段的文件(一个或多个),也可以是一个完整的配置。 使用该功能,你可以: 1 只引用服务商托管配置的 [Proxy] 和 [Proxy Group] 段,自行编写其他段。 2 在多个配置间共享某几个段的内容。 一些说明: • 在通过 UI 修改配置后,会按照 include 的声明将配置写入对应的分离配置段文件。 • 如果引用的

Signed MAICOO

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

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.

Mentions

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.

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.

“自留 channel” (@who_channel), 291 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/who_channel.

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.