|Qiu Yuzhou acd84297d8 Update issue templates||8 months ago|
|.github/ISSUE_TEMPLATE||8 months ago|
|LaunchHelper||1 year ago|
|Pods||1 year ago|
|ShadowsocksX-NG||8 months ago|
|ShadowsocksX-NG.xcodeproj||8 months ago|
|ShadowsocksX-NG.xcworkspace||1 year ago|
|ShadowsocksX-NGTests||1 year ago|
|proxy_conf_helper||1 year ago|
|.gitignore||8 months ago|
|.travis.yml||1 year ago|
|ISSUE_TEMPLATE.md||1 year ago|
|LICENSE||2 years ago|
|Podfile||1 year ago|
|Podfile.lock||1 year ago|
|README.md||11 months ago|
|_config.yml||2 years ago|
|genstrings.py||2 years ago|
Current version is 1.7.1
Next Generation of ShadowsocksX
It’s hard to maintain the original implementation as there is too much unused code in it.
It also embeds the
ss-local source. It’s crazy to maintain dependencies of
So it’s hard to update the
Now I just copied the
ss-local from Homebrew. Run
ss-local executable as a Launch Agent in the background.
Serve PAC JS file as a file URL. So there is only some source code related to GUI left.
Then I will rewrite the GUI code in Swift.
ss-localfrom shadowsocks-libev 3.0.5
ss-local is run as a background service through launchd, not as an in-app process.
So after you quit the app, the
ss-local might be still running.
Added a manual mode which won’t configure the system proxy settings, so that you could configure your apps to use the SOCKS5 proxy manually.
Contributions must be available on a separately named branch based on the latest version of the main branch
The project is released under the terms of the GPLv3.