1 Jul 2026, 19:14 UTC≈2,980 views17 reactionsread 7 August 2026
💥💥 已更新 💥💥
👍13🥰3❤1
Channel
Notif 💬
@Enkelte_notif
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,738subscribers
+47 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 | -1002261288662 |
|---|---|
| Type | Channel |
| Username | @Enkelte_notif |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/Enkelte_notif |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 17:56 | 3,738 | +24 |
| 13 Aug 2026, 10:34 | 3,714 | +20 |
| 10 Aug 2026, 21:16 | 3,694 | +5 |
| 8 Aug 2026, 02:17 | 3,689 | -2 |
| 7 Aug 2026, 12:33 | 3,691 | first reading |
Engagement
20 posts held, back to 15 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 2 pagesof 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 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
187 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 48.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 90 | 48.1% | |
| ❤ | 63 | 33.7% | |
| 🎉 | 9 | 4.81% | |
| ✍ | 6 | 3.21% | |
| 🥰 | 5 | 2.67% | |
| 👏 | 4 | 2.14% | |
| 😁 | 4 | 2.14% | |
| 😍 | 4 | 2.14% | |
| 👨💻 | 1 | 0.535% | |
| 🔥 | 1 | 0.535% |
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 20 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 187reactions 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 15 March 2026 to 1 July 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
12 May 2026, 00:13 UTC≈6,480 views13 reactionsread 7 August 2026
比较有趣的一点是 GrainTCP 用到的灰出口接口 request.fetcher.connect 早在至少2024年之前就存在了，但是通过搜索发现好像没有什么开源代码用到 request.fetcher.connect，而是导入 socket() 模块接口，所以 GrainTCP 也是第一个引入这个用法的开源项目，可以一定程度上减少1101代码特征。
❤10😁2👍1
12 May 2026, 00:07 UTC≈6,500 views27 reactionsread 7 August 2026
⚡️ GrainTCP — 面向 Cloudflare Workers 的 VLESS over WebSocket TCP 主线实现 🥇 与早期那类重状态机传输代码不同，这份代码的主方向不是继续堆大缓冲 / 大定时器，而是把 Workers 下真实 TCP relay 的主热路径收紧。 🥈 上传侧使用 显式队列 + 机会性合包 + microtask drain，把高频小包尽量压成更少的实际写入次数。 🥉 下载侧已经收敛成两段式主线：大包 direct send + 立刻换新 buffer，小包 <32KB 做 grain 聚合，专门削减高频小 frame 场景下的 send() 次数与调度压力。 补充几点： - 32KB 是 聚合上限，不是“必须攒满才发” - chunk=64KB 是当前通用默认档，不是源码硬上限 - concur=4 适用于 Workers / Pages 默认部署，如果改…
👍19❤7🎉1
11 May 2026, 20:40 UTC≈4,650 views13 reactionsread 7 August 2026
Shadowsocks 的实验实现 — CF-Workers-Shadowsocks 作为面向 Shadowsocks over WebSocket 场景的 Cloudflare Worker 实验项目，它不是只支持单一 AEAD 的简化代理，也不是单纯把现成流量套进 WS 转发，而是在 Worker 内直接实现： 客户端 SS 数据 → WebSocket 接入 → 按 method 解密 → 解析目标地址 → connect() TCP 出站 → 回包再按对应 method 加密返回 用这种方式，把旧流密码、AEAD、Shadowsocks 2022 统一收进单文件 Worker 内完成。 CF-Workers-Shadowsocks 接近协议级实验：它不是依赖外部 SS 服务端，而是在 Workers 内直接实现Shadowsocks 的方法适配、密钥派生、分帧解包与回包加密。 📍 项目定…
👍9❤3🎉1
29 Apr 2026, 20:12 UTC≈4,560 views12 reactionsread 7 August 2026
信道已启，ToiCF 之 GitHub 道场由此铺开。 研究之种、测试之码、协议之验、工具之养，将如落叶归根，渐次归入组织之库。 库之方向，大致如下： • 边缘网络与运行时之舞，观其行止 • 代理、隧道、中继之协议，于静室中实验 • 真实链路之验证，可复现之实测工具 • Cloudflare Workers 等平台之上，探网络之能 • 实验代码、测试数据、相关文档，皆须维护 若君对此诸方向心生涟漪，愿参与测试、整理文档、提交代码、复现实验或长期维护，便可申请加入此组织。
✍6❤4👍2
29 Apr 2026, 19:40 UTC≈4,490 views3 reactionsread 7 August 2026
基于 TLSClient 的进阶功能 — CF-Workers-TOR 作为面向 Tor exit 场景的 Cloudflare Worker 实验项目，它不是依赖系统 Tor 客户端，也不是简单转发现成代理流量，而是在 Workers 内通过内嵌 TLSClientMini 直接连接真实 Tor relay： 候选 Tor relay path → 第一跳 Tor relay → 真实 TLS 握手 → CREATE2 / EXTEND2 建立 Tor circuit → BEGIN / DATA 转发普通 clearnet 目标 用这种方式完成 Cloudflare Workers 内部 Tor relay TLS、ntor 派生、relay cell 加解密和 exit stream 转发。 CF-Workers-TOR 接近协议级实验：它把 TLSClientMini 从"真实链路验证工具"进一步扩展成 Tor …
❤3
16 Apr 2026, 17:12 UTC≈5,060 views5 reactionsread 7 August 2026
Debug: ① TLS 1.3 解密后的明文尾部 0 padding：从末尾向前跳过 padding 0x00，取最后一个非零字节作为 inner content type。 ② TLS 1.3 inner alert 处理：正确识别解密后的 inner alert；遇到 close_notify 结束读取，其他 alert 直接抛错。 同步更新 HTTPSMini_v1.js 和Check_Proxy.js。
👍4❤1
16 Apr 2026, 06:32 UTC≈4,720 views4 reactionsread 7 August 2026
修正了微小的逻辑谬误，如修补战甲的裂痕！昔日IPv4_Only那愚蠢的哨兵，竟因两路出口IP相同而陷入迷茫，致使轮询的ProxyIP域名化作“未知”迷雾，如同奥丁在迷雾中迷失方向。即刻部署此更新，荣耀归于勇者！
❤4
16 Apr 2026, 02:39 UTC≈4,540 views9 reactionsread 7 August 2026
File
基于TLSClient的多重功能 - Check_Proxy.js 作为面向 ProxyIP 场景的 Cloudflare Worker 检测器，它放弃了传统基于 /cdn-cgi/trace 的描述型判断方式，转而使用内嵌 TlSClient 进行真实链路验证: 直接让候选入口 → 实际由 Cloudflare CDN 反代的域名 → 通过真实 SNI/Host + TLS 握手 + HTTP → 请求 来判断该 IP 是否具备真正的 ProxyIP 反代能力。 相比只检查 /cdn-cgi/trace 是否存在、响应格式是否符合预期的描述型方法， Check_Proxy 更接近真实使用场景，能明显减少“有 trace 但不能用”的误判，把检测逻辑从表面特征识别提升到实际功能验证，正确率高达100%。 因此作为纯 Workers 实现检测 ProxyIP 的唯一入口。 测试入口: https://pr-a…
❤6🎉2👏1
13 Apr 2026, 14:39 UTC≈4,180 views3 reactionsread 7 August 2026
File
v1 版本修复以下内容∶ ① 原先会无条件的将IP/IPv6作为SNI转发到代理服务器，导致部分代理无法正常使用。 ② 加入忽略TLS发出的警告，兼容部分域名入口的代理。 已通过随机取量500+测试样本的严格基准测试。
❤2👍1
13 Apr 2026, 00:05 UTC≈4,160 views5 reactionsread 7 August 2026
SSTP代理出站测试 日本🇯🇵教育网 vless://[email protected]:2083/?type=ws&encryption=none&flow=&host=a.main-506.workers.dev&path=%2Fsstp%3A%2F%2Fpublic-vpn-58.opengw.net%3A443%3Fed%3D2560&security=tls&sni=a.main-506.workers.dev&fp=chrome&packetEncoding=xudp&ech=cloudflare-ech.com%2Bhttps%3A%2F%2F223.5.5.5%2Fdns-query#SSTP
👍3❤1👨💻1
12 Apr 2026, 23:58 UTC≈4,580 views7 reactionsread 7 August 2026
File
SoftEther.js 乃 VPANGTE 之战士重铸协议！ 非那凡俗之 WS 至 TCP 之仆从，乃仿VPANGTE（日本大学之伟业）之狂战士实验！ 其核心如奥丁之谋略： • 于受限之 Workers 荒原重筑通讯战路 • 不倚赖那完整系统之网络长盾 • 在脚本之铁砧上锻造协议与转发 数据之路径如瓦尔哈拉之梯： VLESS over WebSocket → 战士 → 虚拟战路 → PPP/IP/TCP → 荣耀目标 代码已铸就： • VLESS 之解析 • UUID 之试炼 • 目标地址/港口之掠夺 • 虚拟战路之建立 • PPP 之谈判（LCP / PAP / IPCP） • 夺取虚拟 IP 之财富 • 手工锻造 IPv4/TCP 之矛 • SYN / ACK / PSH / FIN 之战吼 • 分段、序号、校验和之计算 • WebSocket 与远端 TCP 之双向桥梁 与普通 Worker 之奴仆有别：…
👏2🥰2😁2❤1
Showing the 12 most recent of 20 posts we hold for @Enkelte_notif. 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.
Citation-graph rank
Citation-graph rank — 1,199,744 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 registered channels — 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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Notif 💬” (@Enkelte_notif), 3,738 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Enkelte_notif.
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.