Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.3-2785
- Now you can see the number of times a rule has been used in the rule list.
- Optimized the implementation method of blocking QUIC traffic to increase the likelihood of clients correctly falling back.
- The Smart group will use the SUBSTITUTE policy (DIRECT) instead of failing directly when there are no sub-policies.
- Fixed an issue where the
- Added a new rule type
- Optimized DNS request logs. Now more information is displayed. Additionally, if DIRECT policy connects directly without triggering DNS in the rule system, related DNS logs can still be shown.
- When deleting a policy that is being used by a policy group, it is now allowed to delete it directly and automatically remove it from all policy groups.
- Bug fixes and other Improvements.
Official Channel: @SurgeTestFlightFeed
Version 5.7.3-2785
- Now you can see the number of times a rule has been used in the rule list.
- Optimized the implementation method of blocking QUIC traffic to increase the likelihood of clients correctly falling back.
- The Smart group will use the SUBSTITUTE policy (DIRECT) instead of failing directly when there are no sub-policies.
- Fixed an issue where the
server-cert-fingerprint-sha256 parameter was not effective for TLS-like protocols with sni=off settings.- Added a new rule type
HOSTNAME-TYPE, used to determine the type of request hostname. Optional values are: IPv4, IPv6, DOMAIN, SIMPLE. (SIMPLE refers to hostnames without a dot, such as localhost)- Optimized DNS request logs. Now more information is displayed. Additionally, if DIRECT policy connects directly without triggering DNS in the rule system, related DNS logs can still be shown.
- When deleting a policy that is being used by a policy group, it is now allowed to delete it directly and automatically remove it from all policy groups.
- Bug fixes and other Improvements.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Release
Version 5.7.3-2785
- Now you can see the number of times a rule has been used in the rule list.
- Optimized the implementation method of blocking QUIC traffic to increase the likelihood of clients correctly falling back.
- The Smart group will use the SUBSTITUTE policy (DIRECT) instead of failing directly when there are no sub-policies.
- Fixed an issue where the
- Added a new rule type
- Optimized DNS request logs. Now more information is displayed. Additionally, if DIRECT policy connects directly without triggering DNS in the rule system, related DNS logs can still be shown.
- When deleting a policy that is being used by a policy group, it is now allowed to delete it directly and automatically remove it from all policy groups.
- Bug fixes and other Improvements.
Official Channel: @SurgeTestFlightFeed
Version 5.7.3-2785
- Now you can see the number of times a rule has been used in the rule list.
- Optimized the implementation method of blocking QUIC traffic to increase the likelihood of clients correctly falling back.
- The Smart group will use the SUBSTITUTE policy (DIRECT) instead of failing directly when there are no sub-policies.
- Fixed an issue where the
server-cert-fingerprint-sha256 parameter was not effective for TLS-like protocols with sni=off settings.- Added a new rule type
HOSTNAME-TYPE, used to determine the type of request hostname. Optional values are: IPv4, IPv6, DOMAIN, SIMPLE. (SIMPLE refers to hostnames without a dot, such as localhost)- Optimized DNS request logs. Now more information is displayed. Additionally, if DIRECT policy connects directly without triggering DNS in the rule system, related DNS logs can still be shown.
- When deleting a policy that is being used by a policy group, it is now allowed to delete it directly and automatically remove it from all policy groups.
- Bug fixes and other Improvements.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2786
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for UDP packets (mainly DNS) if there are higher priority sub-routes present, enhancing compatibility. However, automatic determination for TCP packets is currently not supported and still requires manual configuration through DIRECT policy aliases.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2786
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for UDP packets (mainly DNS) if there are higher priority sub-routes present, enhancing compatibility. However, automatic determination for TCP packets is currently not supported and still requires manual configuration through DIRECT policy aliases.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2788
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2788
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.100.0 (3246) is ready to test on iOS.
What to Test:
细节问题修正
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3246) is ready to test on iOS.
What to Test:
细节问题修正
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.100.0 (3247) is ready to test on iOS.
What to Test:
- 优化 No Default Route 模式的实现，现在 Surge Fake IP DNS 可以正确生效了。
（该模式使用了一种特殊的方法配置路由，以此绕过在开启 VPN 时 HomeKit Camera 无法连接的问题）
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3247) is ready to test on iOS.
What to Test:
- 优化 No Default Route 模式的实现，现在 Surge Fake IP DNS 可以正确生效了。
（该模式使用了一种特殊的方法配置路由，以此绕过在开启 VPN 时 HomeKit Camera 无法连接的问题）
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.100.0 (3248) is ready to test on iOS.
What to Test:
- 在 No Default Route 模式下不再配置系统代理，以避免产生问题
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3248) is ready to test on iOS.
What to Test:
- 在 No Default Route 模式下不再配置系统代理，以避免产生问题
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
⚠️版本回撤‼️
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
⚠️版本回撤‼️
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
⚠️版本回撤‼️
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
⚠️版本回撤‼️
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
⚠️版本回撤‼️
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
⚠️版本回撤‼️
Version 5.7.4-2787
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2789
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2790
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2790
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
频道加入樱花佬签到脚本喂饭Bot🎉
使用方法:
- /script help: 查询脚本列表
- /script 关键词: 查询匹配脚本
脚本列表如下:
Sakura Checkbox, 中免会员小程序签到, 高德地图打车签到, 米游社小助手, 森空岛小助手, 松鼠ios签到, 雨晨ios签到, 亚朵酒店签到, 腕表之家签到, 起点读书, AcFun签到, 天翼云盘, macat签到, 霸王茶姬小程序签到, 途虎养车积分签到, 小豆苗app签到, 华住会, 捷停车签到, 美图买菜任务, 元气森林会员中心, 沪上阿姨小程序签到, 哈啰单车奖励金签到, 知轩藏书签到, 阿里云签到, 什么值得买每日签到, 百度贴吧, 花夏ios签到, 网上国电费查询, 海信爱家, TestFlight自动加入, 雀巢会员俱乐部签到, Switch520签到, 夸克网盘签到, Boxjs备份, Boxjs恢复, Sub-Store, 轻之文库, 美团签到, STLXZ签到, B站每日等级任务, 巴哈姆特签到, 喜马拉雅签到任务, 奇瑞汽车, 巴奴毛肚火锅签到, 鸿星尔克签到, 建行生活, 达美乐披萨, 托迈酷客, 爱奇艺签到, 动漫之家日常任务, Hax数据监控, 微博超话, ChinaBroadnet, 刺猬猫, 慢慢买, 波点音乐自动签到, 美的会员签到, 网易云音乐人, Sub-Store, 比格披萨自助签到, 蜜雪冰城小程序签到, 猫耳FM签到, 卫岗天天订, IQOO社区签到, G动, 腾讯体育, 星星充电, 蒙牛母婴签到, 杜蕾斯会员中心签到, 正佳广场小程序签到, V2ex签到, 晓晓霸王餐, 胖乖生活, 杰士邦安心福利社, PP停车, 小米刷步, 摸鱼来啦, 超燃汇, 微博签到, 益禾堂签到, 龙湖天街签到, 唯品会签到, 唯品会自动续期, 柠季签到, 永旺Aeon签到, 万达智慧商业签到, 海底捞签到, 丘大叔柠檬茶, 哈根达斯, QQ音乐, 奈雪的茶, 康佰家, 希望云社区
使用方法:
- /script help: 查询脚本列表
- /script 关键词: 查询匹配脚本
脚本列表如下:
Sakura Checkbox, 中免会员小程序签到, 高德地图打车签到, 米游社小助手, 森空岛小助手, 松鼠ios签到, 雨晨ios签到, 亚朵酒店签到, 腕表之家签到, 起点读书, AcFun签到, 天翼云盘, macat签到, 霸王茶姬小程序签到, 途虎养车积分签到, 小豆苗app签到, 华住会, 捷停车签到, 美图买菜任务, 元气森林会员中心, 沪上阿姨小程序签到, 哈啰单车奖励金签到, 知轩藏书签到, 阿里云签到, 什么值得买每日签到, 百度贴吧, 花夏ios签到, 网上国电费查询, 海信爱家, TestFlight自动加入, 雀巢会员俱乐部签到, Switch520签到, 夸克网盘签到, Boxjs备份, Boxjs恢复, Sub-Store, 轻之文库, 美团签到, STLXZ签到, B站每日等级任务, 巴哈姆特签到, 喜马拉雅签到任务, 奇瑞汽车, 巴奴毛肚火锅签到, 鸿星尔克签到, 建行生活, 达美乐披萨, 托迈酷客, 爱奇艺签到, 动漫之家日常任务, Hax数据监控, 微博超话, ChinaBroadnet, 刺猬猫, 慢慢买, 波点音乐自动签到, 美的会员签到, 网易云音乐人, Sub-Store, 比格披萨自助签到, 蜜雪冰城小程序签到, 猫耳FM签到, 卫岗天天订, IQOO社区签到, G动, 腾讯体育, 星星充电, 蒙牛母婴签到, 杜蕾斯会员中心签到, 正佳广场小程序签到, V2ex签到, 晓晓霸王餐, 胖乖生活, 杰士邦安心福利社, PP停车, 小米刷步, 摸鱼来啦, 超燃汇, 微博签到, 益禾堂签到, 龙湖天街签到, 唯品会签到, 唯品会自动续期, 柠季签到, 永旺Aeon签到, 万达智慧商业签到, 海底捞签到, 丘大叔柠檬茶, 哈根达斯, QQ音乐, 奈雪的茶, 康佰家, 希望云社区
应群友需求，现已增加「适合Surge 5卡片视图 适配两个机场（英文）」配置文件，有需求的可以下载使用。
https://github.com/Rabbit-Spec/Surge/tree/Master/Conf
https://github.com/Rabbit-Spec/Surge/tree/Master/Conf
GitHub
Surge/Conf at Master · Rabbit-Spec/Surge
Surge自用配置以及模块和脚本. Contribute to Rabbit-Spec/Surge development by creating an account on GitHub.
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2791
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2791
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#Mac #Beta
Version 5.7.4-2791
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Version 5.7.4-2791
In previous versions, if the enhanced mode was enabled, all outgoing packets would be forced to use the primary interface due to Surge overriding the system's routing table. This bypassed the routing table to avoid creating a loop.
However, this also caused issues where packets could not be sent from the correct interface in cases with multiple network cards or other VPNs.
This version improves on that design. Now, in enhanced mode, Surge will automatically check routes and still use standard routing for TCP/UDP packets if there are higher priority sub-routes present, enhancing compatibility.
Official Channel: @SurgeTestFlightFeed
Forwarded from Surge's Changelog
#iOS #TestFlight
Surge 5 5.100.0 (3249) is ready to test on iOS.
What to Test:
- 修正规则集中包含重复的 DOMAIN 与 DOMAIN-SUFFIX 规则时，可能导致 DOMAIN-SUFFIX 失效的问题
- 发现有用户因为配置了过于频繁的 cron 脚本（10s 一次）导致电量消耗激增。该版本增加了 cron 脚本运行频率的自动计算，当单脚本超过每小时 10 次时给于警告
Official Channel: @SurgeTestFlightFeed
Surge 5 5.100.0 (3249) is ready to test on iOS.
What to Test:
- 修正规则集中包含重复的 DOMAIN 与 DOMAIN-SUFFIX 规则时，可能导致 DOMAIN-SUFFIX 失效的问题
- 发现有用户因为配置了过于频繁的 cron 脚本（10s 一次）导致电量消耗激增。该版本增加了 cron 脚本运行频率的自动计算，当单脚本超过每小时 10 次时给于警告
Official Channel: @SurgeTestFlightFeed