Telegram RegisterThe public register of Telegram
Telegram profile photo for fancyss

Channel

fancyss

@fancyss_project

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

3,336subscribers

+145 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001707110394
TypeChannel
Username@fancyss_project
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/fancyss_project

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 94% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

3,1913,3363,263.57 August 2026 — 3,191 subscribers7 August 2026 — 3,193 subscribers10 August 2026 — 3,196 subscribers13 August 2026 — 3,197 subscribers16 August 2026 — 3,209 subscribers19 August 2026 — 3,216 subscribers23 August 2026 — 3,228 subscribers26 August 2026 — 3,237 subscribers29 August 2026 — 3,241 subscribers1 September 2026 — 3,240 subscribers5 September 2026 — 3,253 subscribers10 September 2026 — 3,263 subscribers14 September 2026 — 3,265 subscribers18 September 2026 — 3,268 subscribers27 September 2026 — 3,290 subscribers5 October 2026 — 3,311 subscribers12 October 2026 — 3,336 subscribers7 August 202612 October 2026
17 measurements spanning 66 days, net +145. 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 3,169–3,358 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 11:393,336+25
5 Oct 2026, 09:593,311+21
27 Sept 2026, 14:593,290+22
18 Sept 2026, 13:013,268+3
14 Sept 2026, 09:373,265+2
10 Sept 2026, 09:393,263+10
5 Sept 2026, 11:573,253+13
1 Sept 2026, 15:033,240-1
29 Aug 2026, 15:073,241+4
26 Aug 2026, 21:453,237+9
23 Aug 2026, 20:583,228+12
19 Aug 2026, 20:033,216+7
16 Aug 2026, 21:143,209+12
13 Aug 2026, 16:183,197+1
10 Aug 2026, 07:253,196+3
7 Aug 2026, 17:343,193+2
7 Aug 2026, 06:153,191first reading

Engagement

19 posts held, back to 29 March 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 3 pages of 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 19 posts for this entry, the most recent from 2 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
45s
Average length
23s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

104 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 77.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8177.9%
❤1918.3%
👎43.85%

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 17 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 104 reactions 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 29 March 2026 to 2 June 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

2 Jun 2026, 08:01 UTC≈4,950 views8 reactionsread 7 August 2026

【20260601】fancyss 3.5.30更新 注意:由于xray-core设定了2026年6月1日后不再允许不安全,所以如果你的节点无法正常使用,请更新服务器端配置正确证书,如果是自签证书,请配置pinnedPeerCertSha256(点阅字段为pcs),以正常使用节点。 - update Xray-core 升级到自编译 v26.6.1版本。 - update node-tool 升级到 0.1.16。 - update webtest 缓存生成版本更新到 `20260601_1`,避免升级后复用旧测速运行产物。 - fix 修复webtest因生成允许不安全的配置导致测速失败。 插件目前还在迭代期,等周边功能落实稳定后会继续更新节点分流功能,届时才会进入3.6.0 更新日志 | 下载地址 | 问题反馈 | 机场推荐1 | 机场推荐2 | anytls机场

👍5❤3

20 May 2026, 15:45 UTC≈3,730 views6 reactionsread 7 August 2026
Photo

【202605020】fancyss 3.5.29更新 - update SS http obfs 改为纯 Xray TCP HTTP header。 - update 新增 MTK 机型 GS-BE7200X 安装支持。 - update Xray-core 升级到 `v26.5.9-1bdb488`。 - update node-tool 升级到 0.1.14。 - update sub-tool 升级到 0.1.17,支持 Clash/Mihomo AnyTLS。 - update 订阅节点主身份改为 `profile_<profile_id>`。 - fix Xray 分流支持 SS 无 obfs / http obfs。 - fix Xray 分流继续拒绝 tls obfs。 - fix 切换节点时清理 obfs helper 残留。 - …

❤4👍2

10 May 2026, 13:02 UTC≈3,410 views8 reactionsread 7 August 2026

【202605010】fancyss 3.5.28更新 - Xray-core 升级到自编译 v26.3.27 - node-tool 升级到 0.1.13 - tuic-client 升级到 v1.8.1 - NaïveProxy 升级到 v148.0.7778.96-2 - 详细状态新增status-tool 和 websocketd内存占用 - 详细状态新增程序启动时间信息 - 修复详细状态中订阅数量一直为0的问题 插件目前还在迭代期,等周边功能落实稳定后会继续更新节点分流功能,届时才会进入3.6.0 更新日志 | 下载地址 | 问题反馈 | 机场推荐1 | 机场推荐2 | anytls机场

👍7❤1

9 May 2026, 16:52 UTC≈2,590 views3 reactionsread 7 August 2026

【20260503】fancyss 3.5.27更新 - 主要修复anytls-zig内存泄露问题 插件目前还在迭代期,等周边功能落实稳定后会继续更新节点分流功能,届时才会进入3.6.0 更新日志 | 下载地址 | 支持机型 | 问题反馈 | 机场推荐1 | 机场推荐2

👍3

4 May 2026, 03:06 UTC≈2,730 views6 reactionsread 7 August 2026
Photo

【20260503】fancyss 3.5.25更新 - 修复部分anytls节点因需要允许不安全导致不可用的问题 - 修复部分场景下插件状态检测一直waiting的问题(终于修复) - 修复DNS测试自定义域名检测错误的问题 - 修复添加订阅同步成功后订阅卡片显示节点为0的问题 - 修复选择节点卡片,卡片列表跳动的问题 插件目前还在迭代期,等周边功能落实稳定后会继续更新节点分流功能,届时才会进入3.6.0 下面有个AnyTLS的机场推广,我开发过程中最近几日使用的,虽然用得不多,但是这几日还算稳定,有需要的大家自己斟酌,我挂了aff,看能报销点token费用不。 更新日志 | 下载地址 | 机场推荐1 | 机场推荐2 | anytls机场

👍5❤1

3 May 2026, 14:07 UTC≈1,840 views15 reactionsread 7 August 2026
Photo

【20260503】fancyss 3.5.24更新,添加AnyTLS协议支持 添加AnyTLS协议支持,插件包体积增加了不到200KB,原anytls golang二进制6.1MB实在巨大,即使压缩也会占用不少空间,这也是fancyss一直不想添加AnyTLS支持的原因,但是这里得感谢codex + GPT5.5 不到一个小时就用zig重写了AnyTLS协议的zig语言实现(也感谢我自己掏钱买token)。编译并压缩后体积不到200KB。简直是储存空间小,性能不强的路由器上的福音。 眼尖的朋友可能都注意到了,fancyss用zig已经写了很多小工具,用来替代一些繁重的低性能shell代码。 比如用sub-tool后,以前订阅解析节点,TUF-AX3000这种弱鸡机型一秒能解析一个节点,GS7这种强点的一秒也就解析十几个。现在用了sub-tool后,节点的解析部分,基本上100多个节点就是1秒的事。 再比如status-…

👍13❤2

3 May 2026, 03:32 UTC≈1,650 views4 reactionsread 7 August 2026
Photo

3.5.24会加anytls支持,请期待 更新日志 | 下载地址 | 机场推荐1 | 机场推荐2

👍4

2 May 2026, 02:47 UTC≈1,550 views3 reactionsread 7 August 2026

【20260502】fancyss 3.5.23更新,目前进入相对稳定版本 - 修复一系列插件状态延迟检测的问题 - 弱性能机型如armv7机型,现在状态检测占用更少 插件目前还在迭代期,等周边功能落实稳定后会继续更新节点分流功能,届时才会进入3.6.0 更新日志 | 下载地址 | 支持机型 | 问题反馈 | 机场推荐1 | 机场推荐2

👍3

1 May 2026, 13:24 UTC≈1,450 viewsread 7 August 2026

帮朋友推一下,对我来说也是福音:出门在外,手机蜂窝挂VPN太费电,用这个socks5的telegram高速代理,出门在外tg再也不断连了。 自助下单机器人:@tgzxdaili_bot

1 May 2026, 13:24 UTC≈1,640 views4 reactionsread 7 August 2026
Photo

最近国家整治机场行业,导致大批量跑路。为了防止失联,一般都得配备三到四个机场,才能确保不会失联。但是可以直接用这个官方代理。如人在海外。 给大家推荐一个TG专用官方代理,免翻墙,免其他软件,官方TG打开就能用。 为什么选择专线?: 军工级加密守护您的信息安全。 专线级跨海带给您的高速网络。 自助下单机器人:@tgzxdaili_bot

👎4

29 Apr 2026, 14:04 UTC≈1,650 viewsread 7 August 2026
Poll

fancyss节点列表使用卡片还是表格

  1. 表格33%
  2. 卡片43%
  3. 无所谓24%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

29 Apr 2026, 14:04 UTCAnonymous Poll254 voters

fancyss节点列表使用卡片还是表格

  1. 表格33%
  2. 卡片43%
  3. 无所谓24%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 19 most recent posts we hold, published 29 March 2026 to 2 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“fancyss” (@fancyss_project), 3,336 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/fancyss_project.

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.