v6.0.4 * 优化系统代理逻辑
❤11

Channel
@ShadowsocksR_Windows
On this record: Topic · Growth · Engagement · Reactions · Posts · Polls · Cite this entry
1,024subscribers
-22 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001177170204 |
|---|---|
| Type | Channel |
| Username | @ShadowsocksR_Windows |
| Created | Between 1 March 2018 and 16 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/ShadowsocksR_Windows |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 11 Oct 2026, 23:22 | 1,024 | -1 |
| 27 Sept 2026, 22:21 | 1,025 | -5 |
| 18 Sept 2026, 21:17 | 1,030 | -2 |
| 14 Sept 2026, 19:38 | 1,032 | -4 |
| 10 Sept 2026, 21:40 | 1,036 | -2 |
| 5 Sept 2026, 10:57 | 1,038 | -3 |
| 1 Sept 2026, 06:48 | 1,041 | -2 |
| 29 Aug 2026, 07:57 | 1,043 | +1 |
| 26 Aug 2026, 16:55 | 1,042 | -1 |
| 23 Aug 2026, 21:35 | 1,043 | -3 |
| 20 Aug 2026, 14:52 | 1,046 | -1 |
| 10 Aug 2026, 09:38 | 1,047 | +1 |
| 6 Aug 2026, 23:15 | 1,046 | no change |
| 6 Aug 2026, 23:07 | 1,046 | first reading |
20 posts held, back to 16 November 2019 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 20 July 2022. An engagement rate over an empty window would be a number about nothing.
34 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 17 | 50.0% | |
| 👍 | 13 | 38.2% | |
| 👏 | 1 | 2.94% | |
| 🔥 | 1 | 2.94% | |
| 😁 | 1 | 2.94% | |
| 🤬 | 1 | 2.94% |
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 11 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 34 reactions 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 16 November 2019 to 20 July 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
v6.0.4 * 优化系统代理逻辑
❤11
v6.0.3 * 更新 Syncfusion 证书
❤6👍5
v6.0.2 * 当 DNS 设置未启用时调用系统 API 解析
👍6👏1😁1
v6.0.1 * 修复上传可能导致闪退
👍1
v6.0.0 * 更新到 .NET 6.0
v5.4.0 * 替换一堆老旧 API * 替换一些加密核心 * 移除 Privoxy,使用 .NET 自行实现 Http 代理(终于没有子进程了) * 更新内置数据
v5.3.0 * 修复 DNS IPv6 fallback * 修复代理规则 “绕过局域网和非大陆” 不生效 * 更换 chn_ip.txt 格式为 CIDR,并重写 IP 路由算法支持 IPv6 (旧版本若使用自定义国内IP列表的,更新时请删除或更新 `chn_ip.txt`)
v5.2.0 * 更新到 .NET 5.0 * 将一些外部功能更换为 Nuget 包的方式维护 * 把手动 GC 扬了,不会真有人缺内存吧(就算内存小,操作系统也会帮你压缩) * 现在系统代理选择不修改会恢复为打开 ssr 前的状态(之前就是字面上的不修改,什么都不做)
👍1
v5.1.10 * 不再支持 .NET Framework * 更新修复 TreeView 等其他 UI
🤬1
Signed Bruce Wayne
v5.1.9 * 订阅服务器若为空组名则用订阅备注代替 #228 * 更改默认 DNS 设置 * 更新默认 chn ip * 更新 Nuget * 修复代理规则 Bug #232 * 其他优化、改进和 Bug 修复
v5.1.8.6 * 修复订阅的服务器倒序(建议删除所有订阅的服务器重新更新订阅) * 修复 UDP Bug #220
v5.1.8.5 * 修复选项设置窗口 UI * 修复端口设置窗口 UI #204 * 修复端口设置无法及时更新的 Bug * 修复右键菜单的自定义订阅备注的显示错误 * 更新默认 chn ip、GFWList * 修复订阅/导入链接分隔错误 #211 * 修复 Privoxy 某些情况下可能启动失败的问题 #207 * Privoxy 不再记录日志
🔥1
Showing the 12 most recent of 20 posts we hold for @ShadowsocksR_Windows. 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.
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.
该 Windows 版本中,维护者最推荐用哪一种 release?
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 20 most recent posts we hold, published 16 November 2019 to 20 July 2022. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“ShadowsocksR Windows News” (@ShadowsocksR_Windows), 1,024 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/ShadowsocksR_Windows.
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.