Telegram RegisterThe public register of Telegram

Channel

Project WARP

@ProjectWARP

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

1,146subscribers

+3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001652417743
TypeChannel
Username@ProjectWARP
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 live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/ProjectWARP

Growth

1,1431,1461,144.57 August 2026 — 1,143 subscribers7 August 2026 — 1,143 subscribers10 August 2026 — 1,145 subscribers13 August 2026 — 1,146 subscribers7 August 202613 August 2026
4 measurements spanning 6 days, net +3. 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 1,143–1,146 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:251,146+1
10 Aug 2026, 01:131,145+2
7 Aug 2026, 09:031,143no change
7 Aug 2026, 08:551,143first reading

Engagement

20 posts held, back to 21 July 2023the 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 31 March 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

159 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 54.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8754.7%
2213.8%
👏1811.3%
😢127.55%
🤬74.40%
🎉63.77%
🍾21.26%
👎21.26%
😁10.629%
🤔10.629%
🥰10.629%

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 18 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 159reactions 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 21 July 2023 to 31 March 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

11 Jun 2025, 04:04 UTC≈3,550 views8 reactionsread 7 August 2026

回旋镖这就来了 我是不是该说GitHub封的好 这波 GitHub 在大气层

👍6👏2

11 Jun 2025, 04:04 UTC≈3,020 views2 reactionsread 7 August 2026
Forwarded from @alist_news

项目已交由公司运营,之后我会帮忙审查开源版本仓库的代码,以及确保 release 的分发由 ci 自动构建,main 分支已开启分支保护,后续所有的提交都会经过 pr 审核。

2

11 Jun 2025, 04:01 UTC≈2,900 views1 reactionsread 7 August 2026
Forwarded from @sky66666666666666666666666666666Photo

Photo, posted without a caption

1

7 Apr 2025, 14:48 UTC≈4,030 viewsread 7 August 2026

继 fscarmen 的 warp 后 GitHub 光荣榜又新增一员大将

7 Apr 2025, 14:47 UTC≈3,410 views0 reactionsread 7 August 2026
Forwarded from @alist_newsPhoto

🫶发工单申诉中……

23 Dec 2024, 17:29 UTC≈9,010 views2 reactionsread 7 August 2026

2024.12.24 menu.sh v3.1.4 / warp-go.sh v1.2.3 Support Docker to externally listen on 0.0.0.0/0 without requiring the use of host network mode. Thanks to Bro @Anthony_Tel 支持 Docker 在无需使用 host 网络模式的情况下,对外监听 0.0.0.0/0。感谢网友 @Anthony_Tel

2

24 Sept 2024, 14:34 UTC≈5,580 views16 reactionsread 7 August 2026

2024.9.24 menu.sh v3.1.3 The Linux Client adds the MASQUE protocol option, available in both Proxy mode (menu 5) and WarpProxy mode (menu 14) Linux Client 增加 MASQUE 协议可选项,Proxy 模式(菜单5)和 WarpProxy 模式(菜单14)都可以使用

👍13🍾21

21 Sept 2024, 12:51 UTC≈5,550 views20 reactionsread 7 August 2026

WARP目前的几个协议分析 1. WireGuard (已实现) 上层协议 Any 底层协议 UDP - 无reserved原版 - 带reserved改版 - 带reserved+hmac改版 (BoringTun开源有具体的算法) 2. L2TP/IPsec (未研究) 上层协议 Any 底层协议 UDP - 当WireGuard无法连接时启用 - 仅位于 移动端App (iOS可复现 Android未知) - 认证信息由算法生成, 未深入研究 *可能已经移除 3. HTTP/3 Proxy - MASQUE (未实现) 上层协议 TCP/UDP/IP (尚未确定) 底层协议 QUIC (UDP) - mTLS 双向认证, 服务器自签名证书, 客户端算法生成自签名证书 (客户端有校验 无法MITM) - 未发布公网SNI (需HOSTS) 4. HTTP/1.1 Proxy (参考文档) 上层协议 TCP 底层协议

👏153👍2

21 Sept 2024, 08:52 UTC≈4,510 views3 reactionsread 7 August 2026

Cloudflare WARP MASQUE 协议需要 mTLS 双向认证 目前无法制作第三方客户端 https://blog.cloudflare.com/masque-building-a-new-protocol-into-cloudflare-warp/ https://datatracker.ietf.org/doc/draft-ietf-quic-multipath/

👍2😁1

1 Aug 2024, 13:09 UTC≈4,810 views7 reactionsread 7 August 2026

Cloudflare 决定终止 WARP+ 推荐计划 根据 Cloudflare 近日更新的技术文档,该服务商将于2024年11月1日结束 WARP+ 的推荐计划。届时,将不再提供新的推荐码。当用户的设备使用完现有的推荐配额时,将自动迁移到 WARP 免费计划。如果用户想在该时间点之后继续使用 WARP+ 需要付费订阅,该服务在美区的月费为$4.99美元。 推荐计划长期以来为那些刷流量“白嫖” WARP+ 的用户提供了诸多便利,现在CF决定关上这扇窗。而 Cloudflare Zero Trust 的大门还敞开着,只要使用 Zero Trust 账户同样可以轻易获得比普通 WARP 更好的连接。根据 CF 的文档,WARP+ 相较于免费版延迟更低速度更快,但对于中国大陆用户而言这种优势所带来的好处是微乎其微的。 大陆用户面临的更大问题是 —— 自6月6日以来,GFW 显著加强了对 WARP 服务的干扰,其可用性已经大幅下降

👍61

23 Jul 2024, 06:21 UTC≈3,760 views1 reactionsread 7 August 2026

https://warp.cloudflare.now.cc/ warp api 增加了获取加入 Zero Trust 所需的 token ;增加了生成 1923 PB warp+ license,现功能应该比较完善了。 使用说明打开 URL 就有了。

👍1

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

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

“Project WARP” (@ProjectWARP), 1,146 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/ProjectWARP.

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.