AI 挺擅长发现事物间的隐秘联系并且进行应用,比如蛋白质折叠与特性 再比如前几天看到的“旧药新用”,不过这些前提是要有比较多的数据,如果是过于前沿的领域、没太多旧数据能关联过来的话,AI 仍需努力
👍59❤6⚡5🤣4🎉1💯1

Channel
@projectXtls
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
30,056subscribers
+427 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001408690055 |
|---|---|
| Type | Channel |
| Username | @projectXtls |
| Description | Donation: https://github.com/XTLS/Xray-core/issues/3668 GitHub: https://github.com/XTLS 中文群组:https://t.me/projectXray Русский: https://t.me/projectVless Persian: https://t.me/projectXhttp |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 49 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/projectXtls |
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Oct 2026, 18:26 | 30,056 | +12 |
| 23 Oct 2026, 21:05 | 30,044 | +11 |
| 22 Oct 2026, 22:15 | 30,033 | +15 |
| 21 Oct 2026, 21:50 | 30,018 | +14 |
| 20 Oct 2026, 13:28 | 30,004 | +9 |
| 19 Oct 2026, 10:39 | 29,995 | -5 |
| 18 Oct 2026, 12:30 | 30,000 | +9 |
| 17 Oct 2026, 15:41 | 29,991 | +10 |
| 16 Oct 2026, 14:57 | 29,981 | +7 |
| 15 Oct 2026, 13:30 | 29,974 | -2 |
| 14 Oct 2026, 14:00 | 29,976 | -5 |
| 13 Oct 2026, 04:55 | 29,981 | +19 |
| 9 Oct 2026, 00:17 | 29,962 | +24 |
| 4 Oct 2026, 16:57 | 29,938 | -4 |
| 26 Sept 2026, 19:37 | 29,942 | +1 |
| 19 Sept 2026, 17:16 | 29,941 | +2 |
| 17 Sept 2026, 02:57 | 29,939 | +15 |
| 15 Sept 2026, 05:39 | 29,924 | +8 |
| 13 Sept 2026, 14:36 | 29,916 | +13 |
| 11 Sept 2026, 15:57 | 29,903 | first reading |
89 posts held, back to 31 July 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 132 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 23 October 2026 |
|---|---|
| Posts held | 89 (31 July 2026 – 23 October 2026) |
| Views total | 389,670 |
| Reactions total | 2,393 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Oct 2026, 17:23 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 25 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
6,110 reactions across 89 posts, in 35 distinct kinds. The most used accounts for 26.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,607 | 26.3% | |
| 🤣 | 1,241 | 20.3% | |
| 😁 | 1,189 | 19.5% | |
| ❤ | 305 | 4.99% | |
| 👏 | 257 | 4.21% | |
| 🌭 | 238 | 3.90% | |
| 🍌 | 165 | 2.70% | |
| 🔥 | 98 | 1.60% | |
| 💅 | 77 | 1.26% | |
| 💯 | 77 | 1.26% | |
| 🤩 | 70 | 1.15% | |
| ❤🔥 | 69 | 1.13% | |
| 😈 | 68 | 1.11% | |
| 🌚 | 62 | 1.01% | |
| 🏆 | 61 | 0.998% | |
| 💘 | 47 | 0.769% | |
| 🗿 | 47 | 0.769% | |
| 🆒 | 42 | 0.687% | |
| 😎 | 41 | 0.671% | |
| ☃ | 37 | 0.606% | |
| 15 further kinds | 312 | 5.11% |
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 89 of the 89 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 6,110 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 89 most recent posts we hold, published 31 July 2026 to 23 October 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @projectXtls. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 89 most recent posts we hold for this entry, published 31 July 2026 to 23 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
AI 挺擅长发现事物间的隐秘联系并且进行应用,比如蛋白质折叠与特性 再比如前几天看到的“旧药新用”,不过这些前提是要有比较多的数据,如果是过于前沿的领域、没太多旧数据能关联过来的话,AI 仍需努力
👍59❤6⚡5🤣4🎉1💯1
10.22 直接先把该版本设为了 latest,似乎也不是不行,完整的 release notes 等月底或下个月初的版本吧,半年积攒的更新写起来有点酸爽,其实我几乎不用 AI,或许让 AI 来补,顺便 v26.9.8 多余了也被删了
👍40😎6❤4🔥2🤩2⚡1👏1
阿三开源互联网
🤣143🤩6😁4😍3❤🔥2🗿2🎄1👍1
https://github.com/XTLS/Xray-core/releases/tag/v26.10.21 紧急安全更新:由于前几天印度八张中间证书的私钥因过于简单而被破解,本版本内置的 RootCAs 依赖库移除了三张根证书(v26.10.10、v26.10.17 内置有这些证书,已被撤版),并使用 Go 1.27.3 编译以确保即使操作系统 CA 库未更新也会过滤掉问题证书,用户应尽快升级到该版本,月底发 stable release(操作系统的 CA 库可能更新较慢,所以要覆盖掉上一个 latest)
👍47🤣30👌4☃2❤2💘1🆒1
换来换去的都有不足,终于还是重开了当初的 Xray-rules-dat 文件夹 昨天发布的 Xray-core v26.10.17 相较于上周的版本,主要更新内容: - 内置了轻量版 TCP/IP 栈,性能翻倍,移除 gVisor,体积减小 4.3MB - 设置出站 interface 失败时会取消 dial,主要避免 TUN 入站陷入回环 - TUN 入站 autoSystemDnsToGateway 支持 FreeBSD,避免 DNS 泄露 - REALITY 同步至 Go 1.27.3 部分代码,XTLS Vision 的代码做了兼容 - MASQUE 客户端也支持了 XMUX 全部参数,默认 maxConnections 1 - XDRIVE 的一些合理改动,下个版本开始优化速度、延迟,敬请期待 - XDNS 支持了 DoH(包括 h3),Noise 也支持了 Lua,暂不开放内联 - Lua 暂时限制为仅沙盒,以及…
👍127🤣14❤9👏4❤🔥2🌭2🕊2🍾1
频道订阅数刚突破三万,可能 GFW 阵营加串子阵营也贡献了那么几百 这啥玩意儿啊,真论这个的话,谁吃谁的流量
👍29😁17🤔3🎄2💘1😍1
质疑,理解,成为,超越 之前还是太给反智大本营那些脑残逼脸了,言论太自由了,都串好几天了被踢了还敢有意见,世界随心情 ban 人的时候咋不见你们有意见😁
😁56👏9🌚4☃1⚡1🎉1
这两天好多人转发这消息,其实没逝的,虽然 VLESS Encryption 被偷到客户端密码也无法被解密或 MITM,但毕竟 Surge 群友认为没人会想去解密机场共用密码的 SS 不是,好在机场后来也与时俱进换成普遍 allowInsecure 的 AnyTLS 了,好事是有了前向安全,坏事是这下甚至不用密码就能被 MITM 了,不然为什么说中国翻墙娱乐圈未来可期😁
👏57😁23❤4☃1💯1🥰1
种什么种子?忽悠人加入它们的反智大本营吗?Cherry / drownrat 这智障真的是进哪里哪里就会被拉低智商,幸好我早把它踢了😁
😁46👍8👏4☃3🎉1🗿1🆒1
乐,Cherry 拿开盒威胁我并多次提“CS”的时候一点也没觉得是人身攻击 甚至早说了不是我的小号,Cherry 这弱智非觉得是我,开盒都开不明白
😁47👍7🤣5🎉3💘2🤩2❤1🤔1
那确实,不知道的歪果仁还以为在我强推 pin 证书之前有很多人 pin 证书所以 Xray 搞了个捅破天的漏洞呢,歪果仁根本想不到此前绝大多数人根本不 pin 证书😁,就比如强推 pcs 没覆盖到 AnyTLS 所以当时的生态留到了现在,自签机场少吗?其中又有几家 pin 了证书?怕不是没有 Chrome 指纹确实是鹦鹉,然而默认 Golang 指纹流行的话直接封掉就行都不用看别的,TSPU 还搞啥限制连接数甚至波及到了正常 Chrome
👍37☃2❤2💯1🤔1🥰1🆒1
我咋听说主动探测是不存在的,自签证书就行,顺便发现你能被 MITM “对客户端的识别”又是啥玩意儿,听说 Golang 指纹从来没有被针对过
🤣26💅4🤔3❤2😍2🆒1
Showing the 12 most recent of 89 posts we hold for @projectXtls. 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.
@projectXtls edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
Named by 5 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.
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.
@projectXtls named 3 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 8 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 38 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“Project X Channel” (@projectXtls), 30,056 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/projectXtls.
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.