Paily Connect pinned «我们始终相信,开源不仅意味着分享代码,也意味着让一个项目拥有超越原本团队的可能。今天,我们也成为了其中的一分子。 由于资源有限以及团队成员个人原因,我们决定彻底停止 Paily Connect 的服务运营,并将核心代码库正式开源: https://github.com/openpaily/paily-core 我们希望通过开源,让 Paily Connect 过去积累的一些代码和思路能够继续被看到、被研究,也希望如果有人对这个项目感兴趣,可以在此基础上继续构建自己的服务。 如果您正在维护本项目的一…»

Channel
Paily Connect
@nodpai
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
8,462subscribers
+297 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001597704516 |
|---|---|
| Type | Channel |
| Username | @nodpai |
| Description | Paily Connect 免费订阅。 官网: https://pai.yt 群组: https://t.me/commpai 前往置顶消息查看订阅信息。 |
| Created | 17 July 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/nodpai |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 16:51 | 8,462 | -15 |
| 7 Nov 2026, 12:45 | 8,477 | -6 |
| 4 Nov 2026, 09:37 | 8,483 | -14 |
| 1 Nov 2026, 04:40 | 8,497 | -19 |
| 28 Oct 2026, 23:19 | 8,516 | +2 |
| 26 Oct 2026, 01:57 | 8,514 | +6 |
| 22 Oct 2026, 18:51 | 8,508 | +14 |
| 19 Oct 2026, 04:48 | 8,494 | +30 |
| 16 Oct 2026, 12:59 | 8,464 | +24 |
| 13 Oct 2026, 23:41 | 8,440 | +46 |
| 8 Oct 2026, 14:21 | 8,394 | +39 |
| 2 Oct 2026, 06:20 | 8,355 | +51 |
| 16 Sept 2026, 14:40 | 8,304 | +31 |
| 12 Sept 2026, 12:21 | 8,273 | +9 |
| 8 Sept 2026, 09:18 | 8,264 | +23 |
| 2 Sept 2026, 17:48 | 8,241 | +14 |
| 31 Aug 2026, 02:04 | 8,227 | +18 |
| 28 Aug 2026, 09:43 | 8,209 | +20 |
| 25 Aug 2026, 16:38 | 8,189 | +22 |
| 22 Aug 2026, 07:56 | 8,167 | first reading |
Engagement
24 posts held, back to 28 January 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 39 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 24 posts for this entry, the most recent from 19 September 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 220
- Videos
- 6
- Links
- 144
Lifetime counters from Telegram’s own channel header, read 12 November 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.
Reaction mix
73 reactions across 2 posts, in 5 distinct kinds. The most used accounts for 67.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 49 | 67.1% | |
| ❤ | 12 | 16.4% | |
| 🙏 | 6 | 8.22% | |
| 😢 | 5 | 6.85% | |
| 🤣 | 1 | 1.37% |
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 3 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 73 reactions 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 28 January 2025 to 19 September 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
Channel name was changed to «Paily Connect»
我们始终相信,开源不仅意味着分享代码,也意味着让一个项目拥有超越原本团队的可能。今天,我们也成为了其中的一分子。 由于资源有限以及团队成员个人原因,我们决定彻底停止 Paily Connect 的服务运营,并将核心代码库正式开源: https://github.com/openpaily/paily-core 我们希望通过开源,让 Paily Connect 过去积累的一些代码和思路能够继续被看到、被研究,也希望如果有人对这个项目感兴趣,可以在此基础上继续构建自己的服务。 如果您正在维护本项目的一个分支,您可以通过频道私信联系我们,我们将在频道定期推荐高质量的项目。 Paily Connect 的运营至此告一段落。 感谢每一位使用过、反馈过问题、提供过建议,以及曾经关注过 Paily Connect 的用户。 中秋将至,也祝大家: 保持前行,保持热爱。 Paily Connect 团队
👍49❤9🙏6😢5🤣1
Paicatch2:多渠道的智能节点/订阅抓取工具 https://github.com/openpaily/paicatch2 Paicatch2是我们开发的一个项目,作为Paily Connect庞大节点池的内容来源。它负责爬取公开于互联网的节点或订阅,经过一系列工作流后推送至Paily Connect主端,等待进一步处理。 自Paimon Node 1.5开始,我们就将抓取系统更新到更为动态的2.0版本,即Paicatch2。它支持三种模式的抓取:通过telegram频道,通过一些定制的抓取规则,或者通过一些发布节点的wordpress网页。其中,通过telegram频道抓取的方式要求您拥有一个telegram账号专门用于抓取,它的工作原理是每隔一段时间处理所有未读消息。 现在,我们选择将其以MIT协议开源以回馈社区,并展示我们长时间以来进行的探索与研究。
情况通报 很不幸地告诉大家,由于国内最后一个测试点的下线,我们的服务不得不被迫中断,我们正在积极寻找新的解决方案。 我们为给各位带来的不便表示诚挚的歉意。
情况通报 近日,Paily Connect 主站荣获 GFW 的 SNI 屏蔽,我们很高兴能成为为数不多被官方所认可的免费订阅之一。 如您需要继续在墙内获取订阅,推荐您使用以下链接: Clash : https://sub.pai.yt/clash Base64 : https://sub.pai.yt/base64 Sing-Box: https://sub.pai.yt/singbox 我们也欢迎各位向我们提供资源,包括但不限于订阅反代,备用域名等。Paily Connect 的发展离不开您的支持。
❤3
建议收集 我们正在优化我们的订阅,如果您有想要的流媒体项目,或者对我们的订阅有什么改进的建议,欢迎在评论区提出!
支持我们 Paily Connect 为完全免费的公益项目,相关设施和服务器都由我们的团队人员自行购买或者搭建,无偿为大家提供高质量的免费订阅。 如果您愿意支持我们的工作,可以考虑捐赠我们或者成为我们的志愿者。我们欢迎包括但不限于以下这些: - 提供海外的稳定服务器资源以运行服务核心 - 提供中国境内的计算资源以测试节点 - 提供机场/自建节点订阅以提升订阅质量 - 成为志愿者参与维护订阅库/新功能开发(后者需要有编程经验) - 与我们合作,共同提升免费服务质量 - 向我们捐款(请通过频道私信) Paily Connect 离不开您的信任与支持,我们愿在各位的帮助下,为互联网作出更多的贡献❤️
我们正在跟进最新的运营商海外 QoS 情况,欢迎各位用户积极反馈在受影响网络下 Paily Connect 的使用体验。您也可以积极分享我们的服务,以帮助更多人在特殊时期保持备用连接。 移动优化订阅尚未恢复,我们推荐受影响的用户切换至电信优化订阅使用。我们诚挚邀请符合条件的用户向我们捐赠测试资源。
维护通告 移动优化订阅暂时不可用,请您暂时切换至 全局订阅 使用。 如果您有好的移动非公网机器资源(家宽亦可,推荐 2c2g 及以上,不限系统)并且想提供给 Paily Connect 节点测试服务,请通过 频道私信 联系我们,我们将感激不尽。
加入 Paily Connect 大家庭 如果你是 Paily Connect 的深度使用者,我们欢迎您加入我们的内部群聊。在这里,你可以对我们提出建议,或者与其他成员交流,交换想法。在这里你可以收到 Paily Connect 的最新功能与更新。 目前申请入群是由管理员手动通过,您必须至少拥有一个头像,并且是 Paily Connect 的深度使用者以及频道的老粉丝才拥有入群资格。如果你是知名频道主、行业内人员或非中文用户(not China Mainland user),通过频道私信,让我们确认,以便更快的进入群聊。 链接:https://t.me/+cFjvTyxWHoxmNTlh
更新说明 我们于今日对 Paily Connect 进行了小型更新,进一步提升了您的使用体验。更新如下: 1. 针对非 Clash 系客户端优化 我们针对 V2Ray,Sing-Box 等非 Clash 系客户端对订阅进行了系统性的优化,优化后的订阅将在此类客户端获得更佳的表现。 2. 分发逻辑优化 针对最近用户量上升导致部分节点表现下降的问题,我们在分发逻辑上进行了优化,将不同的用户负载平衡到不同节点上,确保订阅在更多用户使用时仍有不错的表现。 温馨提示: 为了获得最佳使用体验,我们仍推荐通过 Clash 类客户端(如 FlClash)使用 Paily Connect,Clash的支持永远在我们的第一梯队。 为了获得更准确的延迟,我们推荐您使用 Google 204(https://www.google.com/generate_204)作为您的客户端延迟测试链接。
Showing the 12 most recent of 24 posts we hold for @nodpai. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@nodpai named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 8 August 2026 – 4 November 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@wxgqlfx · 34,229
Telegram ranks this channel #7 of 37 here — alongside 36 others — read 5 September 2026
@CMLiussss_channel · 72,074
Telegram ranks this channel #11 of 47 here — alongside 46 others — read 21 August 2026
@freeVPNjd · 23,983
Telegram ranks this channel #12 of 31 here — alongside 30 others — read 19 September 2026
@go4sharing · 59,641
Telegram ranks this channel #12 of 40 here — alongside 39 others — read 29 August 2026
@WFVPN · 40,784
Telegram ranks this channel #16 of 32 here — alongside 31 others — read 31 August 2026
@MatsuriDayo · 45,738
Telegram ranks this channel #18 of 58 here — alongside 57 others — read 30 August 2026
@XFLTDtop · 19,443
Telegram ranks this channel #20 of 48 here — alongside 47 others — read 5 October 2026
@FreeVPN8 · 43,331
Telegram ranks this channel #22 of 30 here — alongside 29 others — read 30 August 2026
@chongshengvpn · 69,411
Telegram ranks this channel #26 of 35 here — alongside 34 others — read 20 August 2026
@FlClash · 54,302
Telegram ranks this channel #28 of 53 here — alongside 52 others — read 28 August 2026
@cheap_proxy · 26,294
Telegram ranks this channel #37 of 49 here — alongside 48 others — read 13 September 2026
@DNSPODT · 73,241
Telegram ranks this channel #59 of 59 here — alongside 58 others — read 20 August 2026
@surfboardnews · 28,395
Telegram ranks this channel #64 of 64 here — alongside 63 others — read 9 September 2026
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“Paily Connect” (@nodpai), 8,462 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/nodpai.
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.