TGTGInsighttelegram intelligenceLIVE / telegram public index
返回频道列表
Surge Channel avatar

TGINSIGHT CHAT

Surge Channel

@SurgeChannel

科技

Surge唯一官方频道:https://t.me/SurgeTestFlightFeed 以下为第三方创建: 群连接 https://t.me/+TO9iLpyTE1FjZTM1 群频道 https://t.me/+nZUgB3lPosQ2Y2Y1

Subscribers4,670频道当前订阅规模
Tracked posts1,017频道帖子计数
Recent reach4,036最近帖子视图总和
Recent posts

最近帖子

第 78/85 页 · 共 1,017 条

发布 11月16日

#iOS#TestFlight Surge 5 5.21.0 (2960) is ready to test on iOS. What to Test: - 修正通过 QUIC 类协议作为代理链使用 WireGuard 可能崩溃的问题

328 views

发布 11月16日

#Mac#Beta Version 5.4.1-2491 #### Rule Engine Optimizations - The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed. 1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage. 2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs. 3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved. - A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms. - An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater. 4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule. 5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries. 6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference) - Main ruleset matching efficiency has been slightly optimized. - The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations. - RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters. - DOMAIN-SET rule sets also support configuration with extended-matching. #### Minor Optimizations - Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM. - All comments (at the beginning and end of lines) can now use #, //, ; three common comment symbols. - Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately. - Bug fixes.

330 views

Hashtags

发布 11月16日

#Mac#Beta Version 5.4.1-2490 #### Rule Engine Optimizations - The implementation of RULE-SET and DOMAIN-SET has been completely rewritten. Now, Surge automatically preprocesses and indexes rule sets during resource updates, significantly increasing the matching speed. 1. There is no longer any difference in performance and memory usage between RULE-SET and DOMAIN-SET types of rule sets, allowing flexible usage. 2. There is no longer a restriction in DOMAIN-SET rule sets that prevents the use of eTLDs. 3. The matching speed for DOMAIN, DOMAIN-SUFFIX, IP-CIDR, and IP-CIDR6 rules in RULE-SET has been greatly improved. - A DOMAIN/DOMAIN-SUFFIX rule set with approximately 100,000 entries used to take 100ms for a single match in the old version; now, it only takes single-digit ms. - An IP-CIDR rule set with approximately 10,000 entries used to take about 0.1ms for a single match in the old version. The new version only needs 0.0002ms, an improvement of about 500 times. The performance improvement for IP-CIDR6 rules is even greater. 4. In the new version, building a regional IP address collection using the IP-CIDR rule set offers the same performance as directly using the internal GEOIP rule. 5. The Inline Ruleset added in the previous version does not benefit from this optimization, but there is virtually no difference at the scale of hundreds of entries. 6. In previous versions, rules within a Ruleset were matched one by one from top to bottom. If rules requiring DNS resolution were included, DNS would only be triggered when starting to match that sub-rule. In the new version, if any rule requiring DNS resolution is included in the rule set, DNS resolution will occur before testing that rule set. (In most cases, there is no difference) - Main ruleset matching efficiency has been slightly optimized. - The efficiency of IP-CIDR6 rules has been significantly improved even in non-indexed situations. - RULE-SET rules can now be configured directly with parameters no-resolve and extended-matching, which are equivalent to configuring all sub-rules with these parameters. - DOMAIN-SET rule sets also support configuration with extended-matching. #### Minor Optimizations - Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM. - All comments (at the beginning and end of lines) can now use #, //, ; three common comment symbols. - Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately. - Bug fixes.

290 views

Hashtags

发布 11月16日

https://community.nssurge.com/d/2233-ip

585 views

发布 11月16日

#iOS#TestFlight Surge 5 5.21.0 (2959) is ready to test on iOS. What to Test: - 主规则匹配效率小幅优化 - IP-CIDR6 规则在非索引情况下的效率也得到大幅提升 - RULE-SET 规则可直接配置参数 no-resolve 和 extended-matching,均等价与为所有子规则配置了该参数

318 views

发布 11月16日

#Mac#Beta Version 5.4.1-2489 - Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM. - All comments (at the beginning and end of lines) can now use #, //, ; three common comment symbols. - Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately. - Bug fixes.

324 views

Hashtags

发布 11月15日

#iOS#TestFlight Surge 5 5.21.0 (2958) is ready to test on iOS. What to Test: - 修正特定的规则集建立索引时有概率出现的崩溃

324 views

发布 11月15日

#Mac#Beta Version 5.4.1-2488 - Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM. - All comments (at the beginning and end of lines) can now use #, //, ; three common comment symbols. - Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately. - Bug fixes.

330 views

Hashtags

发布 11月15日

#iOS#TestFlight Surge 5 5.21.0 (2957) is ready to test on iOS. What to Test: - 修正 DOMAIN-SET 在某些情况下依然无法被载入的问题 - 修正规则集中的 IP-CIDR6 规则未能正确被建立索引的问题

316 views

发布 11月15日

#Mac#Beta Version 5.4.1-2486 - Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM. - All comments (at the beginning and end of lines) can now use #, //, ; three common comment symbols. - Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately. - Bug fixes.

317 views

Hashtags

发布 11月15日

#iOS#TestFlight Surge 5 5.21.0 (2956) is ready to test on iOS. What to Test: 修正当使用的 RULE-SET 不存在或不包含任何有效规则时产生的崩溃。

287 views

发布 11月15日

#Mac#Beta Version 5.4.1-2485 - Now, when performing MITM, the certificate used for signing will be sent to the client together, to support using intermediate certificates for MITM. - All comments (at the beginning and end of lines) can now use #, //, ; three common comment symbols. - Profile error message prompt optimization, now it can give the exact line number where the error occurred more accurately. - Bug fixes.

287 views

Hashtags

12•••5•••10•••15•••20•••25•••30•••35•••40•••45•••50•••55•••60•••65•••70•••757677787980•••8485