📐 PAC: add options for direct and proxied groups

[database64128]

Please follow the guide below

• You will be asked some questions, please read them carefully and answer honestly

• Put an x into all the boxes [ ] relevant to your pull request (like that [x])

• Use Preview tab to see how your pull request will actually look like

• Searched for similar pull requests

• Compiled the code with Visual Studio

• Require translation update

• Require document update (readme.md, wikipage, etc)

What is the purpose of your pull request?

• Bug fix
• Improvement
• New feature

---

Description of your pull request and other information

• Configuration: geositeDirectGroups + geositeProxiedGroups + geositePreferDirect
• PAC: rule generation using these new groups + cleanup
• Closes GeoSite PAC interfere with Windows Store/Windows Feedback/Windows Mail, etc #2984
• Closes 可能geoip数据导致不需要走代理的却走了代理。希望增加域名白名单功能。 #2987
• Related: Geosite包含大量国内地址，未来有改进计划吗？ #2971, 启用shadowsocks之后uwp应用无法联网(无法连接互联网，不是不走代理) #2973, 新版本使用geosite导致winstore无法加载 #2974, Why did we change PAC source to geosite? #2981, attr 类型没有被正确处理 v2fly/domain-list-community#235

Notes

• The PAC mode now defaults to whitelist mode.
• geositeDirectGroups is initialized with cn and geolocation-!cn@cn.
• geositeProxiedGroups is initialized with geolocation-!cn.
• When geositePreferDirect is false (default), PAC works in whitelist mode. Exception rules are generated from geositeDirectGroups. Unmatched domains goes through the proxy.
• When geositePreferDirect is true, PAC works in blacklist mode. Blocking rules are generated from geositeProxiedGroups. Exception rules are generated from geositeDirectGroups. Unmatched domains are connected to directly.
• The new default values make sure that:
  • When in whitelist mode, Chinese domains, including non-Chinese companies' Chinese CDNs, are connected to directly.
  • When in blacklist mode, only non-Chinese domains goes through the proxy. Chinese domains, as well as non-Chinese companies' Chinese CDNs, are connected to directly.

[chenshaoju]

Base Shadowsocks-4.2.0.61-Release.exe, the generated pac.txt is whitelist correctly.

After change geositePreferDirect to true, The generated pac.txt is blacklist correctly.

But there is an issue: after quit Shadowsocks, changing the geositePreferDirect and select update local pac from Geosite, The pac.txt will not update, still old version, and no any information popup from the taskbar tray area.

[database64128]

But there is an issue: after quit Shadowsocks, changing the geositePreferDirect and select update local pac from Geosite, The pac.txt will not update, still old version, and no any information popup from the taskbar tray area.

The current behavior is to perform an update of pac.txt only when the upstream geosite database updates or it's the first run of a new version. So you're supposed to manually delete pac.txt to force a regeneration.

We are targeting v5 for the UI, which will fully support these features. For now, advanced users just have to put up with a few more clicks. 😅

[chenshaoju]

This may case user confused...

At least have a message bubble popup.

Looks need more work here. 😅

[chenshaoju]

👍 Looks good to me, but someone else must approve.

[JohnQuick]

The new default values make sure that:
When in whitelist mode, Chinese domains, including non-Chinese companies' Chinese CDNs, are connected to directly.
When in blacklist mode, only non-Chinese domains goes through the proxy. Chinese domains, as well as non-Chinese companies' Chinese CDNs, are connected to directly.

What's the difference of those two mode? Both modes state that "Chinese domains, as well as non-Chinese companies' Chinese CDNs, are connected to directly."
And there's no definition of "Chinese domains" and "non-Chinese domains".
And why are you determining whether it's a Chinese domain or not? Users only care whether this domain is accessible directly or not, no matter which category it's in.